From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: PAN Sunny S K <sunnypan@ust.hk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Building of compat-wireless-old in 2.6.25 BSP kernel for PowerPC architecture
Date: Wed, 27 Jan 2010 10:06:15 -0800 [thread overview]
Message-ID: <43e72e891001271006l3422b6e2iccb89954feeaa34b@mail.gmail.com> (raw)
In-Reply-To: <47088.143.89.144.207.1264589300.squirrel@sqmail.ust.hk>
On Wed, Jan 27, 2010 at 2:48 AM, PAN Sunny S K <sunnypan@ust.hk> wrote:
> Hi,
>
> Thanks Pavel, Xiao and especially Luis for their quick reply.
> So as suggested, I'll firstly try to build the latest compat-wireless
> driver with the 2.6.25 kernel. And update the kernel to 2.6.34 as the last
> attempt which requires support from Freescale.
>
> Let me briefly mention a little background and the problem I've
> encountered when building the driver.
>
> Our project is base on a Freescale MPC8377EWLAN reference design which
> runs by a MPC8377 PowerQUICC II PowerPC processor. It uses LTIB to develop
> and deploy BSP for this architecture and the Linux kernel version provided
> is 2.6.25 (a slightly patched kernel to adapt the processor) The wireless
> interface we're using is Wistron DNMA-83 (equivalent to Unex DNMA-83)
> which uses Atheros AR9160 chipset.
>
> To fully utilize the 802.11 a/b/g/n mode provided by the chipset (and the
> proprietary driver came with the package has too many problems), we look
> for the ath9k driver and would like to build it with the 2.6.25 kernel.
>
> So what I did to build the driver is to provide the KLIB and KLIB_BUILD
> with the path of 2.6.25 source and modified the CROSS_COMPILE variable in
> the .config of the kernel to make sure it uses the MPC8377 toolchain to
> compile the source. However, the following error occurred (With my latest
> trial of the bleeding edge compat-wireless-2.6):
>
> make -C /MyProject/ltib-mpc8377ewlan-20090922/rpm/BUILD/linux-2.6.25
> M=/root/Desktop/compat-wireless-2009-12-11 modules
> make[1]: Entering directory
compat-wireless-2009-12-11 is from a bleeding edge snapshot. Bleedign
edge snapshots
do not yet have MQ support backported, but MQ support was not merged
by then, so hmm...
OK try this:
./scripts/driver-select ath9k
That will only enable to compile ath9k.
If you hit a debugfs compile error then you've hit the other blocker
from backporting down to 2.6.23 on bleedigng edge.
If you want to try something that actually does compile for sure
against 2.6.25 try the stable compat-wireless for 2.6.32.5 and use
./scripts/driver-select:
http://bombadil.infradead.org/~mcgrof/tmp/compat-wireless-2.6.32.5-rc3.tar.bz2
Luis
next prev parent reply other threads:[~2010-01-27 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 6:44 Building of compat-wireless-old in 2.6.25 BSP kernel for PowerPC architecture PAN Sunny S K
2010-01-26 7:28 ` Pavel Roskin
2010-01-26 16:31 ` X Xiao
2010-01-26 16:53 ` Luis R. Rodriguez
2010-01-27 10:48 ` PAN Sunny S K
2010-01-27 18:06 ` Luis R. Rodriguez [this message]
2010-01-29 6:41 ` PAN Sunny S K
2010-01-29 17:35 ` Pavel Roskin
2010-02-01 4:06 ` PAN Sunny S K
2010-02-01 4:14 ` Gábor Stefanik
2010-02-01 4:29 ` PAN Sunny S K
2010-02-01 18:03 ` Gábor Stefanik
2010-02-02 12:15 ` Sunny Pan
2010-01-27 22:02 ` Pavel Roskin
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=43e72e891001271006l3422b6e2iccb89954feeaa34b@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sunnypan@ust.hk \
/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