Changes between Initial Version and Version 2 of Ticket #730


Ignore:
Timestamp:
2018-05-25T20:55:30Z (7 years ago)
Author:
Jakub Jermář
Comment:

Remove the solved match ID issue from description.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #730 – Description

    initial v2  
    1 The driver won't bind because it's got 0x0cf3 as vendor ID in its .ma file, but the match for the bust contains 0xcf3.
    2 
    3 After fixing that the driver crashes with assertion failure upon loading. Apparently there are two attempts at calling ddf_dev_data_alloc(). The immediate cause seems to be because the driver is calling usb_device_create_ddf(). I'm not sure whether this is incorrect or obsolete..
     1The driver crashes with assertion failure upon loading. Apparently there are two attempts at calling ddf_dev_data_alloc(). The immediate cause seems to be because the driver is calling usb_device_create_ddf(). I'm not sure whether this is incorrect or obsolete..
    42
    53In any case I am not sure how usb+nic driver could have ever worked: libnic allocates and uses dev data (which it absolutely should not do since it's a top-half framework). If USB does the same...