[02:13] <GrueMaster> rsalveti: Still hanging around?
[02:14] <rsalveti> GrueMaster: yup
[02:18] <GrueMaster> Interesting info on our audio issues.  Quick update:  Dove & panda are new hardware for this cycle, hence new bugs.  Beagle, however, works with lucid, fails with maverick.
[02:18] <rsalveti> GrueMaster: but new kernel for beagle, that could explain
[02:19] <GrueMaster> new everything.  New kernel, new alsa, new pulseaudio...
[02:19] <GrueMaster> Lots of variables.
[02:19] <rsalveti> true
[02:20] <GrueMaster> And I have eliminated the kernel for the most part, as I can run speaker-test just fine.
[02:20] <rsalveti> hm, ok
[02:21] <GrueMaster> Oh, and btw, our own David Henningsson has created an alsamixertest script that should help in figuring out what needs to be in alsa.conf.
[02:22] <GrueMaster> https://launchpad.net/~diwic/+archive/maverick
[02:22] <GrueMaster> I haven't tested it yet, but I have built it for armel.
[02:23] <GrueMaster> Requires a loopback cable (hp<>mic), and all mine are currently tied up.
[02:23] <rsalveti> hm, cool
[02:24] <rsalveti> if you want to test that with panda, I sent you an email with latest deb, that has probably everything we need from the kernel side
[02:24] <GrueMaster> At any rate, it has been a long day of testing.  I'm going to backup this fresh lucid image on my beagle, then kill it with an upgrade.
[02:24] <rsalveti> setting up the card name and everything
[02:24] <GrueMaster> Yea, I saw the email  Also planned on doing that before I call it quits.
[02:25] <rsalveti> cool
[06:27] <rsalveti> berco: can you share with us the file /usr/share/alsa/cards/SDP4430.conf? want to test with latest audio patch series
[06:28] <rsalveti> I'm already getting SDP4430 - SDP4430 from /proc/asound/cards
[07:23] <Xase> ... Can anyone assist me in setting up an ARM toolchain for ubuntu x86
[07:26] <persia> Xase, What are you seeking to accomplish?
[07:26] <rsalveti> Xase: with maverick you just need to isntall the correct packages
[07:26] <Xase> To build the android Kernel for an arm device.
[07:27] <Xase> /bin/sh: arm-eabi-gcc: not found
[07:27] <Xase> I have Maverick.
[07:27] <Xase> What packages?
[07:27] <rsalveti> gcc-4.5-arm-linux-gnueabi for example
[07:27] <Xase> ...
[07:27] <persia> Xase, Which release are you running?
[07:27] <rsalveti> just give apt-cache search arm-linux
[07:27] <Xase> Well that would explain that's why I couldn't find it.
[07:27] <Xase> Lol
[07:27] <rsalveti> you should see the cross packages
[07:27] <Xase> I had no idea that's what apt-cache did.
[07:28] <Xase> Man... I wish there was a "ubuntu-phone" I could be running instead.
[07:28] <Xase> Or if MeeGo was a little more... well going.
[07:28] <Xase> :D
[07:28] <persia> Xase, It's called "Kubuntu-Mobile"
[07:29] <Xase> No effin way >_>
[07:29] <persia> Mostly gets tested on the n900s
[07:29] <Xase> ... I almost bought one of those.
[07:29] <persia> But needs a few hacks, because the n900 kernel isn't open, etc.
[07:29] <persia> Also works for i386 phones (but actually doesn't have the driver for the baseband chip in my x86 phone)
[07:29] <rsalveti> the kernel is open
[07:30] <Xase> ... there are x86 phones?
[07:30] <persia> rsalveti, Not according to the kubuntu-mobile guys 12 hours ago.  Are you sure?
[07:30] <Xase> Now you're just blowing my mind.
[07:30] <persia> Xase, Yes, but this isn't the best channel to discuss them :)
[07:30] <rsalveti> persia: well, afaik yes
[07:30] <Xase> Of course not.
[07:30] <Xase> But now I must google explosively.
[07:30] <rsalveti> you could try upstream + additional patches from the stock kernel
[07:30] <persia> rsalveti, Maybe some closed drivers or something?  I dunno: there's a special procedure.
[07:30] <rsalveti> you can grab the kernel sources from it
[07:31] <rsalveti> generally you should just take care of the battery and watchdog stuff
[07:31] <rsalveti> to avoid random resets
[07:31] <Xase> Hmm
[07:31] <Xase> still reports: /bin/sh: arm-eabi-gcc: not found
[07:31] <persia> rsalveti, You might want to touch base with rbelem and ian_brasil: they'd love to have a less complicated procedure :)
[07:31] <persia> Xase, Which release are you running?
[07:32] <Xase> Maverick.
[07:32] <rsalveti> Xase: after installing the correct packages you should see arm-linux-gnueabi-gcc
[07:32] <rsalveti> persia: sure, I worked with them directly at indt already, will try to ping them later
[07:32] <persia> And if your build file needs arm-eabi-gcc, you'll have to modify the build file.
[07:32] <rsalveti> to understand what's going on :-)
[07:32] <Xase> /bin/sh: arm-eabi-gcc: not found
[07:32] <persia> rsalveti, I thought you'd find them familiar names :)
[07:33] <Xase> ln -s arm-linux-gnueabi-gcc arm-eabi-gcc ?
[07:33]  * rsalveti listening a cool mp3 from temple of the dog at his omap 4 board 
[07:33] <rsalveti> with latest patches
[07:33] <Xase> Wouldn't just a symbolic link be fine?
[07:33] <rsalveti> but still manual work on alsa side
[07:33] <rsalveti> Xase: question is, why?
[07:33] <rsalveti> your build script is the wrong guy here
[07:33] <Xase> ... so I don't have to keep modifying stuff.
[07:34] <Xase> I didn't create the build script.
[07:34] <Xase> Blame Google.
[07:34] <rsalveti> well, you can then create a link and mess with your system :-)
[07:34] <rsalveti> but I guess that at least this part is expected from you to change it
[07:34] <rsalveti> it's the cross-compiler
[07:36] <Xase> So you'd instead recommend just modifying the build script?
[07:37] <rsalveti> yup
[07:37] <rsalveti> cooloney: I think I found a possible culprit for the mem issue
[07:38] <rsalveti> cooloney: http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-maverick.git;a=commitdiff;h=644bab98ce980246e6b945962fec9a733a48c325;hp=adaf930e8ae3eaca5d8eda744dfce96caf71447e
[07:38] <rsalveti> cooloney: at http://kernel.ubuntu.com/git?p=rsalveti/ubuntu-maverick.git;a=shortlog;h=refs/heads/rsalveti-ti-omap4-1gb I added the previous patches and this latest one on top
[07:38] <Xase> Darn that's inexplicably complicated at the moment.
[07:38] <Xase> Lemme find my CTRL+F
[07:38] <rsalveti> cooloney: you can find the deb file at http://people.canonical.com/~rsalveti/maverick/kernel/es2/linux-image-2.6.35.3+_2.6.35.3+-87_armel.deb if you want to test it
[07:38] <cooloney> rsalveti: got it, awesome man
[07:39] <rsalveti> I'm running the 5th build atm, no issues
[07:39] <rsalveti> without highmem
[07:39] <rsalveti> if I use highmem I'll always get this problem
[07:39] <cooloney> rsalveti: yeah, let me try it. 2G:2G split right
[07:39] <rsalveti> cooloney: we were missing one errata for pl310
[07:40] <rsalveti> cooloney: then I found that at the upstream l-o we already got a patch that selects the errata by default
[07:40] <rsalveti> just did the same thing
[07:41] <Xase> bah arm-eabi-gcc isn't specified in either Kbuild or Makefile >_>
[07:41] <cooloney> rsalveti: so even we enable this errata for pl310, we still needs 2G:2G split and npitre's patch, right?
[07:41] <cooloney> without highmem
[07:41] <rsalveti> cooloney: yup
[07:41] <cooloney> rsalveti: thanks, got it
[07:41] <rsalveti> cooloney: that could be at least one workaround to use 1gb
[07:41] <rsalveti> while we try to debug the highmem issue
[07:41] <rsalveti> but would prefer to test highmem with upstream
[07:41] <cooloney> rsalveti: yeah, just in time, a workaround to us 1G for our release
[07:42] <rsalveti> but even getting the mmc fix, couldn't get it recognized with upstream kernel
[07:42] <cooloney> rsalveti: yeah, i tried patches in l-o list for mmc of es2.0 board, but the same as you
[07:42] <Xase> arm-linux-gnueabi-menuconfig?
[07:43] <Xase> nm
[07:43] <Xase> I'm reading wrong.
[07:43] <rsalveti> cooloney: description of the errata: http://paste.ubuntu.com/503055/
[07:43] <Xase> so wrong.
[07:43] <Xase> Just do yourself a favor and put me on the ignore list.
[07:44] <rsalveti> cooloney: so it seems this could be our culprit, just need more testing
[07:44] <rsalveti> will let it building during the night and check it tomorrow
[07:44] <rsalveti> but so far so good
[07:45] <rsalveti> 2cpus, with l2, 2g:2g and 1gb support
[07:45] <Xase> BAH
[07:46] <Xase> ...
[07:46] <Xase> Wow.
[07:47] <Xase> I guess this is goodbye guys.
[07:47] <Xase> I just rm'd the arm asm
[07:47] <Xase> from the project file
[07:47] <cooloney> rsalveti: great, man,
[07:48] <cooloney> rsalveti: i will post your patches with npitre's again
[07:48] <Xase> Sweet. Nevermind.
[07:48] <Xase> I need sleep.
[07:49] <rsalveti> cooloney: with highmem I can easily get Unhandled fault: imprecise external abort
[07:49] <Xase> ...
[07:49] <rsalveti> so probably another issue
[07:49] <rsalveti> cooloney: cool, just let do some more testing and then we can post it
[07:49] <Xase> Too tired 2:49 AM... something about supporting nothing but the Calgary with this source >_>
[07:49] <rsalveti> *lets
[07:51] <cooloney> rsalveti: without highmem, it looks like l2 controller pl310 is the root cause. So this errata is necessary.
[07:52] <cooloney> rsalveti: i agree with highmem, it is different from pl310 errata issue.
[07:53] <rsalveti> cooloney: yeah
[07:53] <rsalveti> there's also some more l2x0 patches going upstream: http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=shortlog;h=refs/heads/l2x0-pull-rmk
[07:54] <rsalveti> and sram fixes at http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=shortlog;h=refs/heads/omap_for_2.6.37
[07:54] <cooloney> rsalveti: yeah, i reviewed that before. those l2x patches are for kexec implementation on omap4
[07:55] <cooloney> and it follows Thomas Gleixner's generic one
[07:55] <rsalveti> yep
[07:57] <persia> kexec is awfully nice :)
[07:58] <cooloney> persia: heh, need more testing and backport some patches to enable that.
[07:59] <rsalveti> maybe with 2.6.37 on N :-)
[07:59] <persia> No worries.  I think I need two more cycles before we depend on it :)
[07:59] <Xase> ... gaddangit
[08:00] <Xase> I've messed up my source.
[08:01] <Xase> Gotta read the config a bit more clearly >_>
[08:05] <Xase> Well see, because I couldn't get it to compile I had modified a ton of crap, so now using the plain source... it compiles out of box.
[08:05] <Xase> Thanks #ubuntu-arm
[08:06] <persia> Xase, So it's working for you now?
[08:07] <Xase> Kind of...
[08:07] <Xase> Still getting this "message"
[08:07] <Xase> arch/arm/mach-msm/board-mot.h:125: error: #error Calgary is the only HW supported by this release
[08:07] <Xase> And that's after using the source directly from the Calgary source page.
[08:08] <Xase> I have no clue what it means though so... shrug.
[08:08] <persia> And you're targeting a Calgary device?
[08:08] <Xase> Anyways... anything I can do to help Ubuntu-arm out.
[08:08] <Xase> Yes Persia.
[08:08] <Xase> Also known as the Motorola Devour.
[08:08]  * persia suspects some subtle machine definition in the cross-compiler somewhere.
[08:09] <Xase> Should... I speficy TARGET=Calgary ?
[08:09]  * persia has no information about the source being compiled.
[08:09] <Xase> I'm new to any sort of compiling outside of software...
[08:09] <persia> If that's a sensible option, try it.
[08:09] <Xase> It's the source for the Calgary Device.
[08:10] <persia> Note that you'll probably get better advice about the specific compilation steps from a Calgary-specific resource (wiki, forum, channel, mailing list, etc.).  We mostly focus on running Ubuntu native on ARM.
[08:10] <persia> (with a wink and nod at limited cross-compilation)
[08:11] <Xase> TARGET_PRODUCT=calgary makes sense =/
[08:11] <Xase> Yeah.
[08:11] <Xase> Kind of figured.
[08:11] <Xase> If there was anything for the Calgary.
[08:11] <Xase> It's an end-of-lifed device.
[08:11] <Xase> But I am better off asking in Android perhaps ;)
[08:12] <Xase> Again, is there anything I can do to help test/debug ARM Ubuntu?
[08:21] <persia> Xase, If you happen to have hardware that can run it (e.g. Netwalker, Efika MX, Beagleboard, IGEPv2, Efika SmartBook, etc.) and want to help test and fix bugs, that would be great.
[08:22] <Xase> =( I will try
[08:22] <Xase> I might be able to attain something
[08:22] <persia> If you don't have any of that, but have other ARMv7+VFP capable armel hardware with a working (recent) linux kernel, please try our userspace.
[09:34] <berco> rsalveti: sorry, I didn't see your post earlier
[09:35] <berco> rsalveti: I just attached the file to bug #637947
[09:35] <ubot2> Launchpad bug 637947 in linux-ti-omap4 (Ubuntu Maverick) (and 1 other project) "no sound devices on current ES2.0 boards (affects: 1) (heat: 14)" [High,Confirmed] https://launchpad.net/bugs/637947
[09:35] <berco> rsalveti: do you have all you need kernel wise?
[09:53] <NCommander> ogra: you about to help merge? :-)
[10:24] <sveinse> If I want to make a maverick target image, which version of rootstock should I use?
[10:25] <persia> sveinse, theoretically, anything ought work to some degree, but 0.1.99.4 would be most likely to have the best support.
[10:26] <sveinse> thanks
[12:54] <dcordes> Hi. Can somebody point to the oo.org build time problem ?
[13:57]  * dcordes drops a pin
[13:58]  * ogra shades his ears from the noise
[14:00] <dcordes> ^^
[14:08] <dcordes> I see a disruption of the force in 09-29 image
[14:09] <dcordes> it won't start oemconfig althoug I have the semephore set
[14:09] <ogra> hmm, has been tested a lot though (since it's the RC candidate)
[14:09] <ogra> what arch ? omap or omap4 ?
[14:21] <dcordes> ogra: I picked the omap4 and applied the few changes as usual
[14:21] <ogra> "the few changes" ?
[14:22] <dcordes> it's not much really
[14:22] <dcordes> I install my kernel modules
[14:22] <dcordes> add few networking scripts
[14:22] <dcordes> and do
[14:22] <dcordes> 'touch /var/lib/oem-config/run'
[14:22] <dcordes> usually after that, I start the rootfs and it will run oemconfig
[14:23] <dcordes> no problems
[14:23] <ogra> yeah, it surely does for us
[14:23] <dcordes> It might be corruption then. I see some error message:
[14:24] <dcordes> Use of uninitialized value $item in hash element at /usr/share/perl5/Debconf/Format/822.pm
[14:25] <ogra> yeah, smells like
[14:25] <dcordes> need to get to the library and download the new image @ 3,3MB/s againm
[15:03] <rsalveti> berco: thanks
[15:04] <rsalveti> berco: got the file from latest proposed tree with tons of sound patches
[15:04] <rsalveti> *kernel
[15:14] <cooloney> rsalveti: i am going to post out our highmem issue workaround patch including your pl310 errata one.
[15:14] <cooloney> rsalveti: do you think we need more test
[15:15] <rsalveti> cooloney: well, just saw that I'm going to the 10th build here
[15:15] <rsalveti> no issues
[15:15] <rsalveti> so it seems better
[15:15] <rsalveti> cooloney: were you able to test?
[15:15] <rsalveti> i just tested using usb, didn't test yet with mmc
[15:16] <rsalveti> but you can propose it, np, it's a fix anyway that we're not using atm
[15:17] <cooloney> rsalveti: yeah, i tested it on my mmc, just 1 build, it passed.
[15:17] <cooloney> rsalveti: ok, let me post it firstly
[15:17] <rsalveti> cool
[15:20] <cooloney> rsalveti: you know, it is quite slow for me to connect with ports.ubuntu.com
[15:20] <cooloney> rsalveti: drive me crazy
[15:20] <cooloney> rsalveti: i will test audio fixing tomorrow.
[15:22] <rsalveti> yeah, can imagine
[15:24] <cooloney> rsalveti: thx for the testing, it seems like that you're never sleep
[15:26] <rsalveti> cooloney: I try to :-)
[15:26] <rsalveti> cooloney: I saw you changed my patch to change just the config file
[15:26] <rsalveti> while it works for us, as we build just one flavor, I decided to change the Kconfig because this was the same change that went upstream
[15:27] <rsalveti> that would fix the issue for all ARCH_OMAP4 boards
[15:28] <rsalveti> but I'm ok with your patch, just to let you know why I changed the Kconfig :-)
[16:07]  * rsalveti lunch
[16:46] <robclark> hmmm...
[16:46]  * robclark somehow manages to murder an mmc card with fdisk..
[16:49] <GrueMaster> btdt.
[16:49] <GrueMaster> I usually end up doing a complete nuke at that point.  dd if=/dev/zero of=/dev/<SD Card>
[16:50] <robclark> no... I no longer even get a device file for the card
[16:53] <GrueMaster> ouch
[16:53] <GrueMaster> May need to reboot.
[16:54] <GrueMaster> Also, I discovered on one of my cards that one of the plastic guides on the side near the contacts had bent covering the contact.  Breaking it off fixed it.
[16:56] <GrueMaster> ogra_ac: For the release notes:  upgrading beagle from lucid->maverick can run of of free space if USB drive is 4G or less.  Haven't tried yet on larger.
[16:56] <ogra_ac> mind to talk to skaet and add it to the wiki `
[16:56] <ogra_ac> ?
[16:57] <GrueMaster> I'll drop a not on #u-release.
[16:57] <GrueMaster> note even.
[17:25] <prpplague> ogra_ac: ping
[17:27] <ogra_ac> prpplague, i'm here
[17:27] <prpplague> ogra_ac: hey, we were discussing possibly using a usb->sata on the bamboo board
[17:27] <prpplague> ogra_ac: any thoughts on that?
[17:28] <ogra_ac> you will be easily maxing out the USB with that i guess
[17:28] <ogra_ac> the babbage imx51 board has such a setup, not really an advantage over a simple external USB disk
[17:29] <prpplague> well the EHCI through put it pretty stable
[17:29] <prpplague> ogra_ac: are they using OHCI or EHCI ?
[17:29] <ogra_ac> ehci
[17:29] <ogra_ac> ~24MB/sec reported by hdparm
[17:29] <prpplague> ahh
[17:31] <ogra_ac> and i doubt you can get much more through USb
[17:32] <ogra_ac> so i guess just attaching SATA to the USB bus wont really gain much over a cheapo external USB disk directly attached to USB
[17:32] <prpplague> yea that is kinda of why i didn't consider it
[17:32] <prpplague> other than size of storage
[17:32] <ogra_ac> i thought there was a way to attach it differently ?
[17:32] <GrueMaster> It would be nice for convenience, but won't enhance performance.
[17:32] <ogra_ac> gpio?
[17:33] <prpplague> ogra_ac: it is possible to do PATA via the GPMC, and then use a PATA->SATA bridge
[17:34] <robclark> prpplague: maybe even PATA is fine.. I think they still sell those
[17:34] <ogra_ac> ah
[17:34] <robclark> ;-)
[17:34] <ogra_ac> GPMC, right
[17:34] <GrueMaster> Hmm.  PATA<>CF would be interesting.
[17:34] <ogra_ac> yeah, even PATA would rock
[17:34] <prpplague> GrueMaster: PATA to CF is pretty easy
[17:35] <prpplague> the only thing that would have to be done is a kernel driver to "work the gpmc" like a PATA interface
[17:35] <GrueMaster> Yes I know.  I have 3 running systems that way.  Fileserver, firewall, and serial-console monitor.
[17:35] <robclark> prpplague: well get crackin!  ;-P
[17:36] <robclark> GPMC->PATA would probably drive two hd's, wouldn't it?  A master and slave..
[17:36] <prpplague> robclark: gotta finish current project first
[17:36] <GrueMaster> Pfft.  Multitask.
[17:36] <GrueMaster> :P
[17:36] <prpplague> robclark: not sure i have enough chipselect signals to do two
[17:37] <robclark> hmm..
[17:40] <robclark> prpplague: I guess I don't need both LED's..  depopulate one, some blue wire, and use that gpio as an extra CS?
[17:41] <prpplague> robclark: negative
[17:41] <prpplague> robclark: the controls need to be tied to the gpmc controller
[17:41] <prpplague> robclark: the gpmc has it's on chipselects and such to control memory read/writes
[17:56] <ogra_ac> ARGH !!!!
[17:56] <ogra_ac> who designed the pandaboard.org page !!!!!
[17:57]  * ogra_ac just linked the logo in a blog post ... 
[17:57] <ogra_ac> at least i thought i link the logo
[17:57] <ogra_ac> sigh
[17:57] <ogra_ac> the whole page is a jpeg
[17:57] <GrueMaster> Heh.
[17:57] <ogra_ac> what an insanity !!
[17:59] <rsalveti> ogra_ac: hehe
[17:59] <rsalveti> they asked already to change to at least a png
[18:01] <ogra_ac> that wont make it smaller though ... i just bloated planet.ubuntu.com with it
[18:02] <robclark> I don't know what you guys are talking about...  pandaboard.org looks fine in lynx ;-)
[18:02]  * robclark ducks
[18:03] <ogra_ac> LOL
[18:03] <GrueMaster> HA
[18:03] <robclark> ogra_ac: maybe orbarron could send you a more appropriately sized logo?
[18:04] <ogra_ac> robclark, well, its fine now
[18:04] <ogra_ac> i'll just live with the embarrasement
[18:09] <gourneau> Can rootstock be used to build debian root fle systems?
[18:11] <ogra_ac> gourneau, i dont think anyone tested that ever
[18:12] <dcordes> ogra_ac: any ac100 kernel news ?
[18:12] <gourneau> Maybe it will be me then, I want to use Ubuntu.  How are the seed images defined?
[18:13] <ogra_ac> dcordes, see planet.ubuntu.com
[18:13] <ogra_ac> (no, no kernel news, but fully working images
[18:13] <ogra_ac> )
[18:14] <dcordes> ogra_ac: ah well didn't see any user space problems ..
[18:14] <ogra_ac> dcordes, plenty
[18:15] <dcordes> the SoC doesn't support neon right ?
[18:15] <ogra_ac> right
[18:17] <dcordes> what userspace related problems do you see ?
[18:17] <dcordes> did you create a meta bug ?
[18:17] <ogra_ac> android kernel
[18:17] <ogra_ac> no
[18:17] <ogra_ac> i dont think you will see any official support for the device any time soon
[18:17] <dcordes> haha sometimes you make me laugh
[18:18] <ogra_ac> feel free to create one though
[18:18] <dcordes> I am looking to make things work, not if they will magically fix.
[18:18] <ogra_ac> dcordes, thne tak to phh in #ac100 :)
[18:18] <dcordes> I know the bum
[18:18] <ogra_ac> *then talk
[18:19] <ogra_ac> he has done a lot of low level stuff
[18:19] <ogra_ac> and is still doing
[18:19] <dcordes> without kernel source ?
[18:19] <ogra_ac> well, there kind of is kernel source
[18:20] <ogra_ac> its not as if there wouldnt be public branches of tegra eclair
[18:20] <dcordes> now you got me all confused
[18:20] <ogra_ac> the kernel supports modules ;)
[18:20] <ogra_ac> you cant change the core indeed
[18:21] <gourneau> Does anyone know of a good Ubuntu tablet about 7 inches, with a host USB port.  The smartq v7 is the best I can find.
[18:28] <dcordes> gourneau: htc hd2 but you need to supply external power for the usb and the display is not 7 inches
[18:29] <ogra_ac> and you can run ubuntu natively ?
[18:35] <orbarron> orga_ac: pandaboard.org is a temp site for now... plz forgive the jpeg
[18:36] <dcordes> ogra_ac: yes
[18:36] <dcordes> ogra_ac: http://vimeo.com/14630263
[18:36] <ogra_ac> orbarron, i dont care about jpeg, i care about that i right clicked the logo and pasted ion my blog post ... now my post has the whole site in it
[18:36] <dcordes> ogra_ac: with full snappyness
[18:37] <dcordes> lol bluepaste :>
[18:37] <GrueMaster> ogra_ac: Do any of our initramfs scripts touch nand on beagle?  I keep getting nand i/o errors on mtdblock0.
[18:38] <ogra_ac> GrueMaster, nope
[18:38] <GrueMaster> But only after upgrading lucid to maverick (which replaces the kernel in nand).
[18:38] <ogra_ac> GrueMaster, not in maverick
[18:38] <GrueMaster> Very odd.
[18:38] <GrueMaster> That's what I thought.
[18:38] <ogra_ac> oh, upgrade is different
[18:38] <ogra_ac> that still uses nand indeed
[18:38] <GrueMaster> No, this is running a preinstalled image.
[18:39] <dcordes> Is there any known breakage in 27th omap4 preinstalled image ?
[18:39] <GrueMaster> But I only get the error if the maverick kernel is also in nand.
[18:39] <GrueMaster> dcordes: Use the 29th.  It will be the official RC.
[18:40] <dcordes> GrueMaster: ok I downloaded it already but had some strange problem
[18:41] <dcordes> sounds like it must be on my end if you consider it for RC
[18:41] <dcordes> somebody interested in adding HTC HD2 maverick RC infomration in planet ?
[18:42] <dcordes> then we have covered the full embedded family
[18:42] <dcordes> smartbook, dev board and cell phone
[19:11] <dcordes> nevermind :)
[19:16] <devilhorns> grrrrr
[19:16] <devilhorns> someone needs to spank the icon designers
[19:18] <ajay> hi all , i have igep board but in minicom i am getting message as ����
[19:18] <ajay> no boot prompt
[19:19] <GrueMaster> devilhorns: Are you referring to bug 651391?
[19:19] <ubot2> Launchpad bug 651391 in gnome-control-center (Ubuntu) "Changing desktop font changed entire theme appearance in une-efl (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/651391
[19:19] <devilhorns> GrueMaster, no, gimme a sec, I will show you my "gripe" :)
[19:19] <rsalveti> ajay: probably missing x-loader and u-boot
[19:20] <ajay> but green light is glowing on that board
[19:20] <devilhorns> GrueMaster, ok, keep in mind when you look @ this, that my code does everything properly (in that it centers the icons)
[19:20] <devilhorns> http://home.comcast.net/~devilhorns/files/unity_efl.png
[19:20] <devilhorns> GrueMaster, but, look @ the button
[19:21] <devilhorns> and looking @ the icon itself, you can see "the problem"
[19:21] <GrueMaster> Yep.  Icons aren't centered in their frame.  Bad.
[19:22] <devilhorns> yep :)
[19:22] <devilhorns> now what kinda moron makes icons like that ... *sigh*
[19:22] <ajay> rsalveti, is this happens due to any null modem cable error as well?
[19:22] <GrueMaster> There's probably a patent if they did.
[19:22] <rsalveti> ajay: could be, but generally you get tons of weird characters when getting garbage
[19:22] <devilhorns> a patent for centering icons ? I highly doubt that :)
[19:23] <rsalveti> ajay: are you open it with 115200?
[19:23] <ajay> yes
[19:23] <GrueMaster> Never know with software patents.
[19:23] <ajay> hw and sw flow control is off
[19:23] <rsalveti> generally I never use minicom, just screen /dev/ttyUSB0 115200 is enough for me
[19:23] <devilhorns> GrueMaster, well, if that is the case, then every designer on the planet is in trouble :) I mean really, how Doesn't center images ? :)
[19:23] <rsalveti> but could be cable issues also
[19:23] <rsalveti> maybe wrong pins
[19:24] <GrueMaster> heh
[19:24] <ajay> rsalveti, i have checked i am using cross cable
[19:24] <ajay> null modem
[19:24] <ajay> IDC10 DB9 also as mentioned in websites
[19:26] <ajay> rsalveti, for screen /dev/ttyUSB3 115200 also i am getting just blank screen
[19:26] <rsalveti> ajay: any garbage?
[19:26] <ajay> nothinmg
[19:26] <ajay> if i write then it is getting garbage
[19:27] <ajay> rsalveti, if i write same thing is getting printed
[19:27] <rsalveti> hm
[19:28] <ajay> just for enter key getting printed at start �
[19:28] <devilhorns> GrueMaster, btw
[19:28] <ajay> is it cable problem?
[19:28] <ajay> or uboot xloader got corrupted
[19:28] <devilhorns> that bug is not in une-efl ... it's a control-center (appearance properties) problem
[19:28] <GrueMaster> That's what I thought when I filed it.
[19:29] <rsalveti> ajay: could be, but it it was corrupted you should not get any echo from uart
[19:29] <ajay> rsalveti, but not even getting uboot prompt
[19:29] <ajay> or any message saying loading
[19:30] <devilhorns> yea, the issue is that "appearance-properties" creates a "custom" theme whenever you change any "looks" (fonts, colors, etc). When it creates that "custom" theme, it takes the base theme, changes all the properties for it in gconf, then saves it. When it does the changes, it reads the values of the original theme (icons, colors, etc) and updates gconf values for that
[19:30] <pcacjr__> ajay: are you doing that with sudo ?
[19:30] <rsalveti> ajay: I would first suggest you to make sure you're using a valid x-loader and u-boot
[19:30] <rsalveti> if I'm not wrong, there's a default one at the nand
[19:30] <devilhorns> so modifying anything, resets all the gconf properties to default for that "base theme", and saves the custom values
[19:31] <rsalveti> then checking if the cable and etc is correct
[19:31] <devilhorns> so it's reseting "icon theme" to the default for that original theme
[19:31] <ajay> pcacjr, i am doing with root
[19:32] <ajay> rsalveti, how to make sure that i am using valid xloader or u-boot
[19:32] <pcacjr__> rsalveti: should he at least get some weird bytes on the screen ?
[19:33] <devilhorns> GrueMaster, @ any rate, I'm not going to "doctor" my code for badly designed icons :) the centering issue will remain just that. an "issue" because of bad icons :)
[19:33] <GrueMaster> I wouldn't either.  File a bug on the icon set.
[19:33] <rsalveti> ajay: getting the stock one, provided by the igep website
[19:33] <rsalveti> pcacjr__: yup
[19:33] <devilhorns> GrueMaster, indeed :) Will do that later when I have some time
[19:34] <rsalveti> ajay: http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=8&zenid=701aa01925001b84ed070559d8ac0851
[19:34] <rsalveti> probably same one from beagle
[19:35] <ajay> rsalveti, i have same one
[19:35] <rsalveti> ajay: http://www.igep.es/index.php?option=com_content&view=article&id=99&Itemid=112&dir=/var/www/vhosts/igep.es/httpdocs/downloads/01-ISEE_Products/IGEPv2/SW_Releases/binaries
[19:37] <ajay> rsalveti, shall i keep xloader and uboot in sdcard
[19:37] <ajay> from above link
[19:38] <rsalveti> yep, at least at beagle you can boot using the x-loader and u-boot from the sdcard by using the user button, don't know if we have the same for igepv2
[19:38] <ajay> rsalveti, no there is no button for igep
[19:38] <ajay> rsalveti, http://labs.igep.es/index.php/How_to_recover_a_IGEP_bricked_board
[19:39] <ajay> this site is for showing to recover a board
[19:39] <ajay> but not sure shall i follow these steps
[19:42] <dcordes> bbl
[19:42] <rsalveti> ajay: well, if you just follow these steps you'll for sure be able to flash a valid x-loader and u-boot, and get something at your uart
[19:42] <rsalveti> if you set up your sd and still see garbage, than your problem could be related with your cable setup
[19:55] <devilhorns> anyone running unity ?
[19:59] <ajay> rsalveti, is this problem due to power cable also?
[20:00] <rsalveti> ajay: just if you're not using the proper 5v one
[20:17] <ogra_ac> bug 607752
[20:17] <ubot2> Launchpad bug 607752 in ubuntu "[needs-packaging] devmem2 needs packaging (affects: 2) (heat: 59)" [Wishlist,New] https://launchpad.net/bugs/607752
[20:17] <ogra_ac> hrm
[20:17] <ajay> rsalveti, i tried above wiki of recovering brick igep board
[20:17] <ajay> but for this also i am getting similar error as no messages
[20:18] <ajay> if i press any key from keyboard hetting printed as �
[20:20] <rsalveti> so probably an issue at your cable setup, or usb-serial converter
[20:26] <lool> rsalveti: Plenty of people get this issue with IGEP
[20:26] <lool> There is a hardware grounding issue I'm sure
[20:27] <lool> one workaround is using a differnt USB serial adapter, or a real PC serial port; another workaround is plugging a mini-USB cable to the IGEP to help grounding
[20:29] <rsalveti> lool: hm, interesting
[20:35] <vgrade> hi guys, anyone working on i.MX51
[20:37] <ogra_ac> amitk does
[20:40] <vgrade> ogra_ac, thanks
[21:02] <GrueMaster> rsalveti: Can you download http://ports.ubuntu.com/dists/maverick/main/installer-armel/20100211ubuntu28/images/omap/netboot/omap/* and try on your beagleXM?  I am seeing it either not detecting my USB keyboard or it is locking up hard.
[21:02] <rsalveti> GrueMaster: sure
[21:02] <GrueMaster> You will have to copy these to an existing image partition1 to get MLO & u-boot.bin
[21:03] <rsalveti> sure, np
[21:03] <rsalveti> GrueMaster: which image did you use as base?
[21:03] <GrueMaster> RC
[21:03] <GrueMaster> Or 20100929.
[21:04] <rsalveti> OK, ping back you in some minutes
[21:07] <GrueMaster> too bad u-boot for beagle doesn't support tftp.  Make my life much easier.
[21:12] <ogra_ac> rsalveti, GLES packages uploaded
[21:13] <ogra_ac> cross your fingers that the release team lets them in :)
[21:13] <rsalveti> ogra_ac: cool, let's wait and see :-)
[21:13] <rsalveti> ogra_ac: where can I track it?
[21:13] <ogra_ac> i filed bug 652347
[21:13] <ubot2> Launchpad bug 652347 in ubuntu "[needs-packaging] opengles-sgx-omap3 and powervr-omap3 need to be packaged for maverick (affects: 1) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/652347
[21:13]  * ogra_ac hopes thats enough to justify the FFe 
[21:14] <ogra_ac> rsalveti, some clear final statement for bug 607752 would be helpful btw
[21:14] <ubot2> Launchpad bug 607752 in ubuntu "[needs-packaging] devmem2 needs packaging (affects: 2) (heat: 59)" [Wishlist,New] https://launchpad.net/bugs/607752
[21:15] <rsalveti> yup, devmem2 is very useful but ugly
[21:16] <ogra_ac> right
[21:16] <ogra_ac> the discussion just doesnt end clearly with "we will use it"
[21:17] <rsalveti> ok, will comment on it
[21:35] <GrueMaster> rsalveti: I get the same results on the beagle & beagleXM with the netboot image.  complete lockup.
[21:36] <rsalveti> weird, my image is just resizing, will test it when it finishes
[21:36] <rsalveti> now creating swap...
[21:36] <GrueMaster> resizing?
[21:36] <GrueMaster> It should boot into the debian installer.
[21:37] <rsalveti> yep, but I was going to test your kernel to see if it works or not
[21:38] <GrueMaster> Make sure you are using the boot.scr, uImage and uInitrd from http://ports.ubuntu.com/dists/maverick/main/installer-armel/20100211ubuntu28/images/omap/netboot/omap/*
[21:38] <rsalveti> I just flashed 20100929
[21:38] <GrueMaster> Oh.
[21:38] <rsalveti> yup, will use that
[21:38] <GrueMaster> No need to go through the preinst boot stuff.
[21:39] <rsalveti> I know, just wanted to at least have a proper rootfs
[21:39] <rsalveti> ok, will use your kernel and initrd now
[21:39] <GrueMaster> Why?  It creates one (or it is supposed to).
[21:40] <GrueMaster> brb
[21:41] <ogra_ac> rsalveti, the initrd contains the debian-installer
[21:41] <ogra_ac> it will wipe your rootfs
[21:42] <rsalveti> oh, ok, didn't know the debian-installer was inside it
[21:42] <rsalveti> yep, so just booting it should be enough
[21:42] <rsalveti> let me try
[21:42]  * rsalveti used with the pre-installed image
[21:42] <ogra_ac> the great thing is that the whole installer lives in ram
[21:42] <ogra_ac> so you can do whatever you like to your disks
[21:48] <ward|> whats the simplest way of getting a rootfs for my PXA272 based PDA ? i should be able to roll my own kernel
[21:48] <ogra_ac> see /topic
[21:48] <ogra_ac> ;)
[21:48] <ward|> is that the simplest way?
[21:48] <ward|> allready saw that
[21:48] <rsalveti> GrueMaster: yup, no usb
[21:49] <rsalveti> GrueMaster: probably missing modules...
[21:49] <ogra_ac> rsalveti, yeah
[21:49] <rsalveti> let me boot with uart
[21:49] <ogra_ac> old re-occuring bug
[21:50] <ward|> ogra, oh never mind, it cant get much simpler than that i see :p
[21:50] <ogra_ac> ward|, yep :)
[21:52] <rsalveti> no modules at all
[21:52] <rsalveti> not good
[21:55] <ward|> so together with a 2.6.x kernel this should work fine? is there a minimum version or something?
[21:58] <ogra_ac> ward|, udev in ubuntu is usually tied closely to the kernel version
[21:58] <ogra_ac> ward|, so you should make sure yu have something matching
[21:59] <ward|> ogra, ah, so if i only got one specific kernel version i can compile, i should forget about it and use another distro?
[21:59] <ogra_ac> which version do you have ?
[22:03] <ward|> ogra, let me see
[22:04] <ward|> ogra, 2.6.26
[22:04] <ogra_ac> ugh
[22:04] <ogra_ac> thats ancient
[22:04] <ogra_ac> with luck you can use jaunty on that
[22:04] <ogra_ac> but jaunty is EOL in a few weeks
[22:05] <ward|> well its not really coneniant updatiung the kernel all the time on a closed source PDA lol
[22:05] <ogra_ac> indeed
[22:07] <GrueMaster> Ok, netboot for dove works.  Just finished.
[22:15] <rsalveti> GrueMaster: so, no modules at your uInitrd
[22:16] <GrueMaster> Well now.  That would be a bad thing.
[22:21] <rsalveti> ndec: upstream kernel is activating the errata for arch_omap4: https://patchwork.kernel.org/patch/183142/
[22:21] <rsalveti> so I believe it should be fine with it
[22:21] <rsalveti> at least my board is still up and building after using the errata
[22:22] <rsalveti> 20 hours, and 9 builds
[22:23] <ndec> rsalveti: but my understanding is that this errata is not needed on es2.0, it's fixed in the arm chip in es2.0...
[22:24] <ndec> rsalveti: but i might be wrong ;-)
[22:24] <rsalveti> ndec: yep, thought the same but couldn't find anything about it =\
[22:29] <rsalveti> GrueMaster: any idea why we're building the initrd without any modules?
[22:29] <rsalveti> ogra: said that this is a re-occuring bug
[22:29] <ogra> rsalveti, space
[22:29] <GrueMaster> Nope.  Ask an engineer.  btw, meeting.
[22:29] <rsalveti> yup
[22:59] <ward|> ogra, i think i found out why the devs chose 2.6.26 lol
[23:00] <ward|> ( ogra, provided you are ogra_ac)
[23:00] <ogra> yes, i'm both on differnt devices in different rooms
[23:00] <ward|> yeah just making sure :)
[23:01] <ward|> the debian EABI docs use this version aswell, and they make it clear only that one is supposed to work: "NOTE: Take a lot of care, that _only this old linux kernel version works_."
[23:02] <ward|> so maybe there are a lot more devices lie mine with this outdated kernel
[23:03] <ward|> thought i should mention it so ubuntu-arm devs can investigate this if they want to
[23:08] <robclark> ndec / rsalveti: which errata?
[23:09] <rsalveti> robclark: PL310_ERRATA_588369
[23:09] <robclark> ok.. let me check
[23:10] <robclark> rsalveti: ok.. this one seems to apply to the cortex-a9 IP, prior to r2p0
[23:10] <robclark> (just need to check which rev on cortex is in es2.0)
[23:11] <robclark> r1p2.. so keep the errata enabled
[23:15] <rsalveti> robclark: oh, cool, thanks for identifying it
[23:19] <robclark> rsalveti: btw, was there any new discoveries on highmem in last couple days?
[23:20] <rsalveti> robbiew: well, we were first trying to debug the issue without highmem, because we always face problems when using highmem
[23:20] <rsalveti> with one cpu, without l2
[23:20] <rsalveti> so then I found that we were not using this errata yesterday
[23:20] <robclark> oh, ok.. so same sort of issue even without highmem?
[23:21] <robclark> so w/ PL310 errata patch, it is getting more stable?
[23:21] <rsalveti> gave it a try and I'm running without highmem, 2g:2g, 1gb, 2cpus and doing well
[23:21] <robclark> ok.. that sounds like an improvement
[23:21] <rsalveti> robclark: more than 20 hours building
[23:21] <robclark> have you tried w/ highmem yet?
[23:21] <rsalveti> no issues
[23:22] <rsalveti> robclark: yup, and still get the issue easily, so probably another bug
[23:23] <robclark> and that is also w/ the nvidia highmem patch?
[23:23] <rsalveti> robclark: yup
[23:23] <robclark> hmm.. ok.. so still another issue lurking :-(
[23:23] <rsalveti> yeah :-( but at least we have a workaround to use 1gb now
[23:24] <robclark> yeah.. I think 2g/2g is way to go for now
[23:25] <rsalveti> and the build is now taking less than 2 hours
[23:25] <rsalveti> using an external usb disk
[23:31] <robclark> ohh..  we tried a USB drive at the last sprint, although I think it was quite a slow usb powered hd..
[23:38] <GrueMaster> That and it was all ES1 then, wasn't it?
[23:39] <rsalveti> probably, and using usb otg
[23:47] <GrueMaster> rsalveti: Can you confirm Bug #652522?  Thanks
[23:47] <ubot2> Launchpad bug 652522 in debian-installer (Ubuntu) "modules missing from omap netboot image. (affects: 1) (heat: 8)" [Medium,New] https://launchpad.net/bugs/652522
[23:48] <rsalveti> GrueMaster: sure