From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fo0ju-0008FW-6z for qemu-devel@nongnu.org; Wed, 07 Jun 2006 12:18:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fo0jq-0008Db-8I for qemu-devel@nongnu.org; Wed, 07 Jun 2006 12:18:37 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fo0jq-0008DU-1S for qemu-devel@nongnu.org; Wed, 07 Jun 2006 12:18:34 -0400 Received: from [81.29.64.88] (helo=mail.shareable.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fo0rS-0003Dp-PP for qemu-devel@nongnu.org; Wed, 07 Jun 2006 12:26:27 -0400 Date: Wed, 7 Jun 2006 17:18:23 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] I want to add the ARMv6 instructions, who can give some advices? Message-ID: <20060607161823.GA31417@mail.shareable.org> References: <39134b110606070011y1ea95f6bh5e64468bc5b53c04@mail.gmail.com> <200606071607.19593.paul@codesourcery.com> <20060607154853.GA29923@mail.shareable.org> <200606071658.27892.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606071658.27892.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org Paul Brook wrote: > > Qemu is already compatible "in part" with the the instructions and > > models described in the manual, isn't it? > > > > So by the language of clause 2(i), aren't you _already_ prohibited from > > working on Qemu's ARM code? > > All the information used to implement the current qemu Arm support is > available from other sources not covered by this licence. I'm confident I > could prove this if necessary. Of course, I'm sure you're right. In the thread you cited earlier, Wolfgang Schildbach refers to "ARM System Developer's Guide", by Sloss, Symes, and Wright, Elsevier 2004 as documentation that may be sufficient for Qemu ARMv6 support, and which is not covered by the license. If ARMv6 support were developed by someone else, using only that book, and maybe looking at other code (GCC, Linux etc.), that would prove that all the information used is from other sources not covered by the license, wouldn't it? The support might be missing a few features, if the other information sources are incomplete, but even incomplete support that can be deduced from those sources would be good enough for most purposes. If that were done, you could prove that the resulting feature in Qemu was written using sources not covered by the license. So would you have any problem contributing to Qemu after ARMv6 support was integrated, if the person who contributes ARMv6 support states that they have never seen the ARM document and refers to the sources they have used instead? -- Jamie