From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
Cc: Netdev <netdev@oss.sgi.com>, Dan Williams <dcbw@redhat.com>,
vkondra@mail.ru, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: wireless 2.6 work
Date: Tue, 22 Mar 2005 21:15:52 -0500 [thread overview]
Message-ID: <4240D158.1060302@pobox.com> (raw)
In-Reply-To: <20050310025036.GE17854@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> Jeff,
>
> I'm sick off the low activiity and slow support on wireless we have. I
> know you're busy so I wanted to offer my help in helping around work on
> wireless-2.6, now that I have time after work, and before I commit
> myself to anything else. It's a bit suicidal, but oh well. Oh yeah and
> I'll also start using bitkeeper due to the recent clarifications on the
> license of its usage.
Great! While I think BitKeeper is useful, you are more than welcome to
continue sending patches.
To wireless developers, BitKeeper will mainly be of use in sync'ing with
the latest wireless-2.6 tree.
> I'll willing to review as much patches as I have to and also hopefully
> write documentation on writing new wireless drivers. That said, if I can
> be of any assistance, where what you like me to start on?
>
> Here's what's on my agenda so far:
>
> * Help cleanup new ralink driver, start using ieee802211 and get into wireless-2.6.
> * Push prism54's new WPA and WDS support into wireless-2.6
> * Start seeing what I can use off of ieee80211 for prism54, clean it,
> and move to wireless-2.6
> * Start incorporating WPA through wpa_supplicant onto as many drivers
> * Start standardizing all things a bit, as bitched about and well pointed out
> by Dan Williams <dcbw@redhat.com>
> * Listen to Jouni, he's the man
Well, all this sounds good to me. See also the 'status' post I just
made, and the 'note on wireless development process' I am about to write.
I'm really hoping someone will look into integrating wireless 802.11 as
a "real" protocol, rather than faking ethernet. This work starts with
the "p80211" template DaveM provided, and hopefully continues with
Vladimir's updates of DaveM's code (did he post those anywhere?). There
are also issues such as ARP types that Dan Williams mentioned to me as
issues.
The "integrate wireless into net stack" work requires a very
self-motivated person who is willing to poke into the net stack, and
answer their own questions.
Jeff
next prev parent reply other threads:[~2005-03-23 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:50 wireless 2.6 work Luis R. Rodriguez
2005-03-10 3:02 ` Luis R. Rodriguez
2005-03-23 2:15 ` Jeff Garzik [this message]
2005-03-23 22:07 ` Vladimir Kondratiev
2005-03-25 4:11 ` Jeff Garzik
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=4240D158.1060302@pobox.com \
--to=jgarzik@pobox.com \
--cc=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=vkondra@mail.ru \
/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).