Thanks for the info William. Great work, as usual. =)
Regarding the loading an initrd, that is high on my priority list to solve. It might be a problem with the kernel, or u-boot... too early to say for sure.
Might be unrelated, but I think this is similar to what we are seeing with omap4. The 3.11 kernel is happy with 'bootm kernel - fdt', but sad with 'bootm kernel initrd fdt'. Could be a coincidence.
-Jon Disnard irc: masta fas: parasense
On Tue, Sep 3, 2013 at 8:38 AM, William Cohen wcohen@redhat.com wrote:
On 09/03/2013 09:18 AM, Darryl L. Pierce wrote:
On Thu, Aug 22, 2013 at 10:58:23PM -0400, William Cohen wrote:
I have moved to running the vanilla mainline linux-3.11-rcN kernel on my Samsung Chromebook. There are some notes on the steps that I used to get it running at:
http://people.redhat.com/wcohen/chromebook/booting-3.11kernel.txt
The config file is a bit different than the fc20 kernel configuration. I started from the "make exynos_defconfig" and working towards something that is closer to the fc20 configuration. There are a couple drawbacks with this configuration. The usb3 and wireless are not working in the configuration. Also cool things like KVM virtualization are not working.
How about sound?
Hi Daryl
This kernel is not for general use. This information is more to help developers avoid the issues that I encountered when building a mainstream kernel to try performance tools on. There are a number of things not working with this kernel configuration/build:
-usb3 -sound -wireless
Right now the nv-uboot being used doesn't really allow for an initramfs, so a number of things that should be modules are being compiled into the kernel so that the machine boots up. I am hoping that in the near future there will be a nv-uboot that is closer to what fedora expects (allows ext4 and initramfs).
-Will