| Dominik Brodowski | 5085cb2 | 2005-06-27 16:28:45 -0700 | [diff] [blame] | 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 |  | 
| Dominik Brodowski | eb05bfe | 2005-06-30 02:58:47 -0700 | [diff] [blame] | 22 | You can determine the hash of the product ID strings by catting the file | 
 | 23 | "modalias" in the sysfs directory of the PCMCIA device. It generates a string | 
| Dominik Brodowski | 5085cb2 | 2005-06-27 16:28:45 -0700 | [diff] [blame] | 24 | in the following form: | 
 | 25 | pcmcia:m0149cC1ABf06pfn00fn00pa725B842DpbF1EFEE84pc0877B627pd00000000 | 
 | 26 |  | 
 | 27 | The hex value after "pa" is the hash of product ID string 1, after "pb" for | 
 | 28 | string 2 and so on. | 
 | 29 |  | 
| Randy Dunlap | d29693b | 2006-05-21 20:57:42 -0700 | [diff] [blame] | 30 | Alternatively, you can use crc32hash (see Documentation/pcmcia/crc32hash.c) | 
 | 31 | to determine the crc32 hash.  Simply pass the string you want to evaluate | 
 | 32 | as argument to this program, e.g.: | 
| Dominik Brodowski | 5085cb2 | 2005-06-27 16:28:45 -0700 | [diff] [blame] | 33 | $ ./crc32hash "Dual Speed" |