From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39371) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QCvJx-0005dZ-Vt for qemu-devel@nongnu.org; Thu, 21 Apr 2011 10:57:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QCvJw-0000n0-Kk for qemu-devel@nongnu.org; Thu, 21 Apr 2011 10:57:29 -0400 Received: from b.mail.sonic.net ([64.142.19.5]:57348) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QCvJw-0000mQ-BU for qemu-devel@nongnu.org; Thu, 21 Apr 2011 10:57:28 -0400 Message-ID: <4DB045C2.70100@twiddle.net> Date: Thu, 21 Apr 2011 07:57:06 -0700 From: Richard Henderson MIME-Version: 1.0 References: <1303225501-12778-1-git-send-email-rth@twiddle.net> <4DAEF1D1.7070309@twiddle.net> <98CE88F4-2E03-43E8-AE84-F6B78416FF74@adacore.com> <4DAF01BE.7080605@twiddle.net> <1303393062.17953.20.camel@nibbler.dlib.indiana.edu> <1303397328.17953.46.camel@nibbler.dlib.indiana.edu> In-Reply-To: <1303397328.17953.46.camel@nibbler.dlib.indiana.edu> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/24] Alpha system emulation, v2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brian Wheeler Cc: Tristan Gingold , qemu-devel@nongnu.org On 04/21/2011 07:48 AM, Brian Wheeler wrote: > On Thu, 2011-04-21 at 15:43 +0200, Tristan Gingold wrote: >> On Apr 21, 2011, at 3:37 PM, Brian Wheeler wrote: >> >>> On Thu, 2011-04-21 at 14:31 +0200, Tristan Gingold wrote: >>>> On Apr 20, 2011, at 5:54 PM, Richard Henderson wrote: >>>> >>>>> On 04/20/2011 08:46 AM, Tristan Gingold wrote: >>>> BSD should be doable, but I doubt for Tru64. Do you have technical doc about the SRM ? >>>> IIRC, the SRM uses its own palcode and SRM specific pal calls. IIRC the main thing that was lacking between SRM and the Evaluation Board PALcode that was used in MILO is the Console Callback (CCB) structure and routines. > Ah, gotcha. It almost seems like the console could actually be > implemented in qemu itself, rather than a guest side thing, as long as > it looks like part III of the ARM :) My first try last year was going down this path. It turned out to be irritatingly difficult to manage the data setup inside QEMU itself. Thus I came to be writing a custom PALcode image that makes a number of simplifying assumptions based on the ability to off-load some work to QEMU. r~