ssvb has quit [Ping timeout: 245 seconds]
ssvb has joined #linux-exynos
ssvb has quit [Quit: Leaving]
prahal has quit [Ping timeout: 250 seconds]
zombah has quit [Quit: Leaving]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> oops
<Tenkawa_> brb
Tenkawa_ has quit [Client Quit]
<Tenkawa> that was odd
<Tenkawa> time to see if I can figure out this video problem again
LanDi has joined #linux-exynos
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
<Tenkawa> hi all
<Tenkawa> this is definitely dts related I think
<Tenkawa> wish i knew what though
Tenkawa has quit [Quit: brb]
Tenkawa has joined #linux-exynos
<Tenkawa> definitely dts... got it to change from white to black
<Tenkawa> just need to get it + drm figured out now
si1v3r has joined #linux-exynos
<Tenkawa> hey si1v3r
_whitelogger has joined #linux-exynos
si1v3r has quit [Ping timeout: 245 seconds]
si1v3r has joined #linux-exynos
<si1v3r> Tenkawa: Hi. My new router has been screwy. heh
<Tenkawa> ouch
<Tenkawa> I'm trying to track down a dts/framebuffer annoyance
<si1v3r> Nah, I just forgot to copy over the leases table from my old one. Bunch of devices all popped up on the wrong IPs.
<Tenkawa> ahhhhh
<si1v3r> Protip: don't run a dns server on dhcp
<Tenkawa> heh.. yeah that can be painful
<Tenkawa> anyone got their /proc/cmdline handy from a snow chromebook? thanks
<si1v3r> I've got a peach
<si1v3r> cros_secure console=tty1 debug verbose root=/dev/mmcblk0p7 rootwait rw lsm.module_locking=0
<si1v3r> pit
<Tenkawa> yeah mine is fairly close
<Tenkawa> trying to see if disabling iommu will fix this video problem
<Tenkawa> this darn thing is picky
amitk_ has joined #linux-exynos
ssk has joined #linux-exynos
LanDi has quit [Quit: fui !]
ssvb has joined #linux-exynos
ssk has quit [Quit: Leaving]
<javier__> Tenkawa: what kernel version are you trying? 4.0-rc1?
<javier__> Tenkawa: ok, I built v4.0-rc1 and booted on Snow, as expected I got http://paste.debian.net/plain/159370 due exynos drm not working with iommu enabled
<javier__> Tenkawa: disabling iommu is a workaround but then I got this NULL pointer dereference error http://paste.debian.net/plain/159371
<javier__> Tenkawa: this patch tries to fix that https://lkml.org/lkml/2015/2/17/434 but even with that one I still don't get display working
<javier__> so yeah, exynos drm seems to not be working on 4.0-rc1 :(
<javier__> Tenkawa: I also noticed that the Snow DTS bits didn't make it in 4.0-rc1
<javier__> that is commit b174e79ef518 ("ARM: dts: represent bridge and panel connection for exynos5250-snow")
<sjoerd> javier__: did that one get included in the fixes pull request kujin did ?
<javier__> sjoerd: you mean the patch to disable iommu? he picked on his v4.0-samsung-defconfig
<javier__> I mentioned this morning that is -rc material since 4.0-rc1 boot is broken due that on most exynos5 boards
<sjoerd> javier__: no the dts bits
<javier__> *mentioned to kukjin
<javier__> sjoerd: I don't think so yet I don't know if that is technically a fix since display were not working anyways before 4.0-rc1
<sjoerd> right
<sjoerd> samsung-fixes-2 had a bunch of dts patches but i didn't look at the specifics
<javier__> sjoerd: yeah but display on Snow is not working even with today's linux-next...
<sjoerd> fair enough
<sjoerd> one day :)
<javier__> haha
zombah has joined #linux-exynos
gautam__ has joined #linux-exynos
ard has joined #linux-exynos
opuk has quit [Changing host]
opuk has joined #linux-exynos
ssk has joined #linux-exynos
prahal has joined #linux-exynos
prahal has quit [Ping timeout: 252 seconds]
ssk has quit [Ping timeout: 245 seconds]
prahal has joined #linux-exynos
ssk has joined #linux-exynos
ssk has quit [Quit: Leaving]
afaerber has quit [Ping timeout: 264 seconds]
afaerber has joined #linux-exynos
si1v3r has quit [Ping timeout: 250 seconds]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> hi all
<Wizzup> hi
<Tenkawa_> well the good news... 4.0.0-rc1 boots up with almost everything functional on exynos5250-snow
<Tenkawa_> problem.... the screen just turns white
<Tenkawa_> changing drm settings and dts changes its behaviour however nothing is makig text come up
<Tenkawa_> any thoughts?
<Tenkawa_> theres so many drm settings/combinations
<Tenkawa_> I thought simplefb should take care of it. is there something I'm missing to force fb0 to be console in my bootline?
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<afaerber> Tenkawa, to use simplefb, you need an nv-uboot with simplefb support and you need to disable anything in your .dts that loads the exynos drm, including possibly dp-controller, hdmi, panel nodes
<Tenkawa_> then I definitely had it running using dtb because my scripts still use mkimage and a dts
<Tenkawa_> so I have to be missing something simple
<afaerber> you sound confused. you need a .dtb either way
<Tenkawa_> afaerber: yes however it is possible to "not" use nv-uboot
<Tenkawa_> I dont want to add nv-uboot to the mix
<Tenkawa_> It was running fine up until a certain point
<Tenkawa_> and I lost my kernel
<afaerber> Tenkawa_, if you don't, then you can't use simplefb. you'll need to get the real exynos drm working
<Tenkawa_> afaerber: thats fine too... the conundrum is it activates and creates a white screen (everything else is functional)
<Tenkawa_> so I need to determine which drm setup the dts needs and/or which drivers in the kernel drm stack to adjust
<afaerber> welcome to the club :)
<Tenkawa_> heheheheh
<Tenkawa_> and drm and dts are both not my forte
<Tenkawa_> at least the rest of the box works (kb, wifi, etc).. just cant see it
<Tenkawa_> you know its going to be something monumentally simple in the end
<Tenkawa_> heheheh
<afaerber> probably ;)
<Tenkawa_> it always is haahaaa
<Tenkawa_> from what I can tell I think it is fimd related
<Tenkawa_> compiling another test
<Tenkawa_> got this part down to a science
Tenkawa_ has quit [Quit: reboot]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> bah no dice on that try
<Tenkawa_> still white background
<Tenkawa_> going to see what syslog says
<Tenkawa_> pwm-backlight probe keeps deferring
<Tenkawa_> it appears to use FIMD in 3.8
<Tenkawa_> fimd and displatpor
<Tenkawa_> er displayport
gautam__ has quit [Quit: Leaving]
<Tenkawa_> ok so fimd is definitely the display
<Tenkawa_> think I may have found it... was burried
* Tenkawa_ hopes
<Tenkawa_> FIMD was hard to get to select based on its dependencies
<Tenkawa_> brb
Tenkawa_ has quit [Quit: lets try that again]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> uggh
<Tenkawa_> this thing just doesnt like me
<Tenkawa_> just keeps requesting deferral
<javier__> Tenkawa_: is a regression in the exynos drm driver, I don't think is something trivial
<Tenkawa_> well crap
<Tenkawa_> why was it working a few code changes ago?
<Tenkawa_> I was really hoping to test 4.0-rc on here
<Tenkawa_> hold that thought.. need to reboot
Tenkawa_ has quit [Quit: leaving]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> guess I'll be waiting for a hopeful fix
<javier__> Tenkawa: it never really worked with mainline, what you were probably using was a 3.19 + the posed patches to add display support for snow
<Tenkawa_> OH
<Tenkawa_> those patches avail for 4 yet?
<Tenkawa_> (memory isnt what it use to be)
<Tenkawa_> javier__: you're probably right
<Tenkawa_> I seem to recall something like that
<Tenkawa_> I'm a dork
afaerber_ has joined #linux-exynos
<Tenkawa_> javier__: thank you for being patient with my misremembering
<Tenkawa_> I'd even use 3.10 with those patches if they are still out there
<Tenkawa_> I just lost my copy
afaerber has quit [Ping timeout: 244 seconds]
<javier__> Tenkawa_: no worries, everything already landed in linux-next but is not working. Padovan is looking at it so it should be working soon
afaerber_ has quit [Quit: Verlassend]
<Tenkawa_> ahh
<Tenkawa_> linux-next is what I'm tracking so thats good for me
<Tenkawa_> refresh my memory.. whats the best/appropriate way to get my git up to date with those changes without pulling the whole thing again
<Tenkawa_> er git repo
<javier__> $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git && git remote update linux-next
<Tenkawa_> ok thanks
<Tenkawa_> updating away....
<Tenkawa_> pulling rather
<Tenkawa_> I ws so use to svn
<Tenkawa_> having to learn git and forget all I know about svn, cvs, cvsup, etc
<Tenkawa_> javier__: no way to update it after a clone without a add/remote?
<Tenkawa_> I just want to pull changes.. not push any
<javier__> Tenkawa_: not sure I understood your question. Once you updated the remote you can checkout a new branch
<Tenkawa_> well right now I'm running the clone to pull the base
<Tenkawa_> do I need all the above just to keep that updated?'
<javier__> oh, now you just need git remote update then
<javier__> *no you just need
<Tenkawa_> ok cool
<Tenkawa_> thanks
<Tenkawa_> wow this repo is getting big
prahal has quit [Ping timeout: 264 seconds]
amitk_ has quit [Quit: leaving]
prahal has joined #linux-exynos
ssvb has quit [Ping timeout: 255 seconds]
Tenkawa_ has quit [Quit: leaving]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> javier__: almost there
<Tenkawa_> it initialized however no output
<Tenkawa_> checking logs now
<Tenkawa_> no white screen and and it did lines and stuff on startup
<Tenkawa_> javier__: the kernel messages look much more promising too
<Tenkawa_> actual drm/fb messages
<Tenkawa_> I think I need to change a setting to use it
<Tenkawa_> however I think it is initialized
<Tenkawa_> ah hhaa
<Tenkawa_> got an idea.. brb
Tenkawa_ has quit [Client Quit]
afaerber has joined #linux-exynos
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> oh i feel like I'm so close now
<Tenkawa_> javier__: it seems to initialize the panel fine
<Tenkawa_> just no output
<Tenkawa_> its almost like it doesnt get a device node on the tree
<Tenkawa_> the one thing I am seeing is GPIO errors with the panel
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 0.182878] [drm] Initialized drm 1.1.0 20060810
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 0.968009] exynos-drm exynos-drm: bound 14400000.fimd (ops fimd_component_ops)
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 0.969635] exynos-drm exynos-drm: bound 145b0000.dp-controller (ops exynos_dp_ops)
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 0.969654] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 0.969666] [drm] No driver support for vblank timestamp query.
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 1.224389] exynos-drm exynos-drm: fb0: frame buffer device
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 1.224434] exynos-drm exynos-drm: registered panic notifier
<Tenkawa_> Mar 3 11:56:11 arrakis kernel: [ 1.236881] [drm] Initialized exynos 1.0.0 20110530 on minor 0
<Tenkawa_> thats the drm output of the boot
<Tenkawa_> brb
Tenkawa_ has quit [Quit: leaving]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> javier__: fbset even sees the framebuffer
<Tenkawa_> sounds like a "mapping" issue
<Tenkawa_> at least it acts like one
<Tenkawa_> ugghgh
<Tenkawa_> so close.. if I only understood dt/dtc better
<Tenkawa_> brb.. trying something out there.....
Tenkawa_ has quit [Quit: leaving]
<daniels> Tenkawa: fimd is the element of the display controller which feeds the edp->lvds bridge which feeds the actual panel
<daniels> Tenkawa: if fimd is requesting deferral, then something fimd depends on isn't present
<daniels> Tenkawa: which can be clock/regulator (unlikely), gpio (equally unlikely), the bridge (not unlikely), or the panel (ditto)
afaerber has quit [Quit: Verlassend]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> bah I give up for now
<Tenkawa_> this thing does not like me
<Tenkawa_> javier__: could I use nv-boot on here with the 4.0-rc kernel?
<Tenkawa_> brb again...
Tenkawa_ has quit [Quit: leaving]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
prahal has quit [Ping timeout: 245 seconds]
Tenkawa_ has quit [Quit: leaving]
ssvb has joined #linux-exynos
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
zombah_ has joined #linux-exynos
Tenkawa_ has quit [Quit: leaving]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has joined #linux-exynos
<Tenkawa_> if any of you do get 4.0-rc working on a xe303c12 (snow) again let me know
<Tenkawa_> brb
<Tenkawa_> yet another reboot
Tenkawa_ has quit [Quit: leaving]
Tenkawa_ has joined #linux-exynos
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Client Quit]
mkatic has joined #linux-exynos
<mkatic> daniels: ping
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<daniels> mkatic: hi
<mkatic> greetings
<daniels> mkatic: how can i help?
<mkatic> a few weeks ago you were having a discussion with libv about his mali related article
<mkatic> you mentioned that you had working mali on mainline kernel?
<mkatic> i tried to get that going myself on linux-next
<mkatic> but i could use some pointer
<mkatic> *pointers
<daniels> mkatic: which platform? i only test on two platforms - peach-pi and odroid-xu3
<mkatic> snow
<daniels> ah ...
<Tenkawa_> I would just be happy with working display on mainline again for a chromebook 1 heehee
<Tenkawa_> (snow)
<daniels> Tenkawa has been trying to get the snow going as well
<Tenkawa_> yep
<Tenkawa_> getting close I think
<daniels> i haven't tried any platforms with a bridge chip (snow/peach-pit)
<Tenkawa_> the dt and bridge is beingh stubborn
<Tenkawa_> and I have a limited exposyre to dt
<Tenkawa_> so I'm learning it as I go
<daniels> we have those in our lava lab which will be added to kernelci.org quite soon, but those are in another city ...
<mkatic> well, i didn't get that far with mali driver
<daniels> mkatic: oh, right
<mkatic> i'm just not sure how to properly build this thing
<mkatic> i got the latest version
<mkatic> but the contents are kinda confusion
<mkatic> there's a single patch that should supposedly be applied to the kernel
<daniels> mkatic: i haven't pushed my current linux-next branch as i have some atomic modesetting stuff to finish first
<daniels> mkatic: but getting drivers/gpu/arm/ and drivers/base/kds/ from http://cgit.collabora.com/git/user/daniels/linux.git/log/?h=wip/3.18.x/exynos-odroid-wip would be a good start
* tyler-baker will test his chromebook 1 on mainline
<mkatic> the patch adds some kds handling to dma-buf
<daniels> mkatic: you'll also need that if you want to avoid tearing
<daniels> mkatic: since that branch was in the middle of atomic rework, i went for the alternate approach, of clocking the mali high enough that tearing wasn't visible :\
<mkatic> ok, i'll look into your tree, thank you
<mkatic> tenkawa: i'm running 3.19.0-next.2015022 on my snow
<mkatic> i have no problems with the display
<Tenkawa_> mkatic: yeah it broke recently
<Tenkawa_> it boots however lcd panel wont init
<Tenkawa_> flashes and does nothing
<Tenkawa_> keyboard/wifi/etc all work fine
<Tenkawa_> just cant see a darn thing
<mkatic> i did try 3.19.0-next.20150227 and that one got me a black display
<Tenkawa_> yep
<Tenkawa_> thats the prob
<Tenkawa_> 22 you said is working though?
<Tenkawa_> I'll pull it for now then
<Tenkawa_> I got to get away from 3.18
<mkatic> yes, i only have a minor change to get wifi going
<Tenkawa_> is that the next from kernel.org btw?
<mkatic> runs quite well for me, much more stable than chromeos 3.8 kernel
<Tenkawa_> yeah
<mkatic> yes
<Tenkawa_> cool thanks
<Tenkawa_> pulling now
<Tenkawa_> or at least about to
<mkatic> forgot to mention it, shutdown and suspend are broken
<Tenkawa_> yeah
<Tenkawa_> I found that out the hard way
<Tenkawa_> and thank you....
<Tenkawa_> now I have to remember how to get git to go to a specific rev
<mkatic> also, wizzupo pointed out that one should revert 68ff2a00dbf590dc9483c20f85fd1f1faa054604 to get wifi going on linux-next 20150222
<mkatic> daniels: How come chromebook mali platform layer doesn't come included with arm mali tarballs?
<Tenkawa_> ok.. i might have to ask how to do that later
<tyler-baker> arrg yeah my snow's panel isn't working on next-20150303
<Tenkawa_> tyler-baker: yup
<Tenkawa_> ]
<daniels> mkatic: the platform layer is meant to be supplied by whoever supplies the, well, platform
<daniels> mkatic: since it handles things like the exact register and clock details for power-on
<daniels> mkatic: over time i'd expect that to using devicetree to describe as much as possible, but pre-DT that just wasn't a thing
<mkatic> makes sense, thank you
<Tenkawa_> tyler-baker: I'm going to try backing up all the dts/dtb defs and migrate those to the newer source where its broke
<mkatic> i assume that most up to date version of the chromebook layer is the one the tree you posted here?
<tyler-baker> Tenkawa_, I just reported DRM exynos failures on next
<Tenkawa_> and see what that breaks in the process
<Tenkawa_> cool
<Tenkawa_> thank you
<tyler-baker> Tenkawa_, let me try to add the IOMMU option back
<Tenkawa_> iommu makes it really go weird
<Tenkawa_> for me anyway
<tyler-baker> well that was the case until today
<Tenkawa_> ahhhh
<tyler-baker> now we are seeing DRM related failures on the latest next on exynos instead of the IOMMU issue
<tyler-baker> Tenkawa_, have you found a kernel version that works 3.19+?
<Tenkawa_> tyler-baker: nope
<tyler-baker> ok
<tyler-baker> let me help run this down
<Tenkawa_> I'll be very happy to help test
<Tenkawa_> I was really enjoying the newer kernel on here until I had to rebuild the box (f2fs glitch)
<Tenkawa_> ok... lets see if I can checkout the right tag
<Tenkawa_> darnit
<Tenkawa_> only saved the 4 one.. got to go dload again
<Tenkawa_> isnt there a gitweb fo kernel.org?
<Tenkawa_> nm
<Tenkawa_> I was being goofy
<Tenkawa_> which node worked? 22nd right?
<Tenkawa_> scrollback is stuck
<mkatic> 20150222, correct
<Tenkawa_> excellent8
<mkatic> make sure you disable IOMMU
<Tenkawa_> going to set it up to build here in a sec
<Tenkawa_> ok
<mkatic> let me send you my .config
<Tenkawa_> I saved mine
<mkatic> just in cas
<mkatic> e
<Tenkawa_> ok
<Tenkawa_> thanks
<Tenkawa_> got it
<Tenkawa_> will i need the wifi patch too?
<Tenkawa_> if so how do I pull that one patch?
<Tenkawa_> this is where I really like ccache
<Tenkawa_> and when I get home.. 12 distcc cores
<Tenkawa_> compiling compiling compiling heehee
<Tenkawa_> fortunately I have my usb wifi too just in case
<mkatic> just revert commit 68ff2a00dbf590dc9483c20f85fd1f1faa054604
<mkatic> and enable userspace fw loader helper
<mkatic> hm
<mkatic> actually, i'm not sure if revert that commit is necessary if you enable the userspace fw loader helper
<mkatic> better ask wizzup
<Tenkawa_> ok
<Tenkawa_> got my ralink just in case
<Tenkawa_> that i know works
<mkatic> gotta go, talk to you tomorrow
mkatic has quit [Quit: Leaving]
<Tenkawa_> ok.. hopefully I'll bbiaf... might have to compile one module in for wifi if all goes well...
Tenkawa_ has quit [Quit: leaving]
Zotan has quit [Remote host closed the connection]
Zotan has joined #linux-exynos
<javier__> tyler-baker: is so frustrating how fragile the exynos drm driver is :(
<javier__> I think kevin is right and we should just disable until it becomes stable...
<daniels> atomic \o/
<tyler-baker> javier__, I agree, it's becoming difficult to for us to bisect some of these issue on next
<daniels> it still has a load of issues, but atomic very neatly solves a hell of a lot of the things it got so very badly wrong, including fb/vblank refcounting
<javier__> daniels: yeah but all the atomic work is meant for 4.1 right? while we need to fix the current issues in 4.0-rc1 and -next regardless of the atomic work
<daniels> javier__: yeah agreed, i meant in general rather than right immediately now
<javier__> daniels: totally agree
Tenkawa_ has joined #linux-exynos
Tenkawa_ has quit [Changing host]
Tenkawa_ has joined #linux-exynos
<Tenkawa_> yay!!
<Tenkawa_> back on 3.19
<Tenkawa_> and internal wifi
<tyler-baker> woot
<Tenkawa_> thanks all
<Tenkawa_> that 0322 version worked great
<Tenkawa_> I'll start trying to determine why its broke newer tomorrow
<Tenkawa_> oh thats so much better
<Tenkawa_> time to go home.. I should be back later
<Tenkawa_> cheers all
Tenkawa_ has quit [Client Quit]
zombah_ has quit [Quit: Leaving]