From: Peter Hurley <peter@hurleysoftware.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: Enable physical DMA above 4GB
Date: Fri, 29 Mar 2013 07:31:01 -0400 [thread overview]
Message-ID: <1364556661.3559.63.camel@thor.lan> (raw)
In-Reply-To: <515578D0.9090701@ladisch.de>
On Fri, 2013-03-29 at 12:19 +0100, Clemens Ladisch wrote:
> Peter Hurley wrote:
> > On Fri, 2013-03-29 at 11:44 +0100, Stefan Richter wrote:
> >>> On Mar 26 Peter Hurley wrote:
> >>>> The FW643e-2 is natively PCIe (not behind a bridge) and supports phys
> >>>> DMA past 4GB (the datasheet says all 48 bits but I can only test it out
> >>>> to 10GB).
> >>>>
> >>>> I thought the FW643e was as well? You'll have to test that out :)
> >>
> >> Does lspci or something similar show which PCI devices are capable of 64 bit
> >> wide addressing?
> >
> > Not definitively.
> >
> > Usually (but not always), if the host registers are 64-bit addressable,
> > then the device supports DAC.
>
> DACs are a feature of conventional PCI.
>
> All PCI Express devices are 64-bit addressable. In the lspci output, PCIe
> devices have the "Express" capability.
The "device" could be sitting behind a PCIe-PCI bridge that _only_
supports the host window for 64-bit. All other 64-bit decodes could
return garbage.
> However, whether a device can *generate* 64-bit DMA requests is completely
> device-specific.
prev parent reply other threads:[~2013-03-29 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:22 [PATCH] firewire: Enable physical DMA above 4GB Peter Hurley
2013-03-26 16:12 ` Clemens Ladisch
2013-03-26 17:04 ` Peter Hurley
2013-03-26 18:22 ` Clemens Ladisch
2013-03-26 18:56 ` Stefan Richter
2013-03-26 19:08 ` Peter Hurley
2013-03-26 20:35 ` Stefan Richter
2013-03-29 10:44 ` Stefan Richter
2013-03-29 10:50 ` Peter Hurley
2013-03-29 11:19 ` Clemens Ladisch
2013-03-29 11:31 ` Peter Hurley [this message]
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=1364556661.3559.63.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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.