linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org, Olof Johansson <olof@lixom.net>
Subject: Kernel 3.15: Boot problems with a PA6T board
Date: Wed, 18 Jun 2014 10:57:54 +0200	[thread overview]
Message-ID: <53A15492.3090604@xenosoft.de> (raw)
In-Reply-To: <1403074303.32307.5.camel@concordia>

Am 18.06.14 08:51, schrieb Michael Ellerman:
> On Tue, 2014-06-10 at 15:20 +0200, Christian Zigotzky wrote:
>> Hi All,
>>
>> Could you help me to remove the changes of the PCI code, please? Or
>> which patches shall I remove to get the old PCI code?
> Hi Christian,
>
> Thanks for doing the bisect. It wasn't clear why that change was causing your
> issue, so I guess we're a bit stuck.
>
> Olof (on CC), was going to try and look at it when he got some spare time.
> Please keep him on CC.
>
> cheers
>
>
>
Hi Michael,

Thank you for your answer. Adrian told me the reason about this issue.

Quote Adrian:

As I recall, PCI resource allocation on Nemo was always a little strange 
due to using an AMD south bridge together with the PA6T north bridge. 
The south bridge does not behave as a standard PCIe device, but instead 
presents itself as multiple devices on the PCIe root bus. This is not 
compliant with the PCIe specification. We modified the core powerpc PCI 
code so that Nemo could boot, but the changes to PCI code in 3.15 have 
broken the old workaround. I don't understand the PCI changes in 3.15 
enough to comment further at this point.

Regards,
Adrian

Quote end

Cheers,

Christian

  reply	other threads:[~2014-06-18  9:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 16:02 Boot problems with a PA6T board Christian Zigotzky
2014-05-05  5:48 ` Michael Ellerman
2014-05-05  9:41   ` Christian Zigotzky
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 [this message]
2014-06-18  9:26                               ` Christian Zigotzky
     [not found] <25927053.1589.1403105603389.JavaMail.adrian@Gurnard>
2014-06-18 17:42 ` 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=53A15492.3090604@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 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).