summaryrefslogtreecommitdiff
path: root/docs/mdev.txt
diff options
context:
space:
mode:
authorMike Frysinger2007-06-28 17:13:51 +0000
committerMike Frysinger2007-06-28 17:13:51 +0000
commitae7f7ebcb767714e4d294025e432638329f2948d (patch)
treed6cb4b84504a961897c4e2ebd2c12cb40a74b504 /docs/mdev.txt
parent12d2129d500ed93a331c5a9863dd56f5dd0235e9 (diff)
downloadbusybox-ae7f7ebcb767714e4d294025e432638329f2948d.zip
busybox-ae7f7ebcb767714e4d294025e432638329f2948d.tar.gz
document firmware support
Diffstat (limited to 'docs/mdev.txt')
-rw-r--r--docs/mdev.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/mdev.txt b/docs/mdev.txt
index 51c3f0e..0b2c37d 100644
--- a/docs/mdev.txt
+++ b/docs/mdev.txt
@@ -66,3 +66,15 @@ command to the shell), so make sure you have a shell installed at /bin/sh.
For your convenience, the shell env var $MDEV is set to the device name. So if
the device 'hdc' was matched, MDEV would be set to "hdc".
+
+----------
+ FIRMWARE
+----------
+
+Some kernel device drivers need to request firmware at runtime in order to
+properly initialize a device. Place all such firmware files into the
+/lib/firmware/ directory. At runtime, the kernel will invoke mdev with the
+filename of the firmware which mdev will load out of /lib/firmware/ and into
+the kernel via the sysfs interface. The exact filename is hardcoded in the
+kernel, so look there if you need to want to know what to name the file in
+userspace.