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  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, 17 Jul 2020 16:36:47 +0100
From:   Mark Brown <>
To:     Greg KH <>
Cc:     Arnd Bergmann <>,
        Catalin Marinas <>,
        Linus Walleij <>,
        Bjorn Andersson <>,
        "" <>,
        Fabio Estevam <>,
        Anson Huang <>, Jon Corbet <>,
        Will Deacon <>, Olof Johansson <>,
        Russell King <>,
        Bartosz Golaszewski <>,
        Andreas Kemnade <>,
        Geert Uytterhoeven <>,
        dl-linux-imx <>,
        Sascha Hauer <>,
        "open list:GPIO SUBSYSTEM" <>,
        John Stultz <>,
        Adam Ford <>,
        Linux ARM <>,
        "" <>,
        Leo Li <>, Vinod Koul <>,
        Sascha Hauer <>,
        Kevin Hilman <>,
        "" <>,
        Shawn Guo <>
Subject: Re: [PATCH 1/3] gpio: mxc: Support module build

On Fri, Jul 17, 2020 at 04:13:44PM +0200, Greg KH wrote:
> On Fri, Jul 17, 2020 at 03:54:49PM +0200, Arnd Bergmann wrote:

> > > 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 :)

> > Can you give a specific example? The only problem I'm aware of for
> > those SoCs is drivers being outside of the mainline kernel. Clearly
> > having support for loadable modules helps SoC vendors because it
> > allows them to support a new platform with an existing binary kernel
> > by shipping third-party driver modules, but for stuff that is already
> > in mainline, we could in theory support all hardware in a single gigantic
> > binary kernel with no support for loadable modules at all.

> That did not work for many drivers for some reason, look at all the work
> Saravana had to do in the driver core and device tree code for it to
> happen correctly over the past year.

Could you be more specific about these issues?  I'm aware of his work
around probe ordering but that's not at all arch specific, the same
issues affect every architecture, so doesn't seem to be what you're
talking about.

arm64 has never supported anything other than a multiplatform kernel,
and the actively maintained 32 bit platforms have supported one for more
than half a decade at this point.  CI systems keep managing to test
these kernels, distributions seem to keep managing to ship them and
users appear able to install and use them so it doesn't seem quite so
fundamentally broken as all that.

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

Powered by blists - more mailing lists