From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FOjH6-0002GF-0d
	for qemu-devel@nongnu.org; Wed, 29 Mar 2006 17:36:24 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FOjH3-0002G0-Ky
	for qemu-devel@nongnu.org; Wed, 29 Mar 2006 17:36:22 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FOjH3-0002Fx-EI
	for qemu-devel@nongnu.org; Wed, 29 Mar 2006 17:36:21 -0500
Received: from [64.233.182.189] (helo=nproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FOjJ5-0001Z8-S3
	for qemu-devel@nongnu.org; Wed, 29 Mar 2006 17:38:28 -0500
Received: by nproxy.gmail.com with SMTP id g2so238659nfe
	for <qemu-devel@nongnu.org>; Wed, 29 Mar 2006 14:36:19 -0800 (PST)
Message-ID: <dd8f98f40603291436g69185369h63618afdaa979b61@mail.gmail.com>
Date: Wed, 29 Mar 2006 14:36:19 -0800
From: "John Hogerhuis" <jhoger@gmail.com>
Subject: Re: [Qemu-devel] Missing ARMv6 instructions?
In-Reply-To: <200603292301.41791.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_8987_9354900.1143671779627"
References: <200603291539.12628.paul@codesourcery.com>
	<OF77E92E27.62D3CA02-ONC1257140.0057B2AD-C1257140.0057E53B@codingtechnologies.com>
	<20060329203912.GA14514@mail.shareable.org>
	<200603292301.41791.paul@codesourcery.com>
Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

------=_Part_8987_9354900.1143671779627
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

So it's a purely contractual issue as opposed to an IP issue.

Is a party to this contract allowed to write a disassembler? I can imagine =
a
very nice disassembler feature that would explain in detail how each
instruction it decodes works...

Of course no matter how such documentation were to escape, you're still use=
d
up by your contractual obligations as far as implementing an emulator, I
guess.

-- John.

------=_Part_8987_9354900.1143671779627
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

So it's a purely contractual issue as opposed to an IP issue.<br><br>Is a p=
arty to this contract allowed to write a disassembler? I can imagine a very=
 nice disassembler feature that would explain in detail how each instructio=
n it decodes works...
<br><br>Of course no matter how such documentation were to escape, you're s=
till used up by your contractual obligations as far as implementing an emul=
ator, I guess.<br><br>-- John.<br><br>

------=_Part_8987_9354900.1143671779627--