[Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes?

[Luis R. Rodriguez]

On Tue, Jun 27, 2017 at 4:10 PM, Serge E. Hallyn <serge at hallyn.com> wrote:
> Quoting Linus Torvalds (torvalds at linux-foundation.org):
>> For example, how about a script that takes a list of PCI devices, and
>
> Or uses lspci and lsusb output?

Cristina looked at evaluating precisely *this* first as part of her
GSoC project, details on her post I linked.

Each subsystem can use different buses, so each bus might have a
different way to map to a driver. Then the driver can also change
names over kernels.

The *easier* thing to do for now was to just map a loaded module to a
kconfig symbol, and she proposed fairly simple patches to do this.
That'd allow one-to-one mapping of module from udevadm output to a
kconfig symbol. It'd try to de-hackify streamline_config.pl.

Sure built-in is still a problem, but the current logic in
streamline_config.pl to keep that enabled seems sensible.

Part of another problem is the symbol renames that happen over
kernels, but if a map existed for this, then that should enable a
forward conversion. The GSoC effort was actually partly with a focus
on backporting, so this map would ultimately be important.

 Luis