qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] target-ppc: fix interrupt vectors for MPC603 and e300
Date: Mon, 26 Apr 2010 20:11:03 +0300	[thread overview]
Message-ID: <p2pf43fc5581004261011g21c523a6t12921ca4094aa412@mail.gmail.com> (raw)
In-Reply-To: <7193FDBE-AE3E-4597-A8DD-A20F577230A6@kernel.crashing.org>

On 4/26/10, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> >
> > > It is explained in [e300CORERM] at chapters 5.2.3, 5.5.1.1 and 8.3.3.
> > > Clearly, the vector offset is 0x100 and the exception prefix can be 0 or
> > > 0xFFF00000, depending of the MSR[IP] bit.
> > >
> > > So, yes, I'm sure the value of hreset_vector must be 0x100.
> > > But hreset_excp_prefix can change. It could be another patch.
> > >
> >
> > Interesting. That's different from 970.
> >
>
>  On 970, you can have the same effect (well, more general) by
>  changing HIOR.
>
>
> >
> > > About the prefix initialization, the datasheet says it is "determined by
> > > MSR[IP]". and is "determined by the state of the msrip signal". But I
> don't
> > > understand what is the msrip signal and how MSR[IP] is changed (is it
> related
> > > to msrip ?). Do you have an explanation for this part ?
> > >
> >
>
>  Your code can change MSR[IP]; there is also a strapping pin that is
>  sampled on HRESET (and copied to MSR[IP]).

Wouldn't this mean that when the reset is issued by hardware, MSR[IP]
is always 1 (to boot from ROM) but with software reset it can take
software defined values?

I think now QEMU ignores MSR[IP].

  reply	other threads:[~2010-04-26 17:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  9:21 [Qemu-devel] [PATCH 0/2] some fixes for PPC e300 Thomas Monjalon
2010-04-21  9:21 ` [Qemu-devel] [PATCH 1/2] target-ppc: fix processor versions (PVR) for e300 Thomas Monjalon
2010-04-21  9:21 ` [Qemu-devel] [PATCH 2/2] target-ppc: fix interrupt vectors for MPC603 and e300 Thomas Monjalon
2010-04-21 10:14   ` Alexander Graf
2010-04-21 12:07     ` Thomas Monjalon
2010-04-21 12:36       ` Alexander Graf
2010-04-21 13:13         ` Thomas Monjalon
2010-04-22 19:40         ` Hollis Blanchard
2010-04-26 15:35           ` Segher Boessenkool
2010-04-26 15:02         ` Segher Boessenkool
2010-04-26 17:11           ` Blue Swirl [this message]
2010-05-02 14:19             ` Segher Boessenkool
2010-05-02 15:03               ` [Qemu-devel] VGA blank mode K D

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=p2pf43fc5581004261011g21c523a6t12921ca4094aa412@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=segher@kernel.crashing.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).