From: Aurelien Jarno <aurelien@aurel32.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix curses on big endian hosts
Date: Fri, 31 Dec 2010 20:10:27 +0100 [thread overview]
Message-ID: <20101231191027.GE3615@hall.aurel32.net> (raw)
In-Reply-To: <AANLkTim2BQ-uJW1JDQhAb3fccKGsomd8Lr=VfUfNhahH@mail.gmail.com>
On Thu, Dec 30, 2010 at 05:42:43PM +0000, Blue Swirl wrote:
> On Wed, Dec 29, 2010 at 9:27 PM, Aurelien Jarno <aurelien@aurel32.net> wrote:
> > On big endian hosts, the curses interface is unusable: the emulated
> > graphic card only displays garbage, while the monitor interface displays
> > nothing (or rather only spaces).
> >
> > The curses interface is waiting for data in native endianness, so
> > console_write_ch() should not do any conversion. The conversion should
> > be done when reading the video buffer in hw/vga.c. I supposed this
> > buffer is in little endian mode, though it's not impossible that the
> > data is actually in guest endianness. I currently have no big endian
> > guest to way (they all switch to graphic mode immediately).
>
> First versions of OpenBIOS for Sparc64 used text console, I switched
> to VBE frame buffer later.
Do you know if it is easy to switch back to text console? That would be
an easy way to check what is correct.
> I'm also puzzled by the uses of TARGET_WORDS_BIGENDIAN in
> hw/vga_template.h. I'd suppose that VGA (especially PCI devices) would
> be always little endian, so why the checks?
>
I also don't explain them. I have tried to remove them, and powerpc and
sparc target still seems to work.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-12-31 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 21:27 [Qemu-devel] [PATCH] Fix curses on big endian hosts Aurelien Jarno
2010-12-30 17:42 ` Blue Swirl
2010-12-31 19:10 ` Aurelien Jarno [this message]
2010-12-31 23:41 ` Andreas Färber
2011-01-01 0:05 ` Aurelien Jarno
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=20101231191027.GE3615@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=blauwirbel@gmail.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).