linux-kernel - Re: uninline check

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: <Pine.LNX.4.64N.0707181210520.29955@blysk.ds.pg.gda.pl>
Date:	Wed, 18 Jul 2007 12:33:45 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	zippel@...ux-m68k.org, jdike@...aya.com, alan@...rguk.ukuu.org.uk,
	Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: uninline check_signature()

On Tue, 17 Jul 2007, Geert Uytterhoeven wrote:

> > > No, no revert, please.  If the architecture doesn't support readb() then we
> > > need some reliable way of working that out within Kconfig.
> > 
> > Isn't that CONFIG_HAS_IOMEM?
> 
> No, having memory mapped I/O doesn't mean you have PCI.

 Hmm, TURBOchannel is not PCI, but is still accessible with 
{read,write}{b,w,l}().

> How to access memory mapped I/O depends on the bus behind the device.

 I would have thought this is to be resolved within ioremap() so that 
drivers can be made portable without twisting your arms.  With the more 
recent ioport_map() call that may be extended to port I/O type devices as 
well.  The Alpha with its dense and sparse I/O space proves it can be done 
for arbitrarily complicated arrangements.

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