From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH] firewire: Enable physical DMA above 4GB
Date: Tue, 26 Mar 2013 21:35:32 +0100 [thread overview]
Message-ID: <20130326213532.38a7bd4c@stein> (raw)
In-Reply-To: <1364324929.3866.13.camel@thor.lan>
On Mar 26 Peter Hurley wrote:
> On Tue, 2013-03-26 at 19:56 +0100, Stefan Richter wrote:
> > It has been a long time though since I last checked whether PhyUpperBound
> > is implemented; maybe it has become more widespread than it was back then.
> >
> > Or maybe it hasn't: All OHCI-1394 chips that ever came to market are 32
> > bit chips anyway. So the few rare ones that do support PhyUpperBound
> > larger than 4 GB cannot in fact use it.
> >
> > Or am I severely behind the times about this?
>
> 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 :)
OK, will do.
--
Stefan Richter
-=====-===-= --== ==-=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2013-03-26 20:36 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 [this message]
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
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=20130326213532.38a7bd4c@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=peter@hurleysoftware.com \
/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