Subversion Repositories or1k

 request_firmware() hotplug interface:
 ------------------------------------
        Copyright (C) 2003 Manuel Estrada Sainz <ranty@debian.org>

 Why:
 ---

 Today, the most extended way to use firmware in the Linux kernel is linking
 it statically in a header file. Which has political and technical issues:

  1) Some firmware is not legal to redistribute.
  2) The firmware occupies memory permanently, even though it often is just
     used once.
  3) Some people, like the Debian crowd, don't consider some firmware free
     enough and remove entire drivers (e.g.: keyspan).

 about in-kernel persistence:
 ---------------------------
 Under some circumstances, as explained below, it would be interesting to keep
 firmware images in non-swappable kernel memory or even in the kernel image
 (probably within initramfs).

 Note that this functionality has not been implemented.

 - Why OPTIONAL in-kernel persistence may be a good idea sometimes:
 
        - If the device that needs the firmware is needed to access the
          filesystem. When upon some error the device has to be reset and the
          firmware reloaded, it won't be possible to get it from userspace.
          e.g.:
                - A diskless client with a network card that needs firmware.
                - The filesystem is stored in a disk behind an scsi device
                  that needs firmware.
        - Replacing buggy DSDT/SSDT ACPI tables on boot.
          Note: this would require the persistent objects to be included
          within the kernel image, probably within initramfs.
          
   And the same device can be needed to access the filesystem or not depending
   on the setup, so I think that the choice on what firmware to make
   persistent should be left to userspace.

 - Why register_firmware()+__init can be useful:
        - For boot devices needing firmware.
        - To make the transition easier:
                The firmware can be declared __init and register_firmware()
                called on module_init. Then the firmware is warranted to be
                there even if "firmware hotplug userspace" is not there yet or
                it doesn't yet provide the needed firmware.
                Once the firmware is widely available in userspace, it can be
                removed from the kernel. Or made optional (CONFIG_.*_FIRMWARE).

        In either case, if firmware hotplug support is there, it can move the
        firmware out of kernel memory into the real filesystem for later
        usage.

        Note: If persistence is implemented on top of initramfs,
        register_firmware() may not be appropriate.