From: Jan Neskudla <jan.neskudla.ext@nsn.com>
To: ext Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/5] rapidio: adding memory mapping IO support and misc fixes
Date: Fri, 08 May 2009 12:06:35 +0200 [thread overview]
Message-ID: <1241777196.16400.25.camel@demuxf9c> (raw)
In-Reply-To: <AF270294-0B90-4935-9D4A-F17EB7811CE2@kernel.crashing.org>
On Thu, 2009-05-07 at 10:21 -0500, ext Kumar Gala wrote:
> On May 7, 2009, at 9:10 AM, Jan Neskudla wrote:
>
> > And one more think, when I enabled usage of DMA, rionet does not
> > compile too,
> > but in this case I do not have a fix. I tested this on kernel
> > 2.6.29.1 and
> > EP8548 as target board.
>
> What exactly do you mean by that? What CONFIG options cause compile
> failure? Can you post the compiler error.
>
> - k
The problem is with the missing stucture dma_client in the kernel tree
sources. It looks to me that a dma model changed after 2.6
.28. Here are the details.
I used a pristine kernel 2.6.29 + patch 2.6.29.1 than Leo's patches in
this order.
rio-warn_unused_result-warnings-fix.patch
rionet-add-memory-access-to-simulated-Ethernet-over-rapidio.patch
powerpc-add-memory-map-support-to-Freescale-RapioIO-block.patch
powerpc-fsl_rio-use-LAW-address-from-device-tree.patch
rapidio-add-common-mapping-APIs-for-RapidIO-memory-access.patch
Important CONFIG options are:
PPC_86xx=y
HPC8641_HPCN=y
RAPIDIO=y
DMADEVICES=y
FSL_DMA=y !!
NETDEVICES=y
RIONET=y/m
RIONET_MEMMAP=y
RIONET_DMA=y !!
And the error during compilation:
CC drivers/net/rionet.o
drivers/net/rionet.c:110: error: field `rio_dma_client' has incomplete
type
drivers/net/rionet.c: In function `rio_send_mem':
drivers/net/rionet.c:239: error: parse error before "rnet"
drivers/net/rionet.c: At top level:
drivers/net/rionet.c:514: warning: "enum dma_state" declared inside
parameter list
drivers/net/rionet.c:514: warning: its scope is only this definition or
declaration, which is probably not what you want
drivers/net/rionet.c:515: error: parameter `state' has incomplete type
drivers/net/rionet.c:515: error: return type is an incomplete type
drivers/net/rionet.c: In function `rionet_dma_event':
drivers/net/rionet.c:516: warning: type defaults to `int' in declaration
of `__mptr'
drivers/net/rionet.c:516: warning: initialization from incompatible
pointer type
drivers/net/rionet.c:518: error: variable `ack' has initializer but
incomplete type
drivers/net/rionet.c:518: error: `DMA_DUP' undeclared (first use in this
function)
drivers/net/rionet.c:518: error: (Each undeclared identifier is reported
only once
drivers/net/rionet.c:518: error: for each function it appears in.)
drivers/net/rionet.c:518: error: storage size of 'ack' isn't known
drivers/net/rionet.c:522: error: `DMA_RESOURCE_AVAILABLE' undeclared
(first use in this function)
drivers/net/rionet.c:524: error: `DMA_ACK' undeclared (first use in this
function)
drivers/net/rionet.c:531: error: `DMA_RESOURCE_REMOVED' undeclared
(first use in this function)
drivers/net/rionet.c:544: warning: `return' with a value, in function
returning void
drivers/net/rionet.c:518: warning: unused variable `ack'
drivers/net/rionet.c: In function `rionet_dma_register':
drivers/net/rionet.c:553: error: implicit declaration of function
`dma_async_client_register'
drivers/net/rionet.c:554: error: implicit declaration of function
`dma_async_client_chan_request'
drivers/net/rionet.c: In function `rionet_close':
drivers/net/rionet.c:731: error: implicit declaration of function
`dma_async_client_unregister'
make[2]: *** [drivers/net/rionet.o] Error 1
Jan
next prev parent reply other threads:[~2009-05-08 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 14:10 [PATCH 0/5] rapidio: adding memory mapping IO support and misc fixes Jan Neskudla
2009-05-07 15:21 ` Kumar Gala
2009-05-08 10:06 ` Jan Neskudla [this message]
2009-05-08 10:28 ` Gerhard Jaeger
2009-05-08 11:39 ` Jan Neskudla
-- strict thread matches above, loose matches on Subject: below --
2009-04-28 10:16 Li Yang
2009-04-28 12:06 ` Kumar Gala
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=1241777196.16400.25.camel@demuxf9c \
--to=jan.neskudla.ext@nsn.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).