**** BEGIN LOGGING AT Sat Feb 19 02:59:57 2011 Feb 19 12:30:53 hi. which qemu gives best results for beagleboard ubuntu-arm? Feb 19 12:31:11 the one in natty Feb 19 12:32:00 ok, looking... Feb 19 12:32:35 would that be qemu-system-arm? Feb 19 12:34:25 ogra, is it in qemu-kvm-extras. Feb 19 12:37:09 that should be a transitional package, but yes, it should get you the right bits Feb 19 12:38:06 any change i will get it to work by rebuild of source package from natty under maverick? Feb 19 12:38:55 if you rebuild the right one, you want the qemu-linaro source package, it uses omap by default for all VMs in natty Feb 19 12:39:52 ah, qemu-kvm_0.14.0~rc1+noroms-0ubuntu3.dsc no good? Feb 19 12:40:12 no, look for qemu-linaro Feb 19 12:40:32 found it Feb 19 12:41:11 shall i configure and compile from trunk/2011.02 instead? Feb 19 12:41:36 i think thats the same as what is in natty atm Feb 19 12:41:53 https://launchpad.net/ubuntu/natty/+source/qemu-linaro says newer version avail Feb 19 12:43:51 do you know quick tip to install builddeps, i can take package names from dsc, but there might be a better way. Feb 19 12:44:00 "for packaging" Feb 19 12:44:23 just sudo apt-get build-dep qemu-kvm should suffice Feb 19 12:44:34 ok Feb 19 12:44:35 i doubt they changed much between natty and maverick Feb 19 12:44:40 indeed Feb 19 12:46:33 LOL: E: Unable to find a source package for should Feb 19 13:02:10 is bootloader for beagle included in qemu-linaro? Feb 19 13:08:16 is ../ubuntu-10.04-netbook-armel+omap.img an SD card image? Feb 19 13:17:55 sim_, yes, its supposed to be dd'ed to an sd and contains two partitions, the rootfs partition gets expanded to the full size of the SD on first boot Feb 19 13:19:17 im puzzling on the qemu-system-arm cmdline. Feb 19 13:19:57 does it load the kernel from the SD, or do i need to spec it on the cmdline? Feb 19 13:22:26 i think you need to spec it on cmdline Feb 19 13:23:01 but tbh i havent tried the linaro packages yet, there might be a way to just use u-boot from the image Feb 19 13:24:04 u-boot resides in flash i guess, so i should build a flash image first and present to qemu on cmdline? Feb 19 13:24:34 -mtdblock i think? Feb 19 13:25:24 u-boot resides on the first partition of the SD card image Feb 19 13:25:38 none of the boards we currently build for have flash Feb 19 13:26:06 (while you can use a beagle C4 with the images its not really recomended and the XM which we test on has no flash) Feb 19 13:39:51 ogra, its a casper image Feb 19 13:40:11 ?? Feb 19 13:40:34 i unpacked ubuntu-10.04-netbook-armel+omap.img and it looks like a bootcd Feb 19 13:40:39 yes Feb 19 13:40:44 ah, its a live image. Feb 19 13:40:48 no Feb 19 13:41:05 its a preinstalled image that expands itself to the full size of the card on first boot Feb 19 13:41:19 ok Feb 19 13:41:24 nothing "live" in there Feb 19 13:41:48 do you know the qemu cmdline i should use to boot it? Feb 19 13:42:02 no, sorry, check the linaro documentation Feb 19 13:42:10 they likely have info on their wiki Feb 19 13:42:32 ok thanks. Feb 19 13:59:59 ogra, is there nand emulation in qemu? Feb 19 14:00:58 no idea, might be for some ancient machines Feb 19 14:01:38 beagleboard has NAND Feb 19 15:01:34 hi Feb 19 15:01:55 i have a beagleboard C4 which i'd like to use for some tinkering around Feb 19 15:02:20 it appears to be configured so that it 'autoboots' after some timeout if i don't press a key Feb 19 15:02:44 using minicom i can't seem to send a keypress such that it cancels the autoboot Feb 19 15:02:55 so it's kind of useless fo me at the moment Feb 19 15:03:15 is there anything unusual i need to do to send keypresses over serial? Feb 19 15:03:25 input is coming over just fine it seems Feb 19 15:04:17 brendand_, is this a fresh install that you did, or did someone else set it up for you? Feb 19 15:04:41 well, i'd say i got it from someone else, but that would be lying Feb 19 15:04:56 i actually used to do some stuff on it with Windows Feb 19 15:05:17 and hyperterminal worked fine for sending keystrokes Feb 19 15:05:18 okay, well the 'autoboot's' is not normal.. so either some configured it do that.. or... ;) Feb 19 15:05:22 i did Feb 19 15:05:23 :P Feb 19 15:05:40 yes - i got myself in this situation... Feb 19 15:05:43 embarrasing Feb 19 15:05:47 so undo it? Feb 19 15:06:14 if you don't remember what you did, just reinstall it a base os and start again.. Feb 19 15:06:20 that would be one way. wouldn't i still need to be able to send keystrokes to do anything with u-boot? Feb 19 15:06:56 ah.. u-boot's autoboot.. Feb 19 15:07:08 so you don't want it to autoboot, but stay in u-boot? Feb 19 15:07:08 yeees Feb 19 15:07:16 well. i think i do Feb 19 15:07:33 certainly i'd like to be able to interact with u-boot in some way Feb 19 15:09:13 well... in u-boot, type printenv... you'll see the whole enviroment scripts including the autoboot stuff.. Feb 19 15:09:46 but your on your own..i just use u-boot as a bootloader, nothing else.. Feb 19 15:10:14 http://pastebin.com/GHZayL8m Feb 19 15:10:32 at line 13 i'm just hammering keys and it counts down from 3 Feb 19 15:10:50 ah Feb 19 15:10:50 thru the serial terminal? Feb 19 15:10:54 yeah Feb 19 15:11:33 has it worked before? Feb 19 15:11:42 in windows Feb 19 15:12:00 ah.. dump minicom... use gtkterm.. Feb 19 15:12:45 will do Feb 19 15:13:01 have also tried putty and screen, with no success. let's see how this works Feb 19 16:36:43 ogra, there? anyone else who knows how linux-fsl-imx51 worked and why there is a seperate debian.fsl-imx51 directory? Feb 19 17:01:03 Neko, no idea and imx51 is removed from the archive since quite some time, fo rthe subdir talk to the kernel team during workhours, if you want to use imx51 today, use the linaro kernel Feb 19 17:10:51 (though the linaro flavour is called differently) Feb 19 20:47:15 ogra, it's for our kernel... Feb 19 20:47:43 because we use make-kpkg we have no .dsc and therefore don't get any virtual packages for linux-image-efikamx for now Feb 19 20:48:54 I don't care about fsl-imx51 but I do care that it is the only reference for this arch in ubuntu that has a debian directory that "works" for us.. seems the scripts were updated for 2.6.35+ and they don't build .31 kernels anymore. we're not spending the time to port to .35 just to fix a package error :D Feb 19 20:49:04 (there are other reasons pressuring that but not packaging :) **** ENDING LOGGING AT Sun Feb 20 02:59:57 2011