All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Zimman <chris@cryptoapps.com>
To: Oliver Amft <oam@gmx.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCI DMA memory problem
Date: Tue, 24 Jun 2003 14:19:35 -0500	[thread overview]
Message-ID: <20030624191935.GA9845@dingdong.cryptoapps.com> (raw)
In-Reply-To: <3EF8A001.2090603@gmx.net>


On Tue, Jun 24, 2003 at 09:01:21PM +0200, Oliver Amft wrote:
>
> 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).

My first thought is -- is/are the SDRAM bank(s) configured correctly?

I don't know that it'd necessarily be related, but for the 405GP,
PPCBoot 1.2.0 doesn't have the PCI bridge setup quite right for all
PCI devices (eg. 82559 won't work).  I have code to fix the bridge
setup if you need it -- although I'm not even certain they exist in
the GPR.

--Chris

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-24 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 19:01 PCI DMA memory problem Oliver Amft
2003-06-24 19:19 ` Chris Zimman [this message]
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=20030624191935.GA9845@dingdong.cryptoapps.com \
    --to=chris@cryptoapps.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=oam@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.