On Thu, Mar 22, 2007 at 05:02:45PM -0400, Pavel Roskin wrote:
On Thu, 2007-03-22 at 15:36 -0500, Larry Finger wrote:
I think softmac and bcm43xx-sm should be in one tarball and should be
built
together with one make invocation. Just melt the codebases together. :)
That's another
On Thu, Mar 22, 2007 at 02:35:14PM -0500, Larry Finger wrote:
Developing a V3 firmware driver for 802.11b devices doesn't seem to be
viable. From what I see in
the latest versions of the specifications, support for 802.11b devices is
disappearing from the
Broadcom drivers. Thus, I think a
On Thursday 22 March 2007 20:35, Larry Finger wrote:
Michael Buesch wrote:
On Thursday 22 March 2007 13:58, John W. Linville wrote:
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
On Thursday 22 March 2007 21:55, Larry Finger wrote:
Michael Buesch wrote:
Ah, and yeah. There is the issue of symbol clashes with bcm43xx-mac80211.
Is that an issue when built modular? We should make life of distributors
easy by allowing both bcm43xx-sm and bcm43xx-mac80211 be loaded at
On Thursday 22 March 2007 22:09, Larry Finger wrote:
Based on Michael's comments, I think it would be easier to teach
bcm43xx-softmac to work with
mac80211 than it would be to put V3 firmware back in bcm43xx-mac80211. Do you
agree Michael?
Putting v3 support into bcm43xx-mac80211 is not an
On Thursday 22 March 2007 22:02, Pavel Roskin wrote:
It will be easy enough to change bcm43xx-sm names to avoid
them.
s/bcm43xx/bcm4301/
or something like that
I'd vote for that name change, yes.
--
Greetings Michael.
___
Bcm43xx-dev mailing
On Thu, 2007-03-22 at 08:58 -0400, John W. Linville wrote:
Although it's unfortunate that I cannot test dadwifi and bcm43xx on the
same kernel. It's quite bad, especially on the slow G3 PowerMac.
Why not? The wireless-dev kernel still has the softmac bcm43xx driver,
as well as the
On Thu, 2007-03-22 at 16:19 -0500, Larry Finger wrote:
Compiling both as modules, I didn't get any messages about duplicate symbols.
Did I miss something?
That's correct. I thought your concern was about conflicts if both
drivers are linked into the kernel.
But what's needed now is a
Michael Buesch wrote:
On Thursday 22 March 2007 22:02, Pavel Roskin wrote:
It will be easy enough to change bcm43xx-sm names to avoid
them.
s/bcm43xx/bcm4301/
or something like that
I'd vote for that name change, yes.
What about bcm43xx-bphy since the 4303 would also be supported by
John W. Linville wrote:
On Thu, Mar 22, 2007 at 12:34:52AM -0400, Pavel Roskin wrote:
On Wed, 2007-03-21 at 23:22 -0500, Larry Finger wrote:
Pavel Roskin wrote:
Maybe we could have a git repository for the softmac driver? That would
make it easy to generate new patches. git is quite good an
On Thursday 22 March 2007 13:58, John W. Linville wrote:
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?
Once mac80211 is merged we probaby need a (out of tree?) fork of the
On Thu, 2007-03-22 at 00:09 -0300, Fernando Toledo wrote:
I try to test if the combined patch work on the last kernel
ntbkragnarok:/usr/src/linux-2.6.20.3# patch --dry-run -p1
../broadcom/combined_2.6.20.2.patch
patching file drivers/net/wireless/bcm43xx/bcm43xx_main.c
patching file
Pavel Roskin wrote:
Maybe we could have a git repository for the softmac driver? That would
make it easy to generate new patches. git is quite good an resolving
such conflicts.
We already have one - it is Linville's wireless-2.6 git tree. My patches are
just for those who
choose not to
13 matches
Mail list logo
