Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed (was: Re: Wiki page for non-MPSAFE network stack de-orbit scheduling)

2009-03-20 Thread Robert Watson
On Mon, 16 Feb 2009, Robert Watson wrote: The following schedule is proposed, assuming nothing goes horribly wrong with the new USB code in the next few weeks, and remaining nits relating to USB network and 802.11 drivers are handled: 16 February 2009HEADS UP to lists (this e-mail) 0

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed (was: Re: Wiki page for non-MPSAFE network stack de-orbit scheduling)

2009-03-15 Thread Robert Watson
On Sun, 15 Mar 2009, Robert Watson wrote: On Mon, 16 Feb 2009, Robert Watson wrote: 16 February 2009HEADS UP to lists (this e-mail) 01 March 2009 Disable build of all IFF_NEEDSGIANT drivers in 8.x Slightly delayed while USB NDIS was sorted out, I will be moving ahead with

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed (was: Re: Wiki page for non-MPSAFE network stack de-orbit scheduling)

2009-03-15 Thread Robert Watson
On Mon, 16 Feb 2009, Robert Watson wrote: 16 February 2009HEADS UP to lists (this e-mail) 01 March 2009 Disable build of all IFF_NEEDSGIANT drivers in 8.x Slightly delayed while USB NDIS was sorted out, I will be moving ahead with disabling the build of all IFF_NEEDSGIANT d

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed

2009-02-24 Thread Bruce Simpson
Robert Watson wrote: .. Just a reminder that 1 March is gradually approaching. It looks like the new USB stack is settling nicely, so I currently have no plans to defer the above schedule. Just to say: this is good news for 8.x, particularly for VIMAGE. Losing the Giant lock from the netwo

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed (was: Re: Wiki page for non-MPSAFE network stack de-orbit scheduling)

2009-02-24 Thread Robert Watson
On Mon, 16 Feb 2009, Robert Watson wrote: The following schedule is proposed, assuming nothing goes horribly wrong with the new USB code in the next few weeks, and remaining nits relating to USB network and 802.11 drivers are handled: 16 February 2009HEADS UP to lists (this e-mail) 0

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed

2009-02-17 Thread Robert Watson
On Tue, 17 Feb 2009, Krassimir Slavchev wrote: if_sr and if_ar are really simple and could probably be converted "trivially".. especially if their netgraph code is used. however I wonder if anyone still has that hardware (they are drivers for two sync serial cards). I still have such Digi/

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed

2009-02-17 Thread Krassimir Slavchev
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julian Elischer wrote: > Robert Watson wrote: >> >> (Bcc to arch@) >> >> On Mon, 26 May 2008, Robert Watson wrote: >> >>> Just to keep track of things: >>> >>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT >> >> Delayed by about six months, the merge and

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed

2009-02-16 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Watson wrote: > Network device drivers intimately tangled with the old TTY code: > > if_cx > if_ppp > lf_sl The old TTY code appears to be the reason that the bluetooth/ng_h4 driver was "abandoned". Not having investigated further, I do

Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed

2009-02-16 Thread Julian Elischer
Robert Watson wrote: (Bcc to arch@) On Mon, 26 May 2008, Robert Watson wrote: Just to keep track of things: http://wiki.freebsd.org/NONMPSAFE_DEORBIT Delayed by about six months, the merge and switch to the new USB stack in 8.x means that we're now fairly close to being able to pick up t

HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed (was: Re: Wiki page for non-MPSAFE network stack de-orbit scheduling)

2009-02-16 Thread Robert Watson
(Bcc to arch@) On Mon, 26 May 2008, Robert Watson wrote: Just to keep track of things: http://wiki.freebsd.org/NONMPSAFE_DEORBIT Delayed by about six months, the merge and switch to the new USB stack in 8.x means that we're now fairly close to being able to pick up this project again. Th