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:	Tue, 10 Mar 2015 10:02:15 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Brian Norris <computersforpeace@...il.com>,
	Andrew Victor <linux@...im.org.za>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	linux-kernel@...r.kernel.org,
	Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
	alexandre.belloni@...e-electrons.com
Subject: Re: [PATCH] ARM: at91: force CPU selection

On Monday 09 March 2015 23:59:58 Brian Norris wrote:
> @@ -114,6 +114,12 @@ config SOC_AT91SAM9
>             AT91SAM9XE
>  endif # SOC_SAM_V4_V5
>  
> +config MACH_AT91_AUTO
> +       def_bool y
> +       depends on !SOC_AT91SAM9 && !SOC_SAMA5D4
> +       select SOC_SAMA5D3 if SOC_SAM_V7
> +       select SOC_AT91RM9200 if SOC_SAM_V4_V5
> +
>  comment "AT91 Feature Selections"
>  
>  config AT91_SLOW_CLOCK

Hi Brian,

I actually added a bunch of these in other places, but have stopped
doing so because Russell didn't like them, and I tend to follow
his argument now that it's actually pretty confusing.

In case of at91, we can do better now, once we have multiplatform
enabled, and we can simply remove the SOC_SAM_V7 and SOC_SAM_V4_V5
symbols entirely (if Alexandre's patch doesn't already do that).

With multiplatform enabled, you no longer have to select a particular
SoC, because we always get the default selection and the kernel
will build without any one of them being enabled.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ