From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fo2tK-0001jr-HA for qemu-devel@nongnu.org; Wed, 07 Jun 2006 14:36:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fo2tG-0001jf-4A for qemu-devel@nongnu.org; Wed, 07 Jun 2006 14:36:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fo2tF-0001jc-TJ for qemu-devel@nongnu.org; Wed, 07 Jun 2006 14:36:25 -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 1Fo30t-0007i0-Oo for qemu-devel@nongnu.org; Wed, 07 Jun 2006 14:44:20 -0400 Date: Wed, 7 Jun 2006 19:36:09 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] I want to add the ARMv6 instructions, who can give some advices? Message-ID: <20060607183609.GA8524@mail.shareable.org> References: <39134b110606070011y1ea95f6bh5e64468bc5b53c04@mail.gmail.com> <200606071734.06090.paul@codesourcery.com> <20060607172152.GA3513@mail.shareable.org> <200606071825.11037.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606071825.11037.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: > > > Basing work on the gcc/binutils code doesn't help me either because I > > > wrote most of that code in the first place :-) > > > > Since the idea is for someone else do it, that doesn't matter. > > > > I'm wondering why, if it were done, it would be a problem for you to > > contribute in future in the areas which you contribute to now. > > Because a large proportion of my contributions, and most of my > interest is in this area. Sorry, I guess my question wasn't clear. I'm not asking why it would be a problem for you to stop contributing to ARM support in Qemu. That's not the meaning of my question above. Of course it would be a problem for all of us if you had to stop. I am asking why you think you'd have to stop contributing to the pre-ARMv6 feature set, given that it's unrelated to the restrictions that you're bound by. If it's post-ARMv6 contributions that you're interested in, you can't contribute them now or in future; so someone else contributing changes in that area makes no difference to you. Or does it? That's my question; I don't see why post-ARMv6 functionality in Qemu would prevent you from contributing to the pre-ARMv6 functionality (devices, CPU model etc.), which is the only area you're publically able to contribute now anyway. I realise they would overlap substantially in the code, but that doesn't mean you have to contribute any changes or reveal any information which depends on the ARMv6 or later documentation. I don't see why it would make a difference to what you're able to do, and that's why I'm asking why you think it would. Thanks, -- Jamie