From: Felix Radensky <felix@embedded-sol.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: known working sata_sil24.c setup on powerpc platforms?
Date: Thu, 07 Apr 2011 00:05:59 +0300 [thread overview]
Message-ID: <4D9CD5B7.3070601@embedded-sol.com> (raw)
In-Reply-To: <BANLkTimMatkioUudyaiy+r68=MyrJqiYQg@mail.gmail.com>
Hi Leon,
On 04/06/2011 11:58 PM, Leon Woestenberg wrote:
> Hello Felix,
>
> On Wed, Apr 6, 2011 at 10:49 PM, Felix Radensky<felix@embedded-sol.com> wrote:
>> I think there's a hardware problem with mini PCI-E slot
>> on P2020RDB related to legacy IRQ routing. See this
>> thread for details
>> http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg40037.html
>>
>
> Unfortunately the PCIe is slot already occupied, so that's why I
> searched for and found the Mini PCIe Sil3132 card.
>
> Legacy IRQ routing on PCIe is broken in what sense? Software (device
> tree, kernel) or silicon (p2020) ?
It's a board design problem specific to P2020RDB. Maybe it's
fixed in latest board revisions. I have P2020RDB rev C and the
problem is still there. Freescale people on the list should know
better.
> On the MSI side, I'm getting quite far on transfers, but at one point
> the device stalls. Maybe a race condition in interrupt handling in
> sata_sil24.c?
Sorry, cannot help you with that. I have no experience with
sata_sil24.
Felix.
next prev parent reply other threads:[~2011-04-06 21:06 UTC|newest]
Thread overview: 32+ 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 17:48 ` Moffett, Kyle D
2011-04-06 18:12 ` Jeff Garzik
2011-04-06 18:12 ` Jeff Garzik
2011-04-06 18:50 ` Leon Woestenberg
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 [this message]
2011-04-07 4:48 ` Kushwaha Prabhakar-B32579
2011-04-07 4:48 ` Kushwaha Prabhakar-B32579
2011-04-07 16:52 ` Leon Woestenberg
2011-04-07 16:52 ` Leon Woestenberg
2011-04-08 3:44 ` Kushwaha Prabhakar-B32579
2011-04-08 3:44 ` Kushwaha Prabhakar-B32579
2011-04-08 8:24 ` Leon Woestenberg
2011-04-08 8:24 ` Leon Woestenberg
2011-04-08 8:31 ` Kushwaha Prabhakar-B32579
2011-04-08 8:31 ` Kushwaha Prabhakar-B32579
2011-04-08 9:12 ` Leon Woestenberg
2011-04-08 9:12 ` Leon Woestenberg
2011-04-08 9:41 ` Kushwaha Prabhakar-B32579
2011-04-08 9:41 ` Kushwaha Prabhakar-B32579
2011-04-08 12:19 ` Leon Woestenberg
2011-04-08 12:19 ` Leon Woestenberg
2011-04-08 12:35 ` Kushwaha Prabhakar-B32579
2011-04-08 12:35 ` Kushwaha Prabhakar-B32579
2011-04-08 14:33 ` Leon Woestenberg
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=4D9CD5B7.3070601@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=leon.woestenberg@gmail.com \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.