On 03/22/15 22:21, Stefano Cappa wrote:
Hi
I prefer a generic version, without specific things, like this one: h**p://postimg.org/image/hfkpjt3ux/ created by Johannes Berg.
And, if available something for the broadcom chip bcm4339.
Hi Stefano,
The bcm4339 is supported by the brcmfmac driver and is a cfg8211-based
driver aka fullmac device where the 802.11 stack runs on the device. I
did write up some stuff about the driver internally, but we can consider
putting it on wireless.kernel.org under creative commons license.
Regards,
Arend
Thank you.
________________________________________
Da: Kathy Giori<kathy.giori@xxxxxxxxx>
Inviato: domenica 22 marzo 2015 19.35
A: Stefano Cappa
Cc: linux-wireless@xxxxxxxxxxxxxxx
Oggetto: Re: informations about Linux wifi driver's architecture today
On Sun, Mar 22, 2015 at 11:19 AM, Stefano Cappa
<stefano.cappa@xxxxxxxxxxxxxx> wrote:
Hi!
some months ago, i saw the presentation of Johannes Berg in PDF, but now it isn't available, probably because it's very old.
This slides will be updated to a new release?
I have this slide and in page 5/35 (2009-02-26) there is the "Architecture - planned". This is the actual architecture or there are some differences in 2015? If yes, where i can find the new version of this page, with a little diagram?
Ciao Stefano,
Perhaps Johannes can post a current overview diagram on the Linux
wireless wiki (if you share with him which diagram you want to be
updated).
In terms of vendor-specific architecture, and how it fits in, Kalle
Valo posted a high-level diagram for ath10k:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/architecture
Are you mainly interested in the architecture of vendor-agnostic upper
layers or a description of a specific vendor driver?
kg--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
