From: Carlo Pisani <carlojpisani@gmail.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: C3600, sata controller
Date: Tue, 14 May 2019 01:24:47 +0200 [thread overview]
Message-ID: <CA+QBN9BkXRp2hCd4ADXtWOisHz1Fa0JvWo-0iR56ZTDZiaG=Yg@mail.gmail.com> (raw)
In-Reply-To: <66bf0e79-16a4-a411-19ba-cd7d5a232976@bell.net>
> The issue is probably the signalling voltage and clock rate capability.
PCI_X means 64bit, no matter voltage of anything.
You can have PCI_X at 33Mhz, 66Mhz, 100Mhz
You can have PCI_X at 5V, or PCI_X at 3.3V
> TTL logic, it is likely that 3.3V CMOS logic can't provide the high level for 5V TTL logic.
inputs are 5V tolerant, outputs are already ok about their levels
> I suspect the only slot that might work with a PCI-X card is the 3.3V SL2.
the SIL24 PCI_X card has been already checked in that slot, and it
fails in the same way as it fails when it's plugged in one of the 5V
slots
> However, if you see I/O errors in the PIM dump following an HPMC, then it's not compatible.
if things were that way, it wouldn't be a random failure, but rather
an immediate failure
to me, it looks more like a timing error, or something bad with DMA 64bit
it's like to force the card to be "DMA32bit" only, just to check it
next prev parent reply other threads:[~2019-05-13 23:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 21:45 linux-next: Signed-off-by missing for commit in the parisc-hd tree Stephen Rothwell
2019-05-02 5:48 ` Helge Deller
2019-05-12 20:44 ` C3600, sata controller Carlo Pisani
2019-05-12 20:49 ` Carlo Pisani
2019-05-12 21:10 ` John David Anglin
2019-05-12 21:15 ` Carlo Pisani
2019-05-13 23:14 ` John David Anglin
2019-05-13 23:24 ` Carlo Pisani [this message]
2019-05-13 23:47 ` Carlo Pisani
2019-05-14 1:50 ` John David Anglin
2019-05-14 8:22 ` Carlo Pisani
[not found] ` <CA+QBN9CgMRFmv+isvH-Y=FCCFwKhmD5_5s5u32xg+wk-gTLK5A@mail.gmail.com>
2019-05-14 12:10 ` John David Anglin
2019-05-14 12:29 ` Carlo Pisani
2019-05-14 12:57 ` C3600, optical Fibre Channel, any card? Carlo Pisani
2019-05-14 13:01 ` C3600, sata controller Sven Schnelle
2019-05-14 14:23 ` John David Anglin
2019-05-17 15:43 ` Carlo Pisani
2019-05-17 17:21 ` Helge Deller
2019-05-17 18:05 ` John David Anglin
2019-05-17 18:25 ` Carlo Pisani
2019-05-13 15:10 ` Carlo Pisani
2019-05-13 21:58 ` Carlo Pisani
2019-05-17 17:31 ` Carlo Pisani
2019-05-25 8:59 ` Carlo Pisani
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='CA+QBN9BkXRp2hCd4ADXtWOisHz1Fa0JvWo-0iR56ZTDZiaG=Yg@mail.gmail.com' \
--to=carlojpisani@gmail.com \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@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;
as well as URLs for NNTP newsgroup(s).