From: <jhf@rivenstone.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [FBDEV UPDATE] Newer patch.
Date: Wed, 22 Oct 2003 16:50:43 -0400 [thread overview]
Message-ID: <20031022205043.GA725@rivenstone.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0310221814290.25125-100000@phoenix.infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 1081 bytes --]
On Wed, Oct 22, 2003 at 06:31:22PM +0100, James Simmons wrote:
>
> Hi folks.
>
> I have a new patch against 2.6.0-test8. This patch is a few fixes and I
> added back in functionality for switching the video mode for fbcon via
> fbset again. Give it a try and let me know the results.
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
The attached patch is needed to make tdfxfb compile after
applying this patch and also in test8-mm1 (so presumably in your older
patch as well) (tdfxfb_imageblt calls cfb_imageblt).
tdfx is still badly broken in -mm1 both before and after replacing
the older fbdev patch in -mm1 with your new one. The behavior is much
the same as reported with other drivers -- out of range frequencies
and the same backtraces. With fbset working I can set a new
resolution which gets me a barely usable console -- lots of
artifacts.
I don't have time to test against vanilla -test8; maybe later.
Thanks!
--
Joseph Fannin
jhf@rivenstone.net
"That's all I have to say about that." -- Forrest Gump.
[-- Attachment #1.2: out --]
[-- Type: text/plain, Size: 924 bytes --]
diff -aur linux-2.6.0-test8-mm1_orig/drivers/video/Makefile /usr/src/linux-2.6.0-test8-mm1_duo/drivers/video/Makefile
--- linux-2.6.0-test8-mm1_orig/drivers/video/Makefile 2003-10-22 15:30:33.000000000 -0400
+++ /usr/src/linux-2.6.0-test8-mm1_duo/drivers/video/Makefile 2003-10-22 16:38:27.000000000 -0400
@@ -32,7 +32,7 @@
obj-$(CONFIG_FB_CYBER) += cyberfb.o
obj-$(CONFIG_FB_CYBER2000) += cyber2000fb.o cfbfillrect.o cfbcopyarea.o cfbimgblt.o
obj-$(CONFIG_FB_SGIVW) += sgivwfb.o cfbfillrect.o cfbcopyarea.o cfbimgblt.o
-obj-$(CONFIG_FB_3DFX) += tdfxfb.o
+obj-$(CONFIG_FB_3DFX) += tdfxfb.o cfbimgblt.o
obj-$(CONFIG_FB_MAC) += macfb.o macmodes.o cfbfillrect.o cfbcopyarea.o cfbimgblt.o
obj-$(CONFIG_FB_HP300) += hpfb.o cfbfillrect.o cfbimgblt.o
obj-$(CONFIG_FB_OF) += offb.o cfbfillrect.o cfbimgblt.o cfbcopyarea.o
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-22 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 17:31 [FBDEV UPDATE] Newer patch James Simmons
2003-10-22 20:38 ` Carlo E. Prelz
2003-10-22 21:46 ` [Linux-fbdev-devel] " James Simmons
2003-10-22 20:50 ` jhf [this message]
2003-10-22 21:46 ` James Simmons
2003-10-23 10:00 ` Geert Uytterhoeven
2003-10-23 14:43 ` Ben Collins
2003-10-23 22:50 ` James Simmons
2003-10-23 23:45 ` Ben Collins
2003-10-30 18:38 ` James Simmons
2003-10-30 23:07 ` Carlo E. Prelz
2003-11-17 18:38 ` Ben Collins
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=20031022205043.GA725@rivenstone.net \
--to=jhf@rivenstone.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).