On Friday 26 January 2007 03:44, John W. Linville wrote:
On Sat, Dec 30, 2006 at 11:25:15PM -0600, Larry Finger wrote:
The current bcm43xx driver ignores any wireless-enable switches on mini-PCI
and mini-PCI-E cards. This patch implements a new routine to interrogate the
radio hardware
On Thu, 2007-01-25 at 09:34 -0500, Gene Heskett wrote:
MLME? More acronyms I've not put in my wet dictionary.. :)
The 802.11 specs have a huge list of acronyms you might want to be
somewhat familiar with. I think I have a printout somewhere, can't ever
remember them either ;)
johannes
Interesting. I looked at the USB dump a bit and compared it to the RNDIS
structures in the Linux rndis gadget driver... The device is a fullmac
device using 802.3 framing.
Most of the interesting things are apparently done via private OIDs and
variables...
Attached are three files to dump the
The dscape driver requires v4 firmware, while the mainline driver
prefers v3. Giving the two different names makes it easier to support
parallel installation. This patches fwcutter to dump v4 firmware with a
different name - the second patch alters the dscape driver to request
it.
This patch alters the dscape version of the bcm43xx driver to explicitly
request version 4 firmware.
Signed-off-by: Matthew Garrett [EMAIL PROTECTED]
---
diff --git a/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
b/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
index 9f4d51d..4f11ce8
Jörg Sommer wrote:
Good morning,
I want to connect to a WPA-EPA-TTLS encrypted network, but wpasupplicant
(0.5.7) says: Driver did not support SIOCSIWENCODEEXT. What does he mean?
Can someone read the wpa_supplicant log and see why it can't connect to
the network?
Could we please have more
Matthew Garrett wrote:
The dscape driver requires v4 firmware, while the mainline driver
prefers v3. Giving the two different names makes it easier to support
parallel installation. This patches fwcutter to dump v4 firmware with a
different name - the second patch alters the dscape driver
On Fri, Jan 26, 2007 at 09:49:15AM -0600, Larry Finger wrote:
NACK. The --postfix switch for fwcutter, and the postfix option for
bcm43xx-d80211 driver handle
this case perfectly well.
It would be helpful to standardise - the default behaviour at the moment
makes the upgrade path difficult.
Matthew Garrett wrote:
On Fri, Jan 26, 2007 at 09:49:15AM -0600, Larry Finger wrote:
NACK. The --postfix switch for fwcutter, and the postfix option for
bcm43xx-d80211 driver handle
this case perfectly well.
It would be helpful to standardise - the default behaviour at the moment
makes
On Fri, Jan 26, 2007 at 01:53:18PM +, Matthew Garrett wrote:
This patch alters the dscape version of the bcm43xx driver to explicitly
request version 4 firmware.
- bcm43xx_pcm%d%s.fw,
+ bcm43xx_v4_pcm%d%s.fw,
There's no difference between pcm
On Fri, Jan 26, 2007 at 01:51:15PM +0100, Johannes Berg wrote:
If you have a snoopy pro
Be careful. Last time I played with SnoopyPro it didn't save the whole
traffic. So, usbsnoopy was a better choice for me.
Martin
___
Bcm43xx-dev mailing list
On Fri, 2007-01-26 at 18:49 +0100, Martin Langer wrote:
On Fri, Jan 26, 2007 at 01:51:15PM +0100, Johannes Berg wrote:
If you have a snoopy pro
Be careful. Last time I played with SnoopyPro it didn't save the whole
traffic. So, usbsnoopy was a better choice for me.
Joe created the logs,
roucaries bastien wrote:
On 1/26/07, Larry Finger [EMAIL PROTECTED] wrote:
roucaries bastien wrote:
Do you have the log stuff that precedes this part? In particular, was
there a assertion that failed?
It is oops on resume and no asseertion failled this boot. However I
have usually a
On Friday 26 January 2007 16:58, Jiri Benc wrote:
(The latest wireless-dev tree. How to reproduce: associate (probably
bringing the interface up is enough) and eject the cardbus card.)
Is this linville's tree or mine?
Either way, did you apply that DMA skb doublefree patch? It fixes
memory
roucaries bastien wrote:
On 1/26/07, Larry Finger [EMAIL PROTECTED] wrote:
roucaries bastien wrote:
On 1/26/07, Larry Finger [EMAIL PROTECTED] wrote:
roucaries bastien wrote:
Do you have the log stuff that precedes this part? In
particular, was
there a assertion that failed?
It
On Friday 26 January 2007 14:53, Matthew Garrett wrote:
This patch alters the dscape version of the bcm43xx driver to explicitly
request version 4 firmware.
NACK.
Use fwpostfix module parameter.
This patch as absolutely zero chance to get in.
Signed-off-by: Matthew Garrett [EMAIL PROTECTED]
On Friday 26 January 2007 14:51, Matthew Garrett wrote:
The dscape driver requires v4 firmware, while the mainline driver
prefers v3. Giving the two different names makes it easier to support
parallel installation. This patches fwcutter to dump v4 firmware with a
different name - the second
On Friday 26 January 2007 17:01, Matthew Garrett wrote:
On Fri, Jan 26, 2007 at 09:49:15AM -0600, Larry Finger wrote:
NACK. The --postfix switch for fwcutter, and the postfix option for
bcm43xx-d80211 driver handle
this case perfectly well.
It would be helpful to standardise - the
roucaries bastien wrote:
On 1/26/07, Larry Finger [EMAIL PROTECTED] wrote:
Does it help to down the wifi card before the s2disk?
Yes no oops but I can't associate to the network after suspend. But at
least no oops.
Did you use an ifup after resuming?
Please send me the log information
On Fri, Jan 26, 2007 at 10:03:03PM +0100, Michael Buesch wrote:
It _is_ standardized.
bcm43xx-softmac only supports v3, bcm43xx-d80211 only supports v4.
So if you want to use both drivers in parallel, use fwpostfix modparam
and install both firmware with different postfix (I use .v3 and .v4
On 1/26/07, Larry Finger [EMAIL PROTECTED] wrote:
Paul Marks wrote:
I have a BCM4311 card, and ever since the PCI-E interrupts patch, I've been
able to associate just fine with my own WPA2-PSK access point, using
wpa_supplicant with ap_scan=1.
However, the access points at my school
Paul Marks wrote:
On 1/26/07, Larry Finger [EMAIL PROTECTED] wrote:
Paul Marks wrote:
I have a BCM4311 card, and ever since the PCI-E interrupts patch,
I've been
able to associate just fine with my own WPA2-PSK access point, using
wpa_supplicant with ap_scan=1.
However, the access
22 matches
Mail list logo
