From: Thomas Gleixner <tglx@linutronix.de>
To: sasin@solomon-systech.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND device ID 0xd5 appears twice in nand_ids.c table
Date: Fri, 20 Apr 2007 22:57:06 +0200 [thread overview]
Message-ID: <1177102626.22861.1.camel@chaos> (raw)
In-Reply-To: <6334E09627481B4AA5C8DE1E69E19D3B06BF9703@SSLEXCHANGE.solomonsystech.com>
On Fri, 2007-04-20 at 14:23 +0800, sasin@solomon-systech.com wrote:
> [resending w/o "Re:", apparently a "suspicious header"]
> The problem is that there is no geometry information in the ID bytes for
> the older parts with page size 512 bytes and below, which is the case
> for the 4MiB part. Unsure if anyone has compiled a dump of ID bytes for
> the older parts so that there is some fixed pattern to rely upon to
> differentiate.
I just merged a patch, that excludes the old obsolete ID's from the
table.
http://git.infradead.org/?p=mtd-2.6.git;a=commit;h=1cf9827b6852d5d81130efbf2e777e50b7126d23
tglx
next prev parent reply other threads:[~2007-04-20 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 6:23 NAND device ID 0xd5 appears twice in nand_ids.c table sasin
2007-04-20 20:57 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 9:41 sasin
2007-04-16 20:20 ` Charles Manning
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=1177102626.22861.1.camel@chaos \
--to=tglx@linutronix.de \
--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