 And here at LinarConnect, we have Chromium OS running on the Snapdragon 845, is that right? Yes, that's right. So what kind of board is this? So that's a development board from Qualcomm that used the Qualcomm Snapdragon 845. Can you see on the other side? That's just like debug board where we just put it. But there is nothing interesting here. But there's... All right. And so this is running the 845 Snapdragon, which is one of the latest chipsets that you can find from Qualcomm. And we've started to work on these chipsets several months ago. And we've started to upstream in the mainland kernel. I mean, most of the support that you would expect when running such a demo. So display driver, audio driver, you have Wi-Fi right now. You have positive mic, yeah? Yeah, all the connectivity drivers, all the peripherals, storage. And all this work has been happening over the last few months. And here what you can see is the Chromium OS. So it's built out of the master branch of the Chromium OS source code. It's running the 4.18 kernel with some of the... I mean, a very few additional patches to finish the enablement of the software. What you see here, you have hardware, accelerated video playback. The rendering is done thanks to the Open Source Freedom driver, GP driver, that I think you've talked many times about. And yeah, it's running... I mean, you can mostly run this stuff out of Mainline in the next, one of the next very few Linux versions. So how's the performance? Is a lot of optimizations that needs to be done or...? I mean, in terms of... Yes, of course. There is performance to be done on the CPU side. So we are missing... I mean, it's not running at the highest speed on the CPU. It's not still not running at the highest speed on the GPU. And there are some LLC memory which is still not enabled for this. And video can be enabled for UBWC, compressed format. So a lot of things, a lot of work which is yet to be enabled on this, which will improve the performance. What is this LLC? LLC is like last level cache controller, which is similar to internal memory or cache memory, which will enable all the hardware to be performing better. So that is not enabled here. So, you got FreeGrenural enabling this? Yes. So what kind of work happened with that? So, hi. Hi. So what have you done with this one? So, I mean, we've been spending the week kind of integrating the hardware video playback with the open source Arduino GL driver and getting it working. Yeah. Can you come closer to the mic? Sure. Yeah. So, yeah, it's early stages, but it works now. Can we go around and click and stuff? Sure, sure. Let's see. I don't know if it might take a moment to load on the network here, but I'll give this a second. So it depends on the network. Yeah. Is this a Snapdragon 845 development tablet or? It's a development board that we use. Development board? Yeah. But there's no 96 boards yet or something like that with the 845? No. There are a few of the quality partners that I can make, board with 845, like such as Sonosoft. So you can buy devices, I mean, dev boards, which are pretty expensive. But there is no 96 board yet. Right here you have your... How's that, the full performance? No. I mean, there's a bunch of driver features, which I haven't had a chance to implement yet. What do you say, hardware binning? What do you say? Yeah. I mean, it's one of a bunch of performance-related features in the GPU that I've not enabled yet, maybe next week. So Chromium OS and Chrome OS uses a lot of hardware acceleration all over the place in the browser. Yeah. Is it a hard work to enable all that in the browser? Yeah. So they use, I mean, OpenGL, OpenGL ES. So, I mean, as soon as you provide the implementation for that, whatever they do in the browser is going to be optimized on the GPU. Similarly for the video, I mean, so they rely on some very standard kernel interface, such as V4L2, which is the video interface for when you give like a compressed frame and you get an uncompressed frame back. And so as soon as your platform software, your Linux kernel provides this implementation for the driver, then you get optimized video playback in the browser. And what is the role around the Linares community to get this enabled? So, Linares, that's a good question. So Qualcomm is a member of Linares and as part of what Qualcomm wants Linares to work on, we are basically doing a lot of upstream work in the Linux kernel for many different and many Qualcomm platforms. So this is the latest one that we have been working on, I mean, since last Connect, and that's the result of what has been done so far. What you can see here, everything that runs here is open source. 95% of what you are seeing here is already merged somewhere, I mean, in the relevant option project. And there is nothing which is not going to be merged. I mean, it's three months from now, everything that you see today will be merged wherever it actually makes sense to be merged. So there is no proprietary software used. I mean, there are blobs, blobs used for the GPU and blobs used for the video IP. But on the Linux side, there is no proprietary software at all, which is being used. So, do you use the Fridu or no? We use the proprietary GPU driver. No, we don't use that. We use Fridu. Yeah, the firmware that we need, I actually already available in the Linux firmware project. On the Linux side, kernel and user space, there is no proprietary software at all. And how's the performance of Fridrino compared to the official Adreno driver? We are not ready to... I mean, we have not reached the full performance here. So, I mean, doing benchmark today will make much sense, so we can't really talk to that. Maybe next Connect we will have more numbers. How do you do to optimize the GPU driver? I mean, like I mentioned, hardware bidding is an important feature that is still missing. There is LRZ and compression, tile textures, some 4G LES in particular. We need to have medium precision support in the shader, which is mostly not Fridrino specific. It's a lot of core Mesa stuff and some folks from Magalia are working on that already. So, as all those different things fall into place, I will get considerably faster, of course. And they say when Google releases a Chrome OS Chromebook, what is the difference between what you do and what they do? They just take it and use it. So, when Google make a product, they pick one SOC, it could be any of them. And so, what they do, they start with Chrome OS, which is the open version of Chrome. And what they do, I mean, we don't really know. So, when they add some more like Google services, proper software and API, they hook up into the Gmail and whatnot. Here, what you are seeing is the open version, which is only Chromium. What Google does is, we don't know, basically. There are a lot of customization. Is there any way to say how far this is from a product? Or how potentially a product? This is just a bunch of developers trying to work with upstream. And this is a cool demo, so the software is available and that actually makes a demo. We usually, I mean, you've seen that previous connect. We always make the demo on the Snapdragon. So, we thought it would be a nice idea to have you show something slightly different this time. So, how's the performance of the Snapdragon 845? Is it the coolest processor right now, the smart smartphone? It's got lots of juice in there, right? It depends if you take Apple into it. In terms of all the end... Apple is not in an arrow, no? No, not yet. No, not yet. It was good. Yeah, so it's the flagship chipset from Qualcomm this year. So, every high-end phone... The amazing second-generation 10nm? It's the latest. There's a lot of stuff you can get out of that to get cool performance. And the browser is as fast as any consumer would want. And potentially, you can open a whole bunch of tabs and it will just load, render everything. I mean, of course, there will always be, I mean, limitations. They are limited by the memory most of the time that you have on these platforms. But yeah, I mean, this is the best CPU you can get out today, on the market.