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

Bug#931852: [armel/marvell] cmdline mtd partition map without effect



On Tue, Jul 16, 2019 at 12:25 PM Ben Hutchings <ben@decadent.org.uk> wrote:
> On Tue, 2019-07-16 at 09:02 +0200, Chris Laif wrote:
> > On Tue, Jul 16, 2019 at 1:22 AM Ben Hutchings <ben@decadent.org.uk> wrote:
> >
> > Thanks. Do you know if the acceptance of 'mtdparts' with/without
> > prefix is specific to the Debian kernel or if it is a decision by the
> > upstream kernel devs? I remember that some months ago one of the beta
> > Buster kernels accepted the 'mtdparts' variable, I /think/ the
> > incompatible change has been introduced during finalisation of Buster.
> >
> > Kernel docs (https://www.kernel.org/doc/html/v4.19/admin-guide/kernel-parameters.html)
> > refer to the 'mtdparts' variable (without prefix).
>
> The difference in behaviour between the built-in and modular builds of
> the driver, is not specific to Debian.
>
> The change to building this driver as a module was our decision,
> however.  That change was made in version 4.16-1~exp1, over a year ago.
>

Thanks. I'm using 'cmdlinepart.mtdparts' now and for me this bug can
be closed. I expect other people will run into this problem but I'm
not in a position to judge of whether including cmdlinepart as a
module or not.

Chris


Reply to: