All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	BALATON Zoltan <balaton@eik.bme.hu>,
	qemu-devel@nongnu.org
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] ppc vga output breakage since commit c3c1bb99
Date: Mon, 30 Mar 2015 12:28:58 +0200	[thread overview]
Message-ID: <5519256A.1010202@redhat.com> (raw)
In-Reply-To: <5519235C.6090004@ilande.co.uk>



On 30/03/2015 12:20, Mark Cave-Ayland wrote:
>> > 
>> > Of course, there's a QEMU regression too and I'm thinking of how to fix it.
> Hmmm that's interesting because the documentation refers to both
> registers being 16-bit: http://wiki.osdev.org/Bochs_VBE_Extensions. And
> indeed the pseudo-code uses outpw/inpw for accesses, even though the
> index and data registers are only 1 byte apart (0x1ce and 0x1cf) in I/O
> space.

Ugh, you're right.

> Maybe OpenBIOS is getting the endian conversion incorrect for the word
> access? (i.e. it's not converting to little endian).

No, that's not it.  It's basically treating the whole access as
"unassigned" because 0x1cf is not allocated (on non-x86 machines, the
DISPI data port is at 0x1d0).

Paolo

  reply	other threads:[~2015-03-30 10:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 19:04 [Qemu-devel] ppc vga output breakage since commit c3c1bb99 BALATON Zoltan
2015-03-28 19:19 ` Mark Cave-Ayland
2015-03-30  9:51   ` Paolo Bonzini
2015-03-30 10:20     ` Mark Cave-Ayland
2015-03-30 10:28       ` Paolo Bonzini [this message]
2015-03-30 11:45         ` Peter Crosthwaite
2015-03-30 11:47           ` Paolo Bonzini
2015-03-31 22:34             ` Mark Cave-Ayland
2015-04-01  7:55               ` Paolo Bonzini
2015-04-02 11:45                 ` Mark Cave-Ayland
2015-04-02 13:53                   ` Paolo Bonzini

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=5519256A.1010202@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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.