From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: SH4: Implement FD bit
Date: Thu, 11 Dec 2008 23:21:14 +0100 [thread overview]
Message-ID: <761ea48b0812111421i4f42af18mcb4672e75f54ae4c@mail.gmail.com> (raw)
In-Reply-To: <1229032933.3898.30.camel@cocoduo.atr>
On Thu, Dec 11, 2008 at 11:02 PM, Lionel Landwerlin
<lionel.landwerlin@openwide.fr> wrote:
>
> According to you, where should I put this "fix" in linux-user/ ?
If you look in target-sh4/translate.c/cpu_sh4_reset you will
find what you need. For linux-user, CONFIG_USER_ONLY
is defined.
HTH,
Laurent
prev parent reply other threads:[~2008-12-11 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 17:22 [Qemu-devel] SH4: Implement FD bit Vladimir Prus
2008-12-07 22:47 ` Aurelien Jarno
2008-12-09 16:36 ` [Qemu-devel] " Vladimir Prus
2008-12-10 9:15 ` Aurelien Jarno
2008-12-10 11:04 ` [Qemu-devel] " Vladimir Prus
2008-12-10 17:31 ` Aurelien Jarno
2008-12-11 20:12 ` [Qemu-devel] " Lionel Landwerlin
2008-12-11 20:57 ` Laurent Desnogues
2008-12-11 22:02 ` Lionel Landwerlin
2008-12-11 22:21 ` Laurent Desnogues [this message]
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=761ea48b0812111421i4f42af18mcb4672e75f54ae4c@mail.gmail.com \
--to=laurent.desnogues@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).