Re: booting the samsung chromeboot xe303c12 with the debian armmp kernel
On 12 November 2014 07:07, Ian Campbell <ijc@hellion.org.uk> wrote:
> On Tue, 2014-11-11 at 18:14 -0200, Pedro Bulach wrote:
>> Is this config/kernel supposed to work on this hw?
>
> I tested on arndale when I added the Exynos support to the kernel, I
> don't know how different an xe303c12 is from that or what platforms
> other folks have tested.
Based on [1] it seems that the current 3.16 kernel can be made to work
on this hw. My goal here would be to use the debian kernel, as opposed
to building a custom kernel.
[1] http://linux-exynos.org/wiki/ARM_Chromebook/Mainline_Linux_kernel
>
> At the very least I'd expect the basics like the console to work, at
> which point it should be easier to figure out what other stuff is
> missing.
>
> I know nothing about how boot on a chromebook is organised, but from
> David's response it sounds like your u-boot arrangements are not yet
> quite right?
That may be true. I will investigate further.
>
>> Where can I find flash-kernel docs to configure it correctly to
>> automate this process? (supposing I will make this work)
>
> The flash-kernel source and package contain a README which lists the
> various fields which can be used in a db entry. If the system boot
> arrangements differ wildly from the small number of cases which
> flash-kernel currently supports then you will probably need to dig into
> the source to add a new one. Hopefully the existing "generic" method
> will work for you -- the others are a bit specialised.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716902 might be
> relevant here (is xe303c12 == Snow?)
Yes, that is snow. I have tried to configure flash-kernel following
tips from this bug report.
If I can manually load the debian kernel, the goal is to use
flash-kernel to automate the generation of the u-boot images from the
debian kernel and initramfs.
Thanks for the input.
Pedro
>
> Ian.
>
Reply to: