git://ftp.safe.ca
/
safe
/
jmp
/
linux-2.6
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Merge branch 'perf/urgent' into perf/core
[safe/jmp/linux-2.6]
/
Documentation
/
pnp.txt
diff --git
a/Documentation/pnp.txt
b/Documentation/pnp.txt
index
af0f6ea
..
763e465
100644
(file)
--- a/
Documentation/pnp.txt
+++ b/
Documentation/pnp.txt
@@
-17,9
+17,9
@@
The User Interface
------------------
The Linux Plug and Play user interface provides a means to activate PnP devices
for legacy and user level drivers that do not support Linux Plug and Play. The
------------------
The Linux Plug and Play user interface provides a means to activate PnP devices
for legacy and user level drivers that do not support Linux Plug and Play. The
-user interface is integrated into
driver
fs.
+user interface is integrated into
sys
fs.
-In addition to the standard
driverfs file the following are created in each
+In addition to the standard
sysfs file the following are created in each
device's directory:
id - displays a list of support EISA IDs
options - displays possible resource configurations
device's directory:
id - displays a list of support EISA IDs
options - displays possible resource configurations
@@
-57,7
+57,7
@@
PC standard floppy disk controller
# cat resources
DISABLED
# cat resources
DISABLED
-- Notice the string "DISABLED". T
H
is means the device is not active.
+- Notice the string "DISABLED". T
h
is means the device is not active.
3.) check the device's possible configurations (optional)
# cat options
3.) check the device's possible configurations (optional)
# cat options
@@
-115,6
+115,9
@@
pnp_unregister_protocol
pnp_register_driver
- adds a PnP driver to the Plug and Play Layer
- this includes driver model integration
pnp_register_driver
- adds a PnP driver to the Plug and Play Layer
- this includes driver model integration
+- returns zero for success or a negative error number for failure; count
+ calls to the .add() method if you need to know how many devices bind to
+ the driver
pnp_unregister_driver
- removes a PnP driver from the Plug and Play Layer
pnp_unregister_driver
- removes a PnP driver from the Plug and Play Layer
@@
-136,8
+139,8
@@
Plug and Play but it is planned to be in the near future.
Requirements for a Linux PnP protocol:
1.) the protocol must use EISA IDs
Requirements for a Linux PnP protocol:
1.) the protocol must use EISA IDs
-2.) the protocol must inform the PnP Layer of a devices current configuration
-- the ability to set resources is optional but prefered.
+2.) the protocol must inform the PnP Layer of a device
'
s current configuration
+- the ability to set resources is optional but prefer
r
ed.
The following are PnP protocol related functions:
The following are PnP protocol related functions:
@@
-155,7
+158,7
@@
pnp_remove_device
- automatically will free mem used by the device and related structures
pnp_add_id
- automatically will free mem used by the device and related structures
pnp_add_id
-- adds a EISA ID to the list of supported IDs for the specified device
+- adds a
n
EISA ID to the list of supported IDs for the specified device
For more information consult the source of a protocol such as
/drivers/pnp/pnpbios/core.c.
For more information consult the source of a protocol such as
/drivers/pnp/pnpbios/core.c.
@@
-164,7
+167,7
@@
For more information consult the source of a protocol such as
Linux Plug and Play Drivers
---------------------------
Linux Plug and Play Drivers
---------------------------
- This section contains information for
l
inux PnP driver developers.
+ This section contains information for
L
inux PnP driver developers.
The New Way
...........
The New Way
...........
@@
-181,7
+184,7
@@
static const struct pnp_id pnp_dev_table[] = {
Please note that the character 'X' can be used as a wild card in the function
portion (last four characters).
ex:
Please note that the character 'X' can be used as a wild card in the function
portion (last four characters).
ex:
- /* Unkown PnP modems */
+ /* Unk
n
own PnP modems */
{ "PNPCXXX", UNKNOWN_DEV },
Supported PnP card IDs can optionally be defined.
{ "PNPCXXX", UNKNOWN_DEV },
Supported PnP card IDs can optionally be defined.
@@
-219,7
+222,7
@@
static struct pnp_driver serial_pnp_driver = {
.remove = serial_pnp_remove,
};
.remove = serial_pnp_remove,
};
-* name and id_table can
not be NULL.
+* name and id_table cannot be NULL.
4.) register the driver
ex:
4.) register the driver
ex:
@@
-232,11
+235,10
@@
static int __init serial8250_pnp_init(void)
The Old Way
...........
The Old Way
...........
-a series of compatibility functions have been created to make it easy to convert
-
+A series of compatibility functions have been created to make it easy to convert
ISAPNP drivers. They should serve as a temporary solution only.
ISAPNP drivers. They should serve as a temporary solution only.
-
t
hey are as follows:
+
T
hey are as follows:
struct pnp_card *pnp_find_card(unsigned short vendor,
unsigned short device,
struct pnp_card *pnp_find_card(unsigned short vendor,
unsigned short device,