05-05-2011
In a course of reading, watching DVDs and browsing it, I'm gradually start getting it. You see I'm used to windows ways... However how do you guys troubleshoot devices if there's no clear indication which driver does what? Let say I have some webcam or sound card, and how I can get the indication that driver for it is installed, and works properly? Or in a case it is installed but conflict with other driver over resources, how it can be determined? All with "lspci" ? You see in windows I have a chain to follow. I can't see this chain as clearly here so far. I realize that I'm newbie, but in windows information is readily available, and here I have to dig it out every piece by piece.
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
DEVICE(9) BSD Kernel Developer's Manual DEVICE(9)
NAME
device -- an abstract representation of a device
SYNOPSIS
typedef struct device *device_t;
DESCRIPTION
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into,
disk drives attached to the expansion card etc. The system defines one device, root_bus and all other devices are created dynamically during
autoconfiguration. Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and
other devices will be added as children of their relevant bus.
The devices in a system form a tree. All devices except root_bus have a parent (see device_get_parent(9)). In addition, any device can have
children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and
device_delete_child(9)).
A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a
devclass (see device_get_devclass(9) and devclass(9)). Various other attributes of the device include a unit number (see
device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe-
cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)).
Devices can be in one of several states:
DS_NOTPRESENT the device has not been probed for existence or the probe failed
DS_ALIVE the device probe succeeded but not yet attached
DS_ATTACHED the device has been successfully attached
DS_BUSY the device is currently open
The current state of the device can be determined by calling device_get_state(9).
SEE ALSO
devclass(9), driver(9)
AUTHORS
This manual page was written by Doug Rabson.
BSD
June 16, 1998 BSD