From: Thomas Gleixner <tglx@linutronix.de>
To: Mikael Starvik <mikael.starvik@axis.com>
Cc: linux-mtd@lists.infradead.org
Subject: RE: NAND programming bug in Linux 2.6.8?
Date: Fri, 15 Oct 2004 14:05:14 +0200 [thread overview]
Message-ID: <1097841913.17034.68.camel@thomas> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66818F58F@exmail1.se.axis.com>
On Fri, 2004-10-15 at 13:50, Mikael Starvik wrote:
> >1. As we do only full page reads, this will never happen. The READ1 code
> >could go away complete.
>
> Hmm. I could swear that I have seen it at least once since my NAND model
> complained about it but now I can't repeat it.
Can you add a BUG() in there ? If it ever happens again we can figure
out where it's called from.
> >2. If you want to read the second half of the page, then it's completely
> >correct to issue the READ1 command, because the column address is
> >shifted right by 1 later. The READ1 command selects the second half of
> >the page whether the chip is in 8 or in 16 bit mode.
>
> Ok, good! My Samsung datasheet (K9F2816U0C) is very vague on this point. In
> the programming examples for the 16 bit device only READ0 and READ_OOB is
> mentioned (while for the 8-bits device READ1 is also mentioned).
Yeah, its not neccecary for 16 bit, as the column address always fits
into 8bit.
tglx
next prev parent reply other threads:[~2004-10-15 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C668018E2C8E@exmail1.se.axis.com>
2004-10-15 11:50 ` NAND programming bug in Linux 2.6.8? Mikael Starvik
2004-10-15 12:05 ` Thomas Gleixner [this message]
2004-10-15 10:53 Mikael Starvik
2004-10-15 11:13 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1097841913.17034.68.camel@thomas \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=mikael.starvik@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox