From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Stephan Maka <stephan@spaceboyz.net>
Cc: netdev@vger.kernel.org
Subject: Re: Wifi support for iproute2
Date: Sat, 3 Mar 2007 19:53:24 -0800 [thread overview]
Message-ID: <20070303195324.75eed906@deepthought> (raw)
In-Reply-To: <20070304012653.GA9587@hooker.hq.c3d2.de>
On Sun, 4 Mar 2007 02:26:53 +0100
Stephan Maka <stephan@spaceboyz.net> wrote:
> Hello
>
> I've always felt uncomfortable by the usability of the wireless-tools
> (iwconfig, iwlist), but I really love iproute2. That's why I started
> to implement "ip wifi".
>
> My GIT tree is located at:
> http://cthulhu.c3d2.de/~astro/git/iproute2.git/
>
> I wonder if this has a chance to get merged in iproute2 somewhen at
> all, or if this is completely inappropriate functionality for this
> tool.
>
> Note that this my first contribution to a Linux-specific tool, *any*
> hints about style and conventions demanded here are welcome.
>
> I'm sure not everyone will use this instead of wireless-tools, and a
> few even don't want it compiled in and linked with iwlib. Should I
> make this optional through a Makefile variable?
>
> If noone else contributes not all of wireless-tools will be
> implemented, it's just too much. But basic stuff for configuring a
> Wifi card is already there.
>
> Everyone told me dscape is near, but I hope iwlib will be ported then.
Don't waste your time with a tool that uses the exist wext API.
But a tool that could use cfg80211 would be useful. After the wireless
summit in Jan, I put it on my "interesting ideas" list.
next prev parent reply other threads:[~2007-03-04 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 1:26 Wifi support for iproute2 Stephan Maka
2007-03-04 3:53 ` Stephen Hemminger [this message]
2007-03-05 2:53 ` Stephan Maka
2007-03-04 23:43 ` 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=20070303195324.75eed906@deepthought \
--to=shemminger@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=stephan@spaceboyz.net \
/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).