public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tirumala Marri <tmarri@apm•com>
To: Ayman El-Khashab <ayman@elkhashab•com>,
	Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@lists•ozlabs.org, Paul Mackerras <paulus@samba•org>
Subject: RE: [PATCH 0/1] ppc4xx: Fix PCIe scanning for the 460SX
Date: Tue, 31 May 2011 14:27:19 -0700	[thread overview]
Message-ID: <fa765cbed63d89c50a79b34f25dc9f5c@mail.gmail.com> (raw)
In-Reply-To: <20110527165108.GA1752@crust.elkhashab.com>

Not sure how I would know --  But with my eiger kit, I got a
cd from amcc that had a patched 2.6.30 or something kernel
in it to support the 460SX.  The pci code was basically
subverted by adding a "port->link=1" at the very end of the
link check to always force it to succeed.  However this code
never appeared in the public git repositories, so I am not
sure how the 460SX functioned (if it ever did) since the
link check that is in there now can't work on that SOC.


[marri]I don't know what PCI-E devices you use. We use E1000
As a device for testing. Link-up was working before the submission.
There were some changes happened afterwards to the common code
Which seems to affected all 4xx devices. I will try latest code
On our other SoCs.


I took care of that in my patch.  Basically it let the
system go to gen-2 speeds and negotiate down.
[marri] Great thx.

  parent reply	other threads:[~2011-06-01  3:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 18:22 [PATCH 0/1] ppc4xx: Fix PCIe scanning for the 460SX Ayman El-Khashab
2011-04-08 18:22 ` [PATCH 1/1] " Ayman El-Khashab
2011-04-08 23:48 ` [PATCH 0/1] " Benjamin Herrenschmidt
2011-04-13  2:09   ` Tirumala Marri
2011-04-29 17:02     ` Ayman El-Khashab
2011-04-29 20:37       ` Benjamin Herrenschmidt
2011-05-01  4:28         ` Tirumala Marri
2011-05-04  5:32         ` Benjamin Herrenschmidt
2011-05-05 16:44           ` Tirumala Marri
2011-05-09 16:09             ` Ayman El-Khashab
2011-05-12 18:16               ` Tirumala Marri
2011-05-24  3:40                 ` Benjamin Herrenschmidt
2011-05-27 16:51                   ` Ayman El-Khashab
2011-05-27 22:57                     ` Benjamin Herrenschmidt
2011-05-31 21:27                     ` Tirumala Marri [this message]
2011-06-27 10:14                       ` Ayman El-Khashab
2011-06-27 10:15                         ` Benjamin Herrenschmidt
2011-05-31 21:18                   ` Tirumala Marri

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=fa765cbed63d89c50a79b34f25dc9f5c@mail.gmail.com \
    --to=tmarri@apm$(echo .)com \
    --cc=ayman@elkhashab$(echo .)com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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