linux-kernel - Re: [PATCH 2/8] Kconfig: unwanted menus for s390.

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]

Date:	Sun, 22 Apr 2007 02:32:09 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 2/8] Kconfig: unwanted menus for s390.

On Sunday 22 April 2007, Arnd Bergmann wrote:
> I would prefer to not have 'depends on !S390' but rather 'depends on MMIO',
> because that is what really drives stuff like IPMI: they expect the device
> to be reachable through the use of ioremap or inX/outX instructions, which
> don't exist on s390.
> 
> While it's unlikely that another architecture has the same restriction,
> it expresses much clearer what you mean.
> 
> In drivers/Kconfig, you can then simply add a
> 
> config MMIO
>         def_bool !S390

I just saw that we already have an option like that, with a slightly different
name.

arch/s390/Kconfig contains

config NO_IOMEM
	def_bool y

and lib/Kconfig contains

config HAS_IOMEM
	boolean
	depends on !NO_IOMEM
	default y

You should probably just use one of these two to disable any driver that
uses ioremap or similar.

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