From: Johannes Berg <johannes@sipsolutions.net>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>, Michael Buesch <mb@bu3sch.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SSB: make it depend on PCI
Date: Thu, 06 Nov 2008 12:22:53 +0100 [thread overview]
Message-ID: <1225970573.3619.208.camel@johannes.berg> (raw)
In-Reply-To: <8bd0f97a0811060315j7d11e1a7p257a4a1bea640f7b@mail.gmail.com> (sfid-20081106_121527_240627_B635B0E2)
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
On Thu, 2008-11-06 at 06:15 -0500, Mike Frysinger wrote:
> while that may be the intent, it doesnt work today.
>
> drivers/ssb/main.c always includes linux/ssb/ssb.h
>
> linux/ssb/ssb.h always calls pci_dma_* functions
>
> arches that do not support PCI fail to build:
> CC drivers/ssb/main.o
> In file included from drivers/ssb/ssb_private.h:5,
> from drivers/ssb/main.c:12:
> include/linux/ssb/ssb.h: In function 'ssb_dma_mapping_error':
> include/linux/ssb/ssb.h:430: error: implicit declaration of function 'pci_dma_mapping_error'
> include/linux/ssb/ssb.h: In function 'ssb_dma_sync_single_for_cpu':
> include/linux/ssb/ssb.h:475: error: implicit declaration of function 'pci_dma_sync_single_for_cpu'
> include/linux/ssb/ssb.h: In function 'ssb_dma_sync_single_for_device':
> include/linux/ssb/ssb.h:493: error: implicit declaration of function 'pci_dma_sync_single_for_device'
> include/linux/ssb/ssb.h: In function 'ssb_dma_sync_single_range_for_cpu':
> include/linux/ssb/ssb.h:517: error: implicit declaration of function 'dma_sync_single_range_for_cpu'
> include/linux/ssb/ssb.h: In function 'ssb_dma_sync_single_range_for_device':
> include/linux/ssb/ssb.h:538: error: implicit declaration of function 'dma_sync_single_range_for_device'
> drivers/ssb/main.c: In function 'ssb_dma_set_mask':
> drivers/ssb/main.c:1183: error: implicit declaration of function 'dma_set_mask'
That seems odd, shouldn't at least the dma_sync_* functions and
dma_set_mask be supported?
There probably need to be ifdefs, if you look at those functions then
you'll see that it depends on the bustype the device is on.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-06 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 9:51 Mike Frysinger
2008-11-06 11:07 ` Johannes Berg
2008-11-06 11:15 ` Mike Frysinger
2008-11-06 11:22 ` Johannes Berg [this message]
2008-11-06 11:26 ` Mike Frysinger
2008-11-06 11:29 ` Johannes Berg
2008-11-06 11:32 ` Mike Frysinger
2008-11-06 11:35 ` Johannes Berg
2008-11-06 16:59 ` Michael Buesch
2008-11-06 21:14 ` Mike Frysinger
2008-11-06 21:24 ` Michael Buesch
2008-11-06 16:56 ` Michael Buesch
2008-11-09 10:51 ` Geert Uytterhoeven
2008-11-09 11:49 ` Michael Buesch
2008-11-06 16:55 ` Michael Buesch
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=1225970573.3619.208.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=vapier.adi@gmail.com \
--cc=vapier@gentoo.org \
/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
all inboxes | Powered by JetHome®