Re: How to change the kernel command line for the NSLU2

[Steve Gane <steve@theganes.co.uk>]

Gordon Farquharson wrote:
> On 5/9/07, Xan <DXpublica@telefonica.net> wrote:
> > En/na Rod Whitby ha escrit:
> > > Slugimage *always* pads with 0xffs.  It's a script in debian-installer
> > > nslu2 support which used to pad with zeros (I presume that's been 
> > fixed
> > > by now).
> > >
> > Can someone confirm it?
>
> It looks like it is still padded with zeros in trunk. I'll try to fix
> and test that in the next couple of days, unless Martin or Joey beats
> me to it.
>
> > > Note that Apex should build out of the box for Debian/NSLU2 just like
> > > any other normal Debian package.
> > So, how affects it to the instructions of the wiki?
>
> To what wiki page you are referring?
The instructions on http://www.nslu2-linux.org/wiki/Debian/CompileApex 
still need to be followed
when building your own apex from source. I wrote a little python script 
that does all of the stages
from make output to mtdblock image: prepend header, byte swap, pad with 
FFs. I could upload
it (to the NSLU2-linux files area?) if anyone thinks it may be helpful:

usage: pad.py [options] infile outfile
  convert an Apex image into an NSLU2 mtdblock image:
  - Add a 16-byte header, with a 4-byte count
  - Byte swap [optional]
  - Pad with FF's

options:
 --version   show program's version number and exit
 -h, --help  show this help message and exit
 -s          Swapped image, don't swap again
 -p bytes    Size to pad to [default 131072]

...probably only works on little-endian machines (i386, AMD, 
Debian/NSLU2, ...)

> Gordon