From: Johann Hanne <jhanne@gmx.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [patch] triviial: add PCI id to atyfb
Date: Thu, 25 Dec 2003 19:13:07 +0100 [thread overview]
Message-ID: <200312251913.07445.jhanne@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
Hi,
the PCI id in this patch is used on an HP NetServer LH3000, where I've also
successfully tested it.
00:07.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC (rev 7a)
00:07.0 Class 0300: 1002:4759 (rev 7a)
Cheers, Johann
[-- Attachment #2: patch-2.4.23-kzviati --]
[-- Type: text/x-diff, Size: 1155 bytes --]
diff -uNr linux-2.4.23/drivers/video/aty/atyfb_base.c linux-2.4.23-kzviati/drivers/video/aty/atyfb_base.c
--- linux-2.4.23/drivers/video/aty/atyfb_base.c 2003-12-17 14:07:39.000000000 +0100
+++ linux-2.4.23-kzviati/drivers/video/aty/atyfb_base.c 2003-12-17 14:11:20.000000000 +0100
@@ -353,6 +353,7 @@
{ 0x4755, 0x4755, 0x00, 0x00, m64n_gtb, 200, 67, 67, M64F_GT | M64F_INTEGRATED | M64F_GTB_DSP | M64F_FIFO_24 | M64F_SDRAM_MAGIC_PLL | M64F_EXTRA_BRIGHT },
{ 0x4756, 0x4756, 0x00, 0x00, m64n_iic_p, 230, 83, 83, M64F_GT | M64F_INTEGRATED | M64F_GTB_DSP | M64F_FIFO_24 | M64F_SDRAM_MAGIC_PLL | M64F_EXTRA_BRIGHT },
{ 0x4757, 0x4757, 0x00, 0x00, m64n_iic_a, 230, 83, 83, M64F_GT | M64F_INTEGRATED | M64F_GTB_DSP | M64F_FIFO_24 | M64F_SDRAM_MAGIC_PLL | M64F_EXTRA_BRIGHT },
+ { 0x4759, 0x4759, 0x00, 0x00, m64n_iic_p, 230, 83, 83, M64F_GT | M64F_INTEGRATED | M64F_GTB_DSP | M64F_FIFO_24 | M64F_SDRAM_MAGIC_PLL | M64F_EXTRA_BRIGHT },
{ 0x475a, 0x475a, 0x00, 0x00, m64n_iic_a, 230, 83, 83, M64F_GT | M64F_INTEGRATED | M64F_GTB_DSP | M64F_FIFO_24 | M64F_SDRAM_MAGIC_PLL | M64F_EXTRA_BRIGHT },
/* Mach64 LT */
next reply other threads:[~2003-12-25 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 18:13 Johann Hanne [this message]
2004-01-06 22:58 ` [patch] triviial: add PCI id to atyfb James Simmons
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=200312251913.07445.jhanne@gmx.de \
--to=jhanne@gmx.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).