From: Johannes Berg <johannes@sipsolutions.net>
To: chunkeey@web.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] wext
Date: Wed, 04 Oct 2006 13:06:13 +0200 [thread overview]
Message-ID: <1159959973.2817.52.camel@ux156> (raw)
In-Reply-To: <200610041256.07110.chunkeey@web.de>
On Wed, 2006-10-04 at 12:56 +0200, chunkeey@web.de wrote:
> no really, the problem is that "my" hardware (aka: prism54 fullmac) does all
> the mac-management, encryption/decryption, AP-Management,... in the firmware.
> And all "management" operation are wrapped into a simple unique
> 4-byte "Operation ID"... That's why the WEXT "would be better" for that
> thing...
>
> (Or, do I mix everything up and nl80211 has "nothing" to do with devicescape's
> networkstack d80211?)
Yes, nl80211 is not tied to d80211, it simply provides a new way of
doing configuration.
johannes
next prev parent reply other threads:[~2006-10-04 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 17:55 [PATCH] wext chunkeey
2006-10-04 8:37 ` Johannes Berg
2006-10-04 10:56 ` chunkeey
2006-10-04 11:06 ` Johannes Berg [this message]
2006-10-04 21:45 ` Jouni Malinen
2006-10-05 8:15 ` Johannes Berg
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=1159959973.2817.52.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=chunkeey@web.de \
--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).