From: Delphi Real Estate <Info@delphi-real-estate.com>
To: linux-wireless@vger.kernel.org
Subject: Kernel Compile Fail with 2.6.26 Drivers
Date: Mon, 19 Jan 2009 09:30:11 -0800 [thread overview]
Message-ID: <200901190930.11401.Info@delphi-real-estate.com> (raw)
Can anyone tell me what I'm doing wrong? I know that 'n' has problems in later drivers than in kernel 2.6.26, so I am trying to graft the 2.6.26 drivers into the 2.6.27 kernel. Source:
http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi-2.6.git;a=summary
I moved the regular Ubuntu kernel 2.6.27.10's iwlwifi directory elsewhere, and copied in Reinette's. But it will not compile, inexplicably:
...
CC [M] drivers/pci/hotplug/cpcihp_generic.o
LD [M] drivers/pci/hotplug/pciehp.o
LD [M] drivers/pci/hotplug/shpchp.o
CC [M] drivers/pci/hotplug/fakephp.o
LD drivers/pci/hotplug/pci_hotplug.o
LD [M] drivers/media/video/uvc/uvcvideo.o
LD [M] drivers/pci/hotplug/acpiphp.o
LD drivers/pci/hotplug/built-in.o
LD drivers/media/built-in.o
LD drivers/pci/built-in.o
make: *** [drivers] Error 2
#
This kernel does compile with its normal iwlwifi directory. In configuring I only set the iwlwifi driver to be a module, disabled the 4965, and enabled the 5000. I can't use the git kernel because I need the Ubuntu patches.
Is there any other way to get 5GHz 'n'?
next reply other threads:[~2009-01-19 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 17:30 Delphi Real Estate [this message]
2009-01-19 18:46 ` Kernel Compile Fail with 2.6.26 Drivers reinette chatre
2009-01-19 21:48 ` Stefanik Gábor
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 17:42 Delphi Real Estate
2009-01-21 16:27 ` Delphi Real Estate
2009-01-22 13:58 ` Delphi Real Estate
2009-01-22 15:17 ` Luis R. Rodriguez
2009-01-23 13:50 ` Delphi Real Estate
2009-01-23 16:53 ` reinette chatre
2009-01-24 2:10 ` Delphi Real Estate
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=200901190930.11401.Info@delphi-real-estate.com \
--to=info@delphi-real-estate.com \
--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).