From: Daniel Silverstone <dsilvers@simtec.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ARM920T CPU ID
Date: Mon, 13 Oct 2008 15:02:48 +0100 [thread overview]
Message-ID: <1223906568.30000.36.camel@petitemort> (raw)
In-Reply-To: <200810131352.12102.paul@codesourcery.com>
On Mon, 2008-10-13 at 13:52 +0100, Paul Brook wrote:
> > Attached is a patch which supplies the ARM920T CPU ID for ARM emulation.
> > This is another step along the way to supporting Simtec Electronics'
> > development boards, and other Samsung ARM9 SoC based systems such as the
> > Openmoko GTA02.
> This at least needs a comment saying that what we implement doesn't look
> anything like a real ARM920, but most software doesn't care.
Where would such a comment best reside? I'm not sure where the
documentation for this kind of thing is meant to go.
(I agree that it's worthwhile to note this information though)
Regards,
D.
--
Daniel Silverstone http://www.simtec.co.uk/
PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895
prev parent reply other threads:[~2008-10-13 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 10:32 [Qemu-devel] [PATCH] ARM920T CPU ID Daniel Silverstone
2008-10-13 12:52 ` Paul Brook
2008-10-13 14:02 ` Daniel Silverstone [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=1223906568.30000.36.camel@petitemort \
--to=dsilvers@simtec.co.uk \
--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.