Submit #3041
open
firmware: Remove embedding of multiple images in one module.
Added by Anonymous over 7 years ago.
Updated almost 4 years ago.
Description
Hello,
this patch removes possibility of embedding more than one firmware image in one kernel module through the parent reference in the firmware_register() function.
This patch is a preparation for firmware subsystem modification for moving firmware images from kernel modules to userland.
The mechanism is not used and it can be functionally fully replaced by putting each firmware image in its own module.
Removing the functionality significantly simplifies handling of firmware images. If firmware images are moved to userland the logical grouping of modules could be expressed by putting the related firmware images into one directory if needed.
jan
Files
From zrj:
(1) Having support for multiple embedded firmware images in one module is useful, and I doubt we would want to move firmware handling to userland.
(2) Having firmware as kernel module allows to load it in "/boot/loader.conf" before kernel boots for early modules, like radeon(4) or network card drivers.
liweitianux wrote:
From zrj:
(1) Having support for multiple embedded firmware images in one module is useful, and I doubt we would want to move firmware handling to userland.
(2) Having firmware as kernel module allows to load it in "/boot/loader.conf" before kernel boots for early modules, like radeon(4) or network card drivers.
In which cases is having multiple firmware images in one module useful?
The DragonFly Projects page mentions a task for moving firmware to userland: https://www.dragonflybsd.org/docs/developer/ProjectsPage/#index19h3
Can it be removed from that page to prevent future misunderstandings?
Also available in: Atom
PDF
Updated by 
Updated by