public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Markus Schiltknecht <markus@bluegap.ch>
To: linux-mtd@lists.infradead.org
Subject: curious questions
Date: Wed, 21 May 2008 11:16:45 +0200	[thread overview]
Message-ID: <4833E87D.10209@bluegap.ch> (raw)

Hi,

I'm new to the list - and having lots of questions. Feel free to simply 
point me to earlier discussions or other resources. Even simple Yes or 
No answers might also do it ;-)

Having read through most of the infradead.org website (and others), I 
today realized, that erase blocks span *multiple* pages, which explains 
the huge difference in 'block size' sometimes cited (around 2K vs around 
128K).

Now, if I understand correctly, a flash chip supports reading and 
(limited) writing to pages, and erasing erase-blocks. But the MTD FAQ 
states:

 > (The mtd device) maintains 3 main operations: read from eraseblock,
 > write to eraseblock, and erase eraseblock

Am I understanding correctly, that I can't write to the a single page 
with MTD (after having erased the according erase-block)? Even if I'm 
writing the single pages in the block sequentially?


Can I repeatedly write to a NAND flash page, to set its bits to 1 
(without resetting any bit to 0) (or vice-versa for XOR)?


I've followed the 'hardware devices' cited on the website, but it seems 
a little out-dated. What's an inexpensive way to get a device with 
accessible NAND chips on it to play with? It looks to me like you only 
get to purchase stuff with embedded FTL, which isn't suitable as an mtd.


Looking forward to your answers, hints and pointers.

Markus

             reply	other threads:[~2008-05-21  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  9:16 Markus Schiltknecht [this message]
2008-05-21  9:38 ` curious questions Jörn Engel
2008-05-21  9:52   ` Markus Schiltknecht
2008-05-21 10:01     ` Jörn Engel

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=4833E87D.10209@bluegap.ch \
    --to=markus@bluegap.ch \
    --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