From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Paul Hickey <paul@christianpatriot.us>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Failed Build of modules for 2.6.27.9-159
Date: Mon, 19 Jan 2009 11:11:38 -0800 [thread overview]
Message-ID: <20090119191138.GA4018@tesla> (raw)
In-Reply-To: <1232319854.4596.1.camel@localhost.localdomain>
On Sun, Jan 18, 2009 at 03:04:14PM -0800, Paul Hickey wrote:
> Ath9k is part of (my) Fedora 10 and loaded in kernel
> 2.6.27-9.159.fc10.x86_64. mac80211 is loaded when Ath9k is loaded and
> loads cfg80211. mac80211 can be loaded without loading Ath9k (you sti=
ll
> get cfg80211) but one of them gives a never ending log entry of
> ForceXPAon:0
You can ignore this ForceXPAon message, it was supposed to be a debug m=
essage
but was left with a normal print.
> I have a valid .config file
> I have the kernel headers and development files as well.
>=20
> [root@panda4 compat-wireless-2009-01-18]# make
> make -C /lib/modules/2.6.27.9-159.fc10.x86_64/build
> M=3D/home/paul/Download/compat-wireless-2009-01-18 modules
> make[1]: Entering directory `/usr/src/kernels/2.6.27.9-159.fc10.x86_6=
4'
>=20
> Message from syslogd@panda4 at Jan 18 15:50:48 ...
> kernel:Disabling IRQ #16
> CC
> [M] /home/paul/Download/compat-wireless-2009-01-18/net/wireless/comp=
at.o
> /home/paul/Download/compat-wireless-2009-01-18/net/wireless/compat.c:=
18:
> error: redefinition of =E2=80=98pci_ioremap_bar=E2=80=99
> include/linux/pci.h:1127: error: previous definition of
> =E2=80=98pci_ioremap_bar=E2=80=99 was here
The 2.6.27 kernel does not have pci_ioremap_bar(), and compat.c defined=
it
for older kernels as a couple of drivers (ipw, and some ralink driver)
make use of it. Can you try downloading today's version of compat-wirel=
ess and
then try to compile?
If you still see the complaint above then please ensure your kernel
headers are installed properly. By default this is the directory used:
/lib/modules/`uname -r`/build
So check:
ls -ld /lib/modules/`uname -r`/build
And ensure that's pointing to a 2.6.27 directory. Then check the includ=
e/linux/pci.h
file there and look for pci_ioremap_bar. If its there then I am surpris=
ed. Please report
back. I just tested a compile test against 2.6.27 on Ubuntu.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-19 19:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 23:04 Failed Build of modules for 2.6.27.9-159 Paul Hickey
2009-01-19 19:11 ` Luis R. Rodriguez [this message]
[not found] ` <1232404986.3641.2.camel@localhost.localdomain>
[not found] ` <20090120000336.GB4018@tesla>
[not found] ` <1232433738.3696.3.camel@localhost.localdomain>
2009-01-20 19:42 ` Luis R. Rodriguez
2009-01-20 20:05 ` [stable] " Greg KH
2009-01-20 20:13 ` Luis R. Rodriguez
2009-01-20 20:16 ` Greg KH
[not found] ` <20090120211630.GJ19581@tesla>
2009-01-20 22:08 ` Kyle McMartin
2009-01-20 22:37 ` Greg KH
2009-01-20 22:55 ` Luis R. Rodriguez
2009-01-20 23:23 ` Kyle McMartin
2009-01-21 0:07 ` Luis R. Rodriguez
2009-01-21 0:12 ` Kyle McMartin
2009-01-21 0:20 ` Luis R. Rodriguez
2009-01-20 20:15 ` Michael Buesch
2009-01-20 21:12 ` Kyle McMartin
2009-01-20 21:21 ` 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=20090119191138.GA4018@tesla \
--to=lrodriguez@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=paul@christianpatriot.us \
/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).