From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Anderson Briglia <anderson.briglia@indt.org.br>
Cc: Anderson Lizardo <anderson.lizardo@indt.org.br>,
linux-omap-open-source@linux.omap.com,
linux-kernel@vger.kernel.org,
Carlos Eduardo Aguiar <carlos.aguiar@indt.org.br>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
David Brownell <david-b@pacbell.net>
Subject: Re: [patch 0/5] Add MMC password protection (lock/unlock) support
Date: Wed, 14 Dec 2005 08:07:18 +0100 [thread overview]
Message-ID: <439FC4A6.4010900@drzeus.cx> (raw)
In-Reply-To: <439F4AD6.9090203@indt.org.br>
Anderson Briglia wrote:
> [resending summary because our first attempt failed]
>
>
> - Password caching: when inserting a locked card, the driver should try to
> unlock it with the currently stored password (if any), and if it fails,
> revoke the key containing it and fallback to the normal "no password present"
> situation.
>
Would it be possible to use the id of the card as a search key for the
password? That way several passwords can coexist.
> - Currently, some host drivers assume the block length will always be a power
> of 2. This is not true for the MMC_LOCK_UNLOCK command, which is a block
> command that accepts arbitratry block lengths. We have made the necessary
> changes to the omap.c driver (present on the linux-omap tree), but the same
> needs to be done for other hosts' drivers.
>
The MMC layer is designed that way, so it's hardly surprising that
drivers have been coded for it. I'm assuming you've removed blksz_bits
in favor of something in bytes?
Rgds
Pierre
next prev parent reply other threads:[~2005-12-14 7:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051213213208.303580000@localhost.localdomain>
2005-12-13 22:03 ` [patch 0/5] Add MMC password protection (lock/unlock) support David Brownell
2005-12-14 22:48 ` Anderson Lizardo
2005-12-27 18:48 ` Carlos Aguiar
2005-12-13 22:27 ` Anderson Briglia
2005-12-13 22:27 ` Anderson Briglia
2005-12-14 7:07 ` Pierre Ossman [this message]
2005-12-14 23:51 ` Anderson Lizardo
2005-12-15 6:49 ` Pierre Ossman
2005-12-15 9:12 ` Russell King
2005-12-15 9:27 ` Pierre Ossman
2005-12-15 10:06 ` Russell King
2005-12-15 13:44 ` Russell King
2005-12-15 16:01 ` Pierre Ossman
2005-12-29 19:06 ` Anderson Lizardo
2005-12-29 20:09 ` Russell King
2005-12-29 21:23 ` Anderson Lizardo
2005-12-29 21:37 ` Russell King
2005-12-29 19:17 ` Anderson Lizardo
2005-12-15 11:57 ` Using MMC by OSK5912 ( was Add MMC password...) Ishigami
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=439FC4A6.4010900@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--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-kernel@vger.kernel.org \
--cc=linux-omap-open-source@linux.omap.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.