From owner-freebsd-current@FreeBSD.ORG Thu Feb 26 21:48:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C5CD1065670 for ; Thu, 26 Feb 2009 21:48:01 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 25AB48FC1A for ; Thu, 26 Feb 2009 21:48:00 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n1QLm0Au043015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Feb 2009 13:48:00 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49A70E10.4060708@freebsd.org> Date: Thu, 26 Feb 2009 13:48:00 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Alex Keda References: <49A701DF.5070109@lissyara.su> <3c1674c90902261300x6dd5f21bja58ecf214bcfb644@mail.gmail.com> <49A70508.20100@lissyara.su> In-Reply-To: <49A70508.20100@lissyara.su> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-DCC-Misty-Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: About bwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 21:48:01 -0000 Alex Keda wrote: > Kip Macy пишет: >> Someone needs to be there to maintain it. To the best of my knowledge >> no one appropriate has stepped forward. > And what exactly should be supported? > He finished - nothing more to do. > > no way to develop a driver. > the new cards have to write a new driver. The driver has many known issues and limitations. Without someone willing to respond to user questions, update the code and test, etc. committing the driver ends up causing more frustration and ill-will than leaving it outside the tree. This is a lesson we've learned many times--people encounter a broken driver and draw incorrect assumptions about the system as a whole. Unfortunately noone has stepped up to own the driver; trust me I've asked many times for someone. Sam