From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Giuliano Pochini <pochini@denise.shiny.it>
Cc: "Timothy A. Seufert" <tas@mindspring.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Console text selection bug
Date: Sat, 10 Mar 2001 09:18:51 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.05.10103100916270.765-100000@callisto.of.borg> (raw)
In-Reply-To: <3AA69A1D.F1F85B48@denise.shiny.it>
On Wed, 7 Mar 2001, Giuliano Pochini wrote:
> >> It's an endian bug in fbcon when accessing the text/attribute buffer.
>
> > Nevertheless, it's a bug. Can someone please change fbcon_invert_region() to
> > use scr_{read,write}w() to access the shadow screen buffer and see whether it
> > works? Patches are accepted at linux-fbdev-devel@lists.sourceforge.net :-)
>
> Yes, it's an endianess bug. scr_{read,write}w() are defined as normal
> assignments in vt_buffer.h, so I wonder where is the bug. Is the shadow buffer
No, their definition in vt_buffer.h depends on VT_BUF_HAVE_RW. If that is
defined in <asm/vga.h>, vga.h must provide its own definitions.
> supposed to be native endian ?
It doesn't really matter, since all accesses must be done using
scr_{read,write}w() anyway. For performance reasons we chose native endianness.
Except when VGA (CONFIG_VGA_CONSOLE || CONFIG_MDA_CONSOLE) is defined, since on
VGA/MDA the shadow buffer _is_ the screen image and must be little endian.
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
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-10 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 17:09 Console text selection bug Giuliano Pochini
2001-03-05 21:35 ` Benjamin Herrenschmidt
2001-03-06 6:18 ` Timothy A. Seufert
2001-03-06 6:52 ` Geert Uytterhoeven
2001-03-07 20:29 ` Giuliano Pochini
2001-03-10 8:18 ` Geert Uytterhoeven [this message]
2001-03-05 23:48 ` Hollis R Blanchard
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=Pine.LNX.4.05.10103100916270.765-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@denise.shiny.it \
--cc=tas@mindspring.com \
/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).