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:
Code:
#define MEM_MAJOR 1
#define RAMDISK_MAJOR 1
is an excerpt from that header file and we have
Code:
$ ls -l /dev | awk '$5 == "1,"' | sort -k1.1,1.1 -k6
brw-r----- 1 root disk 1, 0 Jan 17 10:38 ram0
brw-r----- 1 root disk 1, 1 Jan 17 10:38 ram1
brw-r----- 1 root disk 1, 2 Jan 17 10:38 ram2
brw-r----- 1 root disk 1, 3 Jan 17 10:38 ram3
brw-r----- 1 root disk 1, 4 Jan 17 10:38 ram4
brw-r----- 1 root disk 1, 5 Jan 17 10:38 ram5
brw-r----- 1 root disk 1, 6 Jan 17 10:38 ram6
brw-r----- 1 root disk 1, 7 Jan 17 10:38 ram7
brw-r----- 1 root disk 1, 8 Jan 17 10:38 ram8
brw-r----- 1 root disk 1, 9 Jan 17 10:38 ram9
brw-r----- 1 root disk 1, 10 Jan 17 10:38 ram10
brw-r----- 1 root disk 1, 11 Jan 17 10:38 ram11
brw-r----- 1 root disk 1, 12 Jan 17 10:38 ram12
brw-r----- 1 root disk 1, 13 Jan 17 10:38 ram13
brw-r----- 1 root disk 1, 14 Jan 17 10:38 ram14
brw-r----- 1 root disk 1, 15 Jan 17 10:38 ram15
crw-r----- 1 root kmem 1, 1 Jan 17 15:38 mem
crw-rw-rw- 1 root root 1, 3 Jan 17 15:38 null
crw-r----- 1 root kmem 1, 4 Jan 17 15:38 port
crw-rw-rw- 1 root root 1, 5 Jan 17 15:38 zero
crw-rw-rw- 1 root root 1, 7 Jan 17 15:38 full
crw-rw-rw- 1 root root 1, 8 Jan 17 15:38 random
cr--r--r-- 1 root root 1, 9 Jan 17 15:38 urandom
crw------- 1 root root 1, 11 Jan 17 15:38 kmsg
crw------- 1 root root 1, 12 Jan 17 15:38 oldmem
$
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
sbp_targ
SBP_TARG(4) BSD Kernel Interfaces Manual SBP_TARG(4)NAME
sbp_targ -- Serial Bus Protocol 2 (SBP-2) Target Mode devices driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device sbp_targ
device firewire
device scbus
device targ
Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5):
firewire_load="YES"
cam_load="YES"
sbp_targ_load"YES"
DESCRIPTION
The sbp_targ driver provides support for SBP-2 target mode. This driver is supposed to work with cam(4), targ(4) and firewire(4). You also
need to use scsi_target(8), which can be found in /usr/share/examples/scsi_target, to provide actual devices.
EXAMPLES
# mdconfig -a -t malloc -s 10m
md0
# scsi_target 0:0:0 /dev/md0
(Assuming sbp_targ0 on scbus0)
SEE ALSO cam(4), firewire(4), targ(4), camcontrol(8), fwcontrol(8), kldload(8), scsi_target(8)AUTHORS
The sbp_targ driver was written by Hidetoshi Shimokawa.
BUGS
This driver is currently under development. It does not work correctly in multi-initiator environments or after the bus topology has been
changed.
BSD November 7, 2003 BSD
05-03-2011
