 So, this is the 96 boards here at Lunar Connect. And so what are you going to do with the 96 boards? And who are you? So my name is Amit Pocheria. I am Tech Lead for 96 Boards. I'm Ricardo Salvarim, the Platform Engineer Manager for 96 Boards. And we're just officially starting the 96 Boards team. So it's kind of our first week as a team here. So you have a whole bunch of things to do around the 96 Boards. What kind of things will you do about this? So I think one of the first priorities, we need to go talk to a lot of the NARA engineers and figure out what they need from 96 Boards. Some of the things I've heard this week are we need upstream working mainline kernels, mainline bootloaders in general, working on 96 Boards. So I think that might end up being one of our first tasks to tackle. It's especially because we're talking about the hardware and we have the specification for the hardware for multiple boards. But people are also expecting to be like somehow upstream friendly in a similar corner or similar view to work across the boards as well. So we don't want to have a different experience per board. We want to actually help a little bit to bring some sanity in that sense and also work with the engineers, the NARA engineers to see what is missing from the software side. Make sure that everything is going well from the bootloader perspective, the kernel perspective, the Android builds and any other builds that we do. So you've been in NARA since the beginning, right? You got the price yesterday. That's true. Five years. Five years, yeah. Did it have a different name in the beginning? It didn't have a name, so the name used was NUCO. NUCO. It stands for New Company. Apparently I'm told that all legal documents, when you don't have a name, you just put the name NUCO in there and then when you find a name, you just do a search and replace. And how long have you been in NARA? Yeah, it's kind of a funny story because I was all part of the beginning, the NUCO, when they were building the company but I was, of course, like a canonical at that time, an Ubuntu on ARM. And we were flying around. The first connex, we all looked together with UDS. And then I joined NARA for like a year and a half, almost two years, working on the developer platform team, so doing the builds, like the Ubuntu builds for the Snowball for a few other boards that we had at that time, working with the landing teams to make sure that they were upstreaming and focusing on the right things in there. And it's funny because then now I'm officially coming back from NARA as an employee and that we have a lot of similar challenges, a lot of new exciting stuff to do and specifically because we have now a specification for boards and have people producing boards and excited about it, but we still have the upstreaming kind of problem, right? How to do it right, how to make sure that everything is compatible, that they won't die simply, be talking with the developers, everything is going upstream and everything is working well. I mean, there's things around QA and validation that we need to definitely work on, basically work with some of our builds and baseline QA team and make sure that these boards are stable when they go out. The software is extremely stable and people can use the boards for any applications they might have without it rebooting or overheating. So we've heard there are some such problems which I think we should fix very quickly. We also want to improve on the documentation side of things, make sure that people can build their own software, how to build it, the whole process of flashing, booting and so on, where to find the patches if there are two additional patches that they might be looking for that are still not upstream. So we want to make sure that we improve the experience around all the boards that we have in Ansu's boards. So there's going to be a lot of... It's not so easy to do documentation. There's going to be lots of stuff happening with that. Yeah, I think we will have someone dedicated to work on the documentation side of things. And we are also looking for to hire someone to help on the community side of things with technical support and so on and so forth. So if you're excited about 96 boards, you're excited about helping community on the technical side of things, take a look at the Linaro website. There's a position in there that we're looking for. It's really cool with an affordable 64-bit development board. It could be huge. It can be. I mean, once we have a great software story, I think there's a lot of potential. And yesterday, in the beginning of Linaro, there was a CEO before George Gray and he said that Canonical was very important in the beginning of Linaro. What happened in the beginning? Canonical was helping. It was bootstrapping the engineering resources. Because Canonical had a lot of experienced open source before and they didn't want to set up the whole infrastructure and so on and so forth. And so it had like Launchpad in the beginning. We had like how to host like the kernels because we had the kernel team in Canonical as well. That's where Anna was working before. And so we basically were helping them to bootstrap on the open source side of things, how to do things in the right way and so on. And so this is five year anniversary. What have you been doing mostly in those five years? So I have been tech lead for the power management working group in the last five years. I figured it was time for a change for me as well as for my team. They probably get tired of me by now. I think 96 boards is an exciting challenge because there's some interesting things we can do with 96 boards. But as I said earlier, we first need a very, very crisp software story around this. I mean, the software just has to work. It has to be upstream. It has to satisfy two of our constituencies, which is kernel and bootloaded developers. So those are the low level engineers. And then there's the other engineering, the maker who basically just want to take the board and do things with it, connect sensors, use it in robotics, use it in UAVs. I mean, we want to enable both sides of communities. It's quite a different job, no? It is. The power management has been a big deal for the arm world. So one of the things for me personally, even when I was in the power management team was to get one of these small low cost boards. Out to every engineer in my team where we could actually measure stuff and benchmark stuff as we develop. One of the things that's been missing in the kernel community so far is what is the impact of this patch on the power and performance side of things. We don't do enough of that. So this platform could enable that if we have the right set of boards and good software to go with it. If you didn't have the board, you were just guessing? It wasn't guessing, but we had to... I mean, power is a very sensitive topic around the arm membership because that's one of the key differentiators. And so you had access to some platforms but you couldn't actually talk about a lot of that in detail. And in some cases it was... you had to come up with tools which, yes, allowed you to make better guesstimates. I won't call it just blind guessing, but better guesstimates. So we have things like IdleStat which allow you to track what C-states and P-states the processor is going into and then extrapolate what the savings might have been. And it's also great with the Night Six boards because it's cheap, right? So it has a 64-bit platform and this is the high key. Yeah, I mean, other 64-bit platforms are thousands of dollars currently. And people can experiment and especially with the high key like you play with the build loader, it's open source. We can play like on the kernel side of things as well. We can do like a whole bunch of cool stuff around it. I mean, if you think about it, this is what is going into a Chromebook. This is essentially what's going into a Chromebook. For $70, $70 to $100, I think that's a great price point. And there's also going to be like an interesting challenge with the enterprise edition which we do have a paper around. What's the challenge with that? Because it's the first board that has, you know, like the SATA and so on is going to be like super fast PCI. And it's going to be enabling a whole different, you know, like the complete different range of applications and users and so on. I don't know about you, but I've been waiting for these sorts of boards for a very long time having fast I.O. Exactly. The I.O. is usually, yeah. And lots of memory because I want to replace the servers and my media server at home or something with one of these low cost and low power boards. I can leave it on all the time. I don't have to worry too much. Instead of consuming hundreds of watts on an Intel platform, for example. You can maybe even connect a GPU on the PCI or something. Yes. And it's a full desktop. Yes. It can become a full desktop. We're told that that's possible and it's working in the labs in AMD for this case. So this is going to be a bunch of stuff happening around this, too. Right? Yeah. And we want to make sure that the software experience for it is also great, right? We don't want people to be excited about it and buy it and so on. And then suddenly they're going to have a lot of problems. You know, because things are not upstream necessarily. They don't have sources, the right documentation. So we need to make sure that everything is, for all the boards that we produce, that everything is somehow like, the experience is somehow similar for them Is it easy to measure the power used by these boards? To make something? Currently, you can measure at the board level. We're hoping to talk to partners and get some more fine-grained power instrumentation in there in future boards. So measuring the power, measuring performance, measuring everything. Yes. Benchmarking is really awesome. It's going to be awesome. It's going to be huge. Yeah. That's what we hope for. Thank you.