<steev>
javier__: at some point could you go through the exynos_defconfig and fix it so.... it actually just works, like people claim it does? it seems that it just works but only if you have some kernel config that apparently i don't have
<steev>
javier__: or better, a list of "this must be on for everything to work" - we're kinda working on a script to make sure all the various options are on
amitk has joined #linux-exynos
D1337d has quit [Quit: leaving]
<Wizzup>
steev: we could do that too
<steev>
Wizzup: well i don't see anything *exynos* from your config that isn't in the defconfig, so i dunno
<steev>
maybe it's because i'm not using an nvuboot, i'm just doing a kpart
<Wizzup>
it is possible I disabled some things
<Wizzup>
I use nv-uboot, yeah
<Wizzup>
bbiab.
<steev>
i don't because i'd like these to be fairly generic, instead of having to do an image for peach pi, and image for peach pit, an image for snow, an image for spring
<Wizzup>
I have exactly that
<Wizzup>
I just mkimage for zImage + dts for various machines
<Wizzup>
And that "just works"
<Wizzup>
(at least last time I did that, around 4.0-rcsomething)
<steev>
uh, how? considering u-boot for spring and snow requires separate display issues
<steev>
i'm cloning linux-stable's linux-4.1.y branch and will compare the output of exynos_defconfig's .config to yours
<steev>
Strongly-Ordered/Device load or NC LDREX could return incorrect data, incorrect instructions may be executed from loop buffer, Large data RAM latencies can lead to rare data corruption
<steev>
javier__: pretty much yes, but i use root=PARTUUID=%U/PARTNROFF=1
<javier__>
Doug just says in the bug you shared that "Perhaps this could explain some of the completely random crashes that we have always seen"
<steev>
right
<steev>
i read through the bug, i'm just passing along the information, ojn would know way more than i would... i've only ever committed stuff to chromiumos as an outsider
<steev>
though it was ~2 years ago that it was enabled, so he may not remember
<javier__>
yeah, my point is. If we have a real bug report and a confirmation that an errata fix it, then I want to enable
<javier__>
otherwise I prefer to leave them disabled
<steev>
oh i'm not saying to enable them, i'm just saying that's what chromeos did, and is possibly why Wizzup enabled it
<javier__>
steev: yes, I was referring to Wizzup indeed and not you :)
<steev>
oh haha
bgamari- has joined #linux-exynos
<javier__>
steev: I've some urgent things to finish for work but after that I'll build a v4.1 fit image and test it on my peach pi and pit
<steev>
cool
<steev>
no rush on it, it's almost bedtime here
<javier__>
steev: ok, I'll let you know how it goes. I'll be quite surprised if FIT is not working since I tried some time ago (v4.0 iirc)
<steev>
yeah, i'm just waiting on my latest build to write to SDcard and then i'll test it
<steev>
it's sorta based off wizzup's config
<steev>
that said, flipping through his changes, i really can't see anything that sticks out as "oh yeah, that's why it's not working"
<javier__>
steev: yeah, me neither
<steev>
i just know that i get backlight on, and no tty
<steev>
and since it's a fresh image... no network