From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LNC1l-0006hc-Qh for qemu-devel@nongnu.org; Wed, 14 Jan 2009 15:07:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LNC1j-0006fn-SP for qemu-devel@nongnu.org; Wed, 14 Jan 2009 15:07:49 -0500 Received: from [199.232.76.173] (port=59495 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNC1j-0006fb-Fl for qemu-devel@nongnu.org; Wed, 14 Jan 2009 15:07:47 -0500 Received: from mx20.gnu.org ([199.232.41.8]:38950) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LNC1j-0002Iv-5Y for qemu-devel@nongnu.org; Wed, 14 Jan 2009 15:07:47 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LNC1h-0005s0-F4 for qemu-devel@nongnu.org; Wed, 14 Jan 2009 15:07:45 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH] [RFC] Variable video ram size option Date: Wed, 14 Jan 2009 20:07:42 +0000 References: <496B965A.9000701@eu.citrix.com> In-Reply-To: <496B965A.9000701@eu.citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901142007.42812.paul@codesourcery.com> 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: Trolle Selander > While I have my doubts about there being any applications or games using > VBE & triple buffering that will actually run at 2560x1600 with any kind > of decent performance , I also see no reason to set this limit any lower > than the theoretically usable max, so 48 Megs it is. You're missing the point. There is no "usable max". The only limits are those implied by 16-bit coordinates, address space, and the imagination of the programmer. Paul