All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Hollis Blanchard <hollis@austin.ibm.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: VGA console endian bug
Date: Sat, 11 Aug 2001 12:14:36 +0200	[thread overview]
Message-ID: <20010811121436.A704@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.05.10108111145260.8907-100000@callisto.of.borg>; from geert@linux-m68k.org on Sat, Aug 11, 2001 at 11:52:09AM +0200


On Sat, Aug 11, Geert Uytterhoeven wrote:

> +       for(i = 0; i < sizeof(welcometext); i++)
> +           welcomestring[i] = 0x0700 | welcometext[i];
>             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> +       fbcon_putcs( conp, welcomestring, sizeof(welcometext), 0, 0 );
>
> That's not correct, you _must_ use scr_{read,write}w() to access screen
> buffers. fbcon_putcs() expects a pointer to a shadow screen buffer.
>
> Please try
>
>     scr_writew(0x0700 | welcometext[i], &welcomestring[i]);
>
> instead.
>
> Your code works on ia32 because ia32 and VGA are both little endian.
> It works on SPARC because SPARC and fbdev on SPARC are both big endian.
> I guess it fails on a real VGA textconsole on SPARC too (iff SPARC would
> support VGA text mode).

Well, that fixes "the last known problem".

But it still leaves the question whats really wrong with the vga console :)


Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-08-11 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 16:52 VGA console endian bug Hollis Blanchard
2001-08-10  8:41 ` Geert Uytterhoeven
2001-08-10 21:13   ` Hollis Blanchard
2001-08-11  8:33     ` Geert Uytterhoeven
2001-08-11  8:45       ` Olaf Hering
2001-08-11  9:05         ` Olaf Hering
2001-08-11  9:52           ` Geert Uytterhoeven
2001-08-11 10:14             ` Olaf Hering [this message]

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=20010811121436.A704@suse.de \
    --to=olh@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=hollis@austin.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.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.