[10:17] <mlankhorst> hm weird
[11:02] <zzippy> mlankhorst: weird? whatever. If I can do anything else to help, let me know. Busy in RL next hours. Thank you.
[11:27] <mlankhorst> I'm not working today :)
[18:19] <shadeslayer> RAOF: hi, I believe robert_ancell pinged you about this a couple of minutes ago
[18:20] <shadeslayer> I'm having issues getting X up on the N10
[18:20] <RAOF> shadeslayer: This is correct.
[18:20] <shadeslayer> hey :)
[18:20] <shadeslayer> so, I might be missing something obvious in the kernel I think
[18:21] <RAOF> I saw your Xorg.0.log; *some* things are obviously working.
[18:21] <shadeslayer> I basically take the Android kernel and enable VT, NAMESPACES and HW_CONSOLE_BINDING
[18:21] <shadeslayer> roger
[18:22] <RAOF> But you don't get any framebuffer console, right?
[18:22] <shadeslayer> nope
[18:22] <shadeslayer> if I enable fbcon It doesn't even boot afaict
[18:22] <RAOF> If the framebuffer console doesn't work then it's highly likely that X won't work, because X is using the framebuffer and will be using it in the same way as fbcon.
[18:23] <shadeslayer> oh, that indeed makes sense
[18:23] <shadeslayer> RAOF: I tried the modesetting driver as well
[18:23] <RAOF> That won't work, because you don't have a kms driver.
[18:23] <shadeslayer> that resulted in something about Xf86console setpgid calls failing
[18:23] <shadeslayer> okay
[18:24] <shadeslayer> well this sucks :P
[18:25] <shadeslayer> RAOF: any suggestions on how to make fbcon work?
[18:25] <shadeslayer> I gave up on it because googling didn't turn up anything
[18:25] <RAOF> No idea, sorry.
[18:25] <shadeslayer> :(
[18:26] <shadeslayer> it's super weird that the chromeos kernel works
[18:26] <shadeslayer> same SoC
[18:26] <RAOF> With X and all?
[18:27] <shadeslayer> oh, what I meant was, the chromeos kernel works on the chromebook :D
[18:27] <shadeslayer> which has the same SoC
[18:27] <shadeslayer> and yes, it runs X
[18:27] <RAOF> Plausibly with a non-fbdev driver, of course :)
[18:28] <shadeslayer> maybe
[18:28] <shadeslayer> hrw didn't mention if the fbdev driver works
[18:34] <shadeslayer> RAOF: and xserver-xorg-video-armsoc won't be of any help here?
[18:35] <RAOF> I'm totally unfamiliar with that driver.
[18:35] <shadeslayer> okay
[18:35] <RAOF> But "armsoc" seems like an over-ambitious name, as there isn't a single armsoc and each of the graphics chips will need a different driver.
[18:36] <shadeslayer> yeah, but that thing is specially for the mali GPU's
[18:36] <RAOF> Then that might work?
[18:36] <shadeslayer> the name is a misnomer however :P
[18:36] <shadeslayer> yeah, except I am uncertain on how to put it on the rootfs so that it is seen by the kernel
[18:37] <shadeslayer> or do I just install that driver and X will pick it up?
[18:38] <RAOF> X will pick it up
[18:38] <RAOF> It's not used by the kernel
[18:38] <shadeslayer> oh cool
[18:38] <shadeslayer> ack
[18:42] <shadeslayer> I'll feel super bad if this doesn't work :/
[18:42] <shadeslayer> since I'll have no option left
[18:55] <shadeslayer> here goes nothing
[18:55]  * shadeslayer crosses his fingers
[18:55] <shadeslayer> nope :(
[18:56] <shadeslayer> hm, didn't even try armsoc
[18:59] <RAOF> shadeslayer: You might need to explicitly load it in xorg.conf
[18:59] <shadeslayer> yeah, doing that
[18:59] <RAOF> I don't recall that being hooked up to the autodetect.
[18:59] <shadeslayer> noap
[19:01] <shadeslayer> RAOF: http://paste.kde.org/735350
[19:01] <shadeslayer> ignore the OMAP bits, it was forked from the OMAP driver
[19:02] <shadeslayer> oooh
[19:02] <shadeslayer> [    13.125] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[19:02] <shadeslayer> which is what I got with the modesetting driver
[19:03] <RAOF> Yeah, armsoc can't detect any supported devices.
[19:03] <RAOF> [    13.120] (WW) Falling back to old probe method for armsoc
[19:03] <RAOF> [    13.120] (EE) No devices detected.
[19:03] <shadeslayer> I have half a mind to try out git
[19:04] <RAOF> git armsoc, or git xserver, or both?
[19:04] <RAOF> :)
[19:04] <shadeslayer> git armsoc
[19:04] <shadeslayer> oh
[19:04] <shadeslayer> master is just one commit ahead -.-
[19:05] <shadeslayer> so yay, can't do anything with this tablet
[19:16] <shadeslayer> RAOF: how come the fb driver finds the correct resolution :S
[19:16] <shadeslayer> and everything else
[19:16] <shadeslayer> just fails to start
[19:17] <RAOF> It *is* starting.
[19:17] <shadeslayer> uh okay
[19:17] <shadeslayer> then what's the problem?
[19:17] <RAOF> It's just that what it's displaying isn't ending up on your display.
[19:17] <shadeslayer> 0.op
[19:17] <RAOF> As far as X is concerned, everything's working.
[19:18] <shadeslayer> I see
[19:18] <RAOF> xf86-video-fbdev is happily drawing to what it thinks is the framebuffer.
[19:18] <RAOF> But it's clearly mistaken.
[19:18] <shadeslayer> except it's not
[19:18] <shadeslayer> yeah
[19:31] <shadeslayer> RAOF: no way to debug it as well right
[19:31] <RAOF> shadeslayer: Not that I can think of off hand.
[19:32] <RAOF> Although getting fbcon working would likely fix it too.
[19:32] <shadeslayer> yeah, except I have no idea how
[19:34] <shadeslayer> heh