Hi, Am 18.11.2017 um 09:42 schrieb Alexander Graf: > Am 17.11.2017 um 23:46 schrieb Stefan Brüns <[email protected]>: >> currently config.sh creates several SoC specific files ad-hoc (i.e. using >> echo). This has several drawbacks: >> >> - it bloats config.sh (e.g 840 lines for the omap beagle /var/lib/alsa/ >> asound.state) >> - it creates files which are not tracked by RPM >> - most importantly, these files are never updated > > There is one more problem: The mechanism only works with images, not the > installer. > > Ideally, we could somehow get override logic like this working with the > installer as well. Is there some rpm magic that automatically selects a > package depending on dmi information for example? Or dt compatibles?
Check out the Supplements in https://build.opensuse.org/package/view_file/hardware/bcm43xx-firmware/bcm43xx-firmware.spec?expand=1 That said, I pointed out to Stefan that it would be best to implement the DT dependency resolution in dracut rather than cementing these workaround configs into packages that need to be maintained forever. That leaves a couple of blacklists or forced loads that should be investigated and dropped once fixed in the kernel. Remaining would then be some X11 configs that might go into generic packages if guarded properly? Regards, Andreas -- 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: [email protected] To contact the owner, e-mail: [email protected]
