[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <457449CD.3040108@indt.org.br>
Date: Mon, 04 Dec 2006 12:16:13 -0400
From: Anderson Briglia <anderson.briglia@...t.org.br>
To: ext Pierre Ossman <drzeus-list@...eus.cx>
CC: "Linux-omap-open-source@...ux.omap.com"
<linux-omap-open-source@...ux.omap.com>,
Russell King <rmk+lkml@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@...t.org.br>,
ext David Brownell <david-b@...bell.net>,
"Lizardo Anderson (EXT-INdT/Manaus)" <anderson.lizardo@...t.org.br>,
linux-kernel@...r.kernel.org
Subject: Re: [patch 4/5] [RFC] Add MMC Password Protection (lock/unlock) support
V7: mmc_sysfs.diff
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists