X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=Documentation%2Ffirmware_class%2FREADME;fp=Documentation%2Ffirmware_class%2FREADME;h=e9cc8bb26f7d0952b0226c66e6a43abe8e00a211;hb=43bc926fffd92024b46cafaf7350d669ba9ca884;hp=43e836c07ae89ee817ad75fe33e9cd37ea5b44ae;hpb=cee37fe97739d85991964371c1f3a745c00dd236;p=linux-2.6.git

diff --git a/Documentation/firmware_class/README b/Documentation/firmware_class/README
index 43e836c07..e9cc8bb26 100644
--- a/Documentation/firmware_class/README
+++ b/Documentation/firmware_class/README
@@ -105,20 +105,3 @@
    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.
-