05-03-2011
Corona688, thanks for the clarification. Please correct me if I'm wrong.
Below are my assumptions:
user process->kernel->major device number(the driver)->minor device number->device
Let say I have device X and I want to know what driver(s) it uses (because it makes problems, or just out of curiosity). So how can it be done? It is really easy in Windows.
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
LEARN ABOUT OPENSOLARIS
mknod
mknod(1M) System Administration Commands mknod(1M)
NAME
mknod - make a special file
SYNOPSIS
mknod name b major minor
mknod name c major minor
mknod name p
DESCRIPTION
mknod makes a directory entry for a special file.
OPTIONS
The following options are supported:
b Create a block-type special file.
c Create a character-type special file.
p Create a FIFO (named pipe).
OPERANDS
The following operands are supported:
major The major device number.
minor The minor device number; can be either decimal or octal. The assignment of major device numbers is specific to each system. You
must be the super-user to use this form of the command.
name A special file to be created.
USAGE
See largefile(5) for the description of the behavior of mknod when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
ftp(1), in.ftpd(1M), mknod(2), symlink(2), attributes(5), largefile(5)
NOTES
If mknod(2) is used to create a device, the major and minor device numbers are always interpreted by the kernel running on that machine.
With the advent of physical device naming, it would be preferable to create a symbolic link to the physical name of the device (in the
/devices subtree) rather than using mknod.
SunOS 5.11 16 Sep 1996 mknod(1M)