**** BEGIN LOGGING AT Thu Dec 09 02:59:57 2010
Dec 09 09:29:21 <hrw> hi
Dec 09 09:29:45 <hrw> do we have kernel for pandaboard which will work with 1G ram finally?
Dec 09 09:31:14 <rsalveti> maybe cooloney knows better
Dec 09 09:31:37 <cooloney> hrw: yeah,
Dec 09 09:31:53 <hrw> cooloney: is it available in natty?
Dec 09 09:31:58 <cooloney> i think maverick kernel works with mem=1G, but we use 2:2 split
Dec 09 09:32:12 <hrw> cooloney: which maverick kernel?
Dec 09 09:32:40 <rsalveti> for me it never worked well with high cpu loades
Dec 09 09:32:40 <cooloney> hrw: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4
Dec 09 09:32:40 <rsalveti> always giving weird crashes
Dec 09 09:32:47 <cooloney> that's maverick
Dec 09 09:32:54 <rsalveti> but that might be fixed already at the lates ti kernel
Dec 09 09:32:57 <hrw> btw - definition of stable kernel: "apt-get source somethingbig -b"
Dec 09 09:32:59 <cooloney> hrw: if you wanna try natty, please try linaro natty kernel
Dec 09 09:33:07 <rsalveti> cooloney: are you able already to boot upstream on panda?
Dec 09 09:33:11 <cooloney> http://git.linaro.org/gitweb?p=ubuntu/linux-linaro-natty.git;a=summary
Dec 09 09:33:15 <hrw> cooloney: I use natty and maverick-14 kernel
Dec 09 09:34:01 <cooloney> rsalveti: i can boot up the upstream kernel. but it is panic when it try to use our ubuntu mininal root filesystem
Dec 09 09:34:09 <cooloney> rsalveti: but you can try linaro natty kernel
Dec 09 09:34:20 <cooloney> which is .37 based and very close to mainline
Dec 09 09:34:35 <cooloney> with our ubuntu sauce and config.
Dec 09 09:34:45 <cooloney> so it boots fine with on my panda
Dec 09 09:34:53 <rsalveti> that's nice
Dec 09 09:35:24 <cooloney> rsalveti: so in mainline highmem is disabled defaultly
Dec 09 09:35:47 <cooloney> rsalveti: i can still see such instability with linaro natty kernel
Dec 09 09:35:55 <rsalveti> hm
Dec 09 09:36:14 <cooloney> rsalveti: but if you have time, you can try that on your board
Dec 09 09:36:46 <hrw> otyher thing: usb. 13MB/s is max?
Dec 09 09:37:08 <rsalveti> cooloney: sure, will try it later
Dec 09 09:38:32 <tmzt> does that linaro support omap3/beagle?
Dec 09 09:38:36 <tmzt> kernel
Dec 09 09:42:20 <cooloney> tmzt: sure
Dec 09 09:42:52 <tmzt> cooloney: we are trying to port to the new nook color, which is an omap3+slcd on the lvds, and very similar to beagle
Dec 09 09:42:59 <cooloney> tmzt: so one linaro kernel can boots up on omap3/beagle and omap4/panda with the same natty file system
Dec 09 09:43:34 <tmzt> and we have the source from bn to port the board
Dec 09 09:44:25 <cooloney> tmzt: that's good start point. mainline supports beagle very well
Dec 09 09:44:32 <cooloney> but limited to panda
Dec 09 09:44:49 <cooloney> we still miss some driver or feature of omap4 in mainline
Dec 09 09:44:53 <hrw> nothing strange - omap4 is still young
Dec 09 09:45:01 <tmzt> this is omap3 though
Dec 09 09:45:16 <tmzt> looking for the best support (tony kernel?) for that
Dec 09 09:52:07 <cooloney> tmzt: i think mainline is good for omap3
Dec 09 09:52:23 <tmzt> okay
Dec 09 11:06:22 <janimo1> I am trying to run 10.10 omap3 image under qemu but it hangs timeing out on mtd
Dec 09 11:06:25 <janimo1> qemu-maemo-system-arm -M beagle -m 256 -sd ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img -serial stdio
Dec 09 11:06:56 <janimo1> how can I create a valid beagleboard mtd file to see if that is the prob?
Dec 09 11:07:44 <tmzt> mtd file?
Dec 09 11:13:33 <janimo1> tmzt: something to stand for the expected mtdbloc device in the guest
Dec 09 11:13:41 <janimo1> there
Dec 09 11:13:48 <janimo1> is a sdcard image
Dec 09 11:13:57 <janimo1> and I understand there's a NAND image as well
Dec 09 11:14:04 <tmzt> I guess mtd image has to have an ftl
Dec 09 11:14:30 <tmzt> how's the tegrabook going?
Dec 09 14:34:46 <davidm> ndec1, call time?
Dec 09 15:01:21 <GrueMaster> To all that were planning on attending the Mobile/Arm team meeting today at 15:00 UTC; the meeting has been canceled do to key players' otehr commitments and holiday schedules.  Thank you.
Dec 09 16:37:56 <dmart> asac: yes
Dec 09 20:41:18 <GrueMaster> Hmm.  It would appear that one of the recent changes to Natty since A1 has clobbered X on panda.
Dec 09 20:50:11 <rsalveti> GrueMaster: with which image?
Dec 09 22:00:22 <GrueMaster> No new image.  Just using A1 and running apt-get udgrade.
Dec 09 22:01:25 <rsalveti> ok
Dec 09 22:03:56 <GrueMaster> I'm looking into it now.  Had to check my other board I had sent to Lexington to make sure it survived.  Also had to run a vehicle to the shop (another transmission) and get a bag of fresh ground coffee.
Dec 09 22:04:14 <GrueMaster> Busy morning.
Dec 09 22:09:58 <rsalveti> :-)
Dec 09 23:30:40 <GrueMaster> rsalveti: I stand corrected.  I had used the latest image, 20101206, and updated from there.  Am now running clean image to see what update clobbered X.
Dec 09 23:31:00 <rsalveti> ok
Dec 09 23:31:51 <GrueMaster> Hrm.  Networking fails when the cord isn't plugged in.  (oops).
**** ENDING LOGGING AT Fri Dec 10 02:59:57 2010