On Mon, 2019-07-15 at 09:31 +0200, Chris Laif wrote:
> On Sat, Jul 13, 2019 at 11:37 PM Ben Hutchings <b...@decadent.org.uk> wrote:
> > On Thu, 2019-07-11 at 15:11 +0200, Chris Laif wrote:
> > > Package: debian-installer
> > > Version: 20190702
> > >
> > > I'm using the current Buster kernel/initrd on my Seagate Blackarmor NAS.
> > >
> > > The mtd partition map ('mtdparts' cmdline variable) has no effect
> > > (even with 'cmdline' module loaded):
> > [...]
> >
> > What if you replace "mtdparts=" with "cmdlineparts.mtdparts="?
> >
>
> With "cmdlineparts.mtdparts" it does not work:
[...]
> With "cmdlinepart.mtdparts" (without trailing "s", equal to the name
> of the kernel-module) it works!:Sorry for the typo. > ~ # cat /proc/cmdline > console=ttyS0,115200 > cmdlinepart.mtdparts=orion_nand:0xa0000@0x0(uboot),0x010000@0xa0000(env),0x500000@0xc0000(uimage),0x1a40000@0x5c0000(rootfs) > ~ # cat /proc/mtd > dev: size erasesize name > mtd0: 000a0000 00004000 "uboot" > mtd1: 00010000 00004000 "env" > mtd2: 00500000 00004000 "uimage" > mtd3: 01a40000 00004000 "rootfs" > ~ # > > This seems to break backwards compatibility for a lot of devices > (Google shows lots of hits for "mtdparts=" and only a handful for > "cmdlinepart.mtdparts", so I think nobody is using the latter). > > I wonder what's the best way to have a both Stretch and Buster > compatible cmdline. A quick test shows that "cmdlinepart.mtdparts" > works with Stretch, too (even Stretch does not have a seperate > "cmdlinepart" module). Do you have any recommendations? I think that "cmdlinepart.mtdparts" will work whether or not the driver is actually a module. But I accept it would be better if "mtdparts" also continued to work when the driver is a module. Ben. -- Ben Hutchings If God had intended Man to program, we'd have been born with serial I/O ports.
signature.asc
Description: This is a digitally signed message part
