linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Jaroslav Fojtik <jafojtik@seznam.cz>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Compilation problems with Linux-2.6.34 and compat-wireless
Date: Sat, 12 Jun 2010 13:51:58 -0400	[thread overview]
Message-ID: <1276365118.2625.25.camel@ct> (raw)
In-Reply-To: <4C108B0F.12989.BAFA3@jafojtik.seznam.cz>

On Thu, 2010-06-10 at 08:49 +0200, Jaroslav Fojtik wrote:
> Dear John W. Linville,
> 
> > I'm guessing you need CONFIG_WIRELESS_EXT in /usr/src/linux-2.6.34/.config ?
> I do not know how to turn CONFIG_WIRELESS_EXT in linux 2.6.34. 
> This option no longer exists.

Try enabling an older driver like ipw2100.  That should enable wireless
extensions.

> I guess that:
> CONFIG_WIRELESS_EXT=y  has been renamed to 
> CONFIG_WIRELESS_WEXT=y

I don't see any references to WIRELESS_WEXT in the kernel.  I think your
guess is wrong.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2010-06-12 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  6:49 Compilation problems with Linux-2.6.34 and compat-wireless Jaroslav Fojtik
2010-06-12 17:51 ` Pavel Roskin [this message]

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=1276365118.2625.25.camel@ct \
    --to=proski@gnu.org \
    --cc=jafojtik@seznam.cz \
    --cc=linux-wireless@vger.kernel.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).