Hi,
On 10/12/2015 01:33 AM, Brian Norris wrote:
Hi Boris,
On Fri, Oct 02, 2015 at 08:27:38AM +0200, Boris Brezillon wrote:
Brian, Archit,
On Thu, 1 Oct 2015 19:44:34 -0700
Brian Norris wrote:
On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote:
Some controllers can access the fa
Hi Boris,
On Fri, Oct 02, 2015 at 08:27:38AM +0200, Boris Brezillon wrote:
> Brian, Archit,
>
> On Thu, 1 Oct 2015 19:44:34 -0700
> Brian Norris wrote:
>
> > On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote:
> > > Some controllers can access the factory bad block marker from OOB on
Brian, Archit,
On Thu, 1 Oct 2015 19:44:34 -0700
Brian Norris wrote:
> On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote:
> > Some controllers can access the factory bad block marker from OOB only
> > when they read it in raw mode. When ECC is enabled, these controllers
> > discard r
On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote:
> Some controllers can access the factory bad block marker from OOB only
> when they read it in raw mode. When ECC is enabled, these controllers
> discard reading/writing bad block markers, preventing access to them
> altogether.
>
> T
Some controllers can access the factory bad block marker from OOB only
when they read it in raw mode. When ECC is enabled, these controllers
discard reading/writing bad block markers, preventing access to them
altogether.
The bbt driver assumes MTD_OPS_PLACE_OOB when scanning for bad blocks.
This
5 matches
Mail list logo
