From: Stefano Cappa <stefano.cappa@mail.polimi.it>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: informations about Linux wifi driver's architecture today
Date: Mon, 23 Mar 2015 11:56:25 +0000 [thread overview]
Message-ID: <1427111784891.53085@mail.polimi.it> (raw)
In-Reply-To: <550FE50F.10303@broadcom.com>
Oh thank you.
Yes. This can be very useful.
________________________________________
Da: Arend van Spriel <arend@broadcom.com>
Inviato: lunedì 23 marzo 2015 11.03.59
A: Stefano Cappa
Cc: linux-wireless@vger.kernel.org
Oggetto: Re: informations about Linux wifi driver's architecture today
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@gmail.com>
> Inviato: domenica 22 marzo 2015 19.35
> A: Stefano Cappa
> Cc: linux-wireless@vger.kernel.org
> Oggetto: Re: informations about Linux wifi driver's architecture today
>
> On Sun, Mar 22, 2015 at 11:19 AM, Stefano Cappa
> <stefano.cappa@mail.polimi.it> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-23 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 18:19 informations about Linux wifi driver's architecture today Stefano Cappa
2015-03-22 18:35 ` Kathy Giori
2015-03-22 21:21 ` Stefano Cappa
2015-03-23 10:03 ` Arend van Spriel
2015-03-23 11:56 ` Stefano Cappa [this message]
2015-03-25 1:00 ` Stefano Cappa
2015-03-25 9:07 ` Rafał Miłecki
2015-03-25 9:20 ` Krishna Chaitanya
2015-03-26 2:02 ` Stefano Cappa
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=1427111784891.53085@mail.polimi.it \
--to=stefano.cappa@mail.polimi.it \
--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;
as well as URLs for NNTP newsgroup(s).