From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: compat-wireless + Linux 2.6.26.8 testing results
Date: Sun, 14 Feb 2010 00:10:22 -0500 [thread overview]
Message-ID: <1266124222.13902.42.camel@mj> (raw)
In-Reply-To: <43e72e891002121810g25d21eb5y254969458a9a58e7@mail.gmail.com>
On Fri, 2010-02-12 at 18:10 -0800, Luis R. Rodriguez wrote:
> The bleeding edge compat-wireless updates were stuck due to a
> bluetooth hunk failing on net/bluetooth/hidp/core.c, that should be
> fixed now, at least it compiles for me down to 2.6.27. I also hadn't
> updated a 2.6.33-rcx releases in a while, as well as 2.6.32.y release.
> This should all now be in synch with upstream. I never got reports
> about MQ support on older kernels so I just threw in the code, issues
> can be dealt with once actually found.
I've tried compiling all three tarballs against Linux 2.6.26.8. It's a
kernel with some hardware patches for arm architecture that are hard to
port to newer kernels, so compat-wireless would be very helpful.
compat-wireless-2.6.32.8 compiles just fine with ath5k selected.
compat-wireless-2.6.33-rc8 fails:
/home/proski/src/compat-wireless-2.6.33-rc8/net/mac80211/util.c: In
function '__ieee80211_wake_queue':
/home/proski/src/compat-wireless-2.6.33-rc8/net/mac80211/util.c:290:
error: implicit declaration of function 'netif_tx_wake_queue'
/home/proski/src/compat-wireless-2.6.33-rc8/net/mac80211/util.c:290:
error: implicit declaration of function 'netdev_get_tx_queue'
/home/proski/src/compat-wireless-2.6.33-rc8/net/mac80211/util.c: In
function '__ieee80211_stop_queue':
/home/proski/src/compat-wireless-2.6.33-rc8/net/mac80211/util.c:325:
error: implicit declaration of function 'netif_tx_stop_queue'
compat-wireless-2010-02-13 fails differently:
/home/proski/src/compat-wireless-2010-02-13/net/mac80211/iface.c: In
function 'ieee80211_if_setup':
/home/proski/src/compat-wireless-2010-02-13/net/mac80211/iface.c:738:
error: 'struct net_device' has no member named 'select_queue'
/home/proski/src/compat-wireless-2010-02-13/net/mac80211/iface.c: In
function 'ieee80211_setup_sdata':
/home/proski/src/compat-wireless-2010-02-13/net/mac80211/iface.c:790:
error: 'struct net_device' has no member named 'select_queue'
I tried enabling CONFIG_NETDEVICES_MULTIQUEUE, but it made no
difference.
It looks like compat-wireless-2.6.33-rc8 and compat-wireless-2010-02-13
don't have the patches to deal with the lack of netif_tx_wake_queue and
select_queue in Linux 2.6.26. compat-wireless-2.6.32.8 has such
patches.
If all drivers are selected, compat-wireless-2.6.32.8 fails:
In file included
from /home/proski/src/compat-wireless-2.6.32.8/drivers/net/b44.c:28:
/home/proski/src/compat-wireless-2.6.32.8/include/linux/ssb/ssb.h: In
function 'ssb_dma_sync_single_range_for_cpu':
/home/proski/src/compat-wireless-2.6.32.8/include/linux/ssb/ssb.h:595:
error: implicit declaration of function 'dma_sync_single_range_for_cpu'
/home/proski/src/compat-wireless-2.6.32.8/include/linux/ssb/ssb.h: In
function 'ssb_dma_sync_single_range_for_device':
/home/proski/src/compat-wireless-2.6.32.8/include/linux/ssb/ssb.h:620:
error: implicit declaration of function
'dma_sync_single_range_for_device'
That appears to be caused by the lack of
dma_sync_single_range_for_device on the arm architecture. Other
architectures have it. "make -k" doesn't find any other errors. All
other drivers compile fine.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-02-14 5:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 2:10 compat-wireless updated for 2.6.33-rc8, 2.6.32.8 and next-20100212 Luis R. Rodriguez
2010-02-14 5:10 ` Pavel Roskin [this message]
2010-02-16 21:23 ` compat-wireless + Linux 2.6.26.8 testing results Luis R. Rodriguez
2010-02-16 22:12 ` Pavel Roskin
2010-02-16 22:59 ` Luis R. Rodriguez
2010-02-17 0:45 ` Luis R. Rodriguez
2010-02-17 0:51 ` Luis R. Rodriguez
2010-02-18 4:23 ` Pavel Roskin
2010-02-18 6:15 ` Pavel Roskin
2010-02-18 18:30 ` Luis R. Rodriguez
2010-02-20 0:21 ` Pavel Roskin
2010-02-20 2:37 ` Luis R. Rodriguez
2010-02-18 3:44 ` Pavel Roskin
2010-02-18 18:29 ` Luis R. Rodriguez
2010-02-18 19:18 ` 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=1266124222.13902.42.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).