From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul Mackerras <paulus@cs.anu.edu.au>,
linuxppc-dev@lists.linuxppc.org,
Geert.Uytterhoeven@cs.kuleuven.ac.be
Subject: [PATCH] new offb.c fix
Date: Wed, 23 Dec 1998 10:23:27 +0100 [thread overview]
Message-ID: <19981223102327.016345@mail.mipsys.com> (raw)
In-Reply-To: <19981223043717.005394@mail.mipsys.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Enclosed is the latest version of the patch. I updated more pieces of
code here or there so that offb.c can now theorically work in directcolor
if the cmap_adr field is present.
However, I still disable this feature and uses the ATI kludge only in 8
bits since there is a difference in the way the color registers must be
programmed between different models of ATI chips, and this broke for
example 16 bits on PowerBook G3 Series (LT-G)
It still missing code for getting the default palette set by bootx but
this is less urgent. This fix was more important since I would like
everyone to be able to boot in "no video driver" mode, at least for the
installer. That also means that the installer could be packaged with a
kernel containing _only_ offb to save space.
Note: Geert, while testing in direct colors, I had a funny problem in 32
bits: everything was fine except the console cursor which had a different
color on each virtual console. Since I remember reading about similar
bugs in early versions of other fb devices, I guess it's a common
mistake. Do you have a clue about what's going on ? It's not very
important since we are always in truecolor with this version, but I'm
curious ;-)
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[-- Attachment #2: offb.patch.gz --]
[-- Type: application/octet-stream, Size: 1333 bytes --]
prev parent reply other threads:[~1998-12-23 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-23 3:37 [PATCH] offb.c fix Benjamin Herrenschmidt
1998-12-23 9:23 ` Benjamin Herrenschmidt [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=19981223102327.016345@mail.mipsys.com \
--to=bh40@calva.net \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@cs.anu.edu.au \
/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).