From: Andreas Tobler <a.tobler@schweiz.ch>
To: linuxppc-dev@lists.linuxppc.org, Andreas Tobler <a.tobler@schweiz.ch>
Subject: ATI-chip in PowerbookG3
Date: Thu, 20 May 1999 15:52:40 +0200 [thread overview]
Message-ID: <374413A8.E8E74F85@schweiz.ch> (raw)
Hello,
I want to find out if my ATI chip is supported by the atyfb driver. The
things I can find are the following:
Powerbook Wallstreet G3 from June 98 250MHz 13.1 TFT 96MB Ram
System Profiler output:
Card Name: ATY,264LT-G
Card Model: ATY,LT-G
Card Rom: 113-XXXXX-1.0028
Card Revision: 128
Card Vendor ID 1002
Slot $E1
When I have a look into the file atyfb.c I see the following:
static struct aty_features {
u16 pci_id;
u16 chip_type;
const char *name;
} aty_features[] __initdata = {
/* mach64GX family */
{ 0x4758, 0x00d7, "mach64GX (ATI888GX00)" },
{ 0x4358, 0x0057, "mach64CX (ATI888CX00)" },
/* mach64CT family */
{ 0x4354, 0x4354, "mach64CT (ATI264CT)" },
{ 0x4554, 0x4554, "mach64ET (ATI264ET)" },
/* mach64CT family / mach64VT class */
{ 0x5654, 0x5654, "mach64VT (ATI264VT)" },
{ 0x5655, 0x5655, "mach64VTB (ATI264VTB)" },
{ 0x5656, 0x5656, "mach64VT4 (ATI264VT4)" },
/* mach64CT family / mach64GT (3D RAGE) class */
{ 0x4c42, 0x4c42, "3D RAGE LT PRO (AGP)" },
{ 0x4c44, 0x4c44, "3D RAGE LT PRO" },
{ 0x4c47, 0x4c47, "3D RAGE LT PRO" },
{ 0x4c49, 0x4c49, "3D RAGE LT PRO" },
{ 0x4c50, 0x4c50, "3D RAGE LT PRO" },
{ 0x4c54, 0x4c54, "3D RAGE LT" },
{ 0x4754, 0x4754, "3D RAGE (GT)" },
{ 0x4755, 0x4755, "3D RAGE II+ (GTB)" },
{ 0x4756, 0x4756, "3D RAGE IIC (PCI)" },
{ 0x4757, 0x4757, "3D RAGE IIC (AGP)" },
{ 0x475a, 0x475a, "3D RAGE IIC (AGP)" },
{ 0x4742, 0x4742, "3D RAGE PRO (BGA, AGP)" },
{ 0x4744, 0x4744, "3D RAGE PRO (BGA, AGP, 1x only)" },
{ 0x4749, 0x4749, "3D RAGE PRO (BGA, PCI)" },
{ 0x4750, 0x4750, "3D RAGE PRO (PQFP, PCI)" },
{ 0x4751, 0x4751, "3D RAGE PRO (PQFP, PCI, limited 3D)" },
};
Sorry for the length..
Which of the devices above corresponds to my PB chip?
My kernels come up with the following message:
MacOS display is /pci/ATY,264LT-G
atyfb: 3D RAGE LT PRO [0x4c47 rev 0x80] 4M SGRAM, 230 MHz PLL, 63 Mhz
MCLK
Console: switching to colour frame buffer device 128x48
fb0: ATY Mach64 frame buffer device on /pci/ATY,264LT-G
The BootX parameters are the following:
video=atyfb:vmode:14,cmode:32,mclk:63
Is this valid? At least for kernels < 2.2.7 it works.
I wouldn't ask if'd trust the situation. I already had two repair trips.
And I don't like a third one.
Thanks for any hint
Andreas
--
| Andreas Tobler
| CH-8004 Zuerich
| E-Mail: andreas.tobler@alcatel.ch | a.tobler@schweiz.ch
-----------------------------------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-05-20 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-20 13:52 Andreas Tobler [this message]
1999-05-25 10:00 ` ATI-chip in PowerbookG3 Geert Uytterhoeven
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=374413A8.E8E74F85@schweiz.ch \
--to=a.tobler@schweiz.ch \
--cc=linuxppc-dev@lists.linuxppc.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).