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: Wed, 17 Feb 2010 22:44:35 -0500	[thread overview]
Message-ID: <1266464675.3065.30.camel@mj> (raw)
In-Reply-To: <43e72e891002161459m4174654aj8d7985f32cb8678d@mail.gmail.com>

On Tue, 2010-02-16 at 14:59 -0800, Luis R. Rodriguez wrote:

> > Anyway, I'd rather see
> > dma_sync_single_range_for_device() for ARM backported.
> 
> Patches are welcomed for it indeed.

Here's the patch.  I'm not sure if include/net/compat-2.6.27.h or
compat/compat-2.6.27.h is the real source file, as I was patching the
downloaded tarball.

The missing functions are only used by b44.  The functions available in
2.6.26 don't have the offset argument, so I had to extend the range to
start at zero.  This could affect the b44 throughput, but I would not
worry too much about it.

The is another problem.  For some reason, CONFIG_SSB_PCMCIAHOST is
enabled in compat_autoconf.h, even though the target kernel lacks PCMCIA
support.  However, CONFIG_SSB_PCMCIAHOST is not set in the makefiles, so
ssb.ko is compiled with CONFIG_SSB_PCMCIAHOST, but pcmcia.o is not
linked into it, which leads to unresolved symbols.  However, the build
succeeds and there are no warnings about it.


--- a/include/net/compat-2.6.27.h
+++ b/include/net/compat-2.6.27.h
@@ -185,4 +185,28 @@
 
 #endif /* (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,27)) */
 
+#ifdef CONFIG_ARM
+
+/*
+ * The caller asks to handle a range between offset and offset + size,
+ * but we process a larger range from 0 to offset + size due to lack of
+ * offset support.
+ */
+
+static inline void dma_sync_single_range_for_cpu(struct device *dev,
+		dma_addr_t handle, unsigned long offset, size_t size,
+		enum dma_data_direction dir)
+{
+	dma_sync_single_for_cpu(dev, handle, offset + size, dir);
+}
+
+static inline void dma_sync_single_range_for_device(struct device *dev,
+		dma_addr_t handle, unsigned long offset, size_t size,
+		enum dma_data_direction dir)
+{
+	dma_sync_single_for_device(dev, handle, offset + size, dir);
+}
+
+#endif /* arm */
+
 #endif /* LINUX_26_27_COMPAT_H */

-- 
Regards,
Pavel Roskin

  parent reply	other threads:[~2010-02-18  3:44 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
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 [this message]
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=1266464675.3065.30.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).