linux-kernel - Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE

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: <20120806155805.GR16861@opensource.wolfsonmicro.com>
Date:	Mon, 6 Aug 2012 16:58:06 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Haojian Zhuang <haojian.zhuang@...il.com>
Cc:	sameo@...ux.intel.com, rpurdie@...ys.net, bryan.wu@...onical.com,
	linux-kernel@...r.kernel.org, Bergmann Arnd <arnd@...db.de>,
	Russell King <rmk@....linux.org.uk>
Subject: Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE_MEM

On Mon, Aug 06, 2012 at 11:56:47PM +0800, Haojian Zhuang wrote:
> On Mon, Aug 6, 2012 at 11:46 PM, Mark Brown

> > Right, but _MEM isn't terribly relevant either.  If anything _IO is a
> > bit better as ioports are *somewhat* similar to registers.

> The problem is that each bit is already used in 32-bit IORESOURCE. I can't
> find a empty bit to define the new IORESOURCE.

That's one reason why I've not attacked this problem myself, but frankly
I'm totally happy with using _IO here so I've not looked particularly
closely.
--
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/