[05:27] infinity, do you think the drivers should be purged even from git history or a regular removal commit should be ok? Is having them in .git considered redistribution? === doko_ is now known as doko === _Lucretia__ is now known as _Lucretia_ === Quintasan_ is now known as Quintasan [15:55] root@ubuntu:~# du -hcs / [15:55] 7.0M / [15:55] yay [15:56] * ogra_ fiddles with his embedded rootfs builder === ubuntu is now known as Guest9216 [15:59] what's that on, ogra_? [15:59] vm [16:00] the target is that the tool will build you a tarball with an embedded fs [16:00] no matterr what you run it on, it should work [16:01] and the core rootfs shouldnt be larger than 10M (with upstart. udev etc) [16:03] the system will be truely embedded thoguh, no package manager or anything [16:06] I am using ubuntu-desktop on beagleboard-xm, is there any SDK that works on it? [16:22] what package do I need to install to my ubuntu (laptop) for the toolchain of beagleboard-xm (ubuntu-arm)? is it gcc-arm-linux-gnueabi ? [16:23] well, rather gnueabihf [16:23] (unless you actually want to produce armel stuff which is rather dead) [16:24] I want to compile my C code on beagleboard-xm by using eclipse or Qt-creator [16:25] I am looking for the tool chain for it, do you suggest me to install gcc-arm-linux-gnueabihf ? [16:26] uname -a outputs "Linux beagleubuntu 3.2.0-26-omap #41-Ubuntu Thu Jun 14 18:19:55 UTC 2012 armv7l armv7l armv7l GNU/Linux" on the beagleboard [16:28] well, for compiling a kernel or so the gcc package should be enough ... [16:29] as soon as you start doing things that need dependencies a chroot is way better [16:31] are gcc on my laptop (ubuntu-12.04) and gcc on beagleboard-xm(ubuntu-desktop) the same? [16:31] if your release is the same on both [16:32] the gcc for all arches in ubuntu is built from the same source package so your x86 one as well as the cross one as well as the native one on the beagle itself are identical within one release [16:33] now I see. thank you ogra_ [16:35] 90% of the software you write you can just develop on x86 ... unless its highly HW specific probably ... and then just rebuild it for your target arch if you are done [16:36] the same as for gcc above is usually also true for libs etc so you have the same APIs on both arches [16:37] thanks a lot [17:10] janimo: If there's a sane way to rebase them out of existence in the git history, that would be better. [17:10] janimo: One of the drivers isn't even something that Marvell *can* give you permission to redistribute, since the copyright belongs to one of their partners, not them. === mo is now known as Guest54736 === Guest54736 is now known as mogh [22:25] Hi, i want to get ubuntu running on my Gooseberry board [22:25] but all i can find is that i should extract an image onto my microSD card, but i can't seem to find any images anywhere.. [22:26] Are there any tutorials or other resources on how to go about this?