From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Kevin Cernekee <cernekee@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: NAND flash data table
Date: Thu, 26 Aug 2010 09:02:29 +0300 [thread overview]
Message-ID: <1282802549.24044.267.camel@localhost> (raw)
In-Reply-To: <4C75FF39.9010709@gmail.com>
On Wed, 2010-08-25 at 22:44 -0700, Brian Norris wrote:
> Hello,
>
> I am submitting two documents to the general Linux MTD community
> (attached). They are two tables: one in simple CSV format and the other
> in a lightly formatted HTML page. They comprise the summary of a few
> months' work in studying and cataloging NAND flash parts and their data
> sheets. The attached data should be helpful to other developers in
> debugging support for various chips as well as in determining future
> methods for detection of new chips. There are a few extra comments and
> color-labeling in the HTML doc.
>
> I am open to the wider use of these documents (e.g., incorporation into
> the MTD website as additional documentation) and have GPL'd the table.
> It could very easily be converted to a kind of XML mini-database with
> functionality to build into a web-page. Of course, I don't have time to
> do this at the moment :) Send me any comments or questions, though.
>
> I hope this is useful!
Impressive! How about sending a patch against mtd-www.git and we'll put
this to the web site?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-08-26 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 5:44 NAND flash data table Brian Norris
2010-08-26 6:02 ` Artem Bityutskiy [this message]
2010-08-30 12:34 ` Artem Bityutskiy
2010-08-31 1:43 ` Brian Norris
2010-08-31 1:55 ` [PATCH] NAND-DATA: Added NAND support table Brian Norris
2010-08-31 23:16 ` [PATCH v2] mtd-www: " Brian Norris
2010-09-01 21:59 ` Artem Bityutskiy
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=1282802549.24044.267.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).