linux-kernel - Re: Kconfig condition on BCM2835

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250204-papaya-grudge-2b7dd5c73917@spud>
Date: Tue, 4 Feb 2025 23:31:28 +0000
From: Conor Dooley <conor@...nel.org>
To: daniel.lezcano@...aro.org, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, etienne.buira@...e.fr
Cc: florian.fainelli@...adcom.com
Subject: Re: Kconfig condition on BCM2835_TIMER (and others)

On Mon, Feb 03, 2025 at 01:44:05PM +0100, Etienne Buira wrote:
> Resend with corrected email address.
> 
> On Mon, Feb 03, 2025 at 01:39:33PM +0100, Etienne Buira wrote:
> > Hi all,
> > 
> > I want to build a kernel for Raspberry pi 4B, which, according to the
> > dtb, has a bc2835-system-timer. This device is handled by
> > drivers/clocksource/bcm2835_timer.c, which is built depending on
> > CONFIG_BCM2835_TIMER.
> > 
> > However, the config option is guarded by "if COMPILE_TEST" condition.
> > 
> > Shouldn't that condition be ARM64 || COMPILE_TEST (ie be selectable on
> > arm64 builds)?

Perhaps, but I'd wonder why arm64 and arm32 are being treated differently.
Florian, why's there no select on arm64 when the BCM2835 family option
is enabled?

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)