DragonFly BSD
DragonFly kernel List (threaded) for 2010-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[no subject]


From: Joe Talbott <josepht@cstone.net>
Mail-Followup-To: Johannes Hofmann <johannes.hofmann@gmx.de>,
Subject: Re: wlan_ratectl (was Re: firmware discussion)
Date: Tue, 30 Mar 2010 16:28:32 -0400
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:kernel@crater.dragonflybsd.org>
List-Subscribe: <mailto:kernel-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:kernel-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:kernel-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-kernel@crater.dragonflybsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
References: <77716AC9-CA8B-4054-9E11-07D842BA6252@gmail.com> <20100330131714.GD73251@venus.xenno.com> <9AAD7480-D41F-4900-B190-A2C9B700F7BE@gmail.com> <4bb21880$0$55378$415eb37d@crater_reader.dragonflybsd.org> <15274EA7-EB29-4DF2-9C70-4FA04E01C04A@gmail.com> <201003301730.o2UHU6eS031192@apollo.backplane.com> <20100330174451.GA86744@venus.xenno.com> <201003301750.o2UHoXmX031487@apollo.backplane.com> <20100330175338.GB86744@venus.xenno.com> <4bb253bc$0$55376$415eb37d@crater_reader.dragonflybsd.or
In-Reply-To: <4bb253bc$0$55376$415eb37d@crater_reader.dragonflybsd.org>
Sender: kernel-errors@crater.dragonflybsd.org
Errors-To: kernel-errors@crater.dragonflybsd.org
Lines: 19
X-Trace: 1269981541 crater_reader.dragonflybsd.org 55374
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:14205

On Tue, Mar 30, 2010 at 07:40:44PM +0000, Johannes Hofmann wrote:
> Joe Talbott <josepht@cstone.net> wrote:
> > On Tue, Mar 30, 2010 at 10:50:33AM -0700, Matthew Dillon wrote:
> >>     Well, I guess it comes down to how difficult it would be to integrate
> >>     the ratectl we have into the new infrastructure, and whether there are
> >>     any plans in FreeBSDland to have an integrated ratectl.  If not then
> >>     there is an argument for them adopting ours.
> >> 
> > 
> > Converting the wpi driver I'm porting was not very difficult.  I don't
> > like users of the half dozen or so wifi drivers we currently have
> > losing the ratectl features we have.
> Can the adaption to ratectl be done incrementally (driver by driver)
> and have non-adapted drivers working without it? 

That should be possible.


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]