devicetable.rst 1.3 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. ============
  2. Device table
  3. ============
  4. Matching of PCMCIA devices to drivers is done using one or more of the
  5. following criteria:
  6. - manufactor ID
  7. - card ID
  8. - product ID strings _and_ hashes of these strings
  9. - function ID
  10. - device function (actual and pseudo)
  11. You should use the helpers in include/pcmcia/device_id.h for generating the
  12. 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
  16. PCMCIA_DEVICE_PROD_ID1("some_string", 0x(hash_of_some_string)),
  17. If the hash is incorrect, the kernel will inform you about this in "dmesg"
  18. upon module initialization, and tell you of the correct hash.
  19. You can determine the hash of the product ID strings by catting the file
  20. "modalias" in the sysfs directory of the PCMCIA device. It generates a string
  21. in the following form:
  22. pcmcia:m0149cC1ABf06pfn00fn00pa725B842DpbF1EFEE84pc0877B627pd00000000
  23. The hex value after "pa" is the hash of product ID string 1, after "pb" for
  24. string 2 and so on.
  25. Alternatively, you can use crc32hash (see tools/pcmcia/crc32hash.c)
  26. to determine the crc32 hash. Simply pass the string you want to evaluate
  27. as argument to this program, e.g.:
  28. $ tools/pcmcia/crc32hash "Dual Speed"