 All right, well, hey, thanks everybody for showing up today, whether you're showing up here in person in Seattle or you're showing up at home and tuning in. I really appreciate you dedicating a bit of your time for us. I realize this seems and feels like a long session, 50 minutes. I promise you one thing. I am not going to be the only one entertaining you today. I have invited Stefano to join me as well. And he's going to take us down a technical path in just a little bit. But for now, let me kind of bring you up to speed on where risk five has been, where we're going, what we're excited about, and what consumes us and brings us passion every single day. So I'm Kalista. And I think I've skipped ahead a few slides. I've skipped ahead a lot of slides. Big sneak peek. Oh, I'm going the wrong direction. All right, we're going to get this all sorted out. We're way ahead of where we thought we would be. All right, we're starting this from the beginning now. All right, so Linux is having a birthday or an anniversary. It's been here now for 30 years. And risk architecture has been here almost that long as well. We've been actually a bit longer, I think. We've been around since the mid-80s. And what is exciting and interesting for us is that we're taking the ideology and the collaboration that you find in open source software, and we've brought it to hardware. Because what we've found is that barriers come down, competition comes up, innovation explodes when you collaborate and work together. So we're taking the lessons learned in software and applying them to hardware. And there's never been a brighter time to be part of this. So risk five is the free and open instruction set architecture. It acts more like a standard. In fact, once you freeze it, you need to kind of leave it sit there, because unlike software, you don't have the liberties of continuous integration and development. You freeze it, and then you add onto it in different ways. Many traditional architectures have added onto an incremental approach. Thus, over time, that set of code gets larger and larger. And for risk five, we add onto it in a more modular approach so that you can pick and choose the extensions that fit for the implementation you're going after. That is why it is so disruptive. So the disruptive aspect of the technology is not just in how it is composed, but in the freedom and liberties you have to take it forward. So when you take a modular approach with an open platform, you are no longer constrained by the barriers of your original proprietary agreement. You can go ahead and design and keep that design flexible as you continue to iterate. One design may then morph into an adjacent space. You can take it into a new field. And that is something that you can do with risk five that is unlike any other architecture. That brings you lots of opportunity. So along with the disruptive technology, you also have disrupted opportunity. And that opportunity is very meaningful. I don't know how many of you have gotten to go up the food chain to ask for funding, to ask for resources, to go do something new and cool at work. In my experience of doing that, you don't get to go because it's a cool new technology. You get to go because you've found more revenue streams. You've lowered costs. You've accelerated development plans, or you've removed risk from a particular strategy you're on. And these are all very important business decisions that go along with the technical cool factor that you've found, or the implementation that you're about to deliver on. In the case of risk five, those barriers of design costs, of IP licensing, have gone away. And this has ushered in a tremendous era of innovation. We have now more design houses on risk five than any other architecture. And there are several to choose from. In fact, there are more innovative designs going on in risk five than there were architectures in the mid 80s. If some of you dial back in history, you'll think that was the last time there was a renaissance in hardware architecture innovation. And it was the competition of many different architectures that led to a few proprietary approaches. And now we're taking a much more open approach. And we are well on our way to cementing risk five as the foundation of computing for the next several decades to come, if not more. So how big and what is the size of the opportunity that we're talking about? Keep going. There we go. So overall, we've seen an explosion in microprocessors, internet of things, embedded. You have microprocessors in your toothbrush, in your toaster, in your data center, in HPC, in your car. Everywhere you turn, there is now a proliferation of microprocessors. This is true not only in large implementations, but very small. And in many cases, such as your cell phone, you may have a dozen processors there alone. This does not mean that you need to select just one architecture. In fact, you can have many architectures. The explosion of opportunity is there across all architectures. And we're seeing and feeling from our community, many are choosing kind of the best architecture to fit. And there may be more than one architecture on a chip alone. So this brings about an explosion of opportunity. And by the way, we're about here. This is important to note, because in many of these charts, you're going to see the same visual, but we're at a different point in the timeline. So even OEMs are starting to design more and more of their own ASICs. And this is something that is continuing to grow. This can mean anything from the laptop on your desk to a white box in a hyperscale data center. Many are continuing to design their own ASICs. This is a great chart. This is one of my favorites, because the first time, well, the first year that I was presenting this particular chart, that number said 62 million or billion risk five cores by 2025. This last spring, they updated the research and said, well, actually, we were off by like 20 billion. So now the number is 80 billion risk five cores by 2025. I still think that this number is low. And I think that this number is low, because you have the show and tell crowd who are busy saying, hey, I'm doing risk five, and here's all the risk five I'm doing. And then you have the hide and seek crowd that they have risk five tucked under the covers of all kinds of things. They're just not, they're promoting that. When you buy a cake, you don't generally know where the baking soda came from. Same idea. You don't necessarily buy something because, oh, you know what, I'm gonna buy that really cool watch because it has risk five in it. You buy the cool watch for the features and functions it's delivering. Same thing when you buy a car. You're maybe buying it for infotainment or safety or a variety of other reasons, but you don't go car shopping based on the microprocessor. So the explosion is happening. It started and embedded in IoT and we're continuing to see that as the greatest, strongest growth area. Oh, and by the way, the VC community is seeing this too. And that's why there are so many design shops because there's huge opportunity. There are no entrenched sort of monopoly kinds of companies that are going after all of these new greenfield. The opportunity is there for everyone and the barriers to entry are very low. So we see this happening in IoT. Industrial automotive are leading the way. These are the new workloads that we see coming out most prolifically now. Risk five will shake up the $8.6 billion semiconductor IP market. We are well on our way to realizing this and that's because of design flexibility and the technical nuances that I've described. So those are forecasts, predictions for the future. Where are we at today? Nearly a quarter, 23% of those ASICs have a risk five core on them already. So this means that this is already happening. This isn't the beginning of a revolution. We're no longer in the realm of early adopters. This is now becoming the reality that many folks are going to work for today. In fact, we're seeing everyone from large multinationals deepening their investment to more and more entrepreneurs and startups coming online. So the IP piece of that is well on its way. You see again, where is 2021? Where are we at? So the IP is tracking extremely fast and honestly, the software and tools is tracking very fast as well. As more and more workloads come on to risk five, there's more and more opportunity and we're seeing a lot of software being ported and run on risk five. We have each of the major operating systems moving on to risk five, Buntu, Red Hat, Canonical and SUSE. And then we start to see this going out into each of these different industries. So from embedded to enterprise, we're starting to see that proliferation of starting to move on to the risk five. In data center and cloud HPC, we've had a strong, well actually I'm gonna go into each of these. So let me just take a minute here. So Alibaba has really been public in their declaration of support for risk five and has shown real roadmaps and made significant contributions already. Imagination has come on board and they're also really deeply involved in educating as well. And so you see from academia to HPC to cloud providers, we see a lot of folks that are coming on to risk five. In telecom and communications, Alibaba has done a great effort for the entire industry and has brought Android on to risk five. We're still working with Google to get their official support as well. But there is now an Android SIG, a special interest group in risk five that is really gaining a lot of attention. And we're eager to see not only Android but the affiliated applications as well. And this is also very involved here with the largest telecom provider in South Korea. In automotive, a little bit slower to start to get into the fast lane, I guess, to get on the road. That is a pun. I got one laugh, thank you. I'm gonna get you a Starbucks later for that. Automotive has been a little bit slower. They have huge safety and security things that they need to pay attention to. And we've seen a lot of advances, both from the software team over at NVIDIA as well as Europe and kind of helping to bring some of their GA-next programming on to risk five for power consumption and electric vehicles. Renasas and Sci-Fi are jointly developing solutions as well. IoT devices. So, Huami is one of them that has smartwatches. We see not only this, but we also have earbuds or whatever they're called in various places and pieces. Everybody calls them something different. I call them earbuds. But we see a lot of those now coming with risk five as well. You see things from a small label printer to soldering sticks and all these other little devices that are coming on with risk five as well as moving from there into personal computers into other types of devices used in the consumer space. So, moving forward, AI and ML. These are two categories that are instrumental to finding differentiation and a competitive edge across various industries, whether it is a sensor and security in traffic system or it's the differentiator in cloud provider. AI and ML are being brought to fruition across the board for risk five. And then an edge computing. Western Digital is one of them that has kind of really started to advance. Where do you crunch the data at the point of ingest whenever possible? Because they realize the weight of storage and memory. We're continuing to see even more acceleration in edge computing and bringing risk five to that forefront. So it takes all of us. It takes all of us to realize the opportunity to innovate and to collaborate from chip providers, multinationals to students and universities. And we are engaging around this community and there's a place in here for everyone. I've just walked through a number of charts that you could say, okay, the net message from that is everyone's doing it. But why should you do it? Why should you dedicate your time, your energy, your resources to risk five? Well, there's a lot of opportunity to be had. There is a lot of ground that we can cover together. And we see a lot of folks coming on board. Risk five membership has been skyrocketing over the last couple of years. And it was moving along pretty well and we now had to adjust the chart. It's one of those that looks pretty good and then suddenly it starts to skyrocket. And that's what we're seeing today. And I think that this is a testament to kind of getting past that early adopter phase. So now across 70 different countries, 2,200 or more members, we more than doubled. We grew 133% last year. We more than doubled already this year in the first half. So moving forward, risk five international, our central organization, we have one mission. It's to make all of our community wildly successful on risk five. So there are a lot of things that we do. And across this, Stefano's gonna talk a little bit about what we're doing on the technical side of the house. That's probably one of the most important things we do is technical deliverables. When it comes to open source, you want to avoid forking or proprietary paths altogether. So our goal is to continue to produce extensions, useful tools and other resources so that you can design implementations to meet your strategic goals and to become wildly successful. To do that, we want to make sure that you're compatible to the base profiles and platforms. We want to give you visibility. We want to make sure that we highlight not only what we as an organization are doing, but the many successes of the folks in our community. So those things are really important to us. But digging deeper than that, we need to fuel the entire community. And that means bringing up skills across our learn platform, which includes universities, it includes online learning, it includes training partners. It includes engaging in all kinds of forums to share what RISC-V can do and to meet with you out in the market, which is really what advocacy and alliances are about. So advocacy and alliance are, you've met Drew Faustini, he's here, he's one of our ambassadors. We have ambassadors, a dozen or so around the world. We also have a couple dozen meetup groups or local groups around the world that are engaging, engineer to engineer. And then we have alliances with a few dozen different organizations, regional alliances, industry-based alliances, very technical oriented alliances to work together and collaborate. And then finally, it all comes down to making sure that you have commercial success. So we have something called RISC-V Exchange for that. I'm gonna hand it over to Stefano to talk a little bit about where we are on our technical journey and invite you to join on that. It's been quite a bit of an industry innovation over the past 10 years that RISC-V has been around. There's a, we have, since the inception in 2010, the first ratification of RISC-V. There have been incremental improvements that we've seen along the way. So we've seen proof of concept hardware, we've seen microcontrollers capable of running R-tosses like Zephyr, and finally SOC is capable of running Linux. But I'd like to focus for a moment just on the innovations happening in 2021, because I think there's a lot of things happening that are really gonna solidify how RISC-V runs Linux and how it can support a rich stack of software. So first off, I wanted to mention one of the open source hardware projects that I'm really excited about. It comes out of Western Digital and it's a core called the Swerve cores. So these cores are multi-threaded and combined into a CPU are capable of running Linux. But the key is that they're open source hardware. So you can go to GitHub and download the code yourself. This is a change in the way we can think about our stack and that now the bottom of the stack can actually be open source. But to have open source hardware, you need open source specifications. So there's several specifications that we're working on this year for ratification. The first one I'll talk about is the vector specification. So the vector specification is just gone to public review and should be ratified by the end of November. And we'll talk a little bit about the life cycle of a specification so that makes more sense. But the vector specification is allowing industry adopters to align around a common standard, not just to produce something that may be capable of running Linux, but also in their domain-specific applications. Likewise, we have the crypto and bit manipulation specifications. Again, allowing industry adopters to align around a standard, but then also solving the problem of how do we accelerate cryptographic algorithms inside our applications, things that are critical to Linux applications. We also have the hypervisor and virtual memory specifications, virtual memory being, of course, core to running Linux, but then hypervisor opening the door to what comes tomorrow for risk five in the data center and an automotive where virtualization is crucial. So this is a lot of the work that's getting done in ratifying specifications for hardware for risk five, but that's not to say that there isn't a lot of work being done in the software world as well. So we've got several important communities that we're engaging with. Obviously the kernel community that we engage with pretty much on a daily basis, but also with communities like compilers. So GCC and LLVM, there are virtualization communities like KVM, real-time operating systems like Zephyr, embedded operating systems or embedded systems like the Yachto project. These community ties are really solidifying how we connect that open source hardware through into open source software and all of the communities benefit from this interaction. So I told you I'd talk a little bit about specifications and how we go through our ratification process. Specifications actually start in special interest groups that Kalista mentioned earlier. This is where we're having conversations with different member organizations around where do we see gaps in risk five today or what do we see as the future of risk five in the data center area. From these conversations, we're developing these charters for task groups which have a defined set of deliverables. We then spin off these task groups to go off and do the work and to iterate over several versions on a specification that they think is ready for publication. But before the publication of that specification happens, there are several ratification requirements that are needed and probably most important is the 45 day public review period. So the reason I say that's the most important is because it's core to what makes risk five open source. Now membership and risk five is free and you can become a member for free and contribute to the development of a specification. But even without being a member, you can sign up for our public mailing lists and participate in these 45 day review periods. This gives you a chance as a community member of whatever open source community you're a part of to comment on and discuss these specifications before they go to ratification. This brings the open source conversation in as early as possible before the actual ratification and before the tasks are complete that make it ready for ratification. Once those tasks are all complete, the 45 day review period is finished and those comments have all been addressed. Then we take the specification to the technical steering committee and the board of directors for ratification. There we go. So as this eye chart will attest, there has been a lot of amazing innovations happening in risk five and still many innovations to come. And really I think that's the part that gets me excited is that there's still a lot of really interesting work that needs to be done and all of it's being done in the open. So as an example, I mentioned the cryptography extensions. The cryptography extensions are actually just one version of cryptography, the scalar extensions. We still have vector extensions left to ratify. Likewise, there is a trusted execution environment for risk five. It's called physical memory protection. However, when you compare that environment to more mature environments like arms trust zone or Intel's SGX, there's still a lot of really interesting work to be done on risk five. This gives community members and developers a chance to participate in research and development of new and innovative ideas that has never been done in the public sphere before. It's always been behind some closed door. And that's the thing that to me really gets me excited about the innovation happening in risk five is all the stuff that's left to come and things like cryptography, security, data center and automotive. So for all of this stuff to work and there is quite a lot of work to be done, we realize we're not gonna do it alone. So we've spun up several different technical programs to help us achieve all these goals. The first I'll talk about and probably one of the most important is the developer boards. The developer board program was started because we realized for several types of industries, for example, an automotive or an embedded hardware is a must until you get hardware in someone's hands into an engineer's hands, you're not gonna make progress on moving that forward. So to do that, we've opened up a program where engineers can apply to have these development boards shipped to them free of cost. Now there is a catch, but the catch is that they have to contribute back to open source. So they have to explain to us, this is the open source project I'm gonna be working on and this is how I'm gonna upstream my changes. So by bringing communities together and putting the hardware in the hands of the people who are going to do the work, we not only benefit the risk five community, but the other communities like GCC and KVM that are gonna participate because we enabled the engineers to do the work they needed to do. Now we realize we're not gonna be able to put a piece of hardware in everyone's hand on our budget. So we do have the risk five lab program as well. The risk five lab program has just started. It's pretty much in its nascent, but I think it's gonna be one of the more interesting open source hardware projects out there in that it's going to allow labs that already exist in academia and in corporations and also new labs that wanna spin up and store hardware to allow folks to run continuous integration, regression testing and actually log in to risk five hardware so that they can test their applications and test their ideas before they bring them into a specification or bring them to the risk five communities for more development. Now this has just gotten started, but we already have two different academic institutions and one corporate institution that's helping us to run this and we're looking forward to adding more members to the risk five lab in 2022. Another program that we've gotten started is the risk five developer partner, sorry, the risk five development partner program. One of the thing we realized early on was that the architects and the designers that are helping to write these specifications may not also be the right people that are gonna be writing the tests or that are going to be integrating the golden model or that are going to be upstreaming work to GCC. So what we did is we compiled all the members of our community into one area where those are the core tasks that those folks work on and what this has allowed is a clean handoff from the writing of the specification through to the ratification tasks I mentioned earlier. Those requirements like upstreaming changes to GCC and LLVM or upstreaming changes to the kernel are critical to the specification success but may not be the core competency of those architects that design the spec. So we've again got a bunch of academic institutions and corporations that are already participating in this but I'm excited to say we also have lots of community and individual members that have chipped in. So for example, we have a sale golden model that is part of our architectural tests for compatibility. That model has been written not only by academic institutions and students but also by individual community members who are interested in formal specifications and how can we assure that these specifications that we're writing actually do the things we want them to do in the real world. So as part of our compatibility, we're building on platforms and profiles that are up for ratification this year that are going to create a bar to which anyone looking to implement risk five can show here's a level of compatibility to which I guarantee my product will have and we've got all these great programs standing behind them to help them upstream the work that they need to upstream. Speaking of porting software over and upstreaming stuff for risk five, I did want to mention a couple of different porting efforts that came across our desk recently. So libraries like SPDK and DPDK are pretty robust and complex libraries but as you can see only took weeks or days or even weeks for them to port. Now there are a couple of reasons behind this. A lot of times you have corporate interest or a large group of people that are interested in moving these things forward but the great thing is that we've got a community willing to help people port stuff forward. So as you're trying to bring your applications into the risk five ecosystem, there's a whole group of people willing to help with that effort and that's really the key to what helps risk five succeed is building off of this low level hardware community and allowing it to build all the way up through to the software stack. So I mentioned there's a lot of different communities and I promise this will be the last eye chart but if you look at all the different groups that we're involving in with to create an open source ecosystem, the thing that really sticks out to me is that the ISA is at the heart of it. So unlike before where you might have had an open source software stack, now you've got an open source ISA at the heart and I've already mentioned there are open source hardware implementations out there and what this does is allows the open source community to reach out into a branch that it hasn't been able to reach before and that's an open source ecosystem that stretches from the hardware, from the ISA, all the way through to the user and software and that's something that's never been done before and something that's really exciting. So with that, I'll pass back off to Kalista to talk a little bit about visibility opportunities. Thank you, Stefano. So I challenge you, where do you find yourself in this chart, right? Everybody's doing it, where are you in this chart? This is about how we build community beyond risk five, beyond our members and into the larger industry. Maybe your interest is very industry specific. I still think we have a place for all of us in this chart and that brings us to visibility. One of the big areas that we use to support the commercial success and the success of all of our members if they're in academia or research included as well. There are many ways that we look to showcase the success of the community to recognize and appreciate the strides and the investment and the dedication of our community. And these are just a few of the ways, I know Stefano promised his was the last eye chart, but we have more. We have lots to talk about and these charts will be available for everyone to consume but we invite you to engage with us, engage in the many ways that we can showcase your success and that we can support you. We can support you and your advocacy to dig deeper and investment with your organizations to look for ways to bring your technical teams to risk five to accelerate your traction in your journey because there are so many great reasons to do so from cost savings in taking a risk five approach to design flexibility to accelerated road maps to infusing your technical strategic point of view into the ratified specifications. As Stefano was talking about, the importance of that ratification review period and all the processes and steps that we take, it's because we do freeze it. It does act like a standard at the end of the day and we want as much thought leadership in there as possible. So we'll close now. We'll bring it to some Q and A time. We've got plenty of time for that. But wanted just to highlight that we are here and on the show floor, if you come by, you can also get some risk five fashion. This is this year's T-shirt and would love to share those with you. We are also having a buff on Thursday for the first half of the day where we'll go deeper and we'll engage more with the community around what is happening in risk five from software to hardware and all things in between. I promise it's going to be fun. If you're in the Bay Area or you have friends, family, coworkers in the Bay Area, please invite them to join us at our summit which will be co-located with DAC and Semicon West at the Moscone Center in San Francisco in early December. So we're super excited about that. It will be a hybrid online and in-person event. So please join us for these and please come in and join us here. Stefano is here, Kim is here. We can talk visibility, technology, industry, outlook and all things in between. So thank you and I welcome any questions. What we are interested in running on it and then do you have already like software or for software infrastructure to specify how would you think about it or is it just if you can go now? Can you appreciate the question for them for the deaf? So the question is on how can you engage as a risk five lab or leverage a risk five lab and is there a certain construct on the software? How does that work? How does a risk five lab work? And I'll let Stefano answer that one. Yeah, so right now we're still just in the process of building risk five labs. So we've chosen and continuous integration platforms that we're gonna be using build bot to actually do the work, but we haven't actually completed the list of tests that we're gonna be running. So we don't know exactly like here's the list of regression tests and here's the CI pipeline you're gonna be looking at, but we're in discussions and now into what can we do and what's already being done out there so that we don't duplicate efforts. There's two of the big things going on now. And then in terms of like who can sign up, absolutely anyone can sign up. This isn't gonna be restricted in any way. I think the main thing is gonna be that in order to call yourself a risk five lab, they'll probably just be a bar to which you have to meet. It may just be here's the architecture you're gonna need to build for and here are the tests we need to see being run, that sort of thing. My use case is are you guys thinking about risk five taking a bigger role in the disaggregated future that we see in data centers, especially in memory cyborgs, are you guys working with TXL, Gen Z, Lopez? So the question is on, what role does risk five play in the larger disaggregated data center and how are we advancing that? And our friend here from Seagate is excited to hear more about that. So to answer that, I'm not sure what all of the technical platforms are that we're using there, but as we see it advancing in hyperscale and in data centers, we're kind of akin to what you would see in a scale out HPC environment. Many of the variables are quite similar and that's kind of the advance that we're seeing before it gets into full production. Alibaba is perhaps our most vocal proponent for this and many are using it initially in some of the acceleration. Not sure how many Western Digital is using it, I think, more around some of the memory, but you might, do you have a point of view? Yeah, the only thing I would ask is we do have a data center special interest group that just spun up. So they're having conversations now around memory fabrics and around things like SmartNIC and what are the things that we see in terms of goals for tomorrow that we should be stretching for and where are the gaps today that we need to address so that when we're looking at SmartNIC down the road, what are the things that we're gonna trip over? So that group has started meeting, Alibaba certainly shows up every week, but there are folks from several other companies that come in and yeah, I think we announced on them public mailing lists a month ago, so it's still relatively new, but yeah, absolutely getting some steam. And I think that from what I'm seeing on that level, folks are not necessarily looking to rip and replace the millions that they've poured into existing architectures and investments, but they're looking at risk five, primarily in new investments and new space where they don't have existing and trusted investments. And we are working very closely with open power and others on how do you kind of position for portability or multiple architectures living together in harmony. And so that is I think the direction things are going as folks start to shift over time and next generations onto more of an open approach to hardware. More questions? Hiring managers, looking at... No, that's a great question, mind if I... Yeah, go for it. You can get your stuff. Because I'm excited. No, that's, I'm excited because... Stefano is not looking for a job. Yeah, no, I'm excited because we actually just, we're spitting up some training and that training that we're gonna be doing that certification, we're meeting with folks in the industry to say what would you look for in hiring someone? So here are the skill sets that you see lacking in your applicants and that's the kind of training that we wanna spin up. And I can say just looking at the people that I work with every day and the kind of thing they're struggling for, it's really a mix. There's a lot of software needs that are out there, people who understand sort of the whole stack from the compiler on down to the architecture, but then also just folks who are looking for verification engineers. Or it's hard to find verification engineers that haven't already been gobbled up. So yeah, it is a new opportunity for lots of young graduates, but then also folks just looking to make a career change as well. And some fun facts. So we launched our first online risk five learning, which part of it Stefano helped to write. And we've had like 6,000 people take these classes and it is one of the fastest growth online learning that Linux Foundation has seen ever. And so they have been blown away by the numbers who are signing up for our courses. And that's just what we're offering. Imagination has invested tremendously in a college level course that they're making available. We have half a dozen different training partners that are giving like large group training. There are thousands of folks that are taking online learning in other pockets around the world. This is a huge push across universities. Pakistan has basically said risk five in all universities and have set up specific training institutes. India, thousands of folks in India have been going through risk five training in online courses as well as like week long deep dive sessions to bring skill levels back up. Yeah. And we have a job board too. We've launched a lot of things this year. We also have a job board that is available where we're posting internships. Our internships have gotten a lot of attention and our members are able to post and we see a growth there as well of available risk five jobs. Yeah. And Danny, Danny at Futureway is hiring as well. And he also is wearing his risk five fashion. Yeah. Distribution globally or is it all in China or like where is that being done? The actual like, okay, we designed a chip and now somebody is gonna. Right. So the question is around, you know, how many FPGAs are available and where are chips being produced? I think most of the production is happening in China and that's sort of a global statement I think on most architectures. But, you know, we have several FPGA projects that have spun up. There's, I forget the name of the FPGA group that Navid just started to. Oh, yeah. Yeah, we do have a soft CPU group that specializes in the FPGA and, but from like spending the actual ASICs from the actual production of the chip, I think you'll obviously see a large quantity that coming out of Asia. But I think you've already started to see if you're watching the news, like local state sized folks talking about what risk five is in their future, like in terms of actually producing, if not, you know, CPUs, but actually domain specific processors or, you know, some, right, from a fab level. Yeah, I think not to sort of read the tea leaves, but I think long term, yes. I think because the architecture itself is open source, it's lending itself more to fabrication techniques and industry techniques that are more open. But that's something that really will change the entire fabrication industry. And so that's something that, you know, we may see farther down the line. Well, thank you so much for joining or tuning in or dialing in later. Really appreciate it. Thank you so much. Thank you.