On 2016/02/08 13:53, Christian Ehrhardt wrote: > If you own a skylake based onboard NIC, please give this diff a try.
The most important bit, especially at this point in the release cycle, is whether it makes any changes that cause problems with other chips. I don't have time to look closely now but the question is "does the diff change anything for existing chips, or does it *only* change things for new chips"? > Index: dev/pci/pcidevs > =================================================================== > RCS file: /data/mirror/openbsd/cvs/src/sys/dev/pci/pcidevs,v > retrieving revision 1.1786 > diff -u -p -r1.1786 pcidevs > --- dev/pci/pcidevs 30 Jan 2016 01:02:04 -0000 1.1786 > +++ dev/pci/pcidevs 4 Feb 2016 16:04:31 -0000 > @@ -3353,6 +3353,10 @@ product INTEL I218_LM_2 0x15a0 I218-LM > product INTEL I218_V_2 0x15a1 I218-V > product INTEL I218_LM_3 0x15a2 I218-LM > product INTEL I218_V_3 0x15a3 I218-V > +product INTEL I219_LM 0x156F I219_LM > +product INTEL I219_V 0x1570 I219_V > +product INTEL I219_LM2 0x15B7 I219_LM2 > +product INTEL I219_V2 0x15B8 I219_V2 > product INTEL X557_AT2 0x15ad X557-AT2 > product INTEL CORE5G_H_PCIE_X16 0x1601 Core 5G PCIE > product INTEL CORE5G_M_GT1_1 0x1602 HD Graphics Please maintain numerical order of pid (0x156f/0x1570 are out of place), and like the other entries use lowercase for pid and s/_/-/ in the text version of the device name on the right-hand column. (When committing the pcidevs parts, pcidevs itself needs to be done first, then "make" to update the generated files before committing those, so the generated files show the correct RCS ID in comments).
