From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48041)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bK64Y-0001K5-G3
	for qemu-devel@nongnu.org; Mon, 04 Jul 2016 11:46:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bK64V-0004OZ-A2
	for qemu-devel@nongnu.org; Mon, 04 Jul 2016 11:46:10 -0400
Received: from mx1.redhat.com ([209.132.183.28]:53781)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bK64V-0004OU-42
	for qemu-devel@nongnu.org; Mon, 04 Jul 2016 11:46:07 -0400
References: <1467370471-20554-1-git-send-email-kraxel@redhat.com>
	<1467370471-20554-2-git-send-email-kraxel@redhat.com>
	<20160701154732.GA11200@morn.lan>
	<1467620195.15123.133.camel@redhat.com>
	<7c1baeab-b8b0-93d1-a9a2-054dfd92ece0@redhat.com>
	<1467636384.15123.177.camel@redhat.com>
	<20160704152648.GA2039@morn.lan>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <5180c71c-cc8e-dbbd-3670-d4f143862e86@redhat.com>
Date: Mon, 4 Jul 2016 17:45:56 +0200
MIME-Version: 1.0
In-Reply-To: <20160704152648.GA2039@morn.lan>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH 1/2] serial console, output
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin O'Connor <kevin@koconnor.net>, Gerd Hoffmann <kraxel@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org



On 04/07/2016 17:26, Kevin O'Connor wrote:
> > 4k, we need both character and attribute.  But, yes, if we can allocate
> > that somewhere in real mode address space without running into memory
> > pressure this might be the best option.
> 
> Unfortunately, the screen can be larger than 80x25.

It can with SVGA BIOS, but Gerd here only supports mode 3, doesn't he?

Paolo

> If a large buffer is desired, it's also possible to malloc_high() it
> and then use either: call32() to access it, or int1587 to read/write
> it (see ramdisk.c:ramdisk_copy() as an example).  Either way it seems
> ugly.
> 
> At one point I looked through the sgabios code and was able to
> understand how it did caching.  I'll take another look and see if I
> can describe it.