linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: compat-wireless + Linux 2.6.26.8 testing results
Date: Tue, 16 Feb 2010 17:12:20 -0500	[thread overview]
Message-ID: <1266358340.2659.37.camel@mj> (raw)
In-Reply-To: <43e72e891002161323v70636defr2500784ffb44d775@mail.gmail.com>

On Tue, 2010-02-16 at 13:23 -0800, Luis R. Rodriguez wrote:

> > 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.
> 
> Oh right, so I was hoping to get some reports on results of MQ
> backport on 2.6.32.y, I guess its OK enough to merge now and if its
> borked we can remove older kernel support or something.

I confirm that ath5k and ath9k actually work on that kernel, so the
results are good.

There are some funny messages from ath9k, but scanning still works, and
I don't think it's related to compat-wireless:

ath9k 0000:00:01.0: alloc_safe_buffer: could not alloc dma memory (size=3872)
ath9k 0000:00:01.0: map_single: unable to map unsafe buffer c6ffe020!
ath9k 0000:00:01.0: alloc_safe_buffer: could not alloc dma memory (size=3872)
ath9k 0000:00:01.0: map_single: unable to map unsafe buffer c6800020!

> > That appears to be caused by the lack of
> > dma_sync_single_range_for_device on the arm architecture.
> 
> Interesting... well that would just mean we have to lift SSB off of
> 2.6.28 kernels.

Perhaps you mean 2.6.26?  Anyway, I'd rather see
dma_sync_single_range_for_device() for ARM backported.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2010-02-16 22:12 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 ` compat-wireless + Linux 2.6.26.8 testing results Pavel Roskin
2010-02-16 21:23   ` Luis R. Rodriguez
2010-02-16 22:12     ` Pavel Roskin [this message]
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=1266358340.2659.37.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).