From: Reinette Chatre Date: Tue, 15 Jan 2008 01:46:24 +0000 (-0800) Subject: iwlwifi: remove reference to non-existent documentation X-Git-Tag: v2.6.25-rc1~1162^2~118 X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e7a2827cbbdb11717877c44cbbdf0fb1d14e890c;p=linux-2.6 iwlwifi: remove reference to non-existent documentation The external iwlwifi driver comes with a README file that is referenced by the Kconfig. This README is not present in the driver included in the kernel. Remove references to this documentation. Signed-off-by: Reinette Chatre Acked-by: Tomas Winkler Signed-off-by: John W. Linville --- diff --git a/drivers/net/wireless/iwlwifi/Kconfig b/drivers/net/wireless/iwlwifi/Kconfig index 66ca942ddc..d1af938b9a 100644 --- a/drivers/net/wireless/iwlwifi/Kconfig +++ b/drivers/net/wireless/iwlwifi/Kconfig @@ -9,17 +9,15 @@ config IWL4965 This driver uses the kernel's mac80211 subsystem. - See for - information on the capabilities currently enabled in this - driver and for tips for debugging any issues or problems. - In order to use this driver, you will need a microcode (uCode) image for it. You can obtain the microcode from: . - See the above referenced README.iwlwifi for information on where - to install the microcode images. + The microcode is typically installed in /lib/firmware. You can + look in the hotplug script /etc/hotplug/firmware.agent to + determine which directory FIRMWARE_DIR is set to when the script + runs. If you want to compile the driver as a module ( = code which can be inserted in and remvoed from the running kernel whenever you want), @@ -92,17 +90,15 @@ config IWL3945 This driver uses the kernel's mac80211 subsystem. - See for - information on the capabilities currently enabled in this - driver and for tips for debugging any issues or problems. - In order to use this driver, you will need a microcode (uCode) image for it. You can obtain the microcode from: . - See the above referenced README.iwlwifi for information on where - to install the microcode images. + The microcode is typically installed in /lib/firmware. You can + look in the hotplug script /etc/hotplug/firmware.agent to + determine which directory FIRMWARE_DIR is set to when the script + runs. If you want to compile the driver as a module ( = code which can be inserted in and remvoed from the running kernel whenever you want),