Thanks Matt.
As a general point would it be possible to find more information about what combinations of module and kernel versions are tested at each release? I understand it is virtually impossible to test every possible combination but we have recently encountered 2 separate issues which indicate that the combinations could not possibly have been tested.
Driver S2.27N2.40 with MC74xx modules and Kernel 4.5.4 on Intel x64
No IP data is ever received by application code and packet socket data is corrupted on receive (ethernet header was present when using SOCK_DGRAM with packet sockets)
This issue was eventually resolved by updating to S2.28N2.44 - but nothing on the release notes would indicate this was likely to resolve the issue. There is a mention of a change to hard_header_len on ethernet mode - but this problem only occurs in raw-ip mode.
Driver s2.28N2.44 with MC74xx and MC73xx with Kernel 3.6.8 on Atmel SAM9
QMIDevice triggers a kernel BUG by ‘scheduling while atomic’ during device registration.
We are still investigating this issue and will raise it separately here and with our supplier.
In both of these instances the fault is very serious and means the combination could not have been tested at all. What kind of support can we get in the future to help avoid these type of issues?
Regards,
Andrew