WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc

David Schaefer david.tillmann.schaefer at gmail.com
Tue Dec 15 10:50:34 EST 2020


Well, I now was brave enough to try to write to the block devices with
the last kernel and it failed, io error.

Kind regards

Am Mo., 14. Dez. 2020 um 18:16 Uhr schrieb David Schaefer
<david.tillmann.schaefer at gmail.com>:
>
> If this is a regression, how can we continue here? Can I give hardware
> specs and logs? I have soldered on the board to access UART. I can
> provide e.g. boot logs.
>
> /David
>
> Am Mo., 14. Dez. 2020 um 16:20 Uhr schrieb Richard Weinberger <richard at nod.at>:
> >
> > David,
> >
> > ----- Ursprüngliche Mail -----
> > > I have checked the kernel configuration. For 4.15.18 I have these settings:
> > > CONFIG_MTD_NAND_ECC=y
> > > CONFIG_MTD_NAND=y
> > > CONFIG_MTD_NAND_PXA3xx=y
> > >
> > > and for 4.16.1
> > >
> > > CONFIG_MTD_NAND_ECC=y
> > > CONFIG_MTD_NAND=y
> > > CONFIG_MTD_NAND_MARVELL=y
> > >
> > > I actually copied the working configuration from 4.15.18 to 4.16.1,
> > > did make oldconfig, and compiled it the same way as 4.15.18. Like I
> > > said above, 4.15 works, 4.16 does not.
> > > I hope this answers your question whether I see the issue with the new
> > > and the old marvell drivers because I am not 100% sure what you refer
> > > to here (I guess you mean PXA3XX vs NAND).
> >
> > Ah, right. I forgot that the old driver got removed. I thought we kept it for a few releases. ;-\
> > So there is a regression.
> >
> > Thanks,
> > //richard



More information about the linux-mtd mailing list