Will the X1200 be supported?
Hello, I have a MoBo (MSI K9AGM2) with the ATI Radeon X1200 IGP in it. I recently read (on Phoronix) that you have added support for the X1250. Wikipedia says that the X1200 is the X1250 without the HDMI and the stuff like that. So I want to ask; do you plan on adding support for the X1200? I can help with any tests you want me to do. Thanks, Ahmad Yasser (a.k.a. Extreme Coder) -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Nov 20, 07 18:30:58 +0200, Ahmad Yasser wrote:
Hello, I have a MoBo (MSI K9AGM2) with the ATI Radeon X1200 IGP in it. I recently read (on Phoronix) that you have added support for the X1250. Wikipedia says that the X1200 is the X1250 without the HDMI and the stuff like that. So I want to ask; do you plan on adding support for the X1200? I can help with any tests you want me to do.
AFAIK the X1200 should just work. This Phoronix article was FUBAR, the
X1250 actually worked before, I just added the marketing name of the
chip to the list of known cards...
CU
Matthias
--
Matthias Hopf
Matthias Hopf wrote:
On Nov 20, 07 18:30:58 +0200, Ahmad Yasser wrote:
Hello, I have a MoBo (MSI K9AGM2) with the ATI Radeon X1200 IGP in it. I recently read (on Phoronix) that you have added support for the X1250. Wikipedia says that the X1200 is the X1250 without the HDMI and the stuff like that. So I want to ask; do you plan on adding support for the X1200? I can help with any tests you want me to do.
AFAIK the X1200 should just work. This Phoronix article was FUBAR, the X1250 actually worked before, I just added the marketing name of the chip to the list of known cards...
CU
Matthias
Feel free to email me if you're having trouble getting your X1200 to work. I've got an X1270 which is pretty similar. For giggles, can you send me the output of "lspci -n" on that system, I am curious what the PCI ID is for your IGP. Anyhow, I spent a considerable amount of time getting this card working (under FreeBSD), and have an xorg.conf that I posted to the list earlier that seems to be a good starting point for at least one other person. -- Coleman Kane -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Feel free to email me if you're having trouble getting your X1200 to work. I've got an X1270 which is pretty similar. For giggles, can you send me the output of "lspci -n" on that system, I am curious what the PCI ID is for your IGP.
The problem here is that we have three different variants but it looks like we only used two PCI device Ids, so it's pretty much impossible for the driver to put the right name to each chip. In Windows the correct device name is stored in an INF string in the driver builds we make specifically for a customer, so the correct device name is always reported. Generic drivers have an INF string like "X1200 family". The Ids we used are 791E and 791F. The intent was that 791E be desktop and 791F be mobile, but when the "T" variant was introduced it used the same 791F device ID. In theory the naming should be : X1270 - 690T X1250 - 690 / 690M X1200 - 690C / 690MC (these are also called "...V" in some cases)... ... but the device Ids were not assigned along those lines. Now that OEMs are starting to ship preconfigured Linux systems these issues will go away over time. In the meantime a generic 12xx string might not be the worst answer. JB -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Bridgman, John wrote:
Feel free to email me if you're having trouble getting your X1200 to
work. I've got an X1270 which is pretty similar. For giggles, can you send me the output of "lspci -n" on that system, I am curious what the PCI ID is for your IGP.
The problem here is that we have three different variants but it looks like we only used two PCI device Ids, so it's pretty much impossible for the driver to put the right name to each chip. In Windows the correct device name is stored in an INF string in the driver builds we make specifically for a customer, so the correct device name is always reported. Generic drivers have an INF string like "X1200 family".
The Ids we used are 791E and 791F. The intent was that 791E be desktop and 791F be mobile, but when the "T" variant was introduced it used the same 791F device ID.
In theory the naming should be :
X1270 - 690T X1250 - 690 / 690M X1200 - 690C / 690MC (these are also called "...V" in some cases)...
... but the device Ids were not assigned along those lines. Now that OEMs are starting to ship preconfigured Linux systems these issues will go away over time. In the meantime a generic 12xx string might not be the worst answer.
JB
That mates with what I have been reading. What are the actual differences between these chips? I have had trouble tracking this down outside of what people have been posting on Wikipedia and a gaggle of conflicting articles on the subject. -- Coleman Kane -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
That mates with what I have been reading. What are the actual differences between these chips? I have had trouble tracking this down outside of what people have been posting on Wikipedia and a gaggle of conflicting articles on the subject.
I looked at amd.com and it seems we don't use the X12xx names either -- it's just called the 690 (desktop) or 690M (laptop). I guess that's why the device Ids were allocated the way they were. 690V does not have DVI/HDMI out (presumably no TDMS, in other words). I think the "C" suffix means the same thing but not 100% sure. 690 is the standard part 690T adds sideport memory (ie local frame buffer) or DVO. I say "or" because some pins are shared. JB -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
A bit more info -- looks like the 690T is a variant of the mobile part, which means that our ASIC Ids actually make sense (whew ;)). 791E is "690" (desktop) including the "V" or "C" variant without DVI/HDMI http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_14603_1 4764,00.html 791F is "690M" (mobile) including V/C *and* the T variant with sideport/DVO http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_14603_1 4937^14941,00.html JB -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Nov 20, 07 14:19:52 -0500, Bridgman, John wrote:
A bit more info -- looks like the 690T is a variant of the mobile part, which means that our ASIC Ids actually make sense (whew ;)).
791E is "690" (desktop) including the "V" or "C" variant without DVI/HDMI
[...]
Has anybody already told you that ATI's chip numbering scheme is
somewhat... interesting? ;-)
Matthias, getting a little headache about these chip names ^__^
--
Matthias Hopf
On Nov 20, 2007 8:37 PM, Coleman Kane
Bridgman, John wrote:
Feel free to email me if you're having trouble getting your X1200 to
work. I've got an X1270 which is pretty similar. For giggles, can you send me the output of "lspci -n" on that system, I am curious what the PCI ID is for your IGP.
The problem here is that we have three different variants but it looks like we only used two PCI device Ids, so it's pretty much impossible for the driver to put the right name to each chip. In Windows the correct device name is stored in an INF string in the driver builds we make specifically for a customer, so the correct device name is always reported. Generic drivers have an INF string like "X1200 family".
The Ids we used are 791E and 791F. The intent was that 791E be desktop and 791F be mobile, but when the "T" variant was introduced it used the same 791F device ID.
In theory the naming should be :
X1270 - 690T X1250 - 690 / 690M X1200 - 690C / 690MC (these are also called "...V" in some cases)...
... but the device Ids were not assigned along those lines. Now that OEMs are starting to ship preconfigured Linux systems these issues will go away over time. In the meantime a generic 12xx string might not be the worst answer.
JB
That mates with what I have been reading. What are the actual differences between these chips? I have had trouble tracking this down outside of what people have been posting on Wikipedia and a gaggle of conflicting articles on the subject.
-- Coleman Kane
lspci -n: [ahmad@ahmad ~]$ lspci -n 00:00.0 0600: 1002:7910 00:01.0 0604: 1002:7912 00:07.0 0604: 1002:7917 00:12.0 0106: 1002:4380 00:13.0 0c03: 1002:4387 00:13.1 0c03: 1002:4388 00:13.2 0c03: 1002:4389 00:13.3 0c03: 1002:438a 00:13.4 0c03: 1002:438b 00:13.5 0c03: 1002:4386 00:14.0 0c05: 1002:4385 (rev 14) 00:14.1 0101: 1002:438c 00:14.2 0403: 1002:4383 00:14.3 0601: 1002:438d 00:14.4 0604: 1002:4384 00:18.0 0600: 1022:1100 00:18.1 0600: 1022:1101 00:18.2 0600: 1022:1102 00:18.3 0600: 1022:1103 01:05.0 0300: 1002:791e 02:00.0 0200: 10ec:8136 (rev 01) 03:03.0 0200: 10ec:8139 (rev 10) Let me know if you want me to try out radeonhd or if you need the contest output. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Hey everyone,
perhaps we could use the sum of h/w & firmware capabilities to
uniquely identify the card.
Is the VBE bios s/w version different for each variant?
can we probe in software whether the card has an HDMI o/p or not, this
rules out atleast 1 card from the list.
...or something else along these lines ;-)
I have tried putting up a page for accurately describing the 1250
https://groups.google.com/group/x1250/web/ati-radeon-x1250-specifications
(any contributions to that is much appreciated)
-Jojo
On Nov 21, 2007 12:02 AM, Bridgman, John
Feel free to email me if you're having trouble getting your X1200 to work. I've got an X1270 which is pretty similar. For giggles, can you send me the output of "lspci -n" on that system, I am curious what the PCI ID is for your IGP.
The problem here is that we have three different variants but it looks like we only used two PCI device Ids, so it's pretty much impossible for the driver to put the right name to each chip. In Windows the correct device name is stored in an INF string in the driver builds we make specifically for a customer, so the correct device name is always reported. Generic drivers have an INF string like "X1200 family".
The Ids we used are 791E and 791F. The intent was that 791E be desktop and 791F be mobile, but when the "T" variant was introduced it used the same 791F device ID.
In theory the naming should be :
X1270 - 690T X1250 - 690 / 690M X1200 - 690C / 690MC (these are also called "...V" in some cases)...
... but the device Ids were not assigned along those lines. Now that OEMs are starting to ship preconfigured Linux systems these issues will go away over time. In the meantime a generic 12xx string might not be the worst answer.
JB
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Wed, Nov 21, 2007 at 10:13:18AM +0530, onetwo jojo wrote:
Hey everyone,
perhaps we could use the sum of h/w & firmware capabilities to uniquely identify the card. Is the VBE bios s/w version different for each variant?
can we probe in software whether the card has an HDMI o/p or not, this rules out atleast 1 card from the list. ...or something else along these lines ;-)
I have tried putting up a page for accurately describing the 1250 https://groups.google.com/group/x1250/web/ati-radeon-x1250-specifications (any contributions to that is much appreciated)
-Jojo
We can find out whether the hardware has a HDMI or DVI connector from the BIOS. What we cannot do yet is support this, as there were some undocumented changes to this output subsystem, and we are still in the process of acquiring this hardware. Thanks, Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Nov 21, 07 10:13:18 +0530, onetwo jojo wrote:
perhaps we could use the sum of h/w & firmware capabilities to uniquely identify the card.
The issue with that approach is: who will maintain this list? It will be
*large* and *growing*.
Matthias
--
Matthias Hopf
participants (6)
-
Ahmad Yasser -
Bridgman, John -
Coleman Kane -
Luc Verhaegen -
Matthias Hopf -
onetwo jojo