05-03-2011
lsmod shows which modules are using what other modules, though not as a tree.
It's not always as simple as one module for one device. USB needs a whole bunch of modules to do anything, plus sometimes device-specific things on top of the generic drivers -- but then again, sometimes the generic ones are enough. Sound also takes a bunch of interdependent modules to work.
There's also modules that don't do anything device-related -- like a module to let the kernel understand ext4 filesystems.
So it's really not the same thing, but often close enough for most purposes.
These modules can also be built right into the kernel, instead of being loaded from a file, too. It's possible to create a kernel that loads no modules for anything, ever. You can even build parts of a set of modules into the kernel and leave part of it out. This is sometimes important for things like ALSA, where you might want to replace some modules with updated ones later, but need certain basic parts built in.
This User Gave Thanks to Corona688 For This Post:
4 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am looking for a guide on how to program for either the Linux or FreeBSD (includes 4.4BSD, NetBSD or OpenBSD) kernel. I would prefer to learn how to write device drivers, but anything would help.
If you know, please email me at *removed* or leave a post here
Regards,
Farhan (0 Replies)
Discussion started by: Farhan
0 Replies
2. Solaris
I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr
is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies
3. Linux
I recently started working with Linux and wrote my first device driver for a hardware chip controlled by a host CPU running Linux 2.6.x kernel.
1. The user space process makes an IOCTL call with pointer to a user memory buffer.
2. The kernel device driver in the big switch-case of IOCTL,... (1 Reply)
Discussion started by: agaurav
1 Replies
4. UNIX for Advanced & Expert Users
Hi all!
I am trying to register a device in an existing device class, but I am
having trouble getting the pointer to an existing class.
I can create a class in a module, get the pointer to it and then use
it to register the device with:
*cl = class_create(THIS_MODULE, className);... (0 Replies)
Discussion started by: hdaniel@ualg.pt
0 Replies
IPWFW(4) BSD Kernel Interfaces Manual IPWFW(4)
NAME
ipwfw -- Firmware Module for Intel PRO/Wireless 2100 driver
SYNOPSIS
To compile this module into the kernel, place the following line in your kernel configuration file:
device ipwfw
This will include three firmware images inside the kernel. If you want to pick only the firmware image for the mode you want to operate your
network adapter in choose one of the following:
device ipwbssfw
device ipwibssfw
device ipwmonitorfw
Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5):
ipw_bss_load="YES"
ipw_ibss_load="YES"
ipw_monitor_load="YES"
DESCRIPTION
This module provides access to firmware sets for the Intel PRO/Wireless 2100 series of IEEE 802.11 adapters. It may be statically linked
into the kernel, or loaded as a module.
For the loaded firmware to be enabled for use the license at /usr/share/doc/legal/intel_ipw/LICENSE must be agreed to by adding the following
line to loader.conf(5):
legal.intel_ipw.license_ack=1
FILES
/usr/share/doc/legal/intel_ipw/LICENSE ipwfw firmware license
SEE ALSO
ipw(4), firmware(9)
BSD
January 14, 2010 BSD