mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <RJohnson@Route495Software.com>
To: "\"Mark Hounschell\"" <dmarkh@cfl.rr.com>
Cc: <linux-pci@vger.kernel.org>,
	"Mark Hounschell" <dmarkh@cfl.rr.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: problems doing direct dma from a pci device to pci-e device
Date: Fri, 11 Sep 2009 11:46:09 -0400	[thread overview]
Message-ID: <48E3B73EAC22453CA65D2431F2F47B69@Route495PC> (raw)
In-Reply-To: <4AAA6BE7.8040306@compro.net>

----- Original Message ----- 
From: "Mark Hounschell" <markh@compro.net>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-pci@vger.kernel.org>; "Mark Hounschell" <dmarkh@cfl.rr.com>; 
<linux-kernel@vger.kernel.org>
Sent: Friday, September 11, 2009 11:25 AM
Subject: Re: problems doing direct dma from a pci device to pci-e device


> Alan Cox wrote:
>>> I now have an AM3 based DFI DK 790FXB-M3H5 motherboard. This board has 3 
>>> regular
>>> PCI slots and 3 PCI-E (16x) slots. I also have a PCI-E (x4) version of 
>>> the VMIC-5565
>>> reflective memory  card in one of the PCI-E slots and our gpiohsd card 
>>> in one of the regular
>>> PCI slots. All on the motherboard. No expansion slots being used. 
>>> However I cannot get
>>> data from our gpiohsd into the PCI-E VMIC-5565 cards memory. I can 
>>> certainly get the data there
>>> from a userland buffer, no problem. Just not from one card to the other 
>>> directly. Oh and when
>>> I put the regular PCI version of the VMIC into one of the regular PCI 
>>> slots everything works
>>> as expected. They are then both on the same PCI bus and no bridges are 
>>> involved though.

The read I mentioned was a read immediately following the DMA operation. 
Some PCI (PCI-X using
a HyperTransport serial bus) implimentations deliberately time-out to 
prevent a hung system. The result
that I've seen was no data anywhere. It just vanished!

Reading the destination a few milliseconds (or seconds) later won't prevent 
this timeout!

Cheers,
Richard B. Johnson
http://Route495Software.com/







  reply	other threads:[~2009-09-11 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 14:13 Mark Hounschell
2009-09-11 14:41 ` Richard B. Johnson
2009-09-11 14:50   ` Mark Hounschell
2009-09-11 14:47 ` Alan Cox
2009-09-11 15:25   ` Mark Hounschell
2009-09-11 15:46     ` Richard B. Johnson [this message]
2009-09-11 19:42       ` Mark Hounschell
2009-09-11 20:04     ` Mark Hounschell
2009-09-14  5:36       ` Grant Grundler
2009-09-14  8:03         ` Mark Hounschell
2009-09-15 11:23   ` Mark Hounschell

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=48E3B73EAC22453CA65D2431F2F47B69@Route495PC \
    --to=rjohnson@route495software.com \
    --cc=dmarkh@cfl.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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®