<javier__>
Wizzup: glad that it worked, wifi is disabled since was reported to hang the kernel. I didn't look at it yet but first wanted to try it on linux-next
<javier__>
swabbles: they don't have to necessarily match and in fact some platforms requires them to be different (don't know what's the case on exynos5 though)
<javier__>
swabbles: loadaddr is the address where you load the uImage while the address specified in mkimage is the address where the bootm command will copy the zImage without the 64 byte u-boot header
<javier__>
Wizzup: about fbturbo DDX, AFAIK it uses the Unified Memory Provider (UMP) driver which is not available on that kernel
<javier__>
Wizzup: since *I think* the mali code drop in that kernel uses dma-buf instead
<javier__>
Wizzup: but don't tbh, as I said before I'm very ignorant about graphics...
afaerber__ has joined #linux-exynos
<swabbles>
javier__: ah, thanks for clearing that up.
afaerber_ has quit [Ping timeout: 250 seconds]
liquidAcid has joined #linux-exynos
<Wizzup>
swabbles: basically, I fill in name/email. And then it gives me an error. Sec.
<Wizzup>
(Emerging firefox 30 atm)
liquidAcid has quit [Quit: Leaving]
Wizzup has quit [Ping timeout: 240 seconds]
Wizzup has joined #linux-exynos
<chrs_>
how do you guys know so much about the boot scheme of these devices?
<Wizzup>
spending hours and hours trying
<Wizzup>
reading source code
<Wizzup>
failure after failure :)
ukki_ is now known as ukki
<javier__>
chrs_: most things are also very well documented on chromiumos.org wiki
<swabbles>
And the building instructions for U-Boot Peach Pi(t) have been derived from ebuilds in overlays/chromiumos-overlay, from a Python script in platform/dev-util and third_party/u-boot.