From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>,
Olof Johansson <olof@lixom.net>,
linuxppc-dev@lists.ozlabs.org
Subject: Kernel 3.15: Boot problems with a PA6T board
Date: Wed, 18 Jun 2014 19:42:46 +0200 [thread overview]
Message-ID: <53A1CF96.1070907@xenosoft.de> (raw)
In-Reply-To: <25927053.1589.1403105603389.JavaMail.adrian@Gurnard>
On 18.06.14 17:33, Adrian Cox wrote:
>
> ----- Original Message -----
>> From: "Christian Zigotzky" <chzigotzky@xenosoft.de>
>>>> Christian
>>> But my opinion is, that's normal for the SB600 south bridge to
>>> presents itself as multiple devices on the PCIe bus on x86 PCs. I
>>> see
>>> a lot of PCs with SB600 south bridge on the internet. And the Linux
>>> kernel works with this south bridge. Or is it a powerpc issue?
>>>
> It is a powerpc issue. The SB600 connects to the AMD north bridge in a PC using a mode which is not PCIe compliant, and this makes the SB600 internal units appear as though they are on the root bus of a legacy PC. The powerpc does not have this built-in SB600 support.
>
>
> Adrian
>
next parent reply other threads:[~2014-06-18 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25927053.1589.1403105603389.JavaMail.adrian@Gurnard>
2014-06-18 17:42 ` Christian Zigotzky [this message]
2014-05-04 16:02 Boot problems with a PA6T board Christian Zigotzky
2014-05-05 5:48 ` Michael Ellerman
2014-05-13 12:06 ` Christian Zigotzky
2014-05-26 12:26 ` Michael Ellerman
2014-05-27 23:08 ` Kernel 3.15: " Christian Zigotzky
2014-05-28 4:23 ` Michael Ellerman
2014-05-28 8:53 ` Christian Zigotzky
2014-05-28 11:25 ` Christian Zigotzky
2014-05-29 2:48 ` Michael Ellerman
2014-05-31 10:28 ` Christian Zigotzky
2014-05-31 11:01 ` Christian Zigotzky
2014-05-31 22:33 ` Christian Zigotzky
2014-06-10 10:58 ` Christian Zigotzky
2014-06-10 13:20 ` Christian Zigotzky
2014-06-18 6:51 ` Michael Ellerman
2014-06-18 8:57 ` Christian Zigotzky
2014-06-18 9:26 ` Christian Zigotzky
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=53A1CF96.1070907@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=olof@lixom.net \
/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.