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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240726074925.1c7df571@kernel.org>
Date: Fri, 26 Jul 2024 07:49:25 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Jose Ignacio Tornos Martinez <jtornosm@...hat.com>,
 UNGLinuxDriver@...rochip.com, davem@...emloft.net, edumazet@...gle.com,
 gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
 linux-usb@...r.kernel.org, lucas.demarchi@...el.com, mcgrof@...nel.org,
 netdev@...r.kernel.org, pabeni@...hat.com, woojung.huh@...rochip.com
Subject: Re: [PATCH] net: usb: lan78xx: add weak dependency with micrel phy
 module

On Thu, 25 Jul 2024 00:57:05 +0200 Andrew Lunn wrote:
> Maybe a better solution is to first build an initramfs with
> everything, plus the kitchen sink. Boot it, and then look at what has
> been loaded in order to get the rootfs mounted. Then update the
> initramfs with just what is needed? That should be pretty generic,
> with throw out networking ig NFS root is not used, just load JFFS2 and
> a NAND driver if it was used for the rootfs, etc.

Sorry for a dumb question from the audience but how does this work 
for PCI devices? We don't worry about what drivers may be needed
because there's no "fallback / generic" driver?
For MDIO are the ID registers too complicated to expose to user space
and let it match the drivers using modinfo (avoiding the need to boot
a kitchen sink kernel)?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ