All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chetan Nanda <chetannanda@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Mips: start.S Questions
Date: Fri, 21 Aug 2009 18:35:24 +0530	[thread overview]
Message-ID: <7f245da80908210605q2b78dc9dtf39559feaa9af224@mail.gmail.com> (raw)
In-Reply-To: <574bb010908210553v7dd8570cnfa6d85978b531e10@mail.gmail.com>

On Fri, Aug 21, 2009 at 6:23 PM, Peter Belm <peterbelm@gmail.com> wrote:

> >
> > This is not quite correct.  "romReserved" is only used for the, well,
> > reserved entries.  There are other parameters passed, these two are
> > pretty important for example:
>
>
> The thing I don't get is if you expand the RVECENT macro into the code
> wouldn't you get this:
>
> _start:
>    b reset; nop    /* U-boot entry point */


On power on, first instruction that will get executed is  'b reset, nop'. So
code will Jump to reset label
from where actual booting sequence start.


>
>    b reset; nop    /* software reboot */
>
>    b romReserved
>    b romReserved
>
> ....
>
> romReserved:
>    b romReserved
>
> So wouldn't it get stuck in an infinite loop straight away, calling
> romReserved recursively? I'm obviously overlooking something I think.


So romReserved will not get called in normal booting-sequence as code will
jump to 'reset' label.
 In case of some exception 'romReserved' will be called and then board will
struck in while loop.


Thanks,
Chetan  Nanda

>
>
> And what's the point of passing the second parameter (0-127) to RVECENT
> when
> it's not used?
>
> --
> Regards,
> Peter Belm
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>

      parent reply	other threads:[~2009-08-21 13:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 11:34 [U-Boot] Mips: start.S Questions Peter Belm
2009-08-21 12:40 ` Detlev Zundel
2009-08-21 12:53   ` Peter Belm
2009-08-21 13:02     ` Detlev Zundel
2009-08-21 13:08       ` Peter Belm
2009-08-21 13:42         ` Detlev Zundel
2009-08-21 13:46           ` Peter Belm
2009-08-21 13:05     ` Chetan Nanda [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=7f245da80908210605q2b78dc9dtf39559feaa9af224@mail.gmail.com \
    --to=chetannanda@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 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.