From: Edward Falk <Edward.Falk@palm.com>
To: linux-mmc@vger.kernel.org
Subject: Any work being done on MMC write protect?
Date: Wed, 10 Mar 2010 20:01:24 -0800 [thread overview]
Message-ID: <4B986B14.6040304@palm.com> (raw)
I've written some ioctls (for the 2.6.29 kernel) which implement
SEND_WRITE_PROT and SET_WRITE_PROT. However I can't get them to work --
the former throws a CRC error and the latter returns success but doesn't
actually write-protect the device.
I was wondering if anybody else had done any work in this area.
If anybody wants the code, I can send a patch along.
-ed falk
reply other threads:[~2010-03-11 4:11 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=4B986B14.6040304@palm.com \
--to=edward.falk@palm.com \
--cc=linux-mmc@vger.kernel.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).