[Xpert]ATI Radeon patch testing
I've just checked in the latest patch from ATI. Here's the CHANGELOG entry: 390. Rewrite Radeon DDC/DFP mode detection and management (Kevin Martin). 389. Integrate ATI patch: - Add 2D support for Radeon 9000 (RV250), Mobility M9 (RV250 mobile) and Radeon 9700 (R300) - Clone mode fixes and improvements - Dell VE card fixes - Dual-head VT switching fixes - General code clean up (#A.1217, Hui Yu@ATI). All tests were run on x86 Linux-based systems. I'd like get some feedback on how it works for others with both desktop and laptop Radeons. I've tested this patch on the following cards: Radeon R100 Radeon VE Radeon VE (DELL OEM version) Radeon 7500 Radeon 8500 LE Radeon 9000 Radeon M9 (sample board) Radeon 9700 The cards that I don't have are: Radeon 8500 M6 laptops M7 laptops M9 laptops If you run into any problems, please report them here on Xpert. Thanks, Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 12 Jul 2002, Dr. Andrew C. Aitchison wrote: This breaks DDC on my white box Radeon 7000. Patch to fix this attached. lspci -v -n 01:00.0 Class 0300: 1002:5159 Subsystem: 174b:7112 ... http://www.pcisig.com/membership/vid_search/by_vendor_id/?vendor_id=174btyp e=h suggests that 174b is PC Partner. http://www.pcpartner.com/product-ATI.html suggests they make motherboards wth onchip ATI graphics. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna Hi, Just got a chance to try the latest CVS code, I noticed above patch is in the CVS. However, this patch breaks the DELL VE card detection (at least on my DELL's card). The subsystem vender ID of my DELL VE card is 0x1002 (ATI's ID) and the bit 12 of subsystem card ID is reserved for DELL. It appears some OEMs do not follow this rule. In my next patch, if no other issue, I'll change it to test ATI's ID instead of DELL's ID. Hui ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
I've been thinking about this and it's not clear to me if or how we could determine which is the primary display. If we can't, it wouldn't be all too useful. In current dual-head mapping scheme, DVI port is always treated as the primary head (first screen, using CRTC) if a monitor (whether a CRT or a FP) is connected there. This is inherited from the earlier M6 laptop support. Under this scheme, you can try DDC_DVI type first. If something is detected there, use it as the primary display, And then try DDC_VGA, DDC_CRT2, BIOS settings in turn for the 2nd display. If DDC_DVI fails, try to look at the BIOS settings (assuming bios can be accessed) to make sure there is nothing connected (a lot of laptop panels do not support DDC). If indeed there is nothing connected, then you can try DDC_VGA, DDC_CRT2 and BIOS settings in turn to determine the primary display. This should work with all existing cards AFAIK. Another possibility would be falling back to defaults for display and DDC type based on chip ID etc. That (and maybe options to override them) should do for laptops without a BIOS, for which I consider this most important. Chip ID doesn't reflect actual connector types and DDC types used, especially when more and more OEM cards are out there. Not sure if there will be some OEM cards for which above scheme doesn't work and we have to add an option. Hui -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 11 Jul 2002, Kevin E Martin wrote: I've just checked in a large patch from ATI. Here's the CHANGELOG entry: 199. ATI patch to: - Fix Dell OEM VE card support - Add better clone mode support - Fix large panel (= 1600x1200) detection and initialization problems - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support - Add DDCMode option to detect and use DDC modes - Add PanelOff option to disable panel on laptops - Fix corrupted console problem - Other misc fixes (#A.1043, Hui Yu@ATI). I'd like get some feedback on how it works for others with both desktop and laptop Radeons. Well, I've been testing the 20020712 CVS snapshot (which includes this patch). I haven't noticed any problems on either my 8500 or my Mobility M6 LY. I don't have access to the 64 DDR at the moment, but I'll test it there as soon as I can. Note that I have *not* experimented with any of the new features, so I can't give much input as to how they work. All I can say is that the patch doesn't seem to break anything as far as I can tell. ;) I'll start working on the other patches that have been sent in shortly. The copy of Michel Dänzer's HARDWARE_CLIP_SCREEN_TO_SCREEN_COPY patch which I merged against the 2002-07-01 snapshot still applies cleanly (with only a slight amount of fuzz). But I haven't tested to see if it will compile cleanly and run. I will do that hopefully sometime within the next few days... On another topic--are the comments in the source code the only documentation for the radeon driver? (I'd be willing to take a crack at writing a man page for the radeon driver, but if the only documentation is the source, it's gonna have a lot of FIXMEs in the first attempt...) -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Wed, 2002-07-17 at 08:58, James Ralston wrote: On another topic--are the comments in the source code the only documentation for the radeon driver? At least I'm not aware of anything else. (I'd be willing to take a crack at writing a man page for the radeon driver, Great! That's very much appreciated. While you're at it, please also add the documentation for options to programs/Xserver/hw/xfree86/Options, which can be used by configuration tools like xf86cfg. but if the only documentation is the source, it's gonna have a lot of FIXMEs in the first attempt...) Why don't you start with something, and we can help you fill in the missing bits. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
The combination of two methods will make the auto-detection more reliable. Sounds promising. Will you do that anyway, or should I look into it? Meanwhile I don't have much time on this. Go ahead to do it if you have time, I'll be glad to help if you need any more information. One thing I was a little worried about is that enumerating through all 4 DDC types can be slow. In order for DDC detection working with some old panels, I have to use several delays in DoDDC routine which makes it kind of slow. You probably can ignore DDC_MONID type, I haven't seen it ever being used. Hui ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Mon, 2002-07-15 at 06:40, hy0 wrote: Not every machine has a BIOS. In that case, there are a few more things (in addition to panel size) we need to worry about before it can work reliably. Things like PLL ref clock, display type ... are all derived from video BIOS image. Yes, I see now that the panel parameters should be less of a problem if the display type is known. Is the DDC detection OK? No, because we don't have a way to determine the display type yet (do you happen to know a way which doesn't require a BIOS?). If I hardcode info-DisplayType = MT_LCD; info-DDCType = DDC_DVI; DDC works (nice!), but there's still the same flicker. Option DDCModes isn't used, but I assume not providing any Modes is mostly the same. I took a shortcut in determining the display type -- thru video BIOS settings. It works in most of cases, but not really reliable as seen in your case (I have comments on this inside the code, I think). A more proper way to enumerate through all DDC types and probe potential connected monitors. Once you have EDID data, you can derive its display type. This should work in your case. But, in general, you cannot conclude there is no display connected if the DDC detection fails. A lot of laptop panels simply are not DDC capable, the panel info is hardcoded into the BIOS image (this may not apply to you). Works fine here, and I think it should work with all Apple laptops equipped with a Radeon. But that doesn't say anything about desktops of course. The combination of two methods will make the auto-detection more reliable. Sounds promising. Will you do that anyway, or should I look into it? As for the flicker problem, maybe you can print out all PLL parameters and CRTC settings used by driver and compare them with the settings used for FBDev. If the driver cannot access BIOS, it'll use the hardcoded PLL parameters, I'm not sure if they are correct in your case. Probably not. I just talked to Ani Joshi on IRC, he's going to integrate PLL probing code. With that and display type detection from DDC, things should be looking great. :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 2002-07-11 at 22:27, Kevin E Martin wrote: I've just checked in a large patch from ATI. Here's the CHANGELOG entry: 199. ATI patch to: - Fix Dell OEM VE card support - Add better clone mode support - Fix large panel (= 1600x1200) detection and initialization problems - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support Hmm, with XF86-4.2 I had to use CrtScreen to get a display, now I had to set: Option CloneDisplay 1 Is that the intended way to do it? Without either one, I don't get a display on my CRT (which is my only monitor, somehow the card thinks I have a flat panel which I don't have). Nils -- Nils Philippsen / Berliner Straße 39 / D-71229 Leonberg // +49.7152.209647 [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] Ever noticed that common sense isn't really all that common? signature.asc Description: This is a digitally signed message part
Re: [Xpert]ATI Radeon patch testing
On Sun, 2002-07-14 at 13:57, hy0 wrote: On Thu, 2002-07-11 at 22:27, Kevin E Martin wrote: I've just checked in a large patch from ATI. Here's the CHANGELOG entry: 199. ATI patch to: - Fix Dell OEM VE card support - Add better clone mode support - Fix large panel (= 1600x1200) detection and initialization problems - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support At least Option PanelSize would still be useful for systems where we can't determine the panel parameters yet. Current Radeon driver supports two kinds of panel: TMDS panel (usually used for desktop, named as DFP in the driver for some legacy reason) and LVDS panel (usually used for laptop, named as LCD in the driver). The TMDS panels should be DDC capable, if not, the BIOS won't even be able to bring them up to text mode. For this kind of panel, the radeon driver will try to do DDC detection first. If it fails for some reason, the driver will used EDID data detected by BIOS. With the DDC info, the driver can figure out the panel size and bring it up automatically. The laptop (LVDS) panels usually are not DDC capable (some new ones are). The panel size and timing information are hard coded into video BIOS and radeon driver will use it to bring the panel up. The only potential problem here is that some custom version of BIOS doesn't follow the rule and put the panel info to a different place. I haven't come across such a laptop yet and would like to know if someone has one. Not every machine has a BIOS. Only knowing panel size (together with VESA timings) usually is not good enough to bring a LVDS panel up properly. Even with the correct modeline, it's better to know other things (like power delay) to safely turn the panel on/off. Let user to specify panel size can be error prone. Anyway, if there are people out there really requiring this option, I can put it back. I think it's still needed as a fallback until automatic detection truly works everywhere. Which might not be far away though, more below... As for non-native modes (resolution lower than panel size), by default, radeon driver will use the internal ratio matrix expansion (RMX) unit to scale the display down. It works not only for all standard VESA modes, it'll work also for any mode between 320x200 and panel size, for example 600x500. That was just an example why using virtual resolution as panel size doesn't work in general. - Add DDCMode option to detect and use DDC modes - Add PanelOff option to disable panel on laptops - Fix corrupted console problem - Other misc fixes (#A.1043, Hui Yu@ATI). I'd like get some feedback on how it works for others with both desktop and laptop Radeons. Doesn't quite work on a Titanium PowerBook III (without Option UseFBDev, with a 1280x854 modeline obtained by radeonfb via EDID which works fine with that option). There are flickering lines on the right side. Is the DDC detection OK? No, because we don't have a way to determine the display type yet (do you happen to know a way which doesn't require a BIOS?). If I hardcode info-DisplayType = MT_LCD; info-DDCType = DDC_DVI; DDC works (nice!), but there's still the same flicker. Option DDCModes isn't used, but I assume not providing any Modes is mostly the same. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
PanelSize CrtScreen CloneDisplay CloneMode What are all theese options ? In what section are they used ? Can you give me a sample XF86config and a link to the convenient documentation - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support Hmm, with XF86-4.2 I had to use CrtScreen to get a display, now I had to set: Option CloneDisplay 1 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
Not every machine has a BIOS. In that case, there are a few more things (in addition to panel size) we need to worry about before it can work reliably. Things like PLL ref clock, display type ... are all derived from video BIOS image. As for non-native modes (resolution lower than panel size), by default, radeon driver will use the internal ratio matrix expansion (RMX) unit to scale the display down. It works not only for all standard VESA modes, it'll work also for any mode between 320x200 and panel size, for example 600x500. That was just an example why using virtual resolution as panel size doesn't work in general. Virtual resolution should not be used as panel size, it never has. Is the DDC detection OK? No, because we don't have a way to determine the display type yet (do you happen to know a way which doesn't require a BIOS?). If I hardcode info-DisplayType = MT_LCD; info-DDCType = DDC_DVI; DDC works (nice!), but there's still the same flicker. Option DDCModes isn't used, but I assume not providing any Modes is mostly the same. I took a shortcut in determining the display type -- thru video BIOS settings. It works in most of cases, but not really reliable as seen in your case (I have comments on this inside the code, I think). A more proper way to enumerate through all DDC types and probe potential connected monitors. Once you have EDID data, you can derive its display type. This should work in your case. But, in general, you cannot conclude there is no display connected if the DDC detection fails. A lot of laptop panels simply are not DDC capable, the panel info is hardcoded into the BIOS image (this may not apply to you). The combination of two methods will make the auto-detection more reliable. As for the flicker problem, maybe you can print out all PLL parameters and CRTC settings used by driver and compare them with the settings used for FBDev. If the driver cannot access BIOS, it'll use the hardcoded PLL parameters, I'm not sure if they are correct in your case. Hui ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
Hmm, with XF86-4.2 I had to use CrtScreen to get a display, now I had to set: Option CloneDisplay 1 Is that the intended way to do it? Yes. This option is supposed to be on by default. Since that part of code is not well tested, it's default off for now. Anyone who wants to mirror the 2nd display should turn on this option. Without either one, I don't get a display on my CRT (which is my only monitor, somehow the card thinks I have a flat panel which I don't have). It's strange. Are you using one of mibile cards (M6/M7)? From what I know, only mobile cards for internal qualification behave like this. The retail mobile cards are usually built into a laptop which has a LCD connected. Hui ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 2002-07-11 at 22:27, Kevin E Martin wrote: I've just checked in a large patch from ATI. Here's the CHANGELOG entry: 199. ATI patch to: - Fix Dell OEM VE card support - Add better clone mode support - Fix large panel (= 1600x1200) detection and initialization problems - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support At least Option PanelSize would still be useful for systems where we can't determine the panel parameters yet. - Add DDCMode option to detect and use DDC modes - Add PanelOff option to disable panel on laptops - Fix corrupted console problem - Other misc fixes (#A.1043, Hui Yu@ATI). I'd like get some feedback on how it works for others with both desktop and laptop Radeons. Doesn't quite work on a Titanium PowerBook III (without Option UseFBDev, with a 1280x854 modeline obtained by radeonfb via EDID which works fine with that option). There are flickering lines on the right side. Also, I think it would be nice if the radeon driver was better documented, in a manpage and/or programs/Xserver/hw/xfree86/Options. I don't know what the Clone options are for even after a quick look through the code, how is an end user supposed to know? I'll start working on the other patches that have been sent in shortly. Great, thanks. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On 07/13/02 18:33, Michel Dänzer wrote: On Thu, 2002-07-11 at 22:27, Kevin E Martin wrote: - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support At least Option PanelSize would still be useful for systems where we can't determine the panel parameters yet. From my very short testing, it appears this is not required. It will now pickup the size from the Mode clause in the Screen section. I assume -configure will write out the panel size into the generated Screen section. ~mc ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Sat, 2002-07-13 at 15:45, Michael Clark wrote: On 07/13/02 18:33, Michel Dänzer wrote: On Thu, 2002-07-11 at 22:27, Kevin E Martin wrote: - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support At least Option PanelSize would still be useful for systems where we can't determine the panel parameters yet. From my very short testing, it appears this is not required. It will now pickup the size from the Mode clause in the Screen section. I see, it just seems to set the scaling ratios to 1.0. That wouldn't be bad (if this panel's native mode actually worked), but e.g. someone might want to run at a virtual resolution lower than the panel size, ... I assume -configure will write out the panel size into the generated Screen section. How, if it can't determine it? PS: I don't want so be too negative though. The new code looks very well written and documented, and the new features sound exciting. I'm just worried about leaving behind 'non-standard' systems. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On 07/13/02 22:48, Michel Dänzer wrote: On Sat, 2002-07-13 at 15:45, Michael Clark wrote: I assume -configure will write out the panel size into the generated Screen section. How, if it can't determine it? Probably what I meant was if it could detect it and that the size detection is now done/used at configuration time, not runtime ie. it is not required now to know the panel size at runtime. (ie. before hand X would choke and exit if it couldn't find it, but now it will proceed and choose a default res). For instance, my panel (which before hand was autodetected and required no Mode or PanelSize) comes up at a different default resolution (640x480 I think) until I added a Mode Subsection to my Screen. I've gone back to 4.2 due to other problems (not being able to run gnome2 due to library problems). ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 11 Jul 2002, I wrote: On Thu, 11 Jul 2002, Kevin E Martin wrote: I've just checked in a large patch from ATI. I'd like get some feedback on how it works for others with both desktop and laptop Radeons. I'll start working on the other patches that have been sent in shortly. I'll rebuild from CVS tonight, and start testing late tonight / tomorrow. Alas, the CVS tree isn't currently in a compilable state: In file included from fcint.h:33, from fclang.c:25: /usr/include/unistd.h:966: warning: redundant redeclaration of `ctermid' in same scope /usr/include/stdio.h:585: warning: previous declaration of `ctermid' fclang.c:32:31: ../fc-lang/fclang.h: No such file or directory fclang.c: In function `FcFreeTypeSetLang': fclang.c:48: `fcLangCharSets' undeclared (first use in this function) fclang.c: In function `FcCharSetForLang': fclang.c:142: `fcLangCharSets' undeclared (first use in this function) fclang.c:157: warning: control reaches end of non-void function make: *** [fclang.o] Error 1 I'll try again once Keith has stabilized the lib/fontconfig tree a bit more... James ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 11 Jul 2002, Kevin E Martin wrote:
I've just checked in a large patch from ATI. Here's the CHANGELOG
entry:
199. ATI patch to:
- Fix Dell OEM VE card support
- Add better clone mode support
- Fix large panel (= 1600x1200) detection and initialization problems
- Remove PanelSize and CrtScreen options since they are no longer
needed with new CloneMode and improved flat panel support
- Add DDCMode option to detect and use DDC modes
- Add PanelOff option to disable panel on laptops
- Fix corrupted console problem
- Other misc fixes
(#A.1043, Hui Yu@ATI).
I'd like get some feedback on how it works for others with both desktop
and laptop Radeons. I'll start working on the other patches that have
been sent in shortly.
This breaks DDC on my white box Radeon 7000.
Patch to fix this attached.
lspci -v -n
01:00.0 Class 0300: 1002:5159
Subsystem: 174b:7112
...
http://www.pcisig.com/membership/vid_search/by_vendor_id/?vendor_id=174btype=h
suggests that 174b is PC Partner.
http://www.pcpartner.com/product-ATI.html
suggests they make motherboards wth onchip ATI graphics.
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna
Index: radeon_driver.c
===
RCS file:
/home/CVS/XFree86/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
retrieving revision 1.58
diff -u -r1.58 radeon_driver.c
--- radeon_driver.c 2002/07/11 20:11:51 1.58
+++ radeon_driver.c 2002/07/12 11:46:37
@@ -1240,7 +1240,8 @@
* It needs some special handlings for it's 2nd head to work.
*/
info-IsDell = FALSE;
-if (info-PciInfo-subsysCard (1 12)) { /* DELL's signature */
+if (info-PciInfo-subsysVendor == PCI_VENDOR_DELL
+ info-PciInfo-subsysCard (1 12)) { /* DELL's signature */
if (info-PciInfo-subsysCard 0xb00) {
info-IsDell = TRUE;
info-DellType = 2; /* DVI+DVI config, this seems to be the
Index: xf86PciInfo.h
===
RCS file: /home/CVS/XFree86/xc/programs/Xserver/hw/xfree86/common/xf86PciInfo.h,v
retrieving revision 1.128
diff -u -r1.128 xf86PciInfo.h
--- xf86PciInfo.h 2002/06/30 15:55:26 1.128
+++ xf86PciInfo.h 2002/07/12 11:43:53
@@ -63,6 +63,7 @@
#define PCI_VENDOR_AMD 0x1022
#define PCI_VENDOR_TRIDENT 0x1023
#define PCI_VENDOR_ALI 0x1025
+#define PCI_VENDOR_DELL0x1028
#define PCI_VENDOR_MATROX 0x102B
#define PCI_VENDOR_CHIPSTECH 0x102C
#define PCI_VENDOR_MIRO0x1031
@@ -154,6 +155,7 @@
#define PCI_VENDOR_NVIDIA_SGS 0x12d2
#define PCI_VENDOR_NETGEAR 0x1385
#define PCI_VENDOR_VMWARE 0x15AD
+#define PCI_VENDOR_PCPARTNER 0x174B
#define PCI_VENDOR_SYMPHONY0x1C1C
#define PCI_VENDOR_TEKRAM_20x1DE1
#define PCI_VENDOR_3DLABS 0x3D3D
Re: [Xpert]ATI Radeon patch testing
Mostly works on my laptop: Compaq Evo N600c, using Radeon Mobility M6 LY (rev 0), under Linux RH 7.2, running a 2.4.18 kernel. I note two problems (both existing before this patch, so this is old news): o If I switch to a different VT, after a few seconds, the machine hard hangs. o When logging out from Gnome, the logout dialog screen is funny, with two vertical black bars from the edge of the dialog box. I've not tried playing with DRI (which is disabled in my XF86Config-4 file. - Jim Sender: [EMAIL PROTECTED] From: Kevin E Martin [EMAIL PROTECTED] Date: Thu, 11 Jul 2002 16:27:40 -0400 To: [EMAIL PROTECTED] Subject: [Xpert]ATI Radeon patch testing - I've just checked in a large patch from ATI. Here's the CHANGELOG entry: 199. ATI patch to: - Fix Dell OEM VE card support - Add better clone mode support - Fix large panel (= 1600x1200) detection and initialization problems - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support - Add DDCMode option to detect and use DDC modes - Add PanelOff option to disable panel on laptops - Fix corrupted console problem - Other misc fixes (#A.1043, Hui Yu@ATI). I'd like get some feedback on how it works for others with both desktop and laptop Radeons. I'll start working on the other patches that have been sent in shortly. Thanks, Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert -- Jim Gettys Cambridge Research Laboratory HP Labs, Hewlett-Packard Company [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]ATI Radeon patch testing
I've just checked in a large patch from ATI. Here's the CHANGELOG entry: 199. ATI patch to: - Fix Dell OEM VE card support - Add better clone mode support - Fix large panel (= 1600x1200) detection and initialization problems - Remove PanelSize and CrtScreen options since they are no longer needed with new CloneMode and improved flat panel support - Add DDCMode option to detect and use DDC modes - Add PanelOff option to disable panel on laptops - Fix corrupted console problem - Other misc fixes (#A.1043, Hui Yu@ATI). I'd like get some feedback on how it works for others with both desktop and laptop Radeons. I'll start working on the other patches that have been sent in shortly. Thanks, Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon patch testing
On Thu, 11 Jul 2002, Kevin E Martin wrote: I've just checked in a large patch from ATI. I'd like get some feedback on how it works for others with both desktop and laptop Radeons. I'll start working on the other patches that have been sent in shortly. I'll rebuild from CVS tonight, and start testing late tonight / tomorrow. Thanks for your efforts! James ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
