Hi David, > > > > +-----+-----+-----+-----+----------+---------------+---------------+------------+--- > -----+------+--------+--------+ > > | Yes | No | No | 4 | 401xxx | IDZ/ N/A | qat_401xxx | > > 4xxx | > 4942 | 2 | 4943 | 16 | > > > > +-----+-----+-----+-----+----------+---------------+---------------+-- > > ----------+--------+------+--------+--------+ > > + | Yes | Yes | Yes | 4 | 402xxx | linux/6.4+ | qat_402xxx | > > 4xxx | > 4944 | 2 | 4945 | 16 | > > + > > +-----+-----+-----+-----+----------+---------------+---------------+------------+-- > ------+------+--------+--------+ > > + | Yes | No | No | 4 | 402xxx | IDZ/ N/A | qat_402xxx | > > 4xxx | > 4944 | 2 | 4945 | 16 | > > + > > + +-----+-----+-----+-----+----------+---------------+---------------+ > > + ------------+--------+------+--------+--------+ > > Is there such a kernel module named qat_402xxx upstream? > I can only find qat_4xxx. > Good catch, you're right, there is no kernel module 402xxx. These devices fall under the original 4xxx driver. Will update here, and send a fix for the 401xxx entry later.
Have sent a v2 addressing the above comments: https://patches.dpdk.org/project/dpdk/patch/20230821093349.3519591-1-ciara.po...@intel.com/ Thanks, Ciara
