diff options
author | Robert P. J. Day <rpjday@mindspring.com> | 2007-10-20 00:11:36 +0200 |
---|---|---|
committer | Adrian Bunk <bunk@kernel.org> | 2007-10-20 00:11:36 +0200 |
commit | 646b1c9dad52f3ab17e4e44b2bb7f24aad956db6 (patch) | |
tree | 6ab256acf85319970f6a45fccda6f8d026cbe4d2 /drivers | |
parent | 30afddadac9b3423912e7729b5dec17d638e415f (diff) |
Documentation: Fix erroneous "dmascc=" documentation
Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
Signed-off-by: Adrian Bunk <bunk@kernel.org>
Diffstat (limited to 'drivers')
-rw-r--r-- | drivers/net/hamradio/Kconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/hamradio/Kconfig b/drivers/net/hamradio/Kconfig index 36d2c7d4f4d..62d5d5cfd6a 100644 --- a/drivers/net/hamradio/Kconfig +++ b/drivers/net/hamradio/Kconfig @@ -64,7 +64,7 @@ config DMASCC dmascc. If you don't pass any parameter to the driver, all possible I/O addresses are probed. This could irritate other devices that are currently not in use. You may specify the list of addresses - to be probed by "dmascc=addr1,addr2,..." (when compiled into the + to be probed by "dmascc.io=addr1,addr2,..." (when compiled into the kernel image) or "io=addr1,addr2,..." (when loaded as a module). The network interfaces will be called dmascc0 and dmascc1 for the board detected first, dmascc2 and dmascc3 for the second one, and so on. |