On RedHat at least we have /usr/include/linux/major.h which documents which major number goes with which driver. And remember that there are character drivers and block drivers and one of each can use the same major number. By convention, when this happens the two drivers should be closely related. For example:
is an excerpt from that header file and we have
The major number just tells the kernel which driver to invoke. The driver is the part of the kernel that understands its own minor numbers. But there are conventions here too.
Not all driver writers completely follow conventions.
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)
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)
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)
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
LEARN ABOUT DEBIAN
multi_driver_module
DRIVER_MODULE(9) BSD Kernel Developer's Manual DRIVER_MODULE(9)NAME
DRIVER_MODULE -- kernel driver declaration macro
SYNOPSIS
#include <sys/param.h>
#include <sys/kernel.h>
#include <sys/bus.h>
#include <sys/module.h>
DRIVER_MODULE(name, busname, driver_t driver, devclass_t devclass, modeventhand_t evh, void *arg);
MULTI_DRIVER_MODULE(name, busname, driver_t drivers[], devclass_t devclass, modeventhand_t evh, void *arg);
DESCRIPTION
The DRIVER_MODULE() macro declares a kernel driver. DRIVER_MODULE() expands to the real driver declaration, where the phrase name is used as
the naming prefix for the driver and its functions. Note that it is supplied as plain text, and not a char or char *.
busname is the parent bus of the driver (PCI, ISA, PPBUS and others), e.g. 'pci', 'isa', or 'ppbus'.
The identifier used in DRIVER_MODULE() can be different from the driver name. Also, the same driver identifier can exist on different
busses, which is a pretty clean way of making front ends for different cards using the same driver on the same or different busses. For
example, the following is allowed:
DRIVER_MODULE(foo, isa, foo_driver, foo_devclass, NULL, NULL);
DRIVER_MODULE(foo, pci, foo_driver, foo_devclass, NULL, NULL);
driver is the driver of type driver_t, which contains the information about the driver and is therefore one of the two most important parts
of the call to DRIVER_MODULE().
The devclass argument contains the kernel-internal information about the device, which will be used within the kernel driver module.
The evh argument is the event handler which is called when the driver (or module) is loaded or unloaded (see module(9)).
The arg is unused at this time and should be a NULL pointer.
MULTI_DRIVER_MODULE() is a special version of DRIVER_MODULE(), which takes a list of drivers instead of a single driver instance.
SEE ALSO device(9), driver(9), module(9)AUTHORS
This manual page was written by Alexander Langer <alex@FreeBSD.org>.
BSD May 16, 2000 BSD