Date: Mon, 30 Jun 2008 13:36:45 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) Message-ID: <20080630133335.K54631@fledge.watson.org> In-Reply-To: <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> <20080630141611.56172qs6gac45ri8@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Jun 2008, Alexander Leidinger wrote: >> Here's the revised list of drivers that will have their build disabled in >> the next week (subject to an appropriate block of time for me): > > Is this list supposed to be complete (including dependencies)? bktr uses > some I2C stuff and cxm (in ports) too. As far as I'm aware, this list is complete. I compiled it by identifying all network device drivers that set (or may set) the IFF_NEEDSGIANT. With respect to i2c, this refers *only* to the if_ic.c network device driver, and not the other services associated with i2c, so bktr and other i2c consumers should be unaffected. I'm not familiar with cxm so can't comment on that. If you are aware of any other in-tree network device drivers that use IFF_NEEDSGIANT and aren't on the list, please do let me know. 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?20080630133335.K54631>