linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/14] RFC: Driver for Wireless RNDIS USB devices.
Date: Thu, 24 Jan 2008 13:53:21 -0500	[thread overview]
Message-ID: <20080124185321.GB3200@tuxdriver.com> (raw)
In-Reply-To: <1201110286.8696.10.camel@localhost>

On Wed, Jan 23, 2008 at 07:44:46PM +0200, Jussi Kivilinna wrote:
> On Wed, 2008-01-23 at 09:52 -0500, John W. Linville wrote:
> > I would like to have this driver soon, and FWIW I just put it in the
> > Fedora Rawhide kernel last night.
> > 
> > However, I find that it does not seem to associate with WEP networks
> > on my USR5421.  I haven't had a chance to try it on open or WPA
> > networks, nor have I had a chance to debug it.  It does scan and see
> > the networks.
> > 
> > Have you tested the driver as posted?  What device(s) are you using?
> > Have you used it on encrypted networks?
> 
> I guess I should start testing more if I'm going to be maintainer,
> you're right WEP doesn't work. Unencrypted and WPA/WPA2 networks do work
> for me but not WEP. Ad-Hoc and hidden WPA networks do not work either. I
> have Buffalo WLI-U2-KG125S which should have same hardware/firmware as
> USR5421.

Overall this looks fine to me for initial merge.  I have a couple
of comments:

	-- I'm not too excited about the "Ndis_802_*" naming scheme for
	data structures, although I know you copied it from elsewhere.
	I'd like to see it changed, but I don't consider that a
	merge blocker.

	-- I foresee this driver surviving a conversion to use the
	new cfg80211 configuraiton API.  So the "rndis_wext" name may
	not be the best long-term choice.  I might suggest something
	like "rndis_wlan".  I don't see why we couldn't change that
	post-merge, although I would prefer to do that before the
	final 2.6.25 release.

So, I intend to push this upstream for 2.6.25.  Please consider making
the changes cited above, especially the name change.

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-01-24 19:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20  0:13 [PATCH 00/14] RFC: Driver for Wireless RNDIS USB devices Jussi Kivilinna
2008-01-23 13:21 ` Jussi Kivilinna
2008-01-23 14:52   ` John W. Linville
2008-01-23 17:44     ` Jussi Kivilinna
2008-01-24 18:53       ` John W. Linville [this message]
2008-01-25 13:25         ` Jussi Kivilinna
2008-01-25  1:19 ` David Brownell
2008-01-25 13:20   ` Jussi Kivilinna
2008-01-25 20:08     ` David Brownell

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=20080124185321.GB3200@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=linux-wireless@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).