Date: Thu, 11 Feb 2010 20:20:35 +0200 From: Alex RAY <ray@ddteam.net> To: "M. Warner Losh" <imp@bsdimp.com>, <ray@dlink.ua> Cc: freebsd-mips@FreeBSD.org Subject: RE: GEOM_MTD Message-ID: <4b744a74.0a4d5e0a.5191.fffff0b1@mx.google.com>
next in thread | raw e-mail | index | archive | help
-----Original Message-----
From: M. Warner Losh <imp@bsdimp.com>
Sent: 11 лютого 2010 р. 19:01
To: ray@dlink.ua
Cc: freebsd-mips@FreeBSD.org; loos.br@gmail.com
Subject: Re: GEOM_MTD
In message: <20100211175849.602d08cf.ray@dlink.ua>
Alexandr Rybalko <ray@dlink.ua> writes:
: Hi,
:
: in attachment GEOM module to support MTD partitioning.
: All systems in which I have seen support MTD partitions do it via values in source code.
: For more convenient change the partitions, I use hints.
> I've seen the MTD stuff also passed in as command line arguments for
Linux.
Only MTD device name for mount rootfs, like that "rootfs=/dev/mtdblock/0"
: Example hints file also in attachment.
: In this example one of partitions (0x00040000-0x003e0000) split by keyword '--PaCkImGs--' into two partitions ("kernel" and
: "roots")
: Others think things will be clear from the file itself.
> This seems a little weird to me... > Must be something I'm not getting
about this syntax. Are the characters '-' '-' 'P' 'a' 'C' 'k' 'I' 'm'
'G' 's' '-' '-' at the start of one of the partitions?
Yes. D-Link DIR-320 (cpu BCM5354) load kernel and rootfs in single file which have:
1. image header (image magic, size, CRC etc.)
2. Kernel
3. keyword '--PaCkImGs--' as a delimeter between kernel and rootfs
4. And rootfs
In different firmware different size of kernel and different rootfs offset.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4b744a74.0a4d5e0a.5191.fffff0b1>