Date: Fri, 6 Jul 2007 10:56:56 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Kip Macy <kip.macy@gmail.com> Cc: freebsd-current@freebsd.org, thierry@herbelot.com Subject: Re: Future of the ie(4) driver Message-ID: <20070706105458.A247@fledge.watson.org> In-Reply-To: <b1fa29170707051607s4c6c6316n28f4cb809e44281@mail.gmail.com> References: <200707051428.22766.jhb@freebsd.org> <200707052319.16303.thierry@herbelot.com> <b1fa29170707051607s4c6c6316n28f4cb809e44281@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 5 Jul 2007, Kip Macy wrote: >> I am the proud owner of one ie(4) board. >> >> just now, the machine using it is running -Stable, but I can easily arrange >> for dual booting with -Current. > > An outstanding issue for it is that the NET_GIANT infrastructure is going > away in 7.0, so if_ie will also need to be locked in order to remain. That's actually not the case -- NET_NEEDS_GIANT eliminates support for non-MPSAFE protocol stacks, not non-MPSAFE device drivers. IFF_NEEDSGIANT will, sadly, remain, as several core drivers/frameworks still require Giant. Things on the chopping board for 7.0, hopefully to be restored for 7.1 once locked, are: - i4b - netatm - ng_h4 Things removed entirely: - KAME IPSEC, replaced with FAST_IPSEC now it supports IPv6 However, I do hope to make non-MPSAFE network interface drivers go away in 8-CURRENT, so people who want their non-MPSAFE network interface drivers to persist need to either lock them down or work with someone to test locking patches for them. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070706105458.A247>