From: Jeff Garzik <jeff@garzik.org>
To: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
Cc: Leon Woestenberg <leon.woestenberg@gmail.com>,
Linux PPC <linuxppc-dev@ozlabs.org>, Tejun Heo <htejun@gmail.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: known working sata_sil24.c setup on powerpc platforms?
Date: Wed, 06 Apr 2011 14:12:47 -0400 [thread overview]
Message-ID: <4D9CAD1F.6060500@garzik.org> (raw)
In-Reply-To: <C3A1EF35-6CB6-4674-8B0B-44CD1657FE87@boeing.com>
On 04/06/2011 01:48 PM, Moffett, Kyle D wrote:
> On Apr 06, 2011, at 13:00, Leon Woestenberg wrote:
>> after investigating problems with sata_sil24.c on a freescale p2020
>> soc, I wonder if this driver works on powerpc at all?
>>
>> Does anyone know of a working setup of sata_sil24 on a big endian
>> powerpc system?
>
> Our P2020 boards work fine with legacy PCI interrupts (I think it's a sil3124 over PCI-E); the only deficiency is that MSI does not seem to work.
>
> I know our MSI *does* work in general because we have an Intel 82571EB chipset also attached via PCI-E with working MSI.
We've definitely had issues with sata_sil24 + MSI, also...
sata_sil24 does work on big endian in general.
Jeff
next prev parent reply other threads:[~2011-04-06 18:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 17:00 known working sata_sil24.c setup on powerpc platforms? Leon Woestenberg
2011-04-06 17:48 ` Moffett, Kyle D
2011-04-06 18:12 ` Jeff Garzik [this message]
2011-04-06 18:50 ` Leon Woestenberg
2011-04-06 20:49 ` Felix Radensky
2011-04-06 20:58 ` Leon Woestenberg
2011-04-06 21:05 ` Felix Radensky
2011-04-07 4:48 ` Kushwaha Prabhakar-B32579
2011-04-07 16:52 ` Leon Woestenberg
2011-04-08 3:44 ` Kushwaha Prabhakar-B32579
2011-04-08 8:24 ` Leon Woestenberg
2011-04-08 8:31 ` Kushwaha Prabhakar-B32579
2011-04-08 9:12 ` Leon Woestenberg
2011-04-08 9:41 ` Kushwaha Prabhakar-B32579
2011-04-08 12:19 ` Leon Woestenberg
2011-04-08 12:35 ` Kushwaha Prabhakar-B32579
2011-04-08 14:33 ` Leon Woestenberg
2011-04-07 8:27 ` Martyn Welch
2011-04-07 16:54 ` Leon Woestenberg
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=4D9CAD1F.6060500@garzik.org \
--to=jeff@garzik.org \
--cc=Kyle.D.Moffett@boeing.com \
--cc=htejun@gmail.com \
--cc=leon.woestenberg@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).