linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: alebas@televes.com
To: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6.10-rc1 yet not running on ads8272
Date: Mon, 29 Nov 2004 14:58:19 +0100	[thread overview]
Message-ID: <1101736699.41ab2afb48566@webmail.televes.com:443> (raw)
In-Reply-To: <001d01c4d617$0f72f340$0301a8c0@chuck2>

Mark,

I have tried this before and this doesn't work.
Execution flow never arrives to "2:".

All the other values are extra info I have collected.
But problem was isolated using breakpoints to avoid
stepping influence.

Best regards,

Alex

Citando Mark Chambers <markc@mail.com>:


> RFI = Return From Interrupt.  In normal usage the current
> address is copied into SRR0 when an exception occurs so
> the processor will return to that point with an RFI.  So this
> code is 'faking out' the RFI instruction to return to 2:
>
> Are you maybe trying to trace through this code?  If so,
> and depending on your debugger, you may not be able to.
> If your debugger uses trace or some other exception to do
> single step, once you get past mtspr SRR0,r4 the single
> step exception will overwrite the correct SRR0.  You
> can see if this is the case by only tracing to mtspr SRR0,r4
> and then putting a breakpoint at 2:
>
> Good luck,
> Mark Chambers
>

  reply	other threads:[~2004-11-29 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 19:06 Kernel 2.6 hangs at m82xx_board_init alebas
2004-11-23 20:13 ` Dan Malek
2004-11-29 12:51   ` Kernel 2.6.10-rc1 yet not running on ads8272 alebas
2004-11-29 13:26     ` Mark Chambers
2004-11-29 13:58       ` alebas [this message]
     [not found]       ` <1101736520.41ab2a48a710a@webmail.televes.com:443>
     [not found]         ` <006b01c4d61e$707f2440$0301a8c0@chuck2>
2004-11-30 13:08           ` alebas

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='1101736699.41ab2afb48566@webmail.televes.com:443' \
    --to=alebas@televes.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).