linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: hce <webmail.hce@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Patch for linux wireless extension
Date: Tue, 04 Mar 2008 08:58:21 -0500	[thread overview]
Message-ID: <1204639101.7183.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1204626369.3917.96.camel@johannes.berg>

On Tue, 2008-03-04 at 11:26 +0100, Johannes Berg wrote:
> Jim,
> 
> > I am running a wifi device on kernel 2.6.11 and wireless extension
> > version 17 for an ARM processor, it works fine with an open AP and
> > wpa_supplicant 0.5.8. 
> 
> That's ancient.
> 
> > Now I would like to support WEP and WPA. I know
> > the best is to upgrade to latest kernel, but I am not in the position
> > to do it as various reasons. 
> 
> Upgrade anyway.
> 
> > An alternative as people suggested is to
> > do a wireless extension patch which supports WEP and WPA on kernel
> > 2.6.11. Any advice if it is feasible and where can I find the wireless
> > extension patch for WEP and WPA on kernel 2.6.11 please?
> 
> Hahaha. We'll you'll have to *make* that patch and invest a
> *significant* amount of time into that.

Yeah; it's not just the defines and whatnot in wireless.h; you probably
also want to update wireless-tools too, then you have to update your
driver as well.  It's not hugely complex, but it's going to be a lot of
boring work :)

Dan



  reply	other threads:[~2008-03-04 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  3:01 Patch for linux wireless extension hce
2008-03-04 10:26 ` Johannes Berg
2008-03-04 13:58   ` Dan Williams [this message]
2008-03-06 10:37     ` hce
2008-03-06 14:00       ` Dan Williams
2008-03-07  3:00         ` hce
2008-03-07 12:11           ` Dan Williams

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=1204639101.7183.17.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=webmail.hce@gmail.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).