From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LKsm5-0002SN-HJ for qemu-devel@nongnu.org; Thu, 08 Jan 2009 06:10:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LKsm4-0002S9-BY for qemu-devel@nongnu.org; Thu, 08 Jan 2009 06:10:04 -0500 Received: from [199.232.76.173] (port=33965 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKsm4-0002S6-6i for qemu-devel@nongnu.org; Thu, 08 Jan 2009 06:10:04 -0500 Received: from bart.se.axis.com ([195.60.68.10]:48121) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LKsm3-0003mL-NS for qemu-devel@nongnu.org; Thu, 08 Jan 2009 06:10:03 -0500 Received: from bart.se.axis.com (bart.se.axis.com [127.0.0.1]) by bart.se.axis.com (Postfix) with ESMTP id 1426864140 for ; Thu, 8 Jan 2009 12:10:03 +0100 (CET) Received: from axis.com (edgar.se.axis.com [10.93.151.1]) by bart.se.axis.com (Postfix) with ESMTP id EBD856413F for ; Thu, 8 Jan 2009 12:10:02 +0100 (CET) Date: Thu, 8 Jan 2009 12:10:02 +0100 From: "Edgar E. Iglesias" Subject: Re: [Qemu-devel] [PATCH]: add leon target Message-ID: <20090108111002.GD26971@edgar.se.axis.com> References: <20090107102439.GA15209@ulanbator.act-europe.fr> <20090108100156.GB26971@edgar.se.axis.com> <7B084501-75D2-4E83-AA6B-EC8FD8B945A4@adacore.com> <20090108103328.GC26971@edgar.se.axis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tristan Gingold Cc: qemu-devel@nongnu.org On Thu, Jan 08, 2009 at 11:43:31AM +0100, Tristan Gingold wrote: >> >> Not sure what docs you are refering to, but I had a second look at the > > Sorry I was referring to the AT697E manual. > >> vhd and you seem to be correct. Odd... > > Yes, boring for our case... Hi again, You might want to handle writes to the ITC reg anyway. It is increasingly common for drivers (software) to mix interrupt drivenness with polling modes. These drivers sometimes need to be able to poll for and ack interrupts without necessarily having the core take them. Best regards