Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-06 Thread Allan Jude
On 2014-02-06 22:18, Julian H. Stacey wrote: > Hi, Reference: >> From:David Chisnall >> Date:Thu, 6 Feb 2014 18:52:43 + > > David Chisnall wrote: >> On 6 Feb 2014, at 18:34, Julian H. Stacey wrote: >> >>> Best avoid the obscure word `Deprecated' in manuals: >>

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-06 Thread Julian H. Stacey
Hi, Reference: > From: David Chisnall > Date: Thu, 6 Feb 2014 18:52:43 + David Chisnall wrote: > On 6 Feb 2014, at 18:34, Julian H. Stacey wrote: > > > Best avoid the obscure word `Deprecated' in manuals: > > It's not common/ plain English. Maybe a geek import, or USA > >

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-06 Thread Tom Evans
On Thu, Feb 6, 2014 at 6:34 PM, Julian H. Stacey wrote: > Best avoid the obscure word `Deprecated' in manuals: > It's not common/ plain English. Maybe a geek import, or USA > dialect ? It's not easily internationaly understood English. > Best make manuals easier for non native English spea

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-06 Thread David Chisnall
On 6 Feb 2014, at 18:34, Julian H. Stacey wrote: > Best avoid the obscure word `Deprecated' in manuals: > It's not common/ plain English. Maybe a geek import, or USA > dialect ? It's not easily internationaly understood English. > Best make manuals easier for non native English speakers (& n

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-06 Thread Julian H. Stacey
Yonghyeon PYUN wrote: > On Mon, Feb 03, 2014 at 02:56:37PM +0100, Christian Brueffer wrote: > > Hi, > > > > for some time now we have had two drivers for NVIDIA NForce/MCP network > > chips, namely nve(4) and nfe(4). > > > > The former came first and is based on a binary blob. The latter was > >

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-05 Thread Yonghyeon PYUN
On Mon, Feb 03, 2014 at 02:56:37PM +0100, Christian Brueffer wrote: > Hi, > > for some time now we have had two drivers for NVIDIA NForce/MCP network > chips, namely nve(4) and nfe(4). > > The former came first and is based on a binary blob. The latter was > later ported from OpenBSD and is blob

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-05 Thread John Baldwin
On Monday, February 03, 2014 02:56:37 PM Christian Brueffer wrote: > Hi, > > for some time now we have had two drivers for NVIDIA NForce/MCP network > chips, namely nve(4) and nfe(4). > > The former came first and is based on a binary blob. The latter was > later ported from OpenBSD and is blob-

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-03 Thread Remko Lodder
On 03 Feb 2014, at 15:23, Tim Daneliuk wrote: > On 02/03/2014 07:56 AM, Christian Brueffer wrote: >> Hi, >> >> for some time now we have had two drivers for NVIDIA NForce/MCP network >> chips, namely nve(4) and nfe(4). >> >> The former came first and is based on a binary blob. The latter was

Re: RFC: deprecation of nve(4) in 10-STABLE and removal from 11-CURRENT

2014-02-03 Thread Tim Daneliuk
On 02/03/2014 07:56 AM, Christian Brueffer wrote: Hi, for some time now we have had two drivers for NVIDIA NForce/MCP network chips, namely nve(4) and nfe(4). The former came first and is based on a binary blob. The latter was later ported from OpenBSD and is blob-free. nfe(4) supports all ch