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 su
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 w
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 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 problem with symbols if softmac is enabled in the kernel.
Unless softm
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 ma
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
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 l
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 ma
On Thursday 22 March 2007 21:27, 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 component from now on?
Sure, it can be done. But it introduces b
On Thu, Mar 22, 2007 at 12:45:57PM -0400, Pavel Roskin wrote:
> Having a mac80211 driver with v3 firmware would be a first step at
> bisecting the bug, but I guess it would be very time consuming. On the
> other hand, it could replace the softmac driver eventually.
It sounds like we should consi
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 thin
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
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
[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 component from now on?
>
>
On Thu, Mar 22, 2007 at 03:55:48PM -0500, 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-mac8
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
bcm4
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
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 reso
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 resolving
> > such conflicts.
>
> We already have one - it is Linville's wi
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
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
Fernando Toledo wrote:
> I try to test if the combined patch work on the last kernel
The patch you need is at
ftp://lwfinger.dynalias.org/patches/combined_2.6.20.3.patch.
Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.ber
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 drivers/net/wireless/bcm43xx/bcm43xx_dma.c
Reversed (or previously ap
23 matches
Mail list logo
