matter.
It might be a good idea to set the LAA bit...?
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev
is the part of the hardware
that executes the firmware.
Rafał,
Are you going to repost this series and/or respond to Michael's
comments? I tried to apply some of the ones Michael didn't comment
upon, but they seem to depend on the ones in question.
Thanks,
John
--
John W. Linville
for fixing this! Sorry I missed those bits.
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
the keyword struct in front of the references and no
separate patch is needed.
It won't even grow your current patch in the number of changed lines.
I took care of these modifications to the original patch...
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi
On Fri, Jan 22, 2010 at 01:53:11AM +0100, Rafał Miłecki wrote:
John, I hope to have patch submission fixed, please let me know if there
is anything wrong still.
This batch applied with no problems -- thanks, Rafał!
John
--
John W. LinvilleSomeday the world will need a hero
?
Probably -- I think davem is the person to ask? Infradead is probably
another option (dwmw2).
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready
send-email or find some other mailer to send
your patches -- I recommend Mutt. In any case, do not expect your
patches to get merged unless in the future unless you can rectify
this situation at your end. I just don't have the bandwidth for
dealing with crap like this.
Thanks,
John
--
John W
On Wed, Dec 23, 2009 at 04:10:35PM +0100, Rafał Miłecki wrote:
W dniu 23 grudnia 2009 15:52 użytkownik John W. Linville
If you decide to agree to commit this patch and you want to me resend
this with correct white spaces, please ping me about. For future mails
I'll use some native mailer
forwarded it to linux-wireless?
Other than that, it looks like you are mostly just moving code around.
That's fine, but there doesn't seem to be a lot of point in it
unless the rev 3+ stuff is coming soon? It probably doesn't harm
much either way...
John
--
John W. LinvilleSomeday
) B43_STAT_STARTED)
+ return 1;
+ if (b43_read16(dev, B43_MMIO_RADIO_HWENABLED_LO)
B43_MMIO_RADIO_HWENABLED_LO_MASK)
return 1;
}
--
John W. LinvilleSomeday the world will need a hero, and you
linvi
of
keeping the CPU from going into deep sleep, which increases the power usage
with
reduced battery life.
John: Any thoughts on this matter?
Missing deep sleep is bad. At the very least you need to limit that
to devices that truly need it, as Michael suggested.
John
--
John W. Linville
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo
then and it saves some memory.
You also need to alloc 4 bytes for the tail buffer (that currently is on the
stack, too).
Please make the changes Michael requested and resubmit -- I'll happily
make the adjustments to wireless-testing, etc.
John
--
John W. LinvilleSomeday the world
think the code is straightforward and easy to understand.
So is this patch right or not? Should I hold onto it for 2.6.33
(i.e. after the 2.6.32 merge window)?
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we
involve reverting this patch, applying a version without the
channel change, and applying the channel change - certainly more
confusing than the status quo.
But it is not in net-next-2.6. Please submit the patches as Michael
requested and I'll take care of the reorganization.
John
--
John W
-by: Michael Buesch m...@bu3sch.de
An earlier version was already merged. What is different here?
Please submit a new patch with just the differences.
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have
.
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman
and that actually applies?
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https
it for 2.6.32?
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de
to fix the block that has been
commented-out here?
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre
.
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
___
Bcm43xx-dev mailing list
Bcm43xx-dev
please try new
firmware with encryption and let us know if it works correctly, thanks!
Initvals and new firmware version can be found at
http://www.ing.unibs.it/openfwwf
Awesome...awesome...awesome!!!
--
John W. LinvilleSomeday the world will need a hero, and you
linvi
. Is that simply a driver patch?
John
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https
this...
John
--
John W. LinvilleLinux should be at the core
linvi...@tuxdriver.com of your literate lifestyle.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
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
.
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
*
--
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
://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
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
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
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 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
.
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
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
/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
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
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
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
.
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
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
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
.
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
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
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
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
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
? 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
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
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
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
/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
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
-- 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
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
.
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
:
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
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
://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
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
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
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
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
.\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
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
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
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
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
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
, 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
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
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
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
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
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
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
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
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
+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
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
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
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
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
1 - 100 of 124 matches
Mail list logo
