Re: Fwd: [PATCH] bcm43xx: (hopefully) fix watchdog timeouts.

On Wednesday 25 October 2006 02:37, John W. Linville wrote: > Michael, > > It looks like you have a patch that I don't have, one that moves the > netif_tx_disable and spin_lock_irqsave outside of the "if (badness > > BADNESS_LIMIT)" conditional. > > Could you pass that one along as well, or corre

Please pull bcm43xx-d80211 features and bugfixes

Hi John, Please pull latest bcm43xx-d80211 features and bugfixes. git pull http://bu3sch.de/git/wireless-dev.git for-linville This will introduce hardware encryption for everything but TKIP on v4 firmware. For v3 firmware or TKIP it will transparently fall back to software encryption. It also fi

Re: Back On-line

On Friday 27 October 2006 18:01, Larry Finger wrote: > That fix is > destined for both wireless-2.6 (and 2.6.19-rcX), and 2.6.18.Y (Y=2?). I am doing a fix for wireless-2.6. This fix will be a little bit more complex. Current patch submitted to -stable fixes the problem, but also modifies the wat

Re: master mode support?

On Saturday 28 October 2006 09:16, Mike Mohr wrote: > Hello, > > I'd like to inquire about the status of master mode w.r.t the bcm43xxx > driver. I see that there was some noise about this on the mailing > list some time ago, but it appears to be (from what I can tell) > incomplete. I don't thin

Re: Null pointer error in wireless-dev

On Saturday 28 October 2006 02:55, Jeff Williams wrote: > Hello, and thanks for the great driver! > > For the past month of so, linville's wireless-dev has been crashing on > bringing up bcm43xx_d80211 (unless of course I'm not understanding how git > updates and I've been pulling it wrong). Until

Re: 4311 without CC and/or PCI core?

On Saturday 28 October 2006 14:06, Johannes Berg wrote: > On Sat, 2006-10-28 at 13:52 +0200, Tobias Diedrich wrote: > > > is it possible to have bcm43xx-device without CC or PCI core? > > yes. it isn't the case here though. > > > on my WRT54GL v1.1 I get the following output > > That is probabl

Please pull bcm43xx-d80211 bugfixes

Hi John, Please git pull http://bu3sch.de/git/wireless-dev.git for-linville This will pull the following things since my last pull request: Michael Buesch: bcm43xx-d80211: Fix DMA engine TX buffer unmap crash. bcm43xx-d80211: Don't ignore return value of pci_enable_d

Re: [PATCH] bcm43xx: Fix low-traffic netdev watchdog TX timeouts

On Sunday 29 October 2006 10:11, Hendrik Sattler wrote: > Am Sonntag 29 Oktober 2006 09:50 schrieb Johannes Berg: > > On Sun, 2006-10-29 at 09:19 +0100, Hendrik Sattler wrote: > > > Is this patch also available for 2.6.18.x? > > > > quoting Larry: > > "BTW, that simplified version has been sent to

Re: [PATCH] bcm43xx: Fix low-traffic netdev watchdog TX timeouts

On Sunday 29 October 2006 16:58, Hendrik Sattler wrote: > Am Sonntag 29 Oktober 2006 14:30 schrieb Michael Buesch: > > Complete dmesg with all debugging enabled, please. > > $ grep DEBUG /boot/config-$(uname -r) | grep -v ^# > CONFIG_IEEE80211_SOFTMAC_DEBUG=y > C

Re: bcm43xx stops passing traffic on FC6

On Sunday 29 October 2006 17:28, Gregory Gulik wrote: > > I recently updated a compaq notebook to Fedora Core 6 which has the > bcm43xx driver in the 2.6.18 kernel. I followed the instructions here: > Installing Fedora Core 6 on Compaq Presario R3000Z >

Re: ASSERTION FAILED

On Tuesday 31 October 2006 07:45, nfrench wrote: > Larry Finger wrote: > > nfrench wrote: > >> I have been tring to get my bcm43xx working with the following system > >> > >> amd_x64 > >> kernel 2.6.18.1 > >> > >> patches > >> > >> patch_2.6.18.1_fix_leds > >> patch_2.6.18.1_signal_quality > >> pat

Re: ASSERTION FAILED

On Tuesday 31 October 2006 01:35, nfrench wrote: > Thanks for comments so far up and working. > > I have noticed that I am now getting the following messages > > APIC error on CPU0: 40(40) > > while wireless is enabled, is this just noise from the wireless causing > the APIC to hicup ? I saw

Re: [PATCH] bcm43xx: fix unexpected LED control values in BCM4303 sprom

le > patch. It is good, however, that you pushed the patch upstream. > > John W. Linville wrote: > > On Wed, Oct 18, 2006 at 04:37:08PM +0200, Michael Buesch wrote: > > > >>> @@ -257,7 +263,11 @@ void bcm43xx_leds_update(struct bcm43xx_ > >>&g

Re: [RFC] bcm43xx: Removal of "badness" variable

On Wednesday 01 November 2006 21:30, Larry Finger wrote: > Michael, > > The "badness" variable and the concept of BADNESS_LIMIT were useful during > the debugging of the > preemptible periodic work routines, but now that those problems seem to be > fixed, I propose > simplifying that section of

Re: [RFC] Update to power control function for b/g phys

On Thursday 02 November 2006 17:44, Danny van Dyk wrote: > Hi guys, > > as I'm a bit out of work on this, I'd like to post this patch as RFC first. It > brings the power control routine on par with > > http://bcm-specs.sipsolutions.net/InitPowerControl > > but it contains a huge FIXME() where

Re: [PATCH 2/4] bcm43xx-d80211: Add wireless statistics

On Thursday 02 November 2006 19:46, Larry Finger wrote: > These patches modify bcm43xx-d80211 to use the wireless statics added in > patch 1. > > Signed-Off-By: Larry [EMAIL PROTECTED]> Signed-off-by: Michael Buesch <[EMAIL PROTECTED]> > --- > > Please apply

Re: [PATCH 1/4] d80211: Add wireless statistics

On Thursday 02 November 2006 22:13, Larry Finger wrote: > Hendrik Sattler wrote: > > Am Donnerstag 02 November 2006 19:45 schrieb Larry Finger: > >> This patch modifies d80211 to support wireless statistics. > > > > Just a short question, since git is quite a bit different than e.g. > > subversio

Re: broadcom pcmcia card supported?

On Sunday 05 November 2006 14:07, Christian Hoffmann wrote: > Hello, > > I have a broadcom pcmcia wifi card. Is this supported by the bcm43xx driver? > > r2d2 ~ # cat /sys/bus/pcmcia/devices/0.0/prod_id1 > Broadcom > r2d2 ~ # cat /sys/bus/pcmcia/devices/0.0/prod_id2 > 802.11g PCMCIA > r2d2 ~ # ca

Re: broadcom pcmcia card supported?

On Sunday 05 November 2006 15:20, Hendrik Sattler wrote: > Am Sonntag 05 November 2006 15:01 schrieb Michael Buesch: > > On Sunday 05 November 2006 14:07, Christian Hoffmann wrote: > > > I have a broadcom pcmcia wifi card. Is this supported by the bcm43xx > > > driver?

Re: broadcom pcmcia card supported?

On Sunday 05 November 2006 15:20, Christian Hoffmann wrote: > On Sunday 05 November 2006 15:01, Michael Buesch wrote: > > On Sunday 05 November 2006 14:07, Christian Hoffmann wrote: > > > Hello, > > > > > > I have a broadcom pcmcia wifi card. Is this s

Re: [PATCH] bcm43xx: Add error checking in bcm43xx_sprom_write()

xx_pci_write_config32()'s? Whoops, I thought I had fixed this bug long time ago. The patch is correct. > Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> > Signed-off-by: Larry Finger <[EMAIL PROTECTED]> Signed-off-by: Michael Buesch <[EMAIL PROTE

Re: Any problems with bcm43xx-softmac?

On Friday 10 November 2006 19:41, Larry Finger wrote: > As of this morning, the last two bug fixes on my list were pushed from Jeff > Garzik to Andrew Morton > and Linus Torvalds for inclusion in -mainline (2.6.19-rcX). In addition, all > but one of the > enhancements that I have sent to Linvil

Re: Any problems with bcm43xx-softmac?

On Monday 13 November 2006 19:02, Will Dyson wrote: > On 11/10/06, Larry Finger <[EMAIL PROTECTED]> wrote: > > As of this morning, the last two bug fixes on my list were pushed from Jeff > > Garzik to Andrew Morton > > and Linus Torvalds for inclusion in -mainline (2.6.19-rcX). In addition, > > a

Re: bug report : dscape bcm43xx on linksys WRT54G

On Monday 13 November 2006 23:45, Vincent Danjean wrote: > Index: dscape-ieee80211/src/wireless-dev/ssb/ssb.c > === > --- dscape-ieee80211.orig/src/wireless-dev/ssb/ssb.c 2006-11-13 > 02:00:02.0 +0100 > +++ dscape-ieee80211/s

Re: bcm4318

On Tuesday 14 November 2006 23:51, Joseph Jezak wrote: > Jory A. Pratt wrote: > > Well after doing a serious upgrade on my line I discovered just how > > bad off the bcm4318 truely is. I have a 3Mbp/s line and with bcm4318 I > > am lucky if I can utilize a 1/3rd of that. ( i.e <=1.0Mbps ) Those

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

On Wednesday 15 November 2006 20:01, Ray Lee wrote: > Suggestions? Requests for even more info? Yeah, enable bcm43xx debugging. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/b

[PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast)

This fixes various bcm43xx-d80211 hwcrypto issues, which mainly prevented mcast frames from being decrypted properly. This is mostly a rewrite of the key managing code. Note that after this patch v3 firmware is no longer supported. Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>

Re: [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast)

On Thursday 16 November 2006 16:22, Hendrik Sattler wrote: > Am Donnerstag 16 November 2006 15:07 schrieb Michael Buesch: > > Note that after this patch v3 firmware is no longer supported. > > The the firmware files for v3 and v4 have different names? > If not, that wou

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

On Thursday 16 November 2006 19:17, Larry Finger wrote: > Ray Lee wrote: > > Larry Finger wrote: > >> Ray Lee wrote: > >>> Michael Buesch wrote: > >>>> On Wednesday 15 November 2006 20:01, Ray Lee wrote: > >>>>> Suggestions? Requ

Re: ibook issues

On Saturday 18 November 2006 18:56, Marco wrote: > Hi all, > i have just reinstalled Ubuntu Edgy on my ibook g4 (12'') with an > Airport Express card. > > The first thing that puzzled me is that the fwcutter doesn't recognize > the AppleAirport2 file from MacOS X to get the firmware to be put in >

Re: BCM4318, come on guys :-)

On Sunday 19 November 2006 04:24, Larry Finger wrote: > Ramanalinarivo Sandrinah Vonisoa Annie wrote: > > Hi, > > I just post this to encourage guys to fix problems on 4318 chipset. > > I have a 32bit (Celeron M) Acer 3630 (notebook), and "lspci": > > > > 00:0b.0 Network controller: Broadcom C

Re: BCM4318, come on guys :-)

On Sunday 19 November 2006 20:54, evan foss wrote: > I would just like to express my gratitude that anyone is working on > this. I have a 4311 card built into my laptop and while it still does > not actually work I am grateful for all the work done on it. The fact > that the developers have gotten

Re: [PATCH] softmac: remove netif_tx_disable when scanning

On Sunday 26 November 2006 11:03, Johannes Berg wrote: > On Sat, 2006-11-25 at 23:05 -0500, Daniel Drake wrote: > > > Surely disabling the queue actually makes sense, in order to avoid > > frames designated for the "current session" being transmitted on > > different channels during scanning? >

Re: [PATCH] softmac: remove netif_tx_disable when scanning

On Sunday 26 November 2006 05:05, Daniel Drake wrote: > Larry Finger wrote: > > In the scan section of ieee80211softmac, network transmits are disabled. > > Clearly, this does not make any sense as transmit is necessary for active > > scanning, and transmits are not used when passive scanning. > >

Re: [PATCH] softmac: remove netif_tx_disable when scanning

On Sunday 26 November 2006 14:05, Larry Finger wrote: > Michael Buesch wrote: > > On Sunday 26 November 2006 11:03, Johannes Berg wrote: > >> On Sat, 2006-11-25 at 23:05 -0500, Daniel Drake wrote: > >> > >>> Surely disabling the queue actually makes

Re: [PATCH] softmac: remove netif_tx_disable when scanning

cial for > zd1211rw, currently we have a semi-ugly implementation inside the driver. > > > Also, for bcm43xx this isn't a problem since the firmware (optionally > > but we use that afaik) takes care of not transmitting frames that are > > tagged for a different chann

Re: [PATCH take2] softmac: remove netif_tx_disable when scanning

On Monday 27 November 2006 21:37, Larry Finger wrote: > From: Michael Buesch <[EMAIL PROTECTED]> > > In the scan section of ieee80211softmac, network transmits are disabled. > When SoftMAC re-enables transmits, it may override the wishes of a driver > that may have very good

Re: Progress report

On Wednesday 29 November 2006 15:55, Larry Finger wrote: > Erik Mouw wrote: > > On Wed, Nov 29, 2006 at 12:00:49PM +0100, Florian Fainelli wrote: > >> Le mercredi 29 novembre 2006 07:54, Larry Finger a écrit : > >>> When using the standard bcm43xx-softmac software and transmitting with CCK > >>> mo

Re: 4311 and pcie patch results

On Saturday 02 December 2006 00:51, Larry Finger wrote: > Fernando Toledo wrote: > > > > hi! =( > > im not using ndiswrapper.. > > i have a realtek pcmcia with kismet a cant see anything > > The reason you don't see anything is that your radio is not turned on. At the > moment, bcm43xx does > n

Re: 4311 and pcie patch results

On Saturday 02 December 2006 16:49, Larry Finger wrote: > Michael Buesch wrote: > > On Saturday 02 December 2006 00:51, Larry Finger wrote: > >> Fernando Toledo wrote: > >>> hi! =( > >>> im not using ndiswrapper.. > >>> i have a realtek pcmc

Re: HW enable patch

On Saturday 02 December 2006 18:23, Larry Finger wrote: > Does this patch make your radio come on without any special tricks? > > If it does, we will then be able to go for actually using the RF button. > > Larry > Next time please inline the patch, so it's easier to comment on. > Index: wirel

Re: RFC/T: bcm43xx: report radio hardware status

On Tuesday 05 December 2006 18:56, Larry Finger wrote: > The patch below implements a function to obtain the status of the hardware > enable bit of the radio, > and report this status to the log when the core is initialized. It also > places code in the periodic > work handler to report any chang

Re: RFC/T: bcm43xx: report radio hardware status

On Tuesday 05 December 2006 19:42, Larry Finger wrote: > >> +static inline > >> +int bcm43xx_is_hw_radio_enabled(struct bcm43xx_private *bcm) > >> +{ > >> + /* function to return state of hardware enable of radio > >> + * returns 0 if radio disabled, 1 if radio enabled > >> + * This routine MU

Re: [PATCH] softmac: Fixed handling of deassociation from AP

On Wednesday 06 December 2006 15:45, Larry Finger wrote: > From: Ulrich Kunitz <[EMAIL PROTECTED]> > > A deauthentication from the AP doesn't start a reassociation by > SoftMAC. To fix this mac->associnfo.associating must be set and the > ieee80211softmac_assoc_work function must be scheduled. >

Re: [PATCH] softmac: Fixed handling of deassociation from AP

On Wednesday 06 December 2006 21:17, Ulrich Kunitz wrote: > On 06-12-06 18:52 Michael Buesch wrote: > > > All data in mac->associnfo is protected by mac->associnfo->mutex > > and _not_ mac->lock. > > Are you sure? Yes I am. > One can find

Re: [PATCH] softmac: Fixed handling of deassociation from AP

On Wednesday 06 December 2006 22:51, Ulrich Kunitz wrote: > On 06-12-06 21:52 Michael Buesch wrote: > > > On Wednesday 06 December 2006 21:17, Ulrich Kunitz wrote: > > > On 06-12-06 18:52 Michael Buesch wrote: > > > > > > > All data in mac->as

Re: [PATCH] softmac: Fixed handling of deassociation from AP

On Thursday 07 December 2006 01:36, Larry Finger wrote: > it seems to > me that the mutex protects only the association data; whereas the spinlock > protects more data, but > does include the association data. Nope. The same way you could argue that the BKL should be taken here, as it's "the g

Re: HW enable patch (V3)

On Thursday 07 December 2006 16:32, Larry Finger wrote: > Please note that we do know how to operate > the LEDs, Well, is it probably connected to some GPIO? And must be switched like any other LEDs, but this one depending on the radio-hwenabled bit? > It is really tough that none of the develop

Re: HW enable patch (V3)

On Thursday 07 December 2006 18:34, Jochen Puchalla wrote: > [Donnerstag, 7. Dezember 2006 16:58] schrieb Michael Buesch (wrote): > > On Thursday 07 December 2006 16:32, Larry Finger wrote: > > > Please note that we do know how to operate > > > the LEDs, > > >

Re: RFC/T: bcm43xx: report radio hardware status

On Friday 08 December 2006 16:55, Larry Finger wrote: > Carlo Marcelo Arenas Belon wrote: > > > >> Michael Buesch wrote: > >>>> @@ -3254,6 +3258,12 @@ static void bcm43xx_periodic_work_handle > >>>>

Re: Lockups on Apple G4 PowerBooks/iBooks?

On Saturday 09 December 2006 08:56, Erik Chakravarty wrote: > and we suspect it is the bcm43xx driver or softmac > that is causing this. Why? -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mail

Re: Lockups on Apple G4 PowerBooks/iBooks?

On Saturday 09 December 2006 16:01, Erik Chakravarty wrote: > I take it that this is not a problem known to be associated with the > bcm43xx driver then, which means I will have to do some further testing. > > The problem in diagnosing this is that it's difficult to see log output > once the machi

Re: PCIE cards with dscape

On Monday 11 December 2006 02:15, Matthew Garrett wrote: > Do the PCI-E cards have the same issues as the 4318 chipset? I think so, yes. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/li

Re: RFC/T: bcm43xx: report radio hardware statusa (V2)

On Monday 11 December 2006 11:33, Carlo Marcelo Arenas Belon wrote: > On Sun, Dec 10, 2006 at 04:12:45PM -0600, Larry Finger wrote: > > This version of the patch not only reports the status of the > > hardware-enabled flag, but it also sets > > the LED's 2 and 3 with opposite states. > > why?, is

Re: ieee80211 sleeping in invalid context

ags); \ 044 __raw_spin_lock(&(lock)->raw_lock); \ 045 DEBUG_LOCKS_WARN_ON(l->magic != l); \ 046 } while (0) Which kernel are you using? There is some locking breakage in latest kernels with softmac. I attached the fixes for the known bu

Re: bcm4311 softmac assertion

On Thursday 14 December 2006 19:34, Fernando Toledo wrote: > when ifconfig eth1 up on 2.6.19 from kernel.org > > > SoftMAC: ASSERTION FAILED (0) at: > net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate() > bcm43xx: PHY connected > bcm43xx: Microcode rev 0x127, pl 0xe (20

[PATCH 2/2] bcm43xx-d80211: Fix for PHYmode API change.

This fixes the PHYmode list API breakage for the bcm43xx-d80211 driver. Signed-off-by: Michael Buesch <[EMAIL PROTECTED]> Index: bu3sch-wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx.h === --- bu3sch-wireless-de

[PATCH 1/2] d80211: Turn PHYmode list from an array into a linked list

This turns the PHY-modes list into a linked list. The advantage is that drivers can add modes dynamically, as they probe them and don't have to settle to a given arraysize at the beginning of probing. Signed-off-by: Michael Buesch <[EMAIL PROTECTED]> -- Note that I will also send fi

Re: bcm4311: card up but scan fails

On Thursday 14 December 2006 22:08, Fabian Förg wrote: > Larry Finger wrote: > > There isn't any hardware in the interface that lets us turn it on, > > thus we don't know. None of the developers have your hardware. You can > > try pushing the button, or whatever. If you find some special > > inc

Re: [PATCH 1/2] d80211: Turn PHYmode list from an array into a linked list

On Friday 15 December 2006 14:48, Jiri Benc wrote: > On Thu, 14 Dec 2006 19:20:11 +0100, Michael Buesch wrote: > > This turns the PHY-modes list into a linked list. > > The advantage is that drivers can add modes dynamically, as they probe > > them and don't have to sett

Re: [PATCH 1/2] d80211: Turn PHYmode list from an array into a linked list

On Friday 15 December 2006 15:06, Jiri Benc wrote: > On Fri, 15 Dec 2006 14:54:55 +0100, Michael Buesch wrote: > > Can you also apply the bcm43xx fix for this to your tree? > > I think that should be easiest and prevent long-living breakage. > > It doesn't apply :-( It&

Re: [PATCH 1/2] d80211: Turn PHYmode list from an array into a linked list

On Friday 15 December 2006 15:06, Jiri Benc wrote: > On Fri, 15 Dec 2006 14:54:55 +0100, Michael Buesch wrote: > > Can you also apply the bcm43xx fix for this to your tree? > > I think that should be easiest and prevent long-living breakage. > > It doesn't apply :-( It&

Re: [PATCH 1/2] d80211: Turn PHYmode list from an array into a linked list

On Saturday 16 December 2006 07:40, Michael Wu wrote: > On Thursday 14 December 2006 13:20, Michael Buesch wrote: > > -int ieee80211_update_hw(struct ieee80211_hw *hw) > > +int ieee80211_register_hwmode(struct ieee80211_hw *hw, > > + struct ieee80211_h

Re: oops in bcm43xx_destroy_dmaring - 4318 mini-pci & d80211

On Thursday 21 December 2006 01:07, Steve Brown wrote: > I'm using a recent snap (wpa_supplicant-0.6-2006-12-11) and the current > wireless-dev w/ the PHYmode mods backed out so bcm43xx-d80211 compiles. WTF is "PHYmode mods backed out so bcm43xx-d80211 compiles"?? -- Greetings Michael. __

Re: bcm43xx-softmac code to handle (at least one) iface with an rfkill switch

On Thursday 21 December 2006 17:01, Matthew Garrett wrote: > On Wed, Dec 20, 2006 at 03:08:58PM -0600, Larry Finger wrote: > > + radio_hw_enable = bcm43xx_is_hw_radio_enabled(bcm); > > + if (unlikely(bcm->radio_hw_enable != radio_hw_enable)) { > > + bcm->radio_hw_enable = radio_hw_ena

Re: oops in bcm43xx_destroy_dmaring - 4318 mini-pci & d80211

On Thursday 21 December 2006 01:07, Steve Brown wrote: > I'm using a recent snap (wpa_supplicant-0.6-2006-12-11) and the current > wireless-dev w/ the PHYmode mods backed out so bcm43xx-d80211 compiles. > The module (WL-120G V2A) is from an ASUS wl500-gp and installed in x86 > development machi

[PATCH] bcm43xx-d80211: Fix DMA TX skb doublefree

This fixes a possible double-free of the TX skb buffers. Always NULL the pointer after freeing. Signed-off-by: Michael Buesch <[EMAIL PROTECTED]> Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx_dma.c === --- wi

The new SSB subsystem for bcm43xx (and others)

This is a development snapshot of the new Sonics Silicon Backplane subsystem I am currently designing. A port of the bcm43xx driver is included and it works (more or less). There are still some things left and broken (most are marked with TODO or FIXME). This is just a snapshot for you to look at

Re: Lockups on Apple G4 PowerBooks/iBooks?

On Friday 22 December 2006 04:42, Erik Chakravarty wrote: > Update on this issue: I've just experienced another hang and this time > the following messages were written just as the keyboard stopped > responding and the OS couldn't execute any programs: > > > Dec 22 03:23:10 localhost kernel: [ 30

Re: [PATCH] bcm43xx: Interrogate hardware-enable switch and update LEDs

On Friday 29 December 2006 21:00, 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 enabled bit in the interface, logs the initial state and any > changes

Re: [PATCH] bcm43xx-d80211: Interrogate hardware-enable switch and update LEDs

ccepted into mainline > some time ago. > > Signed-off-by: Larry Finger <[EMAIL PROTECTED]> Signed-off-by: Michael Buesch <[EMAIL PROTECTED]> > --- > > Michael, > > This patch is for wireless-idev, and is the same as the patch recently > submitted for bc

Re: BCM4311 problems

On Saturday 06 January 2007 03:28, Larry Finger wrote: > Michael, > > With your experience with the bcm43xx and other drivers, I hope you can help > me. With my new Turion > 64 X2 laptop with a Dell 1390 (BCM4311) wireless card, I am getting no > transmissions. I don't know > about received data

What is in bcm43xx-wireless-dev.git?

In case you wonder what's the future of bcm43xx, here's a list of changes in my bcm43xx development tree: bcm43xx-d80211: Add some PHY register definitions. bcm43xx-d80211: Move ILT stuff to OFDM table stuff bcm43xx-d80211: Remove PHY OFDM routing bit, if we are on A-PHY. b

Re: [PATCH] bcm43xx: Fix failure to deliver PCI-E interrupts

On Friday 12 January 2007 18:54, Stephen Sinclair wrote: > > That's redundant. If it's not a PCI core, it must be a PCIE core. > > Not to be too blunt, but isn't that sort of sloppy logic? > Imho it's always better to check what something _is_ rather than what > something _isn't_. > The two are on

Re: Various patches for PCI-E and radio-enable switches

On Friday 12 January 2007 20:22, Larry Finger wrote: > As noted in this list earlier today, there is now a patch that makes PCI-E > interfaces work. It has > only been tested with Dell Wireless 1390 cards (BCM4311), but should also > work for BCM4312s. The > receive level for the 4311 is excellen

Re: Various patches for PCI-E and radio-enable switches

On Friday 12 January 2007 21:26, Larry Finger wrote: > Michael Buesch wrote: > > On Friday 12 January 2007 20:22, Larry Finger wrote: > >> As noted in this list earlier today, there is now a patch that makes PCI-E > >> interfaces work. It has > >> only been

Re: What is in bcm43xx-wireless-dev.git?

On Friday 12 January 2007 08:25, Pavel Roskin wrote: > Hello, Michael! > > I've tried the master branch of bcm43xx-wireless-dev.git for the first > time. The results are not encouraging so far (although I'm quite new to > this chipset). > > drivers/ssb/driver_mips/mips.c includes asm/time.h, whi

Re: [PATCH] bcm43xx: Fix failure to deliver PCI-E interrupts

On Friday 12 January 2007 05:52, Larry Finger wrote: > The PCI-E modifications to bcm43xx do not set up the interrupt vector > correctly. > > Signed-off-by: Larry Finger <[EMAIL PROTECTED]> > --- > > John, > > This fix should be applied to wireless-2.6 _AND_ pushed upstream to > 2.6.20-rcX. With

Re: [PATCH] bcm43xx: Fix failure to deliver PCI-E interrupts

On Friday 12 January 2007 17:36, Larry Finger wrote: > Michael Buesch wrote: > > I have one general question before I address your comments. Does a BCM43xx > chip always have either a > PCI or a PCI-E core? I've seen discussion on this list that makes me wonder. >

Re: [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts

On Friday 12 January 2007 19:08, Larry Finger wrote: > The PCI-E modifications to bcm43xx do not set up the interrupt vector > correctly. Tested with BCM4311 (PCI-E) on x86_64 and BCM4306 (PCI) on i386. > > Signed-off-by: Larry Finger <[EMAIL PROTECTED]> ACK. > --- > > John, > > This fix shoul

Re: [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts

On Friday 12 January 2007 19:50, Stephen Sinclair wrote: > > The PCI-E modifications to bcm43xx do not set up the interrupt vector > > correctly. Tested with BCM4311 (PCI-E) on x86_64 and BCM4306 (PCI) on i386. > > This was successful for me. My 4311 is now getting interrupts, and I > was able to

Re: What is in bcm43xx-wireless-dev.git?

On Saturday 13 January 2007 08:45, Pavel Roskin wrote: > Quoting Michael Buesch <[EMAIL PROTECTED]>: > > > > drivers/ssb/driver_mips/mips.c includes asm/time.h, which is missing on > > > x86_64. It also refers to struct ssb_serial_ports, which is not define

Re: Various patches for PCI-E and radio-enable switches

On Friday 12 January 2007 22:13, Larry Finger wrote: > Daniel wrote: > > I know it's working out of the box, but could I still make a developper > > happy with an asus wl-100g? Recently replaced it with a Netgear WG500T > > What is the chip in the wl-100g? The web told me it is Broadcom, but not

Re: What is in bcm43xx-wireless-dev.git?

On Saturday 13 January 2007 20:30, Pavel Roskin wrote: > Quoting Michael Buesch <[EMAIL PROTECTED]>: > > > I looked more closely at it, but I really can't see why it oopses. > > Any idea what's happening there? > > I haven't looked at the code

Re: What is in bcm43xx-wireless-dev.git?

On Sunday 14 January 2007 03:10, Pavel Roskin wrote: > Quoting Michael Buesch <[EMAIL PROTECTED]>: > > > > I haven't looked at the code yet, but I tried to locate the bad commit. I > > tried > > > commit a13f85d8a8eb40dfd157ab78c2fb91b5765b7b9d, which

Re: What is in bcm43xx-wireless-dev.git?

On Sunday 14 January 2007 15:18, Pavel Roskin wrote: > Quoting Michael Buesch <[EMAIL PROTECTED]>: > > > Already done. Please pull my tree and check if it still crashes. > > The crash is gone! Thanks! Still no association though. Ok, nice. Can you send me a comp

Re: What is in bcm43xx-wireless-dev.git?

On Sunday 14 January 2007 17:39, Pavel Roskin wrote: > Quoting Michael Buesch <[EMAIL PROTECTED]>: > > > Ok, nice. > > Can you send me a complete dmesg log after you brought up the card > > and tried to assoc/send some packets? > > Attached. Ok, thanks.

Can someone please try...

...the bcm43xx driver in my tree with a 4318 chip? The code there works excellent with my 4306 now, but I can't get it to work with my 4318. It's strange, it doesn't seem to work at all. I don't seem to be able to TX and RX any packet. Not sure why. To get it, please try to avoid cloning the whole

Re: Can someone please try...

On Tuesday 16 January 2007 19:29, Pavel Roskin wrote: > On Tue, 2007-01-16 at 18:06 +0100, Michael Buesch wrote: > > ...the bcm43xx driver in my tree with a 4318 chip? > > Things are progressing for me a bit because I observed an association to > an AP with no security.

Re: Can someone please try...

On Tuesday 16 January 2007 20:00, Andreas Schwab wrote: > Michael Buesch <[EMAIL PROTECTED]> writes: > > > ...the bcm43xx driver in my tree with a 4318 chip? > > The code there works excellent with my 4306 now, but I can't > > get it to work with my 4318.

Re: Can someone please try...

On Tuesday 16 January 2007 22:50, Pavel Roskin wrote: > On Tue, 2007-01-16 at 20:23 +0100, Michael Buesch wrote: > > > A patch for that is already upstream. > > I don't see it. It's not in your tree yet. It is on its way upstream to linville. > > It's s

Re: Can someone please try...

On Wednesday 17 January 2007 00:51, Pavel Roskin wrote: > On Tue, 2007-01-16 at 23:07 +0100, Michael Buesch wrote: > > On Tuesday 16 January 2007 22:50, Pavel Roskin wrote: > > > On Tue, 2007-01-16 at 20:23 +0100, Michael Buesch wrote: > > > > > > &g

Re: [PATCH] bcm43xx: Check error returns in initialization routines

On Friday 19 January 2007 05:06, Larry Finger wrote: > A number of the calls in the initialization routines fail to check the > returned value for > errors. This patch adds the necessary checks and logs any errors found when > appropriate. ACK > Signed-off-by: Larry Finger <[EMAIL PROTECTED]> >

Re: [PATCH] bcm43xx: Fix problem with >1 GB RAM

On Saturday 20 January 2007 17:18, Larry Finger wrote: > Some versions of the bcm43xx chips only support 30-bit DMA, which means > that the descriptors and buffers must be in the first 1 GB of RAM. On > the i386 and x86_64 architectures with more than 1 GB RAM, an incorrect > assignment may occur.

Re: Can someone please try...

On Friday 19 January 2007 08:54, Pavel Roskin wrote: > Hello, Michael! > > I did more testing, and the results are following. It looks like the > oopses and panics on i386 were triggered by 4k stacks. x86_64 doesn't > have this option. > > Now that I enabled other debug options on both platform

Re: [PATCH] bcm43xx: Fix problem with >1 GB RAM

On Monday 22 January 2007 21:18, Larry Finger wrote: > When I looked at the b44 driver to see how that code handled the problem, it > used the pci-form of > the calls rather than the dma-version. Thus I switched early in the debug > process - even before I > had the necessary hardware. Once I got

Re: Can someone please try...

On Monday 22 January 2007 21:44, Pavel Roskin wrote: > Hello, Michael! > > On Mon, 2007-01-22 at 21:06 +0100, Michael Buesch wrote: > > It's obviously some stack/memory corruption. But I'm not > > sure if this is a stackoverflow. I'd rather say no, it isn

Re: Can someone please try...

On Tuesday 23 January 2007 07:14, Pavel Roskin wrote: > On Mon, 2007-01-22 at 22:00 +0100, Michael Buesch wrote: > > > No more random crashes. There is still a crash if I rmmod the driver > > > while wlan0 is up, but it's a separate issue, and it's easy to avoid &g

Re: [PATCH] bcm43xx: Fix problem with >1 GB RAM

On Tuesday 23 January 2007 16:18, Dan Williams wrote: > > At present, I have a problem getting NetworkManager to see the d80211 > > wireless interface. Once I get > > that solved, I plan to use my system to test with > 1 GB RAM on your git > > tree. In that case, I'll > > switch to the pci-form o

[PATCH resend] bcm43xx-d80211: Fix DMA TX skb doublefree

This fixes a possible double-free of the TX skb buffers. Always NULL the pointer after freeing. Signed-off-by: Michael Buesch <[EMAIL PROTECTED]> -- I already sent this patch to you on 21 Dec 2006. This is a pretty critical patch, so I'd like to make sure it's in your merge

<    1   2   3   4   5   6   7   8   9   10   >