linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Jahns <Thomas.Jahns@epost.de>
To: Linux Fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: State of pm3fb driver
Date: Sun, 3 Oct 2004 14:53:43 +0200	[thread overview]
Message-ID: <20041003125343.GA7675@mercury.jahnsnet.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

Hello,

after I was quite unhappy with the support for my ATI Mach64 adapter in  
my Powermac 7500 I aquired a Formac Proformance III adapter that  
supposedly uses a Permedia 3 chip. Unfortunately it seems that the  
driver is broken in kernel 2.6.8 (at least to my incomplete  
understanding of the subject) for the following reasons:

a) drivers/video/pm3fb.c uses a number of includes no more present
	(I could fix that as shown in the attached patch)
b) even if I fixed the compile time errors the resulting kernel does  
not display anything to the console (but works without problems  
otherwise). Also the kernel log is flooded with repetitions of the  
following line (but that might have other reasons, because I noticed it  
also happens when I boot an older kernel without the pm3 driver:
IN from bad port 64 at c01a22a

c) drivers/video/pm3fb.c and include/video/pm3fb.h contain a number of  
#ifdef statements that check for KERNEL_2_2 and similar vars, but never  
for KERNEL_2_6. So I assume the source has not seen any maintainance in  
2.6?

The card identifies itself as follows in lspci -v -s 00:0e.0:

0000:00:0e.0 Display controller: 3DLabs GLINT R3 (rev 01)
        Subsystem: 3DLabs GLINT R3
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 24
        Memory at 80880000 (32-bit, non-prefetchable) [size=128K]
        Memory at 84000000 (32-bit, prefetchable) [size=64M]
        Memory at 90000000 (32-bit, prefetchable) [size=64M]
        I/O ports at 0800 [disabled] [size=16]
        Expansion ROM at 80840000 [disabled] [size=64K]
        Capabilities: <available only to root>

Any comments what I should try from here?

Ciao, Thomas Jahns
-- 
"Computers are good at following instructions,
 but not at reading your mind."
D. E. Knuth, The TeXbook, Addison-Wesley 1984, 1986, 1996, p. 9

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pm3_includes.patch --]
[-- Type: text/x-patch; charset=unknown-8bit, Size: 614 bytes --]

--- /tmp/kernel-source-2.6.8/drivers/video/pm3fb.c	2004-08-14 07:36:32.000000000 +0200
+++ /home/tjahns/tmp/debian_stuff/kernel-compile/2.6.8/kernel-source-2.6.8/drivers/video/pm3fb.c	2004-10-03 14:15:42.000000000 +0200
@@ -68,14 +68,7 @@
 #include <linux/pci.h>
 #include <linux/ioport.h>
 
-#include <video/fbcon.h>
-#include <video/fbcon-mfb.h>
-#include <video/fbcon-cfb2.h>
-#include <video/fbcon-cfb4.h>
-#include <video/fbcon-cfb8.h>
-#include <video/fbcon-cfb16.h>
-#include <video/fbcon-cfb24.h>
-#include <video/fbcon-cfb32.h>
+#include "console/fbcon.h"
 #include <video/pm3fb.h>
 
 #include <asm/io.h>

             reply	other threads:[~2004-10-04 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-03 12:53 Thomas Jahns [this message]
2004-10-05 13:01 ` State of pm3fb driver Romain Dolbeau
2004-10-05 19:06   ` Thomas Jahns
2004-10-12 19:15     ` David Eger

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=20041003125343.GA7675@mercury.jahnsnet.de \
    --to=thomas.jahns@epost.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).