**** BEGIN LOGGING AT Tue Jun 15 02:59:57 2010
Jun 15 03:24:19 * mozzwald is away: snore...
Jun 15 06:17:24 <EthanZ6174> how can i get a arm-ubuntu source list?
Jun 15 06:17:50 <EthanZ6174> i got so many 404 when i use the kind of normal ones..
Jun 15 07:21:52 <hrw> morning
Jun 15 07:36:32 <cooloney> amitk: around?
Jun 15 07:36:38 <amitk> cooloney: yes
Jun 15 07:36:58 <cooloney> amitk: i am looking at the OTG config issue you pointed out yesterday
Jun 15 07:37:26 <cooloney> from the git log, i think you revert the patch which enabling the OTG in the kernel
Jun 15 07:37:32 <cooloney> so why you revert that?
Jun 15 07:37:40 <cooloney> OTG driver doesn't work at all?
Jun 15 07:39:45 <amitk> cooloney: that config was causing OOPs, IIRC. So we need to see if some more patches are necessary
Jun 15 07:40:22 <cooloney> amitk: yeah, i guess so. so firstly we enable the OTG as the omap3 beagle board defconfig
Jun 15 07:40:31 <cooloney> and test and file another bug?
Jun 15 07:40:38 <cooloney> i think OTG should be built-in
Jun 15 07:41:42 <cooloney> oh, maybe the dmesg.txt from ogra_cmpc in the LP is from a kernel which built-in OTG stuff
Jun 15 07:51:36 <amitk> cooloney: if possible OTG should be a module so we can switch between different gadget drivers - audio, ethernet, gadgetfs, mass storage, etc.
Jun 15 07:52:40 <amitk> cooloney: actually, only the USB Gadget drivers need to be modular, the HW-specific driver can be compiled in
Jun 15 07:53:39 <amitk> cooloney: http://paste.ubuntu.com/449992/ is the diff for that should enable OTG
Jun 15 07:53:50 <amitk> s/for//
Jun 15 07:56:21 <cooloney> amitk: i agree, gadget upper level drivers should be modulars, and TI OTG controller driver should be built-in
Jun 15 07:57:19 <cooloney> amitk: after a study of the oops from the dmesg, i think we missed to built-in the OTG transceiver driver as well as OMAP OTG driver
Jun 15 07:57:37 <cooloney> amitk: let me try to build in them and post a kernel for testing
Jun 15 08:01:31 <lag> Good morning every-peeps
Jun 15 08:03:18 <amitk> morning lag
Jun 15 08:03:24 <lag> Hey amitk
Jun 15 08:08:58 <cooloney> lag and amitk morning. -:)
Jun 15 08:09:27 <lag> Morning cooloney, I'm just replying to your emails
Jun 15 08:13:55 <lag> cooloney: How far have you progressed with the Maverick - Panda kernel?
Jun 15 08:15:49 <cooloney> lag: I added some panda supported yesterday, and sebjan will review that. if that's ok, i will send out for review and pull
Jun 15 08:15:52 <cooloney> lag: for the bug #592295
Jun 15 08:15:53 <ubot2> Launchpad bug 592295 in linux-ti-omap (Ubuntu) "omapdss DISPC error: SYNC_LOST_DIGIT (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/592295
Jun 15 08:16:01 <cooloney> lag: is on .33 or .34?
Jun 15 08:16:53 <cooloney> and i think you may have some solution now
Jun 15 08:17:28 <lag> cooloney: 2.6.34-900-omap4
Jun 15 08:18:04 <lag> If you send me a .33 kernel, I can see if the problem is a lasting one
Jun 15 08:18:42 <lag> cooloney: I have seen your solution, but I think I have a neater one
Jun 15 08:19:24 <cooloney> lag: ok, got it, but in the LP post, you said it is 2.6.33-900-omap4
Jun 15 08:19:45 <cooloney> lag: ok, cool, i don't have the hardware. hehe
Jun 15 08:21:12 <lag> In which case, I have tested it on both
Jun 15 08:21:23 <lag> So it is .33 and .34
Jun 15 08:22:13 <lag> cooloney: Have you read your emails?
Jun 15 08:23:59 <cooloney> lag: oh, just got it.
Jun 15 08:24:07 <lag> ;)
Jun 15 08:24:43 <cooloney> for the .34 repo, git://kernel.ubuntu.com/roc/ubuntu-maverick.git ti-ubuntu-2.6.34
Jun 15 08:24:58 <cooloney> i think sebjan will do his work based on this branch
Jun 15 08:25:24 <lag> Does that boot?
Jun 15 08:25:55 <cooloney> hmmm, i think you told me it boots from you panda
Jun 15 08:26:03 <cooloney> hehe
Jun 15 08:26:25 <lag> If it's the same one you sent me yesterday it does
Jun 15 08:26:29 <cooloney> and after sebjan fixed his kernel cmdline, he boots that kernel on his panda too
Jun 15 08:26:31 <lag> However, I tried to build it and it didn't boot
Jun 15 08:26:38 <cooloney> lag: yeah, it is the same
Jun 15 08:26:41 <cooloney> lag: really?
Jun 15 08:26:47 <lag> Yeah, really
Jun 15 08:27:00 <cooloney> you built from the same tree, but does not boot?
Jun 15 08:27:11 <cooloney> oh, maybe you are trying the my old base
Jun 15 08:27:28 <cooloney> so which commit SHA is your base in you building tree
Jun 15 08:27:29 <lag> It's the one on kernel.ubuntu.com
Jun 15 08:27:35 <lag> Wait one
Jun 15 08:27:40 <cooloney> np
Jun 15 08:28:06 <lag> ea34fca089b7ab2986ff391f1fc036d4425e6995
Jun 15 08:29:41 <cooloney> oh, sorry, that is not including the panda support
Jun 15 08:29:46 <cooloney> pls just git fetch
Jun 15 08:29:52 <cooloney> and rebuild,
Jun 15 08:30:06 <lag> That was the latest when you went offline last night
Jun 15 08:30:08 <lag> :(
Jun 15 08:30:18 <lag> I thought it was something I was doing wrong!
Jun 15 08:30:47 <cooloney> lag: oh, sorry, hold on,
Jun 15 08:30:59 <cooloney> could you post your git log --oneline?
Jun 15 08:31:56 <lag> I've just fetched
Jun 15 08:32:17 <cooloney> ok,
Jun 15 08:32:54 <cooloney> that should be the same as my kernel source, i think
Jun 15 08:33:11 <cooloney> you are using sbuild or just crosscompile
Jun 15 08:41:30 <lag> cooloney: It's still at ea34fca089b7ab2986ff391f1fc036d4425e6995 UBUNTU: SAUCE: fix changelog for our target release - maverick
Jun 15 08:41:35 <lag> Even after a fetch
Jun 15 08:48:03 <cooloney> lag: yeah, i think you got the same kernel source as me
Jun 15 08:48:22 <lag> And that should work?
Jun 15 08:48:38 <cooloney> yeah, i built the kernel package from that.
Jun 15 08:48:46 <cooloney> and uploaded to you and sebjan
Jun 15 08:49:12 <cooloney> so is there any error message when you was booting your own built kernel?
Jun 15 08:49:38 <lag> Nope, I just don't receive any output
Jun 15 08:52:46 <cooloney> lag: hmmm, too bad, no idea about that. you changed the kernel cmdline or something?
Jun 15 08:53:13 <lag> Nope, I'm using the same one
Jun 15 08:53:30 <lag> When I do a diff on or images, they 'differ'
Jun 15 08:53:49 <lag> Is ea34fca089b7ab2986ff391f1fc036d4425e6995 your final commit?
Jun 15 08:55:10 <cooloney> yeah, i didn't change anything since that
Jun 15 08:57:40 <cooloney> lag: you are using sbuild or just cross compiling?
Jun 15 08:59:50 <lag> I'm just using schroot
Jun 15 08:59:55 <lag> I'm using the build scripts
Jun 15 09:05:33 <cooloney> lag: the kernel i uploaded yesterday is cross compiled
Jun 15 09:07:16 <lag> Okay
Jun 15 09:07:21 <lag> Let me try it again
Jun 15 10:36:49 <cooloney> ogra_cmpc and amitk, i updated bug #566645
Jun 15 10:36:50 <ubot2> Launchpad bug 566645 in linux-ti-omap (Ubuntu Maverick) (and 2 other projects) "OTG configuration is broken on omap kernel (affects: 2) (heat: 70)" [High,Confirmed] https://launchpad.net/bugs/566645
Jun 15 10:38:08 <hrw> http://people.canonical.com/~hrw/ubuntu-maverick-armel-cross-compilers/
Jun 15 10:43:41 <zumbi> hrw: congrats! can you try powerpc or mips/el?
Jun 15 10:44:10 <hrw> zumbi: thats dpkg-cross way
Jun 15 10:44:53 <zumbi> hrw: yes, but binary-*-cross.mk merged into binary-*.mk?
Jun 15 10:45:21 <hrw> zumbi: no, this is still on a list
Jun 15 10:46:30 <zumbi> oh! ok, also biarch cross compilers were broken for multilib and non-multilib builds, on lenny used to work fine
Jun 15 10:47:00 <zumbi> anyway, well done :)
Jun 15 10:47:30 <hrw> zumbi: gcc-4.5 cross work resulted in a set of fixes
Jun 15 10:47:44 <zumbi> in a couple weeks I hope to have some time available to help out
Jun 15 10:47:49 <hrw> zumbi: https://edge.launchpad.net/ubuntu/+spec/arm-m-cross-compilers has them linked
Jun 15 10:48:09 <zumbi> i remember you showing me a patch
Jun 15 10:56:34 <JameswStubbs> Hello, anyone here who can give some advice?
Jun 15 10:56:45 <lool> zumbi: We dont have mips/mipsel in Ubuntu and powerpc in not in the main priorities of Linaro, it's more a Debian thing, but that should just work -- problem is that the patches aren't in the Debian toolchain yet
Jun 15 10:58:41 <lool> JameswStubbs: don't ask to ask   ;-)
Jun 15 10:58:54 <hrw> lool: those patches are also not in ubuntu toolchain yet
Jun 15 10:59:19 <lool> hrw: Ok, did you apply any to build http://people.canonical.com/~hrw/ubuntu-maverick-armel-cross-compilers/ ?
Jun 15 11:00:24 <JameswStubbs> Ok then, basically I've built a Ubuntu minimal rootfs using rootstock and have it mounted in qemu with networking, I'm trying to install matchbox. I've installed xorg, and all the matchbox applications but I need GTK, Is there a way to do this without installing the full gnome enviroment?
Jun 15 11:00:57 <hrw> lool: 594534, 590696 were needed
Jun 15 11:01:36 <hrw> I have a build with also 593281 applied to get libgcc1-dbg
Jun 15 11:02:31 <hrw> libgcc1-dbg-armel-cross_4.5.0-5ubuntu1.lool1_all.deb
Jun 15 11:05:04 <JameswStubbs> Bump (Sorry for bumping)
Jun 15 11:06:15 <cwillu_at_work> JameswStubbs, um, then don't bump?
Jun 15 11:06:26 <cwillu_at_work> this isn't ubuntuforums
Jun 15 11:06:34 <lool> lool1 that's me!
Jun 15 11:06:40 <lool> hrw: ~hrw1 please  :-)
Jun 15 11:07:08 <lool> JameswStubbs: in theory you should just be able to apt-get install that
Jun 15 11:07:16 <lool> JameswStubbs: does it pull more than it should?
Jun 15 11:07:23 <lool> JameswStubbs: what specifically is pulled which shouldnt be?
Jun 15 11:07:24 <JameswStubbs> apt-get install what?
Jun 15 11:07:31 <lool> JameswStubbs: matchbox
Jun 15 11:07:39 <JameswStubbs> matchbox pulls everything it needs
Jun 15 11:07:55 <JameswStubbs> But it depends on GTK which is gnome's toolkit I think
Jun 15 11:07:57 <lool> JameswStubbs: You need Gtk+ for what, a custom application?
Jun 15 11:08:10 <JameswStubbs> Matchbox-session needs gtk
Jun 15 11:08:16 <zumbi> lool: then maybe sparc? -- I just wonder if biarch cross compilers are fixed. I saw you having some mails with doko about it, but he was wanting to fix it in the right way, while you wanted a quick hack for linaro
Jun 15 11:08:16 <cwillu_at_work> not seeing the problem
Jun 15 11:08:19 <lool> JameswStubbs: Gtk+ is the toolkit used in GNOME, but it's not the full GNOME environment
Jun 15 11:08:20 <cwillu_at_work> gtk isn't all of gnome
Jun 15 11:08:35 <lool> zumbi: This is incorrect
Jun 15 11:08:44 <JameswStubbs> So what do I need to enter into apt-get to get gtk?
Jun 15 11:08:49 <JameswStubbs> apt-get install gtk??
Jun 15 11:09:19 <lool> zumbi: Linaro is investing time in fixing it the right way, hrw is working on that, but it will take a while so I've asked him to produce intermediate builds the "old" way (regular Emdebian way) in the mean time
Jun 15 11:09:33 <lool> zumbi: there is no additional hack than the existing Emdebian binary-cross stuff
Jun 15 11:09:56 <lool> JameswStubbs: the matchbox-session package should depend on the libgtk package
Jun 15 11:10:00 <lool> JameswStubbs: So this should just all work
Jun 15 11:10:11 <lool> JameswStubbs: I fail to understand your actual problem   :-(
Jun 15 11:10:18 <hrw> lool: patch was yours
Jun 15 11:10:33 <hrw> lool: and I do not provide them outside of my hdd
Jun 15 11:10:43 <lool> hrw: You mean the build fixes?
Jun 15 11:10:44 <zumbi> lool: sure, but Emdebian way only works for armel (also sh4) but the rest of arches were broken
Jun 15 11:10:51 <JameswStubbs> I'd copy and paste it all but it's within 2 vm's :) , When I enter matchbox-session from the prompt, it says something like gtk: couldnt open
Jun 15 11:10:57 <lool> hrw: These are not additional hacks though, they just fix bugs in the current approach, do you agree?
Jun 15 11:11:09 <zumbi> lool: i agree
Jun 15 11:11:16 <hrw> lool: they are fixes, yes
Jun 15 11:11:29 <lool> zumbi: We didn't look into that, we don't have people blocking on cross-compilers for the arches you mention
Jun 15 11:11:47 <lool> zumbi: I would hope that everything will work once hrw is done, but we don't need to produce daily cross-compilers for sparc or powerpc in Linaro right now
Jun 15 11:12:04 <lool> zumbi: We do need to hand out some armel cross-compilers while hrw continue on the quest to clean cross-compilers builds
Jun 15 11:12:21 <lool> JameswStubbs: Ok, you need to be more specific though
Jun 15 11:12:30 <JameswStubbs> Ok I'll try
Jun 15 11:13:03 <zumbi> lool: while I understand you focus on armel (which is primary) I'll try to work on the rest of arches (at least test builds)
Jun 15 11:13:08 <lool> JameswStubbs: (IIUC, you installed only Ubuntu packages in your rootfs, but you see some error messages with gtk, can only comment if we know what the error is)
Jun 15 11:13:23 <lool> zumbi: As I said, I expect the *final* solution to work on other arches
Jun 15 11:13:35 <zumbi> `buildcross` could easily be used to test all cross compiler arches
Jun 15 11:13:42 <lool> zumbi: But I asked hrw to provide hand-built packages *right now* because we need them, we don't need them for other arches than armel
Jun 15 11:13:57 <zumbi> lool: i got it. thanks :)
Jun 15 11:14:01 <lool> Ok  :-)
Jun 15 11:14:24 <JameswStubbs> I've made a rootfs using rootstock. I've then opened it in qemu. I then installed xorg. I then installed matchbox. Now when I enter matchbox-session is returns: (matchbox-desktop:434) : Gtk-Warning **: cannot open display:
Jun 15 11:15:05 <lool> JameswStubbs: Do you run matchbox-session from within Xorg?
Jun 15 11:15:18 <JameswStubbs> Should I enter startx
Jun 15 11:15:31 <JameswStubbs> Then when I get the x shell then enter matchbox-session?
Jun 15 11:15:49 <lool> JameswStubbs: matchbox-session should be started from within a Xorg context, otherwise it doens't know which Xorg DISPLAY to connect to or which credential (XAUTHORITY) to use
Jun 15 11:16:20 <lool> JameswStubbs: I'm not sure what the proper way is to start matchbox-session on boot or to start Xorg + matchbox-session, perhaps startx will do the trick, perhaps you need to setup more things
Jun 15 11:16:54 <lool> JameswStubbs: One way to quickly test matchbox-session is to start Xorg with a xterm and then run matchbox-session from there, but that's certainly not what you would want in the end I guess
Jun 15 11:16:55 <JameswStubbs> I think I need to add match-box session to xinitrc
Jun 15 11:17:12 <lool> Yes, it is indeed possible you have to do that
Jun 15 11:28:01 <JameswStubbs> Hm, All I'm getting after adding matchbox-session to xinitrc is a blackscreen and a mouse, which I can't move.
Jun 15 11:31:40 <JameswStubbs> Any ideas lool?
Jun 15 11:57:03 <lool> JameswStubbs: Check the xinit man page, and/or read through /etc/X11/Xsession.d/* scripts and /etc/X11/Xsession
Jun 15 11:57:23 <lool> JameswStubbs: I don't have a recipe for you, as I didn't do this myself, but it should be easy to look into what the shell scripts are doing
Jun 15 11:57:33 <lool> JameswStubbs: I think one important thing is to have .xinitrc +x or something like that
Jun 15 11:57:54 <lool> and you need a shebang too if you do this obvisouly
Jun 15 11:58:15 <JameswStubbs> shebang? !#?
Jun 15 11:58:40 <lool> #!/bin/sh
Jun 15 12:00:02 <lool> JameswStubbs: I checked and if you look at startx, it will pass xinitrd to xinit which expects to be passed a client program
Jun 15 12:00:13 <lool> So if you pass it a text file, it wont work
Jun 15 12:47:55 <asac> ogra_cmpc: where is rcn? isnt he usually hanging out here?
Jun 15 12:48:57 <lool> asac: 16:10 < cwillu_at_work> okay, that's a week since rcn was last on, anybody want  to come with me on a rescue mission? :p
Jun 15 12:49:00 <lool> asac: 17:09  * cwillu_at_work found rcn
Jun 15 12:49:14 <cwillu_at_work> asac, he should be back today
Jun 15 12:49:20 <cwillu_at_work> took an unannounced vacation
Jun 15 12:50:13 <asac> ah ... one of the weak ones ;)
Jun 15 12:51:23 <armin76> he's running from you :D
Jun 15 12:51:28 <armin76> *away
Jun 15 12:51:38 <cwillu_at_work> I was wondering about that actually :p
Jun 15 12:53:18 <cwillu_at_work> omg
Jun 15 12:53:23 <cwillu_at_work> that's embarrasing
Jun 15 12:53:38 <cwillu_at_work> I've got a webapp I run in an undecorated fullscreen firefox window
Jun 15 12:53:43 <cwillu_at_work> been having horrible performance
Jun 15 12:54:03 <cwillu_at_work> firefox using 60-80% cpu, with the backend server using the other 20%
Jun 15 12:54:14 <cwillu_at_work> (backend has to poll a bunch of serial devices and push data to firefox)
Jun 15 12:54:28 <cwillu_at_work> figured it was just the overhead of updating things / the push system
Jun 15 12:54:39 <cwillu_at_work> finally got around to getting venkman on it
Jun 15 12:56:03 <cwillu_at_work> a completely unrelated piece of code was in a hard mutually recursive loop:  initializing a drop-down menu was triggering a request to get data, and the request handler was triggering an init of the drop-down
Jun 15 12:57:32 <cwillu_at_work> the embarrassing part is that I've been working under the false assumption for long enough to have actually shipped this to customers :p
Jun 15 14:22:56 <hrw> http://people.canonical.com/~hrw/ubuntu-maverick-armel-cross-compilers/ contains now amd64 and i386 cross toolchains for armel target
Jun 15 15:22:03 <rsavoye> hrw: is there a branch for the source used to build your cross toolchain ?
Jun 15 15:22:23 <hrw> rsavoye: I used ubuntu sources
Jun 15 15:22:26 <hrw> will add README
Jun 15 15:22:37 <rsavoye> so no Code Sourcery patch yet ?
Jun 15 15:22:46 <hrw> not yet
Jun 15 15:23:07 <rsavoye> you hacked libstdc++ and libiberty to cross configure ?
Jun 15 15:23:44 <rsavoye> hrw: there is a nice patch in GCC trunk for Android you might want to add when you get to patching 4.4
Jun 15 15:23:58 <rsavoye> all it does is cleanup linking mostly
Jun 15 15:24:24 <hrw> rsavoye: url?
Jun 15 15:24:42 <rsavoye> the thread is at http://www.pubbs.net/201005/gcc/37284-patch-06-add-support-for-android.html
Jun 15 15:25:06 <rsavoye> it's based on my older Android patch, and adds bionic support in a nice generic way
Jun 15 15:25:40 <lool> hey rsavoye
Jun 15 15:25:48 <rsavoye> howdy
Jun 15 15:26:01 <lool> rsavoye: Might make sense for you folks to discuss this on #linaro, but here is fine too
Jun 15 15:26:14 <rsavoye> ah, didn't think of that, thanks
Jun 15 15:26:50 <rsavoye> I was just hacking on ARM toolchains this weekend for Gnash, so pipped up when I saw the link to debs
Jun 15 20:16:18 <fabrice_sp> Hi. Just as a follow up of last time I connected (About atlas build on arm): I'll upload atlas as someone has been able to build it in qemu
Jun 15 20:16:37 <fabrice_sp> in case it loops, who should I poke to kill it?
Jun 15 21:06:08 <tumbleweed> ogra: I'm still getting a fair number of qemu segfaults with lucid
Jun 16 00:22:56 <cwillu_at_work> tumbleweed, qemu had fixed any of those?
Jun 16 00:24:48 <tumbleweed> cwillu_at_work: no, same problem with the current git head
Jun 16 00:25:27 <tumbleweed> I was trying to test a few FTBFS bugs, but it seems that qemu just isn't a workable solution for this
Jun 16 00:25:48 <cwillu_at_work> qemu-static-arm should work fine though
Jun 16 00:26:03 <cwillu_at_work> with the added bonus that you can use all of the cores of your desktop
Jun 16 00:26:14 <tumbleweed> hmm, I haven't tried that
Jun 16 00:26:19 <cwillu_at_work> I've hacked up my rootstock to work via chroot, works great
Jun 16 00:26:51 <cwillu_at_work> <3 asac or lool or whoever told me to try it
Jun 16 00:26:59 <tumbleweed> heh
Jun 16 00:27:24 <tumbleweed> any recommended way to do that? pbuilder integration would be awesome :P
Jun 16 00:28:06 <cwillu_at_work> just change runvm to chroot, calling installer directly
Jun 16 00:28:19 <cwillu_at_work> oh, and fix up the script to not do things like reboot, obviously
Jun 16 00:28:34 <cwillu_at_work> haven't done anything with pbuilder
Jun 16 00:28:48 <tumbleweed> ok, i'll have a shot in the morning (2 30 am)
**** ENDING LOGGING AT Wed Jun 16 02:59:56 2010