From: X Xiao <austinxxh-linux@yahoo.com>
To: linux-wireless@vger.kernel.org, PAN Sunny S K <sunnypan@ust.hk>
Subject: Re: Building of compat-wireless-old in 2.6.25 BSP kernel for PowerPC architecture
Date: Tue, 26 Jan 2010 08:31:38 -0800 (PST) [thread overview]
Message-ID: <796923.61885.qm@web55301.mail.re4.yahoo.com> (raw)
In-Reply-To: <51523.143.89.144.207.1264488274.squirrel@sqmail.ust.hk>
I would recommend you upgrade your kernel to a newer version, where compat-wireless works better with. 83xx is well supported by newer kernels.
xxiao
--- On Tue, 1/26/10, PAN Sunny S K <sunnypan@ust.hk> wrote:
> From: PAN Sunny S K <sunnypan@ust.hk>
> Subject: Building of compat-wireless-old in 2.6.25 BSP kernel for PowerPC architecture
> To: linux-wireless@vger.kernel.org
> Date: Tuesday, January 26, 2010, 12:44 AM
> Dear Sir,
>
> My name is Sunny, I'm from the MTrec group in Hong Kong
> University of
> Science and Technology. We are currently developing a
> network device which
> will utilize the wireless technology. As part of the
> development, we are
> examining different reference design from various
> companies. Currently
> we've received a MPC8377EWLAN from Freescale which we will
> need to port
> our application onto. Our application deployment on other
> device are
> currently based on 802.11abg Atheros card with Madwifi
> driver. Starting
> with this MPC8377EWLAN, we would like to trial with a new
> Atheros AR9160
> 802.11bgn card. Since the chipset is not supported by
> Madwifi, and the
> driver provided by Freescale is proprietary and has problem
> with
> wlanconfig list scan result, we try to build our own driver
> instead of
> relying on Freescale.
> The MPC8377EWLAN is using a PowerPC architecture MPC8377
> CPU and the
> firmware is built by using Freescale's LTIB, the kernel
> came with the LTIB
> is 2.6.25 which is slightly different from the mainstream
> 2.6.25 kernel.
> However, when I try to integrate the compat-wireless-old
> source into the
> LTIB's 2.6.25 kernel, error comes up in socket.c and many
> other networking
> source.
> Therefore, I'd like to seek for some advice of whether the
> compat-wireless-old could be compiled with linux kernels
> that is compiled
> with BSP like LTIB. And how can I solve the building
> problem between the
> compat-wireless-old and the 2.6.25 kernel?
>
> Thanks in advance.
>
> Best regards,
> Sunny Pan
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" 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:[~2010-01-26 16:31 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 [this message]
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
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=796923.61885.qm@web55301.mail.re4.yahoo.com \
--to=austinxxh-linux@yahoo.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