From: Brad Douglas <brad@neruo.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-fbdev@vuser.vu.union.edu
Subject: Re: [PATCH] aty128fb & >8bit
Date: 12 Dec 2000 04:12:27 +0800 [thread overview]
Message-ID: <20001211204332Z129226-439+2988@vger.kernel.org> (raw)
In-Reply-To: <20001210134847.F4810@opus.bloom.county>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
> Hello. I just noticed that in 2.2.18pre27 you can only use the aty128fb
> driver at 8 bit, because of some missing bits to drivers/video/Config.in.
> w/o this you can't use console at > 8 bit nor X. I would consider this to
> be a good thing to squash for 2.2.18 final because 2.2.18 is the 1st release
> in a while that works well on PPC, and lots of PPCs have a rage128.
Also, this patch to make it compile as module. How did these get removed?
I could have swore they used to work fine.
Sorry for the attachment. This computer has evolution.
Brad Douglas
brad@neruo.com
http://www.linux-fbdev.org
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch-2.2.18pre25-videoMakefile --]
[-- Type: text/x-makefile, Size: 328 bytes --]
--- linux-2.2.18pre25/drivers/video/Makefile Mon Dec 11 12:05:55 2000
+++ linux/drivers/video/Makefile Thu Dec 7 15:26:03 2000
@@ -106,6 +106,10 @@
ifeq ($(CONFIG_FB_ATY128),y)
L_OBJS += aty128fb.o
+else
+ ifeq ($(CONFIG_FB_ATY128),m)
+ MX_OBJS += aty128fb.o
+ endif
endif
ifeq ($(CONFIG_FB_IGA),y)
prev parent reply other threads:[~2000-12-11 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 20:48 [PATCH] aty128fb & >8bit Tom Rini
2000-12-11 7:30 ` [linux-fbdev] " Geert Uytterhoeven
2000-12-11 20:12 ` Brad Douglas [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=20001211204332Z129226-439+2988@vger.kernel.org \
--to=brad@neruo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox