And you only had seven years of warning! Despicable.
Being on version 5 is already good, Android 12 is still on a 4.14 kernel. ;D
Is it written in my-c?No, you can currently only use C in the Linux kernel, although Rust support is being introduced. :P
Is it written in my-c?
Is it written in my-c?No, you can currently only use C in the Linux kernel, although Rust support is being introduced. :P
Is it written in my-c?No, you can currently only use C in the Linux kernel, although Rust support is being introduced. :P
(Kidding aside, I'm not sure DiTBho was really considering getting his contributions accepted in the Linux kernel, although, who knows... Otherwise, you can well do as you please. At least I hope so. :-DD)I've suggested submitting the kernel patches in PMs. It costs nothing except a bit of time and a self-esteem/ego hit to post them on LKML (as it is likely nobody responds to the patch), and especially when one describes the use case, at least it will be recorded forever in the mailing list archives.
I've suggested submitting the kernel patches in PMs.
reg_usb_vbus: reg_usb_vbus
{
compatible = "regulator-fixed";
regulator-name = "usb_vbus";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
//gpio = <&gpio 12 GPIO_ACTIVE_HIGH>; <---- commented, handled by phy-en
enable-active-high;
regulator-boot-on;
regulator-always-on;
};
That's quite new compared to many embedded devices. Pretty sure some vendors are still shipping SDKs and binary drivers for 2.6.
2.6.2x is the forever kernel. There are essentially two versions of Linux that you need to deal with, $latest_release and 2.6.2x.
That's quite new compared to many embedded devices. Pretty sure some vendors are still shipping SDKs and binary drivers for 2.6.
2.6.2x is the forever kernel. There are essentially two versions of Linux that you need to deal with, $latest_release and 2.6.2x.
...is this why there are as many versions of Linux as grains of sand in a bucket?No, that is unrelated. This is a bad design issue.