qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: andreas.faerber@web.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc32 network problems
Date: Thu, 7 Jun 2007 22:04:31 +0100	[thread overview]
Message-ID: <20070607210431.GB26587@networkno.de> (raw)
In-Reply-To: <f43fc5580706071259q356d4d0dh545fa26481500627@mail.gmail.com>

Blue Swirl wrote:
> On 6/6/07, Andreas Färber <andreas.faerber@web.de> wrote:
> >I also made some local changes to tcx.c today to avoid having a blue-
> >footed penguin on Intel. There's a TODO in that file saying the RGB
> >functions should be merged with vga.c (where they are being patched
> >by Q) - should I provide a qemu patch doing this and fixing the issue
> >for both? Or is this for some reason restricted to Q?
> 
> I made a patch to fix both vga and tcx while also unifying the pixel
> operations, does it fix the blue foot disease on PPC?

Hm, _with_ this patch I get (on PPC/Linux, emulating LE MIPS):
 - a blue-footed penguin when the cirrus FB is started
 - blue instead of red colour in console output
 - A general blue-to-red inversion for X11 in 16bit mode.

Note that the colours for the last one were already not quite right
(e.g. grey became a pale blue), but with your patch it looks even
weirder.


Thiemo

  reply	other threads:[~2007-06-07 21:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 22:17 [Qemu-devel] Sparc32 network problems Andreas Färber
2007-06-06  7:42 ` Nigel Horne
2007-06-06 12:51 ` Andreas Färber
2007-06-06 18:27   ` Blue Swirl
2007-06-06 18:35     ` Aurelien Jarno
2007-06-06 18:52       ` Blue Swirl
2007-06-06 20:45     ` Andreas Färber
2007-06-07 11:47       ` Andreas Färber
2007-06-09 12:13         ` Andreas Färber
2007-06-10 15:49           ` Blue Swirl
2007-06-10 16:26             ` Andreas Färber
2007-06-10 16:44               ` Blue Swirl
2007-06-07 19:59       ` Blue Swirl
2007-06-07 21:04         ` Thiemo Seufer [this message]
2007-06-07 21:41           ` Andreas Färber
2007-06-08 16:25             ` Blue Swirl
2007-06-08 18:35               ` Thiemo Seufer
2007-06-08 19:04                 ` Blue Swirl
2007-06-09 14:48                   ` Thiemo Seufer
2007-06-08 20:44                 ` Andreas Färber
2007-06-09  7:05                   ` Blue Swirl
2007-06-09  8:05                     ` Blue Swirl
2007-06-09 10:30                       ` Andreas Färber
2007-06-10 15:40                         ` Blue Swirl

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=20070607210431.GB26587@networkno.de \
    --to=ths@networkno.de \
    --cc=andreas.faerber@web.de \
    --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).