From owner-freebsd-current@FreeBSD.ORG Sun Dec 9 13:30:10 2007 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 31D8E16A418 for ; Sun, 9 Dec 2007 13:30:10 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by mx1.freebsd.org (Postfix) with ESMTP id B17B313C474 for ; Sun, 9 Dec 2007 13:30:09 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FAEt5W0d5LSIc/2dsb2JhbACBWg X-IronPort-AV: E=Sophos;i="4.23,273,1194183000"; d="scan'208";a="2891239" Received: from ppp121-45-34-28.lns10.adl2.internode.on.net (HELO mail.clearchain.com) ([121.45.34.28]) by ipmail01.adl6.internode.on.net with ESMTP; 09 Dec 2007 23:44:49 +1030 Received: from [192.168.155.249] (draco.internal.clearchain.com [192.168.155.249]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id lB9DEjH0031087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Dec 2007 23:44:46 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <475BEA3C.5050305@clearchain.com> Date: Sun, 09 Dec 2007 23:44:36 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Jeff Palmer References: <475759B7.6080502@gmail.com> <475762D0.8080404@acm.poly.edu> <4757FC17.4040605@clearchain.com> <47583D14.2020900@rexdb.com> <475870C0.9070908@errno.com> <4758A0A4.2090002@rexdb.com> In-Reply-To: <4758A0A4.2090002@rexdb.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Sun, 09 Dec 2007 23:44:47 +1030 (CST) Cc: Benjamin Adams , Boris Kochergin , freebsd-current@freebsd.org Subject: Re: wireless 3945ABG Wireless support 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: Sun, 09 Dec 2007 13:30:10 -0000 Jeff Palmer wrote: > Sam Leffler wrote: > >> Jeff Palmer wrote: >> >>> Benjamin Close wrote: >>> >>> >>>> Boris Kochergin wrote: >>>> >>>> >>>>> Benjamin Adams wrote: >>>>> >>>>> >>>>>> I'm currently running 6.2 on my ibm T60. >>>>>> I want to upgrade to 7.0 or 8.0. >>>>>> Do either one have the intel 3945ABG wireless driver installed by >>>>>> default? >>>>>> or where can I download the latest drivers for it? >>>>>> Thanks >>>>>> >>>>>> ----------------------------------------- >>>>>> Ben Adams >>>>>> http://www.FreeBSD-World.com/ >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to >>>>>> "freebsd-current-unsubscribe@freebsd.org" >>>>>> >>>>>> >>>>> You can get the driver for 7/8 from >>>>> http://www.clearchain.com/wiki/Wpi, and it's included in 8-CURRENT. >>>>> >>>>> >>>> And about to be MFC'ed to 7... well at least in the next day. >>>> >>>> Cheers, >>>> Benjamin >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>>> >>>> >>>> >>>> >>>> >>>> >>> There seems to be a lot of reports of success using the wpi driver for >>> that chipset, however it's not working for everyone. Count me as one of >>> them it doesn't currently work for. You can search the archives if you >>> are interested in details. >>> >>> >>> >> If you've got a problem and want it fixed please file a PR w/ >> sufficient information for someone to diagnose. Referring to some old >> post is unlikely to result in help. >> >> Sam >> >> >> !DSPAM:8,475870d721261944516145! >> >> >> > Sam, > > I didn't feel a PR was in order just yet, because I had posted and > gotten a reply from Ben with a patch he wanted me to try. The patch got > my hardware a bit closer to associating. However it wasn't "quite there > yet." I'm aware he's busy, and I'm quite patient. So the fact that he > hasn't had me try anything else in the meantime doesn't annoy or bother > me in the least. > > It's quite the opposite actually. These developers who know enough to > write (or port) drivers, and then donate their time to actually _do_ it > have nothing but my utmost respect. > > I didn't mean for that post to sound like "RUN AWAY!" or like I was > complaining. That's actually why I mentioned the large number of > success stories, to show that many people do have it going without > problems. I'm not sure if there are different revisions of the chip, > or what the problem may be; but I was just making the original poster > aware that he may still have problems with it, and he probably wouldn't > be the only one if he did. > > At this point, I'll leave it up to Benjamin Close (who is being CC'd) > Would you prefer I filed a formal PR just to get it "on the record?" > > I've tried the p4fetch.rb script mentioned on the clearchain wpi page, > but apparantly I don't have something installed that it needs. I have > ruby installed, but it complains, so I'm guessing I'm missing a library > or plugin it needs. However, I don't know or use ruby, so I have no > clue what to install. Sadly, downloading things from perforce is a > serious pain if doing it manually, so I just haven't tried the p4 version. > > Hope that cleared things up. In summary: Thanks Ben (and all the > developers!) for some seriously great work. > > Jeff > Hi Jeff, For now please send me logs and a list of issues. I'll work with you to resolve them in the p4 branch as time permits. Cheers, Benjamin