ver writers are doing a good
job with what they've been given so far. I hope this helps to bring
the driver guys in out of the cold, and to put some weight behind
the discussions of where we need to go.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Wed, Jan 18, 2006 at 09:19:20PM +0100, Michael Buesch wrote:
> On Wednesday 18 January 2006 21:06, John W. Linville wrote:
> > The tree also has "softmac" and "dscape" branches. The "softmac"
> > branch includes the Johannes Berg softmac code as
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
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
...?
Presuming that no pristine firmware image is currently available,
does anyone have specific contacts at Broadcom who might be worth
approaching?
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
pull git://bu3sch.de/bcm43xx.git dscape-upstream
> > to pull 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
rivate *bcm);
>
> void bcm43xx_radio_set_tx_iq(struct bcm43xx_private *bcm);
> +u16 bcm43xx_radio_calibrationvalue(struct bcm43xx_private *bcm);
>
> #endif /* BCM43xx_RADIO_H_ */
> --
> Danny van Dyk <[EMAIL PROTECTED]>
> Gentoo/AMD64 Project, Gentoo Scientific Projec
ok under here:
http://people.redhat.com/linville/kernels/fedora-netdev/4/rpms/SRPMS/
--
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
deal with the issue. I don't like them,
although I am the perpetrator of at least one of them. It might be
worth looking at what was done there?
YMMV...
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists
7;t think of stupid APs. Yeah, it should handle it
> I guess.
I'm going to apply this patch as it stands. Please follow-up with
a patch to handle the TSF overflow.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing l
. IMHO we shouldn't be trying to use PHYs with unknown
> revisions.
I don't know about this one in particular, but experience w/ other
PHYs tells me that revisions can move quickly. Are you sure you
would want the driver to not work just because there is a newer PHY?
nlock lockup 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/l
or 2
> make[1]: *** [net/ieee80211] Error 2
> make: *** [net] Error 2
Make sure you are using the 'master' branch of wireless 2.6.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
shuffle wireless-2.6 to drop this patch. A new
patch that passes muster w/ Jeff will be most welcome! :-)
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
.
Please correct me if your desire is otherwise.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
uld take advantage of the
"radio button" infrastructure that Ivo van Doorn has been proposing?
Any volunteers?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
re found 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 M
current tree, is as follows:
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-netdev&m=115137403631920&w=2
After re-reading that thread, I reali
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 clea
CI memory access space
> (1GB) */
Probably 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
st:
http://marc.theaimsgroup.com/?l=linux-netdev&m=115075858220477&w=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
B
work supporting both
stack to date. I think the dscape stack would be much farther behind
w/o the users enabled by the bcm43xx-dscape driver.
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
ybe not other parts.
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://
#x27;m not too 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
--
Jo
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 === rath
/* Store the last TX/RX times here for updating the leds. */
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Sat, Sep 09, 2006 at 11:04:59AM -0500, Larry Finger wrote:
> John W. Linville wrote:
> >On Fri, Sep 08, 2006 at 08:47:54PM -0500, Larry Finger wrote:
> >
> >>PLease send this upstream for inclusion in 2.6.18, if possible. This
> >>patch will not work for
>
looking at Michael's v4 firmware revisions for d80211 with
> an eye toward porting them to softmac.
>
> John - 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
him
44 driver
(same DMA engine) for some time now on Fedora and RHEL.
John
P.S. FWIW, it _seems_ like a good idea. It is just a victim of
implementation details.
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
lowed in C99.
> Other C99 features are already used and accepted in kernel, why not this one?
Most kernel developers just don't like those comment delimiters --
simple as that. It is probably because they are a bit harder to
identify as comments than the older style, but YMMV...
Joh
, please be a little more 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]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
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 correct this patch to match
what is in Linus' tree?
Thanks,
John
On Tue, Oct
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 correct this patch to match
what is in Linus' tree?
Thanks,
John
On Tue, Oct
M43xx_LED_BCM4303_0 0x2B
> > +#define BCM43xx_LED_BCM4303_1 0x78
> > +#define BCM43xx_LED_BCM4303_2 0x2E
> > +#define BCM43xx_LED_BCM4303_3 0x19
>
> Add these to the enum below, instead, please.
> The defines above are mask
On Tue, Oct 31, 2006 at 10:34:20PM -0600, Larry Finger wrote:
> 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_
> >>> continu
that I had pulled changes that Michael had sent to
> John in te past week. If those are applied first, mine should apply cleanly.
I applied them last night w/o incident. They are available in the
current wireless-dev.
John
--
John W. Linville
[EMAIL PROTECTED]
If this means breaking 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-
).
>
> I can test another tree, e.g. wireless-2.6, if there are chances that
> the problem has 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 -05
not apply that patch".
"Pull" is often used to mean "take the patch and apply it" as in "git pull".
Let me know if I'm interpreting you incorrectly.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailin
to be init'd with g mode
> off. I'm not sure anyone has picked up this fix yet. The relevant
> 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
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.
> >
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
18), is not.
> This patch replaces 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
--
3xx_SHM_SHARED,
> > BCM43xx_UCODE_REVISION));
>
> This will crash when the device is not up.
Larry, will you be doing a new version of this patch that accounts
for this comment?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
el oops if the bcm43xx
> chip contains a USB (dangling) core. This bug has been fixed in Michael
> Buesch's tree, but
> apparently not yet in Linville's wireless-dev tree. The patch is as follows:
FWIW, that patch is in my tree as of yesterday. Presumably it should
be in the
n't freeze unregistered devices.
>
> No, that's a different fix for suspend.
>
> This is the fix:
> http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=b87f743f3643ea162892dce0bbc91e6f026a49bf
>
> Pull request was sent to John.
That's "ssb-ohci: Completely disable the driver on non-embedded
systems", also in wireless-dev as of yesterday.
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
or the day when mac80211 replaces softmac in the mainline
> > kernel. What would we
> > need to do?
Why? What value do you predict in having an out-of-tree softmac
version available? Would that effort be better spent on improving
the in-tree mac80211 version?
John
--
Jo
r the
> 4311 out of the mac80211 version. It compiled cleanly, booted up fine, loaded
> bcm43xx-softmac and is
> running correctly.
Did you "=y" the config options? That is what causes the problem
when linking the kernel image.
John
--
John W. Linville
[EMAIL PROTECTED]
On Thu, Mar 22, 2007 at 04:09:51PM -0500, Larry Finger wrote:
> John W. Linville wrote:
> > Is converting the softmac driver to mac80211 (as bcm43xx-old or
> > somesuch) really a bigger job than trying to maintain out-of-tree
> > code for both the driver and the softmac
On Thu, Mar 22, 2007 at 05:02:45PM -0400, Pavel Roskin wrote:
> But what's needed now is a working standalone driver for all supported
> cards.
Out of kernel drivers are a distraction, and IMHO should be avoided.
--
John W. Linville
[EMAI
in the kernel
for some period of time (however short that might be).
When 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]
___
Bc
wo drivers, one for v3 firmware and one for
later 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-de
we should consider this. I am not keen on keeping
softmac around indefinitely.
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
-encoding;
>
> b=c13rHvw5Z5QAZnP6CrA3+XeeF4D8Zdi7GRjiZK3vAoqYZ78O8yNQ6bkAzpi1pKGhbffVx3bGd44Ok057V3PWVhsMjncGr5jMKiiAEQJRpDpKIB++oimQXCPHjGCxUQwesBr2V/yvL06CcBZKsupeD7hHAvo2CeVCLWCuSmcwiGM=
> Date: Wed, 11 Apr 2007 08:16:59 +1000
> From: "stevie.glass" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> User-A
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 t
urrent rawhide kernels but with the most
recent round of wireless-dev updates added.
http://people.redhat.com/linville/kernels/fc7/
Any thoughts?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
[EMAIL PROTECTED]
h
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
ymbol
exports, especially those which are fundamentally internal to
in-kernel subsystems and/or have 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 PROTEC
; Yes, the module is present 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]
_
guess I don't see a problem w/ merging the mips part, as long 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?
> Triv
n this archive:
http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
Hth!
John
[1] Using bcm43xx-fwcutter, of course.
--
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
Bcm
On Sun, Jun 03, 2007 at 05:04:18PM -0500, Larry Finger wrote:
> John W. Linville wrote:
> >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
om using the v4 firmware?
Anyway, I'm glad to hear we 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
onflict. Users don't expect the need to rename firmware,
> and we shouldn't create a problem for them.
Yes, we should probably start 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 defa
wonder if that is
too prone to confusion w/ "b44"? Probably no worse than "ixgb" vs
"cxgb3" 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 01:49:58PM -0500, Larry Finger wrote:
> John W. Linville wrote:
> >
> >Hmmm...well, if you asked to revert it on bcm43xx, why is it appropriate
> >here?
>
> AFAIK, the V4 specs have always had the typo, thus there was no patch
> introduci
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
en reverted in F-7)? That one change "==" to ">", while
this one changes "==" to "!=". Instead of reverting the other,
should it do the same thing as this?
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm4
style issues that might be identified, 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 PROTE
cture -- and
> you'll see the link-local IPv6 address remains 'tentative'.
>
> Once you've fixed 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
> > I agree completely; however, I've had my "hands slapped" in the past for
> > removing that kind of
> > message. As a result, I leave them alone.
>
> Well, there are good reasons for not removing this.
> The resons include that this message is only
function 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-originate
ting
> through the system make bcm43xx-mac80211 into the preferred driver. You
> should ask Fedora how soon
> those will make it into their development kernels (called Rawhide?).
Probably tonight. Maybe earlier if you watch Koji.
John
--
John W. Linville
[EMAIL PROTECTED]
__
on the ssb info.
Excellent. This definitely sounds like the right path to keeping the
drivers straight (or "properly sorted" as the limeys might say). :-)
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@list
> b43 is more a common name 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-d
of patches in development.
The git-format-patch, git-applymbox, and git-rebase 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 w
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
iling, I would like to
> know your distro.
Seems 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]
___
ct b43_wldev *dev,
if (err) {
b43err(dev->wl, "Firmware file \"%s\" not found "
"or load failed.\n", path);
+ return err;
}
if ((*fw)->size < sizeof(struct b43_fw_header))
rball available 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
On Wed, Aug 22, 2007 at 10:25:28AM -0500, Larry Finger wrote:
> John W. Linville wrote:
> >On Sun, Aug 19, 2007 at 02:37:21PM -0500, Larry Finger wrote:
> >>Just in case you missed the details, the latest set of changes to b43
> >>queued by Michael will require
> &g
ith a wireless-dev patch that does not depend on
Dave's tree. The mm-master branch in wireless-dev has dropped those
patches which have gone to Dave M. 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
ilable
in 'everything' as well.
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Kconfig and Makefile in my tree.
I was able 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
bit rate for my BCM4311 was toggling between 18 and 24M. With the same setup,
> b43 usually is at
> either 48 or 54M. Take that Broadcom!!!
Hereby nominated for quote of the day, 2007-08-24... :-)
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm
l terms?
I'm wondering if a tool could easily convert 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
epository -- no new changes since
your clone...
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
b43legacy_wireless_core_detach(wldev);
> list_del(&wldev->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. 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
rxhdr->mac_status);
> > mactime = le16_to_cpu(rxhdr->mac_time);
> > chanstat = le16_to_cpu(rxhdr->channel);
>
> Did this one get committed yet?
Working on it now...
--
John W. Linville
[EMAIL PROTECTED]
___
s);
> + spin_lock_irqsave(&wl->leds_lock, flags);
> ctl = b43_read16(dev, B43_MMIO_GPIO_CONTROL);
> if (activelow)
> ctl |= (1 << led_index);
> else
> ctl &= ~(1 << led_index);
> b43_write16(dev,
ning, not an error. :-)
John
--
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
s patch fixes
> the problem.
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
ch or did you simply forget to apply it?
Where are you looking? It is in Linus' tree.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1a09404a2338163f181d170c7abdc2242b6c6f03
John
--
John W. Linville
[EMAIL PROTECTED]
_
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.
> > >
> >
1 - 100 of 179 matches
Mail list logo
