From: Johannes Berg <johannes@sipsolutions.net>
To: "Bar, Eitan" <eitanb@ti.com>
Cc: netdev@vger.kernel.org
Subject: RE: 80211 questions
Date: Wed, 18 Oct 2006 15:50:41 +0200 [thread overview]
Message-ID: <1161179441.5575.31.camel@ux156> (raw)
In-Reply-To: <19EFC4D481EBF849B14F91557CA737B54A6839@dile02.ent.ti.com>
On Wed, 2006-10-18 at 15:45 +0200, Bar, Eitan wrote:
> [Eitan Bar] I was actually looking for any kind of design document, or
> anything related to the concept behind it.
As for cfg80211/nl80211 it was mostly discussed here on netdev and I
haven't written up anything.
> I'm adding WE support for a Texas Instruments driver for future
> chipsets. The driver is, at the moment, entirely proprietary (including
> user-mode API).
Heh, ok. I'm just wondering whether it would make sense for you to
provide a d80211 driver for that chipset instead. If you could tell me
(even in private if you wish) some details about what your hardware does
in firmware and what it does in the driver, I could help you make that
decision.
> [Eitan Bar] I see. Can you please point out if there's any driver
> currently supporting cfg80211 or nl80211 for reference? (which one are
> you using for testing?)
I have provided some code (very little actually) to make d80211 use
cfg80211 (and you can't do much with nl80211 yet), but no driver
implements it yet directly.
johannes
next prev parent reply other threads:[~2006-10-18 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 13:09 80211 questions Bar, Eitan
2006-10-18 13:29 ` Johannes Berg
2006-10-18 13:45 ` Bar, Eitan
2006-10-18 13:50 ` Johannes Berg [this message]
2006-10-18 14:18 ` Dan Williams
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=1161179441.5575.31.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=eitanb@ti.com \
--cc=netdev@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).