From: Arnd Bergmann <arnd@arndb.de>
To: Anderson Lizardo <anderson.lizardo@indt.org.br>,
linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
David Brownell <david-b@pacbell.net>,
Tony Lindgren <tony@atomide.com>,
Anderson Briglia <anderson.briglia@indt.org.br>,
Carlos Eduardo Aguiar <carlos.aguiar@indt.org.br>
Subject: Re: [patch 4/5] Add MMC password protection (lock/unlock) support V2
Date: Wed, 28 Dec 2005 21:23:11 +0000 [thread overview]
Message-ID: <200512282123.12839.arnd@arndb.de> (raw)
In-Reply-To: <20051228185412.951490000@localhost.localdomain>
On Wednesday 28 December 2005 18:40, Anderson Lizardo wrote:
>
> Implement MMC password reset and forced erase support. It uses the sysfs
> mechanism to send commands to the MMC subsystem. Usage:
>
> Forced erase:
>
> echo erase > /sys/bus/mmc/devices/mmc0\:0001/lockable
>
> Remove password:
>
> echo remove > /sys/bus/mmc/devices/mmc0\:0001/lockable
The MMC password support seems to be a subset of the operations
possible on modern ATA drives. IMHO, any interface you introduce
should be usable for both types of devices.
The only interface I could find for ATA is through HDIO_DRIVE_CMD.
This is currently used by hdparm, but it does not look like it
fits the MMC problem well.
Has anyone already done an ioctl or sysfs implementation of ATA
password user interfaces, or is perhaps the one proposed here
sufficient for ATA drives as well?
Arnd <><
next prev parent reply other threads:[~2005-12-28 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 18:40 [patch 0/5] " Anderson Lizardo
2005-12-28 18:40 ` [patch 1/5] " Anderson Lizardo
2005-12-28 18:40 ` [patch 2/5] " Anderson Lizardo
2005-12-28 18:40 ` [patch 3/5] " Anderson Lizardo
2005-12-29 9:07 ` Chris White
2005-12-28 18:40 ` [patch 4/5] " Anderson Lizardo
2005-12-28 21:23 ` Arnd Bergmann [this message]
2005-12-28 18:40 ` [patch 5/5] " Anderson Lizardo
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=200512282123.12839.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=anderson.briglia@indt.org.br \
--cc=anderson.lizardo@indt.org.br \
--cc=carlos.aguiar@indt.org.br \
--cc=david-b@pacbell.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
/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
Powered by JetHome