From: Tim Gardner <tim.gardner@canonical.com>
To: Brett Rudley <brudley@broadcom.com>
Cc: Greg KH <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Henry Ptasinski <henryp@broadcom.com>,
Nohee Ko <noheek@broadcom.com>
Subject: Re: [PATCH] staging: brcm80211: Make CFLAGS explicit
Date: Fri, 17 Sep 2010 12:33:42 -0600 [thread overview]
Message-ID: <4C93B486.8050706@canonical.com> (raw)
In-Reply-To: <7A94256FD72B884D9E7C55586C3CBCEE12BEC65BEC@SJEXCHCCR01.corp.ad.broadcom.com>
On 09/17/2010 12:03 PM, Brett Rudley wrote:
>
> In a split mac dongle, the HIGH code runs on the host processor while
> the LOW code runs on the dongle and the two talk across an RPC API
> over SDIO or USB.
>
Don't you have the orientation inverted? WLC_LOW is defined for a PCI NIC.
> On a NIC both HIGH and LOW run on the host and the RPC API remains
> identical but the APIs become function straight calls.
>
I'm a bit confused by this. For PCI NICs WLC_HIGH_ONLY is definitely
_not_ enabled, which means to me that HIGH is not running on the host.
> This lets us use the same code and API in both models.
>
> Getting some documentation out on this is in TODO list.
>
Thanks. Perhaps that'll clear up some confusion.
> Brett
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2010-09-17 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 15:20 [PATCH] staging: brcm80211: Make CFLAGS explicit Tim Gardner
2010-09-17 16:21 ` Greg KH
2010-09-17 17:44 ` Tim Gardner
2010-09-17 17:58 ` Greg KH
2010-09-17 18:03 ` Brett Rudley
2010-09-17 18:33 ` Tim Gardner [this message]
2010-09-17 18:39 ` Brett Rudley
[not found] ` <FD96C117992C584DBC47231B1EB6F5568206497F85@SJEXCHCCR02.corp.ad.broadcom.com>
2010-09-21 3:54 ` [PATCH] staging: brcm80211: add fullmac driver Greg KH
2010-09-22 1:56 ` [PATCH] staging: brcm80211: Make CFLAGS explicit matt mooney
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=4C93B486.8050706@canonical.com \
--to=tim.gardner@canonical.com \
--cc=brudley@broadcom.com \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noheek@broadcom.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