From: Vladimir Kondratiev <vkondra@mail.ru>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>,
Netdev <netdev@oss.sgi.com>, Dan Williams <dcbw@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: wireless 2.6 work
Date: Thu, 24 Mar 2005 00:07:02 +0200 [thread overview]
Message-ID: <200503240007.11954.vkondra@mail.ru> (raw)
In-Reply-To: <4240D158.1060302@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 2967 bytes --]
I did posted once; it was long time ago. I am sure I sent it to Dave. I can
resend if needed. Basically, I made Dave's stack work on 2.6 kernels; did
some changes toward QoS and provided simple utility to imitate low level
driver. I was concentrated on interfaces, it is still just skeleton.
I did not touched this work since then. I used to do stuff very close to
802.11 stack. Now I am very busy with some different work.
I can however consult on any 802.11 standard issues, QoS in particular.
Maybe, it is good idea to talk to James Ketrenos as well. Last time I saw him
doing good work on .11 stack.
Vladimir
On Wednesday 23 March 2005 04:15, Jeff Garzik wrote:
JG> Luis R. Rodriguez wrote:
JG> > Jeff,
JG> >
JG> > I'm sick off the low activity and slow support on wireless we have. I
JG> > know you're busy so I wanted to offer my help in helping around work on
JG> > wireless-2.6, now that I have time after work, and before I commit
JG> > myself to anything else. It's a bit suicidal, but oh well. Oh yeah and
JG> > I'll also start using bitkeeper due to the recent clarifications on the
JG> > license of its usage.
JG>
JG> Great! While I think BitKeeper is useful, you are more than welcome to
JG> continue sending patches.
JG>
JG> To wireless developers, BitKeeper will mainly be of use in sync'ing with
JG> the latest wireless-2.6 tree.
JG>
JG>
JG> > I'll willing to review as much patches as I have to and also hopefully
JG> > write documentation on writing new wireless drivers. That said, if I
can JG> > be of any assistance, where what you like me to start on?
JG> >
JG> > Here's what's on my agenda so far:
JG> >
JG> > * Help cleanup new ralink driver, start using ieee802211 and get into
wireless-2.6. JG> > * Push prism54's new WPA and WDS support into
wireless-2.6
JG> > * Start seeing what I can use off of ieee80211 for prism54, clean it,
JG> > and move to wireless-2.6
JG> > * Start incorporating WPA through wpa_supplicant onto as many drivers
JG> > * Start standardizing all things a bit, as bitched about and well
pointed out JG> > by Dan Williams <dcbw@redhat.com>
JG> > * Listen to Jouni, he's the man
JG>
JG> Well, all this sounds good to me. See also the 'status' post I just
JG> made, and the 'note on wireless development process' I am about to write.
JG>
JG> I'm really hoping someone will look into integrating wireless 802.11 as
JG> a "real" protocol, rather than faking ethernet. This work starts with
JG> the "p80211" template DaveM provided, and hopefully continues with
JG> Vladimir's updates of DaveM's code (did he post those anywhere?). There
JG> are also issues such as ARP types that Dan Williams mentioned to me as
JG> issues.
JG>
JG> The "integrate wireless into net stack" work requires a very
JG> self-motivated person who is willing to poke into the net stack, and
JG> answer their own questions.
JG>
JG> Jeff
JG>
JG>
JG>
JG>
JG>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-23 22:07 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
2005-03-23 22:07 ` Vladimir Kondratiev [this message]
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=200503240007.11954.vkondra@mail.ru \
--to=vkondra@mail.ru \
--cc=dcbw@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@ruslug.rutgers.edu \
--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).