From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
Jon Erick Ween <jween@som.llu.edu>,
linuxppc-dev@lists.linuxppc.org, linux-fbdev@vuser.vu.union.edu
Subject: Re: Xfree86-4.0.1, Lombard, Mach64 driver, X-server Crash
Date: Sun, 1 Oct 2000 13:30:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10010011330090.377-100000@cassiopeia.home> (raw)
In-Reply-To: <Pine.A41.3.96LJ1.1b7.1000929112058.7632A-100000@unlserve.unl.edu>
On Fri, 29 Sep 2000, Takashi Oe wrote:
> On Fri, 29 Sep 2000, Geert Uytterhoeven wrote:
> > > > In 2.5.x, we'll have a user-defined xor mask for the cursor as the 17th entry
> > > > in the dispsw_data array.
> > >
> > > Can we put it for 2.4? As far as I can see, the actual size of
> > > dispsw_data matters only between fb driver and fbcon-cfbxx.c, and the
> > > changes required for each driver seem to be rather small. Besides,
> > > controlfb is not the only one which will benefit from this change.
> >
> > That's true. Personally, I see no problems with it if someone's willing to
> > write the patch for _all_ drivers at once. The real 2.4.0 is still a long way
> > to go, I think, and the impact of the required changes is known quite well.
>
> Good! I'll work on it. Only a few allocate memory for dispsw_data
> dynamically, the changes should be trivial for most.
>
> > The main thing we need to be careful about is that the xor mask is different
> > for truecolor and directcolor visuals: truecolor needs an `all ones' mask,
> > while directcolor needs `15' for each color component (drivers that incorrectly
> > report a directcolor instead of truecolor visual will easily be identified).
>
> I don't know how it will work out for atyfb, but we'll see...
Atyfb is directcolor. Grep fro VISUAL_ to find out :-)
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:[~2000-10-01 11:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-27 17:22 Xfree86-4.0.1, Lombard, Mach64 driver, X-server Crash Jon Erick Ween
2000-09-27 17:42 ` Olaf Hering
2000-09-27 18:17 ` Michael Schmitz
2000-09-27 19:13 ` Jon Erick Ween
2000-09-27 19:13 ` Michael Schmitz
2000-09-27 19:21 ` Michael Schmitz
2000-09-28 16:51 ` Jon Erick Ween
2000-09-28 18:14 ` Michael Schmitz
2000-09-27 20:35 ` Benjamin Herrenschmidt
2000-09-28 3:50 ` Takashi Oe
2000-09-28 11:08 ` Geert Uytterhoeven
2000-09-28 23:13 ` Takashi Oe
2000-09-29 11:05 ` Geert Uytterhoeven
2000-09-29 16:27 ` Takashi Oe
2000-10-01 11:30 ` Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-28 4:41 Jon Erick Ween
2000-09-28 19:49 Jon Erick Ween
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.10.10010011330090.377-100000@cassiopeia.home \
--to=geert@linux-m68k.org \
--cc=bh40@calva.net \
--cc=jween@som.llu.edu \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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).