linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: avorontsov@ru.mvista.com
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH v2 4/4] powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E
Date: Tue, 6 Jan 2009 23:33:35 +0100	[thread overview]
Message-ID: <c384c5ea0901061433y446f4ab4i2e18d1141734d60e@mail.gmail.com> (raw)
In-Reply-To: <20090106211513.GA23914@oksana.dev.rtsoft.ru>

Hello Anton,

On Tue, Jan 6, 2009 at 10:15 PM, Anton Vorontsov
<avorontsov@ru.mvista.com> wrote:
> On Tue, Jan 06, 2009 at 02:38:57PM -0600, Kumar Gala wrote:
>>>> Is u-boot PCIe initialization required for this kernel patch to work?
>>>
>>> Yup.
>>
>> Really?  what for?
>
> Hm. U-Boot should initialize SerDes and PCI-E controller (pcie laws,
> inbound/outbound windows, clocks, etc.)
>
> Though if PCI-E controller wasn't initialized (i.e. board reflashed
> with the community u-boot), Linux just won't probe the pcie controller:
>
> cfg_bar = in_le32(hose->cfg_data + PEX_OUTWIN0_BAR);
> if (!cfg_bar) {
>        /* PCI-E isn't configured. */
>        ret = -ENODEV;
>        goto err1;
> }
>
> Or did I misunderstand the question?
>
You understood correctly, thanks for answering.

So to summarize, we need u-boot to initialize the PCIe controller, in
order for Linux to further take it over.

What u-boot versions/releases do provide this initialization?

I know the u-boot with the board works, but it's incompatible with
recent Linux kernels.

Regards,
-- 
Leon

  reply	other threads:[~2009-01-06 22:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 16:40 [PATCH 4/4] powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E Anton Vorontsov
2008-12-30 17:46 ` Kumar Gala
2008-12-30 20:19   ` [PATCH v2 " Anton Vorontsov
2008-12-31 16:48     ` Kumar Gala
2008-12-31 17:10       ` Wolfgang Denk
2009-01-01 14:26         ` Kumar Gala
2009-01-05 17:46           ` Scott Wood
2009-01-05 18:01             ` Anton Vorontsov
2009-01-06 12:18               ` Leon Woestenberg
2009-01-07 15:43                 ` Scott Wood
2009-01-06 18:53               ` Leon Woestenberg
2009-01-06 19:27                 ` Anton Vorontsov
2009-01-06 20:38                   ` Kumar Gala
2009-01-06 21:15                     ` Anton Vorontsov
2009-01-06 22:33                       ` Leon Woestenberg [this message]
2009-01-06 23:42                         ` Anton Vorontsov
2009-01-07  0:40                           ` Leon Woestenberg
2008-12-31 17:41       ` Anton Vorontsov
2009-01-01 14:29         ` Kumar Gala
2009-01-05 16:37           ` Anton Vorontsov

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=c384c5ea0901061433y446f4ab4i2e18d1141734d60e@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=wd@denx.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).