OneNAND: read-while-load (known problem)

[Adrian Hunter]

On 1/8/07, Adrian Hunter <hunter.programmer at gmail.com> wrote:
> On 1/8/07, Kyungmin Park <kyungmin.park at samsung.com> wrote:
> > Hi Adrian,
> >
> > > Do you think there could be a problem with onenand_check_bufferram also?
> >
> > No, onenand_check_bufferram & onenand_update_bufferram is right.
> >
>
> What I meant was this:
>
> 1. Read page x from chip 0. It goes to dataRAM 0 in chip 0
> 2. Read page y from chip 1. It goes to dataRAM 1 in chip 1
> 3. Read page x from chip 0. Now the read incorrectly comes from
> dataRAM 0 in chip 1 because that was the last chip selected.
>
Ah, I see now, onenand_check_bufferram only checks the current dataRAM
so it won't have the wrong chip selected. Please disregard previous
email. Sorry.