From: Oliver Amft <oam@gmx•net>
To: linuxppc-embedded@lists•linuxppc.org
Subject: PCI DMA memory problem
Date: Tue, 24 Jun 2003 21:01:21 +0200 [thread overview]
Message-ID: <3EF8A001.2090603@gmx.net> (raw)
I am implementing a network driver for a DMA device on a custom
405GP/GPr based board. The networking device is attached over PCI bus.
Kernel is currently 2.4.21. BIOS is PPCBoot 1.2.0.
To map the data buffers from skb the driver uses pci_map_single(). When
starting the kernel with SDRAM size configurations other than 32MByte
the device is unable to transfer data (currupted data) - descriptor
dword read/write-back works (set up with pci_alloc_consistent()). For
the kernel start option mem=32MB everything is fine (descriptor +
correct data).
I am wondering if someone has stumbled over this too - any advice
appreciated.
Thanks,
Oliver
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-06-24 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 19:01 Oliver Amft [this message]
2003-06-24 19:19 ` PCI DMA memory problem Chris Zimman
2003-06-24 20:22 ` Wolfgang Denk
2003-06-25 12:48 ` Mark Powell
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 12:36 Oliver Amft
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=3EF8A001.2090603@gmx.net \
--to=oam@gmx$(echo .)net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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