GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
BUS_CHILD_PNPINFO(9) FreeBSD Kernel Developer's Manual BUS_CHILD_PNPINFO(9)

BUS_CHILD_PNPINFOobtain the plug and play information from a device

#include <sys/param.h>
#include <sys/bus.h>
#include <sys/sbuf.h>

void
BUS_CHILD_PNPINFO(device_t dev, device_t child, struct sbuf *sb);

The () method returns the identifying information about the child device. This information is called the plug and play (pnp) details by some buses. This information is a series of key=value pairs. The string must be formatted as a space-separated list of key=value pairs. Names may only contain alphanumeric characters, underscores ('_') and hyphens ('-'). Values can contain any non-whitespace characters. Values containing whitespace can be quoted with double quotes ('"'). Double quotes and backslashes in quoted values can be escaped with backslashes ('´).

The pnpinfo is defined as a series of characteristics of the child device that are independent of which drivers are attached, but are used to allow drivers to claim a device. Typically, plug and play information encodes who made the device, what the model number is, and some generic details about the device. By convention, only the generic information about the device that's used by drivers on that bus to decide on accepting the device is reported. Other configuration information (such as the cache burst size) needed for the operation of the device, but that doesn't distinguish it broadly from other devices is not reported.

bus(9), device(9)

April 22, 2021 FreeBSD 14.3-RELEASE

Search for    or go to Top of page |  Section 9 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.