Hi Kars,
Index 1 should have been ZORRO_PROD_PHASE5_CYBERSTORM_MK_II, I've
corrected that in the meantime.
Fastlane / Blizzard 1230_II distinction is something I an not quite
sure about - does the probe function get called twice if the device
table contains the same ID twice but with different driver_data
contents?
Cheers,
Michael
On Mon, Mar 5, 2018 at 9:02 PM, Kars de Jong <jongk@xxxxxxxxxxxxxx> wrote:
> 2018-03-04 0:54 GMT+01:00 Michael Schmitz <schmitzmic@xxxxxxxxx>:
>> +static struct zorro_device_id zorro_esp_zorro_tbl[] = {
>> + {
>> + .id = ZORRO_PROD_PHASE5_BLIZZARD_1220_CYBERSTORM,
>> + .driver_data = (unsigned long)&zorro_esp_driver_data[0],
>> + },
>> + {
>> + .id = ZORRO_PROD_PHASE5_BLIZZARD_1230_II_FASTLANE_Z3_CYBERSCSI_CYBERSTORM060,
>> + .driver_data = (unsigned long)&zorro_esp_driver_data[0],
>> + },
>> + {
>> + .id = ZORRO_PROD_PHASE5_CYBERSTORM_MK_II,
>> + .driver_data = (unsigned long)&zorro_esp_driver_data[1],
>> + },
>> + {
>> + .id = ZORRO_PROD_PHASE5_BLIZZARD_2060,
>> + .driver_data = (unsigned long)&zorro_esp_driver_data[2],
>> + },
>> + {
>> + .id = ZORRO_PROD_PHASE5_BLIZZARD_1230_IV_1260,
>> + .driver_data = (unsigned long)&zorro_esp_driver_data[3],
>> + },
>> + {
>> + .id = ZORRO_PROD_PHASE5_BLIZZARD_1230_II_FASTLANE_Z3_CYBERSCSI_CYBERSTORM060,
>> + .driver_data = (unsigned long)&zorro_esp_driver_data[4],
>> + },
>> + { 0 }
>> +};
>> +MODULE_DEVICE_TABLE(zorro, zorro_esp_zorro_tbl);
>
>
> The ID ZORRO_PROD_PHASE5_BLIZZARD_1230_II_FASTLANE_Z3_CYBERSCSI_CYBERSTORM060
> is used at index 1 and index 5.
> I'm guessing only the first one will be detected.
>
> Regards,
>
> Kars.
