From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>, ath5k-devel@lists.ath5k.org
Subject: Re: Linux wireless compatibility package for kernels >= 2.6.22
Date: Sun, 11 Nov 2007 23:27:38 -0500 [thread overview]
Message-ID: <1194841658.2276.8.camel@dv> (raw)
In-Reply-To: <43e72e890711101953w6e046b82j6b9087d30c8195b2@mail.gmail.com>
Hello!
On Sat, 2007-11-10 at 22:53 -0500, Luis R. Rodriguez wrote:
> I've started a compatibility package for the Linux wireless subsystem
> for kernels >= 2.6.22. You can download it here:
>
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2
I would prefer that you use exactly the same path for all drivers, so
that the patches are compatible. Wireless drivers should be in
drivers/net/wireless.
Also, I cannot compile it against current wireless-2.6/everything
compiled outside the source tree:
/home/proski/src/compat-wireless-2.6/drivers/iwlwifi/iwl-3945-rs.c:40:40: error: ../mac80211/ieee80211_rate.h: No such file or directory
After some hack to make it compile, I still get:
CC [M] /home/proski/src/compat-wireless-2.6/mac80211/ieee80211.o
/home/proski/src/compat-wireless-2.6/mac80211/ieee80211.c:24:6: warning:
"LINUX_VERSION_CODE" is not defined
/home/proski/src/compat-wireless-2.6/mac80211/ieee80211.c:24:28:
warning: "KERNEL_VERSION" is not defined
/home/proski/src/compat-wireless-2.6/mac80211/ieee80211.c:24:42: error:
missing binary operator before token "("
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-11-12 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 3:53 Linux wireless compatibility package for kernels >= 2.6.22 Luis R. Rodriguez
2007-11-12 4:27 ` Pavel Roskin [this message]
2007-11-13 23:10 ` Luis R. Rodriguez
2007-11-14 18:02 ` Pavel Roskin
2007-11-16 23:54 ` 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=1194841658.2276.8.camel@dv \
--to=proski@gnu.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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