From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Petr Stehlik <pstehlik@sophics.cz>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Wrong colors on ARAnyM
Date: Wed, 16 Feb 2022 20:32:43 +1300 [thread overview]
Message-ID: <45001563-bd16-616e-3d42-263de137c004@gmail.com> (raw)
In-Reply-To: <CAMuHMdWkxDMbS4D8wkEPAVgrFnoJzejUkxKCnvA+MA38vS6g9Q@mail.gmail.com>
Hi Geert,
Am 15.02.2022 um 21:11 schrieb Geert Uytterhoeven:
>> Only the blue bits ever entirely seem to end up where they ought to.
>> Testing this hypothesis on ARAnyM (without getting it to boot all the
>> way, for some odd reason likely to do with my current .config) shows
>> that the current code results in the shifter_tt.color_reg entries either
>> 5 or 0x17, 0x113 or 0x117. Adding the missing parentheses results in
>> what I'd expect to see.
>
> Oops.
>
>> This bug has been present since at least 2.4.30. I do recall seeing this
>> odd blue console before on the Falcon, so it's been a real bug for ages.
>
> I recall seeing an odd blue console before, too.
> I always dismissed it as some artefact of redrawing the screen in
> a different color mode, like we used to have when switching from a
> 16-color to a monochrome text console (remember the underlined text?).
>
> Did/do you see it on the real Falcon, too?
I do see the blue text colour bug, but not the random behaviour in
switching to 2 bpp, on the actual hardware. So there appear to be two
distinct bugs - the STe colour map entries tend towards the blue, and
switching to that palette does not always happen when it should.
Still no idea what causes ARAnyM to miss palette updates or use the
wrong palette at times ...
>> I can confirm that the bug is gone with additional parentheses to apply
>> the shifts (<<8 for red, <<4 for green) to the result of the bit-wise
>> or, not just the right-hand portion of it.
>>
>> Do you want me to prepare a patch, or would you prefer to do it yourself?
>
> Feel free to send a patch.
Done (now that I've tested on hardware).
Cheers,
Michael
> If you don't get to it, I'll make one, eventually.
> Thanks!
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2022-02-16 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cd0eadc8-2255-c905-d466-6514a3e1d6bd@physik.fu-berlin.de>
2022-02-12 14:59 ` Wrong colors on ARAnyM Geert Uytterhoeven
[not found] ` <b03160b6-7f3b-7765-49ee-c49b7dd2c4e0@gmail.com>
2022-02-14 7:41 ` Geert Uytterhoeven
2022-02-14 20:50 ` Michael Schmitz
2022-02-14 21:36 ` Michael Schmitz
2022-02-15 8:11 ` Geert Uytterhoeven
2022-02-15 9:16 ` Petr Stehlík
2022-02-21 1:54 ` Michael Schmitz
2022-02-15 20:49 ` Michael Schmitz
2022-02-16 8:24 ` Geert Uytterhoeven
2022-02-16 18:05 ` Michael Schmitz
2022-02-16 7:32 ` Michael Schmitz [this message]
[not found] ` <3dfea92e-baa1-6374-cdd-7aa8bd8c8ff@tarent.de>
2022-03-09 18:55 ` Wrong colours " Thorsten Glaser
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=45001563-bd16-616e-3d42-263de137c004@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=pstehlik@sophics.cz \
/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