[00:03] * rsalveti back [00:05] sveinse: you can just recompile qt with mesa, using gles and then use the sgx libraries [00:06] the current sgx package doesn't provide the headers needed to build packages, because of the lack of a proper soname [00:06] so if you plan to build and use anything with gles, just do it with the mesa libraries and then install the sgx when you want to test with it [00:14] sooo annoying though :) [00:14] guess crosscompiling would help though === DanaG_ is now known as DanaG [00:17] * sveinse back [00:18] OK. here I am building both the SGX package and qt from sources, both cross compiled [00:19] rsalveti: what is mesa, and how does it fit with Qt. I mean is it any different from compiling Qt and SGX together. (I have very little knowledge of what is inbetween these two sets of software) [00:20] sveinse: why are you cross compiling the sgx package? [00:20] it's just binaries [00:20] Partly history [00:20] the only thing to compile there is the kernel modules, and that doesn't help your qt build [00:21] sveinse: mesa is the software implementation of gl and gles [00:21] sgx should just replace it fine, but we don't have a proper soname at the sgx libraries [00:21] We're building a target system of Ubuntu Maverick. Since we're this early in the development, we haven't had time to setup proper .deb package generation [00:22] So we have some software being compiled, custom kernel (for custom board), custom Qt (since we're not using X11, but want GLES), and so on [00:22] oh, ok [00:22] And. we want to cross compile, since not able to do so make our build server useless [00:23] Plan is though, that we migrate over to standard debs later on (since we want to be able to apt-get update our system). [00:23] ok, now I get it [00:24] Using the powervr-omap3-dkms is something I want to do [00:25] FYI: I have been able to make a system for cross building apps into a ubuntu target system without too many worries. [00:25] Thanks to the armel-cross package! [00:25] cool [00:25] Have to say I'm a little proud of it, but noone here really understands that ;) [00:26] Coming back to the issue here: I'm looking at compiling SGX (or repackageing it, since its mostly bins) and compiling Qt with support for it [00:26] :-) [00:27] You say I can compile Qt with generic mesa support, you say? [00:27] ok, so the only thing currently missing are the khronos headers [00:27] you can build with the sgx libraries, if you grab the correct khronos headers, that you can already find at the mesa-dev packages [00:28] I believe it'll be easier for you now if you just build agains the sgx libraries [00:28] as you're not worried about proper packaging atm [00:28] atm, yes. But it sounds like this will backfire later... [00:29] the only problem is that the lack of a proper soname makes it incompatible with the mesa packages [00:29] we, as a distro, cares about that because we can't be sure that the user will install the drivers, and that the board will contain a sgx chip [00:29] I remember something about some headers while compiling Qt some while ago during the concept test... Caused by the missing Khronos headers, right [00:29] so we need the generic implementation to work [00:30] Ah, since they are hardcoded in the SGX package [00:30] yes, so currently on ubuntu if we build something against mesa, it works with the sgx package [00:30] but not the opposite [00:31] so if you only care about using your software on omap with sgx installed, it's fine for you to just build agains the sgx packages [00:31] yes, I do, thanks [00:31] the only thing you'll need atm is the proper header files, as we currently don't deploy it [00:32] Is the missing headers a bug/glitch, or is it an NDA thing? [00:33] it's just because we don't want people building packages with the sgx one at ubuntu in general [00:33] to avoid bugs with the lack of a proper soname [00:34] but you can find the headers at the mesa package [00:34] let me look it for you [00:34] I admit I have to check google what mesa is... [00:35] sveinse: it's an opensource implementation of gl and gles [00:35] and you can run gl/gles by software if you need [00:35] even on your desktop you can now run gles applications with mesa [00:35] you can also have drivers to accelerate it [00:37] Interesting thing though. The first word in OpenGL is open.... [00:38] sveinse: but an open implementation :-) [00:38] sveinse: check http://ports.ubuntu.com/ubuntu-ports/pool/main/m/mesa/ [00:38] packages: libegl1-mesa-dev libgles1-mesa-dev libgles2-mesa-dev [00:38] thanks [00:38] there you'll find all the needed headers to build for gles [00:39] or just grab the mesa source and look for the files [00:39] sveinse: http://paste.ubuntu.com/543851/ [00:40] * sveinse is still exited to see what effect GL has on the speed and resposiveness of his Qt app... [00:42] If only Ubuntu had Qt compiled for qws without X11, I wouldn't have to recompile Qt [00:42] soon we'll have arm public ppas and you'll be able to create a ppa for that :-) [00:43] sorry, ppa? [00:44] sveinse: If only Qt upstream provided a supported way to do that without having to maintain two complete copies of Qt. [00:45] Yeah, I see that. To my knowledge it is only libQtGui.so which is bound to the gfx-system, and the rest isnt. But you still need to make that distinction while configuring [00:46] sveinse: ppa is one way to have a public repository at the launchpad, so you can submit your packages, launchpad will build and make them available for you [00:46] then you can use the repository entry at your sources.list [00:47] ScottK: that would be nice to see, but don't think they will put resources on it [00:48] rsalveti: That's the reason there's no qt-qws in the archive. It's a lot of maintenance work/buildd time to double it. [00:48] Having worked with setting up a proper build system for cross compiled Qt apps, I have a handful of comment about the Qt build system.... [00:48] Probably none of the printable in public .... [00:50] Well (without starting another fight) its similar to Mac's: If you fit inside the box Apple and/or Nokia has prepared for you it's great! If you dont: Well then the box become Pandora's box... [00:52] rsalveti: FYI: You know that TI has released a 4.00.00.01 version of their SGX? [00:54] sveinse: yes, but afaik the only thing they changed was the support for one additional chip [00:54] that's why we didn't update the package [00:54] great, thought you should know [00:54] thanks anyway :-) [00:55] I think I will use the powervr dkms driver for the kernel part, and my custom Qt+SGX, since I need to custom build Qt anyways [00:56] Did you come to a solution in regards of the devmem2 thing? [00:57] Seems like I have to make something in upstart. The SGX driver wants to do some magic during bootup [00:59] Magic seems to be pvrsrvinit, of which is a precompiled binary thing [01:00] Well, I'm really going to bed this time [01:00] rsalveti: Thanks a lot for you assistance [01:00] Appreciate it! [01:01] sveinse: yes, check the upstart file from our sgx package [01:01] you'll see the hack heh :-) [01:01] you first need to identify the omap 3 version and then use the proper pvrsrvinit [01:02] np, ping me later if you have issues with it [01:02] The powervr-omap3 package? [01:03] sveinse: opengles-sgx-omap3 [01:04] Hm.. Not available from my source (http://ports.ubuntu.com/ubuntu-ports maverick main universe) [01:05] try multiverse [01:06] pool/multiverse/o/opengles-sgx-omap3/opengles-sgx-omap3_3.01.00.07-0ubuntu2_armel.deb [01:06] got it [01:08] Well, thanks. Going to look at it in the morning. Night [01:08] later === asac_ is now known as asac === Baybal__ is now known as Baybal [07:44] rsalveti, I added a bunch of info to https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/690370 [07:44] Launchpad bug 690370 in linux-ti-omap4 (Ubuntu) "Strange out of memory on pandaboard (affects: 1) (heat: 8)" [Undecided,New] [07:44] rsalveti, I can provide you ssh root access to my pandaboard [07:58] rsalveti, I sent you access instructions [07:58] ndec, same :) [08:26] guerby: cool. i am connected ;-) [08:27] ndec, I'll be mostly offline today, synchronize with rsalveti for what you do on it :) [08:27] the processes running are unimportant [08:28] guerby: i don't have much to do on it. i have several panda already ;-) [08:28] ndec, I don't know what's so special with mine to get all those mem errors [08:29] guerby: well, i think i would get the same errors on mine if i was doing the same things as you are. [08:29] guerby: that said, we use the panda pretty heavily since we do a lots of native builds... [08:30] ndec, do you use NFS? [08:30] guerby: not me, but some other folks around do. i work mainly on SD or on USB (host) [08:34] ndec, ok, we'll see what you find out :) If it's too much trouble I'll switch to USB disk for /home or / as documented on omappedia [08:45] morning [10:20] rsalveti: Hi! Are there any known issues regarding the XDamage extension on OMAP4? [13:08] alf_: not that I know, why? [13:10] guerby: hey, will look at the bug [13:10] just need to wake up first :-) [13:10] rsalveti: I am trying to make a small program using EGLImage + XComposite + XDamage and I am getting some problems with Damage events not being reported on some windows when redirecting the whole hierarchy [13:11] rsalveti: if I redirect individual windows I don't have a problem [13:11] rsalveti: it may be a bug in my code... but then again it works on my desktop [13:11] hm, ok [13:12] alf_: can you reproduce with the fbdev x11 driver? [13:12] by just using xcomposite and xdamage? [13:12] rsalveti: haven't tried yet... will do and let you know [13:13] rsalveti: thanks [13:13] alf_: ok, if it works it's probably a bug at the pvr x11 driver === njpatel is now known as njpatel_ [14:00] Does Natty support -mthumb-interwork? === ian_brasil__ is now known as ian_brasil [14:13] rsalveti, hi :) first bootstrap cycle succeeded: http://gcc.gnu.org/ml/gcc-testresults/2010-12/msg01284.html [14:16] ScottK: iirc yes [14:17] hrw: Thanks. [14:19] guerby: nice, so that's with 768 and swap? === sbambrough is now known as scottb-afk [14:20] rsalveti, yes. It still gets backtraces in messages but it had no impact I can see on the GCC bookstrap+check === zyga is now known as zyga-food [14:21] guerby: cool, good to know [14:21] rsalveti, with swap off I got user program fail because of malloc returning NULL but no backtrace at all in messages (with mem hole or not) [14:21] guerby: ok [14:22] will later try to debug with a different vm split and without highmem [14:22] rsalveti, you should be able to ssh in my pandaboard in case you want to check configuration / change stuff & reboot should work [14:22] rsalveti, ok thx :) [14:22] to see if that change affected this case [14:22] I'll be mostly offline until this weekend [14:22] guerby: yeah, saw the email, thanks for that :-) === renato is now known as renatofilho === njpatel_ is now known as njpatel [15:55] GrueMaster: hey, can you later check bug 688765? [15:55] Launchpad bug 688765 in linux (Ubuntu) "Can't init uart3 (no clocks available) at Beagleboard-xM (affects: 1) (heat: 8)" [Undecided,In progress] https://launchpad.net/bugs/688765 [15:55] time for food now [15:55] Sure, is there a patched kernel finally? [15:56] GrueMaster: I created a different bug for our kernel, pointing the patches and a kernel deb file to test [15:58] I thought we were on the mainstream kernel for omap? Why file a different bug instead of posting a patch to the existing one? [15:59] GrueMaster: the other bug was for linaro's kernel [15:59] and this is for maverick [16:00] Ah. I could have sworn there was a bug against the main kernel. Will look into after coffee. [17:10] Has anyone gotten the BeagleBoard Unbuntu install working at: https://wiki.ubuntu.com/ARM/BeagleNetInstall ? [17:10] I think there are some important files missing from the instructions. [17:11] Mark____: I had tested this during Lucid timeframe and it worked fine. I'll double check the instructions. What issues are you seeing? [17:12] Bear in mind this is not tested on a BeagleXM (and likely won't work). [17:12] I thought the FAT partition on the SD card needed a file named MLO [17:12] which would load x-boot-loader. [17:13] The beagleboard should have that preinstalled in nand. [17:13] I'm trying to boot on a Beagle xM and nothing is happening on the serial port. [17:13] If you power up the beagleboard with no USB or SD card, do you see anything on the serial console? [17:13] Ah, XM. Not supported in Lucid. [17:14] XM doesn't have nand, hence no boot loader. [17:14] Yup [17:14] How should I get Ubuntu running on an xM? [17:16] I'll see if I can get the instructions updated (or some workaround) for XM. For now, use http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/10.10/release/ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz and the instructions at https://wiki.ubuntu.com/ARM/OMAPMaverickInstall [17:17] There is an extra step involved if you have an XM rev A3 or later. [17:17] The instructions are there. [17:18] Thanks. I'll check it out now. [17:19] This will give you a netbook image, but once running it is fairly easy to customize. We are working on a pre-installed minimal image for Natty, for developers that want something other than netbook installs. [17:22] I'm doing a Beagle workshop for educators next month and I'm looking for some dirt-simple instructions they can give to they students [17:23] and have something impressive running in a short time. [17:23] I thought I had it with Ubuntu, but we aren't there yet. [17:23] I haven't tested Maverick netboot on omap, but I'm sure some simple instructions could be cobbled together. [17:24] Unless they have a hard requirement for no kvm support, the netbook image should work well for them. [17:26] btw: I updated the net install instructions warning about the lack of support for XM. Thanks for pointing it out. [17:28] I guess I can pull out my C4 board and see if that works. [17:33] It looks like it's working on the C4. [17:33] Now I have to hook up the ethernet adapter. [17:35] Yea, netboot works a little better that way. :P [17:48] Mark____: netboot is kinda unsupported, it should work, but if it breaks, you get to keep both pieces [17:50] Well.... The C4 is set up and it looks like it is doing something. [17:51] If I get this SD working on the C4 can I switch to the xM and have it work? [18:06] Mark____: Try using the maverick netboot. That would have better success, as it has kernel support for XM. But you will need to create a 70-100M fat partition first. And I am not sure if x-loader and u-boot would automatically install there. It would take a little work, but it is doable. === scottb-afk is now known as scottb === scottb is now known as sbambrough [21:09] tgall_foo, ping? [21:14] jcrigby, pong