Date: Tue, 12 Sep 2017 15:47:12 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: freebsd-net@freebsd.org Subject: Re: Need help Message-ID: <59B7E560.8090505@omnilan.de> In-Reply-To: <aafb99be-b2cf-bf4f-a2c3-b22455bd9d8b@yandex.ru> References: <alpine.BSF.2.00.1709121158120.59850@pochta.canmos.ru> <59B7DFE5.7020404@omnilan.de> <59B7E206.8020500@omnilan.de> <f8e1d7be-73df-e5ae-252c-c89ac32924a0@yandex.ru> <aafb99be-b2cf-bf4f-a2c3-b22455bd9d8b@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich Andrey V. Elsukov's Nachricht vom 12.09.2017 15:38 (localtime): > On 12.09.2017 16:35, Andrey V. Elsukov wrote: >>> Either add E1000_DEV_ID_I350_COPPER_NOEE elsewhere, or try without _NOEE >>> appendix if datasheet suggests. >> >> Hi, >> >> just defining device id in the header usually doesn't automatically add >> support for this device. You need to teach probe function to use defined >> id. So, you need to add this id to some array in the if_em.c, probably >> this is igb_vendor_info_array. > > And for stable/10 this array is in the if_igb.c. Thanks for clarifying, I haven't looked what "elsewhere" should read, happy to know it's if_igb.c. Too curious about this id... shouldn't be interested, but as usual, buriosity kills the cat/the time ;-) This might help, looking for "E1000_DEVICE_I350_EEPROM_LESS": https://github.com/BarrelfishOS/barrelfish/blob/master/usr/drivers/e1000/ Now I really go back to work ;-) -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59B7E560.8090505>