Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) ============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) Device table
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) ============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) Matching of PCMCIA devices to drivers is done using one or more of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) following criteria:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) - manufactor ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) - card ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) - product ID strings _and_ hashes of these strings
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) - function ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) - device function (actual and pseudo)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) You should use the helpers in include/pcmcia/device_id.h for generating the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) struct pcmcia_device_id[] entries which match devices to drivers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) If you want to match product ID strings, you also need to pass the crc32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) hashes of the string to the macro, e.g. if you want to match the product ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) string 1, you need to use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) PCMCIA_DEVICE_PROD_ID1("some_string", 0x(hash_of_some_string)),
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) If the hash is incorrect, the kernel will inform you about this in "dmesg"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) upon module initialization, and tell you of the correct hash.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) You can determine the hash of the product ID strings by catting the file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) "modalias" in the sysfs directory of the PCMCIA device. It generates a string
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) in the following form:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) pcmcia:m0149cC1ABf06pfn00fn00pa725B842DpbF1EFEE84pc0877B627pd00000000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) The hex value after "pa" is the hash of product ID string 1, after "pb" for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) string 2 and so on.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) Alternatively, you can use crc32hash (see tools/pcmcia/crc32hash.c)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) to determine the crc32 hash.  Simply pass the string you want to evaluate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) as argument to this program, e.g.:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) $ tools/pcmcia/crc32hash "Dual Speed"