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: Wed, 23 Jan 2008 09:52:43 -0500 [thread overview]
Message-ID: <20080123145243.GA3129@tuxdriver.com> (raw)
In-Reply-To: <1201094475.7733.1.camel@localhost>
On Wed, Jan 23, 2008 at 03:21:15PM +0200, Jussi Kivilinna wrote:
> On Sun, 2008-01-20 at 02:13 +0200, Jussi Kivilinna wrote:
> > Hello,
> >
> > This is second try on wireless RNDIS patchset started by Bjorge Dijkstra. Since
> > Bjorge has disappeared, I claim maintainership of rndis_wext and this patchset
> > until he returns.
> >
> > This patchset adds support for various 802.11 USB devices based on Broadcom
> > 4320 chip. Chip uses RNDIS to communicate with the host, so module depend
> > heavily on rndis_host/cdc_ether/usbnet and needs some changes on these
> > modules in order to work.
> Any change of getting driver merged in 2.6.25?
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?
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-01-23 15:01 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 [this message]
2008-01-23 17:44 ` Jussi Kivilinna
2008-01-24 18:53 ` John W. Linville
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=20080123145243.GA3129@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).