README-all-firmware 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. Firmware taken out of all-firmware to separate PETs
  2. ---------------------------------------------------
  3. The directories inside /lib/modules/all-firmware are the "firmware" needed by modems.
  4. Actually, this can be any data-files, scripts, configuration or even binary-executables.
  5. This "firmware" has been kept in the Woof repository, however the Fossil Version
  6. Control System Sqlite repository is not the most appropriate place.
  7. So, I am in the process of taking them out, to separate PETs. A Woof developer would
  8. include these PETs in the package-list, so they will be built-in to the build of Puppy.
  9. Note, the developer would of course choose an appropriate list of firmware PETs to
  10. include. For example, the an analog modem firmware might not have an appropriate
  11. kernel driver in recent kernels. Though, the Woof build script '3builddistro' can
  12. detect this situation and suggest to remove innapropriate firmware.
  13. These firmware PETs are named "firmware_linux_module_*" to make it unambiguous what
  14. they are for. The "*" part is the name of a directory inside /lib/modules/all-firmware.
  15. Further technical notes
  16. -----------------------
  17. A "firmware_linux_module_*" PET will have files that get installed, just like any PET.
  18. However, the location /lib/modules/all-firmware is special, as files in here only get
  19. installed if matching kernel modules are loaded, meaning that the appropriate hardware
  20. is present.
  21. This keeps files out of the way and not potentially causing conflicts in the system.
  22. To see how a directory inside /lib/modules/all-firmware gets installed, see script
  23. /sbin/pup_event_backend_modprobe.
  24. Regards,
  25. Barry Kauler
  26. Sept. 2012