Bill Nottingham wrote: > Goede, J.W.R. de (j.w.r.degoede@xxxxxx) said: >> 2 Firmware buddy >> ================ >> >> Here is what I would like to see (and would be willing to >> write code for): >> >> 1) A firmware load request is send to userspace >> 2) When the userspace firmware helper cannot find this >> firmware, it logs this to a missing-firmware file. >> 3) When the user logs in, a firmware-helper-applet runs >> 4) If there is missing firmware and a working internet >> connection, the applet becomes active, otherwise it >> exits >> 5) The applet looksup the firmware name in a table which >> matches it to a device-identifier. >> 6) The applet looksup manufacturers + productnames (as seen >> >> on the box/outside) of device-identifier devices. >> 7) The applet shows a gui to the user explaining that >> firmware is needed for his XXXXX (ex. wireless card) to >> work, and asks him to select the manufacturer and >> product >> of his XXXXX. >> 8) The applet downloads the windows-driver from the >> manufacturers websites and runs a special (per driver) >> shell script to extract the firmware >> 9) The user is told to reboot (or do something else to >> get the device re-initialised). > > What cards is this useful for that we don't ship firmware > for? Anything other than bcm43xx and ralink? A number of dvb and v4l devices also require firmware that we don't ship. -- Jarod Wilson jwilson@xxxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
