mirror of
https://github.com/adulau/aha.git
synced 2024-12-27 03:06:10 +00:00
remove mention of CONFIG_KMOD from documentation
Also includes a few Kconfig files (xtensa, blackfin) Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Cc: linux-doc@vger.kernel.org Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
This commit is contained in:
parent
baabaae981
commit
a81792f668
6 changed files with 13 additions and 23 deletions
|
@ -26,11 +26,11 @@ You can simplify mounting by just typing:
|
||||||
|
|
||||||
this will allocate the first available loopback device (and load loop.o
|
this will allocate the first available loopback device (and load loop.o
|
||||||
kernel module if necessary) automatically. If the loopback driver is not
|
kernel module if necessary) automatically. If the loopback driver is not
|
||||||
loaded automatically, make sure that your kernel is compiled with kmod
|
loaded automatically, make sure that you have compiled the module and
|
||||||
support (CONFIG_KMOD) enabled. Beware that umount will not
|
that modprobe is functioning. Beware that umount will not deallocate
|
||||||
deallocate /dev/loopN device if /etc/mtab file on your system is a
|
/dev/loopN device if /etc/mtab file on your system is a symbolic link to
|
||||||
symbolic link to /proc/mounts. You will need to do it manually using
|
/proc/mounts. You will need to do it manually using "-d" switch of
|
||||||
"-d" switch of losetup(8). Read losetup(8) manpage for more info.
|
losetup(8). Read losetup(8) manpage for more info.
|
||||||
|
|
||||||
To create the BFS image under UnixWare you need to find out first which
|
To create the BFS image under UnixWare you need to find out first which
|
||||||
slice contains it. The command prtvtoc(1M) is your friend:
|
slice contains it. The command prtvtoc(1M) is your friend:
|
||||||
|
|
|
@ -42,7 +42,7 @@
|
||||||
<sect1><title>Device Components</title>
|
<sect1><title>Device Components</title>
|
||||||
!Esound/core/device.c
|
!Esound/core/device.c
|
||||||
</sect1>
|
</sect1>
|
||||||
<sect1><title>KMOD and Device File Entries</title>
|
<sect1><title>Module requests and Device File Entries</title>
|
||||||
!Esound/core/sound.c
|
!Esound/core/sound.c
|
||||||
</sect1>
|
</sect1>
|
||||||
<sect1><title>Memory Management Helpers</title>
|
<sect1><title>Memory Management Helpers</title>
|
||||||
|
|
|
@ -305,21 +305,14 @@ driver, like this:
|
||||||
|
|
||||||
which will result in the needed drivers getting loaded automatically.
|
which will result in the needed drivers getting loaded automatically.
|
||||||
|
|
||||||
g. if you are planning on using kerneld to automatically load the
|
g. if you are planning on having the kernel automatically request
|
||||||
module for you, then you need to edit /etc/conf.modules and add the
|
the module for you, then you need to edit /etc/conf.modules and add the
|
||||||
following lines:
|
following lines:
|
||||||
|
|
||||||
options ixj dspio=0x340 xio=0x330 ixjdebug=0
|
options ixj dspio=0x340 xio=0x330 ixjdebug=0
|
||||||
|
|
||||||
If you do this, then when you execute an application that uses the
|
If you do this, then when you execute an application that uses the
|
||||||
module kerneld will load the module for you. Note that to do this,
|
module the kernel will request that it is loaded.
|
||||||
you need to have your kernel set to support kerneld. You can check
|
|
||||||
for this by looking at /usr/src/linux/.config and you should see this:
|
|
||||||
|
|
||||||
# Loadable module support
|
|
||||||
#
|
|
||||||
<snip>
|
|
||||||
CONFIG_KMOD=y
|
|
||||||
|
|
||||||
h. if you want non-root users to be able to read and write to the
|
h. if you want non-root users to be able to read and write to the
|
||||||
ixj devices (this is a good idea!) you should do the following:
|
ixj devices (this is a good idea!) you should do the following:
|
||||||
|
|
|
@ -193,9 +193,6 @@ Description: Automatic 'ovcamchip' module loading: 0 disabled, 1 enabled.
|
||||||
loads that module automatically. This action is performed as
|
loads that module automatically. This action is performed as
|
||||||
once soon as the 'w9968cf' module is loaded into memory.
|
once soon as the 'w9968cf' module is loaded into memory.
|
||||||
Default: 1
|
Default: 1
|
||||||
Note: The kernel must be compiled with the CONFIG_KMOD option
|
|
||||||
enabled for the 'ovcamchip' module to be loaded and for
|
|
||||||
this parameter to be present.
|
|
||||||
-------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------
|
||||||
Name: simcams
|
Name: simcams
|
||||||
Type: int
|
Type: int
|
||||||
|
|
|
@ -873,8 +873,8 @@ config HOTPLUG
|
||||||
plugged into slots found on all modern laptop computers. Another
|
plugged into slots found on all modern laptop computers. Another
|
||||||
example, used on modern desktops as well as laptops, is USB.
|
example, used on modern desktops as well as laptops, is USB.
|
||||||
|
|
||||||
Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
|
Enable HOTPLUG and build a modular kernel. Get agent software
|
||||||
software (at <http://linux-hotplug.sourceforge.net/>) and install it.
|
(from <http://linux-hotplug.sourceforge.net/>) and install it.
|
||||||
Then your kernel will automatically call out to a user mode "policy
|
Then your kernel will automatically call out to a user mode "policy
|
||||||
agent" (/sbin/hotplug) to load modules and set up software needed
|
agent" (/sbin/hotplug) to load modules and set up software needed
|
||||||
to use devices as you hotplug them.
|
to use devices as you hotplug them.
|
||||||
|
|
|
@ -194,8 +194,8 @@ config HOTPLUG
|
||||||
plugged into slots found on all modern laptop computers. Another
|
plugged into slots found on all modern laptop computers. Another
|
||||||
example, used on modern desktops as well as laptops, is USB.
|
example, used on modern desktops as well as laptops, is USB.
|
||||||
|
|
||||||
Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
|
Enable HOTPLUG and build a modular kernel. Get agent software
|
||||||
software (at <http://linux-hotplug.sourceforge.net/>) and install it.
|
(from <http://linux-hotplug.sourceforge.net/>) and install it.
|
||||||
Then your kernel will automatically call out to a user mode "policy
|
Then your kernel will automatically call out to a user mode "policy
|
||||||
agent" (/sbin/hotplug) to load modules and set up software needed
|
agent" (/sbin/hotplug) to load modules and set up software needed
|
||||||
to use devices as you hotplug them.
|
to use devices as you hotplug them.
|
||||||
|
|
Loading…
Reference in a new issue