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: <1216547739.3200.5.camel@wirenth>
Date:	Sun, 20 Jul 2008 10:55:39 +0100
From:	ian <spyro@....com>
To:	Pierre Ossman <drzeus@...eus.cx>
Cc:	Nicolas Ferre <nicolas.ferre@...el.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	ARM Linux Mailing List 
	<linux-arm-kernel@...ts.arm.linux.org.uk>,
	Andrew Victor <linux@...im.org.za>
Subject: Re: [PATCH 1/3] at91_mci: Enable MMC_CAP_SDIO_IRQ only when it
	actually works

On Sat, 2008-07-19 at 01:01 +0200, Pierre Ossman wrote:
> > In your opinion, a printed warning that says to be sure to use only 
> > 4-bit mode SDIO cards on slot B... is not acceptable ?
> 
> It's not really up to the user. The SDIO spec does not mandate 4-bit
> support, so some cards will not have it.

That seems overly rigid.

its not linux violating the spec, its the SDIO controller in this case.

I see no harm in supporting what the hardware is actually capable of.

It wouldnt be the first bit of broken hardware supported by linux.

--
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