[00:42] <vlad> if I have an arm box with the netbook-remix packages installed, is it possible to get -dev packages on there?  Like if I try to install libglib2.0-dev, it complains that the 0netbook2 etc. rel of glib is installed, and that the dev package is coming from normal jaunty and requires the standard non-netbook rev
[00:52] <lool> vlad: Where is this netbook-remix image from?
[00:52] <lool> vlad: It's a preinstalled one from Dell?
[00:52] <lool> vlad: You basically need to use the repos which came in the sources.list of the preinstalled image; you cant mix them with the Ubuntu one
[00:53] <lool> vlad: Hold on, you said an ARM box and we're on #ubuntu-arm  :-)
[00:53] <lool> vlad: Is this a pegatron box?
[00:54] <vlad> yeah
[00:54] <lool> vlad: Ok so this build was a bit special and I'm not sure the sources.list point at the correct archive
[00:55] <vlad> it just points to the normal jaunty ports repo
[00:55] <lool> Nothing more in /etc/apt/sources.list.d/*.list?
[00:55] <vlad> mm, I only looked in sources.list, not in .d/*
[00:56] <vlad> sec
[00:59] <vlad> oh wait, there is
[00:59] <vlad> deb http://netbook-remix.archive.canonical.com/updates jaunty-watertown public ?
[00:59] <lool> That sounds like the right thing yes
[01:00] <lool> vlad: Can you easily paste apt-cache policy libglib2.0-dev?  you might want to apt-get update first
[01:00] <vlad> though just updates -- is there another repo that'll have the full set of packages, with dev packages and stuff?
[01:01] <lool> vlad: In theory, unless things are borken, your install should be pointing at the repos which were used to create it
[01:02] <lool> vlad: jaunty was used as a base with an overlay repo for the packages modified for this build
[01:02] <vlad> hrm
[01:02] <lool> That's in theory because I didn't actually see that rootfs and cant easily check its contents
[01:02] <vlad> I wonder if the entries in sources.list arescrewing it up
[01:02] <vlad> one sedc
[01:05] <lool> vlad: It's about 2am for me so I'll drop off; a bunch of people are familiar with imx51 hardware here, and some played with the one you have; I only touched early hardware and have no idea about the final software image shipped by Canonical OEM, but I'm happy to answer questions you leave here
[01:07] <vlad> ok cool; thanks! I'll poke at it some more
[01:09] <lool> vlad: Perhaps a less bumpy ride to start development is to create a jaunty or a karmic chroot and work in it; this requires in the 300 MB + whatever you add there (e.g. build-deps of your software)
[01:09] <vlad> yeah, or just do it via scratchbox :)
[01:10] <lool> vlad: debootstrap is the regular tool to do this; "sudo debootstrap jaunty my-chroot"
[01:10] <lool> Oh sure; but since you have a native system... up to you
[01:22]  * Martyn has karmic running on his development system :
[01:22] <Martyn> woot!
[01:22] <Martyn> although I had to do a buildroot :(
[10:34] <siji> ogra,u there
[10:47] <siji> while am trying to start the uimage frm MMC
[10:48] <siji> Unknown command 'mmcinit' - try 'help'
[10:48] <siji> getting this msg frm uboot terminal
[10:48] <siji> why it's happening
[10:48] <siji> ?
[10:50] <tasslehoff> siji: maybe you have the version where it is called "mmc init" instead? I believe it changed at some point
[10:51] <tasslehoff> siji: if so, change your bootcmd to use the new command
[10:51] <siji> mmc init is also not there
, even lot of other commands also missing in by uboot
[10:57] <tasslehoff> siji: hm. I only got started with beagle yesterday, so I'm afraid I'm not of much help. Experienced the mmcinit -> mmc init, though.
[10:57] <siji> ok
,actually am not with beagle now.My beagle is wrking fine
[10:58] <siji> am using compulab's X300 evaluation kit
[10:58] <siji> which is based on marvel's PXA300 processor
[10:59] <tasslehoff> siji: ok
[10:59] <siji> is it cose of some old version of uboot or smthing?
[11:01] <siji> Am surprised, even erase command is also not there
[11:01] <siji> :(
[11:03] <gaspa> siji: check really uboot version, it tends to change often command name. So current online documentation may not work for you.
[11:03] <gaspa> s/name/names
[11:04] <siji> oh ok
[11:05] <gaspa> siji: e.g. I've "nand erase" instead of "erase"...
[11:06] <siji> gaspa, while help output giving only limited command set
[11:08] <siji> it doenst contain any such commands
[11:08] <siji> doesnt
[11:09] <gaspa> version?
[11:10] <siji> how to get the version
[11:10] <siji> ?
[11:10] <gaspa> 'version' ?
[11:11] <siji> ok
[11:11] <siji> U-Boot 2009.03-cm-x300-2 (May 26 2009 - 11:47:40)
[11:11] <gaspa> or at early boot time ... I'm seeing this:
[11:11] <gaspa> U-Boot 1.2.0 (Mar 21 2009 - 05:12:20)
[11:12] <siji> ya
[11:12] <gaspa> is that uboot shipped with your card?
[11:12] <siji> ya
[11:13] <siji> gaspa, so this may be customised version of uboot right?
[11:13] <gaspa> surely
[11:13] <siji> ok, thne how will flash it
[11:13] <gaspa> in fact, perhaps it's worth asking in some list/channel about your board.
[11:13] <siji> gaspa,ok
[11:14] <siji> but how will i add new uboot now
[11:14] <siji> there is no erase command
[11:15] <gaspa> jtag? it depends from the board.
[11:17] <siji> gaspa, am not clear
[11:33] <mike^> siji, there's no MMC on CM-X300 :)
[11:34] <siji> mike^,mmc connector is there
[11:34] <siji> in base board
[11:35] <mike^> siji, yes, but there's no mmc support in U-Boot
[11:35] <siji> ok
[11:35] <siji> :(
[11:36] <mike^> siji, you can use USB instead
[11:36] <siji> yes that i did
[11:36] <siji> it's wrking fine
[11:36] <mike^> siji, good to know :)
[11:36] <siji> am booting ubuntu with lxde
[11:36] <mike^> and it works?
[11:37]  * mike^ surprised
[11:37] <siji> yes
[11:38] <mike^> siji, it also should be possible to use mmc for rootfs, as long as you have the kernel on USB or in NAND
[11:39] <siji> mike^, was trying for that only
[11:40] <siji> u mean kernel wil start frm nand and wil search the rootfs frm mmc
[11:40] <siji> right?
[11:40] <siji> but that also failed
[11:40] <siji> hey mike^, thanks
[11:41] <siji> let me give a try again
[11:41] <siji> I compiled the kernel with mmc support (earlier it was as LKM)
[11:41] <siji> but i think forget to put the new kernel image in to nand memory
[11:41] <siji> :)
[11:43] <mike^> siji, use tftp, it's far more efficient. In U-Boot you can set
[11:43] <siji> mike^,ok
[11:43] <mike^> setenv bootcmd 'dhcp; setenv serverip <your tftp server>; tftp 80800000 uImage; bootm'
[11:44] <siji> ok
[11:44] <mike^> and to the kernel build you can append 'cp arch/arm/boot/uImage /path/to/tftproot'
[11:44] <siji> ok
[11:44] <mike^> siji, btw where are from?
[11:44] <siji> India Mumbai
[11:44] <siji> n u?
[11:44] <mike^> compulab.co.il, Haifa, Israel :)
[11:45] <siji> oh grt
[11:45] <siji> oh the same mike who's answering my queries
[11:45] <siji> in compulab support chanel
[11:46] <mike^> siji, yep :)
[11:48] <siji> cool
[11:48] <siji> nice to meet you
[11:49] <mike^> siji, you've got one more answer :)
[11:49] <mike^> no mmc in U-Boot :)
[11:49] <siji> yes right
[11:49] <siji> we are using the evaluation kit now
[14:44] <armin76> NCommander: i want a marvell dove!
[14:45] <NCommander> armin76, O:-)
[14:50]  * armin76 pokes rabeeh 
[16:26] <lool> win 1
[16:26] <lool> Tss
[21:11] <MarkG> Anyone know why armv5 is being dropped in the next Ubuntu release?  That seems pretty big news considering V5 ihas huge number of devices.
[21:11] <vlad> very few of those devices are all that interesting for running a desktop OS, though
[21:12] <MarkG> Is ubuntu Desktop only now then?
[21:13] <MarkG> What does this mean in real terms for someone with a brand-new Sheevaplug?  I find it incrddible that Ubuntu is stopping supporting new hardware.
[21:25] <MarkG> OK, I can assume then that it's game over...
[21:25] <MarkG> can someone recommend another distro that has a good a package manager as ubuntu thats not dropping armv5 support?
[21:26] <kblin> MarkG: seriously? weren't they boasting about the sheeva support?
[21:27] <kblin> MarkG: I guess you could always switch to debian
[21:27] <kblin> that's certainly my plan if ubuntu drops support for my sheeva
[21:31] <MarkG> I think they are keeping quiet about it deliberately.
[21:31] <MarkG> if not too many people know, then what it occurs, it's too late.
[21:33] <MarkG> I suppose it's a halfway house.  There is no money in embedded ARM devices, Canonical want the high-end server market, where there is money, and also want the desktop bit too, but anything outside that, they don't care about.
[21:34] <kblin> there's no money in embedded devices?
[21:34] <kblin> who said that?
[21:34] <kblin> I've got a couple of rooms full of engineers here who would disagree
[21:35] <MarkG> you pay money to Canonical?
[21:35] <kblin> no, but there's certainly lots of people making money on embedded devices
[21:36] <kblin> I've had a couple of people being very interested in the embedded active directory server I've been demoing
[21:37] <MarkG> isn't that the point, there is money in embedded stuff, but if Canonical don't make any of it, and it's a market that Microsoft's not in, then why bother?
[21:37] <kblin> I don't see why you would get less support for an embedded server that's mission critical
[21:39] <kblin> bus as I said, if ubuntu drops support, just switch to debian
[21:39] <kblin> you don't even have to get used to a new package manager then
[21:46] <lool> MarkG: The Ubuntu armel port is mostly aimed at netbook/desktop uses
[21:47] <lool> MarkG: Also, we look forward at the future devices and would like to benefit of every performance bits we can
[21:47] <MarkG> OK, so debian is not dropping support, is that correct?
[21:47] <lool> MarkG: Indeed, Debian has support for armv4t
[21:47] <MarkG> that's OK, i'll switch to that
[21:47] <lool> MarkG: We target armv6+vfp for now
[21:47] <lool> MarkG: Sure
[21:47] <lool> MarkG: I have a sheevaplug BTW   ;)
[21:47] <lool> you can run jaunty on it if you like
[21:48] <MarkG> I'd hate to have to go back to the horrendous emerge of Gentoo
[21:48] <lool> I think Debian is great for sheevaplug
[21:48] <MarkG> I have Jaunty on it, but wonder how long things will continue to be supported
[21:48] <lool> I hope we'll see am armv7 plug soon
[21:48] <MarkG> I hope not, I only just got mine :-)
[21:49] <lool> MarkG: AFAIK, ubuntu desktop is supported for 18 months even on armel
[21:49] <lool> https://wiki.ubuntu.com/KarmicKoala/ReleaseManifest
[21:49] <lool> not 100% sure for jaunty though
[21:50] <lool> MarkG: I wish some people would maintain an armv5 rebuild of Ubuntu though; that'd be cool
[21:52] <kblin> lool: sure, it should build on a sheeva within a couple of weeks, I guess :)
[21:52] <kblin> how big is the current repository?
[21:53] <lool> You mean in terms of size?
[21:53] <lool> I dont know for sure and dont have a mirror to check
[21:54] <kblin> lool: so karmic is armv6?
[21:55] <lool> Yes
[21:55] <lool> +vfp
[21:55] <kblin> and still doesn't support the beagle
[21:55]  * kblin sighs
[21:55] <lool> Eh
[21:55] <lool> It's a lot of work to support it; if people are interested in doing the maintenance they're welcome to step up
[21:56]  * kblin shrugs
[21:56] <lool> there's no support in Debian either for similar reasons
[21:56] <kblin> people keep filing samba bugs, if someone will step up to fix them, I might have some time
[21:56] <kblin> :)
[21:56] <lool> Tss :)
[21:57] <kblin> but assuming the TI folks get the linux-omap stuff upstream, there shouldn't be too much of a maintenance issue anymore, right?
[21:58] <lool> My time is 100% busy with the commitments I have so far; it's 11pm, I stayed up til 2 am yesterday fixing armel image issues so I dont have the bandwidth myself; I think for now beagle would have to be a community port
[21:58] <lool> kblin: Absolutely
[21:58] <lool> kblin: at least that has been the blocker on the debian side of things
[21:58] <lool> I dont know whether canonical would support a beagle flavour of the main kernel but it would be doable in the ports kernel for sure
[22:01] <kblin> I'm beginning to think that for the stuff I'm doing, maybe a small atom board would be less painful.. oh well :)
[22:01] <lool> Beagle is a nice device and I can tell that the bulk of the work to get it running is the kernel part
[22:01] <lool> It works fine with a karmic userspace
[22:05] <kblin> well, yes, mostly fine
[22:05] <kblin> but to be honest I didn't try karmic on it yet