lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:	Tue, 25 Dec 2007 14:35:40 +0100
From:	Pierre Ossman <drzeus@...eus.cx>
To:	"raki john" <raki4652@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: relation between mmc_request, mmc_data and mmc_command

On Sun, 23 Dec 2007 23:25:26 -0800
"raki john" <raki4652@...il.com> wrote:

> 
> Does  mmc_requeest->stop is equal  to mmc_request->data->stop ?
> 
> Does  mmc_request   is equal  to mmc_request->data->mrq ?
> 
> Does mmc_request->data   is equal  to   mmc_request->cmd->data ?
> 
> Does mmc_request   is equal  to mmc_request->cmd->mrq  ?
> 

Yes on all accounts. I don't know the reason for this extreme redundancy. It was there long before I got involved.

> 
> I think Stop command which is part of mmc_request is used for sending stop
> command after Multi Block write. is this correct. If stop command fails(CRC
> fail, timeout), does this mean card  write failed.
> 

It is correct that it is used for multi block writes. But also other open ended transfers.

If the stop command fails, then the card will be in an unknown state. The write should have been completed though.

Rgds
Pierre

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ