From: andrzej zaborowski <balrogg@gmail.com>
To: Blue Swirl <blueswir1@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: qemu curses driver
Date: Tue, 13 Dec 2005 00:19:36 +0100 [thread overview]
Message-ID: <fb249edb0512121519s3811f4b6n@mail.gmail.com> (raw)
In-Reply-To: <BAY104-F15B14BB06D367E65D98899FF460@phx.gbl>
Hiya,
On 12/12/05, Blue Swirl <blueswir1@hotmail.com> wrote:
> Sparc32 graphics cards are just frame buffers without a text mode. Sparc64
> uses PCI cards, including VGA, so any text mode enhancements could be useful
> there.
I just noticed that there's a Sparc64 architecture, and it is there
quite separate from Sparc32. I only didn't see it before because it
doesn't appear in the output of "./configure --help" together with
other targets.
Indeed the "qemu-system-sparc64" executable, unlinke
qemu-system-sparc, is linked with "vga.o", the normal PCI card VGA
emulator.
Fortunately I disabled compiling with Curses only for "sparc" and
"arm", so when I reran ./configure with "sparc64" in the targets list
it compiled just fine with curses support built into
qemu-system-sparc64.
I only have no way to see whether everything works because I didn't
even find a working BIOS image for Sparc 64, but it should be fine.
Do the video adapters used in Sparc 32 machines really have nothing
like a text mode?
Cheers,
--
balrog 2oo5
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
next prev parent reply other threads:[~2005-12-12 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 16:39 [Qemu-devel] Re: qemu curses driver Blue Swirl
2005-12-12 23:19 ` andrzej zaborowski [this message]
2005-12-13 18:53 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2005-12-10 8:17 [Qemu-devel] " andrzej zaborowski
2005-12-12 6:58 ` [Qemu-devel] " andrzej zaborowski
2005-12-12 10:46 ` Johannes Schindelin
2005-12-12 22:53 ` andrzej zaborowski
2008-01-10 16:50 ` andrzej zaborowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb249edb0512121519s3811f4b6n@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=blueswir1@hotmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).