netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: jt@hpl.hp.com
Cc: "John W. Linville" <linville@tuxdriver.com>,
	netdev@vger.kernel.org, Javier Achirica <achirica@gmail.com>,
	Simon Kelley <simon@thekelleys.org.uk>,
	Jouni Malinen <jkmaline@cc.hut.fi>,
	"James P. Ketrenos" <ipw2100-admin@linux.intel.com>,
	Zhu Yi <yi.zhu@intel.com>, Pavel Roskin <proski@gnu.org>,
	"Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>,
	Jeroen Vreeken <pe1rxq@amsat.org>,
	Michael Wu <flamingice@sourmilk.net>,
	Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Michael Buesch <mbuesch@freenet.de>
Subject: Re: [PATCH 2.6.18] WE-21 support (core API)
Date: Thu, 31 Aug 2006 15:32:18 +0200	[thread overview]
Message-ID: <1157031138.16040.17.camel@ux156> (raw)
In-Reply-To: <20060830005655.GA8405@bougret.hpl.hp.com>

On Tue, 2006-08-29 at 17:56 -0700, Jean Tourrilhes wrote:
> 		o modulation
> 		o long/short retry
> 		o relative power saving.

I strongly disagree to these.

What's the point of adding more ioctls that we'll be implementing them
as wrappers around nl80211? Right now, those new ioctls/options aren't
implemented in *any* driver at all so they're completely useless, and
just add more to the pile of historic baggage we end up carrying around.
If we add these to mainline now, it's another thing we'll have to carry
for a long time even though it currently has no users...

I'd much prefer merging nl80211 and putting any really *new* stuff into
it directly. Of course this fragments the user space API for a while
since you need to use two APIs then for the time being to configure all
things, but we can move over all the rest of the configuration gradually
and before we end up in mainline with the new API we can have that
finished.

Or putting it the other way round, I'm ok with
 * cleaning up the ssid mess
 * adding RCPI (we'll probably be using it in nl80211 anyway, so it's
   easier if we add it now and declare no support for other things)
 * getting rid of get_wireless_stats (good one!)
   [actually, I plan to get rid of wireless_handlers too]

johannes

  reply	other threads:[~2006-08-31 13:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  0:56 [PATCH 2.6.18] WE-21 support (core API) Jean Tourrilhes
2006-08-31 13:32 ` Johannes Berg [this message]
2006-08-31 13:51   ` Jouni Malinen
2006-08-31 14:00     ` Johannes Berg
2006-09-06 20:55       ` [RFC] Alternate " John W. Linville
2006-09-06 21:09         ` Michael Buesch
2006-09-06 21:30         ` Jean Tourrilhes
2006-09-08 14:29           ` John W. Linville
2006-09-08 16:13             ` Jean Tourrilhes
2006-09-08 20:04               ` John W. Linville
2006-09-11  9:08               ` Johannes Berg
     [not found]                 ` <20060911162608.GA31459@bougret.hpl.hp.com>
     [not found]                   ` <1158050637.2854.16.camel@ux156>
2006-09-12 16:17                     ` Jean Tourrilhes
2006-09-13  6:17                       ` Johannes Berg
2006-09-06 21:43         ` Larry Finger
2006-09-07  6:42         ` Johannes Berg
2006-08-31 17:12   ` [PATCH 2.6.18] " Jean Tourrilhes
2006-08-31 17:57     ` Michael Buesch
2006-09-01  6:56       ` Johannes Berg
2006-09-01  6:54     ` Johannes Berg
2006-09-01 16:35       ` Jean Tourrilhes
2006-09-01 18:55         ` Michael Buesch
2006-09-01 22:10           ` Jean Tourrilhes
2006-09-02  0:47             ` Michael Buesch
2006-09-04  8:17               ` Johannes Berg
2006-09-04  8:35             ` Johannes Berg
2006-09-04 14:13               ` Stuffed Crust
2006-09-05 17:06               ` Jean Tourrilhes
2006-09-01 22:27           ` Ulrich Kunitz

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=1157031138.16040.17.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=achirica@gmail.com \
    --cc=flamingice@sourmilk.net \
    --cc=ipw2100-admin@linux.intel.com \
    --cc=jkmaline@cc.hut.fi \
    --cc=jt@hpl.hp.com \
    --cc=linville@tuxdriver.com \
    --cc=mbuesch@freenet.de \
    --cc=mcgrof@ruslug.rutgers.edu \
    --cc=netdev@vger.kernel.org \
    --cc=pe1rxq@amsat.org \
    --cc=proski@gnu.org \
    --cc=simon@thekelleys.org.uk \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=yi.zhu@intel.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).