Subject: Re: kern/33778 (Intel Pro Wireless 3945ABG support (wpi driver))
To: None <simonb@NetBSD.org, gnats-admin@netbsd.org,>
From: Greg Oster <oster@cs.usask.ca>
List: netbsd-bugs
Date: 08/09/2006 22:15:08
The following reply was made to PR kern/33778; it has been noted by GNATS.

From: Greg Oster <oster@cs.usask.ca>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/33778 (Intel Pro Wireless 3945ABG support (wpi driver)) 
Date: Wed, 09 Aug 2006 16:14:44 -0600

 Simon Burge writes:
 > The following reply was made to PR kern/33778; it has been noted by GNATS.
 > 
 > From: Simon Burge <simonb@NetBSD.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: simonb@NetBSD.org, netbsd-bugs@netbsd.org,
 > 	gnats-admin@netbsd.org, camjelemon@gmail.com
 > Subject: Re: kern/33778 (Intel Pro Wireless 3945ABG support (wpi driver)) 
 > Date: Tue, 27 Jun 2006 00:14:52 +1000
 > 
 >  Hi Jean-Baptiste,
 >  
 >  I've seen the following panics while using the wpi driver.  This is on
 >  a core-duo machine running an MP ACPI kernel if that matters. 
 
 Hmmm.. I pulled the files into a -current kernel the other day, 
 configured wpi, and started playing..  and I havn't seen any panics
 with it yet.. (and have transferred probably 6GB over the wireless 
 connection, just in testing -- sustaining about 2MB/sec over scp).  
 I've only been using WEP though -- havn't tried the WPA bits yet... 
 
 The machine in question is a core-duo:
 
 cpu0: Intel Pentium M (Yonah) (686-class), 1596.16 MHz, id 0x6e8
 cpu1: Intel Pentium M (Yonah) (686-class), 1596.00 MHz, id 0x6e8
 
 running (a somewhat modified) GENERIC.MP_ACPI.  The wireless shows up 
 as:
 
 wpi0 at pci3 dev 0 function 0: Intel PRO/Wireless LAN 3945ABG Mini-PCI Adapter (rev. 0x02)
 wpi0: interrupting at ioapic0 pin 18 (irq 10)
 wpi0: 802.11 address 00:13:02:ab:cd:ef
 wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
 wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
 
 (yes, the MAC address has been edited for posting :) )
 
 Personally, I'd like to see the driver added in as-is, and we can 
 debug it further from there... 
 
 Later...
 
 Greg Oster