blob: fd1d60d12ca186f1dcdf5cd6d0c77d7e36b0281f [file] [log] [blame]
Mauro Carvalho Chehab3bdab162019-06-12 14:52:53 -03001============
2Device table
3============
4
Dominik Brodowski5085cb22005-06-27 16:28:45 -07005Matching of PCMCIA devices to drivers is done using one or more of the
6following criteria:
7
8- manufactor ID
9- card ID
10- product ID strings _and_ hashes of these strings
11- function ID
12- device function (actual and pseudo)
13
14You should use the helpers in include/pcmcia/device_id.h for generating the
15struct pcmcia_device_id[] entries which match devices to drivers.
16
17If you want to match product ID strings, you also need to pass the crc32
18hashes of the string to the macro, e.g. if you want to match the product ID
19string 1, you need to use
20
21PCMCIA_DEVICE_PROD_ID1("some_string", 0x(hash_of_some_string)),
22
23If the hash is incorrect, the kernel will inform you about this in "dmesg"
24upon module initialization, and tell you of the correct hash.
25
Dominik Brodowskieb05bfe2005-06-30 02:58:47 -070026You can determine the hash of the product ID strings by catting the file
27"modalias" in the sysfs directory of the PCMCIA device. It generates a string
Dominik Brodowski5085cb22005-06-27 16:28:45 -070028in the following form:
29pcmcia:m0149cC1ABf06pfn00fn00pa725B842DpbF1EFEE84pc0877B627pd00000000
30
31The hex value after "pa" is the hash of product ID string 1, after "pb" for
32string 2 and so on.
33
Shuah Khana67cd542016-09-21 16:54:36 -060034Alternatively, you can use crc32hash (see tools/pcmcia/crc32hash.c)
Randy Dunlapd29693b2006-05-21 20:57:42 -070035to determine the crc32 hash. Simply pass the string you want to evaluate
36as argument to this program, e.g.:
Shuah Khana67cd542016-09-21 16:54:36 -060037$ tools/pcmcia/crc32hash "Dual Speed"