public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 26 Jan 2010 08:53:34 -0800	[thread overview]
Message-ID: <43e72e891001260853s4811bc39s2399d138d0a7da83@mail.gmail.com> (raw)
In-Reply-To: <51523.143.89.144.207.1264488274.squirrel@sqmail.ust.hk>

On Mon, Jan 25, 2010 at 10:44 PM, PAN Sunny S K <sunnypan@ust.hk> wrote:
>And how can I solve the building problem between the
> compat-wireless-old and the 2.6.25 kernel?

compat-wireless-old is deprecated. I forked off a new compat-wireless
since mac80211 added multiqueue support a while ago, but recently
compat-wireless started to get support for older kernels again because
mac80211 stopped using the multiqueue support. By default the stable
compat-wireless releases up to the ones based on 2.6.32.3 had support
for kernels >= 2.6.25. Then if you enable only ath5k or ath9k you can
go even lower, to 2.6.23.

This all changed again for 2.6.32.4 where mac80211 once again
re-enabled multiqueue support but I did make an attempt to actually
backport that this time [1] down to 2.6.23 and actually even lower
kernels. That release hasn't been tested yet though so I'm waiting to
hear about results. I may get a chance to test a 2.6.23 kernel with
that snapshot at some point today, we'll see.

So apart from compat-wireless though you actually need the full SoC
support though and that is provided by openwrt but I am not sure down
to what kernel that is backported to. In any case you are better off
just upgrading to a newer kernel as others recommend.

[1] http://marc.info/?l=linux-wireless&m=126420655321607&w=2

  Luis

  parent reply	other threads:[~2010-01-26 16:53 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 [this message]
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=43e72e891001260853s4811bc39s2399d138d0a7da83@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