linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Steve Heflin <sheflin@newagemicro.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ppc platform for AMCC-440EPx - ELDK to the rescue
Date: Wed, 26 Mar 2008 11:26:18 -0500	[thread overview]
Message-ID: <47EA792A.5000109@freescale.com> (raw)
In-Reply-To: <20080326130837.762DBDE2FB@ozlabs.org>

Steve Heflin wrote:
> After that, I was able to see that it was the "setup_hose" function 
> called from /arch/ppc/platforms/4xx/sequoia.c that caused my board to 
> hang. This Sequoia spinoff board has the PCI Host Bridge disabled which 
> I didn't realize until that point.
> 
> Looking back at the powerpc platform, I don't see how to disable the 
> Host Bridge initialization without disabling the entire PCI bus.  This 
> board does have 2 devices hooked on the PCI bus, just no need for a Host 
> Bridge.

And how do you propose to talk to said PCI devices without configuring 
the host bridge?

> Also, I fail to see what the DTS virtualization layer of the hardware 
> buys us.

Maintainability.  Ease of porting to new hardware.

> When debugging, it's so much harder to use than the ppc 
> platform's straight forward and standard methodologies.  I can't 
> understand to goal to eliminate the ppc platform,

Are you volunteering to maintain it, including the rest of us not having 
to care when we change something in common code that breaks it?

> especially given the 
> fact that DENX's ELDK is still using it with Linux 2.6.24.2 !!

Take that up with Denx.

-Scott

  reply	other threads:[~2008-03-26 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 13:08 ppc platform for AMCC-440EPx - ELDK to the rescue Steve Heflin
2008-03-26 16:26 ` Scott Wood [this message]
2008-03-26 22:22 ` Wolfgang Denk
2008-03-26 22:56   ` Dave Cogley
2008-03-27  1:03     ` Josh Boyer
2008-03-27  1:08 ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2008-03-27 20:36 Steve Heflin

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=47EA792A.5000109@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sheflin@newagemicro.com \
    /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).