[DragonFlyBSD - Submit #3244] (Resolved) Additional Intel I219-LM and I219-V Ethernet PCI device numbers from NetBSD

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3244 has been updated by deef.

Due date set to 08/19/2020
Status changed from New to Resolved
% Done changed from 0 to 100

Thank you, commited in a0a0c119+.

----------------------------------------
Submit #3244: Additional Intel I219-LM and I219-V Ethernet PCI device numbers from NetBSD
http://bugs.dragonflybsd.org/issues/3244#change-13920

* Author: davshao
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: Driver
* Target version: 
----------------------------------------
NetBSD current sys/dev/pci/pcidevs.h has additional PCI device numbers for Intel I219-LM and Intel I219-V Ethernet.  Simply adding these numbers has been verified to enable em0 on an Asus Prime H470-Plus mATX motherboard for I219-V11 0x0D4D.  Also NetBSD current had no problem activating its wm0 Ethernet device for this motherboard.

Note that Phoronix had an article "DragonFlyBSD vs. FreeBSD vs. Ubuntu 20.04 On Intel's Core i9 10900K Comet Lake" that noted on-board Ethernet was not functional on either FreeBSD 12 or DragonFly BSD, and that claimed that even for Linux, 5.6 or later was required.  That claim may be incorrect for at least obtaining some minimal functionality on DragonFly for very little effort.

Attached is a patch adding the numbers from NetBSD.  The naming of the devices using "CNP", which I believe is an abbreviation for previous generation codename Cannon Point chipsets, is arguably incorrect; however, I was unable to locate any code name at all for current series 400 Intel chipsets.  In any case, for at least one device, the Cannon Point handler appears to work unchanged.

---Files--------------------------------
i219_400.diff (4.37 KB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account