From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:56562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKVUo-0008Dh-EM for qemu-devel@nongnu.org; Tue, 26 Mar 2013 11:09:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UKVUm-0007Iw-WC for qemu-devel@nongnu.org; Tue, 26 Mar 2013 11:09:06 -0400 Received: from mail.mc.net ([209.172.128.24]:52135) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1UKVUm-0007Hx-Q3 for qemu-devel@nongnu.org; Tue, 26 Mar 2013 11:09:04 -0400 Message-ID: <5151BA0A.1040000@mc.net> Date: Tue, 26 Mar 2013 10:08:58 -0500 From: Bob Breuer MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] selecting a sparc framebuffer from command line List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: Blue Swirl , Mark Cave-Ayland , Gerd Hoffmann , Artyom Tarasenko On 3/26/2013 6:13 AM, Artyom Tarasenko wrote: > It looks like we will have more framebuffers beside TCX in the near future. > One way to use them would be to make new machines combining a base > machine name with a framebuffer name, like ss5tcx and ss5cg3, but I > guess this would produce too many machines if we have more than 2 > framebuffers. > > Should the "-vga" option be (mis)used for selecting a framebuffer? > They are not called "VGA" in the wild, but maybe the name VGA is > obvious enough for a modern user? After all there is already a "-hda" > option in the SPARCStation-5 emulation command line, although in the > non-emulating world no one calls scsi disk "hda". > > Or should an architecture-specific option, like -framebuffer be added? > I would like to see -device used. With a better sbus framework, adding multiple video devices on sparc32 should be really easy to do. I just looked at how "-device cirrus-vga" works. To get -device to override the default video, we need to add minimal support into vl.c to recognize each video device and handle the default_vga flag. Then sparc32 could limit itself to handling either VGA_NONE or VGA_STD when it adds the default video. Bob