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: Fri, 03 Nov 2023 18:02:31 +0100
From: Duje Mihanović <>
To: Michael Turquette <>,
 Stephen Boyd <>, Linus Walleij <>,
 Rob Herring <>,
 Krzysztof Kozlowski <>,
 Conor Dooley <>, Tony Lindgren <>,
 Daniel Mack <>, Haojian Zhuang <>,
 Robert Jarzmik <>, Liam Girdwood <>,
 Mark Brown <>, Jaroslav Kysela <>,
 Takashi Iwai <>, Leo Yan <>,
 Zhangfei Gao <>, Lubomir Rintel <>,
 Catalin Marinas <>, Will Deacon <>,
 Kees Cook <>, Tony Luck <>,
 "Guilherme G . Piccoli" <>,
 Robin Murphy <>
Cc:,,,,,,,,, ~postmarketos/,
 Karel Balej <>
 Re: [PATCH v7 08/10] arm64: Kconfig.platforms: Add config for Marvell PXA1908

On Friday, November 3, 2023 4:34:54 PM CET Robin Murphy wrote:
> On 2023-11-02 3:20 pm, Duje Mihanović wrote:
> > +config ARCH_MMP
> > +	bool "Marvell MMP SoC Family"
> > +	select ARM_GIC
> > +	select ARM_ARCH_TIMER
> > +	select ARM_SMMU
> NAK, not only is selecting user-visible symbols generally frowned upon,
> and ignoring their dependencies even worse, but for a multiplatform
> kernel the user may well want this to be a module.
> If having the SMMU driver built-in is somehow fundamentally required for
> this platform to boot, that would represent much bigger problems.

The SoC can boot without SMMU and PDMA, but not GIC, pinctrl or the arch 
timer. I see that most other SoCs still select drivers and frameworks they 
presumably need for booting, with the exceptions of ARCH_BITMAIN, ARCH_LG1K 
and a couple others. Which of these two options should I go for?


Powered by blists - more mailing lists