From: "Arend van Spriel" <arend@broadcom.com>
To: "Greg KH" <greg@kroah.com>
Cc: linuxdriverproject <devel@linuxdriverproject.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: new utility kernel module for detecting cores in newer chipsets
Date: Sat, 19 Mar 2011 13:13:48 +0100 [thread overview]
Message-ID: <op.vslaxakc3ri7v4@arend-laptop> (raw)
In-Reply-To: <op.vslagcb13ri7v4@arend-laptop>
+ mailing lists
Hi Greg,
There has been several discussion in the community (mainly by b43 and ssb
developers, I believe) to add support for chip core interconnect used in
newer Broadcom chips. Our brcm80211 drivers already have this support and
we have isolated that functionality in a separate kernel module called
brcmaxi to provide it to other drivers. Currently, I have it located under
drivers/staging/brcm80211 as I am not sure whether or not its purpose
justifies a separate folder (under staging or not).
What are your thoughts about this? I would like to know before submitting
a patch for this.
Gr. AvS
--
"The most merciful thing in the world, I think, is the inability of the
human
mind to correlate all its contents." - "The Call of Cthulhu"
next parent reply other threads:[~2011-03-19 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.vslagcb13ri7v4@arend-laptop>
2011-03-19 12:13 ` Arend van Spriel [this message]
2011-03-20 9:55 ` new utility kernel module for detecting cores in newer chipsets Rafał Miłecki
2011-03-20 13:07 ` George Kashperko
2011-03-20 17:04 ` Arend van Spriel
[not found] ` <1300538338.11949.12.camel@maggie>
[not found] ` <20110319214234.GA5152@kroah.com>
[not found] ` <1300573336.11949.25.camel@maggie>
[not found] ` <20110319234524.GA7493@kroah.com>
[not found] ` <op.vsmyhmei3ri7v4@arend-laptop>
[not found] ` <20110320145421.GA13962@kroah.com>
[not found] ` <op.vsnd1a1i3ri7v4@arend-laptop>
[not found] ` <20110320162200.GA17030@kroah.com>
[not found] ` <op.vsng7q1j3ri7v4@arend-laptop>
[not found] ` <20110320185216.GD19375@kroah.com>
2011-03-21 10:12 ` Rafał Miłecki
2011-03-21 14:05 ` Greg KH
2011-03-21 14:27 ` Rafał Miłecki
2011-03-21 14:46 ` Greg KH
2011-03-21 14:52 ` Rafał Miłecki
2011-03-21 15:16 ` Greg KH
2011-03-21 15:33 ` Rafał Miłecki
2011-03-21 15:05 ` Arend van Spriel
2011-03-21 15:14 ` John W. Linville
2011-03-21 15:30 ` Rafał Miłecki
2011-03-21 16:25 ` George Kashperko
2011-03-21 16:24 ` Michael Büsch
2011-03-21 16:28 ` Michael Büsch
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=op.vslaxakc3ri7v4@arend-laptop \
--to=arend@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
/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