All of lore.kernel.org
 help / color / mirror / Atom feed
From: "T. Huth" <1546680@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1546680] Re: Incorrect display colors when running big endian guest on POWER8 little endian host
Date: Mon, 27 Jun 2016 20:15:48 -0000	[thread overview]
Message-ID: <20160627201548.18142.40389.malone@wampee.canonical.com> (raw)
In-Reply-To: 20160217182116.22366.12898.malonedeb@soybean.canonical.com

Which version of QEMU are you using? How did you start QEMU (i.e. which
kind of graphics card did you specify)? And which version of CentOS are
you using for the guest?

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1546680

Title:
  Incorrect display colors when running big endian guest on POWER8
  little endian host

Status in QEMU:
  New

Bug description:
  When running a big endian CentOS guest on a little endian host system
  the display shows severe color issues, probably due to endianness not
  being properly detected / switched in the emulated display hardware.
  Little endian guests show no display issues on the same host hardware
  and software.

  See attachment for an example of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1546680/+subscriptions

  parent reply	other threads:[~2016-06-27 20:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 18:21 [Qemu-devel] [Bug 1546680] [NEW] Incorrect display colors when running big endian guest on POWER8 little endian host Timothy Pearson
2016-02-19 23:23 ` [Qemu-devel] [Bug 1546680] " Timothy Pearson
2016-06-27 20:15 ` T. Huth [this message]
2016-07-26 19:44 ` Timothy Pearson
2016-07-26 19:45 ` Timothy Pearson
2019-02-05  7:21 ` Thomas Huth
2019-04-07  4:17 ` Launchpad Bug Tracker

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=20160627201548.18142.40389.malone@wampee.canonical.com \
    --to=1546680@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.