linux-kernel - Re: [PATCH 1/3] at91_mci: Enable MMC_CAP_SDIO

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] [day] [month] [year] [list]

Message-Id: <1216596503.3200.24.camel@wirenth>
Date:	Mon, 21 Jul 2008 00:28:23 +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>,
	David Brownell <david-b@...bell.net>
Subject: Re: [PATCH 1/3] at91_mci: Enable MMC_CAP_SDIO_IRQ only when it
	actually works

On Sun, 2008-07-20 at 13:13 +0200, Pierre Ossman wrote:
> It does tend to make a mess of things when you start adding up all the
> gotchas of each and every broken controller out there (it seems like
> every controller decides to violate the spec in their own creative
> way).

True.

> What about David's idea? Reconfiguring the PIN to be a GPIO pin with
> an interrupt shouldn't be that difficult?

If it works its a better solution...

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