public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: James Chargin <jimccrown@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARMv7 Execution Flow
Date: Mon, 6 Jun 2016 06:38:48 -0700	[thread overview]
Message-ID: <57557CE8.2040501@gmail.com> (raw)
In-Reply-To: <5754F2A5.3020108@ti.com>

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.

Jim
-- 
Jim Chargin
AJA Video Systems                       jimc at aja.com
(530) 271-3334                          http://www.aja.com

>
> Thanks and regards,
> Lokesh
>
>>
>> Yours,
>>
>> James Pollard
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

  reply	other threads:[~2016-06-06 13:38 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 [this message]
2016-06-06 23:58     ` Simon Glass

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=57557CE8.2040501@gmail.com \
    --to=jimccrown@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox