zombah has quit [Quit: Leaving]
dlan has quit [Ping timeout: 256 seconds]
dlan has joined #linux-exynos
amitk has joined #linux-exynos
Gottox has joined #linux-exynos
<Gottox> Hi! I'm currently trying to compile
<Gottox> u-boot for my chromebook
<Gottox> *samsung chromebook
<Gottox> is the vanilla u-boot enough for that?
<Wizzup> hi
<Wizzup> yes, recent u-boot should work fine
<Gottox> thx. trying to reproduce the nv-u-boot from source without the whole chromiumos tree.
<Gottox> can I find the u-boot configs used for those images somewhere? http://linux-exynos.org/dist/chromebook/nv_uboot/
<Wizzup> there's just a defconfig for that
<Wizzup> sec
<Wizzup> let me clone the repo
<Wizzup> what chromebook do you have btw
<Gottox> xe303c12
<Wizzup> so snow
<Wizzup> ack
<Wizzup> ./u-boot/configs/snow_defconfig ?
<Gottox> ah, I tried smdk5250 for now.
<Wizzup> make snow_config
<Gottox> thx, lets see.
* Wizzup is going through old wiki pages
<Wizzup> Swabbles: guess we should remove http://linux-exynos.org/wiki/User:Swabbles/Snow_Adventures ?
<Wizzup> Gottox: presumably you've seen http://linux-exynos.org/wiki/Samsung_Chromebook_XE303C12 ?
<Gottox> yea, saw that mainline was supported but overlooked the defconfig :D
<Wizzup> I just added that.
<Wizzup> (thanks to your feedback)
<Wizzup> we have generic (poor) guides for mainline kernel and u-boot building that need love
<Gottox> ah that's why I haven't foudn it :)
<Wizzup> if you want I can give you a wiki account
<Gottox> sure, but I can't promise anything.
<Wizzup> of course
<Wizzup> pm me username/email for the acc
<Wizzup> brb
<Wizzup> Gottox: you may want to check 'partitioning' on http://linux-exynos.org/wiki/ARM_Chromebook/nv_u-boot
<Wizzup> and then dd u-boot-dtb.bin to the first partition
<Wizzup> at least, I don't think vbutil is needed
<sjoerd> vbutil is needed
<sjoerd> you need to sign it just like you do a kernel fit image
<Wizzup> right
<Wizzup> should reflect that in our u-boot guide
* sjoerd still has a todo to add u-boot patches to do that when building for a chromebook
<sjoerd> so little time
<Wizzup> oh, it is in the normal one
<Wizzup> s/one/page/
<Wizzup> sjoerd: patches to what? u-boot?
<sjoerd> yes
<sjoerd> As doing this by hand is tedious, i'd prefer the build system to just give me a .kpart or whatever that i can put in place :)
<sjoerd> Especially when doing it for the nyans which need extra special care thusfar
<Wizzup> ack
<Wizzup> yeah, I also feel the mkimage step can be annoying
<Wizzup> since then you need to know what the loadaddr for the specific device is as well
<Wizzup> but perhaps that is already found somewhere in u-boot (doc?)
<sjoerd> They match the u-boot load addresses for the respective boards
<sjoerd> U-boot configuration tells u-boot where it expects to be loaded, so you need to have the mkimage match
<Wizzup> right, would be nice if the u-boot process would just do that ... :)
<Wizzup> the u-boot build process*
<sjoerd> nod
<sjoerd> it's jsut a matter of writing some code
<javier__> sjoerd: that would be great indeed
<Wizzup> si1v3r: what is this page for? http://linux-exynos.org/wiki/Peach_pit
zombah has joined #linux-exynos
jnettlet has joined #linux-exynos
<Gottox> how do I generate a key for u-boot?
<Wizzup> get vboot-utils
<Gottox> it's already there
<Wizzup> then you should have keys
<Gottox> unfortunately not, as I had to build vboot-utils by myself.
<Wizzup> see tests/devkeys/
<Gottox> ah, thx.
si1v3r has quit [Ping timeout: 256 seconds]
si1v3r has joined #linux-exynos
<si1v3r> Wizzup: that page was probably a wiki editing mistake, if i remember right.
<Wizzup> perhaps we should hide/remove it
<si1v3r> probably.
<si1v3r> its the arm template based one right?
<Wizzup> we need to fix the templates (as an aside)
<si1v3r> I think a 'state of the kernel' breakdown of features and when they started working would be very useful
<Wizzup> I have something like that per device
<Wizzup> well, yeah
<Wizzup> ok, I don't have that really
<si1v3r> It's all scattered around
<Gottox> yay, u-boot is booting! :D
<si1v3r> yay!
<Gottox> I'd like to have some docs about how the signed uboot finds the right partition. Is it only done through gpt or can I use msdos too?
<si1v3r> It must be gpt
<Gottox> okay.
<si1v3r> it looks for a partition with a cros kernel part type, and a bootable flag.
<si1v3r> and a clear failure flag, I believe.
<si1v3r> I stick nv uboot in a partiton and give it those flags to get my boot process working.
<Gottox> but it can't fatload I guess.
<si1v3r> fatload works fine
<si1v3r> by default it picks up a file from mmc0:12/u-boot
<si1v3r> uboot being the folder the scripts live in.
<Wizzup> si1v3r: I do the same @ partition
<Gottox> ah, nice.
amitk has quit [Quit: leaving]
<si1v3r> I set up my partitions with that script.
liquidAcid has joined #linux-exynos
<javier__> Gottox: the RO u-boot can only boot a signed image from a gpt partition
<javier__> that is a RAW image on a partition and the partition that chooses to boot depends on the GPT table priority (P) and successful (S) attributes
<javier__> Gottox: it tries to boot the GTP partition that has the highest priority a number of times as specified in the GTP partition tries (T) attribute
<javier__> but once the signed nv-u-boot image is loaded, then you can use fatload or whatever you want to load kernel, just like any other u-boot
<javier__> si1v3r: the tries flag is only used if the successful boot flag is 0 so there is no need to set -T 5 in your script since you are already setting -S 1
<si1v3r> That's good to know, thanks.
<Gottox> javier__: Yea, I'm currently tinkering with u-boot to boot a kernel.
<Wizzup> shouldn't be too hard
<Wizzup> basically ext2load mmc 0:@ (or 1:2) ${loadaddr} /file
<Wizzup> basically ext2load mmc 0:2 (or 1:2) ${loadaddr} /file
<si1v3r> It's not compatible with the defaults but it works.
<Wizzup> si1v3r: that is not snow though
<Wizzup> I think?
<si1v3r> They are the same
<Wizzup> so the loadaddr may be different?
<si1v3r> (here)
<Wizzup> ok.
<si1v3r> afaik, any loadaddr around 0x41000000 - 0x40008000 works
<Wizzup> ack
<Wizzup> yeah I use 0x400....
liquidAcid has quit [Quit: Leaving]