From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Missing ARMv6 instructions?
Date: Thu, 30 Mar 2006 15:30:30 +0100 [thread overview]
Message-ID: <20060330143030.GA23929@mail.shareable.org> (raw)
In-Reply-To: <OFBD8B29C1.CC233146-ONC1257141.002F7C31-C1257141.00338228@codingtechnologies.com>
Wolfgang Schildbach wrote:
> The way I understand this is that anyone who got ARM documentation with
> the license that Paul mentioned, could not contribute patches that
> implement v6 emulation. If, however, someone else (who has not signed such
> a license) were to buy documentation about the ARMv6 architecture that
> comes without a license (for example, the "ARM System Developer's Guide",
> by Sloss, Symes, and Wright, Elsevier 2004), that someone should be able
> to contribute (at least in those aspects of the ARM that are disclosed by
> the book). In that case, ARM should not have any legal hooks except
> copyright, and since at that point you are not using any of their code,
> there is no case. However, I am not a lawyer, so don't take my word for
> it.
I wonder about patents (and their validity).
A MIPS hardware implementation that I worked with had all the basic
MIPS integer instructions except one small group, on the ground that
those instructions were covered by a MIPS patent and so they dared not
include it. It was the instruction used for unaligned memory word
access. For that reason, we used a modified GCC specially for that
chip.
> I also find it hard to believe that building a product competitive
> to an ARM is possible using a description of the instruction set alone.
(I meant a description of the architectural behaviour... not just the
instruction set. Compilers are moving beyond merely implementing
"user space" code, to optimising paths between security levels,
analysing memory orderings between threads, etc. And for that matter,
so are decompilers.)
It's not possible.. yet. Believe me, there are people working on it.
And it doesn't have to be competitive for ARM to have a reaction... as
we're seeing with software emulatation.
> That said, I agree with Paul that lobbying ARM to change their license is
> probably a better route to go. I believe software emulators like qemu are
> really in ARMs best interest since they support ARM development and
> thereby increase the availability of software for ARM cores.
That makes sense to me.
-- Jamie
next prev parent reply other threads:[~2006-03-30 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 12:33 [Qemu-devel] Missing ARMv6 instructions? Wolfgang Schildbach
2006-03-29 14:39 ` Paul Brook
2006-03-29 16:00 ` Wolfgang Schildbach
2006-03-29 20:39 ` Jamie Lokier
2006-03-29 22:01 ` Paul Brook
2006-03-29 22:36 ` John Hogerhuis
2006-03-29 22:37 ` Jamie Lokier
2006-03-30 9:22 ` Wolfgang Schildbach
2006-03-30 14:30 ` Jamie Lokier [this message]
2006-03-30 15:25 ` Lennert Buytenhek
2006-03-30 15:50 ` Paul Brook
2006-03-29 20:40 ` Jamie Lokier
2006-04-01 19:51 ` Chris Wilson
2006-04-01 20:06 ` Jonas Maebe
2006-04-02 1:26 ` Kevin F. Quinn
2006-04-02 16:32 ` Jamie Lokier
2006-04-02 16:42 ` Chris Wilson
2006-04-04 19:42 ` Daniel Jacobowitz
2006-04-05 14:41 ` Thiemo Seufer
2006-04-03 6:42 ` Karel Gardas
2006-04-03 7:00 ` M. Warner Losh
2006-04-03 12:42 ` Paul Brook
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=20060330143030.GA23929@mail.shareable.org \
--to=jamie@shareable.org \
--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).