05-03-2011
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
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 DEBIAN
readdvd
readdvd(1) readdvd 1.0 readdvd(1)
NAME
readdvd - is creating an image of your source dvd media or medias even if it has / they have corrupted blocks
SYNOPSIS
readdvd [-l] [-h]
readdvd -d DEVICE1 [-d DEVICE2] [-d ...] -o file.iso [-s #] [-v] [-vv]
DESCRIPTION
readdvd reads even a corrupted dvd and writes the the result into a new image file on your harddisk.
DEVICE
can be an IDE, SCSI, SATA, USB or FireWire connected optical drive. Not all SATA controller support all Plextor features.
Linux:
/dev/hdX: IDE device
/dev/scdX: Linux 2.4: SATA, SCSI, USB device, or IDE device via ide-scsi emulation
/dev/srX: Linux 2.6: IDE device via new ATA layer, SCSI or USB device
OpenBSD/NetBSD:
/dev/rcdX
FreeBSD:
/dev/cd: SCSI device
/dev/acd: ATA device
MacOS X:
/dev/disk:
win32:
C:,D:,E:, ... X:,Y:,Z:
OPTIONS
-l scan busses for all available CD and DVD devices
-h help shows available options.
-o file.iso
write data to imagefile named file.iso
-s # read source media with selected speed
-v use verbose mode
-vv use extended verbose mode
INTERACTIVE MODUS
q stop reading media and exit
w save sector map which is currently read and continue with the next one
EXAMPLES
readdvd -d /dev/sr0 -o filename.iso -s 8 -v
create an image filename.bin of inserted media in device /dev/sr0 with read speed 8 in verbose mode.
please report man page improvements to T.Maguin@web.de
Gennady ShultZ Kozlov 10. April, 2009 readdvd(1)