Date: Mon, 28 Oct 2019 23:10:28 +0100 From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= <olivier@freebsd.org> To: Franco Fichtner <franco@lastsummer.de> Cc: Gleb Smirnoff <glebius@freebsd.org>, Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org>, freebsd@intel.com Subject: Re: SVN r353868 breaks net/intel-em-kmod Message-ID: <CA%2Bq%2BTcrBXiCbQYB50HBPiCEEAhirXrX6EHgCZXz0sVRxq9wORg@mail.gmail.com> In-Reply-To: <335E057C-1529-4774-B655-6A1CADA2DF11@lastsummer.de> References: <d622987a-2527-d652-3a06-a2a138b6abaf@protected-networks.net> <20191024175642.GN4086@FreeBSD.org> <335E057C-1529-4774-B655-6A1CADA2DF11@lastsummer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 24, 2019 at 8:02 PM Franco Fichtner <franco@lastsummer.de> wrote: > > > On 24. Oct 2019, at 7:56 PM, Gleb Smirnoff <glebius@freebsd.org> wrote: > > > > What's the reason to keep these outside of the tree drivers? > > Unmodified and newer drivers for older FreeBSD versions. > > In particular, 11.x had unfortunate and latent regressions > regarding link negotiation (chipset subset) and netmap support. > > So the root cause is a regression in a FreeBSD RELEASE branch: Why those known regressions are not fixed by an errata in place of a new port ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bq%2BTcrBXiCbQYB50HBPiCEEAhirXrX6EHgCZXz0sVRxq9wORg>