On Wed, Jan 18, 2006 at 03:36:59PM -0500, Jeff Garzik wrote:
John W. Linville wrote:
The master branch of that tree is (mostly) up-to-date w/ Linus, plus
changes I recently sent to Jeff. Those changes are also available on
the upstream-jgarzik branch, but it is frozen to when I requested
On Thu, Jan 19, 2006 at 01:19:40AM +0100, Johannes Berg wrote:
On Wed, 2006-01-18 at 15:06 -0500, John W. Linville wrote:
The tree also has softmac and dscape branches. The softmac
branch includes the Johannes Berg softmac code as well as the the
BCM43xx driver based upon that code.
I
the bcm43xx-dscape branch.
Did you already pull? I did not see it in your git logs.
I have to do some maintainance work on my public repository
and I am waiting for your pull, before I shut down the server.
I have it now. Sorry for being slow!
John
--
John W. Linville
[EMAIL PROTECTED
Project
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Sun, Mar 05, 2006 at 09:47:55PM +0100, Michael Buesch wrote:
Please pull branches softmac-upstream and dscape-upstream
from my repository at:
git://bu3sch.de/wireless-2.6.git
Merged to softmac and dscape branches of wireless-2.6...thanks!
John
--
John W. Linville
[EMAIL PROTECTED
and recursion detection
while testing.
It has almost been two weeks...do we want this patch, or not?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
with multiple cores (APHY)
(untested)
* Fix controller restart breakage.
* Make used wireless core (phymode) selectable at runtime.
* Well, few others. Don't remember :)
Since your subject includes RFT, I'm NOT going to apply this.
Please correct me if your desire is otherwise.
Thanks,
John
--
John W
in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
bcm43xx
John W. Linville:
bcm43xx: fix-up build breakage from merging patches out of order
Larry Finger:
bcm43xx: improved statistics
Michael Buesch:
bcm43xx: suspend MAC while
:
I have applied Larry's patch to my bcm43xx branch...FYI.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://bat.berlios.de/mailman/listinfo/bcm43xx-dev
On Thu, Jul 27, 2006 at 08:37:53PM -0400, John W. Linville wrote:
As most of us are painfully aware, there is a blockage in getting
bcm43xx patches upstream.(*)
(*) http://marc.theaimsgroup.com/?l=linux-netdevm=115137403631920w=2
After re-reading that thread, I realized that Jeff had
On Mon, Jul 31, 2006 at 04:01:43PM -0400, Jeff Garzik wrote:
John W. Linville wrote:
Jeff, if a 10ms maximum delay is still acceptable to you, then please
pull from the bcm43xx branch of wireless-2.6 into the upstream branch
of netdev-2.6.
Just to be clear, 'upstream' not 'upstream-fixes
shouldn't change anything to a magic number...
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
=115075858220477w=2
Was there a newer version that I missed? Did you still want the
older version applied anyway?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman
-dscape driver.
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
.
Perhaps you should post the patch w/o WE-20 support. I'll make sure
they all get in at the same time (if at all).
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo
excited about that. Under the normal process, that would
mean 2.6.19 would be broken until we get the next patch.
When will the patch for the upstream branch be available? Can you make
that patch based on this one (i.e. apply this one before generating
the next patch)?
John
--
John W. Linville
[EMAIL
On Mon, Sep 11, 2006 at 02:59:01PM -0500, Larry Finger wrote:
John W. Linville wrote:
Also, if you could just use --- instead of a long line of ==,
I think I would have to do less manual processing...thanks!
Sorry about the === rather than ---. Is that documented somewhere?
Not too
. */
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
- what do you think?
Let's just take the new/current patch as-is. Someone who understands
rev 0x128 should be able to find the message in the code for
himself... :-)
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
descriptive of what you are sending
me, so I can know to reject big features like this one :)
I'm sorry Greg. I should have warned you about that. Did I get
copied on that patch? Anyway, I should have seen it in your -stable
review postings.
John
--
John W. Linville
[EMAIL PROTECTED
applied them last night w/o incident. They are available in the
current wireless-dev.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
the expectation
of older
out of tree wireless support (ie madwifi), sorry.
Any chance you could provide a pointer to that discussion in the archives?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
been fixed.
Does the tree you are using have this commit?
commit 6bbdce5ac755e3b3cdcf9bb9fdbcc2af78ad34d0
Author: John W. Linville [EMAIL PROTECTED]
Date: Tue Jan 2 21:22:05 2007 -0500
[PATCH] softmac: avoid assert in ieee80211softmac_wx_get_rate
Unconfigured bcm43xx device can hit
spec fix is here: http://bcm-v4.sipsolutions.net/802.11/PHY/calinit
FWIW, by inspection it looks like the mac80211-based driver is
(trying?) to implement this change.
David, have you tried the mac80211 version? Does it still have the
same crash?
John
--
John W. Linville
[EMAIL PROTECTED
On Mon, Mar 12, 2007 at 12:42:18PM -0500, Larry Finger wrote:
David Woodhouse wrote:
On Mon, 2007-03-12 at 10:53 -0400, John W. Linville wrote:
FWIW, by inspection it looks like the mac80211-based driver is
(trying?) to implement this change.
David, have you tried the mac80211 version
On Mon, Mar 12, 2007 at 04:16:34PM +0100, David Woodhouse wrote:
On Mon, 2007-03-12 at 10:53 -0400, John W. Linville wrote:
FWIW, by inspection it looks like the mac80211-based driver is
(trying?) to implement this change.
David, have you tried the mac80211 version? Does it still
both types with a defined constant. In addition, two
bits in the TM State High registers are given definitions to help in
following the code.
Looks reasonable to me -- not sure why this is an RFC? Does anyone
object?
John
--
John W. Linville
[EMAIL PROTECTED
as of yesterday. Presumably it should
be in the next -mm.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
the drivers come out, softmac comes out too. It certainly will
not be left in the kernel to support an out of kernel driver.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de
firmware. Why is this such a problem? Afterall, at one time
the mac80211 (then d80211) driver supported v3 firmware.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman
+XeeF4D8Zdi7GRjiZK3vAoqYZ78O8yNQ6bkAzpi1pKGhbffVx3bGd44Ok057V3PWVhsMjncGr5jMKiiAEQJRpDpKIB++oimQXCPHjGCxUQwesBr2V/yvL06CcBZKsupeD7hHAvo2CeVCLWCuSmcwiGM=
Date: Wed, 11 Apr 2007 08:16:59 +1000
From: stevie.glass [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
User-Agent: Icedove 1.5.0.10 (X11/20070329)
To: John W. Linville [EMAIL PROTECTED]
Subject: Re: Please pull
On Thu, Apr 12, 2007 at 09:52:17AM -0500, Larry Finger wrote:
John W. Linville wrote:
BCM43xx_LOCALE_USA_CANADA_ANZ a correct grouping?
Those categories were copied from the data in the SPROM on the BCM43xx
chips, which are obviously out of date. That said, it is likely that the
code
On Tue, Apr 17, 2007 at 10:25:08AM -0400, Dan Williams wrote:
On Tue, 2007-04-17 at 09:12 -0400, John W. Linville wrote:
On Mon, Apr 16, 2007 at 07:24:14PM -0500, Larry Finger wrote:
Michael Buesch wrote:
On Monday 16 April 2007 20:50, Larry Finger wrote:
@@ -229,6 +229,7 @@ void
no reasonable usage by drivers.
FWIW, this symbol would seem to fulfill both of those criteria.
If you do not object, I would prefer the _GPL version of the patch.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
in the wireless-dev git repository. It's not
yet in any released version of Linux.
FWIW, it should be available in Fedora 7 (due at the end of the month).
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
as the
b44 part has been thoroughly tested. I wonder if Ralf has an opinion?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Sun, May 06, 2007 at 11:44:27AM +0200, Michael Buesch wrote:
On Sunday 06 May 2007 04:00:51 John W. Linville wrote:
I had to remove
the b44 ssb changes from fedora because a) users reported problems;
Which problems were that? The 2 compile issues?
Trivial to fix if that's the only
On Sat, Jun 02, 2007 at 01:39:25PM -0500, Larry Finger wrote:
I can only guess at why FC 7 uses the mac80211 driver.
To wean people off of softmac's teat...
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
are making progress on this front.
Good job, Larry!
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
using a default value for fwpostfix.
As dwmw2 suggested, it would also be nice to fall back to an empty
fwpostfix if the firmware is not found w/ the default extension.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
or e100 vs e1000 I suppose.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Thu, Jul 26, 2007 at 12:56:20PM -0500, Larry Finger wrote:
John W. Linville wrote:
On Thu, Jul 26, 2007 at 11:33:01AM -0500, Larry Finger wrote:
A typo in the specs interchanges the branches in an if statement, which
breaks operations for a BCM4306/rev 2 that has phy-analog == 1
== to !=. Instead of reverting the other,
should it do the same thing as this?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
, I'll
state that this code has been carried in wireless-dev for months and
thereby also spent a lot of time in -mm as well as Fedora (rawhide
and F-7). The code has proven to be reasonably stable and reliable.
Acked-by: John W. Linville [EMAIL PROTECTED]
--
John W. Linville
[EMAIL PROTECTED
that, setting up a local route advertisement dæmon
(radvd) to give you site-local addresses is fairly trivial too -- and
then you can also check that Ethernet multicast is working properly.
I hacked-up the (untested) patch below -- thoughts?
---
From: John W. Linville [EMAIL PROTECTED]
[PATCH] mac80211
that
might work though that would probably involve more code to add all the right
checks.
The patch below seems to work for me w/ an otherwise stock F-7 kernel
w/ iwl3945. Thoughts?
From: John W. Linville [EMAIL PROTECTED]
[PATCH] mac80211: filter locally-originated multicast frames
In STA mode
in my eyes and b43something would be better.
Premature optimization -- if something new shows-up, let it have the
longer name...
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https
commands are
handy as well.
Those simply following the tree should learn about the --reference
option to git-clone, and should use it often. Keeping a backup of
previous git trees with any work in progress wouldn't hurt either.
Questions? Complaints? Comments?
Thanks,
John
--
John W. Linville
On Fri, Aug 17, 2007 at 02:52:56AM +0200, Johannes Berg wrote:
On Mon, 2007-08-06 at 13:05 -0400, John W. Linville wrote:
--- a/net/mac80211/ieee80211.c
+++ b/net/mac80211/ieee80211.c
@@ -3030,9 +3030,10 @@ ieee80211_rx_h_data(struct ieee80211_txrx_data *rx)
memcpy(dst, hdr
to work fine for me w/ latest wireless-dev built w/ mostly-stock
(had to change BCM43XX-MAC80211 to B43) F-7 kernel config on T41 w/ F-7.
Don't even have the %X patch.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
.\n, path);
+ return err;
}
if ((*fw)-size sizeof(struct b43_fw_header))
goto err_format;
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de
for download, as with bcm43xx-fwcutter?
It would be handy for packaging.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
. in the hopes of avoiding conflicts.
Dependencies are another matter... :-)
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
to build it just fine. Yes, I checked to make sure I had
included them in git. :-)
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
the old firmware format
to the new, so that we might add it as an upgrade tool for F8.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Wed, Aug 29, 2007 at 07:34:58PM +0200, Richard Jonsson wrote:
I can't figure out how to keep up to date with the wireless dev tree.
I've set up as told by John W. Linville in a post here and use the
everything branch.
When browsing the tree at kernel.org I see changes from 24'th
://vger.kernel.org/majordomo-info.html
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Mon, Sep 17, 2007 at 12:05:36PM -0500, Larry Finger wrote:
John W. Linville wrote:
Is this the correct patch? The first hunk conflicts with an earlier
patch (b43legacy: Fix cancellation of work queues).
John
Yes, this one is correct. The first one was without a commit message
led_index);
b43_write16(dev, B43_MMIO_GPIO_CONTROL, ctl);
- spin_unlock_irqrestore(wl-leds_lock, flags);
+ spin_unlock_irqrestore(wl-leds_lock, flags);
}
/* Callback from the LED subsystem. */
--
John W. Linville
[EMAIL PROTECTED
:
cat /sys/bus/ssb/devices/ssb0\:0/uevent
I suspect that your device's core is too new to be supported.
dmesg does show this error:
ssb: rev 6000
WARNING: at drivers/ssb/main.c:889 ssb_tmslow_reject_bitmask() (Not tainted)
Technically a warning, not an error. :-)
John
--
John W
.
Sorry, Al Viro got a patch merged before I got to yours!
Thanks anyway!
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Fri, Oct 19, 2007 at 03:47:13PM +0200, Michael Buesch wrote:
On Thursday 18 October 2007 21:53:22 John W. Linville wrote:
On Wed, Oct 17, 2007 at 06:34:03PM +0200, Michael Buesch wrote:
The remaining warning in phy.c will be fixed later.
Signed-off-by: Michael Buesch [EMAIL
.
I sent the next-to-last one to Jeff last night as a fix. The rest
will be sent to Jeff after 2.6.24-rc1 is released, in anticipation of
inclusion into 2.6.25.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
-- it works for both of mine.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
wireless bits that are a month or
so old. You may want to have him try these kernels:
http://koji.fedoraproject.org/koji/buildinfo?buildID=23734
Those at least have wireless bits that are up-to-date w/ wireless-2.6.
John
--
John W. Linville
[EMAIL PROTECTED
/wireless/b43/debugfs.c:355: warning: ‘ret’ may be used
uninitialized in this function
Signed-off-by: Frank Lichtenheld [EMAIL PROTECTED]
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Isn't this what uninitialized_var() is for?
--
John W. Linville
[EMAIL PROTECTED
that in the b44,
yet.
I did a git pull yesterday and the sprom r3 and r4 changes were in
wireless-2.6/everything.
And now, so is this one. I'll probably roll it into the main ssb
sprom patch before actually sending it to Jeff.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED
in MAINTAINERS and add
an entry to Documentation/feature-removal-schedule.txt with a When
of 2.6.26? I think that should give everyone sufficient notice...?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
Signed-off-by: John W. Linville [EMAIL PROTECTED]
---
Documentation/feature-removal-schedule.txt |9 +
MAINTAINERS|2 +-
2 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt
b/Documentation
Signed-off-by: John W. Linville [EMAIL PROTECTED]
---
Amended based on suggestions from Stefano...
Documentation/feature-removal-schedule.txt |9 +
MAINTAINERS|2 +-
drivers/net/wireless/bcm43xx/Kconfig |9 ++---
3 files changed, 16
to an
associate now trigger. I would have to advise distros and users to
always set it last in the wireless init, just before running dhclient
or whatever.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
? At this moment there are
no wireless bits in wireless-2.6 that are not in the latest Fedora
kernels in Koji. The last one I built is here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=27585
Hth!
John
--
John W. Linville
[EMAIL PROTECTED
removal. In the meantime hopefully every distribution will
have or obtain a working udev configuration. If things don't work
out as planned then we will re-evaluate.
Let's stop this now please.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx
and
forth between them.
Given a functioning udev configuration, the persistent naming even
works so that your device stays as 'eth1' when switching to and
fro bcm43xx. I really think everyone is overstating the problem.
John
--
John W. Linville
[EMAIL PROTECTED
interpreter. If you boot with acpi=off
on the kernel command line, does the device either always show-up or
never show-up between the various kernels?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https
on all the devices currently supported by b43? Or are we looking at
another b43legacy type of situation?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx
fwpostfix value...
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
for fwpostfix...
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
don't confuse suggestions (intended to be helpful) with
complaints.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
.
b43 PIO support is dead and unused code.
You merged this patch, but
After applying this patch please do
git rm drivers/net/wireless/b43/pio.h
git rm drivers/net/wireless/b43/pio.c
to remove the main PIO support code.
forgot this.
You're right -- thanks for the reminder!
--
John W
Extra:tsf=001447c239ef
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
it but not
had
opportunity to test it yet. Is this new enough to work?
This is exactly what you want.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx
On Fri, Mar 14, 2008 at 07:49:02AM -0700, Larry Finger wrote:
John W. Linville wrote:
On Fri, Mar 14, 2008 at 05:26:57PM +0530, Abhijit Hoskeri wrote:
[EMAIL PROTECTED]:~/src/wireless-testing$ git checkout --track -b
everything origin/everything
git checkout: updating paths
.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Signed-off-by: John W. Linville [EMAIL PROTECTED]
commit ffc7689ddae5cbe12bde437ae0f2b386d568b5cd
Author: Michael Buesch [EMAIL PROTECTED]
Date: Wed Feb 20 19:08:10 2008 +0100
ssb: Add support for 8bit register access
This adds
On Friday 25 April 2008, Michael Buesch wrote:
This fixes some TX/RX related locking issues.
With this patch applied, some of the PHY transmission errors are fixed.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is for 2.6.26.
--
John W. Linville
[EMAIL PROTECTED
locking issues.
With this patch applied, some of the PHY transmission errors are fixed.
ACK
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
it is a bug in 2.6.25 and .26, it
seems to have zero effect on the performance of the device and can
be delayed.
Would you prefer to have it in 2.6.26 just in case? Or might that
cause a problem somehow?
John
--
John W. Linville
[EMAIL PROTECTED
/debug/b43legacy/phy*/restart
rmmod b43legacy
It should not crash anymore at the rmmod (actually the restart should
also hang in b43legacy, as it has a deadlock, which this patch also fixes).
Anyone get a chance to test this one?
John
--
John W. Linville
[EMAIL PROTECTED
3bf0a32e22fedc0b46443699db2d61ac2a883ac4.
Hth!
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
.
This patch is upstream in John Linville's wireless-testing.git tree
as commit 86ef1ae07289c9f0aa1aa310d43653e513e6f124
...and will probably be 98a3b2fe435ae76170936c14f5c9e6a87548e3ef
in linux-2.6.git.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx
.
This is a cut-down version of 3ab4b64c46784ed83f213bf4e1b51d9c55858600
which is upstream in John Linville's wireless-testing.git tree.
...which will probably be 028118a5f09a9c807e6b43e2231efdff9f224c74
in linux-2.6.git
John
--
John W. Linville
[EMAIL PROTECTED
On Sat, Sep 06, 2008 at 08:41:05PM +0200, Michael Buesch wrote:
On Saturday 06 September 2008 20:34:02 Larry Finger wrote:
A coding error present since b43legacy was incorporated into the
kernel has prevented the driver from using the rate-setting mechanism
of mac80211. The driver has been
become more strict about
requiring regressions only after the merge window, that effectively
enforces the regressions only rule on the -stable trees as well.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev
On Wed, Sep 10, 2008 at 12:40:44AM -0600, Otto Solares wrote:
On Mon, Sep 08, 2008 at 04:54:59PM -0400, John W. Linville wrote:
On Mon, Sep 08, 2008 at 11:22:43AM -0500, Larry Finger wrote:
Greg KH wrote:
Bug fixes, not new features, it's pretty simple :)
Just bug fixes, or does
series many times. I'm sorry that it
snuck-up on you but it was on the list for quite a while.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
://linuxwireless.org/en/developers/Regulatory/CRDA), which will
get your system to provide active scanning.
Hmmm...does the user have CONFIG_WIRELESS_OLD_REGULATORY=y? That is
supposed to enable identical behavior to what we had before w/o
requiring CRDA.
John
--
John W. Linville
[EMAIL PROTECTED
*
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
John W. LinvilleLinux should be at the core
[EMAIL PROTECTED] of your
.
Based on the above, I'm dropping this patch. Please submit a
non-regressing version! :-)
John
--
John W. LinvilleLinux should be at the core
linvi...@tuxdriver.com of your literate lifestyle.
___
Bcm43xx-dev mailing list
In the firmware website you can find more information about the fw
algorithm, its interaction with Broadcom hardware and other
information that we discovered as we were writing it.
I hereby declare this to be Fully Awesome! (TM)
John
--
John W. LinvilleLinux should be at the core
linvi
1 - 100 of 124 matches
Mail list logo
