On Fri, Jul 17, 2020 at 02:27:43PM +0200, Geert Uytterhoeven wrote: > Hi Greg, > > On Fri, Jul 17, 2020 at 2:14 PM Greg KH <gre...@linuxfoundation.org> wrote: > > Android is just finally pushing vendors to get their code upstream, > > which is a good thing to see. And building things as a module is an > > even better thing as now it is finally allowing arm64 systems to be > > built to support more than one specific hardware platform at runtime. > > Can you please stop spreading this FUD?
For many many SoCs today, this is not true. Their drivers are required to be built in and will not work as modules, as we are seeing the patches try to fix. > As I said before, Arm64 kernels have supported more than one specific > hardware platform at runtime from the beginning of the arm64 port > (assumed the needed platform support has been enabled in the kernel > config, of course). > Even most arm32 kernels support this, since the introduction of the > CONFIG_ARCH_MULTIPLATFORM option. In fact every recently > introduced arm32 platform is usually v7, and must conform to this. > The sole exceptions are very old platforms, and the v4/v5/v6/v7 split > due to architectural issues (the latter still support clusters of > platforms in a single kernel). I think the confusion here is that this really does not work well, if at all, on most "high end" SoC chips due to the collection of different things all of the vendors ship to their customers. This is the work that is trying to be fixed up here. And look at the driver core work for many driver subsystems to be fixed up just to get a single kernel image to work on multiple platforms. Just because older ones did it, doesn't mean it actually works today :) thanks, greg k-h
