From owner-freebsd-mobile@FreeBSD.ORG Tue Aug 26 18:58:55 2008 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD0B0106564A; Tue, 26 Aug 2008 18:58:55 +0000 (UTC) (envelope-from jmt@twilley.org) Received: from alpha.twilley.org (alpha.twilley.org [204.152.189.135]) by mx1.freebsd.org (Postfix) with ESMTP id 8B4628FC16; Tue, 26 Aug 2008 18:58:55 +0000 (UTC) (envelope-from jmt@twilley.org) Received: from [10.202.10.160] (205.158.109.36.ptr.us.xo.net [205.158.109.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alpha.twilley.org (Postfix) with ESMTPSA id 2651F233858; Tue, 26 Aug 2008 11:58:55 -0700 (PDT) Message-ID: <48B4526E.8000802@twilley.org> Date: Tue, 26 Aug 2008 11:58:54 -0700 From: Jack Twilley User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Sam Leffler References: <87vdxr9d9y.fsf@chateau.d.lf> <48B42777.1050304@freebsd.org> <48B43D90.8090807@twilley.org> <48B44FCA.9070609@freebsd.org> In-Reply-To: <48B44FCA.9070609@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: =?UTF-8?B?QXNoaXNoIFNodWtsYSDgpIbgpLbgpYDgpLcg4KS24KWB4KSV4KWN4KSy?= , freebsd-mobile@freebsd.org Subject: Re: Is 'ath' going to be updated for 7.1-RELEASE ? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2008 18:58:55 -0000 Sam Leffler wrote: > Jack Twilley wrote: >> Sam Leffler wrote: >>> Ashish Shukla आशीष शुक्ल wrote: >>>> Hi, >>>> >>>> Just came across the release schedule of 7.1-RELEASE. I'm wondering if >>>> new version of 'ath' driver (for Athereos Wireless chipsets) is going >>>> to be included or not ? If yes, I'll be glad to try the betas :). >>>> >>>> >>> Not sure what "new version" means. I'm unlikely to have any time to >>> look at existing ath problems in RELENG_7 before the release. >> I am hoping against hope it means "whatever it takes to make the Asus >> Eee PC work without having to follow the steps on the EeeBSD page". I >> rebuilt kernel and world today and forgot *again* to do the madwifi >> dance. It's getting old. > > The required hal is not even committed to HEAD yet; there's no way it's > going to get into RELENG_7 w/o significant testing. As to "getting old" > others are free to pitch in to make things happen. I have very little > time for freebsd right now and what time I do have is focused on higher > priority issues. All I can offer is the ability to test. I do not have the skill necessary to fix this or I would have written a fix and asked for it to be committed. It is amazingly frustrating to know that there is a workaround and to see that others consider this a low priority issue. If not you, then who should I ask about committing the new HAL to HEAD and helping me check out whatever I need to check out to test the fix so the rest of us can have wireless Ethernet working out of the box? Jack. > > Sam > >