<lancelot>
Trying to get video output from ODROID-U3 with kernel 3.19-rc1
<Wizzup>
also check the irclogs of last week (in topic), some people discussed hdmi
<lancelot>
AOK, thanks
amitk has joined #linux-exynos
D1337d has quit [Ping timeout: 264 seconds]
D1337d has joined #linux-exynos
dlezcano has quit [Ping timeout: 265 seconds]
dlezcano has joined #linux-exynos
<javier__>
lancelot: HDMI is not working for Exynos in mainline
<javier__>
lancelot: I've it working on my wip/exynos/dp-integ but using some hacks cherry-picked from the exynos-reference tree from Samsung and doing some reverts
<javier__>
lancelot: enabling IOMMU makes it work with those patches but I'm not sure if the problem is that the exynos drm hdmi driver does not work without iommu or enabling iommu has the side effect to turn on the needed power domains
<sjoerd>
javier__: did you see Joonyoung's last mail
<javier__>
sjoerd: not yet, I just started and going through my email
* javier__
reads
<javier__>
sjoerd: interesting, so he forced the DISP1 power domain to be turned on on the HDMI and mixer drivers since the kernel does not know about those after commit
<javier__>
d51cad7df871 ARM: dts: remove display power domain for exynos5420
<javier__>
so it seems to be a PD issue after all and is not that the driver can't cope with no IOMMU support
<javier__>
sjoerd: I'll ask him for the patch he has been using to enable the DISP1 power domain in the drivers
<sjoerd>
nod
<javier__>
sjoerd: what is strange that I tried reverting "ARM: dts: remove display power domain for exynos5420" and booting with pd_ignore_unused but I still get the stripes
* javier__
is unsure how the power domain subsystem really works
<sjoerd>
He does mention that configuring that pd is weird
dlezcano has quit [Ping timeout: 245 seconds]
<sjoerd>
also he might be looking at a different pd then the one tweaked with that patch?
* sjoerd
wonders if pd's shouldn't ahve a an always-on property
<javier__>
sjoerd: no, I compared the reg starting address of the removed dev node in that patch (0x100440C0) and is base 0x10000000 + offset 0x440C0 which is the starting of the CMU_CLKSTOP_DISP1_* registers according to the manual
<javier__>
sjoerd: table on page 716
afaerber_ has quit [Quit: Verlassend]
<javier__>
sjoerd: I also wonder if the PD should have an always-on property...
dlezcano has joined #linux-exynos
afaerber has joined #linux-exynos
libv has quit [Remote host closed the connection]
libv has joined #linux-exynos
<lancelot>
Thanks - # CONFIG_DRM_EXYNOS_IOMMU is not set
amitk is now known as fabo3
fabo3 is now known as amitk
dlezcano_ has joined #linux-exynos
dlezcano_ has quit [Remote host closed the connection]
dlezcano has quit [Ping timeout: 256 seconds]
dlezcano has joined #linux-exynos
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
<lancelot>
I tried with CONFIG_DRM_EXYNOS_IOMMU=y and CONFIG_EXYNOS_IOMMU_DEBUG=y ... still the same. I saw patches mentioned, where can I get them?
liquidAcid has joined #linux-exynos
afaerber has quit [Quit: Verlassend]
amitk has quit [Quit: leaving]
WarheadsSE has quit [Quit: WeeChat 1.0.1]
WarheadsSE has joined #linux-exynos
WarheadsSE has quit [Remote host closed the connection]
WarheadsSE has joined #linux-exynos
WarheadsSE has quit [Read error: Connection reset by peer]
WarheadsSE has joined #linux-exynos
Tenkawa has joined #linux-exynos
<Tenkawa>
hi all
<Tenkawa>
anyone know off hand the most recent working kernel for the xe303 first gen chromebook?
<Tenkawa>
I dont need X and can use usb wireless if needed.. I just would really like something newer than 3.8.11
<Wizzup>
There are several different kernels, but by most recent you mean mainline, then something like that
<Wizzup>
wifi is stilla bit iffy iirc
<Tenkawa>
oh?
<Tenkawa>
mainline has a working dt now?
<Tenkawa>
I seem to remember that was preventing it in the past
<Tenkawa>
I'd be happy to experiment with newer kernels if they work now
<Tenkawa>
got any pointers to articles/pages?
<Wizzup>
I still have to write the guide for snow, but some people here have it working
<Wizzup>
I don't think anyone updated the wiki pages on it yet.
<Tenkawa>
oh darn
<Tenkawa>
now that I know its being worked on I'm really jazzed now
<Tenkawa>
I use this machine as my primary laptop\
<Tenkawa>
great little box
<Tenkawa>
the cb2 was meh to me
* Tenkawa
reads the webpage
<Tenkawa>
s
D1337d has quit [Ping timeout: 264 seconds]
<Tenkawa>
trying to compile the kernel in git now
<Wizzup>
Tenkawa: me too, although I switched from snow to peach-pi
<Tenkawa>
difference? (behihd a bit)
<Tenkawa>
er behind
<Tenkawa>
I'm just excited I might be able to finally use this
<Wizzup>
peach-pi is octa core (or quad), with fullhd
<D1337d>
instructions should be identical for teh snow as well with a dtb change
<Wizzup>
cool!
<Wizzup>
ANd the u-boot you're using is the one documented on the wiki?
<D1337d>
yes
<Wizzup>
cool
<D1337d>
i may attempt a mainline uboot in teh comming weeks
* Wizzup
likes content
<D1337d>
if i pull that one off i will write up another page
<Wizzup>
I'll probably try to organise a bit more next week :)
<D1337d>
and update teh original one
<Wizzup>
nice
* D1337d
suspects a high level 'what you want to be doing and why' page may be of use
<D1337d>
as the problem i found when bootstrapping the snow when it came out and notw the chromebook 2 is you find a lot f instructiosn that tell you what to do
<D1337d>
but not why
Tenkawa has joined #linux-exynos
<Tenkawa>
hmm
<Tenkawa>
complained about a missing initrd
<Tenkawa>
everything else seemed ok
<Tenkawa>
do I even need the initrd?
<Tenkawa>
or is that the uimage>
<Tenkawa>
brain cramp night
<Wizzup>
what complained exactly?
<Wizzup>
and how
<Tenkawa>
missing initrd
<Tenkawa>
should I even have one
<Tenkawa>
?
<Tenkawa>
/initrd not found
<Tenkawa>
its in the example
<Tenkawa>
let me try to remove it
<Tenkawa>
all the rest of the files loaed up
<Tenkawa>
I hate that I didnt bring my other box with me
<Tenkawa>
brb.. yet anothe r try
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<Tenkawa>
appears my load alignment addresses are wrong
<Tenkawa>
I really need a proper boot.scr
<Tenkawa>
do you use a env.txt or "just" a boot.scr?
<Tenkawa>
maybe I'm making it too complicated
<liquidAcid>
depends on u-boot
<Tenkawa>
I'm just using the stock nv-uboot from the wiki
<liquidAcid>
don't know that one
<liquidAcid>
just check the uboot env
<Tenkawa>
I'm making it way too complicated
<Tenkawa>
however it keeps referncing initrd
<Tenkawa>
which confuses me
<liquidAcid>
it probably doesn't read any of the scripts