[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sd image creator: armstrap anyone?



On Sat, Jun 01, 2013 at 02:40:15AM +0100, Wookey wrote:
> +++ Leonardo Canducci [2013-05-31 18:10 +0200]:
> > I'm playing with my new Cubieboard. I discovered armstrap[1] on IRC
> > and it seems pretty cool. Anybody tried it? What do you think?
> > 
> > [1] https://github.com/EddyBeaupre/armStrap
> 
> I'm sure it's useful for cubieboards, and it does seem sensibly put
> together, but the idea that it is 'universal' is pretty optimisitic.
> It covers the case where you want to cross-build a local kernel source
> tree and combine that into a debootstrapped debian rootfs, for an
> architecture that has qemu support, and where the image ends up on an
> SD card.
> 
> Now that covers a fair number of boards and it seems to have been
> written with generality in mind, but it's no use at all for most of
> the boards I have to hand (nand, not SD, or targetting arm64 (no
> qemu)). The more boards you try to make it work on, the more the
> assumptions will become noticeable and the more options it will have
> to grow. 
> 
> There is something 'special' about every board IME. That's why
> multistrap just provides 'config-script' and 'setup-script' functions
> to do whatever jiggery-pokery is needed (and that mechanism can work
> without qemu). There is a lot of commonality in the sorts of
> jiggery-pokery needed for many devices of course.  
> 
> There have been 101 scripts like this written. I think live-build
> already does pretty-much all that this script does (except probably
> building a local kernel source). Polystrap/multistrap also does this.

Which do you recommend then for "board bringup" with Debian? Is one of
these tools (Polystrap, livebuild, multistrap) worth investing time in
more than another so that one can re-use the tool and one's experienc
when a new board comes along?

I rarely have problems getting a board to run, I usually stuff an
Ubuntu kernel and then use debbootstrap, but if there was a way to add
a Debian kernel I'd be on that in a New York minute. Right now
cross-compilation is painful be it in a chroot or with Yocto, so if I
could stay in an all Debian environment I'd be much more comfortable.

Regards,

Jeremiah
 
> Enhancing those generic tools with cubie config and a kernel-build
> option might have been smarter than making yet another framework. 
> There are already at least 16 tools I know of for making rootfs images
> of one sort or another in debian. 

+1
 
> 
> Wookey
> -- 
> Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
> http://wookware.org/


Reply to: