 and that's what I'm going to introduce to all of you. My friend, Mike, please. My friend Mike. I'm going to introduce to all of you guys the speakers for the feeling of this talk. This talk will be done by me and my co-partners. The first person to introduce myself. My name is General Lee, and the person called me by the internet. I know what it does in here. I started working on this distribution in 2014. It doesn't become over the feeling you're local. Now I know the feeling, the technical committee members describe the feeling. The feeling community is an open source community that's about many people from different places. We are able to build an easy to use this total rating system. The image on the right is our UI over here, which has this total table in the north. And suppose we're running on X186 up and it's very architecture. And below is our home page. You can go there for more information. Respire with an image in open source instruction set up actually to offer numerous benefits, including flexibility and security. Our team is advocating that we're exploring potential applications and contributing to the development of this technology. Our team has many respire orders in world, including escalated devices and deep computing staff files, T-Heads, hyperlabel, and so on. This is a very welcome of our work on respire for the hardware to choose high-file mesh between 5 and 20. In the common layout, we object to the offline optimizes according to the hardware characteristics, including powerful managing, update display support, computing library and so on, to improve our performance. Also, we build an easy-to-use desktop environment called Mender UV-R to be re-use for rendering experience and for the application. We create an application-compatible way based on QMU or to enrich the application ecosystem in which the application of S8 and 6 architecture can run directly on the respire architecture. This is our landform architecture from source code to packaging combination to managing generation and to unite gesture. Those management and translation management are also connected to our computer. We try to automate the process as much as possible, including automating the code environment and automating the testing of the data industries. For respire-related compilation work in most tools, that's all QMU is used to lock up the devices. Since the end of last year, we have had almost 800 respire activities compiled successfully. Our goal is to build an open-killing respire version with a rich software ecosystem and seamless user preparedness. To achieve this, we are heavily focused on hardware platform, production and software ecosystem. Next time, my partner, the other one, will show our space-based work in those areas. Good afternoon, everyone. My name is Wang Wenzhu. I'm from the High Hall Library of Information Technology and Application Innovation in Tianjin, China. As a member of the open-killing technical committee and the respire of stakeholders, I'm thrilled to be here sharing our work with you. My teammate, Li Jianfeng, has already introduced the work of the open-killing community which covers software compilation and the system structure. In my part, I will elaborate our other work in the initiatives related to respire. First of all, let me talk about the hardware adaptation. For respire, it's new and promising as an architecture, but it also faces some challenges due to its early stage and lack of unified standards. This makes it difficult to adapt operating system on different respire hardware platforms. Therefore, we have been working to make our education compatible with various respire devices and the usual optimal performances. The first is to improve the power management module. This involves modifications to the device tree and the kernel driver to enable the operation of the power management chip. Then we can perform device shutdown, restart, and other functions. Secondly, we are working to optimize the system startup tool and reduce unnecessary service items. This ensures faster boot and efficient reduced boot time. Thirdly, we configure the operating system environment to ensure the normal rules for screen display network cut and USB devices. As we all know, GPU is a key factor that impacts the user experience. Therefore, we have developed a complete GPU software stack to provide seamless user experience. The first component is the driver in the latest kernel. This driver controls the GPU hardware events, managing the input and output of computing tasks. The second component involves adapting and calling GPU-related libraries including Mesa, G-Sphere, LiveGL, and other labs, which are essential for GPU. Further, we have completed the adaptation between OpenKD-UQI and the other software to ensure the normal rules of GPU in desktop environment. Finally, user-level applications such as the regional playback and the web browser are modified to utilize the GPU-level records. This results in higher performance and better visual experience for the user. So building a rich software ecosystem for this value is another key factor that we have been actively pursuing. Firstly, we have created a search of tools and resources that help developers use RISC-L more easily. This includes the comprehensive RISC-L 2-chain, that includes compilers, assemblers, debuggers, and other essential components. Additionally, we have created a software library that provides a range of calling functions and modules for RISC-L based on systems. This library includes various drivers on the utility slide, and you can quickly leverage the functionality of the RISC-L library. Also, we have built the basic user applications such as the bare-box library-based app and the OpenKD-UQI software, which can meet the basic needs for the data work. Finally, we have established the document and the support channels to help developers learn about RISC-L and address any problems they may encounter. Another way to enrich the software ecosystem is binary translation. This allows applications designed for one RISC to run on another RISC-L class. For example, I posted RISC-L 2 in both M1 and M2 chips to run x86 applications. There are also many open source projects that can achieve cross-platform software compatibility. In OpenKD, we are also working on this area to make x86 applications compatible with RISC-L. You will have many of the two technicals to improve the performance, including local library wrapping and dynamic block hatching. A local library wrapping is necessary to translate library files from the source platform to the target platform without transmitting overhead. This allows the platform to directly call the APIs of the local library, avoiding the translation process and greatly improving the system performance. This is the dynamic block hatching. It's another powerful technique as we all know, a small amount of code is executed for the majority of the time, such as the value and the order. By catching a translated code, we can award the need to retranslate each time, so instead we can use the previously translated code which saves time and improves the overhead system performance. Catching a code across can be implemented using different strategies based on specific application scenarios. So finally, let me briefly introduce our version of this work. It is very important to make OpenKD accessible and available to as many people as possible. Since we released the first OpenKD version Only.7 on July 2022, we have updated all version versions, each of which face the previous bugs and add some new features. For example, in version Only.7, we supported VLAN and adapted OpenKD's self-evaluated software. In version Only.7.5, we improved the system stability in OpenKD 9.5, we provided the latest Ukraine desktop environment. So our goal is to make OpenKD on this style a robust desktop environment system that can be used by a wide range of users from desktop users and developers to researchers and artists. So far, OpenKD can run on a five-way style platform, including HVAL iMatch, VisionDial 1 and VisionDial 2, T-Hide and also the Acubus. So the total number of downloads for all versions have reached 15,000 in under a year, from July of last year to now. And we hope to see an increasing number of research users in the future. Now I'm very excited to introduce Roma, the world's first laptop that comes with OpenKD pre-installed. We have equipped the system with basic application software and development environment to provide great use experience for experienced artists and users. So let's please welcome Mr. Liang Yun-Yin, the founder and the CEO of XCalibat, who will introduce the Roma laptop to us. Hi, everyone. Thank you for the great introduction on the OpenKD stuff and the great stuff. And I tell you the story why I started making the first laptop of my life. I run a software company called It's Terrified. We used to make compilers based on Open64. And we decided to make a laptop and to try to get it mass produced from a software guy like me and see how hard it is. It's quite hard. And this is the reason. The reason is that we want to have an experienced 886 you can carry around and play with it. And we come out of this type of storage and we don't need that close compiling. And a lot of open source is not supported but it holds compiling. And I want to try the latest on this by SOC, not only to see how many problems in manufacturing and especially mass production. I met a lot of problems especially in 2002 with the whole COVID things in China. And this is the whole from Mark this is by International. If we can get native development now we can access the software ecosystem OpenKit in all libraries and so on and so forth. And look at the laptop. This laptop is the thing is I can find and do. And we try everything hard. And it will support now OpenKit and possible Chrome OS in the future. And we make some speciality for example, we just kind of try it in the cycle and stuff and begin the box and like the stand and we make a very special hot kit close. Let's get rid of the windows. So that's the problem. And yeah, you will see if the window can show me here. So let's see where it is. It's real. So I don't know if you can see. But anyway, you can see this is a real respite things right and running on it's not joking. So let's see the R key see whether it works. R key for work on browser work. It takes a while to hold up. So you can see it's very very slow. But the point is that why we have to make the first step. Just 19 years ago when ARM has the first 64 bit it follows that now. Right. This is the first 12-inch 64 bit SOC. So and it's now in my experience I put the first ARM 64 bit on Android for Huawei. So I don't know what to think. I think now that respite is evolving with that kind of performance it's far better than ARM 10 years ago. So we look forward to another 10 years and respite will go beyond much quicker than ARM. That's all. You can see the browser is here and it's very slow. And we get better. And especially in May we have a much produced version. A lot more stable. The software looks better. So you look at now. This year we tried 12 nanometer. You will see we might have a much reduced problem. Probably might not be going through the stress testing and heat testing or stuff. But the 22 nanometers fine. And we will look in forward to the end of the year. We support 64 core very thick laptop coming up. And we have a big factory. And you can turn on and off all the cores. Whatever you like. That end. We look forward to Jim Keeler to blow out a very big FED IP coming out and probably sell nanometers. So we look forward to the older trend. And of course we cooperate with open heating. We have a lot of programs on the user the community program. So we are going to do some report for all the people contributing back to heating and our hardware products. And that's the people things. I use the thing is laptop structure. And with the high performance 12 nanometers ever in making a laptop and no experience the pain will come. And we go on through you can see this is the pictures that the SOC not designed good enough to much produce and we need a very high precision soldering just like mobile phone. Mobile phone is a lot of high voting and I can't book the capacity at all for just doing the soldering on the phone. But anyway we get it done by some good friends and this is our motherboard. So the motherboard we have we call it SOM module. And the motherboard we use. We try to use especially after a while we have our own chipset coming out the motherboard won't change. But the SOM will change according to the SOC approach. So it's a very ambitious ambition project. But it's very painful like Peter been chasing me for one. But we will get in there and we will get there. And yes we will open source our motherboard so everybody can take a look and how to make a laptop very easy, very simple. Now from our experience we can say that we will A to 10 weeks we will swap a new SOC and we can match produce a thousand laptops that quick. And yes and we will hopefully in around June we will have a push grab reviewer program. What money can we put Peter in the market. So wherever help us make him better product for RISC-5 or OpenKilling we will reward him. And yes we have a very good relationship with OpenKilling hopefully and we can run a very good international version of OpenKilling we are excited to see that we will do it over now. That's our goal. Thank you very much. RISC-5 chips is amazing to the thing going in. I'm kind of curious like where are you seeing compared to like the arm is good progression right? How do you feel like it's going to come out as far as power versus performance as it evolves? The hot ways I would say that is chicken and apple and the power and performance always a triangle balance. Hopefully the battery if I say that we are trying to compare 86 and I would think it's better but before arm I don't know right in the short term no. But we give enough time with RISC-5 and my approach and the point is we need the one thing now all the SOC companies they always have to choose the development goal. It's not the final product. That makes the the growing is hard. You got to go into a mess for the moment out of practice right? So to move people quick otherwise everybody waiting just showing off the development goal is not going to happen. But you got to test the market and if you fail and you make it better it's better. Hopefully I answer your question. Alright, all questions in the back. It's really great to see another open laptop. I'm curious about the case in the shell. Is that something that you've developed all the idea yourself or is there a library that you can go to that gives you things like the screen and the touchpad and all that like a standard display things like that. And I would say that all these in South Southern China they have a lot of common basically second of the libraries and then people can just match produce it with no copyright and blah blah blah whatever it is. And there's some fancy things there's some untested things and 90s one actually is matched producing in 886 and in the latest i7 and this year I and I did bigger screen. So we used the tested version of the structure and we just changed the board to this type. Basically I would say that anything help this type of pick up and whoever have ambitions that would be. That's why I go to all the people experience and I don't want the world to meet it again. That's why we open source it. You mentioned that you're going to match produce soon. Match produce session will be 7.0 will be DIY planning will be easy for you to replace screen replace battery change to go live. I think we will match produce this one and if the screen and all these things as not as you fit in the structure that possible. But if it's not then it's not. If it's not a modular it's not a full modular design yet. When I look at Chrome Google they do design a modular but the problem is that when you become modular and the price go up in the match produce. For example the 22 nanometer we looking down US dollar and the bone you know size whatever whatever whatever So we had to leverage the common view so we share a law component to x86 otherwise we won't get that cheap at all. Alright another question. We do that are you familiar with laptop? Yeah I heard about it but it's not going to get the price down. The price range is very weird. You have to reuse components as much as you can. Otherwise you even your modular but you know you module with nobody. You module with your own cell phones. So you had to be sharing. Share as much as you can. Yeah and take the fancy structuring and change it and share as many components as you can and that will make much better. At the end of the day the laptop the battery basically the motherboard thing will change. Except 5.5 5.6 5.7 There's no point in changing a laptop for the motherboard. That's why we call it USB. Hopefully it will work. Yes. What supports extension standard USB and HDMI? Everything on Xtm. HDMI, Type-C Blah blah blah blah blah Type-C That means USB, USB port and audio and everything. Same as your mobile. Yeah. Okay. One more question. You mentioned about this. So then also by you think the chip is up? No, not the chip. We use in star 5. We will use all the SoC on the market and try to make it more useable. You are like a crazy guy like Peter we ship all these crazy things It's just to be honest with 5 isn't ready for normal use but it's ready for the crazy developer have a dream about this by grow bigger in 10 years time like us.