zombah has quit [Quit: Leaving]
issoeocio has joined #linux-exynos
issoeocio has quit [Ping timeout: 246 seconds]
afaerber__ has joined #linux-exynos
afaerber_ has quit [Ping timeout: 276 seconds]
gerf213dfs123 has joined #linux-exynos
gerf213dfs123 has quit [Client Quit]
amitk has joined #linux-exynos
dlan has quit [Ping timeout: 256 seconds]
zombah has joined #linux-exynos
afaerber__ is now known as afaerber
amitk has quit [Quit: leaving]
zombah has quit [Quit: Leaving]
liquidAcid has joined #linux-exynos
liquidAcid has quit [Ping timeout: 250 seconds]
liquidAcid has joined #linux-exynos
<javier__> steev: I had some time to do a git bisect today and found that the offending commit is 965278dcb8ab ("ARM: 8356/1: mm: handle non-pmd-aligned end of RAM")
<javier__> steev: v4.1 + the mentioned commit reverted makes the Peach Pit/Pi to boot using a FIT image
<si1v3r> Did it make wifi work as a builtin?
<si1v3r> a fit image with modules sounds kinda silly.
<steev> javier__: oh wow, thanks - i'm sorry, i ended up getting my minnie early (i guess amazon screwed up and shipped some early) and i was playing with it all weekend
<javier__> si1v3r: we are talking about a completely unrelated issue
<steev> si1v3r: uh, a fit image is the kernel binary and dtb files
<javier__> si1v3r: the WiFi not working when built-in is related to how the in-kernel firmware loader works
<javier__> it tries to load the firmware before the rootfs is mounted, that fails and doesn't retry
<steev> damn it
<steev> javier__: happen to know how to make a "--depth=1" pull in the rest of history
<steev> that wasn't particularly clear - i cloned with --depth=1 initially i guess
<steev> wondering how to pull in previous history, but i'm trying a git pull --depth 30
<steev> it seems to be doing something
<javier__> steev: don't worry, I was courious. I'm not that familiar with the ARM MMU code though to understand what's going on
<Wizzup> git fetch
<Wizzup> ?
<steev> Wizzup: if it's depth 1 it doesn't update the old history, you have to pass it a new --depth
<javier__> I'll take a look to the patch tomorrow and see if I can report to the list
<javier__> steev: sorry, I don't get the question
<steev> huh, that's definitely interesting, i'm gonna mention it in #armlinux
<javier__> steev: cool, I gotta go now
<javier__> bye!
<steev> have fun! thanks for the update!
<javier__> steev: you are welcome
<steev> Wizzup: i'mma test with javier__'s claimed fix
<Wizzup> :L)
<Wizzup> :)
liquidAcid has quit [Quit: Leaving]
prahal has joined #linux-exynos
prahal has quit [Remote host closed the connection]
prahal has joined #linux-exynos
mturquette has joined #linux-exynos
D1337d has joined #linux-exynos
zombah has joined #linux-exynos
<steev> javier__: confirmed, reverted 965278dcb8ab here, built image and peach_pi boots and so far all i've tested works
<javier__> steev: yep, I'll look tomorrow at the patch and try to figure out what is doing differently mainline u-boot than the stock RO u-boot
<steev> javier__: i thought peach used coreboot, no?
<javier__> steev: no, it uses u-boot as its RO bootloader
<javier__> steev: there is a coreboot + depthcharge port for Snow and Peach Pit/Pi but it was not finished / stable enough to ship it
<steev> ahh
<steev> it would definitely be nice to have them, but yeah, it would be nice to know why that commit breaks things
<javier__> yeah, althought I thought the MMU was enabled by the kernel after is decompressed so I don't understand why is working with mainline u-boot but no with the stock one
<javier__> anyway, I'll try to look at it and try to answer Mark Rutland's patch thread with a sensible report
<javier__> since is something that has be handled during the v4.1 -rc cycle because is a regression
<javier__> I'll also ask sjoerd tomorrow who has a better understanding than me about the u-boot and kernel interactions and how the MMU is setup
<steev> ah
<steev> good idea, and yeah, not sure how that was missed
<steev> aside from people not using vendor supplied :)