Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

driver_attach(9) [centos man page]

DRIVER_ATTACH(9)					   Device drivers infrastructure					  DRIVER_ATTACH(9)

NAME
driver_attach - try to bind driver to devices. SYNOPSIS
int driver_attach(struct device_driver * drv); ARGUMENTS
drv driver. DESCRIPTION
Walk the list of devices that the bus has on it and try to match the driver with each one. If driver_probe_device returns 0 and the dev->driver is set, we've found a compatible pair. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 DRIVER_ATTACH(9)

Check Out this Related Man Page

STRUCT 
DEVICE_DRIVER(9) Device drivers infrastructure STRUCT DEVICE_DRIVER(9) NAME
struct_device_driver - The basic device driver structure SYNOPSIS
struct device_driver { const char * name; struct bus_type * bus; struct module * owner; const char * mod_name; bool suppress_bind_attrs; const struct of_device_id * of_match_table; const struct acpi_device_id * acpi_match_table; int (* probe) (struct device *dev); int (* remove) (struct device *dev); void (* shutdown) (struct device *dev); int (* suspend) (struct device *dev, pm_message_t state); int (* resume) (struct device *dev); const struct attribute_group ** groups; const struct dev_pm_ops * pm; struct driver_private * p; }; MEMBERS
name Name of the device driver. bus The bus which the device of this driver belongs to. owner The module owner. mod_name Used for built-in modules. suppress_bind_attrs Disables bind/unbind via sysfs. of_match_table The open firmware table. acpi_match_table The ACPI match table. probe Called to query the existence of a specific device, whether this driver can work with it, and bind the driver to a specific device. remove Called when the device is removed from the system to unbind a device from this driver. shutdown Called at shut-down time to quiesce the device. suspend Called to put the device to sleep mode. Usually to a low power state. resume Called to bring a device from sleep mode. groups Default attributes that get created by the driver core automatically. pm Power management operations of the device which matched this driver. p Driver core's private data, no one other than the driver core can touch this. DESCRIPTION
The device driver-model tracks all of the drivers known to the system. The main reason for this tracking is to enable the driver core to match up drivers with new devices. Once drivers are known objects within the system, however, a number of other things become possible. Device drivers can export information and configuration variables that are independent of any specific device. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT DEVICE_DRIVER(9)
Man Page

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How do I know which HBA cards' hardware I have (on Solaris 10) ?

Hi, I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine. The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards. Can anyone suggest how to determine my HBA hardware ? Thanks, Ron. ... (3 Replies)
Discussion started by: ronbarak
3 Replies

2. Solaris

How do I know which HBA cards' hardware I have (on Solaris 10) ?

Hi, I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine. The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards. Can anyone suggest how to determine my HBA hardware ? Thanks, Ron. ... (4 Replies)
Discussion started by: ronbarak
4 Replies

3. UNIX for Dummies Questions & Answers

SoundCard.. Again

Hi everyone.I have an Audigy2 ZS sound card. I'm not a guru so don't send me faraway)) Well my card sounds only in front channels... can't setup 5.1. and i can't made a microphone works. PS: A have red this Yuriy Tsibizov (AKA chibis) many time. Here is some system info dmesg Copyright... (0 Replies)
Discussion started by: Levenson
0 Replies

4. BSD

Detecting usb stick in freebsd

I inserted a 8GB usb stick in a number of machine with FreeBSD 7.1, but the medium was not detected: $ dmesg | grep MB usable memory = 4263022592 (4065 MB) avail memory = 4082540544 (3893 MB) pci0: <serial bus, SMBus> at device 31.3 (no driver attached) ad0: 238475MB <WDC WD2500BEVT-00ZCT0... (6 Replies)
Discussion started by: figaro
6 Replies

5. Solaris

Solaris 10, problem with attaching driver

Today I installed Solaris driver for my NIC card (downloaded from OpenSolaris site ) I`m using Solaris 10 x86 based PC ! When I installation was completed I saw a message "Warning driver successfully added to system bad failed to atach " , then i looked at /etc/drivers_aliases and saw... (3 Replies)
Discussion started by: solaris_user
3 Replies

6. IP Networking

ffserver cannot open ffserver.conf file

Hello, I use ffserver & ffmpeg in order to generate a live stream (recorded by a webcam). I use an embedded processor (SH7724), busybox version 2010.09, kernel 2.6.39.3. the command I issue is: ffserver -f /etc/ffserver.conf & ffmpeg -v 2 -r 24 -s 640x480 -loglevel verbose -f video4linux2 -i... (2 Replies)
Discussion started by: avivf
2 Replies

7. Solaris

Attach Solaris 11.1 rwn driver to RaLink RT8200/8260 Wi Fi Adapter

I installed Solaris 11.1 on a X86 PC. It's working except for one glaring problem : I cannot get a driver attached to the RaLink RT2800 (Wi Fi Adapter). Can someone point me in the direction where " the correct" driver exists, or let me know how I can tell Solaris to attach the device to the... (1 Reply)
Discussion started by: JWH
1 Replies