From: Robert Reif <reif@earthlink.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] fix sparc32 mxcc 64 bit read word order
Date: Sun, 18 Nov 2007 16:58:38 -0500 [thread overview]
Message-ID: <4740B58E.9040004@earthlink.net> (raw)
In-Reply-To: <f43fc5580711181310m61c4c9efk5405e59091cec63@mail.gmail.com>
Blue Swirl wrote:
>On 11/18/07, Robert Reif <reif@earthlink.net> wrote:
>
>
>>Blue Swirl wrote:
>>
>>
>>
>>>On 11/16/07, Robert Reif <reif@earthlink.net> wrote:
>>>
>>>
>>>
>>>
>>>>>This patch fixes the word order for 64 bit reads of the mxcc registers.
>>>>>
>>>>>
>>>>>
>>>>>
>>>Otherwise everything seems OK, but it breaks NetBSD version 3 on SS10:
>>>clock0 at obio0 slot 0 offset 0x200000: mk48t08
>>>timer0 at obio0 slot 0 offset 0x300000data fault: pc=0xf0111a0c
>>>addr=0x0 sfsr=126<PERR=0,LVL=1,AT=1,FT=1,FAV,OW>
>>>panic: kernel fault
>>>halted
>>>
>>>halt, power off
>>>
>>>Without the patch I get:
>>>clock0 at obio0 slot 0 offset 0x200000: mk48t08
>>>timer0 at obio0 slot 0 offset 0x300000: delay constant 99
>>>zs0 at obio0 slot 0 offset 0x100000 level 12 softpri 6
>>>zstty0 at zs0 channel 0 (console i/o)
>>>zstty1 at zs0 channel 1
>>>scsi-disk: Unsupported command length, command 79
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>This is a classic case of two wrongs make a right. OpenBios need to be
>>fixed to set mbus module id to start at 8, not 0 for mbus based machines.
>>
>>
>
>Turbosparc manual says that the module id is hardwired to 0x8, so
>would it be OK if mid was i + 8 for all machines?
>
>
>
>
>
Probably but I don't know for sure. I just fired up a SPARCclassic X
which has a microSPARC CPU and the mid was 0. You may need to check the
CPU type for the SS5. I don't have the time right now to dig out a
microSPARC SS5 to check it out.
next prev parent reply other threads:[~2007-11-18 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 12:48 [Qemu-devel] [RFC][PATCH] fix sparc32 mxcc 64 bit read word order Robert Reif
2007-11-15 18:10 ` Blue Swirl
2007-11-15 23:08 ` Robert Reif
2007-11-17 9:21 ` Blue Swirl
2007-11-18 20:57 ` Robert Reif
2007-11-18 21:10 ` Blue Swirl
2007-11-18 21:58 ` Robert Reif [this message]
2007-11-19 19:16 ` Blue Swirl
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=4740B58E.9040004@earthlink.net \
--to=reif@earthlink.net \
--cc=qemu-devel@nongnu.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 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.