view Documentation/pcmcia/devicetable.txt @ 524:7f8b544237bf

netfront: Allow netfront in domain 0.

This is useful if your physical network device is in a utility domain.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
author Keir Fraser <keir.fraser@citrix.com>
date Tue Apr 15 15:18:58 2008 +0100 (2008-04-15)
parents 831230e53067
line source
1 Matching of PCMCIA devices to drivers is done using one or more of the
2 following criteria:
4 - manufactor ID
5 - card ID
6 - product ID strings _and_ hashes of these strings
7 - function ID
8 - device function (actual and pseudo)
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.
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
17 PCMCIA_DEVICE_PROD_ID1("some_string", 0x(hash_of_some_string)),
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.
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
24 in the following form:
25 pcmcia:m0149cC1ABf06pfn00fn00pa725B842DpbF1EFEE84pc0877B627pd00000000
27 The hex value after "pa" is the hash of product ID string 1, after "pb" for
28 string 2 and so on.
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.:
33 $ ./crc32hash "Dual Speed"