netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.co.intel.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: jt@hpl.hp.com, Christoph Hellwig <hch@infradead.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 17:37:16 -0600	[thread overview]
Message-ID: <404FA6AC.7040009@linux.co.intel.com> (raw)
In-Reply-To: <404F5744.1040201@pobox.com>

Jeff Garzik wrote:

 > Yes, it would be good to end the cycle of re-implementing 802.11 over
 > and over again ;-)

< snip >

 > * start working on generic 802.11 stack in wireless-2.6 queue

As we're currently walking the path of implementing the same thing for the 
IPW2100 driver,  being able to re-use this code would be _very nice_.

I'd like to get WEP into IPW2100 as soon as possible, and would like to do so in 
a way that would make transitioning to a common 802.11 layer seamless (or at 
least reasonably isolated).  Any suggestions on how to best do this, or where we 
might be able to help, would be much appreciated.

I'm very interested in these discussions, so if they move to or are being 
discussed on another list (besides netdev), please let me know where.

Thanks,
James

  reply	other threads:[~2004-03-10 23:37 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 [this message]
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     ` [PATCH 2.6] Intersil Prism54 wireless driver Jeff Garzik
2004-03-11  2:21       ` 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=404FA6AC.7040009@linux.co.intel.com \
    --to=jketreno@linux.co.intel.com \
    --cc=davem@redhat.com \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).