qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Missing ARMv6 instructions?
Date: Wed, 29 Mar 2006 21:39:12 +0100	[thread overview]
Message-ID: <20060329203912.GA14514@mail.shareable.org> (raw)
In-Reply-To: <OF77E92E27.62D3CA02-ONC1257140.0057B2AD-C1257140.0057E53B@codingtechnologies.com>

Paul Brook <paul@codesourcery.com> wrote:
>> qemu cvs only supports ARMv5TE.
>> 
>> The ARMv6 architecture is released under a more restrictive
>> licence than ARMv5.  The Arm licencing department have explicitly
>> prohibited the distribution of open source ARMv6/v7 emulators.
>>
>> > We're trying to get this restriction lifted, but so far to no avail.

Wolfgang Schildbach wrote:
> Thanks, Paul. That explains it...
> I find it strange that ARM would restrict emulation of their architecture 
> -- that could hardly pose a threat to their business, I would say.

I find it strange that they can restrict emulation, if they can.

Perhaps they can't, and maybe they like to send threatening letters to
frighten people away from doing it?

That's not so surprising for ARM.  They halted the development of an
open source ARM-compatible FPGA design too.

What claim does ARM have over software that they don't write and whose
only resemblance is that it speaks the same protocol?

It looks, and smells, like an attempt at "interface copyright".
I.e. to copyright something just for offering a similar interface.

E.g. much the same as Microsoft attempting to stop people implementing
a "task bar".  Yet, Microsoft can't do that, and nobody is afraid of
writing window managers with task bars.

I could understand a claim if someone acquired ARM's documentation
under an agreement to not produce an emulator.  But I don't see how
someone who has no connection with ARM can be restricted by ARM in
that way.

Has ARM ever actually followed through on their threats and _won_ a
case to ban compatible software from being distributed?

And if there is a possibility of that - in which countries do they
have any weight?  Dare I suggest encouraging the development of
patches they don't like to countries where they have no legal weight?

-- Jamie

  reply	other threads:[~2006-03-29 21:14 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 [this message]
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
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=20060329203912.GA14514@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=paul@codesourcery.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).