linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org, Wolfram Sang <wsa@pengutronix.de>
Subject: Re: [PATCH] powerpc/mpc52xx: add Phytec phyCORE-MPC5200B-IO board (pcm032)
Date: Fri, 6 Mar 2009 21:01:25 -0500	[thread overview]
Message-ID: <9e4733910903061801w3a9661acm3e8855abb743d3e0@mail.gmail.com> (raw)
In-Reply-To: <20090303081212.GL5367@pengutronix.de>

On Tue, Mar 3, 2009 at 3:12 AM, Robert Schwebel
<r.schwebel@pengutronix.de> wrote:
> On Sun, Mar 01, 2009 at 09:33:16PM -0700, Grant Likely wrote:
>> On Sun, Mar 1, 2009 at 7:19 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
>> > Would it be easier to get Pengutronix to release a new u-boot for
>> > the pcm030? I'm using U-Boot 1.2.0-mpc5200b-tiny-2 (Apr 17 2007 -
>> > 11:49:20).
>>
>> Only if it is a chip IO setup problem (like port_config or clock
>> setup). Otherwise the kernel should be setting up the PCI controller
>> correctly. Regardless, I don't think the kernel should be crashing
>> when PCI is in a funny state.
>
> Ack; I didn't follow the thread in detail, but if possible I'd like to
> avoid bootloader updates; it's quite a lot of effort because there are
> thousends of devices in the field, not to mention the whole
> qualification mechanics at Phytec.

On a pcm030 1245-1
u-boot-1.2.0-mpc5200b-tiny-3,  boots ok and PCI is initialized correctly.

The readme is not clear that tiny-3 should be used on 1245.1 hardware.
http://www.pengutronix.de/oselas/bsp/phytec/download/phyCORE-MPC5200B-tiny/=
Readme

This phrase implies the tiny-3 should only be used on 1245.2 hardware.
"U-Boot binary to be used with
OSELAS.BSP-Phytec-phyCORE-MPC5200B-tiny-6 (board revision 1245.2)"

Where is the difference between the 1245.0, 1245.1 and 1245.2 hardware
documented?



>
> Wolfram can check the issue when being back in the office.
>
> rsc
> --
> Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |
> Industrial Linux Solutions =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | http://www.p=
engutronix.de/ =A0|
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 =A0=
 =A0|
> Amtsgericht Hildesheim, HRA 2686 =A0 =A0 =A0 =A0 =A0 | Fax: =A0 +49-5121-=
206917-5555 |
>



--=20
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2009-03-07  2:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 15:32 [PATCH] powerpc/mpc52xx: add Phytec phyCORE-MPC5200B-IO board (pcm032) Wolfram Sang
2009-02-25 15:40 ` Wolfram Sang
2009-02-27  5:31 ` Grant Likely
2009-03-01 10:18   ` Wolfram Sang
2009-03-01 14:48     ` Grant Likely
2009-03-01 15:54       ` Jon Smirl
2009-03-01 22:47         ` Grant Likely
2009-03-02  0:37           ` Jon Smirl
2009-03-02  0:46             ` Jon Smirl
2009-03-02  1:07               ` Grant Likely
2009-03-02  2:15                 ` Jon Smirl
2009-03-02  2:19                   ` Jon Smirl
2009-03-02  4:33                     ` Grant Likely
2009-03-03  8:12                       ` Robert Schwebel
2009-03-07  2:01                         ` Jon Smirl [this message]
2009-03-10 16:03       ` [PATCH v2] " Wolfram Sang

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=9e4733910903061801w3a9661acm3e8855abb743d3e0@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=r.schwebel@pengutronix.de \
    --cc=wsa@pengutronix.de \
    /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).