From owner-freebsd-drivers@FreeBSD.ORG Mon Nov 5 21:59:55 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EF4016A46B; Mon, 5 Nov 2007 21:59:55 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 46ABE13C4AA; Mon, 5 Nov 2007 21:59:54 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FAJoeL0d5LXvK/2dsb2JhbACBWw X-IronPort-AV: E=Sophos;i="4.21,374,1188743400"; d="scan'208";a="226298430" Received: from ppp121-45-123-202.lns11.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.123.202]) by ipmail01.adl2.internode.on.net with ESMTP; 06 Nov 2007 08:29:09 +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 lA5Lx7Jp039733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Nov 2007 08:29:08 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <472F9222.7030809@clearchain.com> Date: Tue, 06 Nov 2007 08:28:58 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Tom Evans References: <472A6708.9030109@clearchain.com> <1194274174.64797.16.camel@localhost> <1194274315.64797.17.camel@localhost> In-Reply-To: <1194274315.64797.17.camel@localhost> 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]); Tue, 06 Nov 2007 08:29:09 +1030 (CST) Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2007 21:59:55 -0000 Tom Evans wrote: > On Mon, 2007-11-05 at 14:49 +0000, Tom Evans wrote: > >> On Fri, 2007-11-02 at 10:23 +1030, Benjamin Close wrote: >> >>> Howdy All, >>> I'm pleased to announce the first 'official' experimental version >>> of the wpi wireless driver and hence require your help in making it >>> become stable. >>> Expect a few things not to work (ie bg scanning, setting txpower) but in >>> general the driver should be usable in station mode (hostap is not yet >>> supported). >>> >>> If you've got an Intel 3945abg wireless card, grab the tarball at: >>> >>> >>> http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz >>> >>> Untar and follow the instructions in the README. >>> If you want more info about the driver, or to checkout the FAQ checkout: >>> >>> http://www.clearchain.com/wiki/Wpi >>> >>> I'm interested in all reports related to panics, things not working as >>> expected, etc. >>> The driver still has debug enabled so expect a few messages to be dumped >>> to the screen whilst in use. >>> >>> Finally, many thanks to all those that have been helping debug the >>> driver along the way. >>> >>> Cheers, >>> Benjamin >>> >> Hi Benjamin >> >> I had a chance to compile the new driver at lunch time today. The driver >> loads semi-successfully - no errors, but it reports 25 'bus_dmamem_alloc >> failed to align memory properly' warnings. It can then be brought up, >> but attempting a 'ifconfig wpi0 scan' hangs. >> /var/log/messages (attached) reports 'wpi0: fatal firmware error'. >> ^T reports: >> load: 0.08 cmd: ifconfig 84691 [sbwait] 0.00u 0.01s 0% 704k >> >> This is running RELENG_7 from 26/10/07. >> >> I am fairly sure that there is no wifi connection available in the >> office though, so I will also try again tonight, sitting the laptop next >> to an AP. >> >> Regards >> >> Tom >> > > One thing I didn't mention: this was using latest code from p4, not the > tarball. I'll try both the tarball and the p4 code tonight. > > Changes between the two are very minimal, though if the tarball does work on your laptop but the p4 doesn't please let me know and we'll work out why. Cheers, Benjamin