[01:45] <Baybal> hmmm??!
[02:03] <prpplague> ho ho hum
[02:03] <prpplague> is it friday yet?
[02:41] <Baybal> my cellphone went crazy and tried to launch irc client on himself
 There's a deadlock which occurs when you use more than a certain number of pthreads in a single ARM program, running inside qemu-arm.
[03:51] <cwillu> sound familiar? :)
[07:48] <ebrahim> Hi
[07:50] <lamp_> Hi
[07:51] <lamp_> mouse and kayboard not working
[07:51] <lamp_> writing  ubuntu-10.04-netbook-armel+omap.img on sd and cheng boot.scr
[07:51] <lamp_> to folowing:
[07:51] <lamp_> fatload mmc 0:1 0x80000000 /casper/uImage
[07:52] <lamp_> fatload mmc 0:1 0x81600000 /casper/uInitrd
[07:52] <lamp_> setenv bootargs quiet splash vram=12M omapfb.mode=dvi:
[07:52] <lamp_> 1280x720MR-16@60  fixrtc file=/cdrom/preseed/ubuntu-netbook.seed  --
[07:52] <lamp_> boot=casper only-ubiquity nocompcache mpurate=720 console=tty0
[07:52] <lamp_> console=ttyS2,115200n8
[07:52] <lamp_> bootm 0x80000000 0x81600000
[07:52] <lamp_> booting beagleboard and see this error:
[07:52] <lamp_>    hub 1-0:1.0: unable to enumerate USB device on port 2
[07:52] <lamp_> My mouse and keyboard not working, how to resolve this problem ?
[07:52] <lamp_> tanks
[07:52] <lamp_>  On C4 beagleboard
[07:54] <lamp_> ?
[07:54] <lamp_> ?
[08:20] <hrw> morning
[08:21] <DanaG> say, anyone have experience with webcams on a beage?
[08:32] <amitk> try #beagle
[08:32] <amitk> lamp_: have you connected to the ehci host port or the otg port?
[08:33] <amitk> lamp_: and are they connected directly or through a usb hub? (A hub is required)
[08:33] <lamp_> ehci
[08:33] <lamp_>  connected directly
[08:38] <amitk> lamp_: directly won't work, you need to connect it through an externally powered hub
[08:47] <lamp_> even otg port
[08:48] <lamp_> flash usb working on directly connect
[08:49] <lamp_> flash usb working on directly connect to ehci
[08:50] <lamp_> sell  externally powered hub ?
[08:50] <amitk> ?
[08:59] <lamp_> Are you sure that buying a  externally powered hub The 'hub 1-0:1.0: unable to enumerate USB device on port 2' problem is solved?
[09:02] <cooloney> amitk: can you use codesourcery 2010q1 cross compiler to build our maverick kernel package for omap3
[09:14] <amitk> cooloney: I haven't tried it. I stick to old CS toolchains in general :)
[09:14] <cooloney> amitk: sorry for bothering, i just tried that, it works.
[09:36] <lool> amitk: Eh you should dogfood or cross-compiler packages!!
[09:44]  * ogra thinks we need more builders ... 50 package in queue and all builders blocked :(
[09:46] <amitk> lool: I'm running maverick on the laptop, so I do a bit of dog-fooding there. I wish we had lucid packages though
[09:47] <lool> amitk: they don't install on lucid?
[09:47] <amitk> lool: they didn't last I tried (a few weeks ago)
[09:48] <lool> amitk: I'd be curious whether that's still the case
[09:48]  * amitk re-adds hrw's repo to sources.list
[09:49] <hrw> amitk: why not /etc/apt/sources.list.d/hrw-cross-compilers.list instead?
[09:49] <hrw> easier to enable/disable
[09:49] <amitk> hrw: that's what I'll do, much longer to type though ;)
[09:49] <hrw> ;d
[09:51] <amitk> hrw: is there a meta package?
[09:51] <hrw> amitk: nope
[09:52] <hrw> amitk: for kernel you only need gcc-4.4-arm-linux-gnueabi I think
[09:54] <amitk> hrw: lool: http://pastebin.ubuntu.com/483859/ (needs libmpfr4)
[09:56] <hrw> they are for *maverick*
[09:57] <lool> hrw: Would it be possible to build them under lucid?
[09:57] <amitk> hrw: that's what you told me the last time, but I repeated the experiment because lool asked me to :)
[09:58] <lool> amitk: Given that the toolchain is relatively self contained, I was hoping these would be installable on lucid
[09:58]  * amitk feels that lucid being LTS should be a target
[09:59] <hrw> lool: some backports from maverick would be needed probably
[09:59] <lool> amitk: You could most probably install libmpfr4 from maverick though   ;-)
[09:59] <lool> hrw: Yeah
[09:59] <lool> hrw: How far are you from a toolchain package for the archive?
[09:59]  * ogra tries to pronounce libmpfr4
[09:59] <ogra> ... and fails :P
[10:01] <hrw> lool: need to solve stage3 problems
[10:01] <hrw> ~curse ubuntu for not using sysroot
[10:02] <lool> Don't do native for linux, it's heavy   :-(
[10:02] <hrw> ?
[10:03] <ogra> lool, arent all our linux packages native anyway ?
[10:03] <lool> 90+ MB
[10:04] <amitk> ogra: it is libmp-4-french people ;)
[10:04]  * ogra thought the packaing tree merge happens on a git level
[10:04] <ogra> amitk, lol
[10:04] <hrw> amitk: you use amd64?
[10:04] <amitk> hrw: yes
[10:06] <hrw> good. deboostrap lucid in progress
[10:10] <amitk> hrw: thanks! Let me know when to test
[10:22] <hrw> ok
[10:29] <hrw> amitk: one more thing - you will get maverick gcc not lucid
[10:39] <amitk> hrw: that is fine
[10:42] <hrw> anyway - first lucid one
[10:43] <hrw> I am curious what will it bring and how will look
[10:47] <ynezz> where can I find content of hrw-cross-compilers.list ? :)
[10:49] <lool> ynezz: At the top of http://people.canonical.com/~hrw/ubuntu-maverick-armel-cross-compilers/
[10:49] <lool> deb http://people.canonical.com/~hrw/ubuntu-maverick-armel-cross-compilers/ ./
[10:49] <lool> etc.
[10:49] <lool> Currently maverick-only
[11:04] <asac> XorA: hi
[11:04] <asac> oops
[11:04] <asac> -> linaro
[11:20] <lag> rsalveti: ping
[11:25] <hrw> amitk: lucid require too many backports to build maverick cross toolchain. better grab maverick one and add all needed maverick libs
[11:33] <ynezz> hrw@canonical? what a change :)
[11:33] <hrw> ynezz: its 4 months now
[11:34] <ynezz> ah, didn't noticed
[11:40] <ynezz> does it mean, that ubuntu is switching from native to cross? :)
[11:40] <ogra> no
[11:40] <persia> Very much not!
[11:40] <ogra> it means that developers can do cross builds if needed
[11:40] <ynezz> ok
[11:40] <ogra> ubuntu will never switch from native to cross
[11:45] <ogra> lool, bug 624568 FYI
[11:45] <ubot2> Launchpad bug 624568 in busybox (Ubuntu) "building busybox without -marm on armel makes several binaries unusable (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/624568
[11:49] <XorA> asac: hi
[11:50] <asac> hey XorA ;)
[11:50] <asac> XorA: so the maverick stack is now more or less ready to start working on things
[11:51] <asac> XorA: you can intall mutter and then just install
[11:51] <asac> libclutter-eglx-es20-1.0-0
[11:51] <asac> to flip to egl
[11:51] <asac> XorA: to implement the extension we talked to about just do a apt-get source libclutter-eglx-es20-1.0-0 ... and then look at the texture_pixmap function in the gles tree
[11:51] <hrw> ynezz: cross builds are option for developers to not wait 3 days for kernel rebuild but have it done in short time
[11:51] <hrw> etc
[11:52] <asac> XorA: -> #linaro ;)
[12:10] <ogra> NCommander, please bump https://edge.launchpad.net/ubuntu/+source/u-boot-linaro/2010.06-695-gbd23130-linaro-0ubuntu1/+build/1934915 to $very_high
[12:10]  * persia encourages asking random buildd admins for such things in #ubuntu-devel: tends to avoid timezone limitations
[12:11] <ogra> i *like* to nag NCommander directly :P
[12:11] <persia> (as in "Could a buildd admin please ...")
[12:11] <persia> Yeah, but doesn't help if he's not around.
[12:11] <ogra> i usually fall back to that if he's not around
[12:11] <persia> I'm 90% certain that's the case now, although I may be mistaken.
[12:16] <lag> ogra: If I can get your XM to do this: http://paste.ubuntu.com/483904/
[12:16] <lag> ogra: Can you start working on it?
[12:16] <lag> (again)
[12:17] <ogra> lag, i'll try soon, i'm currently a bit busy aith panda
[12:17] <ogra> *with
[12:17] <ogra> lag, thats with todays image ?
[12:18] <lag> ogra: No
[12:18] <lag> ogra: Today's image provides: http://paste.ubuntu.com/483908/
[12:19] <ogra> grmpf
[12:19] <ogra> doesnt resize, doesnt reboot
[12:19] <lag> Correct
[12:19] <ogra> i uploaded a fix for the reboot issue yesterday
[12:19] <lag> So, back to my original question
[12:19]  * ogra takes a look what happened to the busybox upload
[12:19] <lag> ogra: No
[12:19] <lag> ogra: It has nothing to do with it
[12:20] <ogra> ?
[12:20] <lag> I believe the daily image is still ro
[12:20] <ogra> it should still reboot
[12:20] <ogra> it cant be ro if you get through to oem-config
[12:21] <ogra> since thats only enabled by touching a certain file on the FS
[12:21] <ogra> line 327 in http://paste.ubuntu.com/483908/
[12:21] <lag> Well tell me what the differences betweek the two pastes I gave you then?
[12:22] <lag> between*
[12:22] <ogra> weird i see the initrd script being executed twice in the latter one
[12:22] <ogra> lag, the first one reboots fine
[12:23] <lag> ogra: Correct
[12:23] <ogra> which image is that ?
[12:23] <lag> The second one is the daily build
[12:23] <lag> The first one is the daily image with my kernel and initrd
[12:23] <ogra> and the first one that works ?
[12:23] <ogra> oho !
[12:24] <ogra> same image ?
[12:24] <ogra> but different kernel ?
[12:24] <lag> Yeah
[12:24] <lag> And initrd
[12:24] <ogra> so i was right saying the broken reboot is a kernel issue ;)
[12:24] <ogra> and you already fixed it !
[12:24] <lag> Seemingly
[12:24] <ogra> perfect
[12:24] <lag> Where is Busybox?
[12:24] <ogra> whatever you did, i want it in our kernel then :)
[12:25] <ogra> its the shell that runs in initrd
[12:25] <lag> So it must be using my Busybox?
[12:25] <ogra> your chroot should have two packages, busybox-static and busybox-initramfs
[12:25]  * lag looks
[12:25] <ogra> can you check which version your used inside the chroot ?
[12:25] <ogra> *you
[12:26] <ogra> might be that my -marm fix is moot
[12:26] <lag> How do I check?
[12:26] <ogra> dpkg -l|grep busybox
[12:26] <lag> ii  busybox-initramfs                1:1.15.3-1ubuntu1        Standalone shell setup for initramfs
[12:26] <ogra> 1:1.15.3-1ubuntu3 has the -marm fix
[12:26] <ogra> hmm
[12:27] <ogra> 1:1.15.3-1ubuntu1 is the oldest one we had in maverick
[12:27] <ogra> could you try upgrading ? that version used to work all the time
[12:27] <ogra> 1:1.15.3-1ubuntu2 stopped working, 1:1.15.3-1ubuntu3 was supposed to fix that
[12:28] <ogra> 1:1.15.3-1ubuntu4 is the current one (with another fix on top of mine)
[12:38] <ogra> gah, todays daily still doesnt reboot :/
[12:38] <ogra> at least on omap4
[12:44] <lag> ogra: I know, I told you that!
[12:44] <ogra> yes
[12:50] <ogra> f*ck
[12:50]  * ogra thinks he found the issue
[12:51] <zumbi_> 111m355
[12:51] <zumbi_> damn :)
[12:52] <persia> have to change that now :)
[12:53] <zumbi_> it is screenlock passwd
[12:53] <zumbi_> but yeap, i need to change
[13:21] <lag> ogra: And ...
[13:22] <ogra_cmpc> lag, fix is uploaded
[13:23] <lag> ogra: Which was?
[13:23] <lag> ogra: And why did it work with my kernel/initrd?
[13:23] <ogra_cmpc> if e2fsck finds a wrong last mount time (because of rtc skew or something) it tears down the whole resize script
[13:23] <lag> Where is that? Jasper?
[13:23] <ogra_cmpc> the last line in the resize script sets that reboot mark for the next script
[13:23] <ogra_cmpc> yeah
[13:24] <ogra_cmpc> no idea why your kernel initrd worked though
[13:24] <ogra_cmpc> since it doesnt seem to be busybox at all
[13:25] <ogra_cmpc> what fixes does your kernel include ?
[13:25] <ogra_cmpc> anything related to ext2/3 ?
[13:39] <lag> ogra: I'll show you
[13:46] <lag> http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=commitdiff;h=fa324d1893d06e157a2f93040a20f1d490c3c834;hp=978e830c47ca5de5824ddf3ba9f7d3571da765a7
[13:46] <lag> http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=commitdiff;h=27dafb99b153bab4bf7f061889775761cf7c2caa;hp=fa324d1893d06e157a2f93040a20f1d490c3c834
[13:46] <lag> http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=commitdiff;h=12f88410bcaab12078b27e766a42b12a7d4bd2b5;hp=27dafb99b153bab4bf7f061889775761cf7c2ca
[13:46] <lag> ogra: -^
[13:46] <ogra> yep, looking
[13:47] <ogra> ah, mmc fixes
[13:48] <lag> Correct o mondo
[13:48] <ogra> might be that thats related, i.e. if the mmc is bad e2fsck will exit 1
[13:48] <ogra> same symptom, different cause
[13:49] <ogra> lets wait until jasper is in the archive and i rolled a new image
[13:49] <ogra> (which might take eternally)
[13:49] <lag> ogra: Are you saying that there is no massive rush to place these patches into our kernel?
[13:49] <ogra> we need more buildds
[13:49] <ogra> lag, there is, but no way to test them quickly in the archive
[13:49] <lag> ogra: That's find by me - they're not even in the linux-omap kernel yet
[13:50] <persia> Nah, just faster buildds.
[13:50] <ogra> lag, https://edge.launchpad.net/builders
[13:50] <persia> more just means more parallel builds of superceded stuff
[13:50] <ogra> lag, we're 60 package (or 10-12h) behind on armel
[13:50] <ogra> (thats a guesstimate, could also only be 8-9h)
[13:51] <ogra> lag, where do they come from initially ? rcn-ee ?
[13:51] <lag> ogra: Yes, they are Robert's patches
[13:51] <ogra> cool
[13:51] <ogra> add them !
[13:52] <lag> They have been ack'ed in linux-omap, but they're not in the tree yet
[13:52] <ogra> pfft, lets be ahead :)
[13:54] <lag> When will development continue on the XM?
[13:55] <ogra> as soon as we can boot it
[13:55] <ogra> which your patch should fix
[13:56] <ogra> i want working images for beta
[14:19] <ogra> lag, dont you need to mention a bug # in pull requests (seeing your mail to the kernel ML)
[14:20] <lag> ogra: Although this does fix one of the bugs, it is not directly associated with one
[14:20] <ogra> ah
[14:20]  * ogra lears something new every day :)
[14:21]  * ogra also learned that the new tires for his new car will cost him about 1000€ :(
[14:22] <ogra> its only rubber ! damned
[14:22] <persia> Get steel wheels: more sparks, less frequent replacement
[14:23] <ogra> yeah, looks surely more shiny to do 270Km/h with these ... though i fear the traction wont be as good :)
[14:23] <persia> Yeah, well.
[14:25] <hrw> ogra: costs of using porsche?
[14:26] <ogra> hrw, costs of buying porsche with horribly wide tires and knowing they need replacement
[14:27] <lag> ogra: Have you tested the daily build on the Panda ES1.0 today?
[14:27] <ogra> i didnt know there is only one set thats allowed though
[14:27] <ogra> lag, yes, thats what i did above to find the jasper issue
[14:27] <hrw> ogra: sucks a bit
[14:27] <ogra> well
[14:27] <lag> Hmm
[14:27] <lag> That's not good
[14:27] <ogra> hrw, i asked for it, i get it :)
[14:27] <hrw> yep
[14:28]  * hrw rebuilds gcc-4.4 again to check for regressions
[14:28] <ogra> lag, whats not good ?
[14:30] <lag> ogra: I recieved my, replacement Panda today
[14:30] <lag> ogra: My old one's USB was borked
[14:31] <lag> ogra: This one doesn't seem to want play nice with HDMI
[14:31] <ogra> ah, well, your broken monitor again
[14:31] <lag> ogra: Nope
[14:31] <ogra> is that es1.0 ?
[14:31] <ogra> or 2.0
[14:31] <lag> ogra: Different one
[14:31] <lag> ES1.0
[14:31] <ogra> yes, but which version
[14:31] <ogra> ah
[14:31] <lag> I haven't plugged my ES2.0 in yet
[14:31] <lag> There are more than one?
[14:32] <ogra> mine is on the way, just had a call from fedex customs
[14:33] <lag> How do you tell which version is which?
[14:33] <ogra> one is painted black, one isnt
[14:33] <hrw> wasn't black ones es2.0?
[14:33] <ogra> right
[14:35] <lag> You asked me which version of ES1.0 I had
[14:37] <ogra> ??
[14:37] <ogra> i didnt
 is that es1.0 ?
 or 2.0
[14:39] <lool> Hmm my beagle doesn't see NAND anymore; I think this was a known bug and got fixed recently; can someone confirm that latest kernels have NAND?
[14:39]  * ogra isnt sure that was uploaded to the archive yet
[14:39] <ogra> i know the fix is committed
[14:39] <ogra> lool, mpoirier was working on that
[14:40] <mpoirier> lool: I committed the fix last week.
[14:49] <lool> mpoirier: c08fa0be3ddeaca289b0646c8d087fc3820a7f3f right?
[14:50] <mpoirier> lool: hold on, I'll double check.
[14:54] <mpoirier> lool: yes that is correct.
[14:55] <lool> mpoirier: thanks
[14:55] <ogra> lool, jcrigby, btw, there is a few patches we carry that are not upstream yet, you might want to pull these in from the ubuntu tree
[14:56] <ogra> (additionally to the NAND ones)
[15:05] <lool> Well mpoirier's patch doesn't apply in Linaro 2.6.35; presumably we got it from linux-omap
[15:06]  * ogra_cmpc thought it was our own developent
[15:06] <lool> It's a workaround for the 2.6.35 situation, but upstream had already fixed it differently -- that's how I read it at least
[15:07] <ogra_cmpc> mmmmk
[15:07] <lool> mpoirier: f450d86790ebf72ac93c7ea5addd6fa278aae64c upstream I think
[15:07] <lool> well in linux-omap; checking linus now
[15:08] <lool> f450d86790ebf72ac93c7ea5addd6fa278aae64c in linus tree
[15:08] <ndec> ogra: hi. back to my question on neon. should we append -neon on the package name or on the version?
[15:08] <persia> package name, definitely
[15:08] <ogra_cmpc> if we cant do runtime detection with hwcaps put it in the name
[15:09] <mpoirier> lool: yes indeed, this is exactly what is written in my commit.
[15:09] <ndec> persia: thanks!
[15:09] <lag> ogra:
 ES1.0
 yes, but which version
[15:09] <lool> mpoirier: Eh indeed
[15:09] <ogra_cmpc> lag, wrong context :P
[15:09] <lool> mpoirier: Sorry, got confused by ogra
[15:09] <lag> :)
[15:10] <lag> ogra: Who is developing the x-loader for ES2.0
[15:10] <ogra_cmpc> TI
[15:10] <ogra_cmpc> lag, did you try with the linaro uboot ?
[15:11] <lag> ogra: Yea
[15:11] <ogra_cmpc> didnt work either i guess
[15:11] <lag> ogra: It's okay, rsalveti Is going to sort me out with new binaries
[15:11] <ogra_cmpc> well, we need new packages too
[15:11] <rsalveti> ogra: sure, as we need a new kernel
[15:12] <rsalveti> ogra: it'd be good to wait sakoman get it working with es2
[15:12] <ogra_cmpc> i thought the current kernel can run on both
[15:12] <ogra_cmpc> only the one we'll get with the next commit cant
[15:12] <ogra_cmpc> (thats how i understood it)
[15:13] <rsalveti> ogra_cmpc: lag: http://rsalveti.net/pub/ubuntu/kernel/maverick/es2/
[15:14] <rsalveti> sweeeet, my es2 just arrived :D
[15:14] <rsalveti> davidm: ^ :-)
[15:14] <ogra_cmpc> lucky guy
[15:15] <davidm> rsalveti, good, I knew it was on a truck heading to you
[15:17] <ndec> rsalveti: which kernel source did you build your kernel from?
[15:17] <rsalveti> ndec: lag: ogra: http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-maverick.git;a=shortlog;h=refs/heads/rsalveti-ti-omap4-es2
[15:17] <rsalveti> I basically applied the patches from
[15:17] <rsalveti> http://gitorious.org/pandaboard/kernel-omap4/commits/L24.8_panda_es2.0
[15:17] <rsalveti> on top of our kernel
[15:17] <rsalveti> also some extra display patches
[15:19] <ndec> rsalveti: ok.. sebjan has sent a more official patch set to cooloney. not sure if you're aware of that. our patchset is here http://dev.omapzoom.org/?p=integration/kernel-ubuntu.git;a=shortlog;h=refs/heads/for-ubuntu-2.6.35. it should be same content as the initial patchset but with many cleaning in the patches
[15:19] <cooloney> ndec: thx
[15:19] <ndec> rsalveti: and this one is more likely to become the 'official' branch in  maverick/ti-omap
[15:19] <cooloney> rsalveti: i am working on it
[15:19] <lag> Where's my email?
[15:19] <ndec> cooloney: thx for?
[15:20] <rsalveti> ndec: sure, but this is the 2.6.35 tree, that we're waiting cooloney do review and etc, but thanks for pointing that
[15:20] <rsalveti> ndec: will this tree work with es1 and es2?
[15:20] <cooloney> lag: i just got it today.
[15:20] <rsalveti> or just es2?
[15:20] <rsalveti> cooloney: oh, so this is the "final" tree?
[15:20] <lag> cooloney: sebjan said he'd sent it to both of us?
[15:20] <lag> cooloney: Are you doing it then?
[15:20] <ndec> ogra: lag: i see you are discussing linaro uboot. are you planning to use this one instead of the current one?
[15:21] <ogra_cmpc> ndec, already switced, yes
[15:21] <ndec> rsalveti: it depends on what 'final' means ;-)
[15:21] <rsalveti> awesome, with all latest hdmi fixes
[15:21] <ndec> rsalveti: yes. including support for multiple FBs
[15:21] <rsalveti> ndec: I mean the point that cooloney can just review and get the tree :-)
[15:21] <ndec> ogra_cmpc: oops... didn't know that. how does that work?
[15:22] <ndec> rsalveti: cool... i thought that final means that there was no more issue with OMAP4...
[15:22] <ogra_cmpc> ndec, lacking an es2 i cant tell yet but anything will be better than the 1.1.4 one
[15:22] <rsalveti> ndec: it's working fine at the moment
[15:22] <cooloney> lag: sebjan doesn't finished it
[15:22] <rsalveti> based on sakoman's work
[15:23] <ndec> ogra_cmpc: so the panda uboot support was merged in the mainline uboot? who did that?
[15:23] <ogra_cmpc> ndec, 1.1.4 has a broken vfat driver
[15:23] <ogra_cmpc> ndec, sakoman
[15:23] <lag> cooloney: ndec just said you've been sent the email?
[15:23] <cooloney> lag: no, i didn't sent email
[15:23] <lool> pm215: Hey there
[15:23] <ogra_cmpc> lag, ndec only pointed to the work branch of sebjan
[15:23] <ogra_cmpc> without saying its done
[15:23] <lool> pm215: ^P/^N or /win 2 to switch windows?
[15:24] <pm215> lool: hello. I see I'm now in both channels with a hopelessly confusing UI :-)
[15:24] <rsalveti> ndec: cooloney: should this kernel be compatible with both es1 and es2?
[15:24] <rsalveti> the new one, based on 2.6.35
[15:24] <persia> pm215, Alt+2 might work also
[15:25] <cooloney> rsalveti: sebjan said it's not ready for both es1 and es2.
[15:25] <cooloney> but he is working on it. i think
[15:25] <rsalveti> cooloney: cool
[15:25] <ogra_cmpc> i dont think es1 support is wanted
[15:25] <ndec> rsalveti: only 2.0 for now. sebjan is trying to see if it can work on es1 as well..
[15:25] <ogra_cmpc> at least thats what i understood in the call
[15:25] <rsalveti> ogra_cmpc: sure, but just wanted to confirm :-)
[15:25] <lag> ndec: What's the difference between "http://dev.omapzoom.org/?p=integration/kernel-ubuntu.git" and "git://dev.omapzoom.org/pub/scm/integration/kernel-omap4.git"
[15:25] <pm215> ^P/^N//win/alt+2> none of those do anything, I'm afraid. Never mind.
[15:25] <cooloney> i've already prepared a omap4 branch based on sebjan's branch
[15:26] <cooloney> lag and rsalveti http://kernel.ubuntu.com/git?p=roc/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4
[15:26] <rsalveti> cooloney: on current sebjan's tree?
[15:26] <lool> pm215: ctrl-1/ctrl-2?  /win 2 might be keeping you in the same window, try /win 1
[15:26] <rsalveti> cooloney: awesome!
[15:26] <cooloney> rsalveti: sebjan is still working on it. so we need wait for a while
[15:26]  * rsalveti preparing the build machine
[15:26] <ndec> lag: kernel-omap4.git is TI BSP team tree, kernel-ubuntu.git is our tree (sebjan's tree) that we use as a staging area between TI BSP and Ubuntu tree
[15:26] <cooloney> rsalveti: i cross compiled it on my local machine
[15:27] <pm215> ctrl-1/ctrl-2> nope, no effect. /win 1 says "Unknown command: WIN"
[15:27] <lool> pm215: If you want to see a quote of the day /qu erat demonstrandum
[15:27] <cooloney> the L24.9 gonna some issue about ASOC codec driver
[15:27] <rsalveti> hm, ok
[15:27] <cooloney> so currently i disabled that ASOC codec drivers
[15:27] <ndec> lag: our tree has some decent level of cleaning (400 patches removed, 3700 checkpatch errors removed)
[15:27] <lool> This joke works better in French, with "/qui est là"
[15:27] <rsalveti> prpplague: didn't you do some work on that?
[15:28] <ndec> lool: even in French I don't understand the joke...
[15:28] <rsalveti> ogra_cmpc: another topic, how is today's image?
[15:28] <ogra> rsalveti, still bad
[15:28] <rsalveti> just download them
[15:28] <rsalveti> ogra: what is broken?
[15:29] <ogra> jasper, oem-config etc
[15:29] <rsalveti> want to test the gles stuff with sgx and efl
[15:29] <rsalveti> and latest clutter and etc
[15:29] <lag> ndec: Excellent news
[15:29] <lool> ndec: Well, IRC clients have an easter egg; you type /qui est là, and it shows you a quote
[15:29] <ndec> lag: well... thx sebjan...
[15:29] <rsalveti> ogra: ouch hehe :-)
[15:29] <lag> ndec: I already have
[15:29] <lag> ndec: Yesterday :)
[15:30] <lool> Apparently, this joke only worked back in the days I was at school
[15:30] <ogra> rsalveti, the build queue was stuck for most of the day so the fixes arent built yet
[15:30] <ogra> or in case of oem-config not even uploaded
[15:30] <persia> Many easter eggs got polished out as more folks use the software, unfortunately.
[15:31] <lool> That one is quite hard to polish out
[15:31] <pm215_> (now I have a sane UI with the unfortunate effect of having to use two nicks...)
[15:33] <rsalveti> ogra: hm, ok
[15:35] <ogra> lool, hey !
[15:35] <ogra> lool, where is the bzr commit for your flaash-kernel change =
[15:35] <ogra> ?
[15:38] <lool> Hmm I thought this was using the package imports
[15:38] <rsalveti> lag: cool, so you're pushing the xM mmc fixes :-)
[15:38] <lag> Attempting to
[15:38] <rsalveti> lag: I'm using it already for days, and it's working nicely
[15:39] <ogra> lool, it has a tree mentioned in debian/control :)
[15:39] <lool> I'll fix that
[15:39] <ogra> thanks
[15:39] <ogra> its my working tree for debian merges too
[15:39] <lag> rsalveti: Yes, I tested them this morning
[15:39] <ogra> so it would be good to keep it consistent
[15:40] <rsalveti> lag: nice
[15:40] <lool> Grmpf, import-dsc doesn't work with native packages
[15:41] <ogra> lool, just push your changes to the tree, what are you doing ?
[15:42] <lool> I'm using the canonical way of importing a dsc into a branch!
[15:42] <ogra> sigh, cant you just leave it as it is and commit your changes ?
[15:43] <lool> ogra: Dude, I did already
[15:43] <ogra> ah, then its fine :)
[15:43] <lool> I don't understand why you care how I do it
[15:43] <ogra> i dont, as long as it ends up in the right tree :)
[15:44] <ogra> i thought you were fiddling with trees here ... sorry
[15:44] <ogra> and thanks for the fix :)
[15:44]  * ogra strikes it from his TODO
[15:46] <ogra> lool, btw, does linaro care about kirkwood ? (there are some pending debian changes for flash-kernel i didnt actually plan to merge unless someone really needs them)
[15:46] <cooloney> i got the 2.6.35 kernel boots on my panda now
[15:47] <cooloney> http://pastebin.ubuntu.com/483996/
[15:47] <ogra> cooloney, that becomes intresting if line 8 changes ;)
[15:47] <rsalveti> cooloney: cool, at your es1?
[15:48] <cooloney> too bad, i don't have the es2 HW
[15:48] <cooloney> rsalveti: yeah, mine is ES1
[15:48] <rsalveti> cooloney: nice, I will test on my es2
[15:49] <cooloney> great, gonna sleep now
[15:49] <rsalveti> cooloney: see ya!
[15:49] <hrw> ogra: still using 512MB on panda? I thought that 1GB was running already
[15:50] <ogra> hrw, not yet
[15:55] <pm215_> help ?
[15:56] <pm215_> whoops, can't drive my irc client still :-)
[16:01] <ogra> lool, so why are the updates of my falsh-kernel branches all failing now ?
[16:01] <ogra> what the heck did you do ?
[16:02] <ogra> GRRRR !!!!
[16:05] <robclark> ogra: if you are brave, you could try porting the 1gb patch from es2 branch..
[16:05] <robclark> http://gitorious.org/~robclark/pandaboard/robclarks-x-loader/commits/omap4_panda_es2.0-1gb
[16:06] <ogra> robclark, why porting ? shouldnt i be able to just build that one ?
[16:06] <robclark> well..  depends on how aligned theory is with fact ;-)
[16:06] <ogra> we dont plan to support es1 anyway
[16:06] <robclark> in *theory* it should work
[16:07] <ogra> i'll try as soon as my es2 arrives, if its good i'll just rebase the package on that one ;)
[16:11] <rsalveti> robclark: nice, will try this one
[16:11] <robclark> I've been using it for a couple weeks on es2..
[16:11] <lool> ogra: I did what I noted in the changelog: moved to the package import branches...
[16:12] <robclark> and in theory same x-loader should work on es1... but I haven't tested that myself, so who knows
[16:12] <ogra> lool, well, and i have to rebade about ten development branches now
[16:12] <ogra> *rebase
[16:12] <lool> ogra: "rebase", why rebase?
[16:12] <lool> it's the same branch
[16:12] <lool> I replaced the package import branch with what was ~ubuntu-core-dev/flash-kernel/ubuntu
[16:13] <ogra> i have to touch them still, you just wiped out teams work branch
[16:13] <ogra> even though i asked you not to
[16:13] <ogra> thats not nice ... but i'll point my branches to the new one
[16:13] <lool> ogra: I don't understand what you're speaking about
[16:13] <lool> You can merge them as you could before
[16:14] <ogra> the master branch of my (and likely others) dev brances is gone from LP
[16:15] <lool> ogra: It's not, it just moved
[16:15] <ogra> ogra@osiris:~/Devel/branches/flash-kernel/ubuntu$ bzr pull
[16:15] <ogra> Using saved parent location: bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/flash-kernel/ubuntu/
[16:15] <ogra> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/flash-kernel/ubuntu/".
[16:15] <lool> bzr pull --remember lp:ubuntu/flash-kernel
[16:16] <ogra> lool, yes, i have to do that on all my branches now, at least note the new location in your changelog entry next time so people using it know where to pull from
[16:16] <lool> ogra: it's the standard location...
[16:16] <ogra> that was a totally unnecessary change that causes extra work
[16:16] <lool> ogra: Wouldn't I do that, you would continue using the old location
[16:17] <ogra> that was my plan yes
[16:17] <lool> What's unnecessary is having two branches, and this will prevent people from not committing before upload
[16:17] <ogra> ...
[16:18] <persia> It doesn't prevent it.  It just does the right thing anyway.
[16:18] <lool> ogra: There, I've pushed lp:~ubuntu-core-dev/flash-kernel/ubuntu again and marked it as abandoned
[16:19] <persia> But it breaks if there are unuploaded commited changes in the branch.
[16:19] <lool> ogra: please don't push to this "old" branch anymore, thanks
[16:19] <persia> (which is a feature, not an impediment: stuff ought be uploaded)
[16:27] <lool> ogra: Look, it sounds like you're pissed off; I'm trying to do the right thing by avoiding the mistake I made in the future; I thought it was obvious how to adjust your local branches for that, but it apparently wasn't as easy as I thought it was, so I've pushed something back will should help a bit, but wont force you into the right branch; do you understand why it's better to move to the new branch?
[16:28] <ogra> lool, so will you run around and move all of cjwatsons branches too (i know he, like me prefers to use branches the old way) ?
[16:29] <persia> So, this doesn't feel like constructive criticism (although I really like they way you've raised it early and publically)
[16:29] <persia> Would you both agree that in future it's best to coordinate between common uploaders of a package before migrating a branch to the UDD home?
[16:29] <ogra> and can you understand that people dont like to be "forced" intop a new way in the middle of the busiest time before a freeze where a branch might be used atm for fixes ?
[16:30] <lool> Quite frankly, I didn't expect that there were any pending merges; I did look for pending merge requests and didn't see any
[16:30] <lool> Would I have seen any, I wouldn't have moved before dealing with these
[16:30] <ogra> lool, i would have moved the branch with the merge in N, its just not cool to do it if someone asks you not to
[16:30] <prpplague> hey all you early developers for the Panda, i'm trying to finalize the features for the Bamboo accessory board for the panda
[16:30] <ogra> but it happened now, so lets forget about it
[16:31] <prpplague> if any has hardware requests for additions to the bamboo, now is the time
[16:32] <lool> ogra: So the additional work it creates is this --remember lp:ubuntu/flash-kernel thing?
[16:32] <lool> I dont want to defer dealing with problems when I can
[16:32] <ogra> lool, that too, worse is that you simply ignored my request
[16:34] <lool> ogra: where did you request what?
[16:35] <ogra> prpplague, do you have a list of stuff thats in already ? so we can see what might be missing ?
 lool, just push your changes to the tree, what are you doing ?
 I'm using the canonical way of importing a dsc into a branch!
 sigh, cant you just leave it as it is and commit your changes ?
[16:36] <prpplague> ogra: accessory board that provides: second sd/mmc, 2 user leds, 2 user buttons, reset button, power led, battery backed RTC, built in usb->rs232 for console power, 2 additional USB host ports, and an abs plastic case
[16:36] <prpplague> ogra: creating a wiki page now
 ogra: Dude, I did already
 ah, then its fine :)
 I don't understand why you care how I do it
 i dont, as long as it ends up in the right tree :)
 i thought you were fiddling with trees here ... sorry
 and thanks for the fix :)
[16:36] <ogra> prpplague, nothing strikes me on first sight
[16:37] <rsalveti> prpplague: yep, sounds ok already :-)
[16:42] <persia> prpplague, Any chance of eSATA?
[16:42] <mopdenacker> I was going to ask...
[16:42] <ogra> persia, heh or inflatable helicopters
[16:42] <prpplague> persia: still working on that request
[16:43]  * persia is *much* more interested in eSATA than inflatable helicopters.  One can glue the abs case to the baloon easily enough, but ...
[16:43] <persia> prpplague, heh, OK :)
[16:43] <ogra> heh
[16:43] <prpplague> http://www.elinux.org/Panda_Bambo
[16:45]  * persia is all sorts of excited: the ABS case is the best feature
[16:50] <prpplague> i've updated the page with the color and dimensions of the case
[16:50]  * GrueMaster assumes the case design includes externally accessable buttons?
[16:50] <prpplague> feel free to leave comments there
[16:50] <prpplague> GrueMaster: yea
[16:50] <GrueMaster> Nice.
[16:50] <prpplague> GrueMaster: front panel will have the power led, 2 buttons, 2 leds, the sd/mmc slot
[16:50] <prpplague> GrueMaster: and the two addtional usb host ports
[16:51] <persia> My main concern about the case is that it be stackable with other stuff: bare boards are hard to feel comfortable about sticking on a shelf with other stuff and attaching to a KVM.
[16:51] <GrueMaster> Very nice.
[16:51] <prpplague> GrueMaster: back will be the back of the panda, with a usb slave port for the console
[16:51] <prpplague> persia: yea the case is stackable
[16:51] <persia> Excellent.
[16:52]  * GrueMaster might have to sneak the credit card away from the wife again soon.
[16:52] <prpplague> estimated cost will be $55.00
[16:52] <prpplague> (plus or minus $5)
[16:53] <GrueMaster> Excellent.  That fits into my monthly turn & burn budget.
[16:53] <GrueMaster> (i.e. not something I need to wait until I have the funds for).
[16:56] <rsalveti> prpplague: nice, not that expensive
[16:57] <hrw> prpplague: when will be available?
[16:57] <hrw> y
[17:00] <prpplague> hrw: should be available on the same day panda's become available
[17:02] <persia> nice!
[17:18] <rsalveti> lunch time!
[17:42] <GrueMaster> Gah, seeing python issues with package updates.  Haven't updated libc6 yet, so there is hope this isn't a bug.
[18:16] <ogra> rsalveti, it wont work completely, the .1 build i'm doing should only fix the reboot issue
[18:17] <rsalveti> ogra: hm, ok
[18:17] <ogra> rsalveti, oem-config/ubiquity was still not uploaded so it will fail
[18:17] <GrueMaster> Still?  I thought the fix went in last week?
[18:17] <ogra> yes, into the branch
[18:18] <ogra> i didnt want to interfere with the ongoing work on the installer team so i waited for them to upload (the tree might have half breeded code in there)
[18:20] <ogra> s/on/of/
[20:11] <dcordes> hi
[20:12] <dcordes> what is the difference between
[20:12] <dcordes> http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100826.1/maverick-preinstalled-netbook-armel+omap4.img.gz
[20:12] <dcordes> http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100826.1/maverick-preinstalled-netbook-armel+omap.img.gz
[20:14] <rsalveti> default kernel, u-boot and x_loader basically
[20:16] <dcordes> ok
[20:17] <GrueMaster> dcordes: omap4 is for panda/blaze, omap is for Beagle
[20:17] <dcordes> rsalveti: so there are no differences in the userspace binary compilation ?
[20:17] <GrueMaster> (should be omap3 in my opinion - just to keep from confusing people with older platforms).
[20:17] <GrueMaster> None.
[20:17] <rsalveti> agree
[20:17] <dcordes> ok guys thanks
[20:18] <dcordes> yeah that would make sense to change omap into omap3
[20:18] <dcordes> +1
[20:18] <dcordes> after people loved ubuntu on the htc hd2 I am going to create a new 'release'
[20:19] <rsalveti> cool
[20:22] <prpplague> just to make sure everyone knows(i announced earlier today) i'm taking feedback and comments on the features for the bamboo board - http://www.elinux.org/Panda_Bambo
[20:23] <dcordes> prpplague: love the case ;)
[20:23] <prpplague> dcordes: hehe, i get 50/50 on that
 the case is ugly
[20:29] <dcordes> prpplague: despite from having that classical box, what is it ?
[20:31] <prpplague> dcordes: accessory board for the panda
[20:32] <dcordes> prpplague: is it bamboo or bambo ?
[20:32] <dcordes> (page title says bambo)
[20:32] <prpplague> yea someone just pointed that out
[20:32]  * prpplague movies the page
[20:34] <dcordes> you should add a small intro. bamboo is an expansion board for the [[panda]] device
[20:34] <dcordes> something like that
[20:36] <dcordes> downloading that maverick netbook rootfs with 20kB/s
[20:36]  * dcordes sighs
[20:36] <dcordes> university is charging too much for such slow dormitory net
[20:42] <prpplague> dcordes: will do, i just assumed the folks who have a panda would understand
[20:42] <ogra_cmpc> GrueMaster, the omap vs omap4 naming was chosen with the idea in mind that we might have a single omap image at some point once linaros unification work for kernel and u-boot is done
[20:42] <ogra_cmpc> GrueMaster, you might have noticed that we use the same scheme for the kernel packages
[20:42] <GrueMaster> My only point is that we are not supporting omap2 hw.
[20:43] <ogra_cmpc> afaik thats on linaros plans too (i might misremember though)
[20:43] <ogra_cmpc> at least kernel wise
[20:43] <dcordes> aha
[20:43] <dcordes> ogra_cmpc: how is the rootstock coming along ?
[20:44] <rsalveti> dcordes: I'm using it right now, working fine :-)
[20:44] <ogra_cmpc> dcordes, i gave it to rsalveti and since it made a quamntum jump in quality ;)
[20:44] <dcordes> :P
[20:44] <dcordes> it is because I joined the bugtracking system
[20:44] <rsalveti> just need some ui fixes
[20:46] <GrueMaster> ogra_cmpc: I'm down to the last 27 package updates to bring A3 current.  Still booting into X with gdm & netbook-launcher-efl so far.  Most critical path packages are updated now.
[20:46] <ogra_cmpc> whats missing ?
[20:46]  * ogra_cmpc doesnt get why we have that issue
[20:47] <rsalveti> GrueMaster: cool, good to know
[20:47] <ogra_cmpc> worrying though
[20:48]  * ogra_cmpc would perfer a clear pointer to a package thats broken
[20:48] <GrueMaster> Woohoo.  leann posted kernel with XM fix.
[20:48] <ogra_cmpc> yeah
[20:49] <ogra_cmpc> sadly i assumed she would just take the branch and upload it, but she cherrypicked ... so the NAND fix is still waiting until after beta
[20:50]  * ogra_cmpc didnt think about that when discussing the freeze exception :(
[20:50] <GrueMaster> I thought that was already in.
[20:50] <ogra_cmpc> in the tree, yes
[20:51] <rsalveti> ogra_cmpc: what nand fix?
[20:51] <GrueMaster> for beagle
[20:51] <rsalveti> hm, so isn't it released already?
[20:51] <ogra_cmpc> rsalveti, the one that makes mtd work again
[20:51] <ogra_cmpc> i didnt see it in any upload yet
[20:51] <rsalveti> mine works, I even get i/o errors
[20:51] <ogra_cmpc> and tohdays only has the cherry picked mmc fix
[20:51]  * rsalveti looks at the kernel tree
[20:52] <GrueMaster> I think it is already there.  I'm looking at today's image on beagle and seeing /dev/mtd*
[20:52] <ogra_cmpc> oh, hmm, then i might be blind and have missed it in the changelog
[20:53] <GrueMaster> That's highly possible.  :P
[20:54]  * ogra_cmpc wonders if he has a misbehaving proxy .... i saw the 20100826.1 image on cdimage a few mins ago, now it seems to be gone again
[20:55] <rsalveti> ogra_cmpc: bug 608266
[20:55] <rsalveti> fix released already
[20:55] <ubot2> Launchpad bug 608266 in linux (Ubuntu Maverick) (and 1 other project) "[regression] no more /dev/mtdblock devices on omap3 in maverick (affects: 1) (heat: 104)" [Medium,Fix released] https://launchpad.net/bugs/608266
[20:55] <ogra_cmpc> ah, ik
[20:55] <rsalveti> with 2.6.35-16.22
[20:55] <rsalveti> :-)
[20:55] <ogra_cmpc> consider me officially blind then
[20:55] <rsalveti> I even told you that I was getting i/o errors
[20:55] <ogra_cmpc> :)
[20:55] <rsalveti> :-)
[20:55] <ogra_cmpc> right, i thought that was with your own kernel
[20:55] <GrueMaster> Helps not to look through a half full beer glass.  :p
[20:56] <ogra_cmpc> i'm never sure what you use over there :P
[20:56] <rsalveti> haha :-)
[20:56] <rsalveti> true
[20:56] <rsalveti> I try to use our kernel with possible fixes
[20:56] <ogra_cmpc> GrueMaster, i had my last beer in prague :)
[20:56] <rsalveti> so we can get it pushed later
[20:56] <rsalveti> ouch
[20:56] <dcordes> GrueMaster: I can offer a 1/3 full whine glass if somebody is interested
[20:56] <GrueMaster> this saddens me.
[20:56] <rsalveti> 2
[20:56]  * dcordes always ready to help the community.
[20:57] <ogra_cmpc> no, its healthy, keep my liver happy and makes me bear more in orlando ;)
[20:57] <ogra_cmpc> dcordes, you whine into a glass ?
[20:57] <ogra_cmpc> now *thats* saddening ;)
[20:58]  * GrueMaster only whines about an empty glass.
[20:58]  * dcordes everybody lol for the funniest typo 2010
[20:58] <dcordes> that got me so down I need to refill
[20:58] <ogra_cmpc> that year isnt over ... and my bad humor isnt either ;)
[21:00] <ogra_cmpc> hmm, where is the .1 image gone .... looking above dcordes saw it too (according to the url)
[21:01] <GrueMaster> I'm pulling it ok.
[21:01] <ogra_cmpc> i get a 404 for the dir
[21:01] <GrueMaster> http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100826.1/maverick-preinstalled-netbook-armel+omap4.img.gz.zsync
[21:02] <GrueMaster> odd
[21:02] <ogra_cmpc> i started a zsync upstairs, not sure it still runs
[21:03] <ogra> yeah, seems to be done
[21:04] <dcordes> ogra_cmpc: .1 image ?
[21:04]  * dcordes is downloading http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100826.1/maverick-preinstalled-netbook-armel+omap4.img.gz
[21:05] <ogra> dcordes, right, but http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100826.1/ gets me a 404 suddenly
[21:05] <ogra> and http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/ doesnt have a .1
[21:06] <ogra> my download worked fine as well
[21:06] <ogra> oh, there is is now
[21:06] <ogra> irritating
[21:07]  * ogra guesses our sync process from the builder to the webserver is somehow strange 
[21:11] <dcordes> ogra: try to request the url 10 times
[21:11] <dcordes> then it works
[21:11] <ogra> well, it seems stable now
[21:11] <dcordes> I always have weird problems with that server *_*
[21:12] <ogra> err, no, it doesnt, its gone again
[21:12]  * ogra checks the server itself
[21:12] <dcordes> here it works but weirdo style as always
[21:13] <dcordes> don't understand the underlying network mechanisms well enough to say what it is
[21:13] <ogra> yeah, its definitely on the server
[21:13] <dcordes> all I know is sometimes the sites there don't show up at a ll
[21:13] <ogra> well, it would be ok if it was just delayed, that on/off stuff is weird
[21:13] <dcordes> but when I keep hitting enter in the browser's url bar it works
[21:13] <dcordes> :)
[21:14] <dcordes> I think when I just let it time out it will also go 404 ...
[21:23] <sakoman> rsalveti: I think I found a fix for the panda u-boot reset command issue
[21:23] <rsalveti> sakoman: nice, what was the issue?
[21:24] <sakoman> OMAP4 seems to want a different bit written to trigger the reset
[21:25] <rsalveti> hm, makes sense
[21:25] <sakoman> TI u-boot was using bit 1 (i.e. 0x02), but I think bit 0 (0x01) is right
[21:26] <sakoman> it also uses a different address than OMAP3, but I already took care of that
[21:27] <rsalveti> cool
[21:27] <sakoman> so while 0x02 worked for all earlier OMAP3s, OMAP36XX/37XX need 0x04, and OMAP4 needs 0x01
[21:27] <rsalveti> got it
[21:27] <sakoman> so I need restructure the code/headers a bit
[21:28] <sakoman> I'll revise the patch I posted previously to also take care of OMAP4
[21:29] <sakoman> rsalveti: little things like this take way too much time, what with building & testig on multiple boards and reviewing multiple 3000 page TRMs!
[21:29] <rsalveti> ouch :-)
[21:36] <suihkulokki> how does the current preinstalled image decide if it is starting on beagleboard or beagleboard xm?
[21:39] <rsalveti> suihkulokki: the omap image should work on both
[21:39] <rsalveti> not with today's image, but that's going to be fixed for tomorrow
[21:41] <suihkulokki> rsalveti: I know it support both :) my question is what does it _do_ to figure out which one it is running on
[21:42] <rsalveti> suihkulokki: http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-maverick.git;a=blobdiff;f=arch/arm/mach-omap2/board-omap3beagle.c;h=623c352f14695a3a01545db9a1307adc5d11e21d;hp=5501f310a9d0c34df4516d6efd0f5e5e25ca2960;hb=52e9cdbb825eae0f3f75550adacebdc36303700b;hpb=978e830c47ca5de5824ddf3ba9f7d3571da765a7
[21:42] <rsalveti> an example
[21:43] <rsalveti> then you can also check by the cpu type
[21:43] <suihkulokki> ok, so there is a gpio to read. thanks.
[21:45] <rsalveti> yup
[21:45] <GrueMaster> Hmmm.  I'm thinking ureadahead is the cause of our current issues.  Testing that theory now.
[21:51] <rsalveti> GrueMaster: hm, it shouldn't, unless we got a new release
[21:51] <GrueMaster> Since Alpha 3, yes.
[21:51] <rsalveti> you can disable it, mv /etc/init/ureadahead.conf /etc/init/ureadahead.disabled
[21:51] <rsalveti> doesn't make a differente
[21:51] <rsalveti> I mean, a major release
[21:52] <rsalveti> *difference
[21:52] <GrueMaster> I updated that, rebooted, then updated all of network manager packages, rebooted.  Not I am getting corrupt filesystem and hangs, but not getting past uInitrd.
[21:52] <rsalveti> ouch
[21:55] <ogra_cmpc> rsalveti, i think parts of ureadahead start in initrd
[21:55] <rsalveti> hm, I'm not sure
[21:55]  * ogra_cmpc neither ... thats why i said i think :)
[21:55] <rsalveti> disabling it from init is enough to get it removed and avoid oom
[21:55]  * ogra_cmpc goes to check
[21:56] <rsalveti> so probably doesn't run inside uinitrd
[21:56] <rsalveti> but :-)
[21:56] <rsalveti> please check
[21:57] <ogra_cmpc> rsalveti, right, only from init
[21:57] <GrueMaster> It does.  I get "init: ureadahead main process (208) terminated with status 5" before it mounts rootfs.
[21:58] <ogra_cmpc> thats fine
[22:00] <ogra_cmpc> GrueMaster, that doesnt mean a thing about the initrd though, there could be a process that hands over data after the initrd for example
[22:00] <ogra_cmpc> thats why i rather look at the code to make sure :)
[22:04] <sakoman> rsalveti: I push a revised patch that fixes both 37XX and OMAP4 u-boot reset command issues:
[22:04] <sakoman> http://www.sakoman.com/cgi-bin/gitweb.cgi?p=u-boot.git;a=commitdiff;h=56473fba8010c5def9ed778da4bcb4455d265b54
[22:05] <rsalveti> GrueMaster: ogra_cmpc: exit 5 means that the trace failed, for some reason
[22:05] <ogra_cmpc> rsalveti, according to Keybuk thaqts because its MMC
[22:06] <ogra_cmpc> i asked him about it a few months ago, he said we shouldnt worry about it, it properly exits
[22:06] <rsalveti> sakoman: cool :-)
[22:06] <rsalveti> ogra_cmpc: hm...
[22:07] <ogra_cmpc> rsalveti, i thinki we should talk to him soon so he can explain the possible benefits for us
[22:07] <ogra_cmpc> i dont really see any
[22:07] <rsalveti> if any
[22:07] <ogra_cmpc> snap :)
[22:07] <rsalveti> ogra_cmpc: sure, we first need to know when he is going to release the new major release
[22:07] <rsalveti> ureahead 2 I guess
[22:07] <ogra_cmpc> likely not during beta freeze
[22:07] <rsalveti> but probably for maverick
[22:08] <ogra_cmpc> thats what he said
[22:08] <rsalveti> hm, ok
[22:08] <rsalveti> but sure, lets talk to him later
[22:08] <ogra_cmpc> the question is if it will work any better then :)
[22:08] <persia> So, ureadahead is good because RAM is faster than flash is faster than {e,}MMC-mitgated flash.
[22:08] <ogra_cmpc> persia, is it ? you still need to read from the SD
[22:09] <rsalveti> persia: doesn't make a difference for beagle
[22:09] <persia> So getting stuff into the page cache in advance always makes boot faster (and ureadahead doesn't read anything that isn't read anyway)
[22:09] <rsalveti> sd is so slow that it really doesn't make a difference
[22:09] <persia> ogra, The point is that you don't have to *wait* on reading from the SD.
[22:09] <rsalveti> the seek is not the issue here
[22:09] <ogra_cmpc> persia, only if things end up in the cache in time
[22:09] <rsalveti> as a normal disk
[22:09] <persia> rsalveti, that's because the beagle doesn't meet the minimum ram requirements (384MB)
[22:09] <rsalveti> 384?!
[22:09] <persia> Yep.
[22:09] <ogra_cmpc> yeah
[22:10] <rsalveti> funny number
[22:10] <persia> Been 384 since Breezy or so.
[22:10] <persia> 3x128.
[22:10] <ogra_cmpc> 384M is the minimum the x86 livecd works in
[22:10] <rsalveti> I know, but still funny
[22:11] <rsalveti> persia: ogra_cmpc: I'd like to test at a valid xm (512mb) to see if changes anything
[22:11] <ogra_cmpc> right
[22:11] <rsalveti> and compare the bootchart
[22:11] <ogra_cmpc> i really doubt it
[22:11] <rsalveti> 2
[22:11] <ogra_cmpc> the IO is to slow to gain any benefit form it is my impression
[22:11] <GrueMaster> Well, any suggestions on where to go?
[22:12] <ogra_cmpc> outside into the sun ?
[22:12] <persia> It helps best when the IO is slow, because it means *not* spending time without full IO bandwidth in use.
[22:12] <rsalveti> lol
[22:12] <rsalveti> persia: doesn't help much
[22:12] <ogra_cmpc> persia, how so if your bandwith is saturated all the time anyway
[22:12] <persia> Mind you, it's Keybuk's code competing with Keybuk's code: ureadahead is only advantageous when upstart fails to use all available IO.
[22:12] <rsalveti> helps a *lot* with normal disks, because the seek time
[22:12] <rsalveti> not much from sd
[22:13] <rsalveti> at least didn't show any difference on my bootchart when caching 64 mb
[22:13] <rsalveti> even more
[22:13] <rsalveti> but, still waiting for a xm test
[22:13] <persia> ogra, If upstart can saturate the IO without ureadahead, then it makes no difference, but Keybuk isn't trying to saturate IO with upstart because he assumes ureadahead will do that (ureadahead is specifically designed to saturate the IO)
[22:13] <prpplague> rsalveti: you guys have a preference where you want to have a pandaboard revision in sysfs?
[22:13] <rsalveti> can test on panda later
[22:14] <rsalveti> prpplague: hm... interesting question
[22:14] <rsalveti> ogra: GrueMaster: ^
[22:14] <GrueMaster> I have nrp.
[22:14] <ogra_cmpc> no idea, really, i personally dont have one
[22:14] <ogra_cmpc> as long as i know where to look in the end :)
[22:15] <rsalveti> prpplague: my question is more with which device do you think of pluging this file into?
[22:15] <persia> Where does this information live for other boards.  Let's strive towards some consistency throughout the industry.
[22:15] <ogra_cmpc> yeah
[22:15] <GrueMaster> I would suggest looking at existing systems for consistency.
[22:15] <rsalveti> proc can be anywhere, but sysfs you need to use a valid device
[22:15] <prpplague> persia: yea that was my question as well, but i can't seem to find any examples
[22:15] <rsalveti> probably no examples
[22:15]  * rsalveti never saw it
[22:16] <ogra_cmpc> likely, else we woldnt parse /proc/cpuinfo for hardware detection
[22:16] <ogra_cmpc> (on all armel systems)
[22:16] <rsalveti> prpplague: is it related with gpios like beagle?
[22:18] <prpplague> rsalveti: yea
[22:18] <prpplague> rsalveti: same type of config
[22:19] <persia> I think that there isn't a standard place (checked 3 arches just now for a variety of HW).  I think most folks just enumerate the devices, and don't actually discuss which board is providing those devices.
[22:19] <ogra_cmpc> prpplague, currently all tools we use parse the Hardware line of /proc/cpuinfo
[22:19] <GrueMaster> prpplague: I'm not seeing any specific standard compared to multiple systems I have here.
[22:19] <persia> Then we autodetect what we can do based on the devices.
[22:19] <persia> So that board mapping becomes fuzzy, based on the set of peripherals exposed.
[22:19] <prpplague> thats what i thought , but i was told by "someone" (not sure who) that canonical wanted a sysfs entry
[22:19] <ogra_cmpc> i wouldnt mind one to set a new standard
[22:20]  * persia wonders what they were thinking
[22:20] <rsalveti> prpplague: hm, for gpio there is the omap-gpio...
[22:20] <ogra_cmpc> the /proc/cpuinfo parsing can be really tricky if you miss a tab or space or so
[22:20] <rsalveti> maybe we can probe it if we can have access to the gpio values from userspace
[22:20]  * rsalveti prefers not touching proc/cpuinfo
[22:20] <persia> ogra, Why?  I'd rather map devices, so that if someone creates $random_board with the same SoC as a panda, and the same peripheral devices, it gets the same support, without lying about itself.
[22:20] <prpplague> ogra_cmpc: might have to generate a new class device
[22:21] <rsalveti> prpplague: could be
[22:21] <rsalveti> or letting userspace to decide by probing the gpios
[22:21] <persia>  /sys/class/ is where it'd belong, but I'd be unhappy to see Ubuntu use it.
[22:21] <ogra_cmpc> persia, sure, but having a file thats easier to parse with a predefined entry might make thiings easier
[22:22] <persia> ogra, For all the same reasons that I argue against all the embedded development practices that make things easier short-term for folks building one-off solutions, I reject that entirely.
[23:32] <rsalveti> GrueMaster: what issue did you have after upgrading the packages?
[23:32] <rsalveti> I updated my panda and now it doesn't boot anymore
[23:32] <rsalveti> seems like an upstart issue
[23:39] <GrueMaster> Yep, that's what I am seeing.
[23:39] <GrueMaster> I updated upstart before ureadahead.
[23:40] <GrueMaster> The fact that it doesn't appear to be going beyond mounting root is what puzzles me.
[23:40] <rsalveti> GrueMaster: it mounts the rootfs here
[23:41] <rsalveti> tries to start postfix and hangs
[23:41] <rsalveti> disable postfix and now I can only see the hang :-)
[23:41] <rsalveti> I'm creating another minimal rootfs with rootstock to see if I didn't mess with anything
[23:41] <ogra_cmpc> try downgrading it
[23:41] <rsalveti> I had an old rootfs there
[23:42] <ogra_cmpc> (either chroot into the SD on an x86 or dpkg -x the older upstart into /mountpoint/of/SD
[23:42] <ogra_cmpc> )
[23:42] <rsalveti> yep
[23:42] <rsalveti> and debug upstart
[23:43] <rsalveti> oh.. how I love it
[23:43] <ogra_cmpc> yesah
[23:43] <ogra_cmpc> well, lets bug Keybok if its really upstart, he is usually helpful (if he gets online :P)
[23:44] <rsalveti> yeah, but first we need to identify if our problem is upstart
[23:44] <ogra_cmpc> well, if downgarding the package fixes it ...
[23:44] <GrueMaster> I have a definite advantage here.  Babbage w/ two SD slots.
[23:44] <rsalveti> yep
[23:44] <rsalveti> lots and lots of issues on our current image :-(
[23:44] <ogra_cmpc> yes :(
[23:45] <rsalveti> it's going to take a while to be able to test efl with sgx and stuff asac asked us to do
[23:45]  * ogra_cmpc goes back to his midnight dinner
[23:45] <rsalveti> see ya
[23:50] <GrueMaster> rsalveti: if you send me the cmdline for rootstock, I can build my own image for the XM here.  Much faster as I have my own mirror server.
[23:52] <rsalveti> GrueMaster: I'm just finishing putting everything into my sd card, then will dd from it
[23:52] <rsalveti> so others can test
[23:52] <rsalveti> but if you want, this is how I'm generating it: ./rootstock --fqdn beaglexm-maverick --login ubuntu --password ubuntu --dist maverick --serial ttyS2 --components "main universe multiverse" --seed linux-image-omap
[23:52] <rsalveti> use rootstock upstream
[23:53] <prpplague> rsalveti / ogra_cmpc / GrueMaster :  http://paste.ubuntu.com/484226/
[23:53] <prpplague> pandaboard revision reporting
[23:53] <prpplague> it reports it as part of the boot up
[23:53] <prpplague> and has the board revision available under /sys/kernel/pandaboard/board_revision
[23:53] <prpplague> any issues with that?
[23:55] <rsalveti> I'd prefer something more generic, like /sys/kernel/board/revision
[23:55] <rsalveti> and then inside you'll have pandaboard: 0.1
[23:55] <rsalveti> for example
[23:55] <rsalveti> because then we can later use that for beagle
[23:59] <GrueMaster> rsalveti: Thanks.
[23:59] <prpplague> understood, making the change now
[23:59] <GrueMaster> prpplague: I have to agree with rsalveti on that one.
[23:59] <prpplague> np