From: John David Anglin <dave.anglin@bell.net>
To: Carlo Pisani <carlojpisani@gmail.com>
Cc: linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: C3600, sata controller
Date: Tue, 14 May 2019 08:10:40 -0400 [thread overview]
Message-ID: <44c01dbf-4b6c-c37d-d5cc-844e5679dea5@bell.net> (raw)
In-Reply-To: <CA+QBN9CgMRFmv+isvH-Y=FCCFwKhmD5_5s5u32xg+wk-gTLK5A@mail.gmail.com>
On 2019-05-14 4:15 a.m., Carlo Pisani wrote:
> I am surprised that a PCI-X chip isn't able to switch into PCI64 mode.
> Cards are usually declared "backward compatible", and it would be just
> a matter of "how" to handle the finite state machine that drives the
> PCI, plus the onboard PLL and synchronization.
I agree but it appears fallback requires BIOS or a QUIRK to configure card. One would have to
look at driver and/or BIOS to see what is/can done. Maybe OpenBIOS has something.
There is ENABLE_HARDFAIL config option in lba_pci.c which determines whether HPMC occurs.
Soft fail might be useful to debug. However, I doubt there's enough public information to configure
card given what Alan said.
>
>
>> Here are some Adaptec 64-bit cards that I found.
>> https://storage.microsemi.com/en-us/support/raid/sata/aar-2410sa/
>> https://storage.microsemi.com/en-us/support/raid/sata/aar-21610sa/
> as written here (1), we have already tested Adaptec 2410SA, and I have
> also recently received an email by AlanCox confirming that the card is
> x86-only!
>
> Subsystem: Adaptec AAR-2410SA PCI SATA 4ch (Jaguar II)
>
> It fails on every non-x86 machine because it relies on PC-BIOS
> extension for the initialization of the onboard Intel i960 chip, and
> we do not have any Linux kernel driver able to do what the PC-BIOS
> does.
I had listed these cards because they are PCI64 and the Adaptec site didn't say Intel
architecture was required. There was one card that claimed to be PCI-X and PCI64
(both 3.3 and 5V signalling) but it required Intel or AMD architecture.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2019-05-14 12:10 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
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 [this message]
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=44c01dbf-4b6c-c37d-d5cc-844e5679dea5@bell.net \
--to=dave.anglin@bell.net \
--cc=carlojpisani@gmail.com \
--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).