From: Andries.Brouwer@cwi.nl
To: dwmw2@infradead.org, linux-kernel@vger.kernel.org
Cc: mdharm-usb@one-eyed-alien.net
Subject: Flash device IDs
Date: Thu, 11 Apr 2002 14:00:35 GMT [thread overview]
Message-ID: <UTC200204111400.OAA599785.aeb@cwi.nl> (raw)
In include/linux/mtd/nand_ids.h there is some information
about device IDs and device properties of NAND flash devices.
In drivers/usb/storage/sddr09.c there is very similar information.
Probably both tables should be merged.
Various comments:
- The combination NAND_MFR_TOSHIBA, 0x79 is missing in nand_flash_ids[].
An appropriate line might be
{"Toshiba TH58NS100DC", NAND_MFR_TOSHIBA, 0x79, 27, 0, 3, 0x4000},
- The type names given as first item in this struct are too precise.
They include all kinds of stuff like voltage and temperature range, etc.
But the device ID only give the size, page size, erase size, I think.
So, given any card, it is quite likely that the kernel report on it
will have incorrect type number.
Moreover, I get the strong impression that Toshiba and Samsung use
identical device IDs, so that one does not need to know the
manufacturer to interpret the device ID.
Probably we should delete the first two items from the
struct nand_flash_dev, and have something like
static inline char *nand_flash_manufacturer(int manuf_id) {
switch(manuf_id) {
case NAND_MFR_TOSHIBA:
return "Toshiba";
case NAND_MFR_SAMSUNG:
return "Samsung";
default:
return "unknown";
}
}
for the manufacturer.
- In sddr09.c it is suggested that the Read Device ID command
returns two bytes. But it may return more. My source has the
comment
/*
* Read Device ID Command: 12 bytes.
* byte 0: opcode: ED
*
* Returns 2 bytes: Manufacturer ID and Device ID.
* On more recent cards 3 bytes: the third byte is an option code A5
* signifying that the secret command to read an 128-bit ID is available.
* On still more recent cards 4 bytes: the fourth byte C0 means that
* a second read ID cmd is available.
*/
Nobody knows anything about this secret command?
I hope to come with a patch one of these centuries.
Andries
next reply other threads:[~2002-04-11 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 14:00 Andries.Brouwer [this message]
2002-04-22 16:25 ` Flash device IDs David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 20:31 Andries.Brouwer
2002-04-23 12:45 ` David Woodhouse
2002-04-23 14:04 Andries.Brouwer
2002-04-23 14:24 ` David Woodhouse
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=UTC200204111400.OAA599785.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
/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