e1000: Add support for [Tiger, Alder, Meteor] Lake client platforms

[kbowling]

Summary

Add PCI IDs and basic support for Intel's newer client platforms.

MFC: 2 weeks

Test Plan

Taking a look at the BSDL DPDK driver I believe these changes to be sufficient for the first two https://github.com/DPDK/dpdk/tree/main/drivers/net/e1000. Meteor Lake is a ways out but no reason not to add the public IDs now.

[grehan]

sys/dev/e1000/e1000_api.c

336

Missing break ?

[markj]

I can't see any problems in the diff.

[erj]

Were there any other hacks or hardware workarounds? I think they usually add some every generation, but maybe they've finally stopped with these last I219 versions.

sys/dev/e1000/if_em.c

183

I almost wish someone would correct these branding strings, but it would be a massive hassle.

[markj]

In D29801#669698, @erj wrote:

Were there any other hacks or hardware workarounds? I think they usually add some every generation, but maybe they've finally stopped with these last I219 versions.

I at least couldn't find any special handling for any of these devices in the Linux or DPDK drivers.

[kbowling]

@erj I am not aware of any. There is a generic I219 errata "em_flush_desc_rings" in the out of tree driver I am adapting to iflib e1000 that will be a separate review/commit.

sys/dev/e1000/if_em.c

183

I'm willing to do it if you can give me some pointers. I'll do so in a different review/commit.