From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Cc: sasin@solomon-systech.com
Subject: Re: NAND device ID 0xd5 appears twice in nand_ids.c table
Date: Tue, 17 Apr 2007 08:20:11 +1200 [thread overview]
Message-ID: <200704170820.11068.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <6334E09627481B4AA5C8DE1E69E19D3B06BF96E0@SSLEXCHANGE.solomonsystech.com>
On Monday 16 April 2007 21:41, sasin@solomon-systech.com wrote:
> NAND device ID 0xd5 appears for a 4MiB device as well as for a 2GiB
> device. So when the new 2GiB device is used, it is detected as the
> older 4MiB device. Should other ID bytes perhaps be used to
> differentiate between the two? This problem will continue as older
> device IDs are reused in newer devices.
Can't the devices be differentiated by reading the part's geometry info?
next prev parent reply other threads:[~2007-04-16 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 9:41 NAND device ID 0xd5 appears twice in nand_ids.c table sasin
2007-04-16 20:20 ` Charles Manning [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-20 6:23 sasin
2007-04-20 20:57 ` 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=200704170820.11068.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=linux-mtd@lists.infradead.org \
--cc=sasin@solomon-systech.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