<springchromebook>
hola, looking for any tips getting a mainline kernel to drive the displayport interface on a hp chromebook 11
<springchromebook>
kernel (3.19.7) boots but with a black screen
<springchromebook>
if I use the .config from the chromebook, system locks up on boot, exynos_defconfig boots with no video
<springchromebook>
I found some reference to a bug with the DRM IOMMU (sorry, no link handy), enabling that does indeed reproduce a lockup at boot with 3.19.7 and the exynos_defconfig, but disabling that option with the chromeos .config does not prevent it from locking up at boot
<Wizzup>
hiya
<Wizzup>
start with linux v4.1-rc2
<springchromebook>
ok, I did try 4.0 also
<Wizzup>
from v4.1-rc2 display worked out of the box for me on snow
<Wizzup>
and the hw is quite similar I think.
<springchromebook>
I think the bug I mentioned was for 4.0, which is why i tried 3.19.7
<springchromebook>
Wizzup: is that with the simple fb
<Wizzup>
no.
<Wizzup>
I disabled simplefb
<springchromebook>
nice, ok i will try that kernel
<Wizzup>
actually, almost everythibf works in v4.1-rc2
<Wizzup>
liquidAcid: well, that *may* explain it for peach actually
<Wizzup>
Although I do not know the details - the audio was way too fast
<Wizzup>
(guessing what changing it to 'burst' would do)
prahal has joined #linux-exynos
<Wizzup>
I guess I can try later -- not today though
<springchromebook>
Wizzup: ok, thanks for the tip. will give this a shot.
<Wizzup>
let me know - and please update the wiki if it does work ;)
<springchromebook>
should I use the exynos_defconfig or the chromeos one?
<Wizzup>
ehm
<Wizzup>
exynos_defconfig
<Wizzup>
mainline has no chromeos config I presume?
<Wizzup>
or does it?
<springchromebook>
there is some options for the chrome ec driver iirc
<Wizzup>
just exynos_defconfig
<Wizzup>
I only add a few things (dm_crypt compiled in instead of module) and disable simplefb
<Wizzup>
but I don't think you actually need to disable simplefb anymore
prahal has quit [Ping timeout: 240 seconds]
prahal has joined #linux-exynos
prahal has quit [Quit: prahal]
prahal has joined #linux-exynos
prahal has quit [Quit: prahal]
liquidAcid has quit [Quit: Leaving]
<springchromebook>
Wizzup: I didnt disable simplefb, locks up on boot - will try disabling it
<springchromebook>
nope, still locks up... :(, hmm
<springchromebook>
I guess I
<springchromebook>
(oops) will try the chromeos config
<springchromebook>
interestingly 4.1-rc2 has a new driver for the displayport-lvds chip that is used on this device... sounds plausible that it might be useful
<springchromebook>
bah, this locks up too
<springchromebook>
ok, I am giving up on this and buying an x86 system i guess
<springchromebook>
thanks for help, sorry it didnt work out
<Wizzup>
you give up quite fast :)
<Wizzup>
we've been at this for over a year
<Wizzup>
there's other people with a spring machine too
<Wizzup>
there are*
<Wizzup>
have some patience :)
springchromebook has quit [Ping timeout: 246 seconds]
<Wizzup>
guess not
afaerber_ has joined #linux-exynos
afaerber has quit [Ping timeout: 276 seconds]
* si1v3r
checks ebay for a cheap spring
<si1v3r>
I think there's a perception issue. "Linux was hacked to run on x" is not the same as "linux supports x".
<si1v3r>
or even, vendor support is not the same as mainline support.
leowt has joined #linux-exynos
<leowt>
today i started digging a little on the dts files from odroid, copied them and started removing things that nanopc-t1 doesnt have, or in other gpio
<leowt>
javier__ i have found out that nanopc-t1 doesnt have the max regulator that odroid has
<leowt>
i also found the schematic for the board, and there is no max regulator
<leowt>
so, the componentes use the power references from 4412 directly?
<leowt>
why is odroid using the max regulator?
<sjoerd>
leowt: which of the various odroid boards
<leowt>
it is on the odroid-common, so i suppose every one