In the case of a nand controller that needs the OOB data before
it can read the page data, an unnecessary read sequence is sent
to the nand. This reduces read performance.
This sequence is sent by default before all page reads, but the
OOB first page read function immediately issues a new command,
On Fri, Nov 20, 2009 at 03:30:46PM +, Nick Thompson wrote:
> In the case of a nand controller that needs the OOB data before
> it can read the page data, an unnecessary read sequence is sent
> to the nand. This reduces read performance.
By how much? Is a similar patch going into Linux?
> Thi
On 20/11/09 20:17, Scott Wood wrote:
> On Fri, Nov 20, 2009 at 03:30:46PM +, Nick Thompson wrote:
>> In the case of a nand controller that needs the OOB data before
>> it can read the page data, an unnecessary read sequence is sent
>> to the nand. This reduces read performance.
>
> By how much
On Mon, Nov 23, 2009 at 10:38:02AM +, Nick Thompson wrote:
> > Ideally a high-level driver like fsl_elbc_nand wouldn't have to implement
> > cmdfunc at all.
>
> I'm not sure I know what you mean here. I'll have a look at that code.
The eLBC NAND controller presents an interface that runs enti
4 matches
Mail list logo
