Hey, folks. It's Ned Pyle again here to talk to you today about enhancing your security and saving time when you combine Windows Server 2022 and Windows 11. You know me, I'm from SMB and File Services. I'm going to focus really heavily on that very popular workload and show you how these things really operate best when combined. Let's go to it. Obviously, Windows 11 and Windows Server 2022 have just come out in the last year or so. You're probably still evaluating, still looking, still kicking the tires. What I love about this thing together, I call it 11 and 22 for ease of talking, is how when I combine them, I can get some experiences that you've really been waiting for for the last 20 years between the Windows and Server architecture. I think the one that you'll probably find the most valuable every single day is the time-saving piece that is SMB compression. We now offer the ability for you to compress larger, more inefficient files, things like VHDs, VHDX, ISO, DMP, anything files don't get smaller over time, they get bigger, right? Developers tend to get less efficient with their file sizes. SMB compression will make up that gap. It can be used with Explorer, Robocopy, MapDrive, shares, you can set it globally, it's very flexible, you don't need to teach your end users how to use it. That's always a recipe for failures, changing something that they've been using one way for 20 years, and then asking them to do it a different way. We don't require you to do that, and I'll show you with a nice demo here in a second. And you can also manage it yourself as an administrator using Windows Evans Center, PowerShell, Group Policy, editing the registry if you'd like to be a wacko. SMB compression is actually a variety of different kinds of compression we have Express, we have Huffman, we have LZNT, LZ77 pattern, negotiates automatically, and the likelihood of you getting anything but Express is really pretty low. And that's a really good balanced compression algorithm that does good performance with good compression, not the most overhead for the best compression. It's trying to find that happy balance where you get good per for not too much payment. Let's actually see this in action. So I have a nice demo here. I have a pretty inefficient file, it's called DogoTime, and inside this file, I've copied a few pictures of my dogs, as everybody always likes to see Ned's dogs and these types of demos. So here's from Halloween this year, Derby and Indy dressed as little dragons, and then there's a lion, a lion tamer, and some hash browns, and some happy flower time. Anyway, it's a handful of JPEGs. As you know, JPEGs do not compress, they're already a highly compressed format. So I'm gonna put them into this VHDX, this container file, this drive that I've mounted, and it's a one gig file using only about 10% of its space with data. So right now, if I was to copy this file, it's one gig file from my machine, and this is really my desktop, two file server at my office, and one gig, you can see the rate right here that we're going, it's not going super fast. It's going as fast as it can, but I have not really amazing internet here. In fact, I've just waited a little while, it's still taking a while. I waited a little bit longer, it's still going, we're a couple of minutes in here, with me doing the cooking show. If I look at my wireless network right now, I'm only getting about 43 megabits upstream, and if you were to go and run a little speed test application on my machine right now, you'd find out that that's the actual maximum speed that my cable provider goes. So now we've waited, and waited, and waited, and waited, we're gonna get to 100%. It's a little one gig file, it's not that big of a file. It takes almost four minutes for me to copy from my work from home office to my office office. That's not awesome. So let's get rid of that file and try this again, but with a little extra option on Robocopy of slash compress. So we're gonna go and hit boop, and this is going, seems like it's kind of still slow, except whoa, it's not slow anymore. And now it's done. That was from four minutes to nine seconds. So that's a pretty good exchange rate, right? My copy now takes instead of four minutes, just under 10 seconds for the exact same file.  But that's the beauty of this feature. We've put the ability for you to tag on compression all over the place. So here I'm in Windows Admin Center. I'm going to just look at one of the shares that I'm using right here is the scratch two share. And you'll notice that little column says compressed data here.  So the user doesn't know that compression is on. Compression is a negotiated thing. It's a requested thing where it's best effort, right? So if the server doesn't support it, who cares? If the client doesn't support it, who cares? But if they both support it, now my experience is instead of using Robocopy, which again, no user will use, if I just use explore and I drag that file onto that share, because compression is turned on on the share, watch my little chart here blow out, zoom. So yet again, it looks like I have like five times the bandwidth I do because that's how good the compression is. Now that's me doing one file or doing one share that doesn't really scale for your everyday kind of use. Let me turn compression back off on the share so you can see there's like nothing up my sleeve. Turn that off. This all works on the fly, by the way, as you can tell. Not rebooting servers, not restarting services, it just works. And I'm going to take a look here with PowerShell on my client. If I run get SMB client configuration that shows me all the SMB settings, and you'll notice now on Windows 11 that I have this request compression flag. So I can actually set compression on my client to just always compress, always try to compress no matter what is set on the server, no matter if I ran Robocopy, if I ran explore, and then you can just stop having to remember to do compression. You're never going to be able to teach your users how to like compress files. So just take it out of their hands, just put it here where we'll just try to do it. And if it works out, great, that suddenly their files just seem to copy much faster. They don't even need to be taught. It'll just be like a little treat. So now if I copy that same file, nothing's configured on the server. It's just on the client globally. You'll see that my chart was bananas here as my performance kicks in with compression yet again, four minutes to 10 seconds. You can also not just do this using PowerShell, which is a sort of an obvious pain point if you don't want to deal with PowerShell. We have group policy. So here I am running the group policy editor, but go into administrative templates into the network section. You'll see under landman server and landman workstation use compression. So I can just turn it on through group policy, deploy it as a policy object and active directory, blast it out to all my servers, all my users, some subset and not have to go and run PowerShell or edit the registry or do other shenanigans, right? That's the beauty of AD and group policy. I can also just map drives. So if I have users going into a login script or if I have a startup script, I can just say when you're mapping a drive, that map drive is always going to be compressed. It works for both PowerShell and USB mapping as well as the ancient net use command that you're probably still using because I use it too. And furthermore on that server, I can make those same kinds of global changes using SMB server configuration commandlet. So I take a look here, a lot of things you can set, but right down in there is request compression. And I can turn that on using set SMB server configuration and slowly type. You think that'd be a better type of system and basically type for a living, right? So it's a true, yes. And now anybody who connects to the server is going to tell the client you should try to compress those files with SMB. So if I go ahead and leave the copy that I had and I'm still using Explorer, like our regular kind of user would and I copy that file, it's going to compress. And anybody who connects to the server is going to compress. All right, that's compression. So that's something you're going to use every single day, it's going to make your life much easier. Let's talk about that next pillar, security of 11 and 22 together. When you combine those two together, and it's important that you combine 11 and 22 together because security, as you know, is always a negotiated capability when it comes to SMB, is we have now the most advanced encryption that you can use in the market, AS256, GCM, young future proof. That's the one where you start bringing it out against quantum computing. We have RDMA encryption now, meaning that in the past you'd use SMB direct, you might want to try to turn on compression for those data fabric workloads of SMB and the performance would absolutely tank because the DMA and RDMA, the direct memory access piece is something we share with the entire computer. And we didn't think that by having shared data, encryption would be a safe concept anymore because everything that's happening there is shared. The encryption's happening on the wire, that's not where you need to be safe, maybe safe end to end. And now we're doing encryption before and after you get through RDMA, so you get a little bit of a performance hit, which you're encrypted the whole way through. And we caught up SMB signing to use AS128's GMAC accelerated signing, so it'll offload, thinking about math onto your ARM or Intel processor and you'll get performance that's better than encryption with signing to prevent things like relay attacks and still be using AS128. All right, so compression was first, encryption was second, it's basically ease of use and safety and we're gonna combine the two in the end for something I call easy mobility, okay? 11 and 22, easy mobility. And that's where we bring SMB over quick. SMB over quick is a new replacement for SMB over TCP. It's an automatic TLS 1.3 VPN. You still have TCP, it's still there, it's still usable. If you opt in to SMB over quick, you now can access edge file servers safely from Windows and actually from other things as well. And now this is supposed to be a Windows and 22 sort of session, but we already have an Android client that we have done with a partner, so you can use mobile phones for this technology. What it means is telecommuters, mobile users, your highest security posture users can now use SMB as it is today through this highly secure, highly available, highly tunneled protocol of quick that works over the internet. It works using UDP, it's works everywhere. Much of the internet, about 25% is already using quick whether it's HTTP 3 or parts of DNS. And SMB is the first like major application protocol is designed for use with file servers to make use of this technology. I mean, quick is the future. So let's get to this little demo here. So here's another Windows 11 machine. This user is an editor over at some publishing house working on editing this coffee table book and this coffee table book is something that I'm trying to get published, not really. And it just has those dogs again that everybody wanted to see in Darby and Indy and then also all of our various foster dogs over the years. People know and love. In fact, if I didn't include them in a demo I would get nasty emails. So anyway, this user signs up, goes to a coffee shop. So it's today case, right? They were connecting through SMB. It worked fine for Word. They leave the building and it stops working. And it's, there's nothing that could be done, right? The SMB over TCP won't work over the internet. The user tries to go back to that map drive. I'm time compressing this error, this ridiculous behavior of Explorer where it finally times out after a whole minute. It just takes a whole minute to give up. So let's go to our experience as the administrator and go to file server settings using admin center and I'll configure SMB over Quick. And it's gonna be not that hard to do. So don't blink. I have a list of certificates that have been provided to the server. The ones that are valid for this purpose. I select the certificate I want and the names that it provides that a user can connect to. I decide if I want to enable the KDC proxy meaning that I'll use Kerberos through its own little side channel. And that's it. That, I mean, that's it. Now Quick is turned on and accessible. And the user who I have not rebooted or done anything with. Now, if they try to open this thing, this Word document, it will just start working because we try to use TCP before we try to use Quick. Meaning the user doesn't have to pick or choose or you don't have to do anything here. It'll just start working immediately. And you can see here in my Wireshark capture that I've got all this Quick stuff going on. I can map drives also specifically to use Quick. So if you don't like the behavior of always use Quick first, if it doesn't work, then try to use TCP. That can be changed using PowerShell. But I can also right here just specify me like in a map drive or me the administrator when I'm doing some task. I want to use say TCP because it'll be a little bit faster. I'm on a network that I trust. I don't want to deal with a slightly less performance in order to get my thing done or I'm already working fine. So I point to a server that might already have Quick on it but now I can say like, yeah, I don't want you to use Quick. Like I'm deciding not to use Quick. And so now we exit out of this various Shell commands. And if I just do a map drive net use and specify that same server, I can say, I've been using Quick this whole time you can still see it in Wireshark. But now if I choose my transport of TCP and I press honor, boop. Then it will just start immediately going back to SMB over TCP. And you can see right there in the Wireshark there was no, again, no rebooting, no restarting services, none of that nonsense. Just works on the fly like that. And I go back to my share. I open up my coffee table book and the user experience here when set up correctly they can't tell anything different when they're in the office or they're at home or they're at the coffee shop or whatever. It'll just work. It's pretty slick. Now, Quick comes from something new. It's Azure Edition Windows Server. The Quick client is in all versions of Windows. The Quick server is in the Azure Edition of Windows 22. And that means that you have an Azure Edition just like data center and standard that will run in Azure the public cloud or on Azure Stack. That's a brand new option until October of this year. You could not run Azure Edition anywhere but Azure. And now you can run it basically anywhere because if you have Azure Stack or Azure, you have on-prem and you have public cloud. And that means that your users can use SMB over Quick to servers running in your data center or in an Azure public cloud data center. They can't tell the difference and you get the flexibility if you want to be in a private cloud or public cloud to do whatever you want. That management story is now tied together as well so that when you get an Azure Stack running and you go to its new VM marketplace, it will deploy Azure Edition VMs for you. That means that you don't even have to pick and choose and get the right OS to do all this stuff. Azure Stack is gonna try and run Azure Edition. Azure Edition is available there for you to run SMB over Quick and compression and hot patch and storage replicas, new compression that also uses SMB's compression that I just showed you. Like this stuff's moving really fast. You have to keep up here because we keep iterating here. We're not waiting every three years anymore. This stuff's all coming out every year and sometimes sooner than every year. So that was a lot to take in. I have a large number of links here to share. The one I think is probably the most interesting to you right away is that ISO download. If you go to the Windows Server 22, what's new page? We actually have links to Azure Edition right there as ISOs. So if you don't have Azure Stack yet, you're still evaluating things. It requires hardware and stuff. You can download the ISO, deploy it onto a regular VM and kick the tires on SMB over Quick. Remember that compression and these other features exist in regular Windows Server 22. So you can always go to the eval center to get those. I really think that Windows 11 and 22 is the real state of the art for file services. When you combine these things together, you're getting that ease of use, that simplicity, that mobility, that security, and that efficiency that you need to do your job. I really wanna thank you for your time today. I know it's real precious. I hope you enjoyed this. And if you have questions, please find me over at the FileCamp blog. And thanks very much for your time.


Rene Choi is going to talk to us about stem cell transplantation in dry AMD Give a second to get his computer all fired up here All right, hello everybody So I'm Rene Choi. I just want to thanks thank Zach again for reminding me that my huge geek as well. I Knew that he thought that of me as I entered residency because one of the first questions he asked me was why are your glasses so thick? I'm not saying that we're really gonna miss you Zach All right, so let's get started today I'd like to cover a topic that I find personally to be very interesting, you know the last number of years I've been to Arvo and that's this topic of stem cells and they're Involvement in regenerating the retina So to begin this journey we really have to define what exactly stem cells are Stem cells are a group of cells right that are not committed toward any specific cell fate They have the limitless potential to regenerate proliferate cell for new and they can become any cell type in the body Now aside from embryonic stem cells There are also what are known as adult stem cells these are endogenous stem cells that are in our body throughout our lives That regenerate or replace lost tissue from everyday wear and tear Some of these include bone marrow stem cells Intestinal stem cells corneal stem cells which everybody hears particularly Familiar with as well as even neural stem cells in the brain However to date there are no identified retinal stem cells in the human eye And that and that's particularly Disappointing because there are a number of diseases that affect the retina an impaired vision by reducing the elements here That are responsible for processing vision many of these include retinitis pigmentosa cone-raw dystrophies age-related macular degeneration Diabetic retinopathy as well as glaucoma Now to emphasize the gravity of these diseases I'd like to demonstrate to you how somebody who's afflicted with retinitis pigment pigmentosa how this disease Manifests visually in this patient. There is a beautiful picture of a Teton National Park For all of us who are not afflicted with this disease. We have no problems seeing this image in its entirety, but over time somebody with retinitis pigmentosa Slowly loses their peripheral vision until They reach irreversible blindness, okay? So I thought to myself How amazing would it be if just like the cornea? We're able to regenerate lost Photoreceptors any other cell type you're interested in the retina just like in the cornea when the epithelial cells You know are abraded those new corneal stem cells grow in and replace that tissue so the first question I asked when I did my literature search was to Determine is there any evidence of regeneration that takes place in the retina regardless of the species? To begin this journey we first have to go into the history of stem cell regeneration 1744 Abraham Tremblay. He was a Swiss naturalist He was the first to observe that when you surgically resect a limb from a hydra It's able to regenerate that limb almost as if no intervention ever took place Few years later in 1781 Charles Benet is actually a cousin of Abraham Tremblay Realized that when he surgically resected the eye Then an anew anew was able to regenerate the lens as well as parts of the retina as well now this discovery set essentially Led to the in the next two centuries all the all the further investigations that took place in retinal regeneration So let's get to the core. What are the source of newly generated cells in the retina? Well, it depends on two things it depends on the species and also depends on where you're looking in the retina now in the Very center of the retina in amphibians the putative stem cells are thought to be the retinal pigmented epithelial cells and the fish It's thought to be the molar glial cells However, in both species in the peripheral retina There's an area known as the sillier marginal zone actually gives rise to new retina progenitors throughout the life of the animal Let's talk about that a little bit more. So here's the sillier marginal zone It lies in between the sillier epithelium and the neural retina and throughout the life of the animal It gives rise to new retina progenitors and cells of all type that are specific to the retina Now what's remarkable about the CMZ is that there's this feedback loop when you damage the retina in amphibians and fish The CMZ is able to to pick up on that and actually increase proliferation in the CMZ But what's even more remarkable? Is that if you ablate a specific cell type if you ablate for instance Amicron cells the CMZ picks up on that and actually generates a higher proportion of amicron cells compared to the other cell types Now what about in mammals, you know including humans. Do we have a CMZ? Unfortunately, we don't Now as I alluded to earlier the source of newly generated cells in the central retina are thought to be the retinal pigmented epithelial cells in amphibians Let's just cover touch a little bit about what retinal pigment to epithelial cells are responsible for it mainly serves as a Has a supportive role for the photoreceptor cells in the retina some of them include providing nutrients for the photoreceptor cells Absorbing UV light to protect the photoreceptor cells Recycling photopigment that's part of the visual phototransduction cascade as well as being responsible for Faggocytosing the photoreceptor outer segments as well Now in the amphibian retina in newts as well as frogs. It's quite amazing. What happens when you perform a retinectomy That's when you physically scoop out the retina you give the animal 30 days to recover. Okay It'll reestablish the retina almost as as if no intervention took place. It's quite remarkable Now what is this process entail? It's something known as RP trans differentiation. It's a two-step process Once the RP cells notice that the retina has been damaged it starts to undergo De-differentiation it becomes an earlier retinal progenitor cell type and then it starts to proliferate and then the second step is to Redifferentiate into all the different cell types within the retina now as I stated earlier in it's in fish It's thought to be the molar glial cells that are the putative stem cells after retinal damage Now I wanted to look in a literature and find out how exactly did they determine this It was a genius experiment that Pamela Raymond's group from the University of Michigan performed What they did was they developed the transgenic line of zebra fish where they had the GFAP promoter That's a molar glial cell specific promoter driving green fluorescent protein Thus all this all the molar glial cells were lit up with were lit up green essentially Now after they damaged the retina specifically ablating the cone and rod footer receptors They found out that there was co-localization between GFP as well as a marker for rod footer receptors as well as GFP GFP as well as a Marker for cone footer receptors thus suggesting that these cells have actually come from the molar glial cells How about in mammals? Well, we know in mice After damage to the retina there's a very limited response of proliferation of the molar glial cells, but they don't actually De-differentiate into a retinal progenitor cells however De-differentiation can take place or can be induced by misexpression of retinal stem cells specific genes However, after de-differentiation The re-differentiation phase is somewhat limited in terms of its profile It can only become certain cell types such as amocrine cells as well as bipolar cells However, what's noted is, you know the evidence is somewhat equivocal because Lineage tracing studies as has been done in fish have not been done in the mammal or in the mice specifically Now in humans as I stated to date There are no identified retinal stem cells in humans So the field has really come up with two translational approaches All right using stem cell stem cell transplantation in order to help Treat the retina and there comes in two approaches one is cell replacement where you use stem cells to actively Replace the lost retinal photoreceptors or other cell types that you're interested in and the other one is cell protection Where the stem cells provide a trophic factor for the remaining retina? There's a seminal paper Published by McLaren and colleagues back in The University College of London and what they noticed was that what they did was they had a retinitis pigmentosa model In mice and they transplanted rod progenitor cells into the sub retinal space of these mice They found out that these progenitor cells were able to differentiate into mature rod photoreceptors Structurally as well as functionally integrate into the retina as well And I should also mention that using the cell replacement Technique right now there are phase one and two trials of taking human embryonic stem cell derived RP cells Transplanting it into the sub retinal space of patients with geographic atrophy And so it's quite amazing, you know Now there's this new cohort of stem cells known as human derived neural stem cells All right, and it's obtained from fetuses from the second trimester There's this two seminal papers published by a group in KC I institute where they took the RCS rat That's a specific retinal degeneration modeling rat The primary defect in these rats is that they had they lack the ability to phagocytose the photoreceptor outer segments And thus this leads to toxic debris in the eventual death of the photoreceptor cells and when they take this this new this human derived neural stem cells and Transplanted into the sub retinal space of these these rats. They find out that not only do they preserve photoreceptor viability also synaptic connections with the second-order neurons and lastly also Functional vision as well based on a behavioral assay that's visually mediated And they found out actually that the mechanism that's responsible for this preservation of the photoreceptors and the rest of retina is twofold one is it actually acts or adopts the RPE's ability to phagocytose the Shed outer segments from the photoreceptors and it also provides trophic factors for the rest of the retina Now we know in geographic atrophy in patients with dry ARMD that part of the primary pathology involves the loss of the RPE loss of the RPE cells and therefore it can't provide those supportive function Or roles for the photoreceptor cells that's leading to further photoreceptor death There's a particular group Stem cell incorporated they performed or organized a multi-center phase one study To determine the safety profile of transplanting these human derived neural stem cells into patients with geographic atrophy And they found out that there was no adverse side effects with transplantation of these cells in eight patients or 15 patients So the question they asked us they asked a number of centers across the country to be part of their phase two trial specifically asking can sub retinal transplantation of these human derived CNS cells Decrease the rate of geographic atrophy and patients afflicted with this with geographic atrophy methods eight macular degeneration patients with geographic atrophy in both eyes They were going to choose the worst the eye with the worst best corrected visual acuity to transplant These human derived CNS cells into the sub-retinal space have them follow up on day zero one seven twenty eight and months 369 12 after transplantation where they would receive a complete eye examination as well as retinal imaging Including fundus autofluorescence OCT as well as photography Their primary outcome measures include Determining the rate of progression of geographic atrophy in these patients as well as secondarily Determine their best corrective visual acuity low luminance visual acuity as well as contrast sensitivity Now I should stop here and just tell you that this project has been put on hold right now because the company is actually Focusing their efforts on using these stem cells for spinal cord as well as brain trauma injury patients Okay, so this this project has not started yet At this point in my talk, I just want to take everybody and bring them to look at the big picture Okay, and I was thinking I'm going through my literature search as well as you know looking into this this project I say it's amazing that people are looking or labs are looking into ways to activate You know possibly intrinsic regenerative mechanisms inside the eye or even use a stem cell transplantation transplantation technique in order to Treat the the eye with with a certain retinal disease as well, but I thought to myself. What is the problem? What is a big problem? You know, what's the limitation using these two approaches and that's Something I identified as retinal remodeling, okay So retinal remodeling was first described by our very own dr. Robert E mark here at the University of Utah They found out was regardless of the type of retinal degeneration model after the after the photoreceptors die The rest of the retina goes through a global massive Rewiring of the retina so the question that I came up with was even if you replace the the lost photoreceptor Or any other cell type that you're interested in how do you know the rest of the retina is Still intact to be able to process vision the same way that you and I do So if I personally were to come up with a Translational approach to help treat blinding diseases affecting the retina. I take a two-step approach first thing I would do is focus my efforts on really Elucidating the mechanisms that govern the path of etiology or the mechanism that drives that specific disease because only once we halt that progression Should we focus our efforts on regeneration or using stem cell transplantation to help replace some of those Lost cells with the hopes of one day Allowing somebody with the affected retinal disease to be able to see this image in its entirety On that note, I like to thank dr. Bernstein for giving me the opportunity to present this topic and Thank you Last but not least our QI project that dr. Jorgensen and I are actually working on Is trying to develop an electronic sign-out program for our neuro ophthalmology patients at the VA because there's such a high turnover of residents there, so it's very important that You know the patients don't fall through the cracks and that we follow up appropriately on their studies So on that note. Thank you very much Dr. Bernstein A little bit about the role of immunosuppression That's definitely true. Okay, that's a very good question. Yes, you know as part of this phase two trial They want to use tachrylimus. Yeah, I believe it was starting at seven days prior to transplantation They have never Showing that there's any side effects right from in terms of inflammation inside of the eye after transplantation But just in case they've been they wanted to use immunosuppression Yeah, and it also includes I believe cortical steroids on the day of the surgery as well And then just one other comment, you know obviously there's a lot of interest from patients about stem cells and what they can do The problem of course is dealing with the hype and the misinformation that's out there And that comes not only from the internet and things out there But even the researchers there's a lot of things because this is Market-driven as you can tell you know this study was done by stem cells Inc And then they make a business decision and withdraw the study because they're going to go do something else but there's incentive to publish very quickly and to To go beyond you know what's just proof of principle and safety Which is what a phase one study is but it gets hyped up You know if you take the worst eye of someone it's likely it's going to get a little bit better regressed to the Mean and they'll make a big deal about that This this field is still really in its infancy and there's a lot of You know people going off to China and Cuba and other places that will take your money a lot of money and inject some stem cells Actually, even Florida will do this now because you can inject abdominal stem cells Directly into a person's eye and the FDA cannot stop you or cannot stop the doctor if it's all done in the same day At the same person's cells So there's a regulatory problems and it's really an issue So it's it's the Wild West out there and you have to tell you have to tell the patients That's what it is and yet and I would certainly never recommend doing anything except under an FDA approved trial in the United States It's going to be a problem otherwise It's not even limited to rat now one of our old colleagues is now we generate crystal lenses in China and so I had a patient yesterday asked me why actually should have an implant I've got a surgery why we can't regenerate his lens Because he looked it up online and a lot of hype now online Colleagues about regenerating lenses as well. We do it every day at the rabbits, but that doesn't mean it's controlled and something we can do and so You know patients are online all the time You know the injection of interatural stem cells into the eye has had disastrous In part of the problems is dr. Bernstein as he alluded to We're just scratching the surface in terms of understanding really even the ontology as well as the epigenetics that control development so if you ask me personally, I feel like this is a very Crew form of engineering. We're just shutting cells into a certain area and praying to God or whoever, you know, that's something happens Jim to my knowledge over two major companies in the U.S. So we're doing this one with stem cells in the center. We were going to be a study site for before they diverted their funds toward final cell projects is the other one companies still focusing on Issues or is it out of the question? They're actually currently undergoing phase one and two. I forgot the name of the company, but they're Yeah, I think they're actually using human embryonic derived stem Rp cells We've seen these patients who I had one a few months ago Last note was from a year ago 2060 at dry AMD and they disappeared and then he came back and he had a total Rd with horrible PBR The result was not pretty so they May ask, sorry, they usually will find a way All right, thank you very much guys You


Hello everyone, so Today, I'm gonna talk about I3C First a few words about me. So I'm working at Bootlid, which some of you knew as predictorans We had to change our name because of legal issues, but We're really the same team of engineers working in the same company. Nothing has changed except the name so A few things about me in the community and the maintainer of the of the MTD subsystem and I worked a lot on ARM SSC support, so developing drivers or supporting platforms and so on Yeah, what we are really interested here is That I submitted RFC for the I3C subsystem So let's see what this is exactly So for the new I2C, I2C means Inter-integrated secret Actually the new I Which is what we are looking after means improved. So if it's improved, it's obviously better and Yeah, I think I'm done Okay, you don't seem You don't seem to be convinced Luckily, I had a few backup slides So let's have a look at what I 3c is exactly So I square C and SPI have been there for quite a long time it's been created invented in the 80s and They were fine. I mean we are using them all every day but still there are a Bit limited. So let's have a look at what they provide. So they both are relatively simple to implement. They both require limiting the amount of pins to connect a few devices That I square C is really slow and SPI is not that slow. Actually, you can have devices which support I Don't remember, but it's around 250 megahertz clocks but the downside of SPI is that for each new device you want to connect on bus you have to add a new chip select pin So it's not that cheap in terms of the number of pins you need to connect devices on and spy bus Both need extra pins to signal interrupts They don't support a plug. They don't support automatic discovery of devices on the bus so On I square C you can at least know if there is something on the bus, but you can't define what? Have I ever let this address and On I square C bus You have the address collision problem So if you have two devices two different devices you want to connect on the same bus You have to make sure that they have different addresses. Otherwise, there is a collision and the transaction won't work So what if we could overcome this limitation with a new protocol? And this is what I3C is here for so I Couldn't decide it Me pee the fact that the I3C standards is pushed and developed by me pee was a good thing or the bad thing So I left it here I let you decide But the good things about the protocol of that it addresses most of the problems we had with I square C and spy First thing you still need only two pins like I square C But now the protocol Supports what they call in band interrupts, which means if you want to signal interrupts You don't need you don't need to add an extra pin per device to do that It's already everything goes through the bus directly It provides higher throughput It's still not what would achieve with a spy bus, but Obviously better than what you have with I square C It's better in term of power management than I square C. Oh, that's Not that easy to determine, but it's the calculation based the calculation done by the me my BPL ions Was based on the per bit basis So it might happen that if you have a nice QC device Connected on my square space C bus it Will probably consume less than if it was connected to a nice and I3C bus That's it. It's a good thing And it supports all plug natively You can discover devices on the bus which is Much easier to support than having to declare all devices to keep statically in your firmware It support dynamic address and assignment, which means the devices no longer have their address assigned statically and One important thing in my opinion is that you have backward compatibility with I square C Which means on the I3C bus you can connect your old I square C devices Or most of them will see a bit later. That is not always the case and I'm not sure about the last one, but I guess this is what the plan to do in the ice I3C group I think the the plan to standardize the device profiles pretty much like what you have with USB classes So you say that you have such kind of device and then there is a command interface to control this device And you don't have to implement a driver for each new device Created by a new vendor So the downside with I3C is that it will Likely be harder to implement in your hardware than I square C was or SPI was So let's have a look at the protocol in more details The first thing you have to keep in mind is that I3C has been developed with backward compatibility in mind Why simply because all the I square C devices won't go away And we want to be able to support them And to support them we have two solutions either we have two buses one for the I square C devices one for the I3C devices Or we make sure that I3C buses are back work compatible with I square C devices And that that's what they decided to do simply because you want you You don't want to add two more pins to expose devices But backward compatibility goes the other way you want to I mean If you are a nice 3C device vendor, you want your device to work Indifferently on an I square C bus on or an I3C bus and that's why you Will like the Backward compatibility with I square C So that's also supported in the protocol. So let's have a look at the physical near or now as I said, it's really Similar to the I square C protocol and we have two lines the clock line the data line The data line is most of the time in open drain Mod with a pull up You have the same a star 3P to start stop act next sequence So these kind of things didn't change Still we have a few few things that have changed and one of them is that we no longer use we no longer Drive the clock in open drain. So let's see why if you have an a clock running at say 400 kHz and You have a line driven with open drain with a pull up You'll have a signal which looks like like that and the same signal driven in push pull So you see that the open drain one takes a bit more time to rise and to go over the logical I level So that's fine because the clock period is large enough to be able to detect when the level goes I and when it goes low But net then takes the same signal and put it at 12 MHz and you'd see that with the open drain with a pull up approach your signal will actually never rise fast enough to Go over the I level Logical I level and that's a problem because we want to be able to transmit things faster on the bus so we have to move to push pull in order to increase the clock frequency But when doing that we break a bit of the backward compatibility For example devices which are doing clock stretching So clock stretching is about retaining the clock law so that the master can't send the next bit of data because the slave is Too slow to handle more data Then that's no longer supported with I should see Also SDA is still most of the time in open drain except when you want to do high speed transfers In this case for the very much reason you have to switch in push pull because you want your signal to raise To rise fast enough to to be able to detect the change And then the last thing that changes that they added new modes of transmission So you what they call either rate mods and then you have several submods So you can use either DDR which means you are transmitting things on both clocks on both edges of the clock or you can turn a bit turn a base mod where you Encode things using the two signals So each transition is in is encoded using SDA and SCL not only SDA So I said that we want to use push pull to be able to achieve higher throughput But that's not simple. I mean I square C has been designed to use open drain with a probe and There are several reasons for that The first one is that it's simpler to implement The second one is that It helps when several devices on the bus have to take control of the bus If you use an open drain with pull-up approach, that means that the default state is High level and when someone wants to drive the line low Then it drives the line low bet if two devices There there is never two devices which drive one devices drive the line low and the other one Divide the other one drive the line high which would then be a problem So We still have to support those devices which want to To use open drain sometime So for us the clock line that means that of course we can do clock stretching and also we can't have multi-buster so That means that For the SDA line There are some phases where You'll want the slave device to control the data line Which means in this case you have to switch from push-pull to open drain and actually the I3C master controller is doing that Dynamically so depending on where it is in this state machine It will decide to drive the line in push-pull or switch to open drain to let the slave device control the line That's all you can make sure I squished devices still work fine on I3C basis So what about performances When you run the clock at 12 megahertz You are about You are at about 1.4 megabyte per second But then you have another problem. I mean I squished devices have not been Developed to support such high-speed clock. They usually run or some of them might support that but at least it's not always the case So we have to make sure that Devices on the I3C devices on the bus still work correctly The first solution is to slow down everything. So slow the clock down Or we can find a solution to make the I squished devices think that the clock signal stays low and that's what the I3C I3C protocol is doing so instead of having a symmetric clock signal Where the low period is equal to the high period you have? clock signal which is a symmetric with the High period which is below 15 nanosecond and the high period which the low period which can be extended and Because some devices embed Spike filters so they detect that the signal was not maintained more than 50 nanosecond Then what they see on the bus is just a low level and nothing more And thanks to that You can achieve better performance than if you drive the wall clock signal at the lower rates So of course you're not you're not achieving the full performance because you're not running the clock at 12.5 megahertz, but it's still better than Slowing the wall bus at the slowest device rate So let's sum up a nice 3C bus can be in three different Configuration you can have the pure bus Configuration which in which case you only have I3C devices connected on it the clock signal runs at 12.5 megahertz you can support all high data rate modes and Of course, this is what you'll want to use But sometimes you have to put I2C devices on the bus and in this case you have two sub cases the fast bus mode mixed fast bus mode, which means all the devices on all the I2C devices on the bus contains and Spike filter and then you can use the trick we've just seen or Some of the devices on the bus don't contain the spike filter and in this case you have to run the clock at the lowest rates Supported by the I2C devices So obviously the last case is you don't want to end up in this case because in this case I3C is pretty much useless So let's switch to addressing scheme We've seen the physical layer now. How can we address devices in I3C? well, it's all It's also pretty similar to I2C. You have seven bit addresses Devices are expected to hack or knock the transaction and Still there are a few differences. The first one is that Devices are no longer statically assigned their addresses. So the master decide Which address will be assigned to the device and then that means you don't have any collision That's that's a good thing. The second thing is that there is a broadcast broadcast address And with this broadcast address, we will be able to address all the devices on the bus at the same time So that's also a new thing And of course this address has been picked in the reserve range of the I2C protocol So that you're sure that no I2C device should have this exact address So let's sum up what we've found about I2C backward compatibility Obviously the fire and Mac layer have been designed to be backward compatible with I2C But still that's not enough For example, you won't be able to connect slaves Which are doing clock stretching because that's completely forbidden in I3C If you have I2C devices, you might be able to connect them to the bus But remember that if you if they don't have spike filters, then the performance will be really low and obviously, you don't you don't want that and Also, you have to remember that some of the IDAT rate modes are not usable when Some devices some I2C devices are present on the bus So it's backward compatible but still has some drawbacks So we've seen the addressing and physical layer now let's see The functional differences between I3C and I2C which is what most developers software developers are interested in So what are the I2C and I3C physical and addressing layer were pretty similar From a functional point of view I2C and I3C are really different for example As I said several times Addresses are not statically assigned, but now they are dynamically assigned by the master But one of the most interesting point here is that all devices on the bus can be discovered and you'll no longer Have to describe them statically in your device tree or or a new bot file or or whatever Also devices are self-descriptive that means that when you discover something on the bus you will know exactly which device this is and You will be able to easily attach the device to a specific driver and Linux Some masters and slaves can support outplug so that's not mandatory, but I guess most of them will support that and of course because of the Functional differences that means that this management is likely to be more Complicated than with I2C. So we'll see a bit later how to control the bus how to assign addresses But of course, it's it's a bit more complicated in the than what you have with I2C And the last thing is that you have different transactions so the first type of transaction will look at is the CCC transaction which is meaning common common codes so these are all the Stand our comments. We will use to manage the bus So thanks to that you will be able to discover all devices on the bus You will be able to query information about the device each device And you will be able to keep the bus in a consistent state And they also plan to use those generic commands to do generic operation That means operation which are not tied to a specific kind of device Let's have a look at what this kind of frame looks like. You will have an 8-bit opcode the most significant bit in this opcode will encode the whether this is broadcast or unicast command and The seven bits will Encode the actual action that will be sent to the device You can have a payroll attached to a command CCC So the payroll in case this is the unicast command the first byte of the payroll will contain the device address and Then after that you have Real data that are passed to the command So just a few examples of commands that you will be able to send the first one is Start the DAA also DAA is for stands for a dynamic address assignment. And this is basically the auto discovery procedure You have enter activity state X So X is just a number and this is about and Managing for a management so asking a device to enter a lower state for example Then you have all Comments which are used to retrieve information about the device so get PID Get VCR get DCR. So PID is the unique Identifier of the device a boost characteristic is about what the device supports in terms of transfer types and at which speed and Then the device characteristic is about Classifying the devices So let's have a look at one of these comments Which is in my opinion the most important one and this is the one you will use when you Initialize the best to discover everything that is connecting other than the best. So this command is called MdAA for enter DAA which stands for dynamic address assignment And To do that the master will actually send a command and then emit emit directly after that repeated start and Then after after each repeated start all devices all I3C devices on the bus will emit the their PID VCR and DCR Information While they do that while all slaves do that they have to monitor the state of the SDA line and Every time the state of the SDA line is not what they Intend to emit that means they lost the arbitration and that means they have to stop emitting things on the bus and The last device that is remaining emitting something on the bus That means it wins the arbitration and the master will then Assign it an address. So if we Just look at Standard and the a procedure the master starts emitting and the a which Forces all devices on the bus to enter a specific state then it emits a repeated start We have two devices on this bus they both emit their PID DCR and VCR at the same time except that only slave one wins arbitration Then slave two are has to be has to stay silent until the next repeated start the I3C master assign an address to slave one Which is now able to communicate on the bus and then emit a new repeated start then same thing with slave two Which now is able to receive a new address and you add up with a repeated start Which is followed by no one hacking the transaction, which means the discovery procedure is done and the bus is Operational so that's it. So let's have a look at those information which are transmitted during DAA the PID is what we will use when trying to Determine which driver which will be connected to the device When the PID you will find the manufacturer ID the part ID An instance ID in case you want to put several devices of the same type on the same bus So usually this instance ID is controlled with external switches or directly using the pins of the of the device And you have extreme permission which I actually don't know what they are Used for but this is something that vendors can put specific data in to differentiate the devices You also have BCR, which is incurring what the devices capable of So is the devices is the device capable of sending interrupts is a device capable of supporting ID rate modes What is the maximum? transfer speed and and so on And the last thing is that is the DCR, which is encoding the device type. So Ideas here are supposed to be standardized by the MIPI Alliance and they are But yet I don't see what they're meaningful for because there is still no Common interface for each type which means you know what kind of device this is but you don't know how to interact with it You don't know what to query information and so on So right now, it's just Informational and you can't use that to to implement a generic driver, which is able to handle all kind of devices of this Another kind of transaction is as You are transfers or private transfers So there are meant to replace ice-query C transfers Except that this time they are using the full speed mode so clock running at hopefully 1212 megahertz And there is no standard to say which kind of information or send to the device So it's completely free and devices are able to implement what they want and and all they like So it's basically what we see with ice-query C already Then we have HDR transfers which are used to Achieve even higher data rates So we have three different modes The DDR mode is obviously one where you will transmit data on both edges of the clock And then you have determined turn any modes which are used to encode data using the two The clock and the data signals But it's a bit complicated to see how to encode data with both SEL and SDA, but that that works and You have two of them actually because depending on whether they are ice-query C devices on the bus or not You may have to ensure that the low the high period is lower than 15 nanoseconds because of the spike filtering and all the stuff we've seen before The data you transmit using HDR Transfers are a bit more standardized than the SDR SDR transfers So you have to first emit a 16-bit word which contains a command code and then again There is a range with their for generic command code So hopefully it was we should see soon some generic commands which will be used by the ice-query C specification and some vendor specific commands, which will be useful for vendor specific drivers Last thing we want to talk about here is invent interrupts So how to avoid having to add a new a new signal to signal interrupts So what does that work? Basically all devices on the bus all ice-query C devices on the bus are able to Take control of the bus temporarily to just send the IBI and The master which is in control of the bus Well, either act or knack the IBI, but once he has knack the ABI the IBI This will have to Retrieve the payload and to determine which device wins when an IBI is generated generated There is the address arbitration Which means the lowest the lower the device address the higher the priority so that means You have to carefully choose the dynamic address assigned to each device because this encodes the priority of the Interim generation on the bus odd join it's Basically what we call odd plug for other protocols It's pretty much the same as IBI when a device is connected on the bus and it will it has It still has no dynamic address It's able to send an interrupt saying that it wants to Join the bus and then the master will be able to act or knack this request And if the master and acts the request then they asked you assign a dynamic address And as we've seen before assigning a dynamic address is about entering DAA. So Yeah, that's all a joint work and the last thing we'll see here is multimaster capabilities so I3C is supporting multimaster natively That means that you'll be able to have so masters on the same bus Unlike What we had with I2C where all masters were able to take control of the bus at the same time It's a negotiation between the masters to know to know which one of them is controlling the bus So you have two type of I3C masters the main master which is responsible for initializing the bus and the secondary master which is Acting as slave at first and then when it needs to emit Frame on the bus then it will have to negotiate with the current master to gain ownership of the bus So that's a bit more complicated than what we had with I2C And of course bus on F ship can be requested by an inactive master which wants to take control of the bus Or it can also be requested by the active master when he wants to Go sleep for example, and he wants someone else to end all the bus. That's that's a two-way thing So these are just Introduction these are just a piece of him information about I3C and obviously I omitted a lot of things So if you want to know more you can go check the I3C specification which is for once Open but that's not usual for me P stuff, but that's a good thing actually And yeah You can go check it So let's see how we plan to support that in Linux. So that's basically what has been proposed in in the RFC So if you go back a bit, you remember that I3C is a bit tricky to categorize because It's back one compatible with I2C device still it's a lot different functionally from And link I3C devices is a lot different from handling I2C device So we have to keep the existing I2C ecosystem working without changing anything But we want to add support for new I3C function like this And to do that we add two options. The first one is extending the I2C framework to add I3C features the second one is to Add a new framework and then connect it to the I2C framework. So we went for option two And that's basically what we have So on the bottom of the diagram you see the hardware stuff And you see two buses one I3C bus one I2C bus Those buses are exposed to Linux through their controller which are then connected to the I2C or I3C framework and if you if you go look at the devices which are connected on both bus You'll see that they are Then connected to their appropriate driver. So if you go look at the yellow device The I3C device in yellow You'll see that it's directly connected to the driver that was registered to the I3C framework You can also have I2C devices connected to the I3C bus So this is the purple one and in this case it will be connected to the I2C framework Going through the I3C framework. So we are basically using the same infrastructure Which means if you add an I2C driver It will work the same way it used to work even if the device is connected on an I3C bus That's that's supported Now we have More complicated case cases. For example, we said that some devices are Compatible with both I2C and I3C and in this case You want the device to be discovered when it's connected on the I2C bus and you want it to be Discovered when it's connected on an I3C bus and you want the same device to be connected to Those the bus device both devices to be connected to the same driver. So you had to add a way to register single driver to both framework and that's what we did. We have a new macro which has evolved to Register a device a driver in both subsystems so that you have a single driver Which has evolved to handle the device which is operating in I2C mode and the same device Which is operating in I3C mode. So a few more words about the design choices First thing is that we separated the API for device driver and master controller drivers that's mainly to ease Implementation of both kind of drivers So people don't have to guess How is this an API for the controller part or is this an API for the device driver part? Everything is separated in two places in two different places. So that's that's good One other important thing is that Even though we have a single bus, which is the I3C bus When you look in CcFS you'll see Two buses represented the I2C one and the I3C one and this is Mainly because we didn't want to break the I2C Ecosystem so we have to keep everything working as before But still those buses are the same thing and they are usually connected through the parenting of So the bus is declared By a specific controller and when you look at the controller, you will be able to connect the I2C bus to the I3C bus And then how do we bind devices to specific drivers We are basically using the DCR and PID values so PID is encoding the manufacturer and Part ID and DCR is encoding the class of the device So we use that to connect a specific device to a driver and the last thing that is to That is important to note is that IBIs are not exposed as regular IAQs simply because most of the time They do not look like regular IAQs. You have payloads which are added to the interrupt and You also want to send messages on the bus after that and we'll see that it's not really possible in an atomic context So we decided to just simplify things and and treat them as not regular IAQs So let's have a look at the device driver API first It's exposed in Linux I3C device.h and you'll be able to declare a driver register it You'll be able to send SDR-HDR transfers and you'll be able you'll you're not be able you're not able to To send CC commands yet because as I said, it's mainly here to manage the bus And I don't think it's needed for device drivers But if it appears it appears to be needed at some point and we will probably change that And you will of course be able to register IBI on LERS and activate the IBIs So let's have a look at the device driver declaration That's pretty much the same thing you have for any kind of driver. You have a pro function and remove function a table of device ID which are used to bind devices to drivers and That's all then you call you declare your driver structure And you call module I3C driver and it registers the driver to the I3C framework So nothing new here The same thing goes for the SDR transfers. So It's pretty simple It looks like the things you've you've been using with I3C So you declare a table of transfers whether these are reads or writes and Then you send the transfers to the device And pretty much the same for HDR transfers except that now you'll have to specify a specific Upcode and the mod you want to send The one the mod you want to use to send this transfer Nothing really complicated IBI is a bit more complicated So you'll have to first declare an IBI handler and This IBI handler is called from a non-atomic context. So you can Send a new message in this IBI handler and when you request an IBI an IBI you will have to specify the max payload size So normally this is defined in the data sheet of the device And then you have to define the maximum number of slots allocated to this IBI This is mainly useful because since you you're not only that in interrupt in Atomic context and the interrupt context That means that you may have several IBIs queued In the device before the device before the walk you actually call the IBI handler So if you're not using If you're not reserving enough slots you might lose some IBI Maybe that's not such a good idea to do that But that's what we come we came up with to to address the problem and Then once you have requested the IBI is that means all resources needed for these IBI have been allocated You can enable the IBI and in your removal layer you can disable the IBI and free the IBI resources Now the master controller API so it's The interface which you're supposed to implement when you want to support to to declare a new master is Not that big and it leaves a lot of freedom to the controller driver and I did that because actually the I only worked on one of them and I'm not sure exactly where Which part are really common to everyone and which parts are specific to the one I worked on So instead of adding a lot of logic in the in the core right now I decided to put a lot of logic in in the controller driver Basically what the controller drivers will have to do is initialize the bus and initializing the bus is quite vague So It will have to declare all the devices which are statically defined. That means all I square C devices You also have some I 3c devices which can be statically defined So again, you will have to declare them in the controller and then once this is done You will start a DAA to discover all the devices on the bus And you will then declare all the devices you've discovered on the bus to the framework So that's basically what you'll have to do when you initial is initializing the bus Then you will also have to provide some methods to send all kind of transfers So you have one for private transfers HDR comments and CCC comments and also one for I square C transfers For CCC command you can you have a support CCC command which which is Used to check that the CCC command is supported because not all CCC commands are mandatory So your controller may support or are not a specific command and the important thing is here is that all Those hooks are working in a synchronous manner. That means when you call this function you and this function returns that means that the the transaction on the bus is done and You don't have to wait for a call back to be called or or things like that. Everything is synchronous IBI's So pretty much the same function you add in the API in device driver API except that here you have to implement them So request API IBI fee IBI enable IBI disable IBI. So that's pretty obvious There is one more which is here to recycle a slot that was used to store a payload of an ABI and Yes, again, one of the important designs choice we made was to Execute IBI alerts in non atomic context so in the work you can text and Because the other Transfers are done in a synchronous manner. That means that from the IBI and learn you are able to send a new something new on the bus Still if you can't avoid it You should avoid it because there is one more if you pair controller That means that if you send something on the bus you block every other IBI and learn So maybe we'll have to rework that a bit to to make it a bit scalable a bit more scalable And yeah, the IBI slot have been allocated ahead of time That means that if the IBI device driver is not dequeuing the IBI fast enough it will lose some of the IBI's Adjoin again not a lot of facility in the framework because I'm not sure how other controllers will handle that so It's basically an interrupt to you will receive from the controller And you will have to when you receive that you will have to trigger a new DAA so Really nothing else we can expose here So that's basically all we've done The status is that we have submitted two versions of the RFC Everything that I just described in the slides have been tested and implemented The only problem right now or the the problem we had before was that we didn't have any real device So we were using a dummy slave device, which we were more or less controlling that then that that was a problem and The next version should have a real device driver for a GPIO expander, so should be able to use All of the API I've been exposing in the device.h file That's it Not much time for questions Let's let's go. Okay. So the question is what if we all and it what if we have in an identical parts connected on the same bus, right? Yeah, so there is an instance ID here Well, there is an instance ID. So so you can By controlling some some of the pins of the device we can assign a specific instance ID Which will provide a different PID which then means that you will be assigned a different address Dynamic address. So that that works that support it. Yeah So it will likely have to be configured a bit differently in our rare Whether it's with switches or by connecting pins to different levels So how much sure is the hot plug support because that looks very handy for making smart peripherals? How much sorry how much sure is a heart plug hot plug support? How much sure is that like is there other devices I can get out there for example and embedded I think the The specification does not Say anything about how to plug devices physically on the bus that's not defined at all now for the So how to generate an interrupt you signal and odd join event. This is really I think it's it's mature enough But how would you actually plug a device and not disturb all those devices on the bus is not Deal to is and in the spec unfortunately So about that So the MIPI group is defining the spec right it is totally free of licensing and stuff like that Okay, so then my question comes who is Assigning and defending VIDs and PIDs because like that's part of the reason you pay in the USB Is so that those are defined and no one else clobbers over your Actually, I don't have the answer, but I guess this is MIPI will we will assign Manufacturer IDs at least okay, and then so finally on that about the hot plug question So that's not to find what triggers that at all so Like in the case of an I squared C you have it's very common to have I squared C muxes And so I'm wondering like in a mux case. How do you say okay? I've switched to the other branch of the mux I need to go hot plug these new devices in again. It's not specified in the specification. So so it's up to the device manufacturer to decide how to Trigger the odd joint event. Yeah How this compares to USB because I'm thinking about you know to data lines you have Hotplug you have device recognition. It's much slower than USB for for sure and it's also It has better energy efficiency than USB it's ready for small embedded devices And it's it's about energy saving. So it's Couldn't be replaced by It's just a sort of a follow-up on that are you expecting sort of a common device driver for peripherals to start coming out I mean it seems like right now with this concept drivers You're gonna need redundant drivers being implemented for all peripherals to maintain backwards compatibility and some of that could be alleviated if there are Common drivers, I mean like CDC that you find yeah Actually until they define a common interface for a specific kind of device It's not possible. So So we need to wait for them to standardize things And I can't tell if it will even happen. It's it's not yet decided. I think So another hot plug question one of the things that's caused a lot of hassle for Some of the other mippy buses with their hot plug support is what happens if you Have a device you want to put into very low power mode by physically removing its power It then rematerializes on the bus re-numerates yeah, and the The bus core has then got a workout that actually this was this is a device already know about yeah It's not supported yet at least in not in the v2 of the RFC, but I'm working on that So I'm working on trying to figure out. Oh, this is a new device. Okay. I assigned a new address But actually a new device So I shouldn't create a new one a newest instance in Linux and I should instead update the address instead of creating a new device So that's things. I'm I'm working on Hopefully it should be supported Correctly thanks Yeah, so the question is when do I expect to see actual devices I really don't know Okay, thanks. Thanks a lot


What's up guys Rooks34 back with another episode of Legacy Week. This is episode two the first week You guys saw Metal Raiders make sure you check that one out if you didn't see it there We go around the camera It was pretty insane 24 packs of metal raiders now we're opening 24 packs of pharaoh's servant Obviously our goal is that guy the Jinzo that would be pretty crazy Also, don't forget to hit the TCG player and you bet fill it link below if you're buying anything on TCG player or eBay it really supports my channel I appreciate all you guys that do it and let's show the giveaway the giveaway limited removal ceasefire and Imperial order all these are pharaoh's servant original Unlimited cards all you have to do to enter this giveaway is like the video be subscribed and let me know what you want to see from pharaoh's servant Probably gonna be Jinzo, but there's a lot of other cards. I've never pulled a buster blader. I pulled 1000 as a strict But it was first edition. Oh, no, I see I pull unlimited. I pulled two of those I've never pulled buster blader though. So that's kind of the goal. There's also legendary fisherman I don't think I've pulled that that would be pretty cool. There's a lot of cool stuff Let's hop into it guys and let's see what we can do Here we go. I'm pretty excited. I love pharaoh's servant. It's just I've had a lot of luck with it in my day So it kind of helps I've pulled two first edition Jinzo's obviously so that's pretty cool. Shout out of eyes Harvey's brother tagging receipt You can't make this up first pack Jinzo's secret rare. I'll look at the full two Jinzo's. Come on. Let's do it Jinzo in the first pack guys Oh my goodness That is incredible. We had incredible luck with secret rears in the first opening Now we got a Jinzo in the second opening legacy week is going well hit the like button if you're enjoying legacy week Also, if you have any other ideas like legacy week that you would like to see I think legacy week's gonna be pretty awesome We got a magic drain. That's a cool card for goat actually pretty good card actually because Nice thing about this card. Yeah, I've been playing goats. So I actually kind of have played some yugioh It's kind of crazy. Good thing about this card. You activate it and they have to discard a spell card to negate So even if they do negate it costs them a spell card. So it's pretty cool All this cost you is one card. They lose at least one card. So it's pretty cool Pretty nice card to force them into you know discarding or losing their card if they don't have a spell card They're just done. So it can be pretty good. All right. I do like that card. All right first pack Jinzo That is pretty incredible. We've gone at vermin the regulates to try. We've got a science soldier Prohibition. This is actually a really nice rare. It's actually worth a couple bucks It's like barrier and dc warrior. Wow. I mean, I think it's like insane. Okay. Let's read it. Honestly I don't even know what it does Clearly the name one card is oh, I do know this card. It can't be played That's actually super good.  Boom never playing it. So you don't want to see Jinzo activate prohibition. No Jinzos Cyber Falcon and skull invitation.  There's just some really sweet looking vanilla's in here Yeah, and also I think island turtle is a short print but only in The original because the original cards had short prints the 2017 reprints do not so yeah Oh, yeah, I forgot to say that this was considered, you know fair sort of booster box You know 24 packs or whatever. I have truth. So so far.  You need to pull one Jinzo and you're happy Wow, I can't be first pack guys our secret rare luck has been awesome DNA surgery. It's a nice card You know, let's put that there cold wave Jochen kuagata earth shaker Hayabusa night these usually start slow and end fast for me And well and strongly how about that? But this one is starting off hot. Well, it started off hot now. It's kind of going back to the regular ways Invitation to a dark sleep Jinzo one of the best cards So have we not wait How we pull Jinzo? No, I'd already pulled a reprint Jinzo man. I pull like five Jinzos now It's crazy respect playing Prohibition double prohibition. That's actually really good That reminds me of when we opened that pharaoh servant original box and pulled that red Tape pack and then all those people on that misprint grouper And that facebook group are like, why would you open that pack?  And I was like, I don't know. I didn't know what it was Arby's brother time seal Bombardment beetle that's a short print as well magic drain again. We're getting a lot of the same rare as in school It's all in wishes. Let me know if I'm if there's any nice comments that I'm missing That are like pricey because of some meta thing or something Okay, go to incuagata so far one foil only but a Jinzo earth shaker Souls of the forgotten world suppression Morphing jar number two. That's actually a pretty cool card burning land flying kama kiri and type zero magic crusher One foil, but it was the best foil. So I'm really hoping for bluster blader. That's what I want I've never pulled one. It is really awesome. By the way. Oh, yeah, I don't think I mentioned my hand got scratched in basketball Sorry about that. It looks a little weird DNA surgery cold way noblemen of extermination cool twin-edit fire dragon one of the best comments and inspection And then yeah my my thumb here. I hit on something. So yeah I'm just beating myself up constantly. It's kind of ridiculous. It's kind of ridiculous. All right bite shoes DNA surgery I don't think I mentioned that in the lot yesterday's video. So I guarantee I'm gonna get a question about what happened Oh feed mega cyber Sweet ultra rare I do love this guy. I did Grade one of these in ps8 10. I sold it to gezi for his complete LOB through ASC first edition ps8 10 set. He's down to one card. He only needs enemy controller So you guys have a mint enemy controller He's definitely looking for one I'm pretty sure there's only a couple of them in 10. So I doubt that anybody Has one that's selling but possible Okay Here we go time seal. So ultra rare and secret rare nice. We didn't get an ultra rare metal raiders. Which is super weird Um, so it's nice to get one here light force sword doku royaiba insight barrier All right final pack of this side just two foils, but two good ones So that's that's good. We got time to catch up. Anyway, second half usually is hot shadow of ice insect imitation DNA surgery Sword hunter monster recovery. I thought said reincarnation. I was like, that's not the same card That is in rise of destiny. Okay second half of this booster box First half was insane jinzo from pharaoh's servant guys like Me pulling a jinzo was like the same thing as somebody battling me and getting the best card. It's like guaranteed Hall of the haunted one of the best cards. I always think of it as bones voice I play hall of the haunted. He says it in such a weird way But oh, that's a nice goat card as well used quite a bit Nice ultra rare appropriate. Um, no appropriate is rare, but I'm saying nice ultra rare Well, they call the hunter there you go.  That's all I gotta say Yeah, okay, I probably played that sound anyway. All right. That was that was bad I gotta calm down ceasefire ultra rare. That was sweet. We got a shift drill bug and major riot Now we're now we're killing it. We got four foils now three ultras in a secret. Okay I like those odds All right, let's see what else we can get infinite dismissal respect play mr. Volcano flame champion and skull invitation cool card Kissing tie that card is annoying all right No supers yet If we do get a super we want it to be nobleman of cross out for sure It's like you use one of those for a hollow version of the goat well expression Dust tornado. It's not a bad super the sintering. Wow interesting Sinnering is terrible. Okay Another nice goat card dust tornado. Oh my goodness. What is in here? Some of these cards have stuff all over them. Okay super rare our first one yet Twin edit firing inspection We have five foils. So we're pulling even better than yesterday. It looks like It's debatable. Let me know what you guys think who which one pulled better in the comments shadow buys. Oh, we definitely got some very Very meteor crush that was like super dark. You could tell that was a foil Very meteor crush super rare. The foils are flowing right now Burning land doku royaiba. I gotta love that card Six foils. I mean that's the ratio for 24 packs basically six to seven So we're doing good Souls of the forgotten driving snow Hayabusa night Dark fire soldier splatbot and armor glass Wow, this is going uh, this is going good. We got two prohibitions as well, which is a strong rare So we're pulling fire bubonic vermin invitation to dark sleep. Oh whoops. We skipped harvey's brother and red moon baby That's why I do it the other way. No, I remember Okay, we got five packs left. It looks like Can we pull another ginzo? Yeah, I'm asking a little bit too much. I know these legacy packs are good, but probably not that good Gradiest we got some on there by choose. What is that? Dark fire soldier number one magic drain again. That's a play set. I'll take that. I mean I usually don't use any rare. So it's a nice rare that I might use. I'll take it Harvey's brother time seal bombardment beetle I open an entire box and then get that card minor goblin official Dimension hole the first card I pulled out of the first edition for a server pack I've told about a million times. So you guys probably know that already All right, we're cooling down after that super hot street But let's see what we can do the regulation of the tribe souls of the forgotten DNA surgery earth shaker Mad sword beast. He's mad. That was nice item Solid wishes. All right, two more packs guys Two more packs. We want to get that old or that secret rare ginzo Let me know if you guys are enjoying legacy week. Also, we're probably premiering this So I hope that is fun down there in chat. What a premiere is is There's a live chat on a recorded video every time I do a premiere somebody thinks it's alive When they ask if it's live or whatever. It's not it's just a recorded video. So Here we go. Gradius cold wave Eye of truth the all-seeing white tiger of mitch's zuri three at a guido solemn wishes burning land and reign of mercy okay Final pharaoh servant pack guys. Here we go our last chance to pull buster blader or another ginzo Here we go Final chance hit the like button for luck Appreciate you guys watching. Let's see what we can do metal detector invitation to a dark sleep world suppression and Nobleman of cross out sweet the super are wanted. That's a really nice one. Okay. So we pulled absolutely awesome in that in this video Not that video. It's still going but okay Let's go over what we got. That was pretty great. I'm pretty hyped about that All right from these 24 packs booster box of pharaoh servant. We have magic drain Play sets. That's pretty cool. We got double prohibition the best rare in the set. I believe we got nobleman of cross out I think that's the best super in the set.  That's a good one the fiend mega cyber and bam The man himself Ginzo Pulled him like five or six times now overall. That's pretty awesome Every time it's just as exciting. So I love it Hope you guys enjoyed the video make sure you guys like the video and subscribe share it if you could help support The channel and also we're approaching 20,000 subscribers for that 20k opening We're going to open first edition lob. We're going to open retro pack one retro pack two champion back one all that craziness So that's what we're doing a legacy week for to lead it up into 20k Then we're going to have that video or maybe in the middle of legacy week if we hit there first So thank you guys for watching. I'll see you guys later peace Dark bright Boom


What's up internet? Welcome to 2023 and we're currently seeing the cheapest prices we've ever seen para sa 1650 and to 3050. Pero... Pero hindi galingin sa amin. This is price watch where we track the GPU and CPU prices of the four largest PC retailers in the country. Tapos once a month, we report about it. Pina-process na rin namin yung data para mas madaling sundan. And all of that can be seen dito sa Google Sheet natin below. Price watch only comes out once a month. Pero yung Google Sheet, once a week, in a update yan. Pwede niyo ma monitor din yung prices kahit walang YouTube episode. We follow the data so it's easier to follow. Blue means it's a good price change, meaning bumaba yung price from last week. Red is the opposite. Tumas yung price from last week. And there's a separate tab dun sa Google Sheet. If you look dun sa lower left, we've also tabulated the prices per week. Kita mo talaga from the start, week one up to the current week 11. Yung ups and downs nung iba-ibang prices. And lastly, bad words yung mga d***s, d***s, d***s, d***s, d***s. Yung mga iba-ibang names nung PC stores dito sa atin. Of course, only Hard Retro Gargets, Free Publicity on the Channel. So, yung apat na stores na yun, tinago namin under ALSS. So, kung nagtataka ka, bakit Wedge, Roy, etc. yung mga tao ko sa stores na yun? Because I don't want to say their names out loud. But I do want to say the name of our sponsor out loud, CDT. And yun, di mo kailang track yung prices kasi always good prices yung mga keys nila. Pusnay di kailang na windows. Pero saan ko hukuan ng legit windows? Daming options, daming prices. Aka nito. Good di na lang. May cdkeyovers.co. Wadalilang ng order. Search for the software you need. Add to cart. Daan ka sa payment options nila. Wala apang 5 minutes finished. May legit? Working CDK na para sa windows mo. Gamitan lang awing kod para makakuhapan ng discounts. Kaya kung nagahalap ka ng legit, mura at original software. Check out CDKovers.co. Alright, so the latest week we have data for is Jan 3 and ito yung sinasabi namin at the lowest prices of 1650 and 3050 we found ever. Ito si Roy, 8,820 lang yung 1650 niya which is Galax. From 9,450 naging 8,820 nalang which is around the 600 pesos difference quite a lot. Tapos yung pinakamura na 3050 also from Roy was around 18,400. Ngayon 15,750 nalang siya. So that's like a 3,000 pesos difference. Laki nung difference for the 1650 and 3050. Yes, the other shops do have stock of both of those cards but nothing approaching the price of what Roy has. At ito yung si Roy, it's very interesting na madalas na wala siyang maraming models but when it does have available models, usually mura siya. Although even with the 1650, there is some price competition. Si Wash may 1650 na 8,995 lang, like 100 pesos difference roughly. And to be fair to Wash, yun din yung price niya last week. So a good downward movement for the 1650 and the 3050. Everybody else pretty much unchanged. And I think this is a function of the Christmas break. So may jap mo ba yung prices going towards Christmas, we saw that in GPUs particularly yung mga Nvidia cards and the 5,000 series of AMD. Talagang balita naman talaga na dapat babagsaki ma-precio nila kasi yung strategy na yung AMD was to try to exhaust inventory. Ubusin na natin yung 5,000 series because we want to move on and start selling the 7,000. Yung problema siya dumagaling yung 5,000 series, inisip na ma-contrumers. But pa ko bibilin yung 7,000 na mas mahal, mas magandangay ang performance but you know, not a lot, a lot. Compared to the 5,000 series na very nicely priced. So AMD slash prices some more just to exhaust the inventory of the 5,000 series. And moving forward, we do expect more sales of the 7,000 just because it might be harder to find the 5,000 series. But most of the discounts na input na prior to Christmas. Seeing week before Christmas, December 14, you notice andaming blue. Blue indicates na bumaba yung price compared to last week. So all across the board for December 14, each shop had at least one card na bumaba yung price. And then medyo ganun din sa CPU side, these guys. Although only two shops had price drops for AMD CPUs. But if we go back all the way to December 5 where there were even some price increases. Bag the things at December 14 closer to Christmas, the only price increase was a 4080. Then jumping to Christmas Day, still strong performance na maraming bumaba na prices. Tumas lang kontin yung 4090. And that trend continues up to the present day itong Jan 3. So the 4090 went up a little December 25 but itong Jan 3, it's back to its normal price. On the AMD side of things, not much movement. There was a slight price decrease of around 2,000. 1,000 or so pesos for a 6700 XT. Although there is a cheaper 6700 XT na ASUS pa, itong CMSI is around the 27,000 mark. Wash has an AMD ASUS 6700 XT for only around 23,000. And he's had that price for a while. Ever since... Actually tumas pang, ever since December 14, yun na yung price niya. So quite a lot of movement, especially in the days leading up to Christmas or the holiday season. For GPUs, bumaba talaga siya. Right after Christmas, first week of January, medyo steady pa rin yung prices except for these two, 1650 and 3050 from ROY which are really good prices. AMD GPUs yun na. Wala machado movement. On the CPU side of things for January 3, cheaper R53600 from ROY, cheaper R53600G and R5... Si Joker yung R53600 niya, bumaba na nga slightly below 10,000. But ROY has it for much less. It's around 7,5K ROY. And the other two shops don't have it. So it's interesting that out of four shops, dalawa meron, pero unlayo ng prices. One is on a very high end. You're almost paying 40% more if you buy it from Joker as compared to ROY. So hindi mo talaga masabi, kung habol mo talaga yung lowest price without any other considerations like customer service, ease of doing business, and responsiveness of the shop, kung habol mo lang talaga yung price, it really pays to compare kasi mangyari talaga yung different shops will have wildly different prices for the same product. Let's move on to the weekly summary. So we're here at week 11. We've been tracking prices for 11 weeks almost three months. 1650, very slight price change compared to last week. Significant drop in the 3050, almost a 1000 peso drop, and that's likely from the effect of the GPU of ROY, na ang baba na priceon niya. 3060, very minimal price drop. Price increase actually into 3080, and I have been mentioning to customers na it's kind of been harder to find the 3080. Also very hard to find the 3070 Ti actually. So there are some indications na yung 30 series, it's becoming hard to find them. But over the break, somebody was telling me they were able to get a 3080 for around 38,000 pesos. That was a very good price regardless ko anong brand yung GPU na yung 38K for a 3080, pretty good price. We didn't see it from the four major stores that we tracked. Price increase also for the 4080 around 5000 pesos. So a significant price increase for a 4080. The average price of a 4080 is over 91,000 pesos, but ours at hardware sugar is a gigabyte at 90,000 pesos. And we've had customers tell us na na that it's quite cheap even compared to their own research. So at least in this instance very clear that we are below the average price. We're selling a card for below average price. 4090 average price is around 111,000 which is 2,000 pesos less than the average last week. Although medyo nags-pike talaga yung 4090 it's been around 114,000. So itong 111,000 is a good price relative to the past weeks that we've been tracking it. And for AMD, not much change really. 6500 XT 13145. Very small price difference with the 6700 XT around the 500 pesos drop compared to last week. This week of course marks the availability of the 7000 series. So yung 7900 XT X and n7900 XT will we be tracking them? Perhaps will we be stocking in them in the shop currently only upon request? So we can't get them if you want them. What we going to CPUs? No change for the 7950X no change for the 7600X Very small price increase for the 5600X 5600G the prices actually of this have been dropping quite a lot. Yung nga, let's say if yung oktober to 94 siyang, yung nga 88 nalang siya that's almost 10 percent. Also a price drop for the 3600 series. Moving on to the Intel side of things no change really. Very minimal drop for the 7600K and the 12500 actually holds quite steady. Interesting to see the price of the 12500 because it is a mid-range previous gen CPU. There seems to be enough of a demand that stores haven't cut the price yet. Indicating that a lot of consumers don't really dinilay hinahanap yung next gen na sobrang mahal. So that's really how we open up 2023. Prices have been stable from the Christmas price drops. They haven't increased perhaps indicating that these newer lower prices are here to state. Particularly for the Ryzen 5000 series where AMD was expected and even dito sa atin umabot na to price them aggressively so nag price drop talaga. On the higher end of the Nvidia side 3080 bit hard to find now. 4080 tumas by a lot actually. Yung nga mga 91,000 pesos yung average price. The 4090 has stabilized again to around 111 which is quite good considering its average price over the past few weeks. But definitely no dramatic decrease in the price. Pamin saan may nagtatanong kumikilala ba kaming computer shop na trusted yung hindi kalolo ko hin? Actually meron kame. Full service PC store ang hardware sugar. Nagbabenta kami ng PC components. Nagbabenta rin kami nung We clean computers. Nasaman na rin yung excellent cable management namin and CPU cooler repasting sa cleaning. We also clean and repaste GPUs. Nasamakati yung physical store namin and you can also buy from our site www.hwsugar.ph na 100% palaging up to date yung inventory dun. Kung instock yung item sa amin available yung sa site. We also ship nationwide. Thanks for watching and if you want to these days makita tayo sa shop.