From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Anderson Lizardo <anderson.lizardo@gmail.com>,
Anderson Briglia <anderson.briglia@indt.org.br>,
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: Thu, 15 Dec 2005 10:06:57 +0000 [thread overview]
Message-ID: <20051215100657.GC32490@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43A136F1.3040700@drzeus.cx>
On Thu, Dec 15, 2005 at 10:27:13AM +0100, Pierre Ossman wrote:
> The spec I have says that this is a single block command. So such
> trickery would not work. It isn't explicit about padding so it might be
> possible to pad the data (since password length is specified in the
> data). If not, then we either ignore this function or have a system
> where we can detect limited hosts and print warnings.
What we need is someone with the real MMC spec to tell us about the
requirements here.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-12-15 10:07 UTC|newest]
Thread overview: 17+ 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-14 7:07 ` Pierre Ossman
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 [this message]
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
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=20051215100657.GC32490@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=anderson.briglia@indt.org.br \
--cc=anderson.lizardo@gmail.com \
--cc=anderson.lizardo@indt.org.br \
--cc=carlos.aguiar@indt.org.br \
--cc=david-b@pacbell.net \
--cc=drzeus-list@drzeus.cx \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox