[Dri-devel] Problems with ATI Rage Mobility M1 under XFree86DRI from CVS
I recently installed Xfree86 4.2.1, and had a little trouble with the screen not displaying anything that looked very much like x windows. There was a problem with my setup, and I had to add the option option "LCDSync" to the devices section of my XF86Config This solved my problem, and I was happily using X, until I decided that I wanted to add DRI support. Now I have the same problem again, (e.g the screen displays the same sort of crap when I load X) but the LCDSync option seems to have no effect. any Ideas why? Thanks Giles Here is my XF86Config: Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Mouse1" "AlwaysCore" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/TTF" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/100dpi" FontPath "/usr/X11R6/lib/X11/fonts/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/local" FontPath "/usr/X11R6/lib/X11/fonts/CID" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" EndSection Section "Module" Load "freetype" Load "extmod" Load "glx" Load "dri" Load "dbe" Load "record" Load "xtrap" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbModel" "pc104" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/misc/psaux" EndSection Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/input/mice" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "accel" # [] #Option "crt_screen"# [] #Option "composite_sync"# [] #Option "linear"# [] #Option "mmio_cache"# [] #Option "probe_clocks" # [] #Option "reference_clock" # #Option "shadow_fb" # [] Identifier "Card0" Driver "ati" VendorName "ATI" BoardName "Mach64 LM" ChipSet "ati" ChipId 0x4c4d ChipRev 0x64 Option "LCDSync" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection Section "DRI" Mode 0666 EndSection --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Radeon 8500 LE bombs out
Radeon 8500 LE (Built by ATI) can't do 1600x1200 on a ViewSoncic A90. The Radeon 7500 can. I placed a bugzilla item at http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=79501 Please fix. Thanks, Frank --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Update on MGA vblank IRQ strangeness
On Fri, Jan 03, 2003 at 03:41:00AM +0200, Ville Syrjälä wrote: > On Thu, Jan 02, 2003 at 04:02:12PM -0800, Ian Romanick wrote: > > So, I've done some more tinkering with the vblank IRQ on the G400. By > > putting debug messages in a few places I managed to determine that > > interrupts are not happening. > > Is the linecomp register programmed correctly? I just had look at the source and it doesn't look right. Perhaps I'm missing something but it looks like the linecomp is programmed as follows: bit 10 = 0 bits 8-9 = 1 bits 0-7 = vertical display end lower 8 bits This should put the linecomp value somewhere between 768 and 1023. So I don't understand why modes with vdispend > 1023 aren't split in two like they should be. And vline interrupts should be generated too. If bit 10 was 1 I'd understand the current situation but now I'm just confused. Any ideas? I've attached a completely untested patch which should fix the linecomp value. -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ --- mga_dacG.c Fri Jan 3 18:23:49 2003 +++ mga_dacG.c Fri Jan 3 18:30:23 2003 @@ -479,7 +479,9 @@ pReg->ExtVga[2] = ((vt & 0xc00) >> 10) | ((vd & 0x400) >> 8) | ((vd & 0xc00) >> 7) | - ((vs & 0xc00) >> 5); + ((vs & 0xc00) >> 5) | + ((vd & 0x400) >> 3); + if (pLayout->bitsPerPixel == 24) pReg->ExtVga[3] = (((1 << BppShift) * 3) - 1) | 0x80; else @@ -498,11 +500,11 @@ ((vd & 0x100) >> 7 ) | ((vs & 0x100) >> 6 ) | ((vd & 0x100) >> 5 ) | - 0x10 | + ((vd & 0x100) >> 4 ) | ((vt & 0x200) >> 4 ) | ((vd & 0x200) >> 3 ) | ((vs & 0x200) >> 2 ); - pVga->CRTC[9] = ((vd & 0x200) >> 4) | 0x40; + pVga->CRTC[9] = ((vd & 0x200) >> 4) | ((vd & 0x200) >> 3); pVga->CRTC[16] = vs & 0xFF; pVga->CRTC[17] = (ve & 0x0F) | 0x20; pVga->CRTC[18] = vd & 0xFF;
Re: [Dri-devel] Re: [Mesa3d-dev] Direct3D driver for Mesa?
On Fri, 2003-01-03 at 15:39, Ian Romanick wrote: > There's actually probably more general interest in the stereo support > than in the Direct3D support. It would take very little to modify the > Radeon, R200, Rage128, and G400 drivers to support switching between > left and right display buffers each refresh. The main missing part is, > well, everything else. :) You need to make sure you are drawing the 2D world into both buffers obviously, and persuade Mesa to handle that and also perhaps interlace. Most of the low end 3D glasses stuff "just works".Some like the Eye-3D need magic patterns displaying during the mode switch to control the glasses setup, but I have some of them figured out and its not hard to capture the output of windows switching glasses mode to deduce the others Alan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: [Mesa3d-dev] Direct3D driver for Mesa?
Kendall Bennett wrote: That would be great Kendall. I'd certainly have an interest in it. Is there any interest in the stereo stuff, or just the Direct3D drivers? There's actually probably more general interest in the stereo support than in the Direct3D support. It would take very little to modify the Radeon, R200, Rage128, and G400 drivers to support switching between left and right display buffers each refresh. The main missing part is, well, everything else. :) It is very nice to see more and more companies opening up legacy (for lack of a better word) code bases to the community. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
