[00:15] <persia> ka6sox, It appears to be based of 2.6.29
[00:16] <ka6sox> yes, but we haven't been able to determine which tree it came from.
[00:16] <persia> so?
[00:17] <persia> I suppose it reduces the porting effort, but I presume you could sensibly look at the diff against mainline 2.6.29, and try to determine which are porting patches.
[00:17] <persia> All the SoC-specific stuff ought be mainline, so it's really just the platform stuff that is interesting.
[00:18] <ka6sox> ya, its a question of time...but if I could ever get more time I'd have more fun.
[00:18] <persia> Heh.
[00:18] <persia> I don't know enough about kernel internals, but I suspect there's something on the order of 10-12 files that have any content that is Nook-specific, and isn't covered by the OMAP stuff.
[00:19] <persia> And strongly suspect that the porting effort to bring those files to 2.6.38 is unlikely to be heroic.
[00:20] <persia> (although I wouldn't expect the result to be as seamless as the current kernel: there's surely some extra hackery present, but those are fixable bugs: the above ought get one booting)
[08:26] <lilstevie> I am having issues with framebuffer setup
[08:26] <lilstevie> not getting any output on screen once GDM starts
[12:59] <rsalveti> janimo: it's hard to have both gl and gles support at Qt
[12:59] <rsalveti> even if we split in two packages, I don't think it'll be easier to maintain
[12:59] <rsalveti> qt takes 1 day to build, and it's huge
[13:04] <ogra> root@ac100:/# apt-get -f install
[13:04] <ogra> Segmentation fault
[13:04] <ogra> grrr
[13:06] <rsalveti> haha :-)
[13:06] <rsalveti> not good
[13:06] <ogra> i guess i'll have to reboot
[13:06] <ogra> nope, not good
[13:06] <rsalveti> good luck
[13:06] <ogra> natty chroot though
[13:06] <rsalveti> oh, ok
[13:06] <ogra> not my main rootfs
[13:39] <janimo> rsalveti, yes, probably more weork than worth it with qt split
[14:06] <berco> ogra: persia: fyi, alsa-lib v1.0.24 with UCM support is now out
[14:07] <berco> still lacking the specific config files for OMAP4 boards
[14:36] <ogra> berco, yeah, we hard that already, i guess luke waits with the upload until after the freeze
[14:37] <ogra> *heard
[14:37] <berco> ogra: let us know how it goes and if you face issues
[14:38] <ogra> will do
[15:33] <ogra> root@ac100:/# apt-get -f install
[15:33] <ogra> Segmentation fault
[15:33] <ogra> hmm, so reboot didnt help
[15:33] <ogra> thats bad
[15:37] <armin76> you broke it :D
[15:40] <ogra> armin76, i wish i did
[15:40] <ogra> then i would know whats wrong
[16:08]  * ogra sighs
[16:08] <ogra> is anyone running a maverick rootfs with natty chroots ?
[16:08] <ogra> (both armel)
[16:09] <rcn-ee_at_work> ogra, squeeze rootfs with natty chroot... or do you think it's a maverick->natty issue?
[16:10] <rsalveti> GrueMaster: up already?
[16:11] <ogra> rcn-ee_at_work, well, i think its a HW issue but i dont get such behavior with maverick->maverick-chroot
[16:12] <GrueMaster> Been up for an hour.
[16:12] <ogra> GrueMaster, really ?
[16:12] <GrueMaster> Still working on coffee infusion.
[16:12] <ogra> GrueMaster, the question is why :)
[16:13] <GrueMaster> puppy walking on bladder - bad combo.
[16:15] <GrueMaster> I'm getting a little miffed at the XM dev's.  No updated documentation since rev A2 available (A3 broke DVI for us), I have a Rev B and no idea what changes have been made, and they are talking about some change to USB on Rev C.
[16:16] <ogra> GrueMaster, i thought rsalveti just added a fix for the broken DVI
[16:16] <ogra> (or reworked a broken one from koen)
[16:17] <rsalveti> GrueMaster: A3 should be the same as B
[16:17] <rsalveti> only chip rev that changed
[16:17] <GrueMaster> And this is documented...where?
[16:17] <rsalveti> and our latest kernel deb should be fine with it
[16:17] <ogra> ricardos head ;)
[16:17] <rsalveti> beagle m-l probably
[16:17] <ogra> just print a pdf from it ;)
[16:18] <rsalveti> yeah :-)
[16:18] <GrueMaster> ogra: The interface is broken.  :P
[16:18] <ogra> file a bug
[16:18] <rsalveti> :P
[16:20] <GrueMaster> At any rate, it is frustrating when software doesn't work as documented, and you don't know the hardware changes that could have affected it.
[16:21] <ogra> welcome to the world of developer hardware
[16:23] <rsalveti> GrueMaster: http://beagleboard.org/hardware/design
[16:23] <rsalveti> Only Rev B change is processor revision
[16:23] <GrueMaster> Interesting.  I would not have found that link going through the main pages.
[16:24] <rsalveti> beagleboard.org -> product details -> Design Materials
[16:26] <GrueMaster> True, but the layout suggests that is for the original beagle only.  Clicking on beagleboard.org>hardware shows a separate link for the XM at the top of the page, which only leads to the old documentation.
[16:26] <GrueMaster> But thanks for pointing that out.
[16:27] <GrueMaster> Pad web page layout.
[16:28] <GrueMaster> s/Pad/bad
[16:30] <rsalveti> yeah, the layout is not that nice
[16:31] <rcn-ee_at_work> there's a git tree for the beagleboard.org layout somewhere.  ;)
[16:31] <rcn-ee_at_work> GrueMaster, under static.. ;) http://www.beagleboard.org/gitweb/?p=beagleboard.org.git;a=tree
[16:44] <GrueMaster> Erm, yea.  I'm looking at this and thinking WTF.  Looks interesting and cool.  If/when I get time to learn yet another development environment, I might submit some changes.  In the meantime, is there a bug tracker to file bugs against the web page?  :P
[16:52] <rcn-ee_at_work> GrueMaster, best to just pink jkridner he does a lot of the web changes..
[16:52] <GrueMaster> ok
[21:41] <sinclair> hi everyone
[21:42] <sinclair> my erlang is segfaulting... and i don't know why =)
[23:11] <Kamondelious> persia, turns out it was bad wiring on the connection between USB wifi dongle and the USB hub, the dongle works fine, just need to fix my wiring.