On Fri, Oct 19, 2012 at 01:42:52PM -0400, Christopher Harvey wrote:
In 16bit NAND mode the GPMC would send the command 0xNN as 0xFFNN
instead of 0x00NN on the bus. The 0xFFs were actually uninitialized
bits that were left unset in the GPMC command output register. The
reason they weren't
* Christopher Harvey char...@matrox.com [121026 07:47]:
On Fri, Oct 19, 2012 at 01:42:52PM -0400, Christopher Harvey wrote:
---
drivers/mtd/nand/omap2.c | 14 +-
1 files changed, 9 insertions(+), 5 deletions(-)
Ping?
Looks like you should cc also the MTD list to get more
In 16bit NAND mode the GPMC would send the command 0xNN as 0xFFNN
instead of 0x00NN on the bus. The 0xFFs were actually uninitialized
bits that were left unset in the GPMC command output register. The
reason they weren't initialized in 16bit mode is that if the same code
that writes to this
