From: Kent Hunt <kenthunt@yahoo.com>
To: lk <linux-kernel@vger.kernel.org>
Subject: 2.4.23 atyfb doesn't work on Presario 1700
Date: Wed, 17 Dec 2003 06:21:13 -0800 (PST) [thread overview]
Message-ID: <20031217142113.65682.qmail@web41104.mail.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
Hi,
I had atyfb working perfectly with stock
kernel 2.4.21 and
perhaps earlier kernels. The reason I don't recall if
it worked with
earlier kernels is because my HD crashed. I cannot
even find out what
was the configuration that made it work.
I cannot make it work with the new atyfb in
2.4.23 either.
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_ATY=y
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FBCON_ADVANCED=y
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
My laptop is a Presario 1700.
01:00.0 VGA compatible controller: ATI Technologies
Inc Rage Mobility P/M AGP 2x (rev 64)
01:00.0 Class 0300: 1002:4c4d (rev 64)
In addition, should this patch be applied? lspci says
I have an AGP and
the id code is 4c4d.
--- linux-2.4.23-acpi/drivers/video/aty/atyfb_base.c
2003-12-14 12:09:09.000000000 -0500
+++
linux-2.4.23-fb/drivers/video/aty/atyfb_base_orig.c
2003-12-13 19:04:06.000000000 -0500
@@ -376,8 +376,8 @@
{ 0x4c50, 0x4c50, 0x00, 0x00, m64n_ltp_p, 230,
100, 100, M64F_GT | M64F_INTEGRATED | M64F_RESET
_3D | M64F_GTB_DSP | M64F_EXTRA_BRIGHT},
/* 3D RAGE Mobility */
- { 0x4c4d, 0x4c4d, 0x00, 0x00, m64n_mob_p, 230,
83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET
_3D | M64F_GTB_DSP | M64F_MOBIL_BUS |
M64F_EXTRA_BRIGHT},
- { 0x4c4e, 0x4c4e, 0x00, 0x00, m64n_mob_a, 230,
83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET
_3D | M64F_GTB_DSP | M64F_MOBIL_BUS |
M64F_EXTRA_BRIGHT},
+ { 0x4c4d, 0x4c4d, 0x00, 0x00, m64n_mob_a, 230,
83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET
_3D | M64F_GTB_DSP | M64F_MOBIL_BUS |
M64F_EXTRA_BRIGHT},
+ { 0x4c4e, 0x4c4e, 0x00, 0x00, m64n_mob_p, 230,
83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET
_3D | M64F_GTB_DSP | M64F_MOBIL_BUS |
M64F_EXTRA_BRIGHT},
#endif /* CONFIG_FB_ATY_CT */
};
Kent
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
[-- Attachment #2: atyfb.txt --]
[-- Type: text/plain, Size: 1972 bytes --]
Hi,
I had atyfb working perfectly with stock kernel 2.4.21 and
perhaps earlier kernels. The reason I don't recall if it worked with
earlier kernels is because my HD crashed. I cannot even find out what
was the configuration that made it work.
I cannot make it work with the new atyfb in 2.4.23 either.
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_ATY=y
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FBCON_ADVANCED=y
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
My laptop is a Presario 1700.
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
01:00.0 Class 0300: 1002:4c4d (rev 64)
In addition, should this patch be applied? lspci says I have an AGP and
the id code is 4c4d.
--- linux-2.4.23-acpi/drivers/video/aty/atyfb_base.c 2003-12-14 12:09:09.000000000 -0500
+++ linux-2.4.23-fb/drivers/video/aty/atyfb_base_orig.c 2003-12-13 19:04:06.000000000 -0500
@@ -376,8 +376,8 @@
{ 0x4c50, 0x4c50, 0x00, 0x00, m64n_ltp_p, 230, 100, 100, M64F_GT | M64F_INTEGRATED | M64F_RESET_3D | M64F_GTB_DSP | M64F_EXTRA_BRIGHT},
/* 3D RAGE Mobility */
- { 0x4c4d, 0x4c4d, 0x00, 0x00, m64n_mob_p, 230, 83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET_3D | M64F_GTB_DSP | M64F_MOBIL_BUS | M64F_EXTRA_BRIGHT},
- { 0x4c4e, 0x4c4e, 0x00, 0x00, m64n_mob_a, 230, 83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET_3D | M64F_GTB_DSP | M64F_MOBIL_BUS | M64F_EXTRA_BRIGHT},
+ { 0x4c4d, 0x4c4d, 0x00, 0x00, m64n_mob_a, 230, 83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET_3D | M64F_GTB_DSP | M64F_MOBIL_BUS | M64F_EXTRA_BRIGHT},
+ { 0x4c4e, 0x4c4e, 0x00, 0x00, m64n_mob_p, 230, 83, 125, M64F_GT | M64F_INTEGRATED | M64F_RESET_3D | M64F_GTB_DSP | M64F_MOBIL_BUS | M64F_EXTRA_BRIGHT},
#endif /* CONFIG_FB_ATY_CT */
};
reply other threads:[~2003-12-17 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031217142113.65682.qmail@web41104.mail.yahoo.com \
--to=kenthunt@yahoo.com \
--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
Powered by JetHome