linux-kernel - Re: [PATCH] staging: brcm80211: Make CFLAGS explicit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C93B486.8050706@canonical.com>
Date:	Fri, 17 Sep 2010 12:33:42 -0600
From:	Tim Gardner <tim.gardner@...onical.com>
To:	Brett Rudley <brudley@...adcom.com>
CC:	Greg KH <gregkh@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Henry Ptasinski <henryp@...adcom.com>,
	Nohee Ko <noheek@...adcom.com>
Subject: Re: [PATCH] staging: brcm80211: Make CFLAGS explicit

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@...onical.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/