summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Added debug code (currently disabled)wonderland-devDeron2007-06-041-0/+283
|
* Add dix extensionDeron2007-06-041-0/+13
|
* Modify existing files in branch.Deron2007-06-044-0/+146
|
* Add more files to branch.Deron2007-06-048-0/+2954
|
* New file in branch.Deron2007-06-041-0/+2215
|
* Disable use of xf86RandR12TellChanged when unavailable (1.2 server).Keith Packard2007-04-211-0/+2
| | | | | When building the new mode setting code out-of-tree against an older server, don't use xf86RandR12TellChanged as that is a RandR 1.2 specific interface.
* Update version to 1.3.0.0xorg-server-1.3.0.0Keith Packard2007-04-191-5/+5
|
* Disable SourceValidate in rotation to capture cursor.Keith Packard2007-04-191-2/+13
| | | | | | | | SourceValidate is used exclusively by the software cursor code to pull the cursor off of the screen before using the screen as a source operand. This eliminates the software cursor from the frame buffer while painting the rotated image though. Disabling this function by temporarily setting the screen function pointer to NULL causes the cursor image to be captured.
* Was accidentally disabling rotation updates in mode set.Keith Packard2007-04-191-2/+3
| | | | | | Setting a mode on an unrotated CRTC was causing all of the rotation updates to be disabled; the loop looking for active rotation wasn't actually looking at each crtc, it was looking at the modified crtc many times.
* Syncmaster 226 monitor needs 60Hz refresh (#10545).Erik Andrén2007-04-171-0/+5
| | | | | | | | | | | | | | I've managed to solve my own bug (#10545) by applying the following patch to the xserver. Please apply. <Conspiracy mode on> This monitor is "Vista Certified". I wonder if this is a pure coincidence... <Conspiracy mode off> With kind regards Erik Andrén
* Allow outputs to be explicitly enabled in config, overriding detect.Keith Packard2007-04-161-10/+35
| | | | | | | Option "Enable" "True" will force the server to enable an output at startup time, even if the output is not connected. This also causes the default modes to be added for this output, allowing even sync ranges to be used to pick out standard modes.
* Use default screen monitor for one of the outputs.Keith Packard2007-04-162-4/+39
| | | | | | By default, use the screen monitor section for output 0, however, a driver can change which output gets the screen monitor by calling xf86OutputUseScreenMonitor.
* typo in built-in module log messageKeith Packard2007-04-161-1/+1
|
* RandR 1.2 spec says CRTC info contains screen-relative geometry.Keith Packard2007-04-151-2/+4
| | | | Was reporting mode size instead of adjusting for rotation.
* Add quirk for Acer AL1706 monitor to force 60hz refresh.Keith Packard2007-04-131-0/+5
| | | | | | This Acer monitor reports support for 75hz refresh via EDID, and yet when that rate is delivered, the monitor does not sync and reports out of range. Use the existing 60hz quirk for this monitor.
* Rotate screen size as needed from RandR 1.1 change requests.Keith Packard2007-04-091-3/+10
| | | | | Screen size must reflect rotated mode size when setting rotated mode using RandR 1.1 SetScreenConfig request.
* Disable CRTC when SetSingleMode has no matching mode. Update RandR as well.Keith Packard2007-04-093-2/+31
| | | | | | | | | xf86SetSingleMode tries to resize all crtcs to match the selected mode. When a CRTC has no matching mode, it now disables the CRTC (instead of crashing). Also, poke the RandR extension when xf86SetSingleMode is done so that appropriate events can be delivered, and so that future RandR queries return correct information.
* In AIGLX EnterVT processing, invoke driver EnterVT before resuming glx.Keith Packard2007-04-091-1/+5
| | | | | | | As the driver EnterVT function generally re-enables the hardware and prepares it for rendering, it must be called before any gl functions are called which could touch the hardware. (cherry picked from commit f24391dbfd12a84253dfec794ee7884afd52e197)
* Bump to version 1.2.99.905 (1.3 RC5)xorg-server-1.2.99.905Keith Packard2007-04-051-2/+2
|
* CVE-2007-1003: XC-MISC Extension ProcXCMiscGetXIDList() Memory CorruptionMatthieu Herrb2007-04-051-2/+11
| | | | (cherry picked from commit 645d87cf8ef724d4591614f9994cdc4d7549a7a8)
* Bug #10296: Fix timer rescheduling.Tomas Janousek2007-04-051-3/+6
| | | | (cherry picked from commit 8c7f56d92d8471ee059c14d322af5f7f555dd5c6)
* Bump version to 1.2.99.904 (1.3 RC4)xorg-server-1.2.99.904Keith Packard2007-04-051-3/+3
|
* Don't erase current crtc for outputs on CloseScreenKeith Packard2007-04-021-1/+0
| | | | | Erasing this variable causes some outputs (SDVO on intel) to fail to be correctly reset at server reset time.
* Set version to 1.2.99.903 (1.3 RC3)xorg-server-1.2.99.903Keith Packard2007-03-261-3/+3
|
* Bump video driver ABI version to 1.2.Michel Dänzer2007-03-261-1/+1
| | | | | | | | | | | | This is necessary because server-1.2-branch bumped to 1.1 for xf86CVTMode and we have xf86XVFillKeyHelperDrawable on top of that. (cherry picked from commit 788cfce911793a26aed16f38f30678ecee82c873) Conflicts: hw/xfree86/common/xf86Module.h Avoid picking up XInput ABI change.
* Add per-drawable Xv colour key helper function.Michel Dänzer2007-03-264-3/+68
| | | | | | | | | | | | | | | This allows overlay Xv adaptors to work slightly better with compositing managers. Bump the video driver ABI minor so drivers only need to check for this at build time. (cherry picked from commit a232693c8c2a206aac47c07b133c071938204e0b) Conflicts: hw/xfree86/common/xf86Module.h Avoid picking up XInput ABI version change.
* fbdevhw: Only deal with RGB weight if default visual is True- or DirectColor.Michel Dänzer2007-03-261-12/+22
| | | | (cherry picked from commit 14d6a9b327381a6bb2dac59c62728e5fd0f0bcfb)
* fbdevhw: Consider mode set equal to mode requested if virtual width is larger.Michel Dänzer2007-03-261-17/+17
| | | | (cherry picked from commit 27a01e100bff21ac0b70c6d72071d7226fc91264)
* fbdevhw: Override RGB offsets and masks after setting initial mode.Michel Dänzer2007-03-261-0/+11
| | | | | | | | | This is a hack, but it should be a NOP for all the setups that worked before and actually seems to fix some others... Based on a patch by Peter Teichmann from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338241 . (cherry picked from commit dc5eb4523298f966bd5fd9ae6672160034b5e82c)
* fbdevhw: Use displayWidth for fbdev virtual width when appropriate.Michel Dänzer2007-03-261-1/+2
| | | | | | | The fbdev API doesn't allow setting the pitch explicitly, so we have to set the virtual width to the pitch we're using for drawing. This fixes corruption after changing the virtual width with RandR. (cherry picked from commit d077c0da470ab7291e8d838eaace57b066477d6f)
* fbdevhw: Fix some issues with the previous commit.Michel Dänzer2007-03-261-2/+3
| | | | | | Fix a TRACE_ENTER typo and only update the internal fbdev mode state cache after actually setting a mode. (cherry picked from commit c385bcf0bde38dd869f7065f859dd4b4126f5690)
* fbdevhw: Consolidate modeset ioctl calling, report failure if it modifies mode.Michel Dänzer2007-03-261-47/+82
| | | | | | | | The fbdev API allows the driver to 'accept' modes it doesn't really support by modifying it to the nearest supported mode. Without this check, e.g. vesafb would appear to accept all modes, even though it actually can't set any modes other than the bootup mode at all. (cherry picked from commit f6815cb68b0f6698497348fc6e4214dacef33b95)
* Make pending properties force mode set. And, remove AttachScreen calls.Keith Packard2007-03-238-140/+139
| | | | | | | | | | | | | | | | Yes, two changes in one commit. Sorry 'bout that. The first change ensures that when pending property values have been changed, a mode set to the current mode will actually do something, rather than being identified as a no-op. In addition, the driver no longer needs to manage the migration of pending to current values, that is handled both within the xf86 mode setting code (to deal with non-RandR changes) as well as within the RandR extension itself. The second change eliminates the two-call Create/AttachScreen stuff that was done in a failed attempt to create RandR resources before the screen structures were allocated. Merging these back into the Create function is cleaner.
* Ensure that crtc desired values track most recent mode.Keith Packard2007-03-231-0/+7
| | | | | | desiredX and desiredY were not recorded during xf86InitialConfiguration. desiredX, desiredY and desiredRotation were not recorded during xf86SetSingleMode.
* Incorrect extra memory copy in RRChangeOutputProperty.Keith Packard2007-03-231-2/+0
| | | | | Left over from previous version of the code, this memmove will break when the mode is not Replace.
* Fix Pending property API, adding RRPostPendingProperty.Keith Packard2007-03-233-59/+99
| | | | | | Pending Properties take effect when the driver says they do, so provide an API to tell DIX when a property effect is made. Also, allow driver to reject property values in RRChangeOutputProperty.
* Make sure RandR events are delivered from RRCrtcSet.Keith Packard2007-03-231-43/+50
| | | | Some paths were skipping the event delivery stage.
* Clean up xf86CrtcRec and xf86OutputRec objects at CloseScreen.Keith Packard2007-03-231-0/+14
| | | | Erase pointers to structures which are freed at server reset time.
* Clear allocated RandR screen private structure.Keith Packard2007-03-231-1/+1
| | | | | Use xcalloc instead of xalloc when allocating this structure to ensure consistent contents at startup.
* Clean up Rotate state on server reset.Keith Packard2007-03-204-18/+79
| | | | | The rotation state is stored in the xf86_config structure which is not re-initialized at server reset time. Clean it up at CloseScreen time.
* Slow down DDC I2C bus using a RiseFallTime of 20us for old monitors.Keith Packard2007-03-171-0/+6
| | | | | This time value makes the bus run slowly enough for even the least reliable of monitors. Thanks to Pavel Troller for finding the necessary change.
* Remove extra (and wrong) I2C ByteTimeout setting in DDC code.Keith Packard2007-03-171-1/+0
| | | | | | | | The DDC code sets the I2C timeouts to VESA standards, except that it had an extra setting of the ByteTimeout value which was wrong (off by a factor of 50). Removing this should help DDC work on many more monitors. Note that the Intel driver duplicated these settings, along with the error. Yay for cult and paste coding.
* Correct ref counting of RRMode structuresKeith Packard2007-03-152-1/+6
| | | | | | | | | RRModes are referenced by the resource db, RROutput and RRCrtc structures. Ensure that the mode reference count is decremented each time a reference is lost from one of these sources. The missing destroys were in RRCrtcDestroyResource and RROutputDestroyResource, which only happen at server reset time, so modes would be unavailable in subsequent server generations.
* Don't wedge when rotating more than one CRTC.Keith Packard2007-03-152-14/+20
| | | | | | Rotation block handler was re-registering the rotation damage structure, creating an infinite loop in the damage code. Track registration of the damage structure to avoid this.
* Allow xf86_reload_cursors during server init.Keith Packard2007-03-151-4/+16
| | | | | | xf86_reload_cursors is supposed to be called from the crtc mode setting commit hook; as that happens during server initialization, check for this case.
* Create driver-independent CRTC-based cursor layer.Keith Packard2007-03-149-13/+710
| | | | | | | | | This moves most of the cursor management code out of the intel driver and into the general server code. Of course, the hope is that this code will be useful for other driver writers as well. Check out xf86Crtc.h for the usage information, making sure you add the needed hooks to the crtc funcs structure for your driver.
* Update to version 1.2.99.902xorg-server-1.2.99.902Keith Packard2007-03-141-3/+3
|
* Revert "Xext: Update device's lastx/lasty when sending a motion event with ↵Keith Packard2007-03-141-2/+0
| | | | | | | XTest." This reverts commit 4c5837c940024cffc8990b602a97ef6ece08e875. There is no lastx/lasty in a valuator on this branch.
* Xext: Update device's lastx/lasty when sending a motion event with XTest.Peter Hutterer2007-03-141-0/+2
| | | | (cherry picked from commit 68c64ad7b1eea79c786b5a7f3459076780163a47)
* Xprint: shorten font filename to fit in tar length limitDrew Parsons2007-03-147-12/+12
| | | | | | | | | The length of the Xprint font file NewCenturySchlbk-BoldItalic.pmf pushes the full path over the traditional 100 character limit for tarballs (when module version number is included). Shorten it to NewCentSchlbk-BoldItal.pmf to get back below the limit and rename other font files in that family to match. (cherry picked from commit d5aba03feff41722c72b4c6193f09d141cbf1678)
View Lorry Controller Status