From: Helge Deller <deller@gmx.de>
To: Hollis Blanchard <hollis@austin.ibm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Olaf Hering <olh@suse.de>
Subject: Re: scr_*() audit
Date: Mon, 27 Aug 2001 09:02:15 +0200 [thread overview]
Message-ID: <20010827070236Z271661-760+6343@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.05.10108221846140.6842-100000@callisto.of.borg> <20010826173058.A1418@austin.ibm.com>
In-Reply-To: <20010826173058.A1418@austin.ibm.com>
On Monday 27 August 2001 00:30, Hollis Blanchard wrote:
> On Wed, Aug 22, 2001 at 07:06:12PM +0200, Geert Uytterhoeven wrote:
> > Since there are still some issues left with the scr_*() functions on
> > big-endian platforms that can have both VGA and frame buffer consoles, I
> > decided to spent some precious time on auditing the usage of these
> > functions.
>
> Much appreciated.
>
> For the record, this resolves my problems with VGA console (only; no fb) on
> PPC. Previously text written to non-active consoles was endian-reversed.
>
> If no one has any problems (anyone else tested it?), could this patch
> please be committed?
For me it looks good too. I just tested it on HP parisc in text- and fb-mode and
it worked without any problems. I only had to add a missing semicolon to the
patch:
linux-2.4.8-ac9/drivers/char/console.c:
while (cnt--) {
- u16 a = *q;
+ a = scr_readw(q);
a = ((a) & 0x88ff) | (((a) & 0x7000) >> 4) | (((a) & 0x0700) << 4);
- *q++ = a;
+ scr_writew(a, q);
+ q++
^^^ here
Greetings,
Helge
next prev parent reply other threads:[~2001-08-27 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 17:06 Geert Uytterhoeven
2001-08-23 21:11 ` Olaf Hering
2001-08-24 11:06 ` Olaf Hering
2001-08-26 22:30 ` Hollis Blanchard
2001-08-27 7:02 ` Helge Deller [this message]
2001-09-29 22:25 ` Geert Uytterhoeven
2001-09-29 22:27 ` Geert Uytterhoeven
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=20010827070236Z271661-760+6343@vger.kernel.org \
--to=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=hollis@austin.ibm.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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
all inboxes | Powered by JetHome®