From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LdR0U-0005bq-HI for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:21:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LdR0T-0005Z3-6B for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:21:37 -0500 Received: from [199.232.76.173] (port=45475 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LdR0T-0005Yk-0t for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:21:37 -0500 Received: from mail-fx0-f175.google.com ([209.85.220.175]:33851) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LdR0S-0005sQ-Ie for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:21:36 -0500 Received: by fxm23 with SMTP id 23so1335604fxm.34 for ; Sat, 28 Feb 2009 07:21:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1235832403-29902-1-git-send-email-agraf@suse.de> References: <1235832403-29902-1-git-send-email-agraf@suse.de> Date: Sat, 28 Feb 2009 17:21:34 +0200 Message-ID: Subject: Re: [Qemu-devel] [PATCH] PPC: Use correct values for 970 interrupts and hreset From: Blue Swirl Content-Type: text/plain; charset=UTF-8 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: qemu-devel@nongnu.org Cc: Alexander Graf On 2/28/09, Alexander Graf wrote: > The 970 doesn't set exception prefix values by default. According to > the ISA it just jumps to real mode with nip=vector. > > Because of that the current hreset_vector is rendered invalid. Before, > it would go to excp_prefix (ROM base) + 0x100 (reset vector) and get > into the firmware. > > But with the corrected excp_prefix, we now have to jump to the real > entry point, which is at 0xFFFFFFFC. I don't think this is correct. 970FX uses HIOR to specify the exception vector base, please see "IBM PowerPC 970FX RISC Microprocessor", page 273. >>From OpenBIOS viewpoint both vectors are OK. > I can't imagine how any OS that does memory management itself could have > possibly worked with the code as it was. Maybe Qemu uses the 604 exception prefix somewhere.