[armedslack] Help deciding which bits of mtd-utils to include in the installer

[Thierry MERLE]

Hi Stuart,

On Thu, 3 Sep 2009 15:24:10 -0700 (PDT)
Stuart Winter <mozes at slackware.com> wrote:

> 
> Hi
> 
> I'm updating the installer for the new EABI port, and although Slackware
> ARM won't yet support installation to flash/NAND, I know there are some
> people who'd want to do it.
> 
What type of devices you plan to address?

Concerning the NSLU2, I only access the mtd block devices, detected directly by the kernel by the MTD drivers (attached my config for NSLU2, kernel 2.6.7.4).
To flash the kernel and the initrd, I grabbed a script from debian.
There is some magic FIS decoding to calculate some offsets but this is particular to the NSLU2.
He is a modified debian script, works only for flashing my custom kernel, only for NSLU2 (I did not update it for other devices).
I commented out the annoying things (dpkg calls), and hardcoded values, it works...

It requires devio, specific to write on mtd block devices.
No need of any flash_erase or nanwrite (for char devices).

Cheers,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config-2.6.27.4.gz
Type: application/x-gzip
Size: 16212 bytes
Desc: not available
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20090904/ad17efcf/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: flash-kernel
Type: application/octet-stream
Size: 6113 bytes
Desc: not available
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20090904/ad17efcf/attachment.obj>