diff options
Diffstat (limited to 'Documentation/pcmcia')
-rw-r--r-- | Documentation/pcmcia/devicetable.txt | 64 | ||||
-rw-r--r-- | Documentation/pcmcia/driver-changes.txt | 51 |
2 files changed, 115 insertions, 0 deletions
diff --git a/Documentation/pcmcia/devicetable.txt b/Documentation/pcmcia/devicetable.txt new file mode 100644 index 000000000000..7225f9eddf9d --- /dev/null +++ b/Documentation/pcmcia/devicetable.txt | |||
@@ -0,0 +1,64 @@ | |||
1 | Matching of PCMCIA devices to drivers is done using one or more of the | ||
2 | following criteria: | ||
3 | |||
4 | - manufactor ID | ||
5 | - card ID | ||
6 | - product ID strings _and_ hashes of these strings | ||
7 | - function ID | ||
8 | - device function (actual and pseudo) | ||
9 | |||
10 | You should use the helpers in include/pcmcia/device_id.h for generating the | ||
11 | struct pcmcia_device_id[] entries which match devices to drivers. | ||
12 | |||
13 | If you want to match product ID strings, you also need to pass the crc32 | ||
14 | hashes of the string to the macro, e.g. if you want to match the product ID | ||
15 | string 1, you need to use | ||
16 | |||
17 | PCMCIA_DEVICE_PROD_ID1("some_string", 0x(hash_of_some_string)), | ||
18 | |||
19 | If the hash is incorrect, the kernel will inform you about this in "dmesg" | ||
20 | upon module initialization, and tell you of the correct hash. | ||
21 | |||
22 | You can determine the hash of the product ID strings by running | ||
23 | "pcmcia-modalias %n.%m" [%n being replaced with the socket number and %m being | ||
24 | replaced with the device function] from pcmciautils. It generates a string | ||
25 | in the following form: | ||
26 | pcmcia:m0149cC1ABf06pfn00fn00pa725B842DpbF1EFEE84pc0877B627pd00000000 | ||
27 | |||
28 | The hex value after "pa" is the hash of product ID string 1, after "pb" for | ||
29 | string 2 and so on. | ||
30 | |||
31 | Alternatively, you can use this small tool to determine the crc32 hash. | ||
32 | simply pass the string you want to evaluate as argument to this program, | ||
33 | e.g. | ||
34 | $ ./crc32hash "Dual Speed" | ||
35 | |||
36 | ------------------------------------------------------------------------- | ||
37 | /* crc32hash.c - derived from linux/lib/crc32.c, GNU GPL v2 */ | ||
38 | #include <string.h> | ||
39 | #include <stdio.h> | ||
40 | #include <ctype.h> | ||
41 | #include <stdlib.h> | ||
42 | |||
43 | unsigned int crc32(unsigned char const *p, unsigned int len) | ||
44 | { | ||
45 | int i; | ||
46 | unsigned int crc = 0; | ||
47 | while (len--) | ||
48 | crc ^= *p++; | ||
49 | for (i = 0; i < 8; i++) | ||
50 | crc = (crc >> 1) ^ ((crc & 1) ? 0xedb88320 : 0); | ||
51 | } | ||
52 | return crc; | ||
53 | } | ||
54 | |||
55 | int main(int argc, char **argv) { | ||
56 | unsigned int result; | ||
57 | if (argc != 2) { | ||
58 | printf("no string passed as argument\n"); | ||
59 | return -1; | ||
60 | } | ||
61 | result = crc32(argv[1], strlen(argv[1])); | ||
62 | printf("0x%x\n", result); | ||
63 | return 0; | ||
64 | } | ||
diff --git a/Documentation/pcmcia/driver-changes.txt b/Documentation/pcmcia/driver-changes.txt new file mode 100644 index 000000000000..9c315ab48a02 --- /dev/null +++ b/Documentation/pcmcia/driver-changes.txt | |||
@@ -0,0 +1,51 @@ | |||
1 | This file details changes in 2.6 which affect PCMCIA card driver authors: | ||
2 | |||
3 | * in-kernel device<->driver matching | ||
4 | PCMCIA devices and their correct drivers can now be matched in | ||
5 | kernelspace. See 'devicetable.txt' for details. | ||
6 | |||
7 | * Device model integration (as of 2.6.11) | ||
8 | A struct pcmcia_device is registered with the device model core, | ||
9 | and can be used (e.g. for SET_NETDEV_DEV) by using | ||
10 | handle_to_dev(client_handle_t * handle). | ||
11 | |||
12 | * Convert internal I/O port addresses to unsigned long (as of 2.6.11) | ||
13 | ioaddr_t should be replaced by kio_addr_t in PCMCIA card drivers. | ||
14 | |||
15 | * irq_mask and irq_list parameters (as of 2.6.11) | ||
16 | The irq_mask and irq_list parameters should no longer be used in | ||
17 | PCMCIA card drivers. Instead, it is the job of the PCMCIA core to | ||
18 | determine which IRQ should be used. Therefore, link->irq.IRQInfo2 | ||
19 | is ignored. | ||
20 | |||
21 | * client->PendingEvents is gone (as of 2.6.11) | ||
22 | client->PendingEvents is no longer available. | ||
23 | |||
24 | * client->Attributes are gone (as of 2.6.11) | ||
25 | client->Attributes is unused, therefore it is removed from all | ||
26 | PCMCIA card drivers | ||
27 | |||
28 | * core functions no longer available (as of 2.6.11) | ||
29 | The following functions have been removed from the kernel source | ||
30 | because they are unused by all in-kernel drivers, and no external | ||
31 | driver was reported to rely on them: | ||
32 | pcmcia_get_first_region() | ||
33 | pcmcia_get_next_region() | ||
34 | pcmcia_modify_window() | ||
35 | pcmcia_set_event_mask() | ||
36 | pcmcia_get_first_window() | ||
37 | pcmcia_get_next_window() | ||
38 | |||
39 | * device list iteration upon module removal (as of 2.6.10) | ||
40 | It is no longer necessary to iterate on the driver's internal | ||
41 | client list and call the ->detach() function upon module removal. | ||
42 | |||
43 | * Resource management. (as of 2.6.8) | ||
44 | Although the PCMCIA subsystem will allocate resources for cards, | ||
45 | it no longer marks these resources busy. This means that driver | ||
46 | authors are now responsible for claiming your resources as per | ||
47 | other drivers in Linux. You should use request_region() to mark | ||
48 | your IO regions in-use, and request_mem_region() to mark your | ||
49 | memory regions in-use. The name argument should be a pointer to | ||
50 | your driver name. Eg, for pcnet_cs, name should point to the | ||
51 | string "pcnet_cs". | ||