netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Christoph Hellwig <hch@infradead.org>,
	prism54-devel@prism54.org, "David S. Miller" <davem@redhat.com>,
	netdev@oss.sgi.com,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] Intersil Prism54 wireless driver
Date: Wed, 10 Mar 2004 13:07:17 -0500	[thread overview]
Message-ID: <404F5955.6040702@pobox.com> (raw)
In-Reply-To: <20040310172114.GA8867@bougret.hpl.hp.com>

Jean Tourrilhes wrote:
> On Wed, Mar 10, 2004 at 04:55:48PM +0000, Christoph Hellwig wrote:
> 
>>On Wed, Mar 03, 2004 at 06:35:24PM -0800, Jean Tourrilhes wrote:
>>
>>>	Hi Dave & Jeff,
>>>
>>>	The attached .bz2 file is a patch for 2.6.3 adding the
>>>Intersil Prism54 wireless driver. Sorry for the attachement, the file
>>>is rather big, if you want inline+plaintext, I'll send that personal
>>>to you.
>>>	I've been using this driver with great success on 2.6.3 and
>>>2.6.4-rc1 (SMP). This driver support various popular CardBus and PCI
>>>802.11g cards (54 Mb/s) based on the Intersil PrismGT/PrismDuette
>>>chipset.
>>>	I would like this driver to go into 2.6.X. However, I
>>>understand that it's lot's of code to review.
>>
>>Here's a few things I found.
> 
> 
> 	I'm forwarding to prism54-devel where the real developpers can
> answer your questions.

since I'm not on the this list, I am getting a bunch of "your message 
for prism54-devel awaits moderator approval" responses.

Maybe the prism54 and hostAP developers could join us on netdev?  It 
would be nice to have everybody in one place, if we're all gonna be 
collaborating on a generic 802.11 stack.

	Jeff

  parent reply	other threads:[~2004-03-10 18:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  2:35 [PATCH 2.6] Intersil Prism54 wireless driver Jean Tourrilhes
2004-03-04  2:37 ` Jeff Garzik
2004-03-04  2:49   ` Jean Tourrilhes
2004-03-10  3:24   ` Jean Tourrilhes
2004-03-10  7:12     ` Jeff Garzik
2004-03-10 17:21       ` Jean Tourrilhes
2004-03-10 16:55 ` Christoph Hellwig
2004-03-10 17:21   ` Jean Tourrilhes
2004-03-10 17:29     ` Christoph Hellwig
2004-03-10 17:29     ` Jeff Garzik
2004-03-10 17:52       ` Jean Tourrilhes
2004-03-10 17:58         ` Jeff Garzik
2004-03-10 23:37           ` James Ketrenos
2004-03-11  2:31             ` Jouni Malinen
2004-03-11  2:43               ` Jeff Garzik
2004-03-15 22:18                 ` Pavel Machek
2004-03-15 22:44                   ` Jeff Garzik
2004-03-15 22:55                   ` Jean Tourrilhes
2004-03-11  2:48           ` Jouni Malinen
2004-03-11  3:02             ` Jeff Garzik
2004-03-11  3:17               ` Jouni Malinen
2004-03-11 16:28                 ` Device naming for wireless NICs James Ketrenos
2004-03-11 16:36                   ` Tomasz Torcz
2004-03-11 16:54                   ` Matthew Galgoci
2004-03-11 18:25                     ` Jeff Garzik
2004-03-11 18:23                   ` Jeff Garzik
2004-03-12 10:30                     ` P
2004-03-10 18:07     ` Jeff Garzik [this message]
2004-03-11  2:21       ` [PATCH 2.6] Intersil Prism54 wireless driver Jouni Malinen
2004-03-10 22:17     ` Luis R. Rodriguez

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=404F5955.6040702@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davem@redhat.com \
    --cc=hch@infradead.org \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=prism54-devel@prism54.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).