[04:12] <lugu> hi all, may i ask what is the status of GDB? i always run into SIGILL in dl_main... any idea?
[04:13] <GrueMaster> Try asking in #linaro.  They tend to work with those tools far more often, and I believe they may actually be supporting it on arm directly.
[04:13] <lugu> ok thanks!
[05:08] <MrCurious> why cant i find the package that libXxf86misc.so is in?!?!
[05:10] <GrueMaster> try "dpkg-query -S <path-to>/libXxf86misc.so
[05:11] <MrCurious> nope
[05:11] <MrCurious> seems ubuntu chose not to include this library
[05:11] <GrueMaster> Oh, are you looking for it to install?
[05:13] <MrCurious> X11_Xxf86misc_LIB
[05:13] <MrCurious> cant divine out the source package name
[05:14] <GrueMaster> May not be in the images anymore. I am not seeing it on oneiric arm.
[05:15] <GrueMaster> And it isn't on my natty amd64 netbook either.
[05:15] <GrueMaster> seems to be depricated.
[05:15] <MrCurious> so much for libfreenect on ubuntu-arm
[05:16] <MrCurious> oddly enough on 11.04 ubuntu intel ITS THERE
[05:16] <MrCurious> stupid caps lock trigger finger
[05:17] <MrCurious> oh wait
[05:17] <MrCurious> intel debian had it
[05:17] <GrueMaster> 11.04 was natty.
[05:17] <GrueMaster> 10.04 maybe.
[05:17] <MrCurious> 11.04 arm ubuntu lacks it
[05:17] <MrCurious> now my facts feel a little straiter
[05:18] <MrCurious> there have been source packages for it in ubuntu until 10.10 as far as i can see
[05:19] <GrueMaster> Well, the last build I have for it in armel is 2009-12-03
[05:20] <MrCurious> i am on launchpad, and saus its not released for natty
[05:20] <GrueMaster> Ok. I was looking direclty on my mirror, which has everything from 10.04 forward for arm.
[05:21] <GrueMaster> But LP is more diffinative.
[05:21] <GrueMaster> At any rate, I'm running on fumes.  13 hour workday.
[05:22] <GrueMaster> night
[05:23] <ScottK> Meh.  That's hardly over half time.
[06:19] <MrCurious> cvdemo has a decent frame rate on panda connected to a kinect
[06:20] <MrCurious> i am not entirely unpleased
[07:22] <LBo> Hi, does anyone know how to change the extraversion variable when creating kernel packages with dpkg-buildpackage?
[07:22] <LBo> I've tried EXTRAVERSION=-leon dpkg-buildpackage -B -uc -us but that didn't work :)
[07:22] <LBo> make-kpkg doesn't work. It complains about some missing commands from a x86 only package
[08:47] <hrw> x-loader-omap4 was deprecated in favour or x-loader - right?
[08:49] <hrw> ogra_: bug 806864 is for you
[08:49] <ubot2> Launchpad bug 806864 in x-loader-omap4 "remove from repository" [Undecided,New] https://launchpad.net/bugs/806864
[08:55] <infinity> hrw: You win a bug closure! ;)
[09:05] <hrw> fun is that I have this message on oneiric
[09:06] <hrw> once it will finish upgrade I will sent apport-collect
[09:06] <infinity> hrw: Which means you have/had the package installed at one point, and now dpkg has gotten grumpy about the stanza...
[09:06] <infinity> hrw: Perhaps worth filing a bug against dpkg for suddenly being irked by version numbers that it used to let slide.
[09:07] <hrw> un  x-loader-omap4                     <none>                             (no description available)
[09:07] <hrw> ii  x-loader-omap4-panda               1.5.0+git20110325+b6bbfe7-1ubuntu1 Board initialization helper for TI OMAP 4 Panda boards
[09:07] <infinity> hrw: Yes, note the "had"... The stanza is in there because you used to have it installed, I assume.
[09:07] <hrw> added dpkg to bug
[09:07] <infinity> hrw: Or you have maverick in your sources.list or something...
[09:08] <infinity> hrw: (apt-cache policy x-loader-omap4)
[09:08] <hrw> none
[09:08] <hrw> N: Unable to locate package x-loader-omap4
[09:10] <infinity> Kay, then it's just stale info in the available DB from having it previously installed.
[09:11] <hrw> added data to bug
[09:11] <infinity> You can fix *your* issue with "dpkg --forget-old-unavail" probably.
[09:11] <infinity> But the part where dpkg suddenly got stricter is still a bug/misfeature.
[09:13] <hrw> will leave it like it is for now
[09:13] <ogra_> infinity, hmm, do you knnow if GrueMaster re-tested omap3 images ?
[09:13] <infinity> ogra_: What's to re-test, we didn't change them, did we?
[09:14] <ogra_> (the u-boort bug is supposed to be fixed, the iso tracker still lists it)
[09:14] <infinity> Oh.
[09:14] <ogra_> we respun all images yesterday
[09:14] <infinity> I'm not sure what the status of omap3 stuff is, to be fair.  You'll have to ask him in the morning.
[09:14] <ogra_> i see he tested all omap4 and omap3 wont have a fixed kernel
[09:14] <ogra_> i was just curious
[09:15] <infinity> Speaking of images, though.  We still have resizing issues on desktop, apparently.
[09:16] <infinity> Fails to actually resize, explodes with ext3 errors.
[09:16] <infinity> Yet server works fine.
[09:16] <infinity> (Again, this is all second-hand from GrueMaster, so you might want to follow up with him)
[09:17] <ogra_> yeah, we'll skip desktop for A2 i think
[09:18] <ogra_> that will likely need some bigger changes, alonngside with the live-build ones
[09:18] <infinity> Fun, fun.
[09:18] <ogra_> looks to me like the underlying filesystem isnt really resize friendly ... alongside with bugs in jasper
[09:19] <infinity> Well, I'll mangle live-build tomorrow (obviously not uploading until after A2), and pass it by you for a quick review.
[09:20] <infinity> I need to get involved in live-build upstream, I think.  There are things I need to do to it that won't be pretty without upstream buy-in.
[09:20] <infinity> But first, I need sleep.
[09:20] <ogra_> yeah, go to bed
[09:21] <infinity> Yes mom.
[09:21] <ogra_> :)
[09:23] <infinity> hrw: Oh, wait.  I just realised that issue you were seeing was a warning, not an error.
[09:24] <infinity>   * Do not allow versions starting with non-digit when doing strict parsing,
[09:24] <infinity>     warn otherwise.
[09:24] <infinity> hrw: Probably not really bug-worthy at all, just annoying that someone (glances at ogra_) used a policy-breaking version number in the past. :P
[09:25] <ogra_> ??
[09:25] <ogra_> from where is that ?
[09:26] <infinity> ogra_: In maverick, you shipped an x-loader-omap4 that had an "L" as the first character in the version.
[09:27] <ogra_> uh, yeah upstream ...
[09:27] <infinity> ogra_: New dpkg is stricter about policy compliance and now vomits warnings about that being in the status file.
[09:27] <ogra_> hrm ...
[09:27] <infinity> (Traditionally, when upstreams have non-policy-compliant versions, we mangle them, like 0.L4-whatever, etc)
[09:27] <infinity> Anyhow, can't go back in time and fix it.
[09:28] <ogra_> nope, sadly ... that stain stick on me now
[09:28] <infinity> And the number of users who will be upgrading from maverick on omap4 systems can probably be counted without removing my socks.
[09:28] <ogra_> *sticks
[09:28] <ogra_> oh, we might have more then ten that do it
[09:28] <ogra_> not by much though i belive
[09:28] <infinity> Possibly, but I wouldn't say it's a large number. :P
[09:29] <infinity> I don't doubt there were a chunk of maverick omap4 users, but the tester/devel types are probably reinstalling every 3 minutes, and the "normal users" (all 4 of them) are more likely to just re-flash new images than upgrade, on these sorts of devices.
[09:30] <infinity> So.  Meh.  Whatever.
[09:30] <ogra_> yep
[09:31] <infinity> I think I'll just close this dpkg bug then.
[09:32] <infinity> hrw: You can hit me later for having marked two tasks in a row as "invalid" on this bug. :P
[09:32] <infinity> hrw: But at least I left a friendly comment!
[09:33] <ogra_> i wonder why lintian didnt complian, i never roll new packages without checking, i think i would have noticed such an error ...
[09:34] <infinity> Dunno.  Seems odd that it wouldn't, since this has been in policy for over a decade.
[09:34] <infinity> Oh, but it's a "should", not a "must".
[09:34] <ogra_> aww
[09:34] <infinity> Hence why dpkg is warning, not erroring, I guess. :P
[09:34] <infinity> Small mercies.
[09:35] <hrw> infinity: thx
[09:36] <hrw> hrw@panda:~$ LC_ALL=C dpkg --forget-old-unavail
[09:36] <hrw> dpkg: warning: obsolete '--forget-old-unavail' option, unavailable packages are automatically cleaned up.
[09:36] <hrw> ;D
[09:36] <hrw> I had to switch to English translation cause I was unable to understand Polish one ;D
[09:38] <infinity> Automatically cleaned up, eh?  Seems not, in your case. :P
[09:44] <hrw> ;)
[09:48] <infinity> hrw: --clear-avail probably still works. :P
[09:49] <hrw> yes, it does
[09:50] <infinity> For entertainment value, there's a huge policy-versus-dpkg debate in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620566
[09:50] <ubot2> Debian bug 620566 in dpkg "dpkg: "version number does not start with digit" is in" [Normal,Open]
[09:56] <stm__> hi all
[09:57] <stm__> iam running ubuntu 10.04 on my pandaboard
[09:57] <stm__> now i builded a kernel with xenomai
[09:58] <stm__> i replaced uImage of previously running kernel which i got from preinstalled images
[09:58] <stm__> but it giving me some errors
[09:59] <stm__> Is there any documentation to built the ubuntu filesystem for custom builded kernels
[10:02] <hrw> update-initramfs -c -kVER-OF-YOUR-KERNEL?
[10:04] <stm__> the error its giving me is unable to load modules
[10:11] <infinity> Did you install your modules after you compiled the kernel?
[10:16] <ogra_> also copying the config to /boot/config-$version helps
[10:16] <ogra_> iirc update-initramfs checks for that too
[10:17] <stm__> yes i installed my modules
[10:18] <stm__> update-initramfs -c -k 2.6.37.6
[10:19] <ogra_> you could add -v then you see what exactly it tries to do ...
[10:19] <ogra_> might reveal you more info
[10:35] <lilstevie> ogra_: on the transformer I do not have the same issue with size
[10:36] <ogra_> size ?
[10:36] <lilstevie> ogra_: my partition is 8MB flat, but can be extended if needed
[10:36] <ogra_> ah, then you have a more friendly bootloader :)
[10:36] <ogra_> the ac100 one can be changed as well
[10:36] <lilstevie> heh :)
[10:36] <ogra_> in fact NCommander did that for many models areound we installed
[10:37] <lilstevie> well I am compressing the initramfs LZMA to fit
[10:37] <ogra_> but its not really an enduser task to hack around in the bootloader
[10:37] <lilstevie> well resizing can be done with nvflash
[10:37] <ogra_> my size probelm is a problem with this specific kernel i think
[10:37] <lilstevie> ah
[10:38] <lilstevie> ogra_: you seen it running on the transformer yet?
[10:38] <ogra_> yep
[10:38] <ogra_> pretty slow though
[10:41] <lilstevie> yeah
[10:41] <lilstevie> need to start on some optimizations
[10:41] <lilstevie> fb is the biggest issue
[10:41] <lilstevie> up to 70% usage on one core at a time
[10:41] <lilstevie> at any one time*
[10:54] <ogra_> you could try the nvidia driver ;)
[10:54] <ogra_> https://launchpad.net/~ac100/+archive/ppa/
[10:54] <ogra_> should work on the transformer too
[10:55] <ogra_> GLES is still a problem though
[10:58] <lilstevie> I get a black screen
[10:58] <ogra_> with that driver ?
[10:58] <lilstevie> and I still have no wifi :)
[10:58] <lilstevie> the nvidia driver
[10:58] <ogra_> got an Xorg log ?
[10:58] <lilstevie> injected using their script
[10:59] <lilstevie> nothing on it
[10:59] <ogra_> no idea what their script does or if it hooks into the right places in the system
[11:01] <lilstevie> well it is done through an xorg.conf in /etc/X11
[11:01] <ogra_> ??
[11:01] <lilstevie> I still have everything in my fs, minus that config file
[11:01] <ogra_> you mean the script puts that in place
[11:01] <lilstevie> yeah
[11:01] <ogra_> right
[11:02] <ogra_> well, it needs to mangle the ldconfig configuration, and should set the right alternative for the driver
[11:02] <lilstevie> ah
[11:02] <lilstevie> I will try through the PPA then
[11:02] <ogra_> it should also put udev rules in place to get you the proper acls for the kernel devices the driver needs to access
[11:02] <lilstevie> still need to figure out this fing wifi though
[11:03] <ogra_> well, there are several broadcom drivers you should be able to try
[11:05] <lilstevie> I don't know if that will help
[11:08] <lilstevie> my driver is identical to the xoom one apart from like 6 lines (wakelock defs)
[11:09] <lilstevie> the xoom one works, mine doesnt
[11:13] <apw> ogra_, how is the new kernle
[11:14] <ogra_> apw, all fine, thanks :)
[11:15] <stm__> update-initramfs -c -k [2.6.37.6] update-initramfs: No match.
[11:15] <stm__> update -initramfs -c -k -v
[11:16] <stm__>  []2.6.37.6 ]
[11:16] <stm__> even that also gicing the same error
[11:16] <stm__> no match
[11:17] <stm__> i have moved config and system map files to boot
[11:23] <ogra_> why did you put the version in brackets ?
[11:28] <stm__> when i run update-initramfs -c -k
[11:29] <stm__> it showing me options
[11:29] <stm__> test06:/media/disk-3/etc# update-initramfs -c -k /usr/sbin/update-initramfs: option requires an argument -- k Usage: /usr/sbin/update-initramfs [OPTION]...  Options:  -k [version]   Specify kernel version or 'all'  -c             Create a new initramfs  -u             Update an existing initramfs  -d             Remove an existing initramfs  -t             Take over a custom initramfs with this one  -b             Set alternate bo
[11:30] <lilstevie> stm__: yeah replace [version] with the version not put it in the brackets :)
[11:30] <lilstevie> update-initramfs -c -k 2.6.37.6
[11:31] <stm__> thanks
[11:32] <stm__> is that the only change i have do
[11:32] <stm__> inorder to boot withe the new uImage
[11:37] <lilstevie> ogra_: do you have sound working on the AC100
[11:38] <ogra_> no
[11:38] <ogra_> not yet
[11:38] <ogra_> there is active work going on though
[11:38] <lilstevie> ok :)
[11:38] <ogra_> and i gave a device to one of the ubuntu alsa guys
[11:38] <ogra_> but he is on paternity leave for a few weeks now
[11:39] <lilstevie> ah
[11:40] <ogra_> others in #ac100 are hacking on it though
[11:41] <lilstevie> I can get aplay to show the device but not play anything
[11:42] <ogra_> same here
[11:42] <ogra_> what coded does the transformer use ?
[11:42] <ogra_> *codec
[11:42] <lilstevie> WM8903
[11:43] <ogra_> hmm, no idea about that one
[11:43] <ogra_> ac100 uses a relatek
[11:43] <ogra_> *realtek
[11:43] <lilstevie> ah
[11:44] <ogra_> alc53**
[11:44] <ogra_> or so
[12:20] <stm__> hi all
[12:24] <stm__> the modules for the new kernel have only drivers directory
[12:24] <stm__> when i run update initramfs
[12:24] <stm__> it giving me the error
[12:24] <ogra_> but you ran make mudules_install when you built your kernel ?
[12:24] <stm__> yes
[12:24] <stm__> i ran
[12:25] <stm__> it given me 2.6.37.6 directory
[12:25] <ogra_> so /lib/modules/$(uname -r)/ should have modules if you selected any in the config
[12:25] <stm__> in lib
[12:26] <stm__> i mean it giving me the error cound not find crzpto directory
[12:26] <stm__> crypto
[12:27] <ogra_> when you installed the crypto stuff should have been removed by the installer ... strange
[12:27] <ogra_> unless you selected "encrypt my home dir" on the user creation page
[12:28] <ogra_> you can manually uninstall cryptsetup though
[12:28] <ogra_> if your kernel has no support for it
[12:29] <stm__> what is the relation with crypt stuff and initrd image
[12:30] <ogra_> to unencrypt filesystems before they get mounted you need to get the password
[12:30] <ogra_> that happens in initrd
[12:31] <ogra_> for all filesystems that have to be in place before login
[12:31] <stm__> ok
[12:33] <stm__> iam sorry for these type questions . iam bit new to this .
[12:34] <stm__> then do i need to uninstall crzpto stuff
[12:34] <stm__> crypto stuff
[12:34] <stm__> to make update this initramfs
[12:52] <hrw> wm8xxx are nice supported in linux usually
[13:00] <hrw> lilstevie: broonie (Mark Brown) is maintainer of wm**** drivers
[13:24] <stm__> @ogra : do i need to change boot args
[13:24] <stm__> for the root device
[13:26] <ogra_> no, the installer should have set the UUID properly
[13:30] <c933103> Is it possible to install the prebuild arm Ubuntu rom on a random omap4 android phone without typing phone-specific commands?
[13:31] <LetoThe2nd> strange, yesterday someone in #pandaboard asked nearly the same and couldn't believe that pandaboard images were not at all meant for his funky motorola thing.
[13:43] <lilstevie> what are "phone-specific" commands
[13:43] <ogra_> whisteling the right tunes to imitate a keypad ?
[13:43] <lilstevie> heh
[13:44] <c933103> Mean you no need to modify command that you type according to the phone you have…
[13:45]  * LetoThe2nd guesses he refers to obscure rooting and flashing command from some homebrew-rom-installer board.
[13:45] <LetoThe2nd> c3would you mind giving an example, link?
[13:52] <c933103> .. can't think of an example ..
[14:02] <LetoThe2nd> then how did you get the idea it could be necessary?
[14:06] <c933103> As people prefer step by step instruction but to any things that need to test and correct themselves……
[14:09] <LetoThe2nd> *** statement parsing error: ENOTUNDERSTANDABLE - bailing out.
[14:11] <c933103> in another word people doesn't like thinking…
[14:52] <stm__> hi
[14:52] <stm__> it i mean the booting prcess giving me the same result
[14:53] <stm__> uncompressing linux done
[14:53] <stm__> booting the kernel
[15:29] <NCommander> ogra_: having the large partition is extremely nice, no cosntant out of disk spce warnings :-)
[15:30] <ogra_> i never have that :)
[15:30] <ogra_> but i also dont use much data on the local disk ... my payload lives externally
[15:35] <lag> ogra_: Where is the delta review page?
[15:35] <lag> ogra_: I don't see what delta I have
[15:35] <ogra_> lag, no idea, i didnt even know about that spec :)
[15:41] <lilstevie> I need to figure out how to layout my emmc :p
[15:41] <lilstevie> I crave the speed of moving internal
[15:42] <GrueMaster> emmc? Which platform?
[15:42] <ogra_> transformer i guess
[15:46] <lilstevie> that one :)
[15:46] <ogra_> not much different from ac100 in that regard
[15:47] <ogra_> more ram, bigger panel and different wlan
[15:47] <lilstevie> gpt on the ac100?
[15:47] <ogra_> ah, no
[15:47] <lilstevie> don't forget the different audio codec :p
[15:47] <ogra_> i thought it used a fastboot based installer too
[15:47] <ogra_> oh, yeah
[15:47] <ogra_> well, they are both tegra2 :P
[15:47] <lilstevie> heh
[15:48] <lilstevie> is yours harmony or ventana
[15:48] <ogra_> harmony based i think
[15:48]  * ogra_ isnt sure
[15:48] <lilstevie> ah ok, this one is ventana
[15:48] <ogra_> bah, so they are totally different devices that pretend to be the same :P
[15:48] <lilstevie> heh
[15:50] <stm__> i have included earlyprintk  /boot/boot.script  stiliam seeing nothing after uncompressing linux
[15:51] <stm__> but it booting fine if i replaces the uimage
[15:54] <lilstevie> ogra_: wifi is not looking good on this device
[15:55] <lilstevie> there is a userland binary which runs after module is loaded and firmware has been uploaded
[18:55] <stm__> hi all
[18:56] <stm__> i have problem while booting with the custom uImage
[18:56] <stm__> its giving me uncompressing linux
[18:57] <stm__> if i change root to /dev/mmcblk0p2
[18:57] <stm__> then the root device is notmounting
[18:58] <persia> Do you have a rootfs on a device that your kernel detects as /dev/mmcblk0p2 ?
[18:58] <stm__> i have ubuntu rootfs on device
[18:58] <stm__> i have bulded a custom uImage
[18:59] <stm__> it is booting good if i used the preinstalled images from ubuntu
[18:59] <stm__> if i change the uImage
[18:59] <persia> How did you construct the uImage?
[18:59] <stm__> then it just showing me uncompressing linux
[19:00] <stm__> i downloaded the kernel
[19:00] <stm__> then patched with adeos ipipe
[19:00] <stm__> and then compiled it
[19:02] <persia> Which kernel did you download?
[19:02] <stm__> 2.6.37.6
[19:02] <persia> From where?
[19:03] <stm__> git://git.xenomai.org/ipipe-gch.git
[19:04] <persia> Are you certain that this kernel includes all the patches from the Ubuntu kernel?  My suspicion is that your new kernel isn't representing your storage in the same manner.
[19:05] <stm__> ok
[19:05] <stm__> then how can i  boot this kernel with ubuntu
[19:06] <persia> Firstly, you'd need to understand how that kernel represents the storage area into which you have placed the rootfs, and pass the correct argument.
[19:06] <persia> Secondly, you'd need to be sure that kernel had the appropriate support for the Ubuntu booting procedures, etc.
[19:09] <stm__> Is there any link for the ubuntu booting procedures on pandaboard
[19:11] <persia> No, but there's nothing remarkably special about the pandaboard in this case.
[19:11] <persia> For the least-failure-prone path, I'd recommend starting with the Ubuntu omap4 kernel sources, and then trying to apply patches to that.
[19:12] <persia> If that result doesn't work, you can be fairly sure that this is due to the patch.
[19:12] <persia> Conversely, if you select an arbitrary kernel, the source of possible failures can be large.
[19:17] <stm__> yes but here the constraint is the ipipe support for pandaboard . They did not released it as a patch . thez released it as patched kernel
[19:19] <persia> You referenced a git tree: you ought to be able to use git to determine which patches have been applied which are not applied in the Ubuntu tree.
[19:24] <demarchi> ndec: i'm trying to get my new blaze board to boot ubuntu
[19:24] <demarchi> ndec: but it's not even showing uboot
[19:25] <demarchi> ndec: i'm trying to boot from SD
[19:31] <rsalveti> demarchi: you need a special x-loader and u-boot for blaze
[19:32] <rsalveti> demarchi: for Maverick https://wiki.ubuntu.com/ARM/OMAPMaverickInstall
[19:32] <rsalveti> then to support Natty I believe you can just use the same x-loader/u-boot combination
[19:33] <rsalveti> just need to check if the kernel supports blaze, and as I don't have one I never tested
[19:33] <rsalveti> GrueMaster: did you ever tested natty on a blaze?
[19:33] <rsalveti> demarchi: do you know which ES rev do you have at your blaze?
[19:34] <rsalveti> we only support >= ES2.x
[19:38] <demarchi> rsalveti: it's ES2.2 GP
[19:39] <demarchi> rsalveti: what's the difference between EMU and GP?
[19:40] <rsalveti> demarchi: hm, quite new actually
[19:40] <rsalveti> demarchi: not sure, maybe you can find it at http://www.omappedia.org/wiki/Blaze
[19:40] <rsalveti> or maybe robclark can help us :-)
[19:40] <rsalveti> otherwise ndec is your man
[19:42] <robclark> demarchi, an EMU is sort of half way between a HS and GP device..
[19:42] <robclark> HS has all the security and firewall stuff.. and is generally a pita to debug / use jtag, etc..
[19:42] <robclark> GP is wide open..
[19:43] <robclark> and EMU has all the security features but can be opened up.. basically intended for R&D..
[19:43] <robclark> (maybe I paraphrase a bit.. but that is the general idea)
[19:44] <demarchi> robclark: depending on my version, i need a different MLO, right?
[19:44] <robclark> yes.. or rather HS and (I think) EMU would need a signed bootloader
[19:45] <demarchi> robclark: i have a GP one
[19:45] <robclark> ok, then don't worry about EMU/HS stuff ;-)
[19:45] <demarchi> nice...
[19:45] <robclark> just use normal blaze/panda/whatever MLO.. depending on what board you are using
[19:46] <demarchi> maybe the problem was because i didn't rename the gp_MLO to MLO when copying to the sd card?
[19:46] <robclark> yeah.. that would be a problem
[19:55] <demarchi> robclark: it didn't work
[19:55] <demarchi> robclark: no output on console :-/
[19:56] <robclark> well..  what board, what bootloader?
[19:57] <robclark> fwiw, ubuntu itself isn't very chatty on the serial console.. but you should see *something* for the boot-loader..
[19:57] <demarchi> robclark: nothing... i don't see u-boot on this board
[19:58] <robclark> hmm.. I'm guessing the default ubuntu image has a panda boot-loader..
[19:59] <robclark> so I'm assuming you replaced that already w/ something for blaze?
[20:04] <demarchi> robclark: the guide for android has the uboot and mlo
[20:04] <demarchi> robclark: i tried those
[20:05] <robclark> where did those come from?  And are they actually for a GP device?
[20:05] <demarchi> robclark: that should work for ubuntu as well
[20:05] <robclark> I think most of the android folks are using either EMU or HS
[20:05] <demarchi> http://www.omappedia.org/wiki/Android:_Working_with_pre-built_binaries
[20:05] <demarchi> there's a gp_MLO there
[20:06] <demarchi> and looking at this thread, i think it should work: http://permalink.gmane.org/gmane.comp.hardware.microcontrollers.omap/69
[20:06] <robclark> hmm..
[20:07] <robclark> well, the non-gp MLO name seems to imply it is for an es2.1..  so it's possible you need something newer..
[20:10] <demarchi> robclark: humn.... true
[20:10] <robclark> well, MLO and u-boot are easy enough to build..
[20:10] <demarchi> robclark: i'll just try to compile a newer version
[20:10] <robclark> it might be easier to just clone the git trees and build your own..
[20:11] <robclark> I think if you take whatever versions are used in 11.04 and just build em w/ sdp4430 config (or whatever it is called..)
[20:32] <GrueMaster> rsalveti: I think I tested Blaze back with Natty Beta 1
[20:33] <persia> Does it need anything than a different u-boot?  Could support be added to our u-boot tree?
[20:34] <rsalveti> persia: needs support at the x-loader and u-boot
[20:34] <rsalveti> but TI didn't actually pushed the support upstream
[20:34] <rsalveti> they are maintaining it at their own tree at omapzoom
[20:35] <GrueMaster> iirc, the mlo/u-boot for blaze from Maverick worked with natty as well.
[20:35] <GrueMaster> Kernel is good.
[20:35] <rsalveti> just need to test if it works with es2.2
[20:35] <GrueMaster> If I get time, I'll check it out, but it is currently low priority for me.
[20:35] <persia> rsalveti, Ah.  Is there something deeply incompatible, or is it just a matter of not having gotten around to it yet?
[20:35] <GrueMaster> I only have a 2.0
[20:36] <rsalveti> persia: lack of hardware for the upstream maintainers and missing someone to actually push the patches upstream
[20:36] <rsalveti> so we can only wait TI to do it :-)
[20:37] <persia> Well, or someone with compatible hardware and sufficient motivation, but yeah, that's most likely TI.
[20:37] <rsalveti> with pandas around, don't know why someone would use a blaze
[20:37] <rsalveti> I mean, from community
[20:38] <persia> It has a nice plastic box, and nice screens, and bamboos are hard to find?
[20:38] <robclark> persia, usually bootloader needs to be updated for a new ES..  if nothing else, to add a new Si revision id.. but usually there are different settings for voltage rails, different memory settings, etc, etc..
[20:38] <persia> There's lots of us that don't like dev boards as a form factor.
[20:38] <rsalveti> persia: it's expensive, hard to get and so on :-)
[20:38] <persia> robclark, Right.  I thought that was just compile-time choices.
[20:38] <robclark> so it is safe to assume that bootloader needs to be rev'd whenever there is a new ES
[20:38] <robclark> no, it is even runtime..
[20:38] <persia> Both x-loader and u-boot?
[20:39] <robclark> but a bootloader built before es2.2 would probably not have es2.2 support ;-)
[20:39] <robclark> because the patches didn't exist at the time
[20:39] <rsalveti> unless the default options match es2.2
[20:39] <GrueMaster> And at $369 for the upgrade, someone else can buy me an upgrade for testing.
[20:39] <rsalveti> but only with some luck :-)
[20:40] <persia> robclark, Right.  non-existence is the best reason for lack of support.  I guess I'm wondering about continuous integration: is it just the lack of available hardware that makes it hard to upstream this stuff?
[20:41] <robclark> not sure.. is there some patches missing (for an existing piece of Si) in upstream tree?
[20:41] <robclark> for xloader, it used to be a problem not having an upstream tree.. but now one exists..
[20:41] <rsalveti> question is, why TI is still not pushing newer modifications upstream
[20:41] <rsalveti> yeah, even for x-loader
[20:42] <robclark> oh..  I didn't realize..
[20:42] <rsalveti> the upstream tree is there, but TI is still pushing newer modifications only at omapzoom
[20:42] <robclark> I thought recent activity was mainly around 4460..
[20:42] <robclark> which isn't really available in the wild..
[20:43] <rsalveti> http://git.omapzoom.org/?p=repo/x-loader.git;a=shortlog;h=refs/heads/omap4_dev
[20:43] <rsalveti> 4460 and es2.3
[20:43] <rsalveti> but at least es2.3 support would be good to have at the upstream x-loader already
[20:44] <rsalveti> and I believe we'll be seeing pandas with 4460 really soon
[20:44] <persia> And it rarely hurts to have some stuff in advance, even before GA, as there's often not budget to get it upstream once it is GA.
[20:44] <robclark> I suppose on the 2.3 stuff.. although I didn't even know there were es2.3 pandas..
[20:44] <robclark> there are already 4460 pandas.. but I think mainly (or possibly only) within TI..
[21:08] <demarchi> rsalveti: blaze has 2 frontal 5MP cameras and 1 in back of 12MP
[21:09] <demarchi> rsalveti: depending on what you are doing, it might answer your question
[21:11] <GrueMaster> demarchi: Must depend on the blaze you have.  Mine is missing all the cameras.
[21:12] <robclark> the camera sensors are swappable, fwiw..
[21:12] <robclark> probably if you didn't need the sensors, they sent you one with empty sockets ;-)
[21:12] <GrueMaster> Mine was a very early model.  ES1.
[21:13] <GrueMaster> I have the ES2 upgrade, but it is 2.0.