From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, "David S. Miller" <davem@redhat.com>
Subject: Re: Updated Wireless Extension patches
Date: Tue, 29 Jun 2004 13:41:43 -0700 [thread overview]
Message-ID: <20040629204143.GA11782@bougret.hpl.hp.com> (raw)
In-Reply-To: <20040629194525.GF23191@havoc.gtf.org>
On Tue, Jun 29, 2004 at 03:45:25PM -0400, Jeff Garzik wrote:
>
> Regardless of our recent discussions, I do want to emphasize that I wish
> to maintain the current WE, and its backwards compatibility, for the
> current 2.6.x stable series at the very least.
>
> So please don't be discouraged from submitting WE patches...
No problem Jeff ;-) Because of my wife, I have learned to
compromise (I just wish she had learned that as well). I already told
you that the actual delivery mechanism to the driver doesn't matter to
me, what matter to me is the vocabulary and gramar of the API. And
also I want to satisfy the need of both driver authors and userspace.
So, we are aiming for the same goal, just having slightly
different methods.
I plan to submit WE-17 to you somewhat soon, because Jouni
needs it, and I've postponed it far too much. There is actually one
change in WE-17 that you should appreciate. WPA and RtNetlink will go
when they are ready, for WPA it depends on Jouni, for RtNetlink on me.
> Jeff
>
>
> P.S. do associated userland wireless-tools patches exist to make use of
> netlink? i.e. how have you been testing it?
Good catch ;-)
There are some advantage to RtNetlink. Unfortunately,
simplicity is not one. Dealing with RtNetlink is a lot of work
compared to ioctl, as you may discover if you migrate your API to it.
I have a pretty simple test app. I'm working on a version of
iwlib that would go through RtNetlink, that would enable the full
Wireless Tools to use RtNetlink. I'll try to release that soon.
Have fun...
Jean
prev parent reply other threads:[~2004-06-29 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 16:23 Jean Tourrilhes
2004-06-29 19:45 ` Jeff Garzik
2004-06-29 20:41 ` Jean Tourrilhes [this message]
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=20040629204143.GA11782@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®