From: Johannes Erdfelt <johannes@erdfelt.com>
To: Jes Sorensen <jes@sunsite.dk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Determine if card is in 32 or 64 bit PCI slot?
Date: Tue, 14 Aug 2001 12:29:19 -0400 [thread overview]
Message-ID: <20010814122919.G3126@sventech.com> (raw)
In-Reply-To: <20010808161703.Q21901@sventech.com> <E15UaNj-00062K-00@the-village.bc.nu> <20010808165919.R21901@sventech.com> <d3elqe63g2.fsf@lxplus015.cern.ch>
In-Reply-To: <d3elqe63g2.fsf@lxplus015.cern.ch>; from jes@sunsite.dk on Tue, Aug 14, 2001 at 05:55:57PM +0200
On Tue, Aug 14, 2001, Jes Sorensen <jes@sunsite.dk> wrote:
> >>>>> "Johannes" == Johannes Erdfelt <johannes@erdfelt.com> writes:
>
> Johannes> On Wed, Aug 08, 2001, Alan Cox <alan@lxorguk.ukuu.org.uk>
> Johannes> wrote:
> >> Are you sure the card actually needs this. Most such cards support
> >> dual address cycle, so when placed in a 32bit slot will still do
> >> 64bit DMA
>
> Johannes> No I don't know if it's needed. I had no idea that PCI could
> Johannes> do that.
>
> Johannes> Is dual address cycle mandated by the PCI specs?
>
> According to the PCI spec "The master is required in all cases to use
> two clocks to communicate a 64-bit address, since the width of a
> target's bus is not known during the address phase."
>
> Aka, the answer to your question is yes.
Ahh, excellent. Thank you very much.
JE
next prev parent reply other threads:[~2001-08-14 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 20:17 Determine if card is in 32 or 64 bit PCI slot? Johannes Erdfelt
2001-08-08 20:56 ` Alan Cox
2001-08-08 20:59 ` Johannes Erdfelt
2001-08-14 15:55 ` Jes Sorensen
2001-08-14 16:29 ` Johannes Erdfelt [this message]
2001-08-09 18:44 ` disappearing cdrom on reboot with 2.4.7-ac10 David Flood
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=20010814122919.G3126@sventech.com \
--to=johannes@erdfelt.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jes@sunsite.dk \
--cc=linux-kernel@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