From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: OBP under qemu-system-sparc64
Date: Wed, 14 Apr 2010 21:30:04 +0200 [thread overview]
Message-ID: <g2mfb8d4f71004141230g62f58fa1m4080def7f6167d81@mail.gmail.com> (raw)
In-Reply-To: <o2tf43fc5581004141138s70651aefjca20a30f66d799cb@mail.gmail.com>
2010/4/14 Blue Swirl <blauwirbel@gmail.com>:
> On 4/14/10, Artyom Tarasenko <atar4qemu@googlemail.com> wrote:
>> 2010/4/14 Artyom Tarasenko <atar4qemu@googlemail.com>:
>>
>> > 2010/4/3 Blue Swirl <blauwirbel@gmail.com>:
>> >> could be interesting to see what OBP
>> >> from a real machine would think of the QEMU machine.
>> >
>> > it doesn't live long enough to think something (must be something trivial):
>> >
>> > $ sparc64-softmmu/qemu-system-sparc64 -bios u1_v3.11.1.bin -nographic
>> > -cpu 'TI UltraSparc I' -d in_asm,int,cpu
>> > --------------
>> > IN:
>> > 0x000001fff0000020: ldxa [ %g0 ] (69), %g2
>> > 0x000001fff0000024: stxa %g0, [ %g0 ] (69)
>> > 0x000001fff0000028: b,a 0x1fff0001d88
>> >
>> > --------------
>> > IN:
>> > 0x000001fff0001d88: rdpr %cwp, %g1
>> > 0x000001fff0001d8c: wrpr 0, %cwp
>> > 0x000001fff0001d90: wrpr %g1, 0, %cwp
>> > 0x000001fff0001d94: call 0x1fff0000210
>> > 0x000001fff0001d98: add %g0, %g0, %o0
>> >
>> > --------------
>> > IN:
>> > 0x000001fff0000210: mov 0x1ff, %o1 ! 0x1ff
>> > 0x000001fff0000214: sllx %o1, 0x20, %o1
>> > 0x000001fff0000218: sethi %hi(0xf1300000), %o2
>> > 0x000001fff000021c: or %o2, %o1, %o2
>> > 0x000001fff0000220: stba %o0, [ %o2 ] (21)
>>
>>
>> and on the real machine there seems to be some device connected to this address:
>> ok 1fff1300000 bypass-asi spacel@ .
>> Data Access Error
>> ok cpu-afsr@ .
>> 104000000
>> ok 1fff1300000 bypass-asi spacel@ .
>> Data Access Error
>> ok cpu-afar@ . cpu-afsr@ .
>> 1fff1300000 104000000
>> But, with single bytes it works:
>> ok 1fff1300000 bypass-asi spacec@ .
>> 64
>> ok 1fff1300001 bypass-asi spacec@ .
>> 64
>> ok 1fff1300002 bypass-asi spacec@ .
>> 64
>> ok 1fff1300003 bypass-asi spacec@ .
>> 64
>>
>> If I put pseudodevices there it still doesn't get too far:
>> #### skip unassigned mem access to 000001fff1300000
>> #### skip unassigned mem access to 000001fff1300004
>> #### skip unassigned mem access to 000001fff1300005
>> #### skip unassigned mem access to 000001fff1300006
>> #### skip unassigned mem access to 000001fff1300007
>
> It's this device:
> model: 'SUNW,sc-up'
> reg: 0000000f.01300000.00000008
> name: 'sc'
thought about it, but it says xx08, and OBP tries xx00+
>> #### skip unassigned mem access to 000001fff1900000
>
> address: fffb6000
> reg: 0000000f.01900000.00000001
> name: 'auxio'
>
>> #### skip unassigned mem access to 000001fff1100004
>
> device_type: 'serial'
> reg: 0000000f.01100000.00000004
> name: 'zs'
>
>> #### skip unassigned mem access to 000001fff1100004
>> #### skip unassigned mem access to 000001fff1100000
>> #### skip unassigned mem access to 000001fff1300007
>> #### skip unassigned mem access to 000001fff1200001
>
> reg: 0000000f.01200000.00002000
> model: 'mk48t59'
> name: 'eeprom'
>
> Zilog serial (escc) and m48t59 are already implemented.
Yes, but I thought they are also already wired.
I'll create one more hwdef entry then.
On the other hand I see
.console_serial_base = 0
. Do we want to keep this setting? How does it work under OpenBIOS?
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-04-14 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 15:17 [Qemu-devel] OBP under qemu-system-sparc64 Artyom Tarasenko
2010-04-14 16:15 ` [Qemu-devel] " Artyom Tarasenko
2010-04-14 18:38 ` Blue Swirl
2010-04-14 19:30 ` Artyom Tarasenko [this message]
2010-04-14 19:44 ` Blue Swirl
2010-04-14 20:33 ` Artyom Tarasenko
2010-04-21 21:53 ` Artyom Tarasenko
2010-04-28 19:56 ` Artyom Tarasenko
2010-04-28 20:10 ` 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=g2mfb8d4f71004141230g62f58fa1m4080def7f6167d81@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--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 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).