 Before starting with this session, just a reminder for you. If you have questions in the talk session, you can see a Q&A area on the right side and you can put the questions there. And the second, keep compassion and respect to make this talk session comfortable for everyone. And the third, this session is recording. And the slides will be shared later. And here, look at this slide. It's not full screen, but let me introduce about Framework laptop a little bit. The Framework laptop, this one, this is my Framework laptop, is one of the most innovative laptop released in years. And also, this is upgradable, repairable, and Linux-friendly laptop. And Fedora project and Framework company have collaborated together to support Fedora Linux on the Framework laptop. And here, just one of the outcomes, you can see left side, this is Framework official pages, Linux compatibility page. And Fedora Linux, you can see on the top of the list. And you can see right side, this one, this one, the company Framework took a survey recently, asking what is your favorite Linux distro to people on their community forums. And the result was Fedora Linux was ranking one or ranking two on the forums. So I think we can say this is Fedora's successful case to increase people. And today we have two great speakers to tell you this topic, the best. So first, Jeffrey, you can see Jeffrey, and Jeffrey is a Fedora contributor. And he has worked to support Fedora Linux on the Framework laptop from the beginning. And the second speaker, Kieran, is from the company Framework. He has worked with Jeffrey together to support Fedora Linux on the Framework laptop. So Jeffrey will have presentation for you first. And the second, Kieran will have presentation. Then we will have Q&A session. So let's get started, Jeffrey. You have our attention. Well, thank you, June. And thank you everybody for attending. My name is Jeff Jeffrey. I have been working on Fedora for over six years now. I specialize in Q&A and community outreach. I spend a lot of my day testing different composes of Fedora on different pieces of hardware, be that ARM hardware, x86 hardware, weird powered PC stuff. You name it, I've probably tested it. So I just want to talk you through how this relationship between Fedora and Framework kind of started from my perspective and how we were able to get Fedora 34 up and running on the Framework laptop. So I don't have a presentation as far as slides. I figured I would just kind of talk you through what happened. So I was contacted by Framework at the beginning of March of 2021. At that time, as I understand Framework was interested in getting as many Linux districts supported on their laptop as possible. And they reached out to us and asked if we would be interested in receiving some prototype hardware that we could run some validation tests on. And ideally have a release of Fedora ready to go when the Framework laptop was ready to ship. Of course, this all happened behind the scenes and a non-disclosure agreement had to be signed. So this was not out in the public. This was not broadcast on test lists or anywhere in the Fedora community. In April, I did receive a Framework laptop and I immediately got to work testing it. It actually worked very well. As I'm sure you know, the Linux kernel is very robust. And by the time that we in Fedora get access to the hardware, most of the time the major changes and drivers have already been added. And this was the case with the Framework laptop. At the time in April of 2021, we were testing out a 5.11 kernel. And there were really only two major issues that we ran into, one of which was a bigger issue than the other as far as Fedora QA and myself was concerned. One of the issues was that the Intel AX210 network card did not want to work out of the box. There was an issue with Linux firmware in the kernel and the AX210 card would see all the networks. It just would never connect. And this was not good. We didn't want to ship. We didn't want to tell users to install Fedora on their Framework laptop and immediately not have network and need to use a USB drive or an Ethernet cable. So that kind of set off the first challenge in getting Fedora running on the Framework laptop. The other issue was that the fingerprint reader did not work out of the box. And so these two issues, one Linux firmware in the kernel and the other was a problem with libfprint. These were the two main issues we had with vanilla Fedora 34 branched at the time because we hadn't released yet. Otherwise everything worked well. And in this time period, there was a lot of daily testing on the Framework laptop that I was doing. I would get that day's compose, try it out, make sure that everything still functioned. And the testing I was doing, I had initially thought to automate some of it or all of it if I could. But because it was one-off hardware at the time, I figured I would just manually test it each day and that would be good enough. Hey, June. Yep. Do you think you could mute your mic? I think it's picking up some background noise. Yep. Thank you. Thanks. Anyway, the testing I was doing, I'd install the day's compose and I would check everything from the webcam to the microphone. I'd check every key on the keyboard, all the hotkeys. I would try USB drives, micro SD cards. Gosh, I'm looking at this right now. The headphone jack, I would make sure that everything was still there. And throughout the life of it, I personally didn't see any regressions as far as hardware went throughout the life of that testing. At the beginning of June in 2021, Kieran reached out to me and said that there was a new BIOS version available. But it wasn't user installable and I'd need to send my main board or the entire computer back. I happened to be traveling through the area in San Francisco where the framework office is. So I just said, hey, Kieran, are you okay if I stop by? And he obliged and it was actually a great, I think we talked for probably close to two hours. And just about different things in the process of how the framework laptop was coming along from a production standpoint and other issues and hiccups. And while I was there, Kieran swapped out my main board for another one with the updated BIOS. And it was kind of good to have that face to face time. You can do a lot through email, but face to face, you can ask questions and it's just a little more fluid. So that was good. One thing that I did want to mention when I was in the framework laptop and Kieran, correct me if I'm wrong here, but I remember you showed me a room with some prototype, some very early prototype hardware. And you also had some computers that you guys drew inspiration from in the design, one of which was an original Macintosh computer. I just kind of remember that off in the corner. And that was kind of neat. I remember seeing that. So anyway, by that time Fedora 34 had already launched. Fedora 34 launched on April 27 of 21. And the framework laptop hadn't come out yet. So we had some time and there was talk about what we were going to do if we were going to spin up a custom sort of Fedora 34 release that included the 5.12 kernel that fixed the Intel AX 210 compatibility and the live F print. Or if we were going to what else we were going to do. Originally that sounded like a good plan to launch a custom framework edition of Fedora. But we don't do that very often if at all in Fedora. So it was suggested to use a re-spin. And if you're unfamiliar with what a Fedora re-spin is. I think they come out every two weeks and they include all the updates to that that version number of Fedora up to that point. So instead of installing vanilla Fedora 34 and then having to update, you get the latest updates included. And so there's much less to have to update. And because the timeline worked out, the re-spin already had the 5.12 kernel in it and it already had to live F print fix in it. So what we did is we had this re-spin spun up. And we would, I passed the link on to Kieran and users were pointed to that link if they wanted to install Fedora. They would go to this re-spin and then they would install it. And this got around the issue of installing vanilla Fedora with the 5.11 kernel and having no network on the first boot, which really would have been, it wouldn't have looked good for Fedora or for framework. So we found this to be the optimal solution. That is kind of the run down as far as what happened from my perspective. And obviously there has been testing that has been done for each release of Fedora since then. And everything has worked fine since then. I have tested the framework laptop in each of the, as soon as we branch and then at the beta and the final releases for both 35 and 36 and have had no issues. It has been flawless and it's a very nice computer. The first thing I was struck by when I received it was the keyboard. I really liked the feel of the keyboard. But June and Kiran, I think that's kind of the story that I had to lay out. So if I could pass it off to Kiran and if you have any questions, please put them in the Q&A and save them for the end and we'll go through whatever else you want to know. But June, back to you. Okay, Jeffrey, thank you for your presentation. I appreciate that. So if you have questions, please put your questions on the Q&A. I will check it. So next presentation from Kiran. So Kiran, the floor is yours. Awesome. Thank you so much, June. And thanks, Jeffrey and everybody for joining us. It's been really great working with the Fedora team and supporting Linux on our systems and Fedora, especially. So maybe I can give you a little bit of background around the product and why we wanted to support Fedora. So the framework laptop is kind of a premium portable notebook. And this was the first product that we shipped in about middle of 2021. And so when we're building a new hardware product, we usually have prototypes and early hardware about six months before we start launching to customers. And this was really a product that we wanted to target like an enthusiast market or a deeply technical market that we knew would be very interested in running Linux or other distributions on. And so we wanted to make sure that it was well supported. And we did that in a couple of different ways, actually. We actually designed some of the hardware in ways where we were expecting or hoping not to have to develop custom drivers, whether they're Linux kernel drivers or, you know, Windows drivers to support functionality. One of the good examples that we had actually is there's a couple of keyboard hotkeys that we have in our in our keyboard. And those are actually not normally exposed through like a PS2 keyboard interface, which is kind of emulated in most laptops. And so in our design, we ended up kind of wiring up a I squared C interface between the embedded controller and the BCH on the CPU and exposing that overhead, which actually does implement the functionality in a standard base way. And so for us to do that, we were able to, you know, implement, you know, all the functionality that we wanted in firmware and not have to write any drivers on the OS layer. And so that allowed us to kind of ship with support, you know, across Linux and Windows and and other operating systems without having to develop any like ACPI driver to support them or different things like that, which is kind of how we how we were able to enable some of the functionality so easily without without having to develop, you know, a custom solution for framework and then ship it across, you know, Fedora or other distributions. So, so I guess my background is I've driven or kind of daily driven Fedora for many, many years. And a number of other distributions I think I probably started using Fedora when I was a teenager, which is probably quite a long time ago, and it's been a great distribution and a great community. So, so, so, so back to our back to our product and Fedora support on it. So, so before we ship a product, when you're building a product, you actually do a number of hardware builds, like engineering build, you do a design validation build, you do production validation, and all that process starts, you know, maybe six months or earlier before you start shipping that product. And so for us to, to kind of think about supporting the Linux community and to be able to kind of ship with support at launch, we have to do a number of different things. And so, you know, one challenge that we have is, we found when we're, you know, starting the, you know, development and engineering builds of our of our laptop is actually that our CM, which is a contract manufacturer, they're the ones who are kind of in charge of physically manufacturing and building the devices. They actually do a lot of validation, but they don't have any background or experience doing validation under Linux at all. So, you know, we don't really have a test plan, we don't have, you know, people with experience internally at our CM that, you know, can really go out and validate to make sure things work and, you know, create fixes for them. And so what we decided to do is we decided to allocate some portion of our build or units that we could send out to distributions like Fedora or community members and, you know, start having early validation so that we can get fixes into distributions in time for shipping the product. I don't know if anybody else has experienced it, but I've definitely bought laptops and PCs in the past where you get it and it's exciting and new hardware and, you know, not everything works out of the box, and you might have to wait, you know, a couple months after you get your product to really have Linux catch up. And so when we were doing our laptop, you know, we wanted kind of that a better experience than that. And so working with Fedora, we were able to do this with Fedora and be really successful, which was awesome. So I think from our side, our lessons learned are to make sure that, you know, we can engage, you know, a distribution like Fedora early and make sure that we can get them prototype hardware and get that kind of tested and validated and brought up before we start shipping that. So that requires some investment in hardware and time and working with Fedora to be able to do that. So that that was a really great experience that we had with with Jeffrey and a lot of other people at Fedora as well. And the other thing that was really advantageous for us was that, you know, we were able to actually build a lot of direct connections through the team at Fedora, and the community to actually enable or start enabling other parts like LBFS firmware update. And some other features that we found, you know, we could implement a little bit better, like the thermal profile control. We ended up making some changes there to support the DPTF framework, which is kind of a CPU performance framework where you can alter the power profiles and states of the CPU. So we implemented that in a specific way on Windows and we were able to kind of carry over the same functionality to Fedora as well and add that functionality for any other OEMs that, you know, also are kind of doing a similar thermal control as the way that we implemented it too. So yeah, kind of out of this relationship that we started, you know, we met up Jeffrey in person. We had a great time and we also had a lot of other great connections to other people inside of the Linux community, which has been, you know, very valuable for us to get, you know, firmware support, firmware update support, and a really great supported distribution. So I think when we shipped our product, Fedora was, I think, the only distribution that we really had that was fully supporting all the hardware, including challenging things like the fingerprint reader. And so, you know, I have been daily driving it and using it as my main development machine, you know, pretty much ever since and it's been a good experience. So we've really enjoyed our experience working with the Fedora team. I think that's most of my talk for the Q&A. I will say, you know, we've also shipped a second generation main board and system and that's been also an interesting experience. We've been kind of committed to open sourcing as much as we can. We're a small company. And so our end goal is to have as much of the system be open source as possible to support, you know, more of the open source philosophy. And while we're not fully open source BIOS and embedded controller, we do ship with a open source embedded controller. And there's some really cool things that our community has been doing around adding interesting features to our embedded controller. And hopefully one day we can also ship an open source BIOS and have more of a complete open source firmware stack that could be used with, you know, Linux distributions and, you know, kind of allow us to support our product over a much longer period of time. So I will hand it back to June and I think we could start our Q&A. Okay. So yeah, thanks for your presentation. It's amazing. So now we have, we have 25 minutes for Q&A. So let's move on to that. So first question. Yeah, we collected questions in advance on the community forum. And the first question, this is to Kieran. What is your motivation? First, you contacted Fedora to support Framework laptop. And yeah, this is the first question, please. Sure. Yeah. So, so I think we had two things. One is the product that we were building, we were really targeting an enthusiast market. And so we were doing a number of things that we knew would be interesting to the Linux community. One is that we were selling a DIY version of the system that you can build yourself. And this is kind of, you know, one unique thing that I think that we do that, you know, is very difficult to find in other manufacturers. So if you want to buy one of our laptops, you can buy it without any RAM and storage. And you can, you know, build it yourself like a desktop PC. And so, you know, there's a lot of people who love to build computers, you know, that are kind of technology enthusiasts. And we really wanted to target that market. We thought that was pretty exciting. And that also allows, you know, Linux users or Linux enthusiasts to buy a computer without, you know, having to pay for a Windows license if they want to run Linux. So we knew that, you know, that was like a great market for our product. And we also knew that, you know, for people who want to run Linux that don't want to run Windows, they would be really interested in a product like that. So we knew that we needed, you know, a good level of support for Linux. And the other thing is, you know, we are building a laptop that's based off of the Intel platform. And as Jeffrey mentioned earlier, you know, we kind of sit in the middle. So Intel's doing a lot of, you know, kernel development for new CPUs, graphics drivers, everything like that, upstreaming that. And so, you know, all of that's kind of ready for us when we launch a product, because, you know, Intel's doing that several months before, you know, maybe new generation CPUs are launched on the market. So there's already like a pretty good amount of support there for us. And so usually, or our expectation was that we really only need to support, you know, maybe some special peripherals or things like the fingerprint driver to be able to get a fully complete system. So it's not a huge amount of work for us to do that versus, you know, if we had a very special custom platform or CPU or things like that, that would be much, much harder. Okay. Thanks for your answer. So as a note, the framework has an option not to buy Windows. So if you want to run Fedora, so just you don't need to buy Windows. Okay, so second question is also to Kieran. I have seen some framework provided the laptop pre-production version to Fedora and other communities. So was, did you actually some provide the laptop to other communities and some contact for that? Yeah, we did. You know, we provided our laptop to Fedora. I think we also provided a system to somebody in the Arch community. And I think there was one or two other distributions. I think Jeffrey's holding up. We originally actually provided the Fedora laptop with a pretty early prototype. So we have two BT builds and this was actually electrically a little bit different than the final version that we shipped. So that was why Jeffrey was talking about we had to swap out his main board because we ended up making a number of electrical changes to it where we swapped out the very early prototype for one that was closer to the mass production version. And so yeah, we wanted to kind of pick a number of distributions that were popular and make sure that they were well supported. And for that, we needed to allocate hardware to get those to the right people to try and get good support when we launched the product. Okay. Okay. Thank you. So next question is to Jeffrey and I'm curious about how many people are working to support Fedora Linux on the framework laptop at Fedora project? That's a good question, June. At Fedora, you know, we are a worldwide project and we have many contributors. That is to say that many of the or much of the work that has gone into the framework laptop has gone into it through contributors who didn't exactly know they were working on framework laptop. And what I mean by that is kind of the scope of Fedora project is so broad that we can work on all kinds of different hardware. That said, initially, back in 2021 when we were trying to get Fedora up and running, I was testing the framework laptop almost daily. And as far as I know, I was the only one within Fedora QA who had access to the hardware. But there were several other people that I worked with often, particularly within the re-spin community talking, going back and forth, saying, hey, could we spin up a custom Fedora version? Should we go with a re-spin? If we go with a re-spin, which one should we go with? Should we go with the first re-spin that included the 512 kernel? Or should we go with the latest re-spin? And it also led to other questions like should we constantly point users of framework laptop to the latest version of the re-spin? Or should we just test whichever one we decide, make sure that it works out of the box and everything else is kind of at your own risk? Any further updates would be at your own risk. So while Fedora is a very wide project, there's a lot of contribution through that. There were only a few people within the Fedora QA community who worked on the framework laptop. And of course, now that framework is in the wild, there's a lot more community support and community goings on. Okay. Yeah, thanks for your answer. So that means now a few people have a framework laptop provided by Framework, right? Jeffrey? Sorry, June, I didn't understand the question. Could you say it one more time? Sure, sure. So at Fedora Project, do a few people have their own framework laptop provided by Framework? Is it right? Okay. As far as I know, I was the only one. Ah, I see. Okay. There could have been more. Kiran, you might know better than I did. Yeah, so when we did this, we're a startup. We didn't have a ton of units to allocate to kind of third-party developers at all. And so we shipped one laptop for each of the, I think, less than a handful of distributions that we ended up sending systems to. So it was pretty limited, actually. Okay. Yeah. Thank you. All right. So let's move on to the next question. The next question is actually a pre-submitted question on Reddit forum. The first, it is a framework laptop, some specific technical topic. It is about a battery drain in the sweep or standby status in the framework laptop new version. And the question says, without expansion cards, some laptop has detachable module interface and without expansion cards or with only USB-C expansion card, it seems that the drain doesn't happen, but with some type of expansion cards, it seems that the drain happens. Do you recognize this issue and do you plan to fix it? Yeah, sure. So this has been a really interesting issue for us. And something that I think is partly due to the unique design of our laptop where we have expansion cards. So maybe the background for the question is, on the framework laptop, we have kind of removable expansion cards in expansion card base. So you can choose what ports you decide to put in different areas. So you can do a type A port, you can do HDMI, display port, micro SD or a storage expansion card. And so that allows you to kind of choose what you want your laptop to be. And it also allows you to choose where you want your ports. So maybe you want it on the left side or the right side. And fundamentally, all of these expansion cards are type C ports when they connect to the main port. So they're running type C. And what we found, this is something that we've been working on actually since we shipped the laptop. But what we found is that when we plug in expansion cards, it powers up various subsystems in the laptop. So the way that the expansion cards kind of connect through the laptop is that there's a CPU. The CPU has type C interfaces that come out. And then for each expansion card, we have a retimer. And that's kind of a special chip that is used to improve the signal integrity between the CPU and the expansion card. And that's to support like a high speed IO. So what we found is that the retimer that we use has a number of different power states. And this has to support different types of interfaces because type C can support USB. It can support USB 4, USB 3. It can also support display port alt mode, which is used for HDMI and display port cards. And so what we found is that when you plug in, for example, a USB-A card, the retimer will kind of power up. And then the host can put it back down into a low power mode. So as part of the USB spec, there's kind of different power states like D0, D1, D2, D3. And they correspond to like a higher and lower power state. So if you have an expansion card in that has a USB kind of functionality, whether it's USB-A or one of the expansion cards that has microSD or storage that's using the USB protocol, the power states are actually mostly driven by the OS. So if you plug in storage, your OS is responsible for kind of powering down the USB interface into a low power state. And generally that works pretty well. The one that's been a little bit more tricky is if you have a display port or HDMI card plugged into your laptop, the retimer actually will kind of generally stay powered up in a high power state, and it will do that in zero or in modern standby. And so that's where we see some of the people are seeing that if I plug in an HDMI or display port card, I see that the power drawing of the system is a bit higher than what they would expect. So what we've done is we've taken some of these lessons learned and we've kind of rolled some changes into the second generation main board. And so what we found is that when we go into sleep with the display port or DP alt mode expansion cards, we did some electrical changes on the main board that allow the retimer to power down in sleep mode. And so that actually reduces that high power drain. And based on that learning on the second generation, we're actually exploring one other optimization which we hope will improve both full power on power draw as well as standby power draw. And the optimization there is actually when you have a display port or HDMI expansion card, there's a signal that kind of goes through the card which tells you whether there's a cable connected or not. And so we're kind of exploring this idea that if the cable is not connected for one of these display expansion cards, we'll actually power down the retimer if the cable is not connected because the default behavior is actually that the retimer is just on all the time. And as far as I can tell, this is actually something that happens on any laptop. So if you have any laptop that has a USB-C port with a display dongle attached and is using a retimer, it's going to have high power draw as far as we haven't been able to see. So we're kind of trying to improve the recipe around that. And some of the challenges to do that is we've been working with Intel to kind of understand the problem. And it's taken us a while to really get to the root cause. And then also some of the functionality that's done this is actually in sort of closed source or semi-closed source PD firmware libraries that we can't really modify the firmware that does it. So we've had to kind of come up with some creative solutions to even try and implement some of this. But that's something that we've been working on and learned while we're doing the 12th Gen system. But our hope for this one, for this specific optimization is that I think we'll be able to port it to both the 11th Gen and 12th Gen and get some additional improvement there. So we've had a lot of discussion from our community and it's been kind of a long time coming. We were originally hoping that this might be just the optimization that can be done in the retimer firmware. Like maybe it could automatically detect whether the DP link is active or not and adjust its power state. But this is kind of the work around that we're currently trying to pursue around reducing power consumption. So I don't have a specific timeline for when this will be done. But I thought it would be fun to share in this talk. We haven't actually shared some of the background around this. But it's something that we've been working on and hopefully we'll have some fixes that we can release as a BIOS update for everybody. Okay. Thank you. Thank you for your answer. And next question. What are the problems or challenges with supporting Fedora Linux on framework laptop? And how did you solve it? This is a question to both of you. I'll go first. So I would say probably one of the bigger challenges that we've been dealing with or one of the more longer running challenges is getting support for BIOS updates. Really kind of nailed and functional on Fedora and Linux in general. And so this has been something where we work with a BIOS vendor to develop or kind of use their BIOS framework or SDK. And we found that implementing LBFS and kind of working around bugs or having bugs in the BIOS that are impacting LBFS has kind of been challenging for us to fix. So I could mention a couple of them. One is when, for example, you update your system, your BIOS, some settings are erased when the BIOS is updated. So this is not really a problem for Fedora, but other Linux distributions that may use custom BIOS like Ufiboot entries, those will get erased. And so it's not a great experience for people to do a BIOS update and then have their system not boot. So we've been able to fix some of those. We've improved this quite a bit on 12th Gen because we were able to get access to a newer BIOS SDK that has some additional fixes that are not on 11th Gen. And then we've also been working on 12th Gen to improve kind of the LBFS update experience. And so we've also found as LBFS versions increase, for example, there was a change to go from sort of an in-memory-based update process to a file-based update process. And that exposed kind of another issue in our BIOS update process where that was not working well. So this is definitely like an area of improvement that we have because to get LBFS working, we have to have people go and modify a configuration file and kind of change the default behavior to enable the BIOS update to work properly. But for this, this is also indication that we need to have more validation early on around LBFS. So if we're able to do validation around firmware updates, maybe three or four months before we ship, then that gives us enough time to actually not just try and fix things on the distro side, but we can actually go back to our BIOS vendor and have time to fix some of these issues before we launch a new product to the community. And so those are some kind of lessons learned that we've found while developing our products to really make sure that we have a really robust test plan and to be able to bring up kind of the end-to-end test process because this is something that Jeffrey or Fedora can't really do. It has to come from us to release BIOSes and then do that full end-to-end test process really early versus I think when we first launched our first product, it was a little bit of a rush at the end to get everything going and it was our first time doing it and learning how everything works. So we'll get better in the future, for sure. Okay, thanks for your answer. Now we have remaining three minutes. So Jeffrey, can you answer some short story? Thank you. Sure. Sure. Really the major challenges that I ran into were with the kernel. Really the major issue that I saw was the network not working out of the box. And that would be bad publicity if a user went to use Fedora on the framework laptop and, oh, I don't have internet. I can't update. I can't really do much of anything. I actually had more good experiences than challenges working on the framework laptop. Kiran and Narav were great to work with and very responsive to emails with questions. I remember they sent a care and feeding guide of your framework laptop that came with it that kind of walked you through why the framework laptop is different and as far as taking it apart or why certain things do things the way that they do. And yeah, so I'd have to say that there were more positives than there were challenges from a QA standpoint. Okay, thank you. So I think we can postpone a little bit, a few minutes. So I think this is the last question. So lastly, do you have a message to audiences for both of you? So Kiran first, please. I really look forward to working with the Fedora community more in the future and we really want to make sure that all of our products that we ship are really well supported as a first class citizen on Fedora and Linux in general. I think that's something that's really great. Personally, I have the motivation of wanting to use Linux as a daily driver. And so I think it's just really wonderful that we can build a product that can be used by the open source community and just works. That's the experience that we want everybody to have. And so we'll continue to work towards that for our projects and any future products that we're shipping in the future. And we have some really cool things coming down to the development train. And it'll be cool to keep releasing these to everybody. So I'm excited. Okay, thank you. So next is Jeffrey, please. Really, we were talking here as if, you know, a small team of people got on the Fedora side got Fedora running on the framework laptop and and to some extent that is true. But really, we couldn't, we couldn't have done that, especially in a timeframe given without the community that we have throughout Fedora and the willingness of people to work with each other for no personal gain other than to be able to say, hey, I was there. I did that. So really, thank you to the community. And if there are viewers who are interested in learning how to contribute Fedora project.org, I would suggest you go there and view the wiki and there's all kinds of resources and ways that you can contribute to Fedora. To Fedora Linux and the Fedora project as a whole, and we welcome that. And that is why we are able to get Fedora running on products like framework and then have talks like this. So that's, that's, that's what I have to say. Okay, thank you. Great. So, unfortunately, we are running out of the time. So, we'll finish. Thank you, everyone. Thank you. Thank you, Jeffrey and the Kieran. So, thank you. Bye bye. Yeah, thank you. Thank you so much, June, for also organizing this and, and, and planning this talk. We really appreciate it. Yeah. Thank you. Thank you, June. So, I see there are some questions in the Q&A. I will hang and try to answer any before we get kicked out. Yeah. Yeah. I'm good to do that as well. If maybe we can go through these questions. Should we do it? Sure. All right. So I guess I'll start. There was one from Neil that said, you know, would we offer a framework laptop OS option alongside windows? That was the first question that I see. I would say maybe one day we will do that on our side to kind of ship a full system that's pre-installed with Fedora, requires us that we kind of bring up something that we call CTO, which is basically enabling individual orders either that are, you know, kind of custom assembled and built as part of the manufacturing process. And so there's, there's a lot of kind of background pieces that have to come together on the logistics and manufacturing side to support that. And, you know, to really simplify our supply chain, we don't do that yet. So we do, you know, in our factory, we basically build two different versions of the system. We build a DIY version and we build a pre-built version that has windows installed in it. And so for us to enable Fedora, you know, we've actually had a request for people who would like to build Fedora. They would like other distributions. They would like nothing. They would like custom hardware. And that really means, you know, being able to build a one-off laptop. And so that's definitely something that's doable and very possible. And a lot of manufacturers do that. And, you know, maybe one day in the future we will also do that. But it does require us to, you know, set up, for example, integration between our store front-end and our manufacturing side and, you know, be able to kind of ship individually customized machines to individual users. And so just to really simplify things, we haven't done that yet. How many questions can you see it? I can see some specific questions. If you click on session and then if you click, there's a Q&A section on the right side of this. I can't see it. I don't know why. Can you move on on your side? Sorry. Sure. Yeah. So there's another question from Kevin who said, are there plans to offer a higher res or touch screen displays? I will say I can't answer this question just because we, you know, we're not really going to announce new hardware before it's officially announced. Definitely if you want to subscribe to our newsletter or other emails, you will find out when things are announced. So another question from Jason was the Fedora issue, his main issue is battery life. I feel like we answered that quite a bit earlier in the Q&A. So maybe we can move on from that one. Another one from Kevin, plans for AMD or ARM. Again, not going to go into future hardware plans, but for sure stay tuned and you'll find out about new and interesting things when they're announced. From Matthew Miller, can Fedora Q&A team help develop a test plan for your manufacturer? So yes, I would say yes, we can. And that is something that we've also started internally is to start developing kind of a written test plan that we can follow internally, but also our manufacturer could potentially follow. And so part of it is deciding and allocating resources between our manufacturer and internally for how we do testing and validation of the hardware. Right now, actually, we also do some testing internally across Fedora and other Linux distributions to kind of just check very quickly to make sure things either work or don't work to see where support is needed. Okay, another one from Matthew. What about TrackPoint? Matthew is a lover of the TrackPoint. Let's see. I will say again, I've not announced new hardware here. Or a Fedora logo key. That's an interesting one. Maybe with CTO. That one is quite difficult to do keys just because the supply chain for the hardware, really your keyboards built to the sub supplier that then goes into the full system assembly. So to do custom keys and things like that really is a very long supply chain to enable something like that. Okay, let's see. Daniel Schaefer. Hi, Daniel. And you mentioned the CPU thermal framework that we were talking about, I think, to improve this. So this is really, I think there's two parts. One is there's a thermal framework that runs called Thermal Damon, if I'm not mistaken. And this sort of manages the performance profiles of the CPU and the system. But a lot of this is actually defined in the BIOS level through some ACPI tables that will define, for example, different operating points of the system and then how the CPU should react. So it could say, if a temperature sensor goes above a certain value, then we should start throttling the CPU. And so we have like sort of different operating profiles that are defined depending on the performance mode that you set in Linux. So like on Fedora, you can kind of click in the menu bar or in GNOME in the upper right corner and there's a kind of setting under battery where you can change the performance mode between performance balanced and power stable. And that will kind of change the settings between different modes that we've defined in the BIOS to kind of change how your system performs. So this is all kind of run through, I think GNOME provides events to Thermal Damon and then that will kind of change these operating parameters that are defined by the BIOS. Okay, let's see. Sam N, we've seen a number of Linux native laptops crop up from big brands. Can you comment on what we've done differently? I feel like Jeffrey might be a good person to answer since we, I'm not as familiar with other brands. So I don't know if there's differences with how you work at Fedora between us or other companies. I would say no. There is no difference. No one really gets special treatment. That said, the difference as far as what the framework laptop offers to Fedora that perhaps others don't, really the modularity and the ability to upgrade on the fly when you want to is something that's just kind of not seen in any other brand. Maybe we have run out of time, right? I guess. So we should finish, maybe. Yeah. Sounds good. Yeah, maybe next session will be coming. Next session is the social thing. So we can keep going as long as people are interested and you don't mind staying. Okay, I see. I was actually just popping on here, not to scare people away, but to have thoughts on that last question. Okay. So I'm Matthew. I hope people recognize me. But I'm a Fedora project leader here. So I've worked with various different manufacturers, I guess in some of these things, some of which have been successful and some have not. I think, yeah, we don't try to play favorites, but we definitely like, you know, the most successful ones are the ones that engage with us and work with us like framework does and, you know, like Lenovo, like that's been the best. And also companies that are interested in Linux and interested in making it work. And so I think framework is a good example of that. And I think also framework kind of fits the open source and Fedora values in a good, a lot of ways. It is meant to be more sustainable. It's meant to be something that is not something, you know, that you're buying and then throwing away or going through. It's meant to be something that is yours and that you build and you own and you upgrade. And I think that's a good fit, just conceptually for that reason. That's why it's different. Full disclaimer, they did send one to me to help, you know, make sure it's working, but I'm enthusiastic about it. So, not paid promotion. I do really think it's a very nice fit for Linux and general and Fedora in specific. Cool. Thank you. Yeah, thanks. Thanks. So, Kieran, did you see remaining questions? Yeah, we have a few more that we can go through. There's somebody who is asking about if there's a version that has GPU options. And I will say, not gonna talk about future hardware plans again. Let's see. There are also official blank expansion cards from Michael. I would say, you know, currently we do not offer a blank expansion card, but we do have some pretty cool community expansion cards that different people have developed. And maybe the closest one is there's somebody who made a snack drawer expansion card and it's a tiny expansion card with a drawer that you can put things in. So, maybe if you would like a blank one, you could look on our community forums and pick up a snack drawer one. And then another one from Matthew. Are there plans to update the expansion card integral interface to USB4? And actually the answer is we currently do support USB4 on our laptop. So, yeah, it's supported and enabled so you can use USB4 if you want. And let's see, another question from, oh, from you, Jeffrey. Did the first revision of the motherboard work out of the box? I would say, yes, it booted successfully and the majority of the functionality worked out of the box for the very first revision that we got. So, maybe some background around this is usually when you build a main board, you kind of follow a recipe from your chipset vendor. And there's a lot of review and design reviews that you go between your ODM or your contract manufacturer and your chipset vendor, like Intel in this case, to make sure that the design is going to work properly. And on the electrical side, there's a lot of very detailed reviews. So you'll do everything from just looking at schematics, making sure that things are connected up right in your schematics to doing initial layout and doing kind of signal budget analysis of things like high-speed IO channels between different pieces. The memory interface to the CPU to make sure that when you're doing sort of your design and layout, that things are going to work properly. So the first thing is you kind of follow the recipe that your chipset vendor provides and actually if you don't follow the recipe, they won't approve your design and you won't even be able to build a product around it. So it's quite strict in terms of what you're able to do. But it also means that you have a high probability of things working the first time or at least a higher probability. Let's see. There was a question from Dominic. Any plans for AMD? I will say this is probably one of our highest-asked questions, but I also cannot talk about future hardware plans. And the last question I see is from Paul, which is where do I subscribe to the newsletter? And you can do it on our website, frame.org. And if you go to the bottom of the landing page or our front page, there's an option to subscribe to our newsletter. And we'd love it if you do that. And I think that's all of the questions. So... Yeah, we can. Now I can see your session tab. Okay, so everyone, thank you for attending this event. Yeah, I'm happy to be here. So thank you. Thank you, speakers, Jeffrey and Kieran and Mashu. Thank you. Awesome. Thank you, everybody. This was a lot of fun. And hopefully we can do it again. Yeah. Thank you. Bye-bye. Take care, everybody. Bye-bye.