All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] calling pci_init before relocation?
Date: Mon, 31 Jan 2011 12:11:15 +0100	[thread overview]
Message-ID: <4D4698D3.8060401@discworld.dascon.de> (raw)
In-Reply-To: <20110131104254.103BCD42A99@gemini.denx.de>

Wolfgang Denk wrote:
> Dear Michael Schwingen,
>
> In message <4D45EA43.3070108@discworld.dascon.de> you wrote:
>   
>> The system hangs during early init, and does not get past relocation.
>>     
>
> That is to be expected when you use this before relocation. Don't do
> that, then.
>
>   
>> If I interpret the code correct, the PCI code is called from
>> board_init_r on PowerPC platforms.
>>     
>
> So what? board_init_r() is (quoting the comment) "the  next  part  if
> the  initialization  sequence: we are now running from RAM and have a
> "normal" C environment, i. e. global data can  be  written,  BSS  has
> been cleared, the stack size in not that critical any more, etc."
>
> So it's perfectly safe and clean to run pci_init() there.
>   
I know - I only wanted to point at the differences: the problem is that 
the ARM code does it before relocation currently, and I was trying to 
understand why.

cu
Michael

      reply	other threads:[~2011-01-31 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 21:39 [U-Boot] calling pci_init before relocation? Michael Schwingen
2011-01-30 22:07 ` Albert ARIBAUD
2011-01-30 22:46   ` Michael Schwingen
2011-01-30 23:01     ` Albert ARIBAUD
2011-01-31  8:45       ` Heiko Schocher
2011-01-31 10:46         ` Wolfgang Denk
2011-02-01  7:35         ` Michael Schwingen
2011-02-01  8:04           ` Heiko Schocher
2011-01-31  9:45       ` Michael Schwingen
2011-01-31 10:42     ` Wolfgang Denk
2011-01-31 11:11       ` Michael Schwingen [this message]

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=4D4698D3.8060401@discworld.dascon.de \
    --to=rincewind@discworld.dascon.de \
    --cc=u-boot@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.