From: "John W. Linville" <linville@tuxdriver.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Henry Ptasinski" <henryp@broadcom.com>,
"Greg KH" <gregkh@suse.de>, "Rafał Miłecki" <zajec5@gmail.com>,
"Dan Carpenter" <error27@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH v2] Move brcm80211 to mainline
Date: Wed, 31 Aug 2011 10:18:00 -0400 [thread overview]
Message-ID: <20110831141800.GB2474@tuxdriver.com> (raw)
In-Reply-To: <4E5E214E.2060109@hauke-m.de>
On Wed, Aug 31, 2011 at 01:55:58PM +0200, Hauke Mehrtens wrote:
> If brcmsmac gets merged it should support all braodcom softmac wireless
> devices with ieee80211n support, this includes also the N-PHY devices
> with SB-bus, otherwise ieee80211n support has to be added to b43 and
> then I do not see any advantage over just using b43 and removing
> brcmsmac. Will Broadcom support these older chip in brcmsmac and also
> all new devices still missing now or has the community to add support
> for these devices without any help by broadcom?
This requirement seems rather artificial. Vendors choose which devices
they want to support. Intel has abandoned devices (e.g. ipw2100,
ipw2200, and iwlegacy), and arguably so has Atheros (e.g. ath5k).
Why should Broadcom be compelled to support older devices simply
because there is some overlap between brcmsmac and b43? If they went
down that path, would you then demand that they support the b43legacy
devices as well? Why not?
The strategy of cramming all vaguely similar devices under "one"
driver doesn't have a great track record IMHO. We have had to split
iwlwifi, and may have to do so again. e1000 got split similarly,
as did b43/b43legacy. I see no reason to compel a driver to support
an extended range of hardware when there are reasonable dissimilarities
between the devices.
> What are your plans in updating the PHY code in brcmsmac? As Rafał
> mentioned your closed source linux wifi driver (wl) is ~6 months ahead
> of brcmsmac now.
For the last ~6 months the Broadcom team has been working on getting
their driver out of staging. I have to believe that they would have
rather been working on updating device support during that time. I can
only presume that they would make that a priority in the long run.
How many times has b43 been > ~6 months behind on it's hardware
support? Despite Rafał's recent heroic efforts at improving that,
I can't help but wonder how long will it be before b43 is again
dreadfully behind?
> Are you planing to replace your closed source linux driver with brcmsmac
> on normal x86 desktops and Linux SoCs and will you support brcmsmac as
> you did before with wl?
I'm guessing that their customers will decide this for them, if we
allow the customers to have a reasonable choice.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-08-31 14:30 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 0:20 [RFC] Move brcm80211 to mainline Henry Ptasinski
2011-07-07 0:40 ` Rafał Miłecki
2011-07-07 0:58 ` Pavel Roskin
2011-07-07 1:45 ` Greg KH
2011-07-07 14:46 ` Henry Ptasinski
2011-07-07 14:58 ` Greg KH
2011-07-07 21:55 ` Henry Ptasinski
2011-07-07 22:04 ` Greg KH
2011-07-07 22:25 ` Pavel Roskin
2011-07-07 15:17 ` Jonas Gorski
2011-07-07 21:21 ` Henry Ptasinski
2011-07-07 0:45 ` Pavel Roskin
2011-07-07 15:01 ` Henry Ptasinski
2011-08-24 22:28 ` [PATCH v2] " Henry Ptasinski
2011-08-24 22:53 ` Greg KH
2011-08-24 23:17 ` Henry Ptasinski
2011-08-24 23:47 ` Greg KH
2011-08-24 23:54 ` Joe Perches
2011-08-25 0:42 ` Henry Ptasinski
2011-08-25 0:52 ` Joe Perches
2011-08-25 1:11 ` Henry Ptasinski
2011-08-25 2:23 ` Greg KH
2011-08-25 2:45 ` Joe Perches
2011-08-25 5:02 ` Johannes Berg
2011-09-30 21:54 ` Arend Van Spriel
2011-09-30 22:11 ` Luis R. Rodriguez
2011-08-24 23:05 ` Dan Carpenter
2011-08-25 0:49 ` Henry Ptasinski
2011-08-24 23:10 ` Aaro Koskinen
2011-08-24 23:18 ` Henry Ptasinski
2011-08-24 23:54 ` Aaro Koskinen
2011-08-24 23:41 ` Jonas Gorski
2011-08-25 0:20 ` Henry Ptasinski
2011-08-25 8:53 ` Michael Büsch
2011-08-25 10:34 ` Jonas Gorski
2011-08-25 17:59 ` Henry Ptasinski
2011-08-25 21:07 ` Rafał Miłecki
2011-08-25 21:09 ` Rafał Miłecki
2011-08-26 17:58 ` Henry Ptasinski
2011-08-25 20:55 ` Rafał Miłecki
2011-08-25 21:11 ` Rafał Miłecki
2011-08-25 21:23 ` Larry Finger
2011-08-26 17:55 ` Henry Ptasinski
2011-08-26 19:37 ` Rafał Miłecki
2011-08-26 19:45 ` Rafał Miłecki
2011-08-27 12:05 ` Rafał Miłecki
2011-08-27 13:18 ` Michael Büsch
2011-08-27 13:58 ` Rafał Miłecki
2011-08-30 13:02 ` David Woodhouse
2011-08-27 14:35 ` Dan Carpenter
2011-08-27 14:50 ` Greg KH
2011-08-27 15:08 ` Rafał Miłecki
2011-08-27 15:12 ` Rafał Miłecki
2011-08-27 16:45 ` Hauke Mehrtens
2011-08-27 15:21 ` Greg KH
2011-08-27 15:27 ` Rafał Miłecki
2011-08-30 1:42 ` Henry Ptasinski
2011-08-30 4:28 ` Greg KH
2011-08-30 6:22 ` Johannes Berg
2011-08-30 8:31 ` Rafał Miłecki
2011-08-30 9:28 ` Michael Büsch
2011-08-31 12:31 ` Rafał Miłecki
2011-08-30 6:17 ` Rafał Miłecki
2011-09-10 16:48 ` Rafał Miłecki
2011-08-30 18:14 ` Greg KH
2011-08-31 17:55 ` Luis R. Rodriguez
2011-08-31 18:33 ` Greg KH
2011-08-31 18:58 ` Luis R. Rodriguez
2011-08-31 11:55 ` Hauke Mehrtens
2011-08-31 14:18 ` John W. Linville [this message]
2011-08-31 17:46 ` Luis R. Rodriguez
2011-08-31 17:47 ` Luis R. Rodriguez
2011-08-27 14:59 ` Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2011-08-27 16:41 Xose Vazquez Perez
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=20110831141800.GB2474@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=devel@linuxdriverproject.org \
--cc=error27@gmail.com \
--cc=gregkh@suse.de \
--cc=hauke@hauke-m.de \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).