W dniu 09.01.2014 21:15, Held Bier pisze: >> one cannot boot from a stock linux kernel > > One can, but Samsung ARM Chromebook is not fully supported by mainline > kernel. At least you'll miss wi-fi.
Wi-Fi, USB3, Audio and some other stuff probably too. But you get working virtualisation with proper U-Boot. >> One currently must "borrow" the ChromeOS kernel > > It's the kernel with best support for this machine. If you're trying > to avoid using Google's blobs, you may take the tree code from > https://chromium.googlesource.com/ instead > (chromiumos/third_party/kernel -b release-R31-4731.B is what stable > Chrome OS uses atm) instead, which you're free to investigate prior > usage (an old building guide > http://people.redhat.com/wcohen/chromebook/chrome_kernel.txt is mostly > right). > You'll still need few proprietary components to get full hw support: > 1) Mali GPU userland driver; OpenGL ES support > 2) Wi-Fi firmware; Part of linux-firmware package in all major distributions as it is freely redistributable. > 3) HW videocodec firmware (highly optional). Did someone got it working? >> The Debian folks are currently stuck on how to boot a stock linux kernel >> from nv-u-boot > > I doubt they're stuck. The wiki way is just the most easy and fast. I > had no problems in booting Linux from nv-u-boot, and there is nothing > distro-special about it. For Google's nv-u-boot you're just making a > combined image of exynos5250 device tree and your kernel in form of > zImage, and then booting it. There are nv-u-boot images which boot Linux kernel with separate DTB. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
