All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARMv7 Execution Flow
Date: Mon, 6 Jun 2016 17:58:12 -0600	[thread overview]
Message-ID: <CAPnjgZ3GRY1jU8Jkg5MXxpnZvVWNr0P65DzRs6_dsU72K0GuaQ@mail.gmail.com> (raw)
In-Reply-To: <57557CE8.2040501@gmail.com>

Hi James,

On 6 June 2016 at 07:38, James Chargin <jimccrown@gmail.com> wrote:
> Hi James,
>
> On 06/05/2016 08:48 PM, Lokesh Vutla wrote:
>>
>> Hi James,
>>
>> On Saturday 04 June 2016 12:25 AM, James Pollard wrote:
>>>
>>> Hi,
>>>
>>> I'm a new U-Boot user. I'm trying to follow the flow of execution for the
>>> ARMv7 architecture, and have found myself running into confusion.
>>>
>>> ...
>
>
> I've found, in my similar explorations for other architectures, that the
> link map can provide clues to where a particular function is linked from.
>
> In this case, based on the reply from Lokesh, I'd imagine the link map would
> show no definition. Also, perhaps there is an objdump option to display this
> info.
>
> I've noticed however, since the change to Kbuild, the names of all files
> contributing to the final link are "build-in.o" which decreases the
> usefulness of the link map for this purpose.

You can also take a look at the README under 'Board Initialisation
Flow:'. Unfortunately not all boards use this new flow, but it should
at least provide you with the intent. This is indeed an area that
takes some time to understand.

Regards,
Simon

      reply	other threads:[~2016-06-06 23:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 18:55 [U-Boot] ARMv7 Execution Flow James Pollard
2016-06-06  3:48 ` Lokesh Vutla
2016-06-06 13:38   ` James Chargin
2016-06-06 23:58     ` Simon Glass [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=CAPnjgZ3GRY1jU8Jkg5MXxpnZvVWNr0P65DzRs6_dsU72K0GuaQ@mail.gmail.com \
    --to=sjg@chromium.org \
    --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.