From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Kaila Thornton <Kaila.Thornton@seakr.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Fabien Chouteau <chouteau@adacore.com>
Subject: Re: [Qemu-devel] SPARC Leon3 Devices - Registers?
Date: Thu, 11 Jul 2013 14:23:03 +0200 [thread overview]
Message-ID: <CACXAS8BA9TACvVBxTcWJHWs-9zdyME0qtabSdgtYkYKh7ck9zQ@mail.gmail.com> (raw)
Hi Kaila,
On Mon, Jun 24, 2013 at 8:46 PM, Kaila Thornton
<Kaila.Thornton@seakr.com> wrote:
> I'm currently working on trying to add more devices to the SPARC Leon3
> machine, but I'm running into a few problems.
>
> At the moment, I'm running QEMU on an i386 machine and targeting the generic
> leon3 board. I need to write some code that allows QEMU to gain access to
> the SPARC registers as my bootloader is loading, and change the values of
> them.
Can you explain a bit more? If you'd like to change the CPU register
values manually, it can be done via gdb.
Other hardware registers can be altered in gdb too if the
corresponding page is mapped.
Or do you mean, you have a board where some device can modify CPU
registers directly and you'd like to emulate this board?
Artyom
P.S. qemu-devel@ has sometimes really lots of messages daily. It makes
sense to add a maintainer of related subsystem to CC, so your question
doesn't get lost. The official Leon3 and Grlib maintainer is Fabien
Chouteau <chouteau@adacore.com>.
The whole list of maintainers is available in the MAINTAINERS file.
--
Regards,
Artyom Tarasenko
linux/sparc and solaris/sparc under qemu blog:
http://tyom.blogspot.com/search/label/qemu
next reply other threads:[~2013-07-11 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 12:23 Artyom Tarasenko [this message]
2013-07-12 10:12 ` [Qemu-devel] SPARC Leon3 Devices - Registers? Fabien Chouteau
-- strict thread matches above, loose matches on Subject: below --
2013-06-24 18:46 Kaila Thornton
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=CACXAS8BA9TACvVBxTcWJHWs-9zdyME0qtabSdgtYkYKh7ck9zQ@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=Kaila.Thornton@seakr.com \
--cc=chouteau@adacore.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).