Hi Miquèl,
El mar., 12 may. 2020 a las 9:34, Miquel Raynal
() escribió:
>
> Hi Álvaro,
>
> Álvaro Fernández Rojas wrote on Tue, 12 May 2020
> 09:24:32 +0200:
>
> > Hi Miquèl
> >
> > > El 12 may 2020, a las 9:16, Miquel Raynal
> > > escribió:
> > >
> > > Hi Álvaro,
> > >
> > > Álvaro Fernández
Hi Álvaro,
Álvaro Fernández Rojas wrote on Tue, 12 May 2020
09:24:32 +0200:
> Hi Miquèl
>
> > El 12 may 2020, a las 9:16, Miquel Raynal
> > escribió:
> >
> > Hi Álvaro,
> >
> > Álvaro Fernández Rojas wrote on Tue, 12 May 2020
> > 08:51:11 +0200:
> >
> >> The current code checks that the
Hi Álvaro,
Álvaro Fernández Rojas wrote on Tue, 12 May 2020
08:51:11 +0200:
> The current code checks that the whole OOB area is erased.
> This is a problem when JFFS2 cleanmarkers are added to the OOB, since it will
> fail due to the usable OOB bytes not being 0xff.
> Correct this by only check
Hi Miquèl
> El 12 may 2020, a las 9:16, Miquel Raynal
> escribió:
>
> Hi Álvaro,
>
> Álvaro Fernández Rojas wrote on Tue, 12 May 2020
> 08:51:11 +0200:
>
>> The current code checks that the whole OOB area is erased.
>> This is a problem when JFFS2 cleanmarkers are added to the OOB, since it
The current code checks that the whole OOB area is erased.
This is a problem when JFFS2 cleanmarkers are added to the OOB, since it will
fail due to the usable OOB bytes not being 0xff.
Correct this by only checking that data and ECC bytes aren't 0xff.
Fixes: 02b88eea9f9c ("mtd: brcmnand: Add chec
