[01:39] <rsalveti> apachelogger: ouch
[01:39] <apachelogger> rsalveti: do you happen to know where does our omap_rev_lt_3_0
[01:40]  * apachelogger is trying to get our dkms package build modules for the meego kernel, since he is out of other options
[01:40] <apachelogger> currently fails to build with omap_rev_lt_3_0 being implictly defined
[01:40] <rsalveti> apachelogger: what exactly are you trying to do, port ubuntu to n900?
[01:41] <rsalveti> when I was trying that I basically ported the meego patches to the ubuntu tree, got it booting but didn't have time to test the sgx packages
[01:41] <apachelogger> porting is a bit of a strong word, ScottK tells me someone is working on a kernel that will run on the n900
[01:41] <apachelogger> meanwhile I am trying to work out what needs doing on the kubuntu side of things to give decent user experience
[01:41] <rsalveti> I was doing that, then mpoirier also got some work on it
[01:42] <rsalveti> ok
[01:42] <rsalveti> so for now I'd recommend you to use at least the sgx kernel patch available for meego
[01:42] <rsalveti> then try using their libraries and x driver, but that's what you said you did
[01:42] <rsalveti> would be interesting to see your segfault
[01:43] <apachelogger> yeah
[01:43] <rsalveti> this weekend I'm planing to waste some time on that, now that I got my n900 back
[01:43] <apachelogger> hooray
[01:43] <rsalveti> at least to get a proper kernel tree that can be properly used by ubuntu's userspace
[01:43] <apachelogger> having a working kernel makes things a lot more fixable for me ^^
[01:44] <rsalveti> apachelogger: this was the latest tree that I did some work http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-maverick.git;a=shortlog;h=refs/heads/rsalveti-master-n900
[01:44] <apachelogger> ok
[01:44] <rsalveti> got it booting until x11, and then used the efl interface
[01:45] <rsalveti> but then I had to give my n900 to a friend of mine
[01:45] <rsalveti> and I got it back this week
[01:45] <rsalveti> while at uds I was debugging this with rbelem
[01:49] <rcn-ee> apachelogger, which kernel?  give this a shot.. http://gitorious.org/angstrom/angstrom-linux/commit/38adc41c6f6d686156083ff0889d0b2dd71f2e14
[01:49] <apachelogger> rcn-ee: 1.1
[01:49] <apachelogger> we did dirty kernel copies ^^
[01:50] <apachelogger> https://wiki.ubuntu.com/ARM/n900
[01:51] <rcn-ee> ah, the meego kernel..
[01:51] <apachelogger> aye
[01:51] <rsalveti> rcn-ee: yeah, there are some other patches just to make n900 work properly
[01:51] <apachelogger> DKMS: install Completed.
[01:51] <apachelogger> omg
[01:51]  * apachelogger gets all jumpy
[02:04]  * rbelem o/
[02:05] <apachelogger> QGLShader: could not create shader
[02:05] <apachelogger> Warning: "" failed to compile!
[02:05]  * apachelogger sighs
[02:06] <rbelem> apachelogger, which plasma-mobile are you running?
[02:06] <apachelogger> whatever is in maverick
[02:06] <apachelogger> oh
[02:06] <apachelogger> omg
[02:06] <apachelogger> uh
[02:06] <apachelogger> OGLES2Coverflow works
[02:06]  * apachelogger got gles2 it seems \\o/
[02:06] <rbelem> \o/
[02:07] <rbelem> apachelogger, you rock!
[02:07] <apachelogger> now if only plasma would like to work too
[02:07] <rsalveti> apachelogger: cool
[02:07] <apachelogger> rsalveti: would Qt need to be compiled against special sgx headers?
[02:07] <apachelogger> currently it is built against mesa's gles
[02:07] <rsalveti> just to be compiled with opengl
[02:07] <rsalveti> apachelogger: nops, that should work
[02:07] <apachelogger> strange
[02:08]  * rsalveti brb
[02:09] <rbelem> apachelogger, do you know any tool that makes debian/copyright maintainance easy? :-)
[02:09] <apachelogger> http://people.ubuntu.com/~apachelogger/scripts/
[02:09] <apachelogger> copyright and license scripts
[02:12] <apachelogger> http://paste.ubuntu.com/541253/
[02:16] <rbelem> apachelogger, maybe martin has better clues about that
[02:16] <apachelogger> http://comments.gmane.org/gmane.comp.lib.qt.qml/1749
[02:16] <apachelogger> that does not sound very good
[02:17] <rbelem> apachelogger, qt not compiled with gl es?
[02:17] <apachelogger> no, it is
[02:18] <apachelogger> but apparenlty it needs to be compiled against an appropriate version
[02:18] <GrueMaster> I'd look at the problem in a deeper vein.  "The device itself is runs on a Atom Z520 processor".  That is Poulsbo video, which (when I worked on it) wasn't that great.
[02:19] <rbelem> apachelogger, hum... martin said something about use mesa gl es libs to compile
[02:19] <GrueMaster> And I don't know of any GMA500 (Poulsbo) support in Ubutnu since 8.04.
[02:19] <apachelogger> rbelem: that is what I did
[02:20]  * apachelogger did not even know one needed proprietary blob until this week ^^
[02:21] <rbelem> brb
[02:24] <apachelogger> in the lands of meego the have sgx devel packages, making me think they build against it...
[02:31] <apachelogger> rbelem: if you can find someone to give input on the problem, that would be great
[02:31]  * apachelogger needs to go to bed
[02:32] <apachelogger> rbelem: also, fwiw, plasma-netbook does not manage to come up with *anything*
[09:29] <hrw> hi
[09:29] <hrw> do we have kernel for pandaboard which will work with 1G ram finally?
[09:30] <rsalveti> maybe cooloney knows better
[09:31] <cooloney> hrw: yeah,
[09:31] <hrw> cooloney: is it available in natty?
[09:31] <cooloney> i think maverick kernel works with mem=1G, but we use 2:2 split
[09:31] <hrw> cooloney: which maverick kernel?
[09:32] <cooloney> hrw: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4
[09:32] <rsalveti> for me it never worked well with high cpu loades
[09:32] <rsalveti> always giving weird crashes
[09:32] <cooloney> that's maverick
[09:32] <rsalveti> but that might be fixed already at the lates ti kernel
[09:32] <hrw> btw - definition of stable kernel: "apt-get source somethingbig -b"
[09:32] <cooloney> hrw: if you wanna try natty, please try linaro natty kernel
[09:32] <rsalveti> cooloney: are you able already to boot upstream on panda?
[09:32] <cooloney> http://git.linaro.org/gitweb?p=ubuntu/linux-linaro-natty.git;a=summary
[09:33] <hrw> cooloney: I use natty and maverick-14 kernel
[09:33] <cooloney> rsalveti: i can boot up the upstream kernel. but it is panic when it try to use our ubuntu mininal root filesystem
[09:33] <cooloney> rsalveti: but you can try linaro natty kernel
[09:34] <cooloney> which is .37 based and very close to mainline
[09:34] <cooloney> with our ubuntu sauce and config.
[09:34] <cooloney> so it boots fine with on my panda
[09:34] <rsalveti> that's nice
[09:35] <cooloney> rsalveti: so in mainline highmem is disabled defaultly
[09:35] <cooloney> rsalveti: i can still see such instability with linaro natty kernel
[09:35] <rsalveti> hm
[09:35] <cooloney> rsalveti: but if you have time, you can try that on your board
[09:36] <hrw> otyher thing: usb. 13MB/s is max?
[09:36] <rsalveti> cooloney: sure, will try it later
[09:38] <tmzt> does that linaro support omap3/beagle?
[09:38] <tmzt> kernel
[09:42] <cooloney> tmzt: sure
[09:42] <tmzt> cooloney: we are trying to port to the new nook color, which is an omap3+slcd on the lvds, and very similar to beagle
[09:42] <cooloney> tmzt: so one linaro kernel can boots up on omap3/beagle and omap4/panda with the same natty file system
[09:43] <tmzt> and we have the source from bn to port the board
[09:44] <cooloney> tmzt: that's good start point. mainline supports beagle very well
[09:44] <cooloney> but limited to panda
[09:44] <cooloney> we still miss some driver or feature of omap4 in mainline
[09:44] <hrw> nothing strange - omap4 is still young
[09:44] <tmzt> this is omap3 though
[09:45] <tmzt> looking for the best support (tony kernel?) for that
[09:51] <cooloney> tmzt: i think mainline is good for omap3
[09:52] <tmzt> okay
[11:06] <janimo1> I am trying to run 10.10 omap3 image under qemu but it hangs timeing out on mtd
[11:06] <janimo1> qemu-maemo-system-arm -M beagle -m 256 -sd ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img -serial stdio
[11:06] <janimo1> how can I create a valid beagleboard mtd file to see if that is the prob?
[11:07] <tmzt> mtd file?
[11:13] <janimo1> tmzt: something to stand for the expected mtdbloc device in the guest
[11:13] <janimo1> there
[11:13] <janimo1> is a sdcard image
[11:13] <janimo1> and I understand there's a NAND image as well
[11:13] <tmzt> I guess mtd image has to have an ftl
[11:14] <tmzt> how's the tegrabook going?
[14:34] <davidm> ndec1, call time?
[15:01] <GrueMaster> To all that were planning on attending the Mobile/Arm team meeting today at 15:00 UTC; the meeting has been canceled do to key players' otehr commitments and holiday schedules.  Thank you.
[16:37] <dmart> asac: yes
[20:40] <GrueMaster> Hmm.  It would appear that one of the recent changes to Natty since A1 has clobbered X on panda.
[20:49] <rsalveti> GrueMaster: with which image?
[22:00] <GrueMaster> No new image.  Just using A1 and running apt-get udgrade.
[22:01] <rsalveti> ok
[22:03] <GrueMaster> I'm looking into it now.  Had to check my other board I had sent to Lexington to make sure it survived.  Also had to run a vehicle to the shop (another transmission) and get a bag of fresh ground coffee.
[22:03] <GrueMaster> Busy morning.
[22:09] <rsalveti> :-)
[23:30] <GrueMaster> rsalveti: I stand corrected.  I had used the latest image, 20101206, and updated from there.  Am now running clean image to see what update clobbered X.
[23:30] <rsalveti> ok
[23:31] <GrueMaster> Hrm.  Networking fails when the cord isn't plugged in.  (oops).