From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CDjhQ-0005iT-6G for qemu-devel@nongnu.org; Sat, 02 Oct 2004 09:13:20 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CDjhP-0005iE-4A for qemu-devel@nongnu.org; Sat, 02 Oct 2004 09:13:19 -0400 Received: from [129.104.30.34] (helo=a.mx.polytechnique.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CDjag-00010N-VB for qemu-devel@nongnu.org; Sat, 02 Oct 2004 09:06:23 -0400 Message-ID: <415EA7FE.8000100@bellard.org> Date: Sat, 02 Oct 2004 15:07:10 +0200 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] Patch: Sparc system support References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: blueswir1@hotmail.com Cc: qemu-devel@nongnu.org Blue Swirl wrote: > Most of your changes are ok, except for the DHCP one. It's idea is to > respond to BOOTP clients which use no extensions added by DHCP. > > The magic address-banging loader is a quick & dirty hack anyway, I'm > thinking of a better way to initialise Proll and implement kernel loading. OK. So you mean I must reverse your patch in bootp.c or implement a correct bootp server ? > What are you planning for env->access_type? Sparc MMU needs to know > whether the memory access is for data or instructions, did the access > come from user or kernel code and is it read or write. rw == 2 in cpu_handle_mmu_fault() will mean 'code access'. I made the patch in my repository for i386 and PowerPC, but I need to test it more before commiting. Fabrice.