netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Renzmann <mrenzmann@web.de>
To: Dan Williams <dcbw@redhat.com>
Cc: Jean Tourrilhes <jt@hpl.hp.com>, netdev@oss.sgi.com
Subject: Re: Where Linux 802.11x support needs work
Date: Wed, 26 Jan 2005 08:17:10 +0100	[thread overview]
Message-ID: <41F743F6.2020008@web.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0501252224000.4275@devserv.devel.redhat.com>

Hi.

Dan Williams wrote:
> madwifi: doesn't seem to implement SIOCGIWSTATS

It does. The SIOCGIWSTATS is used in tools/athstats.c (line 195 in 
current CVS) for example to get the rssi (via qual.qual).

>>>o  Ad-Hoc mode support is quite flaky or absent from most drivers
>>	Low priority for most vendors, firwmares are only lightly tested.
> Yeah, I don't expect much to happen here but it would be nice.  FWIW, at 
> least madwifi and atmel seem to work OK here.

Madwifi unfortunately has some known problems in Ad-hoc implementation. 
Someone worked on that, but the patches have not been sent in as far as 
I can tell.

>>	Note that various other people have their own todo list. Jeff
>>also has things he has in minds. I have (few) patches on my web
>>pages. Driver authors also have their wishes.
> True, but I'm not sure how many of those wishes/todo lists are actually 
> well-known or public.  I don't really see any great momentum in the Linux 
> 802.11x world, but more a hodge-podge of improvements.  I was hoping that 
> the post today could help  direct a bit more attention and effort at Linux 
> 802.11x stuff so we could try to clean it up and improve it.

How about setting up a project that cares of finding, defining and 
implementing such quasi-standards in the Linux 802.11 world? Most things 
are very WLAN specific, so I think netdev isn't the best place to 
discuss them. Of course this only works IMO when many (if not all) of 
the wlan driver authors join in and help out.

Comments?

Bye, Mike

  parent reply	other threads:[~2005-01-26  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  2:40 Where Linux 802.11x support needs work Jean Tourrilhes
2005-01-26  4:03 ` Dan Williams
2005-01-26  4:41   ` Michael Wu
2005-01-26  7:31     ` Roar Bjørgum Rotvik
2005-01-27 16:24       ` Michael Wu
2005-01-27 18:09       ` Michael Renzmann
2005-01-26  7:17   ` Michael Renzmann [this message]
2005-01-26 18:03     ` Dan Williams
  -- strict thread matches above, loose matches on Subject: below --
2005-01-25 21:47 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=41F743F6.2020008@web.de \
    --to=mrenzmann@web.de \
    --cc=dcbw@redhat.com \
    --cc=jt@hpl.hp.com \
    --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;
as well as URLs for NNTP newsgroup(s).