From: Anderson Briglia <anderson.briglia@indt.org.br>
To: ext Pierre Ossman <drzeus-list@drzeus.cx>
Cc: "Linux-omap-open-source@linux.omap.com"
<linux-omap-open-source@linux.omap.com>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@indt.org.br>,
ext David Brownell <david-b@pacbell.net>,
"Lizardo Anderson (EXT-INdT/Manaus)"
<anderson.lizardo@indt.org.br>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 4/5] [RFC] Add MMC Password Protection (lock/unlock) support V7: mmc_sysfs.diff
Date: Mon, 04 Dec 2006 12:16:13 -0400 [thread overview]
Message-ID: <457449CD.3040108@indt.org.br> (raw)
In-Reply-To: <45709B95.9000009@drzeus.cx>
ext Pierre Ossman wrote:
> Anderson Briglia wrote:
>> Hi Pierre,
>>
>> ext Pierre Ossman wrote:
>>> Patch looks ok. But I never got an answer what the difference between
>>> "change" and "assign" is.
>> You're right, the command is the same, but the difference is the
>> password's
>> length and password itself sent to the card.
>> According to MMC spec 4.1, when a password replacement is done, the
>> length value
>> (PWD_LEN) shall include both passwords, the old and the new one, and
>> the password
>> (PWD) shall include the old (currently) followed by the new password.
>
> So shouldn't this be something that userspace handles?
>
I merged the code for "change" and "assign". But the action (returned from kernel
to user space application continues as "change" and "assign" separately.
Anderson Briglia
prev parent reply other threads:[~2006-12-04 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 14:53 [patch 4/5] [RFC] Add MMC Password Protection (lock/unlock) support V7: mmc_sysfs.diff Anderson Briglia
2006-11-25 8:56 ` Pierre Ossman
2006-11-27 11:31 ` Anderson Briglia
2006-12-01 21:16 ` Pierre Ossman
2006-12-04 16:16 ` Anderson Briglia [this message]
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=457449CD.3040108@indt.org.br \
--to=anderson.briglia@indt.org.br \
--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=rmk+lkml@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