public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
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: Thu, 17 Feb 2022 07:05:59 +1300	[thread overview]
Message-ID: <e150da65-d239-54e8-b637-98d5354cbc64@gmail.com> (raw)
In-Reply-To: <CAMuHMdWZ+H5kJyOUQWW49EGUemUe7qERuLaMWFOs0N8nNbuMTQ@mail.gmail.com>

Hi Geert,

On 16/02/22 21:24, Geert Uytterhoeven wrote:
>
>> The atafb driver references a 'linux/tools/hardware.txt' file for a
>> description of the Videl registers. Does anyone still have a copy of
>> that file?
> At least full-history-linux doesn't have it.
Might be a reference to the old FTP archive at Erlangen then ...
>> Failing that - how would I go about setting specific text colours for
>> the console (or draw a test pattern showing the result of the four
>> palette entries)?
> I typically use fbtest for that.
One more reason to hunt for that in the dino age package archives :-)
>
> I also have a script to show the 16 colors (assumed there are 16):
>
> #!/bin/bash
> printf "\e[7m"
> printf "\e[30m                    BLACK                     \n"
> printf "\e[31m                    RED                       \n"
> printf "\e[32m                    GREEN                     \n"
> printf "\e[33m                    YELLOW                    \n"
> printf "\e[34m                    BLUE                      \n"
> printf "\e[35m                    MAGENTA                   \n"
> printf "\e[36m                    CYAN                      \n"
> printf "\e[37m                    WHITE                     \n"
> printf "\e[1m"
> printf "\e[30m                    BLACK                     \n"
> printf "\e[31m                    RED                       \n"
> printf "\e[32m                    GREEN                     \n"
> printf "\e[33m                    YELLOW                    \n"
> printf "\e[34m                    BLUE                      \n"
> printf "\e[35m                    MAGENTA                   \n"
> printf "\e[36m                    CYAN                      \n"
> printf "\e[37m                    WHITE                     \n"
> printf "\e[0m"
>
Thanks, that ought to do - I vaguely remembered there should be control 
sequences to set colour (having worked on VT100 and VT2xx emulators, 
though not the actual hardware terminals) but wasn't too sure.

Cheers,

     Michael


> 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

  reply	other threads:[~2022-02-16 18:06 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 [this message]
2022-02-16  7:32           ` Michael Schmitz
     [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=e150da65-d239-54e8-b637-98d5354cbc64@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