All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schweigstill <andreas@schweigstill.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] clarifications u-boot for arm
Date: Tue, 18 Jul 2006 12:54:17 +0200	[thread overview]
Message-ID: <44BCBDD9.8040900@schweigstill.de> (raw)
In-Reply-To: <8bf247760607140651l4e0bc8fdh55e1e0b731209597@mail.gmail.com>

Dear Ram!

Ram schrieb:
>     Does this really invoke start_armboot?.  This is because
> _start_armboot is what is
>     stored in pc and not start_armboot and there is also a branch
> point _start_armboot (underscore start_armboot) Please see above.

And why don't you learn the syntax and semantics of ARM assembler
before you send messages to this list?

>   I didnt understand the things relating interrupt and thier processing though.

In order to understand the interrupt related things I recommend reading
some documents about ARM architecture, your processor datasheet(s) AND
U-BOOT DOCUMENTATION. Then you will find out by yourself why it is so
difficult to understand interrupt handling on most platforms... :-) And
why don't you just hook your JTAG debugger on the interrupt entry point
and try to follow the execution flow? Then you will also notice
something very important in U-Boot...

Andreas Schweigstill

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstra?e 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

      parent reply	other threads:[~2006-07-18 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14  7:29 [U-Boot-Users] clarifications u-boot for arm Ram
2006-07-14  8:16 ` Wolfgang Denk
2006-07-14 13:51   ` Ram
2006-07-14 14:11     ` Russell Peterson
2006-07-14 14:23       ` Jerry Van Baren
2006-07-18 10:54     ` Andreas Schweigstill [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=44BCBDD9.8040900@schweigstill.de \
    --to=andreas@schweigstill.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.