[08:20] <lag> cooloney: ping
[08:22] <cooloney> lag: yeah,
[08:22] <lag> cooloney: Good morning
[08:22] <cooloney> lag: morning, man
[08:22] <lag> Is the OMAP4 repo on our server yet?
[08:23] <amitk> morning guys!
[08:23] <lag> Morning Amitk
[08:24] <amitk> I heard that we have a newly-rebased tree from TI?
[08:24] <cooloney> lag: yeah, i just synced one from sebjan
[08:24] <cooloney> and he is trying to unify the panda code into his tree
[08:25] <lag> Great
[08:25] <cooloney> i will pull from him after that and built for you guys for testing
[08:25] <amitk> what version is the tree based on cooloney ?
[08:25] <lag> What's it' called?
[08:25] <cooloney> lag: do you have other omap4 hardware instead of panda?
[08:25] <cooloney> amitk: oh it is based on TI 2.6.34 integration tree
[08:26] <lag> No, just Panda
[08:26] <hrw> morning
[08:26] <lag> I'm guessing it would be called ubuntu/ubuntu-lucid-arm.git
[08:26] <comradekingu> Gnome bytter ut F-spot med shotwell
[08:26] <comradekingu> Wrong chan, sorry
[08:27] <cooloney> lag: lucid-arm.git? no, the new branch is for maverick
[08:27] <lag> I'm guessing it would be called ubuntu/ubuntu-maverick-arm.git
[08:27] <lag> ;)
[08:28] <amitk> why is it a separate tree and not a branch in the maverick git tree?
[08:28] <lag> I understood that it's not ready to go into the main repo yet
[08:29] <lag> I was chatting with cooloney and ogra about it the other day
[08:29] <cooloney> lag: http://kernel.ubuntu.com/git?p=roc/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-ubuntu-2.6.34
[08:30] <cooloney> that is a temp branch in my repo
[08:30] <lag> Okay
[08:30] <lag> And after?
[08:30] <cooloney> after it is ready, i will push it out for review and merge into maverick
[08:30] <cooloney> amitk ^^
[08:30] <amitk> ok
[10:29] <lag> cooloney: ping
[11:01] <cooloney> lag: could you please try the kernel from http://people.canonical.com/~roc/kernel/omap4-2.6.34-panda/ on your panda?
[11:03] <lag> Was it built from roc/ubuntu-maverick.git
[11:03] <cooloney> lag: yeah, it is
[11:03] <cooloney> lag: i cross built it locally
[11:04] <lag> By locally, do you mean on 'your' machine?
[11:04] <lag> I am building the same kernel currently on one of the build servers
[11:04] <cooloney> lag: yes, on my machine, since i failed to use sbuild on tyler
[11:04] <cooloney> lag: aha, cool, are you using sbuild?
[11:05] <lag> No idea
[11:05] <lag> Whatever's specified in the chroot
[11:06] <lag> I guess so, as I received an sbuild error this morning when the permissions were messed up
[11:08] <cooloney> lag: yeah, me2, so i switched to my local builder
[11:09] <lag> Well once the maverick-armel issue is sorted apw will have it available again within 2 mins
[11:10] <apw> lag its not that simple
[11:10] <apw> but i am working on it
[11:10] <lag> Is it not the same issue as the other build server?
[11:10] <apw> lag no
[11:10] <lag> You nailed that in moments few
[11:10] <apw> as in the machine is now working for you, but not for him
[11:10] <lag> Ok, sorry for giving false hope :)
[11:10] <lag> Oh, that sucks
[11:11] <lag> (for him)
[11:11] <lag> :)
[11:11] <apw> there is a collision due to two different chroot types, a normal one, and a union one for hard builds
[11:12] <lag> I'll not pretend to know a great deal about chroot architecture. I thought they were just different directories each with their own TLD in
[11:18] <apw> lag, nope they arn't quite.  well they are in the normal case which you use to build, and are union mount overalys in the case of the sbuild use case
[11:18] <apw> and by default they use the same names and everything breaks
[11:19] <apw> i think i have it sorted out though
[11:22] <lag> Good stuff
[11:24] <cooloney> apw: ok, let me try again.
[11:25] <apw> cooloney, not fixed yet
[11:25] <lag> !Good stuff
[11:25] <apw> cooloney, i'll let you know when we are there
[11:25] <ubot2> Factoid 'Good stuff' not found
[11:25] <apw> lag, i am waitng on a new chroot building
[11:25] <cooloney> apw: no, failed again. ok, no problem.
[11:26]  * lag gigges - "stupid bot"
[11:26] <apw> cooloney, yep i know
[11:26] <apw> sbuild -d sbuild-maverick-armel PACKAGE*.dsc
[11:26] <apw> cooloney, could you try again now, note the sbuild- prefix on the chroot name as above
[11:29] <cooloney> apw: thanks a lot, man. it is running now
[11:29] <cooloney> apw: i guess you created a new chroot named sbuild-maverick-armel?
[11:30] <apw> cooloney, yes, as it needs to be a different form from the normal ones, in which changes are persistant
[11:30] <apw> i've only make one on that machine and only for maverick
[11:30] <apw> now i know it works i'll get with rtg to get them made across the board
[11:31] <cooloney> apw: ok, very nice, thx.
[11:31] <apw> cooloney, if you need a different release made let me know
[11:33] <cooloney> apw: one more sbuild-lucid-armel is better.
[11:33] <apw> cooloney, you need lucid yes ?
[11:34] <cooloney> apw: yeah, i might use it for build ti-omap and fsl-imx51
[11:34] <apw> cooloney, ok, its building now will let you know when its done
[11:34] <cooloney> apw: currently, i focus on ti-omap4 for M
[11:34] <apw> yp
[11:35] <cooloney> apw: thanks a lot.
[11:35] <apw> i suspect we'll make them all as they are pretty cheap
[11:35] <cooloney> yeah, i think so, and are those schroot setup scripts in our kteam-tools?
[11:44] <amitk> cooloney: lag: how are we doing on the bugs in omap support in lucid?
[11:44] <amitk> can one of you take up the USB OTG bug
[11:44] <amitk> ?
[11:46] <lag> amitk: I am still quite tied up with a suspend-resume bug, but I can take a look for you if you like?
[11:49] <amitk> lag: please do, assuming you have a beagleboard now
[11:50] <lag> I do not :(
[11:51] <amitk> does either mporier or cooloney have one?
[11:51] <lag> Just my lonely panda - no wonder they're going extinct
[11:51] <amitk> most zoos would love to get a panda :)
[11:51] <lag> I couldn't tell you
[11:55] <cooloney> amitk: i'd love to do that. but i don't have beagleboard and panda
[11:55] <cooloney> amitk: what's the USB OTG bug?
[11:56] <cooloney> i saw some fixing in 2.6.34 kernel
[11:57] <amitk> cooloney: we need to find patches and fix configuration so the USB OTG works in Lucid
[11:59] <cooloney> amitk: ok, any bug on LP? i do love to do that.
[11:59] <lag> cooloney: That image works
[12:00] <cooloney> lag: thanks for the testing.
[12:00] <lag> But has a heart attack when a monitor is plugged in via HDMI
[12:02] <cooloney> lag: do you think that is the first time you meet that?
[12:02] <amitk> cooloney: lag: you should bookmark this page -> https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap/
[12:02] <cooloney> no such thing in .33 kernel?
[12:03] <cooloney> amitk: got it. thx
[12:06] <lag> amit: I already have it, thanks
[12:06] <lag> cooloney: bug592295
[12:07] <lag> cooloney: bug 592295
[12:07] <ubot2> Launchpad bug 592295 in linux-ti-omap (Ubuntu) "omapdss DISPC error: SYNC_LOST_DIGIT (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/592295
[13:26] <lag> cooloney: Are you still around?
[14:39] <cwillu_at_work> cwillu@lucid-zippy:~$ sudo modprobe usbhid
[14:39] <cwillu_at_work> [sudo] password for cwillu:
[14:39] <cwillu_at_work> [  400.146759] usbhid: unknown relocation: 3
[14:39] <cwillu_at_work> FATAL: Error inserting usbhid (/lib/modules/2.6.35-rc3-dl0/kernel/drivers/hid/usbhid/usbhid.ko): Invalid module format
[14:39] <cwillu_at_work> that doesn't strike me as the sort of thing that should be possible :p
[14:47] <rsavoye> does anyone know the url for gcc 4.4 in Maverick for ARM ?
[14:47] <rsavoye> I dug around on launchpad, but only found lp:ubuntu/gcc-4.4
[15:02] <cwillu_at_work> rsavoye, http://ports.ubuntu.com/ubuntu-ports/pool/universe/g/gcc-4.4/
[15:08] <rsavoye> is there a bzr branch for it ?
[15:09] <cwillu_at_work> apt-get source it, it'll tell you if there is
[15:09] <cwillu_at_work> but yes, probably
[15:09] <rsavoye> I wanted to check the level of ARM patches
[15: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
[15:10] <cwillu_at_work> https://launchpad.net/ubuntu/+source/gcc-4.4
[15:11] <rsavoye> that looks like it, thanks
[15:11] <zumbi> rsavoye: afaik, doko uses debian svn for gcc devel, svn.debian.org -- project: gcccvs
[15:12] <rsavoye> I wanted to check the code sourcery patches for ARM, which aren't in the Debian sources
[15:12] <rsavoye> there are some new patches in gcc trunk for Android I was going to migrate
[15:13] <zumbi> rsavoye: http://svn.debian.org/wsvn/gcccvs/branches/sid/gcc-4.5/debian/patches/#_branches_sid_gcc-4.5_debian_patches_
[15:13] <rsavoye> right, but this patch I don't believe is in debian at all
[15:13] <zumbi> rsavoye: where are CS patches at?
[15:13] <rsavoye> got me, but I heard there was one for ARM stuff
[15:14] <zumbi> well, there are tons of fixes and patches for ARM
[15:14] <rsavoye> as the CS sources haves fixes for 4.4 based on 4.6
[15:15] <rsavoye> not a huge big deal, I was just doing some Android toolchain hacking and thought maybe I'd check
[15:15] <zumbi> they backport 4.6 development into 4.4 (probably for next release)
[15:15] <rsavoye> yes
[15:15] <rsavoye> maybe it's not merged in yet
[15:15] <zumbi> well, g'luck!
[15:16] <rsavoye> Guess I'll stick to my build of 4.5 for now.
[15:22] <wocao> where is the soucelist for  arm
[15:29] <cwillu_at_work> wocao, how do you mean?
[15:29] <amitk> sources.list?
[15:29] <amitk> sauce list?
[15:29] <amitk> :)
[15:30] <ogra> yum
[15:30] <ogra> sauce
[15:35] <wocao> sourcelist for arm platform
[15:36] <wocao> ?
[15:36] <wocao> where i can fine
[15:36] <wocao> where i can find
[15:37] <ogra> in /etc/apt/
[15:41] <cwillu_at_work> wocao, deb ports.ubuntu.com/ubuntu-ports lucid main universe
[16:09]  * cwillu_at_work found rcn
[16:59] <mpoirier_> lag: what was that ?
[17:10] <lag> amitk: Ping
[17:13] <lag> Ogra: Ping
[17:19] <ogra__> lag, yep ?
[17:19] <lag> If I'm fixing bugs for Panda, which tree should I be using?
[17:20] <lag> Things seem a little scattered
[17:20] <ogra> no idea, cooloney should have created one on the server
[17:20] <lag> He has one for Maverick
[17:20] <ogra> right
[17:20] <lag> Hang on
[17:20] <ogra> panda will be maverick
[17:21] <lag> He has one for Maverick in his own area
[17:21] <ogra> hmm
[17:21] <lag> Will panda only be Maverick?
[17:21] <ogra> then i dont know
[17:21] <ogra> yes
[17:21] <lag> I have a working Lucid kernel?
[17:21] <Martyn> good morning
[17:21] <ogra> lag, we wont add new kernels to lucid :)
[17:21] <ogra> its released
[17:22] <lag> Okay, but the Maverick one doesn't work on Panda yet?
[17:22] <lag> Or does it?
[17:22] <ogra> no idea
[17:22] <ogra> afaik we dont have binaries yet
[17:22] <Martyn> I've nearly finished the first set of ARM symbol de-dup patches.   I honestly had no idea how much work I had signed up for at UDS.  This is tough, tough work
[17:22] <ogra> so i havent tested anything yet
[17:22] <lag> Okay
[17:23] <ogra> we got the branch on friday afaik
[17:23] <lag> So I can't fix Panda bugs yet then, is that what you're saying?
[17:23] <Martyn> I thought it would be easy to separate the functions out .. but it wasn't.
[17:23] <Martyn> ogra : What's new?
[17:23] <ogra> lag, do we do have bugs for omap4 yet ?
[17:24] <ogra> since there is no package in the archive yet i doubt we do
[17:24] <lag> I have filled one
[17:24] <lag> But that was with the Lucid kernel!
[17:24]  * lag head explodes 
[17:24] <lag> 's*
[17:24] <ogra> which was just a build of the plain TI omap4 upstream kernel
[17:25] <ogra> we dont have the actual kernel yet we will use
[17:25] <lag> Okay, I guess that clears things up
[17:25] <lag> Phew!
[17:25] <ogra> the lucid package you use was just a quick build of what was available to get the boards up at all
[17:25] <lag> Got you
[17:26] <ogra> the actual kernel package we will use has to be built by cooloney first, would probably be best to ask if you can help him with that
[17:26] <ogra> since thats the current blocking factor
[17:26] <lag> Okay, I'll have a word with him tomorrow
[17:27] <ogra> what was your bug about ?
[17:27]  * cwillu_at_work continues happily using his working rcn kernels :)
[17:27] <ogra> clearly a kernel issue ?
[17:27] <lag> HDMI
[17:27] <lag> Yeah
[17:27] <ogra> k
[17:27] <lag> https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap/+bug/592295
[17:27] <ubot2> Launchpad bug 592295 in linux-ti-omap (Ubuntu) "omapdss DISPC error: SYNC_LOST_DIGIT (affects: 1) (heat: 6)" [Undecided,New]
[17:28] <cwillu_at_work> now, if only I could get firefox to stop crashing when using webworkers
[17:28] <Martyn> When did the Panda board support go into the kernel?
[17:28] <ogra> Martyn, not yet
[17:29] <Martyn> *nod*  The only thing I've seen so far was the proposed patch by David Anders, and it missed the patch window (just like the Smooth-Stone patch missed it)
[17:29] <Martyn> Both then end up on hold until 2.6.36
[17:45] <tumbleweed> I'm trying to replicate http://launchpadlibrarian.net/49300098/buildlog_ubuntu-maverick-armel.hdf5_1.8.4-patch1-2_FAILEDTOBUILD.txt.gz in qemu but it keeps segfaulting at the same point in the build processes
[17:46] <tumbleweed> are qemu-system-arm segfaults the norm?
[17:56] <ogra> tumbleweed, depneds what kernel you use
[17:57] <tumbleweed> ogra: the versatile kernel in the repos doesn't work with my qemu
[17:58] <tumbleweed> so I'm using the one from http://ports.ubuntu.com/ubuntu-ports/dists/lucid/main/installer-armel/current/images/versatile/netboot/
[17:59] <ogra> thats the same kernel as the archive kernel
[17:59] <ogra> but thats alright then, you shouldnt see segfaults
[18:00] <tumbleweed> ogra: it doesn't seem to be. md5sums don't mathc
[18:00] <tumbleweed> also 2.8M vs 3M
[18:00] <ogra> well, debian-installer just pulls the binary out of the package
[18:00] <ogra> when it builds the netinstall kernel
[18:01] <tumbleweed> with a HEAD qemu and the archive kernel: http://paste.ubuntu.com/449748/
[18:01] <ogra> oh
[18:02] <ogra> you should mention that you dont use the ubuntu qemu
[18:02] <tumbleweed> I was getting it with ubuntu qemu first, tried git after that
[18:02] <tumbleweed> actually haven't tried ubuntu qemu with the archive kernel. does that
[18:03] <ogra> vmlinuz-2.6.35-2-versatile ?????
[18:03] <ogra> thats not a lucid kernel
[18:03] <tumbleweed> ogra: maverick
[18:04] <tumbleweed> aah, right
[18:04] <ogra> right, thats untested yet :)
[18:04] <ogra> theoretically it should work though
[18:05] <ogra> there were no changes to the versatile branch to my knowledge
[18:05] <ogra> apart from newer upstream
[18:06] <tumbleweed> ok. I see no bugs. I'll file one
[18:06] <ogra> great, thanks
[18:06] <ogra> anyway, your build log seems to have a SIGILL
[18:07] <ogra> could be a toolchain issue
[18:07] <tumbleweed> yeah, I saw that. Tried to replicate, and got sidetracked by this
[18:07] <ogra> since it happens during linking
[18:07] <tumbleweed> I tihnk it cgot past that, though
[18:08] <ogra> are you using a lucid rootfs in your vm image ?
[18:08] <tumbleweed> maverick
[18:08] <ogra> ah
[18:09] <cwillu_at_work> what's the newest firefox build available for arm?
[18:10] <cwillu_at_work> i.e., does anyone have 3.7 builds?
[18:10] <ogra> i dont think so
[18:10] <ogra> theer was no firefox upload to maverick yet
[18:11] <ogra> so the latest in the archive must be the lucid version
[18:11] <cwillu_at_work> :/
[18:11] <cwillu_at_work> building firefox isn't fun :*(
[18:12] <ogra> i dont know if there is any PPA with dailies of trunk
[18:12] <ogra> asac would know such stuff
[18:13] <asac> cwillu_at_work: ogra: https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[18:13] <asac> not for armel ;)
[18:13] <ogra> right, thats what i suspected
[18:14] <asac> but firefox 3.7 is there ... which afaik is now branched ... so trunk might be missing temporarily
[18:14] <cwillu_at_work> asac, I suppose I could apt-get source it myself :/
[18:14] <asac> cwillu_at_work: yep
[18:14] <asac> cwillu_at_work: is there any important reason why we should try a ffox 3.7 build?
[18:14] <ogra> tahts great, you can tell us about build failures in advance then :)
[18:14] <asac> if there is a good reason (like important bug fix landing for arm that needs landing), i spin that in a ppa
[18:15] <cwillu_at_work> asac, I can crash a 3.6 build at will by running my app on it?
[18:15] <cwillu_at_work> no idea if it's fixed yet, but it's annoying enough to duplicate that I really want it to get fixed by accident :p
[18:16] <asac> cwillu_at_work: do you see that problem o intel too?
[18:16] <cwillu_at_work> yep
[18:16] <asac> then test it with that ppa
[18:16] <ogra> and it worked on former releases i assume
[18:16] <cwillu_at_work> asac, have been, so far so good
[18:16] <asac> intel builds are avail there ;)
[18:16] <cwillu_at_work> ogra, no, webworkers didn't exist previously
[18:16] <ogra> ah
[18:16] <cwillu_at_work> but they're a pretty big win performance wise in my case
[18:16] <tumbleweed> ogra: gaaah. wrong terminal. ubuntu qemu boots the maverick kernel fine, sorry
[18:16] <ogra> phew
[18:17]  * ogra wipes the sweat off his forehead 
[18:18] <ogra> tumbleweed, what i would try is to build the package in the same vm inside a lucid chroot, if thta succeeds its most likely a toolchain issue
[18:20] <tumbleweed> brb supper
[18:28] <ojn> Martyn: I didn't see patches for either go by on arm-kernel. Where were they posted? (panda and smooth-stone support)?
[18:31] <tumbleweed> ogra: when I say "boots fine" I mean it says "booting the kernel" and then hangs at 100% CPU
[19:02]  * gsnedders found the reason why the BeagleBoard he has wasn't working properly: the NAND is b0rked.
[23:35] <cwillu_at_work> ogra, well, I seem to be stable given some code modifications on 3.6.6 from the nightlies
[23:35] <cwillu_at_work> on x86