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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090811140223.GA4278@console-pimps.org>
Date:	Tue, 11 Aug 2009 15:02:24 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Adrian Hunter <adrian.hunter@...ia.com>
Cc:	Pierre Ossman <pierre@...man.eu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-embedded@...r.kernel.org" <linux-embedded@...r.kernel.org>,
	"nico@....org" <nico@....org>,
	"nicolas.ferre@....atmel.com" <nicolas.ferre@....atmel.com>,
	"hskinnemoen@...el.com" <hskinnemoen@...el.com>,
	"tony@...mide.com" <tony@...mide.com>,
	"david-b@...bell.net" <david-b@...bell.net>,
	"manuel.lauss@...il.com" <manuel.lauss@...il.com>,
	"mirq-linux@...e.qmqm.pl" <mirq-linux@...e.qmqm.pl>,
	"ppisa@...ron.com" <ppisa@...ron.com>,
	"Lavinen Jarkko (Nokia-D/Helsinki)" <jarkko.lavinen@...ia.com>,
	"ben@...ff.org" <ben@...ff.org>,
	"saschasommer@...enet.de" <saschasommer@...enet.de>,
	"avorontsov@...mvista.com" <avorontsov@...mvista.com>,
	"oakad@...oo.com" <oakad@...oo.com>,
	"ian@...menth.co.uk" <ian@...menth.co.uk>,
	"HaraldWelte@...tech.com" <HaraldWelte@...tech.com>,
	"JosephChan@....com.tw" <JosephChan@....com.tw>
Subject: Re: New MMC maintainer needed

On Mon, Aug 03, 2009 at 02:13:28PM +0300, Adrian Hunter wrote:
> Pierre Ossman wrote:
>> Con:
>>
>>  - The scanning code gets less clear as you increase the number of
>>    possible paths through it.
>>
>>  - Different systems will have different init sequences, possibly
>>    provoking bugs in the cards.
>>
>>  - Host driver writers now have more capability bits they have to
>>    consider. And these might be less than obvious since SD/MMC/SDIO are
>>    normally compatible so these bits seem useless.
>>
>>  - With the current logic (which was better in the first version),
>>    "normal" drivers will have to explicitly state that they work as
>>    intended by setting all bits.
>
> And the pro is objective.
>
>> Pro:
>>
>>  - A slightly reduced scanning time.
>
> That's great!  Why do you disregard this so easily?
>

Ping. Adrian, do you have any initialisation times for this patch? I'm
afraid I don't have any eMMC hardware, so I'm not able to gather any
numbers.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ