From: Jeff Andre <andre@guardian.stortek.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 440GP DMA and dma.h
Date: Tue, 9 Dec 2003 12:52:17 -0700 [thread overview]
Message-ID: <20031209195217.GA28122@guardian.stortek.com> (raw)
I'm trying to get DMA working on a custom board with a 440GP. I was
having problem getting a DMA transfer started and traced the problem
to 'enable_dma' not being called. After a bit amount of research I
found that my device driver didn't have an undefined external reference
to 'enable_dma'.
I traced the problem to the include of <linux/pci.h> that eventually
included <asm/scatterlist.h> that included <asm/dma.h>. This header
has many of the DMA functions defined as inline and static, 'enable_dma'
being one of them. If I comment out the include of <asm/dma.h> the
compiler finds the include in my driver of <asm/ppc4xx_dma.h> and DMA
transfers work (sort-of).
Does anyone have a clue as to what I'm doing wrong? I can't believe
I'm the first to discover this.
Thanks,
Jeff Andre
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-12-09 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031209195217.GA28122@guardian.stortek.com \
--to=andre@guardian.stortek.com \
--cc=linuxppc-embedded@lists.linuxppc.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).