From: David Woodhouse <dwmw2@infradead.org>
To: Larry Doolittle <ldoolitt@recycle.lbl.gov>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND flash
Date: Tue, 16 Oct 2001 17:08:51 +0100 [thread overview]
Message-ID: <21715.1003248531@redhat.com> (raw)
In-Reply-To: <20011016083420.A18642@recycle.lbl.gov>
ldoolitt@recycle.lbl.gov said:
> I think you should double check that assertion. My understanding is
> that the "Smart" in the name is a bug. These are actually NAND chips,
> consumer-grade packaged, standardized, and marketed, with no smarts at
> all. So you _could_ use the nand.c driver, with the right interface-
> specific wrapper layer to get at the device.
Correct, with the proviso that some SmartMedia 'adapters' have
microcontrollers built in, and the host can't actually _get_ at the raw
flash.
> Unfortunately, the result would not be content-compatible with other
> SmartMedia users, because SmartMedia also has a standard for encoding
> blocks on the nand chips. I tried to read that standard, but the PDF
> file is encrypted in a way that is incompatible with xpdf-0.92. The
> URL for that reference material has been posted here before, it's
> http://www.ssfdc.or.jp/spec/english/
Acroread can manage it. It all looks fairly simple to implement.
--
dwmw2
next prev parent reply other threads:[~2001-10-16 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 15:34 NAND flash Larry Doolittle
2001-10-16 16:08 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 15:04 Eugeny Mints
2003-10-09 15:14 ` David Woodhouse
2003-10-09 15:21 ` Stephan Linke
2003-10-09 18:01 ` Charles Manning
2002-06-21 9:44 NAND FLASH Steve Tsai
2002-06-21 9:56 ` Thomas Gleixner
2002-06-21 17:07 ` Steve Tsai
2002-06-21 17:29 ` Thomas Gleixner
2001-10-16 13:53 NAND flash nagaraj trivedi
2001-10-16 13:51 nagaraj trivedi
2001-10-16 15:06 ` Steven J. Hill
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=21715.1003248531@redhat.com \
--to=dwmw2@infradead.org \
--cc=ldoolitt@recycle.lbl.gov \
--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