libv has quit [Read error: Connection reset by peer]
libv has joined #linux-exynos
libv has quit [Ping timeout: 264 seconds]
libv has joined #linux-exynos
libv has quit [Ping timeout: 264 seconds]
_anomaly_ has joined #linux-exynos
Mahdi91 has joined #linux-exynos
Mahdi91 has quit [Client Quit]
prahal has joined #linux-exynos
indy has quit [Ping timeout: 250 seconds]
pekka30 has quit [Ping timeout: 272 seconds]
pekka30 has joined #linux-exynos
libv has joined #linux-exynos
indy has joined #linux-exynos
<Wizzup_>
SJRvanSchaik: What was the fix again for when fbset -i shows (nil) for the addr?
<Wizzup_>
hang on
<Wizzup_>
something else is probably wrong
D1337d has quit [Ping timeout: 272 seconds]
zombah has joined #linux-exynos
D1337d has joined #linux-exynos
dlan has quit [Ping timeout: 276 seconds]
dlan has joined #linux-exynos
afaerber has quit [Ping timeout: 240 seconds]
<Wizzup_>
[indeed[
<Wizzup_>
]
afaerber has joined #linux-exynos
leowt has joined #linux-exynos
jrmy__ has joined #linux-exynos
ssvb has quit [Ping timeout: 246 seconds]
<jrmy__>
Hi all, is there a simple solution to make the screen working on chromebook snow, with a mainline kernel?
<jrmy__>
With v4.1-rc2 + exynos_defconfig I get a white screen.
<javier__>
jrmy__: are you using a nv-uboot with simplefb support?
<jrmy__>
Yes
<javier__>
jrmy__: that's not going to work since now snow has a proper drm/kms driver and there isn't a way to do a handoff between simplefb and exynos drm
<javier__>
jrmy__: so you need to disable CONFIG_FB_SIMPLE
<javier__>
or use a nv-uboot that doesn't add the simplefb dev node in the FDT
<jrmy__>
Ok I'll try. Thanks.
<javier__>
yw
<Wizzup_>
jrmy__: it works for me on mainline
<Wizzup_>
But indeed, with FB_SIMPLE disabled
<Wizzup_>
Now that I can finally test (fixed the btrfs issues with the devs) I will document snow more
<Wizzup_>
Pretty much everything seems to work on v4.1-rc2, except for sound + suspend (due to wifi perhaps)
<Wizzup_>
javier__: actually, I wanted to ask you about sound
<Wizzup_>
I see alsa, and on peach-pi, it produces some sound, but it's not quite correct
<Wizzup_>
but I guess that is known?
<jrmy__>
I confirm, it works for me with FB_SIMPLE disabled.
<javier__>
Wizzup_: yes, it was working for me when I tested but it seems to depend on setup made by the boot-loader
<javier__>
so there is something missing in the kernel, I've to look at it
<Wizzup_>
javier__: I see; I'm using mainline u-boot
<javier__>
Wizzup_: S2R should work on Snow, I had issues on Peach Pi due the mwifiex driver preventing to suspend if keep-power-in-suspend was not defined in the DTS
<javier__>
exynos4 is very well supported now and even there are DTS for the 4412 based odroids that you can use as a reference
<leowt>
they have a eclipse dotfile with odroid-3.8 kernel
<leowt>
yes i know :/
<leowt>
but
<leowt>
what about dts?
<leowt>
i am very new in this
<javier__>
leowt: DTS = Device Tree source file
<javier__>
is a description of the hw topology
<javier__>
is used instead of the old board files that described the hw in C
<leowt>
yes i get that, but there isnt one for this board, being that, i have to do it
<leowt>
and i dont know where to start :)
<javier__>
right but you should have all the information in the board files and have the odroid as a reference
ssvb has joined #linux-exynos
<leowt>
i wanted to take this in small steps
<leowt>
so i can learn in the process
<javier__>
leowt: you can start with a minimal DTS that only gets you serial working
<javier__>
and start from there, then add mmc, usb, etc
<leowt>
i will compile a 4.0 kernel using a dts from odroid u3
<leowt>
since it is the closest board
<leowt>
then
<leowt>
=)
<javier__>
leowt: yeah, if the boards are really very similar that may work
<leowt>
is there any problems with uboot 2010-12 and dtb?
<javier__>
leowt: u-boot 2010-12 is a pretty old version but I don't know if there is a problem with dtb
<javier__>
is that the u-boot that is shipped on the device?
<javier__>
leowt: I would start appending the DTB then just to remove more variables from your equation
<leowt>
javier__ i only have a binary of uboot for this platform, they released a source for a similar one but it doesnt work since memory init and clock are different
<leowt>
yes
<leowt>
im am just compiling one
<leowt>
=)
<twitch153>
Has anyone got the linux 4.0.1 kernel loaded on the Odroid XU3? I'm running into a few snags myself while trying to get it to boot. From what I can see, HDMI isn't work for it. Can't diagnose much else, the UART isn't that helpful for me at the moment.
<javier__>
leowt: wonder how you got with CONFIG_FB_S3C enabled btw since that is not in exynos_defconfig
<leowt>
it was enabled on the platform original kernel
<javier__>
leowt: I see, then you are not using exynos_defconfig :)
<leowt>
i am, but i enabled it
<leowt>
:)
<javier__>
right, you don't need that for exynos4 since is a driver for the controller on older Samsung S3C SoCs
<leowt>
ook, rebuilding
amitk has quit [Quit: leaving]
<twitch153>
Seems with using exynos_defconfig it boots fully, but HDMI isn't enabled, ethernet doesn't work, and in my previous config when having HDMI enabled it didn't work.
<twitch153>
So I'll stick with not using 4.0.1 for now, I guess.
ssvb has quit [Quit: Leaving]
<leowt>
javier__ uboot is expecting ramdisk not dtb files :/
<bgamari>
afaerber, what is the status of the Odroid XU work?
<afaerber>
bgamari, patches still haven't been picked up - last weekend I rebased them onto the lastest kgene tree and they still applied without problems there