From: "Michael Büsch" <mb@bu3sch.de>
To: Greg KH <gregkh@suse.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless@vger.kernel.org,
"Henry Ptasinski" <henryp@broadcom.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Nohee Ko" <noheek@broadcom.com>
Subject: Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs)
Date: Thu, 14 Oct 2010 19:24:17 +0200 [thread overview]
Message-ID: <1287077057.20394.19.camel@maggie> (raw)
In-Reply-To: <20101014171739.GA28522@suse.de> (sfid-20101014_191829_132773_43868632)
On Thu, 2010-10-14 at 10:17 -0700, Greg KH wrote:
> > Finishing N-PHY support in b43 does not need much work plus:
> > 1) We support SSB devices
> > 2) We support older (LP/G-phy) devices
> > 3) We share infrastructure (easier to maintain)
> > 4) We probably could support modes like AP
>
> If that would be a simpler task than trying to clean up the brcm80211
> driver, that seems quite reasonable.
That's really an unrelated topic. b43 and brcm80211 support different
kinds of devices whereas both devices may share certain sub-devices.
Like the radio device (b2056) in this case.
So it's not just a matter of "cleaning up" brcm80211. That doesn't give
us support for old SSB based N-PHY devices, because brcm80211 does not
support them at all.
--
Greetings Michael.
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <mb@bu3sch.de>
To: Greg KH <gregkh@suse.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless@vger.kernel.org,
"Henry Ptasinski" <henryp@broadcom.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Nohee Ko" <noheek@broadcom.com>
Subject: Re: Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs)
Date: Thu, 14 Oct 2010 19:24:17 +0200 [thread overview]
Message-ID: <1287077057.20394.19.camel@maggie> (raw)
In-Reply-To: <20101014171739.GA28522@suse.de> (sfid-20101014_191829_132773_43868632)
On Thu, 2010-10-14 at 10:17 -0700, Greg KH wrote:
> > Finishing N-PHY support in b43 does not need much work plus:
> > 1) We support SSB devices
> > 2) We support older (LP/G-phy) devices
> > 3) We share infrastructure (easier to maintain)
> > 4) We probably could support modes like AP
>
> If that would be a simpler task than trying to clean up the brcm80211
> driver, that seems quite reasonable.
That's really an unrelated topic. b43 and brcm80211 support different
kinds of devices whereas both devices may share certain sub-devices.
Like the radio device (b2056) in this case.
So it's not just a matter of "cleaning up" brcm80211. That doesn't give
us support for old SSB based N-PHY devices, because brcm80211 does not
support them at all.
--
Greetings Michael.
next prev parent reply other threads:[~2010-10-14 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 16:40 Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs) Rafał Miłecki
2010-10-14 16:40 ` Rafał Miłecki
2010-10-14 16:51 ` Greg KH
2010-10-14 17:06 ` Rafał Miłecki
2010-10-14 17:06 ` Rafał Miłecki
2010-10-14 17:17 ` Greg KH
2010-10-14 17:24 ` Michael Büsch [this message]
2010-10-14 17:24 ` Michael Büsch
2010-10-14 17:38 ` Rafał Miłecki
2010-10-14 17:38 ` Rafał Miłecki
2010-10-14 18:14 ` John W. Linville
2010-10-14 18:14 ` John W. Linville
2010-10-14 18:18 ` Luis R. Rodriguez
2010-10-14 18:18 ` Luis R. Rodriguez
2010-10-14 22:12 ` Dan Williams
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=1287077057.20394.19.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
--cc=brudley@broadcom.com \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--cc=noheek@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.