From: "hinko.kocevar@cetrtapot.si" <hinko.kocevar@cetrtapot.si>
To: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Removable serial flash devices
Date: Wed, 05 Oct 2005 07:39:22 +0200 [thread overview]
Message-ID: <4343670A.1040003@cetrtapot.si> (raw)
Hi,
We have SPI dataflash (www.datakey.com) connected to CPU GPIO pins.
Device can hold up to 32Mbit serial flash and can be added/removed at
any time. How is MTD coping with 'hotpluging' of MTD devices? Are there
any available designs or device drivers that implement similar? Can we
add/remove (mtd register/unregister) device as it is detected or are
there any other limitations to this procedure?
Right now we are presenting datakey device as character device and use
stream I/O operations. In this case we can quickly detect and add/remove
device from the system. In case of MTD we are worried about mtdxx dev
entry that could remain registered if datakey is removed during data access.
With the stunning EBS mount performance we would like to put jffs2 on
datakey device in contrast to raw flash access we are using now.
Regards,
hinko
reply other threads:[~2005-10-05 5:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4343670A.1040003@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--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