From: Joshua Kwan <joshk@triplehelix.org>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [FBDEV updates] Newest framebuffer fixes.
Date: Thu, 10 Apr 2003 20:34:26 -0700 [thread overview]
Message-ID: <20030411033426.GA13930@triplehelix.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0304102005330.23030-100000@phoenix.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
On Thu, Apr 10, 2003 at 08:09:41PM +0100, James Simmons wrote:
>
> Hi!
>
> Here are the latest framebuffer changes. Some driver updates and a
> massive cleanup of teh cursor code. Tony please test it on the i810
> chipset. I tested it on the Riva but there is one bug I can't seem to
> find. Please test this patch. It is against 2.5.67 BK. It shoudl work
> against 2.5.67 as well.
I found that it requires this patch to compile correctly for radeonfb,
lifted from another LKML message:
--- a/include/linux/pci_ids.h 2003-04-02 22:10:00.000000000 +0200
+++ b/include/linux/pci_ids.h 2003-04-02 22:02:32.000000000 +0200
@@ -279,6 +279,7 @@
#define PCI_DEVICE_ID_ATI_RADEON_QO 0x514f
#define PCI_DEVICE_ID_ATI_RADEON_Ql 0x516c
#define PCI_DEVICE_ID_ATI_RADEON_BB 0x4242
+#define PCI_DEVICE_ID_ATI_RADEON_QM 0x514d /* LN (my Radeon 9100) */
/* Radeon RV200 (7500) */
#define PCI_DEVICE_ID_ATI_RADEON_QW 0x5157
#define PCI_DEVICE_ID_ATI_RADEON_QX 0x5158
And even then it does not build. Requires this patch.
--- a/drivers/video/radeonfb.c 2003-04-10 20:15:06.000000000 -0700
+++ b/drivers/video/radeonfb.c 2003-04-10 20:31:16.000000000 -0700
@@ -894,16 +894,6 @@
rinfo->pll.ref_div = 12;
rinfo->pll.ref_clk = 2700;
break;
- case PCI_DEVICE_ID_ATI_RADEON_ND:
- case PCI_DEVICE_ID_ATI_RADEON_NE:
- case PCI_DEVICE_ID_ATI_RADEON_NF:
- case PCI_DEVICE_ID_ATI_RADEON_NG:
- rinfo->pll.ppll_max = 40000;
- rinfo->pll.ppll_min = 20000;
- rinfo->pll.xclk = 27000;
- rinfo->pll.ref_div = 12;
- rinfo->pll.ref_clk = 2700;
- break;
case PCI_DEVICE_ID_ATI_RADEON_QD:
case PCI_DEVICE_ID_ATI_RADEON_QE:
case PCI_DEVICE_ID_ATI_RADEON_QF:
The kernel is still building, I will see what happens...
On 2.5.67-mm1 without the fbdev.diff, the computer would boot and not go
into fb mode at all. It would just hang there. So I'm trying this now.
Hope it works :)
Regards
Josh
--
New PGP public key: 0x27AFC3EE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-11 3:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 19:09 [FBDEV updates] Newest framebuffer fixes James Simmons
2003-04-10 19:09 ` James Simmons
2003-04-10 21:14 ` Paweł Gołaszewski
2003-04-10 21:14 ` Paweł Gołaszewski
2003-04-10 21:37 ` James Simmons
2003-04-10 21:37 ` James Simmons
2003-04-10 21:16 ` John Weber
2003-04-10 21:36 ` James Simmons
2003-04-10 23:06 ` John Weber
2003-04-11 3:34 ` Joshua Kwan [this message]
2003-04-11 5:13 ` John Weber
2003-04-11 18:21 ` James Simmons
2003-04-13 7:41 ` Joshua Kwan
2003-04-15 19:02 ` James Simmons
2003-04-11 18:20 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-04-13 8:17 Antonino Daplas
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=20030411033426.GA13930@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=jsimmons@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.