linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	linux-wireless@vger.kernel.org, Joe Jezak <josejx@gentoo.org>,
	Daniel Drake <dsd@gentoo.org>
Subject: Re: [PATCH] softmac: use list_for_each_entry
Date: Mon, 11 Jun 2007 15:14:27 -0500	[thread overview]
Message-ID: <466DAD23.30602@lwfinger.net> (raw)
In-Reply-To: <20070611191854.GG10397@tuxdriver.com>

John W. Linville wrote:
> On Fri, Jun 01, 2007 at 09:12:49PM +0200, Johannes Berg wrote:
>> On Fri, 2007-06-01 at 10:59 -0500, Larry Finger wrote:
> 
>>> In the earlier discussion, we also concluded that the product of a conversion from softmac to 
>>> mac80211 should not be included in mainline, with the exception of the b-only code. Depending on how 
>>> long the port and testing take, and the state of bcm43xx-mac80211 at that time, a reversal of that 
>>> earlier decision may be in order.
>> I'd think that once somebody has time for it both port and testing
>> should go pretty soon, and I'd think that we can do that sooner than fix
>> the current bcm43xx-mac80211, in which case IMHO the result should be
>> included in mainline seeing that zd1211rw will probably be ready for
>> mac80211 in the .23 timeframe. That means that at that point we might
>> even be able to drop softmac already if the second straightforward (here
>> I mean without any other changes to the driver) bcm43xx port is ready :)
> 
> FWIW, I would like to see a mac80211-based port of the current
> bcm43xx driver available as soon as it is ready, without waiting to
> strip-out the non-b portions.  This should help us abandon softmac
> as soon as possible.
> 
> Plus, we may need to consider preserving the driver in its current
> form (aside from the softmac -> mac80211 port) for some time as a
> compatibility aid for those who already have working configurations
> with the "bcm43xx" driver.  Forcing a happy user to locate new firmware
> for no obvious benefit to them is not very nice (as I have learned
> so well w/ Fedora 7)...

I agree that we should do a port of the current bcm43xx driver to mac80211 ASAP. I also believe that 
it needs to include the non-b portions, particularly for the initial testing, but I have no 
objections to leaving it intact, at least until the new driver is better at operations.

Michael Wu offered to do the initial port, but I don't know what his progress has been.

Larry

      parent reply	other threads:[~2007-06-11 20:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27 14:27 [PATCH] softmac: use list_for_each_entry Akinobu Mita
2007-05-31 20:24 ` Johannes Berg
2007-06-01 15:59   ` Larry Finger
2007-06-01 19:12     ` Johannes Berg
2007-06-11 19:18       ` John W. Linville
2007-06-11 20:06         ` John W. Linville
2007-06-11 20:14         ` Larry Finger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=466DAD23.30602@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=akinobu.mita@gmail.com \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=josejx@gentoo.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).