Google Working On New "Fuchsia" Operating System, Powered By Magenta / LK Kernel

[duby229]

I still didn't see. The only code I know, which have a sense to run before the kernel, is some kind of bootloader. Drivers and most of initialization would be in Linux kernel; so what's the point to run one more kernel before that? To… initialize something which Linux kernel can initialize either…? That just wouldn't make a sense.

Well, that's basically what lk does.

https://www.codeaurora.org/blogs/little-kernel-based-android-bootloader

[Hi-Angel]

They get to run code before the linux kernel even gets loaded.

I still didn't see. The only code I know, which have a sense to run before the kernel, is some kind of bootloader. Drivers and most of initialization would be in Linux kernel; so what's the point to run one more kernel before that? To… initialize something which Linux kernel can initialize either…? That just wouldn't make a sense.

[duby229]

Hmm, wait, I didn't get, what are advantages of running a kernel from a kernel?

They get to run code before the linux kernel even gets loaded.

[Hi-Angel]

Android devices, in particular, QUALCOMM Android devices, have been running Little Kernel since the HTC DREAM back in 2008.
The version of the LINUX kernel that you are running has nothing at all to do with Little Kernel.

Bootloader chain;
PBL --> SBL1 --> SBL2 --> TZ --> SBL2 --> SBL3 --> LK --> Linux

Hmm, wait, I didn't get, what are advantages of running a kernel from a kernel?

[droidhacker]

Mhm, mine have version 3.4, and I doubt that 15M lines is little enough :Ь

More over, LK modules are incompatible with Linux ones. And, given there's a bunch of peoples hacking around to have Cyanogen Mode up and running on new phones, plus manufacturer's programmers, who needs to know what API they programming for, the world would have know about the new kernel quickly.

Android devices, in particular, QUALCOMM Android devices, have been running Little Kernel since the HTC DREAM back in 2008.
The version of the LINUX kernel that you are running has nothing at all to do with Little Kernel.

Bootloader chain;
PBL --> SBL1 --> SBL2 --> TZ --> SBL2 --> SBL3 --> LK --> Linux

[funtastic]

Most interesting thing I found out from this: it uses Flutter, a framework to develop Android/iOS apps from Google (using Dart). This project has been flying under everyone's radar, but it looks like finally we are seeing Google reacting and making something better than the current tools to develop for Android (Java, Android SDK).

https://flutter.io/

[mmstick]

Rust has been found in the source code.

[Hi-Angel]

Just a little bit of information that most people here would probably benefit from knowing about.... your Android phones most likely *already run* littlekernel.
aboot (multi-boot loader), and fastboot are applications that run on littlekernel.
https://source.codeaurora.org/quic/l...tree/app/aboot -- note that "lk" == "littlekernel".

Mhm, mine have version 3.4, and I doubt that 15M lines is little enough :Ь

More over, LK modules are incompatible with Linux ones. And, given there's a bunch of peoples hacking around to have Cyanogen Mode up and running on new phones, plus manufacturer's programmers, who needs to know what API they programming for, the world would have know about the new kernel quickly.

[droidhacker]

Just a little bit of information that most people here would probably benefit from knowing about.... your Android phones most likely *already run* littlekernel.
aboot (multi-boot loader), and fastboot are applications that run on littlekernel.
https://source.codeaurora.org/quic/l...tree/app/aboot -- note that "lk" == "littlekernel".

[c117152]

From what I can tell, it's a microkernel with object abstractions that's compiled against musl and uses the ChromeOS userland.
It was probably approved when Google saw how trivially Microsoft implemented the linux syscalls and managed to run so much of ubuntu in such a short amount of time.