Am 24.10.2015 um 21:00 schrieb Stefan Brüns:
Broadcom 63xx is MIPS only, unfortunately KConfig does
Someone on opensuse-arm list disputed that, saying these drivers are
specifically both for MIPS and ARM (just like there's some drivers with
SH or PPC in the name historically that are valid and used for ARM).
Note that for example Exynos4 drivers are reused for Exynos5, so we need
to consider transitive relations as well, not just 63xx.
So, what do you base the above on? Did you verify that no OF compatible
string from those drivers is used in arch/arm/boot/dts/*? If you did,
please propose a paragraph to add to the commit message as explanation.
Signed-off-by: Stefan Brüns <stefan.bruens(a)rwth-aachen.de>
config/armv6hl/default | 4 ++--
config/armv6hl/vanilla | 4 ++--
I assume this part is good, as most users will run a Raspberry Pi with
config/armv7hl/default | 4 ++--
config/armv7hl/lpae | 4 ++--
config/armv7hl/vanilla | 4 ++--
For these I'm less certain. There's a bcm63138.dtsi file, for instance,
which is referenced from bcm963*.dts. Haven't found time to investigate
how all these families are connected.
5 files changed, 10 insertions(+), 10 deletions(-)
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org