Sponsored Content
Operating Systems Linux Fedora Is Kernel module is the same as a device driver? Post 302519658 by Corona688 on Wednesday 4th of May 2011 02:39:47 PM
Old 05-04-2011
I don't think looking at the major numbers in a microscope is going to tell you what you want. The whole point of device files is to not have to care about that; they don't have a whole lot to do with what specific driver is being used. They'll tell you broad things about what class of driver, perhaps.

Quote:
Originally Posted by Corona688
The kernel knows what a major+minor number means, but this often just deals with generic input layers like "SCSI disk" -- which these days can mean anything from USB to SATA to PATA, not just actual SCSI. That Linux is now able to treat nearly all disks so identically is mostly a good thing -- device names don't mysteriously change from hda to sda anymore -- but also means it doesn't tell you much about which driver's used.

Try lspci -k, that'll tell you what PCI/AGP/PCIE devices are being claimed by what modules. You can also explore the virtual /sys/ directories to find out more about the devices within.
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Kernel and Device Driver Programming

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

SUNWglmr -- rasctrl environment monitoring driver for i2c or SCSI device driver ?

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

Linux Device Driver: avoid mem copy from/to user/kernel space

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

Get pointer for existing device class (struct class) in Linux kernel module

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
UK(4)							   BSD Kernel Interfaces Manual 						     UK(4)

NAME
uk -- SCSI user-level driver SYNOPSIS
uk* at scsibus? target ? lun ? DESCRIPTION
The uk driver provides support for a process to address devices on the SCSI bus for which there is no configured driver. A SCSI adapter must also be separately configured into the system before this driver makes sense. KERNEL CONFIGURATION
If a count is given, that number of uk devices will be configured into the NetBSD kernel. IOCTLS
The uk driver has no ioctls of its own but rather acts as a medium for the generic scsi(4) ioctls. These are described in <sys/scsiio.h>. FILES
/dev/uk[0-255] unknown SCSI devices. DIAGNOSTICS
All scsi(4) debug ioctls work on uk devices. SEE ALSO
ioctl(2), cd(4), ch(4), scsi(4), sd(4), ss(4), st(4) HISTORY
The uk driver appeared in 386BSD 0.1. BSD
October 11, 1993 BSD
All times are GMT -4. The time now is 01:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy