diff options
372 files changed, 24103 insertions, 0 deletions
diff --git a/ATIProprietaryDriver.mdwn b/ATIProprietaryDriver.mdwn new file mode 100644 index 00000000..4e5c0854 --- /dev/null +++ b/ATIProprietaryDriver.mdwn @@ -0,0 +1,39 @@ + + +## ATI/AMD Closed Source "fglrx" Drivers + +Since the Radeon R200 chipset series ATI/AMD is providing its own set of closed source binary only drivers for their hardware. The drivers were originally designed for the FireGL professional graphics adapters but got extended soon for supporting any comparable mainstream board design from ATI Inc. and from third party board vendors. + +See also the [[VideoDrivers|VideoDrivers]] page for a list of other drivers for ATI hardware. + + +### Driver Package + +The rpm packaged drivers from ATI/AMD do provide those main components: + +* readme file or a set of documentation pages +* DRI compatible driver module for 2D support +* DRI compatible driver module for OpenGL support +* kernel module (precompiled binaries plus source/lib for self building) +Other than that there are those minor components: + +* a set of install/uninstall scripts for usage by the rpm packaging +* a customized x11 configuration tool +* a binary control panel based upon QT toolkit and its sources +* sample source for the gamma correction interface +* sample application for OpenGL pbuffer rendering extension +The driver is hosted at [[http://www.ati.com|http://www.ati.com]] - go to download, select your board and then the Linux operating system for getting to the matching page. If Linux is not listed for your specific board then that might just be a web update error - you should then try out the drivers for a similar board as there is really only one single driver for all boards. + + +### Status + +The driver is relatively mature and does perform quite well for professional OpenGL applications. Some gaming applications do work reasonably nice, some others might still expose some minor or major problems. 2D performance is below of what the open source DRI drivers do provide, but is still acceptable fast for everyday work. The set of drivers still is bound to XFree86 4.0.0 and X.Org 6.7.0, but might get updated to be compatible with the latest X.Org release. Further updates and inclusion of GLSL are expected for one of the very next releases. + +The current drivers are for Linux/i386 and Linux/x86_64 (AMD 64bit or Intel EM64T) platforms only, but there were some Linux/ia64 drivers available from the download page of some big OEM vendor. + +For more information and discussion on the current driver releases a visit of the [[http://www.rage3d.com|http://www.rage3d.com]] forums is recommended. + + +### Support + +Please note that Xorg developers are mostly unable to help with any issues with this driver. For discussions with other users, please use the #ati IRC channel on irc.freenode.net. diff --git a/AdamJackson.mdwn b/AdamJackson.mdwn new file mode 100644 index 00000000..4c67e77c --- /dev/null +++ b/AdamJackson.mdwn @@ -0,0 +1,111 @@ + +X hacker, for Red Hat and recreationally. [[See elsewhere.|http://freedesktop.org/wiki/AdamJackson]] + + +# Old school 3D hardware + +I have something of a rare hardware fetish. The following list of cards I'd like to have at some point is as much for my own benefit as anyone else's. If you have one of these and are willing to part with it, please let me know! Contact info can be found through the link at the top. + +Even better, if you have programming information for this hardware, or contact information for the defunct companies, let me know. Even if it's just a definitive "sorry, this never taped out", that's better than nothing. + + +## 3dfx + +* Voodoo 5 6000. Sure, why not. +* Also, just about any sufficiently interesting Quantum3D card is fair game. + +## 3dlabs + +* Anything newer than what's supported by the gamma(4) driver. I've got a Wildcat VP760. I'm sure there's more than one generation of Wildcat though. + +## Ark Logic + +* 8100 (Tiger3D) and 8300 (Cougar3D). If they exist. + +## ArtX + +* Anything! They look like they were in business just long enough to sell some of their own kit before being bought by ATI (ATI paying to have ArtX take over really). I already have a Game``Cube, thanks though. + +## ATI + +* Rage Fury Maxx. Dual rage128. I have one but I don't think it POSTs anymore. + +## Barco + +* Did some medical imaging cards, among other things. Some were Number Nine chips with extra output cleverness, but there seem to have been some custom ASICs too. +* Update, 2008-05-01: I have two now. One's a pair of Cirrus chips behind a PCI bridge. The other is a custom ASIC. The PCI ID is for "Metheus Corporation", who Barco definitely bought. Despite having a ROM, it's not VBE-compliant. And, terrifyingly, the string "Tseng" appears in it. The ASIC name appears to be "Aura", according to the ROM. + +## Chromatic Research + +* mPact. Actually I have one, don't remember which one though (there's two, according to pci.ids). These were early shader-like hardware, so I would dearly love to find programming information or a competent driver disassembly. + +## Diamond + +* Various FireGLs. This is a bit misleading since Diamond never did silicon, but wikipedia [[lists|http://en.wikipedia.org/wiki/FireGL#List_of_Cards]] basically four varieties: FireGL 1 - 4 with IBM chips, 1000 through 3000 just boring old Permedias, 4000 is some wacky Mitsubishi chip and 5000 is something totally alien. I'd love to lay hands on a 4000 or 5000, I have examples of the other two varieties. + +## Dome + +* Same story as Barco, really. Later sold to Planar but still sold under the Dome marque. Not sure any of these were non-#9 chips, to be honest. + +## Evans and Sutherland + +* Pretty much any REALimage chip. I have a Lightning 1200 and a Tornado 3000. The E&S chips look like they also made their way into Accel``Graphics' Accel``Galaxy and other boards. See also Real``Vision below. + +## Intel + +* Intel 752 or 754 cards. These are rumored to exist but I've never seen one in the wild. Should be more or less i810 graphics on a card? + +## Intergraph + +* Don't really know the genealogy here. I have a few cards, need to document them better. These are probably predecessors of the post-glint 3dlabs kit. + +## iXMicro + +* Anything. I had a Twin Turbo ages ago but gave it away to daniels. + +## Matrox + +* QID. Pretty sure this is just a Parhelia with two extra output pipes. Almost certainly, pci.ids lists QIDs as variants of other P-series chips. I have a Parhelia and a P650, but it's a little unclear where the register banks for the other two CRTCs on a QID live. + +## Neomagic + +* Magic``Media 256XL+. The only one with a 3D engine. Almost certainly only to be found in laptops. The OQO model 01 possibly? + +## Number Nine + +* Imagine 2 (PCI ID 105D:2339) +* Ticket 2 Ride (PCI ID 105D:493D) +* Anything done by [[Silicon Spectrum|http://siliconspectrum.com/]]. + +## NVIDIA + +* NV2. Assuming any ever made it outside NVIDIA campus. + +## Oak Technology + +* Warp 5. If it exists. Wikipedia has a picture of a prototype board. + +## RealVision + +* Anything. Corporate takeover history leads me to believe they inherited the gfx group from E&S, so these might be related kit. I don't speak Japanese though. + +## S3 + +* Delta``Chrome and Gamma``Chrome. I have a Chrome S27. + +## Tech Source + +* Raptor 2100T. Yet more ATC hardware. + +## Tritech + +* Pyramid3D. Eval hardware definitely produced, definitely never shipped to retail. + +## Tseng Labs + +* ET6300. Again, not sure this ever reached market. + +## XGI + +* Volari V8 Duo. If it shipped. +* XP10.
\ No newline at end of file diff --git a/AdvancedTopicsFAQ.mdwn b/AdvancedTopicsFAQ.mdwn new file mode 100644 index 00000000..d4790c01 --- /dev/null +++ b/AdvancedTopicsFAQ.mdwn @@ -0,0 +1,50 @@ + + +# Advanced Topics + +[[!toc ]] + + +## I want to make the mouse cursor invisible + +X always must have a cursor. Its appearance depends on the window the cursor is over. You can change the appearance of the root window cursor and make it invisible that way. To make the root window mouse cursor invisible create an empty bitmap file. To do so you can either create a file [[emptyCursor.xbm|emptyCursor.xbm]] with the content: +[[!format txt """ +#define emptyCursor_width 1 +#define emptyCursor_height 1 +#define emptyCursor_x_hot 0 +#define emptyCursor_y_hot 0 +static unsigned char emptyCursor_bits[] = { +0x00}; +"""]] +or you can use the application `bitmap`. Start bitmap, create a new bitmap file with the `File->New` menue, and save it with `File->Save`. Assuming you called the empty bitmap file `emptyCursor.xbm` you can now change the root window cursor with: +[[!format txt """ + xsetroot -cursor emptyCursor.xbm emptyCursor.xbm +"""]] +NOTE: As mentioned this *only affects the root window cursor*. Modern window managers create their own root window. Its cursor is not affected by this. Also most applications define their own cursors. Moving a cursor over an application will cause its cursor to be displayed if it defines its own cursor. If it doesn't it will inherit the cursor of its parent window. + + +## I want to run the Xserver without a mouse attached, however the Xserver doesn't start without a core input device + + +### Server 1.4 (X11R7.3) and later + +The server will start without any devices connected. No core input device is needed anymore, it is automatically allocated. If your server crashes or shows other signs, this is a bug. Please file a bug report. + +You may also want to add the following line to the [[ServerFlags|ServerFlags]] section of your xorg.conf file: +[[!format txt """ + Option "AllowEmptyInput" "True" +"""]] + +### Earlier versions + +X refuses to start if the initialization of the core pointer input driver fails. You can add the line: +[[!format txt """ + Option "AllowMouseOpenFail" +"""]] +to the `"ServerFlags"` section to prevent this. However the better solution is to use the `void` driver as driver for the mouse input device. + + + +--- + + IDEA: Dual head setup and configuration issues diff --git a/AdvancedTopicsFAQ/emptyCursor.xpm b/AdvancedTopicsFAQ/emptyCursor.xpm new file mode 100644 index 00000000..9b330a37 --- /dev/null +++ b/AdvancedTopicsFAQ/emptyCursor.xpm @@ -0,0 +1,6 @@ +#define emptyCursor.xpm_width 1 +#define emptyCursor.xpm_height 1 +#define emptyCursor.xpm''x''hot 0 +#define emptyCursor.xpm''y''hot 0 +static unsigned char emptyCursor.xpm_bits[] = { +0x00}; diff --git a/AlanCoopersmith.mdwn b/AlanCoopersmith.mdwn new file mode 100644 index 00000000..57526871 --- /dev/null +++ b/AlanCoopersmith.mdwn @@ -0,0 +1,16 @@ + + +## Alan Coopersmith +[[!table header="no" class="mointable" data=""" +[[!img http://planet.freedesktop.org/faces/alanc.png] | Release Manager: X11``R6.9, [[7.5|Releases/7.5]], [[7.6|Releases/7.6]], [[7.7|Releases/7.7]] +X.Org Modular Maintainer: Solaris port, app/xdm, lib/libX11 +Co-lead (with [[MatthieuHerrb|MatthieuHerrb]]) of X.Org [[Security|Development/Security]] Team +Member, [[X.Org Foundation Board of Directors|BoardOfDirectors]]: 2009 - present +See also: [[http://people.freedesktop.org/~alanc|http://people.freedesktop.org/~alanc]], [[http://blogs.oracle.com/alanc/|http://blogs.oracle.com/alanc/]] +"""]] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/ArchitectureToDo.mdwn b/ArchitectureToDo.mdwn new file mode 100644 index 00000000..c005ba0e --- /dev/null +++ b/ArchitectureToDo.mdwn @@ -0,0 +1,87 @@ + + +# The Grand ToDo List + +[[!toc ]] + + +## What is this? + +This is a list of fundamental problems standing in the way of a better implementation of the desktop. On-topic items include graphics and input problems and needed features. + +To anyone working on these problems, or working on a large problem not listed here: please update this page with comments. It is intended to be a kind of road map, so feel free to comment on what you believe is the preferred solution to a problem. + +Non-coding mailing list lurkers are encouraged to update this page if they see a mistake or something that looks out of date. If unsure about a change, put it in italics and put a question mark after it. _(Got that?)_ Someone else will come along and confirm/deny the question. + + +## XAA + +_"<ajax> - XAA is totally unsuitable for accelerating modern desktop usage"_ + +XAA is designed around accelerating the wrong primitives. + +Solutions include: + +* implementing KAA in Xorg +* using the Kdrive X server _(has something other than XAA, right?)_ +* using Xgl _(requires [[MesaSolo|MesaSolo]] and friends to be ready)_ + +## Render Acceleration + +_"<ajax> - Render is largely unaccelerated"_ + +This depends on the XAA problem above. XAA isn't suitable for accelerating render. + +Solutions include: + +* replacing XAA +* using Xgl _(see above)_ +_Does/did the proprietary nvidia driver accelerate render? How?_ + + +## DRI FBO/pbuffer + +_"<ajax> - DRI really needs pbuffers and fbo's"_ + +Self evident? + +_There's interest in getting DRI to transfer textures from one process to another for a "glcompmgr." Related?_ + + +## DRI needs a memory manager + +_... assume video memory only large enough to store one texture ... _ + +_<ajax> the first client in general can't assume that its textures are still where it left them. thus we have an sarea. "shared area". when DRI clients dirty some bit of state, they leave a note of what state they touched in the sarea. so our second client would have dirtied the texture state, so the first client knows it needs to push its texture again. now remember we're wanting to share textures between clients. so introduce a third client. 1 and 3 want to share their texture. 1 owns it. 2 runs, evicting the shared texture. 3 goes next, and the texture it wants isn't there anymore. except 3 can't push it, because 3 is trying to pull it from 1. see the problem? 3 never had a copy of this texture. _ + +_<tjk> sounds like a proper dri memory manager would solve that._ + +Right now DRI uses some kind of "peer to peer" memory management technique. DRI really needs to start managing video and agp memory for the clients. This would enable passing textures from one client to another without copying and without the possibility of deadlocking. + +Additionally this would reduce the complexity of clients. + +Presumably, DRIMM would be responsible for moving data between video memory, agp memory, and it's own storage in main memory tying all of the information to the process it belongs to. + +_Would this eliminate the need to map video memory into the client's address space? or Would it make it easier to implement memory protection so that one client can't start scribbling on another client's video data just for fun?_ + + +## Multiple cursors + +_Shared projector systems have serious need for multiple simultaneous streams of input. _ + +_I recently had a chance to play with the projector table at MERL, and we can expect similar such devices as commercial products over the next couple years; it provides a compelling demonstration of the need. _ + +* _- Jim_ +Do we handle this with multiple cursors? Or do with handle with by making applications explicitly request input from many cursors? + + +## Configuration format + +There has been noise about an elektrified x server and machine vs human readable configuration file format. The x server itself does need a configuration makeover, but by a more general mechanism. [[XHotplugProposal|XHotplugProposal]] would like to do with with some sort of external configuration client. This would enable a legacy X![[OrgConfig|OrgConfig]] client, an elektrified client, a HAL-based client using dbus, etc without introducing dependancies for the X server itself. The other advantage to using a client is hotplug. See the dynamic reconfiguration section above. + + +## X on GL + +DRI is being reworked and merged with the linux framebuffer code. [[MesaSolo|MesaSolo]] is being prepared and mode selection code is being rewritten. _(right?)_ + +Xgl is a proof of concept server, but without the above, it cannot run except inside an ordinary X server. As soon as the above are ready, we will have a legitimate possibility for moving all rendering onto the GL API as a standalone GL X server. diff --git a/ArchitectureWorkingGroup.mdwn b/ArchitectureWorkingGroup.mdwn new file mode 100644 index 00000000..0b63eecd --- /dev/null +++ b/ArchitectureWorkingGroup.mdwn @@ -0,0 +1,58 @@ + + +# X.Org Foundation Architecture Working Group + +The X.Org Foundation Board of Directors recently voted to create an Architecture Working Group to serve as a forum to discuss the technical direction of the X Window System. + +The Architecture Working Group intends to represent a variety of interests in X Window System technologies, including traditional Xserver and protocol library developers, toolkit developers, application developers, as well as end-users. As a result, this working group hopes to serve as a forum for a wide variety of discussions related to the X Window System, including (but not limited to) architectural discussions, general technical directions, as well as development processes and procedures. + +The goal of the Architecture Working Group is to facilitate discussion and provide a forum to help build consensus in the areas mentioned above. To further this goal, membership is open to all interested participants. In this way, the Architecture Working Group can chart the technical direction of the X Window System, as well as advance its use, maintainability, and improve the scalability of the X.Org Foundation's development efforts. + +For those areas that have a more focused scope in influence and/or duration, as well as a critical mass of interested participants, a sub-working group may be created. The Release Wranglers, the [[Testing Working Group|TestGroup]], and the [[Modularization Working Group|ModularizationWorkingGroup]] are examples of existing sub-working groups. + +As already noted, membership is open to all interested participants. In an effort to encourage participation from as many of the growing list of X.Org contributors as possible, a new mailing list has been created for this working group. To subscribe, please visit: + + * [[http://lists.x.org/mailman/listinfo/xorg-arch|http://lists.x.org/mailman/listinfo/xorg-arch]] + +## Current Projects: + +The X Developer's Meeting held in Cambridge in February, 2005, concluded with a discussion of topics of current interest to the X.Org community. In addition, some issues were raised that people felt were good developer-oriented issues for the Architecture Working Group to address via the creation of processes and guidelines to facilitate developers. Some of those areas include: + + +### Development and release + + * Create processes that explain how new code/features get to HEAD + * Draft guidelines for committing changes + * Understand possible ABI changes and implicit dependencies + * Reference bugzilla ID in the commit message + * More information in the comments and commit message is better + * More atomic commits - don't check 15-20 different things in at one time + * Need for an on-going code czar - someone who's authority to remove controversial code (until further discussion) is unquestioned + * Which licenses are acceptable for contributions to X.Org projects + +### Creation of a documentation project (or even a sub-working group) + + * Convert existing documents to Doc``Book + * Get APIs and specifications in one, easy-to-find place + * Can vendors contribute internally-generated documentation that has general information + * Translate documentation to other languages? + +### Other related pages + + * [[ArchitectureToDo|ArchitectureToDo]] contains an initial list of projects + * [[http://www.freedesktop.org/wiki/FreedesktopProjects|http://www.freedesktop.org/wiki/FreedesktopProjects]] contains a list of Freedesktop projects + * [[XDevConf|http://www.freedesktop.org/wiki/Software_2fXDevConf]] includes the projects discussed at given at the February, 2005, X Developers Meeting in Cambridge. + * [[XInputHotplug|XInputHotplug]] is Kristian Hogsberg's project for hotplug of input devices + * [[LookingGlassIntegration|LookingGlassIntegration]] describes the Looking Glass functionality and an effort to integrate the Xserver changes into the tree for a future release. + +### Sub-working groups + + * Processes/guidelines describing what is needed to create a sub-working group +If you have ideas for other projects in any of these categories, or if you know of other projects not already listed here, please add them. + + +## FAQ: + +A list of some possible questions and answers you may have about the Architecture Working Group can be found at: + + * [[ArchitectureWorkingGroupFAQ|ArchitectureWorkingGroupFAQ]]
\ No newline at end of file diff --git a/ArchitectureWorkingGroupFAQ.mdwn b/ArchitectureWorkingGroupFAQ.mdwn new file mode 100644 index 00000000..640dd0f6 --- /dev/null +++ b/ArchitectureWorkingGroupFAQ.mdwn @@ -0,0 +1,23 @@ + + +# Architecture Working Group FAQ + +Q: I read the announcement about the creation of the Architecture Working Group within X.Org, but what does this really mean? + +A: This change will allow the technical discussions to take place in an open community forum, and it will free the board of directors to concentrate on other organizational and infrastructural issues. + +Q: What does this mean for the existing working groups? + +A: Three other previously established working groups -- the Release Wranglers, Testing Working Group and Modularization Working Group -- which previously made progress reports to the board of directors will now make their reports directly to the Architecture Working Group. + +Q: How is this list/group different from [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]] discussions? + +A: The content on [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]] discusses, to a large extent, defects and questions about the X.Org releases. The Architecture Working Group mailing list intends to discuss a wider range of longer-term technical and development issues. + +Q: I have a question, but I'm not sure if I should post it to [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]] or to [[xorg-arch@lists.x.org|mailto:xorg-arch@lists.x.org]]. Which list should I use? + +A: If in doubt, it is acceptable to start discussions on [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]]. If people feel the topic is better suited for discussion in the Architecture Working Group, the discussion can migrate to [[xorg-arch@lists.x.org|mailto:xorg-arch@lists.x.org]]. + +Q: What happened to the Architecture Board elected by the members last year? + +A: One of the primary reasons for the formation of the X.Org Foundation was to lower barriers to participation in and increase contribution to X Window System technologies. After careful consideration, the X.Org Foundation's Board of Directions determined that the best way to foster open participation in the development of this technology was to move architectural responsibilities away from a small, albeit elected, group to a larger group where all can participate. diff --git a/BartMassey.mdwn b/BartMassey.mdwn new file mode 100644 index 00000000..0fab557f --- /dev/null +++ b/BartMassey.mdwn @@ -0,0 +1,13 @@ + + +## Bart Massey + +Email: bart AT SPAMFREE cs DOT pdx DOT edu + +Bart Massey is an [[Associate Professor of Computer Science|http://www.cs.pdx.edu/~bart]] at [[Portland State University|http://pdx.edu]] in Portland, Oregon USA, where his research focus is on open source software engineering and open hardware technologies. Bart is the founder and proprietor of [[bart-massey.com LLC|http://bart-massey.com]], and Technologist in Residence at the Oregon [[Open Technology Business Center|http://opentechcenter.com]]. He has been involved with X development and education in various ways since around X11 release 2, and is the lead architect of the [[XCB|http://xcb.freedesktop.org]] library. + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/BoardOfDirectors.mdwn b/BoardOfDirectors.mdwn new file mode 100644 index 00000000..4e8a2c43 --- /dev/null +++ b/BoardOfDirectors.mdwn @@ -0,0 +1,43 @@ + + +# The X.Org Foundation Board of Directors + +Also see the [[XorgFoundation|XorgFoundation]] page. + +* Contact: board AT foundation DOT x DOT org + +### Current Members +[[!table header="no" class="mointable" data=""" +**Name** | **Affiliation** | **Contact** | **End of term** | **Office** + [[Alan Coopersmith|AlanCoopersmith]] | Oracle Corp. | alan.coopersmith AT oracle.com | Q1 2015 | + [[Alex Deucher|AlexDeucher]] | AMD | alexdeucher AT gmail DOT com | Q1 2014 | + [[Martin Peres|MartinPeres]] | University of Bordeaux - LaBRI | martin.peres AT free DOT fr | Q1 2015 | + [[Matt Dew|MattDew]] | Micron | marcoz AT osource DOT org | Q1 2014 | + [[Matthias Hopf|MatthiasHopf]] | Georg-Simon-Ohm University | mat AT mshopf DOT de | Q1 2014 | + [[Peter Hutterer|PeterHutterer]] | Red Hat | peter.hutterer AT who-t DOT net | Q1 2015 | **Secretary** + [[Stuart Kreitman|StuartKreitman]] | Oracle Corp. | stuart.kreitman AT oracle.com | Q1 2015 | **Treasurer** + [[Keith Packard|http://keithp.com/]] | Intel | keithp AT keithp DOT com | Q1 2014 | +"""]] + +End of term based on an [[election|BoardOfDirectors/Elections/]] date in the first quarter of each year. + + +### Recent Members + +* [[Eric Anholt|EricAnholt]] (Intel) eric AT anholt DOT net (term ended: 2012) +* [[Bart Massey|BartMassey]] (Portland State University) bart AT cs DOT pdx DOT edu (term ended: 2012) +* [[Matthieu Herrb|MatthieuHerrb]] (CNRS/LAAS) matthieu DOT herrb AT laas DOT fr (term ended: 2011) +* [[Donnie Berkholz|DonnieBerkholz]] (Gentoo Linux) dberkholz AT gentoo DOT org (term ended: 2010) +* [[Adam Jackson|AdamJackson]] (Red Hat, Inc.) ajax AT redhat DOT com (term ended: 2009) +* [[Daniel Stone|DanielStone]] (Collabora Ltd.) daniel AT fooishbar DOT org (resigned: 2009) +* [[Carl Worth|CarlWorth]] (Intel) cworth AT cworth DOT org (term ended:2009) +* [[Egbert Eich|EgbertEich]] (SUSE Linux Products GmbH) eich AT freedesktop DOT org (term ended: 2008) +The company affiliations are given only for reference. The X.Org Foundation has only personal membership; the Board Members do not represent their employers or affiliations. + +Originally, the Board had regular phonemeetings, now the meetings are held on irc. Summaries of these meetings are published at [[MeetingSummaries|BoardOfDirectors/MeetingSummaries]]. These meetings take place fortnightly, on Thursdays at 2pm Pacific Time (22:00 UTC depending on daylight savings time) in the #xf-bod channel on the OFTC network (irc.oftc.net #xf-bod). Please refer to the [[X.Org calendar|https://www.google.com/calendar/embed?src=nl1n1fmvu091eqh35ldqspar80@group.calendar.google.com&ctz=Australia/Brisbane]] for the next meeting time (remember to set the TZ). Some logs from these meetings can be found at [[IrcLogs|BoardOfDirectors/IrcLogs]]. + +The Foundation is operated according to its [[Bylaws|BylawReview]]. + +--- + + [[CategoryCategory|CategoryCategory]] diff --git a/BoardOfDirectors/Elections.mdwn b/BoardOfDirectors/Elections.mdwn new file mode 100644 index 00000000..179431c6 --- /dev/null +++ b/BoardOfDirectors/Elections.mdwn @@ -0,0 +1,27 @@ + +The [[X.Org Foundation|XorgFoundation]] holds annual elections for its [[Board of Directors|BoardOfDirectors]]. The full set of election rules is laid out in the [[Bylaws|http://www.x.org/wiki/BylawReview]]. What follows is a brief unofficial summary. + +Normally half of the board, 4 of the 8 members, are up for election each year for a two year term. If additional vacancies are present in the board, additional members will be elected to fill the remaining portion of vacated terms. + +The [[Members|http://members.x.org/]] of the X.Org Foundation are eligible to vote in elections. [[Membership|Membership]] is open to individuals who have contributed to the X Window System in some way, typically code, documentation or substantive public service. + +Votes are collected via a web application on [[http://members.x.org/|http://members.x.org/]] during an announced period. Each voter provides a ranked list of their preferences among the nominated candidates. The results are then tallied using the [[simple Borda Count method|http://en.wikipedia.org/wiki/Borda_count]]. + +For example, in an election with 6 candidates, the rankings are scored as follows: + +* [[!table header="no" class="mointable" data=""" +**rank** | **points** + 1 | 6 + 2 | 5 + 3 | 4 + 4 | 3 + 5 | 2 + 6 | 1 + none | 0 +"""]] + +Thus, refusing to rank someone denies them any points at all. Of course each rank can be assigned to at most one candidate. + +Candidates with the highest point total are elected to the board until all available seats for two-year terms are taken. If any remaining seats are open to fill vacancies, the next highest scoring candidates are elected to those until they are all filled. + +There is a limit of no more than two directors affiliated with the same company or institution. Once two seats are filled with affiliates of a given entity, all further candidates from that entity are skipped over in the ranked results list. diff --git a/BoardOfDirectors/Elections/2010.mdwn b/BoardOfDirectors/Elections/2010.mdwn new file mode 100644 index 00000000..dd0a1abf --- /dev/null +++ b/BoardOfDirectors/Elections/2010.mdwn @@ -0,0 +1,112 @@ + +The [[X.Org Foundation|XorgFoundation]] is holding elections for the [[BoardOfDirectors|BoardOfDirectors]]. The [[Elections|BoardOfDirectors/Elections]] overview page describes the voting methods and process. [[Members|Membership]] may vote by logging in to the web app on [[https://members.x.org/|https://members.x.org/]] + +For the 2010 elections, the regular 4 seats are open for 2 year terms, and one additional seat is open for a 1 year term to finish the term vacated by Daniel Stone's resignation. + +[[!toc ]] + + +## Election Dates + +* **Voting opens:** [[Friday, 5 Feb. 2010, 1 am UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=5&year=2010&hour=1&min=0&sec=0&p1=0]] +* **Voting closes:** [[Thursday, 18 Feb. 2010, 11pm UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=18&year=2010&hour=23&min=0&sec=0&p1=0]] + +## Candidates + + +### Eric Anholt +Current Affiliation +: Intel + +Statement of Contribution +: My role in X.Org has largely been as a developer, including contributions to the EXA acceleration architecture, RandR 1.2 development, and developing native Intel modesetting. + +Personal Statement +: I got my start in X working on Mesa and 2D drivers back in the early days of DRI, and later moved on to working in the X Server on acceleration architectures. I've since been working at Intel on the X Server, the 2D driver, and the 3D driver and Mesa. On the board this past term, I've primarily contributed by working on minor administration tasks. In particular, I made touchups on the members system (failing at my plan to replace it), and was the point person approving new members as they applied. + + + +### Alex Deucher +Current Affiliation +: AMD + +Statement of Contribution +: I've been working on Xorg video drivers for many years. I now work at AMD supporting the open source driver stack and helping provide chipset documentation for AMD hardware. + +Personal Statement +: The X Window System has interested me since I first saw screen shots of X window managers back in 1997. I got actively involved in X around 2000 and my interest and participation has grown from there. I now work for AMD supporting open source software on AMD graphics hardware. Prior to starting at AMD, I worked in telecom engineering and intellectual property risk management. My current focus has been on 2D and 3D driver support and documentation for AMD hardware. I have previously contributed to a number of other X drivers including drivers for hardware from S3 and Siliconmotion and mentored several Google and Xorg summer of code projects. Sitting on the X.Org Foundation Board of Directors would give me a chance to lend my unique expertise and skill set to the future direction of the X Window System and related technologies. I would like to focus on increasing new user participation and finding solutions to legal obstacles to handling new technologies in the open source X graphics stack. + + + +### Matthieu Herrb +Current Affiliation +: Centre National de la Recherche Scientifique (CNRS) + +Statement of Contribution +: Long time X contributor. Current focus: Security, *BSD support + +Personal Statement +: I'm 46 years old and work for a French research lab in Toulouse, in the south-west of France. I've been contributing to X since the XFree86 2.x era. I'm maintaining the OpenBSD port of X.Org and trying to help other BSD projects to get the support they need too. I've also been handling security issues in X.Org since The X.Org foundation has a very important role to play in education and animation of the community around X.Org, in particular by organizing X developer conferences and providing support for people to participate to these events. As a member of the board I will continue to support these efforts to promote the X technology. I strongly believe that the multi-platform nature of X is one of its key strength and will continue to work with the board to support portability towards a wide range of operating systems, as well as the MIT style licensing of the core X.Org server and libraries. + + + +### Matthias Hopf +Current Affiliation +: SuSE GmbH + +Statement of Contribution +: Working on radeonhd (one of the principal authors), R[67]xx bringup, RandR (1.3, specifically), general Xserver fixes. + +Personal Statement +: I'm active in X development for over 5 years now. For SUSE I'm working on stabilizing the Xserver and drivers to get enterprise quality in our products, upstream I'm trying hard to foster new and fancy developments that do not conflict with backwards compatibility too much. I'm a strong advocate of Google SoC and X.org's participation therein. + + + +### Stuart Kreitman +Current Affiliation +: Sun Microsystems + +Statement of Contribution +: +Xorg promoter to the Open``Solaris community, hacker, Dev``Conf organizer, board member for several terms. + + +Personal Statement +: I am current co-treasurer, former board member, early co-architect of the Xorg Foundation and dis-architect of the late X Consortium. My contributions to the Foundation and the Xorg community include Conference organization, donations of funds and equipment from Sun, and education within Sun to promote alignment and transition to a pure-Xorg based product set. My technical interests are in the areas of input handling, thin clients, and large scale multiuser deployments. As of Feb 15, 2010, I will be an employee of Oracle Corporation, advocating for Xorg desktop to a wider but less *nix-centric user community, an uphill task that really needs the support of this Xorg community. + + + +### David Nicol +Current Affiliation +: tipjar LLC + +Statement of Contribution +: Coding since 1980, dot-com since 1996. + +Personal Statement +: If elected to the X.Org foundation Board of Directors, David Nicol will participate in the bi-weekly meetings on IRC and attend the annual face-to-face. David Nicol brings decades of experience as a software consultant, and recent credentials from a top entrepreneurship program, to add value to the organization by verifying that our activities continue to further our mission in an ever-improving way. + + + +### Keith Packard +Current Affiliation +: Intel + +Statement of Contribution +: Have written a bit of X server code over the years, designed and wrote a few extensions that add nice features to the window system. + +Personal Statement +: The X.org board continues to perform an important role in the X community. Over the last couple of years, the primary activities of the board have involved organizing technical conferences and providing funding for developers to attend both those conferences and other important free software conferences around the world. I've been involved in the board since the reformation of the X.org foundation, as treasurer for the whole time and as an intermittent board member. If elected, I will offer my services as treasurer again and work to continue offering opportunities for X developers to meet around the world. + + + +### Carl Worth +Current Affiliation +: Intel + +Statement of Contribution +: I was lured into the world of X by an invitation to implement trapezoid rasterization for the software implementation of Render in the server. From there I moved up the stack implementing the cairo graphics library so there would be an easier way to get interesting graphics in X without coding XRender directly. More recently, I've come back down the stack working to improve the xf86-video-intel drivers so that cairo will be reasonably accelerated. + +Personal statement +: The X Window System has an essential role in an increasing number of mobile and desktop platforms built with Free Software. Of course, the X.Org Foundation has no technical role in the development of the system. But the Foundation does have a unique position to be able to facilitate the workings of the community. Examples of Foundation activities include hosting developers' summits and attracting new developers by funding students. I have contributed time and effort by serving on the X.Org Foundation Board over the past two years and would be happy to contribute similarly in the future. + diff --git a/BoardOfDirectors/Elections/2011.mdwn b/BoardOfDirectors/Elections/2011.mdwn new file mode 100644 index 00000000..b2f7261b --- /dev/null +++ b/BoardOfDirectors/Elections/2011.mdwn @@ -0,0 +1,123 @@ + +The [[X.Org Foundation|XorgFoundation]] is holding elections for the [[BoardOfDirectors|BoardOfDirectors]]. The [[Elections|BoardOfDirectors/Elections]] overview page describes the voting methods and process. [[Members|Membership]] may vote by logging in to the web app on [[https://members.x.org/|https://members.x.org/]] + +For the 2011 elections, the regular 4 seats are open for 2 year terms. + +Results of the Candidate Q&A can be found on [[BoardOfDirectors/Elections/2011/qa|BoardOfDirectors/Elections/2011/qa]]. + +[[!toc ]] + + +## Election Dates + +* **Nomination period opens:** [[Tuesday, Jan. 18, 2011, 00:00 UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=18&year=2011&hour=1&min=0&sec=0&p1=0]] +* **Nomination period closes:** [[Monday, Feb. 07, 2011, 23:59 UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=7&year=2011&hour=23&min=59&sec=0&p1=0]] +* **Publication of candidates:** [[Monday, Feb. 14, 2011|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=14&year=2011&hour=12&min=0&sec=0&p1=0]] +* **Deadline for X.org membership application and renewals:** [[Friday, Feb. 11, 2011, 23:59 UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=11&year=2011&hour=23&min=59&sec=0&p1=0]] +* **Candidate Q&A begins:** [[Monday, Feb. 14, 2011|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=14&year=2011&hour=12&min=0&sec=0&p1=0]] +* **Candidate Q&A ends:** [[Monday, Feb. 21, 2011, 23:59 UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=21&year=2011&hour=23&min=59&sec=0&p1=0]] +* **Election period opens:** [[Monday, Feb. 21, 2011, 00:00 UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=21&year=2011&hour=0&min=0&sec=0&p1=0]] +* **Election period closes:** [[Monday, Feb. 28, 2011, 23:59 UTC|http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=28&year=2011&hour=23&min=59&sec=0&p1=0]] + +## Candidates + + +### Eric Anholt +Current Affiliation +: Intel + +Statement of Contribution +: My role in X.Org has largely been as a developer, including contributions to the EXA acceleration architecture, RandR 1.2 development, and developing native Intel modesetting. + +Personal Statement +: Eric Anholt has been active in the X community for the last 5 years as an Intel graphics driver developer, and before that as a general DRI driver and FreeBSD DRM hacker. As an X.Org board member, Eric has managed the member application process, done minor system administration on the X.Org server, and passed messages on to the freedesktop.org sysadmin when it has been out of his scope. + + + +### Alan Coopersmith +Current Affiliation +: Oracle + +Statement of Contribution +: X11 R6.9, 7.5, + 7.6 Release Manager, Modularization Task Force + Security Coordination Team, Maintainer of xdm + Solaris/OpenSolaris port of Xorg + +Personal Statement +: I am running for re-election to the X.Org Foundation Board, having served as a member for the past two years, and the Secretary for the past year. + + +: The role of the X.Org Board is to manage the resources of the foundation and use them to support the developers, both current and new. Travel sponsorships for developers and Summer of Code students to come to X.Org conferences have worked well, and the board has also funded some targeted hackfests, and have accepted proposals for a couple more still in the planning stages. The Board should encourage more proposals for other ways to make use of the foundations resources. + + +: When I last ran, I said that members should have greater visibility into the workings of the X.Org Board, including more frequent reports from the board of the tasks it is working on. This has happened over the past two years, with information on board meetings now regularly provided to the members, and should continue. + + +: I am glad to have been able to serve the X.Org membership over these past two years, and appreciate the opportunity to continue to serve. + + + +### Stuart Kreitman +Current Affiliation +: Oracle + +Statement of Contribution +: +Xorg promoter to the Open Solaris community, hacker, [[DevConf|DevConf]] organizer, board member for several terms + + +Personal Statement +: As current treasurer and former board member of X.org, I am thankful to be considered for re-election to the board. I generally attend the bimonthly board meetings already, so this added role would allow us to reach a quorum more often, which would expedite business. + + +: My technical life has included Xorg maintenance and advocacy within my organization and user community (Sun, now Oracle), and occasionally committing resources from that organization for the benefit of the Xorg community. + + + +### Bart Massey +Current Affiliation +: Portland State University + +Statement of Contribution +: I am a member of the X.Org Foundation Board, an Associate Professor of Computer Science at Portland State University, and an X geek with 20 years experience. I'm the architect, advisor, and sometimes implementor to the XCB project, which provides a modern replacement to Xlib. I've also tried to help out with design and algorithms for Xft, Render, Cairo, and various other projects. PSU hosts freedesktop.org's infrastructure, and PSU students have contributed to X in substantial ways. I am currently investigating X in Haskell and GUI toolkit design. + +Personal Statement +: I've had the privilege of serving the X.Org Foundation Board as a Board Member over the last four years, as Secretary for three. + + +: In the last two years, the X.Org Foundation has consolidated many of the gains that we made previously. The Foundation was successful in supporting and encouraging communication in the X community, and in deploying our resources to support X technical development. + + +: We have been working harder to recruit new developers. I recently helped to initiate an effort to collect, reorganize and rationalize X developer documentation. We plan to push forward in the coming year with new developer documents, for which I am organizing a book sprint. I have continued to be involved with the Google / X.Org Summer of Code, and have continued to contribute to various X projects such as XCB that are new-developer friendly. + + +: There's still a lot to do. The end of our interminable corporate and financial reorganization is in sight. We need to understand how the Foundation should support transitions to "post-X.Org" technologies such as Wayland. I'd like to continue with the Board and help with these activities. I humbly ask for your support in doing so. + + + +### Tiago Vignatti +Current Affiliation +: Nokia + +Statement of Contribution +: Following Linux graphics open communities since 2006. My interests are on X Window System development and implementation, processes of open source development, and any other graphics technologies that enable embedded system development. + +Personal Statement +: As a university student, back in 2006, I got involved with X.Org when I started my contribution with X development; the time was great, I was doing it as a hobby and for fun, and I had the pleasure to attend a couple of X conferences. + + +: Nowadays I do the same, but working for Nokia; besides being paid (which is good), the difference now is that I try push the resources of the company to keep the open source implementation of X, in which I believe and think it can be shaped in a beneficial way for everyone, technically and politically speaking. + + +: Also, I believe I can give a step further, using my experience and knowledge to help the Foundation in all the possible ways, attracting more developers and contributors for the development of X. I would be quite happy to do my best for X.Org. + + + +### Carl Worth +Current Affiliation +: Intel + +Statement of Contribution +: I was lured into the world of X by an invitation to implement trapezoid rasterization for the software implementation of Render in the server. From there I moved up the stack implementing the cairo graphics library so there would be an easier way to get interesting graphics in X without coding XRender directly. More recently, I've come back down the stack working to improve the xf86-video-intel drivers so that cairo will be reasonably accelerated. + +Personal Statement +: The X Window System has an essential role in an increasing number of mobile and desktop platforms built with Free Software. Of course, the X.Org Foundation has no technical role in the development of the system. But the foundation does have a unique position to be able to facilitate the workings of the community. Examples of foundation activities include hosting developers' summits and attracting new developers by funding students. I would be happy to contribute of my time and effort to help with these and other appropriate foundation activities. + diff --git a/BoardOfDirectors/IrcLogs.mdwn b/BoardOfDirectors/IrcLogs.mdwn new file mode 100644 index 00000000..7f07fa2e --- /dev/null +++ b/BoardOfDirectors/IrcLogs.mdwn @@ -0,0 +1,106 @@ + +IRC logs of [[BoardOfDirectors|BoardOfDirectors]] Meetings on channel #xf-bod on the oftc irc network. + +Meetings are held every second Tuesday. + + +## 2010 + +* [[Feb. 16|BoardOfDirectors/IrcLogs/2010/02-16]] +* [[Mar. 2|BoardOfDirectors/IrcLogs/2010/03-02]] +* [[Mar. 16|BoardOfDirectors/IrcLogs/2010/03-16]] +* [[Mar. 30|BoardOfDirectors/IrcLogs/2010/03-30]] +* [[Apr. 13|BoardOfDirectors/IrcLogs/2010/04-13]] +* [[Apr. 27|BoardOfDirectors/IrcLogs/2010/04-27]] +* [[May. 11|BoardOfDirectors/IrcLogs/2010/05-11]] +* [[May. 25|BoardOfDirectors/IrcLogs/2010/05-25]] +* [[Jun. 8|BoardOfDirectors/IrcLogs/2010/06-08]] +* [[Jun. 22|BoardOfDirectors/IrcLogs/2010/06-22]] +* [[Jul. 6|BoardOfDirectors/IrcLogs/2010/07-06]] +* [[Jul. 20|BoardOfDirectors/IrcLogs/2010/07-20]] +* Aug. 3 - Meeting was canceled +* [[Aug. 17|BoardOfDirectors/IrcLogs/2010/08-17]] +* [[Aug. 31|BoardOfDirectors/IrcLogs/2010/08-31]] +* Sep. 17 - Meeting was held live during [[XDS 2010|Events/XDS2010]] +* [[Sep. 28|BoardOfDirectors/IrcLogs/2010/09-28]] +* [[Oct. 11|BoardOfDirectors/IrcLogs/2010/10-11]] - Meeting moved to Monday from now on, same time +* [[Oct. 25|BoardOfDirectors/IrcLogs/2010/10-25]] +* [[Nov. 8|BoardOfDirectors/IrcLogs/2010/11-08]] +* [[Nov. 22|BoardOfDirectors/IrcLogs/2010/11-22]] +* [[Dec. 6|BoardOfDirectors/IrcLogs/2010/12-06]] +* [[Dec. 20|BoardOfDirectors/IrcLogs/2010/12-20]] + +## 2011 + +* [[Jan. 3|BoardOfDirectors/IrcLogs/2011/01-03]] +* Jan. 17 - Meeting was canceled (Martin Luther King, Jr. day) +* [[Jan. 31|BoardOfDirectors/IrcLogs/2011/01-31]] +* [[Feb. 14|BoardOfDirectors/IrcLogs/2011/02-14]] +* [[Feb. 28|BoardOfDirectors/IrcLogs/2011/02-28]] +* [[Mar. 14|BoardOfDirectors/IrcLogs/2011/03-14]] +* [[Mar. 28|BoardOfDirectors/IrcLogs/2011/03-28]] +* [[Apr. 11|BoardOfDirectors/IrcLogs/2011/04-11]] +* [[Apr. 28|BoardOfDirectors/IrcLogs/2011/04-28]] - Meeting moved to Thursday from now on, same time +* [[May. 12|BoardOfDirectors/IrcLogs/2011/05-12]] +* [[May. 26|BoardOfDirectors/IrcLogs/2011/05-26]] +* [[Jun. 09|BoardOfDirectors/IrcLogs/2011/06-09]] +* [[Jun. 23|BoardOfDirectors/IrcLogs/2011/06-23]] +* [[Jul. 7|BoardOfDirectors/IrcLogs/2011/07-07]] +* [[Jul. 21|BoardOfDirectors/IrcLogs/2011/07-21]] +* [[Aug. 4|BoardOfDirectors/IrcLogs/2011/08-04]] +* [[Aug. 18|BoardOfDirectors/IrcLogs/2011/08-18]] +* [[Sep. 1|BoardOfDirectors/IrcLogs/2011/09-01]] +* Sep. 14 - Meeting was held live during [[XDC 2011|Events/XDC2011]] +* Sep. 29 - Meeting was canceled +* [[Oct. 13|BoardOfDirectors/IrcLogs/2011/10-13]] +* [[Oct. 27|BoardOfDirectors/IrcLogs/2011/10-27]] +* [[Nov. 10|BoardOfDirectors/IrcLogs/2011/11-10]] +* Nov. 24 - Meeting was canceled (Thanksgiving) +* [[Dec. 8|BoardOfDirectors/IrcLogs/2011/12-08]] +* Dec. 22 - Meeting was canceled (X-mas) + +## 2012 + +* [[Jan. 5|BoardOfDirectors/IrcLogs/2012/01-05]] +* [[Jan. 19|BoardOfDirectors/IrcLogs/2012/01-19]] +* [[Feb. 2|BoardOfDirectors/IrcLogs/2012/02-02]] +* [[Feb. 16|BoardOfDirectors/IrcLogs/2012/02-16]] +* [[Mar. 1|BoardOfDirectors/IrcLogs/2012/03-01]] +* [[Mar. 15|BoardOfDirectors/IrcLogs/2012/03-15]] +* [[Mar. 29|BoardOfDirectors/IrcLogs/2012/03-29]] +* [[Apr. 12|BoardOfDirectors/IrcLogs/2012/04-12]] +* [[Apr. 26|BoardOfDirectors/IrcLogs/2012/04-26]] +* [[May. 10|BoardOfDirectors/IrcLogs/2012/05-10]] +* [[May. 24|BoardOfDirectors/IrcLogs/2012/05-24]] +* [[Jun. 07|BoardOfDirectors/IrcLogs/2012/06-07]] +* [[Jun. 21|BoardOfDirectors/IrcLogs/2012/06-21]] +* [[Jul. 05|BoardOfDirectors/IrcLogs/2012/07-05]] +* [[Jul. 19|BoardOfDirectors/IrcLogs/2012/07-19]] +* [[Aug. 02|BoardOfDirectors/IrcLogs/2012/08-02]] +* [[Aug. 16|BoardOfDirectors/IrcLogs/2012/08-16]] +* [[Aug. 30|BoardOfDirectors/IrcLogs/2012/08-30]] +* Sep. 13 - Meeting was canceled (XDC) +* Sep. 19 - Meeting was held live during [[XDC 2012|Events/XDC2012]] +* [[Oct. 4|BoardOfDirectors/IrcLogs/2012/10-04]] +* [[Oct. 18|BoardOfDirectors/IrcLogs/2012/10-18]] +* [[Nov. 1|BoardOfDirectors/IrcLogs/2012/11-01]] +* [[Nov. 15|BoardOfDirectors/IrcLogs/2012/11-15]] +* [[Nov. 29|BoardOfDirectors/IrcLogs/2012/11-29]] +* [[Dec. 13|BoardOfDirectors/IrcLogs/2012/12-13]] +* Dec. 27 - Meeting was canceled (X-mas holidays) + +## 2013 + +* [[Jan. 10|BoardOfDirectors/IrcLogs/2013/01-10]] +* [[Jan. 24|BoardOfDirectors/IrcLogs/2013/01-24]] +* [[Feb. 7|BoardOfDirectors/IrcLogs/2013/02-07]] +* [[Feb. 21|BoardOfDirectors/IrcLogs/2013/02-21]] +* [[Mar. 7|BoardOfDirectors/IrcLogs/2013/03-07]] +* [[Mar. 21|BoardOfDirectors/IrcLogs/2013/03-21]] +* [[Apr. 4|BoardOfDirectors/IrcLogs/2013/04-04]] +* [[Apr. 18|BoardOfDirectors/IrcLogs/2013/04-18]] +* [[May. 2|BoardOfDirectors/IrcLogs/2013/05-02]] +* [[May. 16|BoardOfDirectors/IrcLogs/2013/05-16]] +* [[May. 30|BoardOfDirectors/IrcLogs/2013/05-30]] +* [[Jun. 13|BoardOfDirectors/IrcLogs/2013/06-13]] +* [[Jun. 27|BoardOfDirectors/IrcLogs/2013/06-27]]
\ No newline at end of file diff --git a/BoardOfDirectors/MeetingSummaries.mdwn b/BoardOfDirectors/MeetingSummaries.mdwn new file mode 100644 index 00000000..9060353f --- /dev/null +++ b/BoardOfDirectors/MeetingSummaries.mdwn @@ -0,0 +1,9 @@ + +Summaries of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]] Meetings are posted here. They were not posted, or only posted to the members.x.org site, for several years, before resuming in 2010. + +* [[2006|BoardOfDirectors/MeetingSummaries/2006]] +* [[2008|BoardOfDirectors/MeetingSummaries/2008]] +* [[2009|BoardOfDirectors/MeetingSummaries/2009]] +* [[2010|BoardOfDirectors/MeetingSummaries/2010]] +* [[2011|BoardOfDirectors/MeetingSummaries/2011]] +* [[2013|BoardOfDirectors/MeetingSummaries/2013]]
\ No newline at end of file diff --git a/BoardOfDirectors/MeetingSummaries/2006.mdwn b/BoardOfDirectors/MeetingSummaries/2006.mdwn new file mode 100644 index 00000000..b4c91d06 --- /dev/null +++ b/BoardOfDirectors/MeetingSummaries/2006.mdwn @@ -0,0 +1,27 @@ + +Summaries of the Board of Director Meetings are posted here. + +* [[BodMeetingSummaries-01-10-2006|BodMeetingSummaries-01-10-2006]] +* [[BodMeetingSummaries-01-17-2006|BodMeetingSummaries-01-17-2006]] +* [[BodMeetingSummaries-01-24-2006|BodMeetingSummaries-01-24-2006]] +* [[BodMeetingSummaries-01-31-2006|BodMeetingSummaries-01-31-2006]] +* [[BodMeetingSummaries-02-14-2006|BodMeetingSummaries-02-14-2006]] +* [[BodMeetingSummaries-02-21-2006|BodMeetingSummaries-02-21-2006]] +* [[BodMeetingSummaries-02-28-2006|BodMeetingSummaries-02-28-2006]] +* [[BodMeetingSummaries-03-07-2006|BodMeetingSummaries-03-07-2006]] +* [[BodMeetingSummaries-03-14-2006|BodMeetingSummaries-03-14-2006]] +* [[BodMeetingSummaries-03-21-2006|BodMeetingSummaries-03-21-2006]] +* [[BodMeetingSummaries-04-11-2006|BodMeetingSummaries-04-11-2006]] +* [[BodMeetingSummaries-04-25-2006|BodMeetingSummaries-04-25-2006]] +* [[BodMeetingSummaries-05-16-2006|BodMeetingSummaries-05-16-2006]] +* [[BodMeetingSummaries-05-30-2006|BodMeetingSummaries-05-30-2006]] +* [[BodMeetingSummaries-07-14-2006|BodMeetingSummaries-07-14-2006]] +* [[BodMeetingSummaries-08-08-2006|BodMeetingSummaries-08-08-2006]] +* [[BodMeetingSummaries-08-15-2006|BodMeetingSummaries-08-15-2006]] +* [[BodMeetingSummaries-08-22-2006|BodMeetingSummaries-08-22-2006]] +* [[BodMeetingSummaries-08-29-2006|BodMeetingSummaries-08-29-2006]] +* [[BodMeetingSummaries-09-05-2006|BodMeetingSummaries-09-05-2006]] +* [[BodMeetingSummaries-09-26-2006|BodMeetingSummaries-09-26-2006]] +* [[BodMeetingSummaries-10-03-2006|BodMeetingSummaries-10-03-2006]] +* [[BodMeetingSummaries-10-10-2006|BodMeetingSummaries-10-10-2006]] +* [[BodMeetingSummaries-10-17-2006|BodMeetingSummaries-10-17-2006]]
\ No newline at end of file diff --git a/BoardOfDirectors/MeetingSummaries/2008.mdwn b/BoardOfDirectors/MeetingSummaries/2008.mdwn new file mode 100644 index 00000000..64093131 --- /dev/null +++ b/BoardOfDirectors/MeetingSummaries/2008.mdwn @@ -0,0 +1,2 @@ + +Coming soon diff --git a/BoardOfDirectors/MeetingSummaries/2009.mdwn b/BoardOfDirectors/MeetingSummaries/2009.mdwn new file mode 100644 index 00000000..0ac1797f --- /dev/null +++ b/BoardOfDirectors/MeetingSummaries/2009.mdwn @@ -0,0 +1,2 @@ + +Coming Soon. diff --git a/BoardOfDirectors/MeetingSummaries/2010.mdwn b/BoardOfDirectors/MeetingSummaries/2010.mdwn new file mode 100644 index 00000000..61949c9a --- /dev/null +++ b/BoardOfDirectors/MeetingSummaries/2010.mdwn @@ -0,0 +1,26 @@ + +Summaries of the 2010 meetings of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]. +[[!table header="no" class="mointable" data=""" + 2010 | [[2011 >>|BoardOfDirectors/MeetingSummaries/2011]] +"""]] + +* [[March 2|BoardOfDirectors/MeetingSummaries/2010/03-02]] +* [[March 16|BoardOfDirectors/MeetingSummaries/2010/03-16]] +* [[March 30|BoardOfDirectors/MeetingSummaries/2010/03-30]] +* [[April 13|BoardOfDirectors/MeetingSummaries/2010/04-13]] +* [[April 27|BoardOfDirectors/MeetingSummaries/2010/04-27]] +* [[May 25|BoardOfDirectors/MeetingSummaries/2010/05-25]] +* [[June 22|BoardOfDirectors/MeetingSummaries/2010/06-22]] +* [[July 6|BoardOfDirectors/MeetingSummaries/2010/07-06]] +* [[July 20|BoardOfDirectors/MeetingSummaries/2010/07-20]] +* Aug. 3 - Meeting was canceled due to lack of quorum +* [[August 17|BoardOfDirectors/MeetingSummaries/2010/08-17]] +* [[August 31|BoardOfDirectors/MeetingSummaries/2010/08-31]] +* Sept 14 - Meeting skipped due to [[XDS2010|Events/XDS2010]] +* [[Sept. 28|BoardOfDirectors/MeetingSummaries/2010/09-28]] +* [[Oct. 11|BoardOfDirectors/MeetingSummaries/2010/10-11]] - Meetings moved from Tuesday to Monday +* [[Oct. 25|BoardOfDirectors/MeetingSummaries/2010/10-25]] +* [[Nov. 8|BoardOfDirectors/MeetingSummaries/2010/11-08]] +* [[Nov. 22|BoardOfDirectors/MeetingSummaries/2010/11-22]] +* [[Dec. 6|BoardOfDirectors/MeetingSummaries/2010/12-06]] +* [[Dec. 20|BoardOfDirectors/MeetingSummaries/2010/12-20]]
\ No newline at end of file diff --git a/BoardOfDirectors/MeetingSummaries/2011.mdwn b/BoardOfDirectors/MeetingSummaries/2011.mdwn new file mode 100644 index 00000000..71e70076 --- /dev/null +++ b/BoardOfDirectors/MeetingSummaries/2011.mdwn @@ -0,0 +1,13 @@ + +Summaries of the 2011 meetings of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]. +[[!table header="no" class="mointable" data=""" + [[<< 2010|BoardOfDirectors/MeetingSummaries/2010]] | 2011 +"""]] + +* [[Jan. 3|BoardOfDirectors/MeetingSummaries/2011/01-03]] +* Jan. 17 - canceled (US holiday: Martin Luther King, Jr. Day) +* [[Jan. 31|BoardOfDirectors/MeetingSummaries/2011/01-31]] +* [[Feb. 14|BoardOfDirectors/MeetingSummaries/2011/02-14]] +* [[Feb. 28|BoardOfDirectors/MeetingSummaries/2011/02-28]] +* [[Mar. 14|BoardOfDirectors/MeetingSummaries/2011/03-14]] +* Mar. 28
\ No newline at end of file diff --git a/BodMeetingSummaries-01-10-2006.mdwn b/BodMeetingSummaries-01-10-2006.mdwn new file mode 100644 index 00000000..7d1fd849 --- /dev/null +++ b/BodMeetingSummaries-01-10-2006.mdwn @@ -0,0 +1,45 @@ + + +[[!format txt """ +Summary of the BoD meeting Jan 10, 2006: + +Present Stuart Kreitman, Jim McQuillan, Kevin Martin, Stuart Anderson, + Leon Shiman, Egbert Eich + +Topics discussed: +- Management + * note taking + * system administration +- Budget + +Details: +* Note taking: we will continue to collect notes taken by board + members. + + Leon offered to create edited notes. + + Egbert offered to create a summary from notes he took. + Use these as a basis for decision on the format for publication +* System administration + + The question was raised if the organization needs somebody hired to + do system administration and possibly share this person with other + OS projects (idea from last year's XDevConf) + + Stuart Anderson offerd to continue to do this for us pro bono + which would require that he is allowed to do it his way without + major interference from others to keep the burdeon on him low. + + For backup and emergency he will give the root passwords to other + board members. + + Stuart would also be happy to take requests to improve things like the + web site according to ideas from our community provided he is + given the time to look around for the best existing software solution. +* Budget + + Discussion form previous week was continued and closed. + + People agreed that we don't have to make provisions for paid management + tasks as yet as current proposal leaves enough room to add these as + discretionary items. + + Egbert Eich agreed to provide insight into the data that he used for + his estimates. + + He will also turn the budget into a publishable form adding the minor + modifications discussed and circulate this to the board for apporval. + + A consensus exists that we need to work with the community to see + which events interesting for X.Org exist that we can use our funds for. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-01-17-2006.mdwn b/BodMeetingSummaries-01-17-2006.mdwn new file mode 100644 index 00000000..afab2d0f --- /dev/null +++ b/BodMeetingSummaries-01-17-2006.mdwn @@ -0,0 +1,67 @@ + + +[[!format txt """ +Summary of board telecon Jan 17, 2006. + +Attendees: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) (joined later) +Egbert Eich (EE) + +Subjects: +- Publication of conference summary +- Board meeting with sponsors +- How to deal with travel funding requests +- Conferences: + California + FOSDEM +- BoD travel expenses + +1. Conference Summaries + + The board decided to publish the summary of the Jan 10, 2006 + confcall as prepared by EE on the x.org wiki. + + Page needs to be write protected. SA created the BoD group to + be able to restrict write access to the board. + + BoD minutes can be linked to http://wiki.x.org/wiki/BodMinutes + +2. Board sponsor meeting. + + The XDevConf2006 in California provides a good opportunity to meet + with the sponsors. + + The board will have a face to face meeting on Tuesday, Feb 7, 2006 + in San Jose, California. + + It was decided to hold the Sponsors-BoD meeting on Thursday, Feb 9, 2006 + from 7:30 - (apporximately) 10:00 AM. + + SK will organize a meeting room in the building where the conference + will take place. + + The first talk on this day will be scheduled for 10:00 AM to give + the sponsors and BoD members the opportunity to attend all talks. + +3. Funding Request + + The board has received a request for travel funding to XDevConf + from Dave Airlie. Dave will give a presentation at the conference. + + Funding this in full would require us to spend 1/5 of our budget + set aside for this purpose. + + LS will communicating with Airlie regarding air fare and other costs + + LS reported that a group of X contributors at the GPLv3 meetings + confirmed that a strong policy providing travel support for meeting + participation was important. + + + LS will look for an inexpensive flight opportunity. + + SK will look for an opportunity to get additional funding + from SUN. + + SK will look for inexpensive accomodation. + +4. Conferences + + SK will investigate opportunities to get local people involved in + providing a better infrastructure for conference attendees. + + Information about the FOSDEM meeting were exchanged. + SK is interested in attending. + +5. BoD Travel Expenses + + LS requires funding for travel to attend the BoD meeting. + + It was confirmed that BoD members who don't have other sources + of funding can request support from the budget set aside for this. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-01-24-2006.mdwn b/BodMeetingSummaries-01-24-2006.mdwn new file mode 100644 index 00000000..fe736f77 --- /dev/null +++ b/BodMeetingSummaries-01-24-2006.mdwn @@ -0,0 +1,75 @@ + + +[[!format txt """ +Board Meeting 01-24-06 + +Attendees: +Stuart Kreitman (SK) +Leon Shiman (LS) +Jim McQuillan (JM) +KM Kevin Martin (KM) +Stuart Anderson (SA) +Egbert Eich (EE) + +Topics: +- Minutes/Summaries +- Travel funding +- Agenda for f2f board board+sponors meeting in California +- Conferences + +* Minutes/Summaries + - LS circulated minutes of last meeting to the BoD on Monday, 01-23-06. + They will be approved unless somebody objects by email. + - Summaries on BoD meetings for publication: + Focus on topics discussed, results and action items assigned. + EE has circulated draft of summary on 01-17-06 and will continue + to do so for future meetings. + Responsibilities of the secretary: + . take and circulate minutes of calls. + . make sure summaries are published. + +* Travel funding + - LS has worked with Dave Airlie on finding inexpensive transportation + opportuinites. Dave agreed to cover some of his costs himself. + Based on available transportation rates LS and Dave agreed that + X.Org will fund USD 1300. + Board members will work on finding a room sharing opportunity for Dave. + LS will add to agenda for follow up meeting: policy for travel funding + for future events. + +* Agenda for BoD face to face meeting at XDevConf2006 + a. Treasurer + Board decided that dependent on the issue if participation of + the treasurer is required a meeting with him will be arranged. + LS will therefore make up a list of issues to be discussed. + b. Rewrite of the bylaws. + - Proposals for organizational changes have been made which have + not been drafted in words yet. + - Architecture WG should be removed from the bylaws. + (The architecture board is still in place but not acting any more + as board members have agreed to assign the responsibilities to the + architecture working group.) + - Draft should be in time for the upcoming election for the members to + vote on. + c. Define role of the sponsors group. Some confusion about the role of + the sponsors seems to exist. + LS will collect and circulate further items/details. + +* Agenda for BoD - sponsor group meeting at XDevConf2006 + - Final agenda may depend on the outcome of the board f2f meeting. + - Some topics may require discussion with/feedback from the sponsors. + - LS will circulate preliminary list of topics together with the + BoD meeting topics to the board. + +* Conferences + + XDevConf + - Everybody should provide a short abstract for talk. + - People should also provide slides for proceedings on the web. + - SK will prepare preliminary talk schedule. Can be modified according + to requirements. + + Socal Linux Expo in LA, Californa Feb. 11-12 + - SK will attend and organize booth. + - LS will provide booth material. + - Others are welcome to join in booth activeties. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-01-31-2006.mdwn b/BodMeetingSummaries-01-31-2006.mdwn new file mode 100644 index 00000000..fb48636e --- /dev/null +++ b/BodMeetingSummaries-01-31-2006.mdwn @@ -0,0 +1,58 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon Jan 31, 2006 + +Present: +Leon Shiman (LS) +Jim Gettys (JG) +Jim McQuillan (JQ) +Stuart Kreitman (SK) +Stuart Anderson (SA) +Kevin Martin (KM) +Egbert Eich (EE) + +Agenda: +1. Minutes +2. Reimbursement requests for BoD travel +3. Expenses for LA show +4. Schedule and agenda review of f2f meetings +5. Should X.Org issue a statement on the software licensing + policy discussions presently going on? +6. Organizational issues regarding XDevConf. +7. SK FOSDEM travel funding +8. Reports on possible sponsoring opportunity + +1. Minutes + The minutes taken by LS are for internal use by the BoD. LS tries to + capture the conversation as close as possible and post them to the + BoD for review. He is asked to reword emotionally charged statements + such that they still capture the meaning without conveying the emotion + when requested. +2. BoD travel + SA asks for funding for accomodation. He will be sharing with LS and + Dave Airlie. BoD travel expenses have been budgeted. No objections. +3. Expenses for LA show + SK asks X.Org to pick up shipping expenses for the LA show. + Since there is a budget for this there is no objection. +4. Schedule and agenda for the BoD meetings. + Scheduling and location issues have been discussed for the BoD f2f + meeting, the BoD-sponsors meeting and a possible meeting of the BoD + with the treasurer. + An email thread has been created to add/clearify agenda items. +5. Software licensing issues + Currently numerous individuals and groups trigger discussions on open + source licensing issues should X.Org make an official statement. + X.Org will make no statement unless addressed directly BoD will make + sure any incorrect statements it discoveres are corrected. +6. Organizational issues regarding XDevConf + SK gives update XDevConf organization. + Conference moderation issues are discussed: schedule will be tighter than + on last years conference therefore talk and discussion afterwards need + to stay in given time frame. +7. SK FOSDEM travel funding + SK's airfare and hotel will be covered by SUN. He informs board that he + may need funding for other expenses. +8. A possible sponsoring opportunity was mentioned. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-02-14-2006.mdwn b/BodMeetingSummaries-02-14-2006.mdwn new file mode 100644 index 00000000..a52d06ff --- /dev/null +++ b/BodMeetingSummaries-02-14-2006.mdwn @@ -0,0 +1,35 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon Feb 14, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Jim Gettys (JG) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics: +1. Lenght of meeting +2. Report from SOCAL +3. X@FOSDEM +4. LWE Boston +5. XDevConf + +1. Agreed to have a brief meeting due to last week's travel and time demands. +2. SK attended SOCAL 2006 with an X.Org booth. Reported positive feedback. +3. No action required at this point. +4. LS reported that he received notice that IDG's Industry Advisory Group + did not approve .Org space for X.Org in the April LWE in Boston. The + decision was reportedly based on industry reports that X is only used + on unix and linux, and that freedesktop.org fully represents them. + SK took action item to investigate. LS will also investigate further. +5. BoD moved to officially thank SK and SUN for their effords to make this + year's XDevConf a success. + + + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-02-21-2006.mdwn b/BodMeetingSummaries-02-21-2006.mdwn new file mode 100644 index 00000000..671dbd3c --- /dev/null +++ b/BodMeetingSummaries-02-21-2006.mdwn @@ -0,0 +1,105 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon Feb 21, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics +------ +1. FOSDEM funding requests +2. IRS 501(c)(3) filing status / bylaws +3. Minute taking for the records of the organization +4. Proposal: reduce frequency of calls +5. Drafting proposal for travel funding policy +6. Timetable for board elections and bylaw ratification by + the members. +7. Follow up on the meeting with the sponsors to draft a + proposal for an advisory group. +8. LWE Boston (April) status + +1. FOSDEM funding + + Discussed funding request for FOSDEM: + Luc Verhaegen asked for USD ~550 to accomodate people attending + the HotHouse and DevRoom at FOSDEM. + Request was approved. + Daniel Stone requested partial funding of his airfare to FOSDEM. + Although this funding request was received rather late board + approved partial funding of USD 200 based on lowest available airfare + for the trip. + +2. IRS filings + + LS reported on the status of the IRS 501(c)(3) filings. Our legal + counsel has assigned one of his staff members to this issue. There + are still some issues to be resolved in connection with flaws in the + transition processes between predecessor organizations. Also + 'open software' is not a common purpose among organizations that + file for 503(c)(3). However problems to be expected. + Legal counsel will use bylaws in present state for filing. + The group that's working on the bylaw revision (KM, SA and EE) + would like to get in touch with legal counsel about open questions. + +3. Minute Taking for Records + + Issues about the level of details of the meeting minutes for the + records were raised. + LS reported from conversations with legal counsel that the + organization is responsible to keep records of its meetings that + it has applied due diligence to the issues it has dealt with. + Therefore the records need to contain enough to show the background + of an issue dealt with and the different roads to a resolution it + has considered taking. + LS will produce minutes containing enough background information + to show that. + EE will continue to produce notes for publications independently. + This serves as a check for omissions in either set. + Both should have been read and be approved by the time of the + next meeting. + +4. Proposals + + The proposal was made to reduce the frequency of the calls. + There was support for this among the board members. + +5. Travel funding Policy + + Board agrees that there is still room in approving the communication + with the contributors about the availability of funds for travel + support to X.Org developers events. + Considering that funding requests that were made came in in a rather + short timeframe for the event to attend it was agreed upon that + the organization should put together travel funding policies. + Some board members have some ideas on this issue. Issue was deferred + to email discussion. + +6. Election Timeframes + + People on both the election committee and the bylaw group will + work out a time table to syncronize bylaw ratification and board + elections. Their rough draft is pretty much in line with what LS + has drafted. + +7. Establishing an Advisory Board. + + LS circulated his minutes from the meeting with the sponsor + organizations of X.Org. He strongly suggests to the board to read + them to extract issues to see how to proceed on setting up an + advisory board. + +8. LWE Boston April 2006 + LS Received notice from LWE that the X.Org Foundation will be given + booth space there. X.Org will receive a room at no charge + to allow developers and contributors to X to meet. Preparation + should start soon. + Also it is proposed to hold an informal follow up meeting with + our sponsor organizations. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-02-28-2006.mdwn b/BodMeetingSummaries-02-28-2006.mdwn new file mode 100644 index 00000000..38b0ea12 --- /dev/null +++ b/BodMeetingSummaries-02-28-2006.mdwn @@ -0,0 +1,68 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon Feb 28, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics +------ +1. Approval of minutes and notes from last meeting +2. Report on exchange with assigned lawyer of SFLC +3. Bylaw workgroup (KM, SA, EE) report rewrite status +4. Report FOSDEM +5. Upcoming events + +1. Approval of minutes and notes + Minutes taken by LS and summary notes for publication by EE taken at + last call were approved. Also new minute format which does not list + individual statements but describes the course of the discussions and + the arguments looked at was approved. It was noted as notes and minutes + are taken independently that there may be slight differences due to + different perspectives of the authors. It was agreed that this should + not be a problem as long as the differences are insubstantial. + It also was noted that each one serves a different purpose. + +2. Report on exchange with assigned lawyer of SFLC + LS as secretary reported reported that SFLC has assigned Karen Sandler + as the laywer to help with the irc 501(c)3 filings and bylaw revisions. + She will look into what has been filed so far and if it may be useful + to redo things already done. + SA has been appointed as the contact to the legal counsel by the bylaw + workgroup. + +3. Bylaw workgroup (KM, SA, EE) report rewrite status + The bylaw workgroup reported that it had met 3 times already however + that further meetings are required to complete the task and provide + a draft for board and legal review. March 6, is the current target + date for completion. If there is a slip the board will be notified in + time. + Two of the bylaw workgroup members are also on the election committee; + since the completion of the bylaw revision is a prerequisite for the + election and is the more time consuming task the majority of the current + effords were spent on it. + +4. Report FOSDEM + SK and EE have attended the FOSDEM X HotHouse and DevRoom. It was + noted that the event was a big success, the HotHouse had attracted + more participants than expected. It provided a good opportunity for + developers to meet and exchange. The talks at the DevRoom were well + visited (some were crowded). + It was noted that there seems to be a disconnect between X.Org as + an organization and the people who are working for X.Org as a + development project. + The board formally thanks Luc Verhagen for the excellent job he + has done to organize the event. + +5. Upcoming events + X.Org has been invited to give a presentation at FOSE - a US government + trade show held in Washington DC (USA). + Also FISL at Brasil is coming up. JQ will be there and SK might. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-03-07-2006.mdwn b/BodMeetingSummaries-03-07-2006.mdwn new file mode 100644 index 00000000..c108c98a --- /dev/null +++ b/BodMeetingSummaries-03-07-2006.mdwn @@ -0,0 +1,36 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon March 07, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Jim Gettys (JG) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics +------ +1. Approval of minutes and notes of previous meeting +2. Discussion on first draft of the rewrite of the bylaws + +1. Minutes and notes approval + Board agreed to ratify the notes and minutes from the previous + meeting unless objections are raised within 24 hours after the + call. + +2. Bylaw discussions + The board received the initial draft of the bylaws from the bylaw + committee including a schedule for the ratification process. + This schedule includes period for public review and discussion. + The ratification will be concluded by a vote of the members. + The bylaw committee explained the changes made and collected the + initial feedback from board members. + It was noted that the current draft is not yet complete pending + the rewrite of one section and feedback from legal counsel on + specific questions. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-03-14-2006.mdwn b/BodMeetingSummaries-03-14-2006.mdwn new file mode 100644 index 00000000..20bc1459 --- /dev/null +++ b/BodMeetingSummaries-03-14-2006.mdwn @@ -0,0 +1,49 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon March 14, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics +------ +1. Recreation of Banner for booth. +2. Approval of minutes and notes for publication. +3. Further discussion on bylaw draft. + +1. Recreation of Banner + The main X.Org banner with logo for the LWE booth got lost and + therefore needs to be recreated. + The following suggestions were put on the table: + - Remove dated information (possibly candidates + lists of technologies, sponsors) + - Minimise cost of graphics work required, make it reusable. + LS will have the graphics work done and propose a new design to the + board. Board authorized funds. + The cost are estimated at USD 150 for the graphics work and + USD 600 for the printing. + +2. Approval of minutes + Notes for publication approved immediately, minutes approved if + no objections within 24h. + +3. Bylaws + Bylaw committee pointed out that closure on bylaws is prerequisite + for upcoming BoD election. Any delay will delay election thus because + of the tightness of schedule cooperation of board members is required: + Comments on bylaws not mentioned during this meeting are due by end + of day Wednesday (March 15, 2006). + Continued discussion of bylaws: - correction of numerous typos, + ambiguous and unclear wordings and phrases were discussed changes + were suggested or left for discussion by the bylaws committee. + Further issues to be included into the bylaws were mentioned. + Consensus on most issues was reached. Remaining issues are pending + further discussion by email. + LS agreed to send in his comments and suggestions. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-03-21-2006.mdwn b/BodMeetingSummaries-03-21-2006.mdwn new file mode 100644 index 00000000..35609e79 --- /dev/null +++ b/BodMeetingSummaries-03-21-2006.mdwn @@ -0,0 +1,61 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon March 21, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Jim Gettys (JG) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics +------ +1. Approval of minutes and notes from last meeting. +2. Changing the schedule for the upcoming election and bylaw approval. +3. Further discussion on bylaw rewwrite. + +1. Minute Approval + The different understandings of last weeks discussion on recreating + the banner were discussed briefly. + The group agreed that the points brought up last week were mere suggestions + and no final decision had been made. + LS will work together with Paul Swart (sponsor) on a draft. The graphics + work will be prepared by Ruth Shiman. + +2. Rescheduling the election process + Last year the date we aimed at for holding the election was during + June/July. The low turnout of the nomination process suggested + that the summer month may not be the right time for an election. + A lot of members seem to attend conferences or have planned vacation + during this time. + The board saw two possibilities to remedy this: either move the election + process to an earlier time (such as May) or to a later date in the fall. + + The board came to the conclusion that the old board should be allowed + to finish its business before summer without being hampered by the + election process. Then first thing in early fall the annual board + election can be held such that the new board can constitute itself + and start working. + + In our present situation this would have the additional benefit that + the schedule for the bylaw and membership agreement rewrite can be + more flexible giving us more time for public review and debate. + + September/October seems to be a good time for the election as it seems + to be suitable for people both on the northern and southern hemisphere. + +3. Further bylaw discussions + The initial draft of the bylaws presented by the bylaw committee + is almost complete now. + The majority of the board members have read the document. Issues + about details in wordings and the procedures outlined in the draft + were discussed and suggestions for modifications were put onto the + table. Discussions are expected to continue while the bylaw committee + is considering the suggested changes before the document will be + passed to X.Org's legal counsel for review. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-04-11-2006.mdwn b/BodMeetingSummaries-04-11-2006.mdwn new file mode 100644 index 00000000..5a516e5a --- /dev/null +++ b/BodMeetingSummaries-04-11-2006.mdwn @@ -0,0 +1,52 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon April 11, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Leon Shiman (LS) +Kevin Martin (KM) +Egbert Eich (EE) + +Topics +------ +1. Approval of Minutes and Notes +2. Further Schedule +3. Bylaw Status +4. Security Releases + +1. Approval of Minutes and Notes + No minutes have been taken on last call. Summary for publication + has been circulated just prior to call - will be arroved unless + issues are raised by email. LS will try to generate minutes from + EE's private notes. + +2. BoD discussed further schedule: + a. It was agreed that discussion of upcoming events should not take + place among the board but be held on a more open forum. + b. Bylaws have to be finished, including the membership agreement. + c. Work on reimbursement and spending policy needs to be done. + It was discussed how ideas should be collected: There are people + who could contribute valuable input outside of the board. + d. Further issues to be collected on the mailing list to be put + on agenda. + +3. Bylaws: + Bylaw committee incorporated comments collected on last call and + during the past two weeks. Document is almost ready for legal + review. Deadline for further comments has been set. Later comments + should not delay the process. + +4. Security Releases: + The issue of how to announce and make available security fixes has + come up in the community: the last security release has not yet + been made available on X.Org's official web site. + Resolution: + Among the security WG a volunteer should be found who'd willing + to be responsible for such announcements to be given access to + the X.Org web page. SA will make an announcement to the security + maling list. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-04-25-2006.mdwn b/BodMeetingSummaries-04-25-2006.mdwn new file mode 100644 index 00000000..ae8cb590 --- /dev/null +++ b/BodMeetingSummaries-04-25-2006.mdwn @@ -0,0 +1,83 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon April 25, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan n(JQ) +Leon Shiman (LS) +Kevin Martin (KM) +Egbert Eich (EE) + +Topics +------ +1. Moving more BoD discussions to email. +2. Bylaw review process. +3. State of X.Org machines. +4. Additional machines from SUN +5. Notes approval + +1. Moving more BoD discussions to email. + It was noticed that it is getting increasiongly difficult to hold + a board call as board members have other obligations at the time of + the call. + - Last weeks call was canceled. + - LS and EE announced that they will not be available for calls the + following two weeks. It was therefore suggested to cancel the next + two calls. + - Some board members were not able to join this call from the beginning. +p It was therefore decided to move more discussions to email which would + give people who cannot make it at the time the calls are scheduled to + participate in the discussions. + +2. Bylaw revision progrss + Bylaw committee announced it had received the last set of reviews from + board members. It will schedule a time for a call to discuss these issues. + +3. State of X.Org machines + Daniel Stone has repeatedly approached the board on the state of the + X.Org machines. Presently freedesktop.org acts as the canonical upstream + source for X.Org releases. + - ftp.x.org does not have the latest security patches + - www.x.org doesn't announce the availability of these patches. + Daniel pointed out that people looking for the availability of security + fixes will normally check the projects main web site. + Not announcing the availability of security patches there may in + give those people a false sense of security. + Therefore he started a discussion on the X.Org security mailing list + making suggestions on how to remedy this problem. + The board decided to move the discussion on how the community would + loke to see the X.Org machines used to a larger audience. It was + furthermore decided that the mailing list xorg@freedesktop.org + would be the right audience. + KM will make an announcement on the security mailing list suggesting + to move the discussion and to repost the messages that were exchanged + on the security mailing list on this matter to xorg@freedesktop.org + if noone objects. + Furthermore it was decided to not start a separate discussion on + the web server issue as both matters belong together. + +4. SK reported that the machines donated to X.Org by SUN Microsystems + had been shipped to MIT. These machines are explicitely titled to + MIT and thus cannot be moved to a different location. + He also mentioned that they are equipped with remote management + facilities. + Thus they only require physical attendance for the initial setup + and the configuration of the remote management console. + The taks to do this has not yet been assigned to anyone. + SK furthermore mentioned that SUN would like to see OpenSolaris to + be the OS used on these machines to demonstrate the capabilities + of this other open source OS. + It was pointed out that this would make it more difficult to find + people who are willing to administrate these machines as the expertise + in OpenSolaris is not too pelntyful in our community. + +5. Notes approval. + The notes of the last board meetings have not been read by all board + members. Since they had been circulated almost two weeks ago it was + decided that if no objection was raised within 24 hours they would + be approved for publication. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-05-16-2006.mdwn b/BodMeetingSummaries-05-16-2006.mdwn new file mode 100644 index 00000000..b34263d8 --- /dev/null +++ b/BodMeetingSummaries-05-16-2006.mdwn @@ -0,0 +1,66 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon May 16, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQuillan (JQ) +Leon Shiman (LS) +Kevin Martin (KM) +Egbert Eich (EE) + +Topics +------ +1. Approval of Notes from +2. Bylaws +3. Press Release for 7.1 release. +4. Status of Mirroring +5. Misc +6. State of Machines from SUN. + + +1. Approval of Notes from April 24 + Notes circulated on April 27. Although not everybody has read the + notes no extension of review period has been requested. + +2. Bylaws + Issue was tabled as bylaw committee has not made any progress + since last meeting due to other committments. Due to urgent work on + the 7.1 release KM will be unable to join a meeting before next + week. + +3. Press release for 7.1 release + KM described the progress of the 7.1 release. Release is scheduled + for the coming Friday if everything runs on schedule. The question + was brought up if provisions need to be made for the press release + as in the past X.Org avoided weekends when making press releases. + It was pointed out that media are expected to pick up press releases + at any time. It was decided to contact Ajax as release manager if + sees any issues. + +4. Status of Mirroring + After the issues with the directory structure on freedesktop.org + have been resolved mirroring of the release tree has been started. + +5. Misc. + LS reported that on his trip to Europe he met a corporate group + from South Korea that is very intereseted to participate in our + community and possible also become a sponsor. + Cultural and language barriers exist. Mentoring may be required. + Furthermore LS reported on a group from St.Petersburg he has met + on LinuxTag that is also very interested in participating in the + X.Org community. Since the group has been busy manning a booth + they were unable to visit the X.Org booth to meet with people + from the community. + No immediate action by the board required. + +6. State of Machines from SUN + LS will schedule a meeting with Ajax at MIT to introduce him to + the location and get him access. It is planned to rack the SUN + machines at this time. + SK reported that he found issues with the remote management unit + of those machines. If remote management is not possible over the + network a remote dump terminal facility may be required. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-05-30-2006.mdwn b/BodMeetingSummaries-05-30-2006.mdwn new file mode 100644 index 00000000..09a64d3b --- /dev/null +++ b/BodMeetingSummaries-05-30-2006.mdwn @@ -0,0 +1,41 @@ + + +[[!format txt """ +Notes form X.Org BoD telecon May 30, 2006 + +Present: +Stuart Kreitman (SK) +Jim McQuillan (JQ) +Leon Shiman (LS) +Kevin Martin (KM) +Egbert Eich (EE) + +Topics +------ +1. Portland Machine +2. Bylaws +3. Status of Machine at MIT +4. Notes from last Meeting +5. Next Meeting + +1. State of Portland Machine + Discussed machine at Portland State and remote management facilities + of the new SUN machines. + +2. Bylaws + Decided to move bylaw discussion to next meeting since the latest + version has not been circulated. Otherwise bylaw committee is in + good shape. + +3. Status of Machine at MIT + No news as Adam who volunteered to help racking it was busy so far. + +4. Notes from last Meeting + Notes from last meeting will be approved unless objections filed until + Friday. + +5. Next Meeting + It was agreed to close this meeting early. + The next meeting will probably be in two weeks. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-07-14-2006.mdwn b/BodMeetingSummaries-07-14-2006.mdwn new file mode 100644 index 00000000..01e2f2aa --- /dev/null +++ b/BodMeetingSummaries-07-14-2006.mdwn @@ -0,0 +1,59 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon July 14, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim Gettys (JG) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics +------ +1. Bylaw Subcommittee Report +2. Planning an F2F Meeting this Year +3. Board Elections +4. Status Incorporation Documents / other unfinished Business +5. Status of Server at MIT + +1. Bylaw Subcommittee Report + The bylaw subcommittee has received feedback from the laywer. + The feedback was discussed issues that the subcommittee felt + it was unable to solve itself were posted back to the laywer + with questions and comments. + +2. Planning of F2F Meetings this Year + There will be no f2f meeting of the board at OLS as not all members + will be there. The next phone meeting will be scheduled for Jul, 25th. + +3. Board Elections + The election process will not start until after the summer (ie. middle + of August). Election subcommittee will meet in Ottawa to discuss + schedule details. + JG is presently looking into the election software that is used by + the Gnome Foundation. + +4. Status Incorporation Documents / other unfinished Business + LS hopes to be able to have the Incorporation Documents + which include the non profit status documents and the paperwork + for the IRS filings ready for the next meeting. + He will also refile the applications to give SK counter signature + authority for money transfers with our bank. + Recent difficulties with money transfers were discussed. LS assured + the board that the procedures the bank applied for money transfers + were reasonable and were not the cause of the delays. + +5. Status of Server at MIT + The status of the servers at MIT were discussed. + SA would like to reinstall expo. The current setup is suboptimal + which caused the delay in email delivery to the board when mailman + died due to a full root fs. + The SUN machines have not been mounted in the racks, yet. Adam Jackson + who volunteered to do this together with LS was busy with other things. + SK asks to run OpenSolaris on the SUN machines. He will take over the + responsibility to administrate these machines. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-08-08-2006.mdwn b/BodMeetingSummaries-08-08-2006.mdwn new file mode 100644 index 00000000..8923f326 --- /dev/null +++ b/BodMeetingSummaries-08-08-2006.mdwn @@ -0,0 +1,62 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon August 8, 2006 + +Present: +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim Gettys (JG) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics: +======= + +1. Khronos/VESA Membership +2. Status of Corporation +3. Status of bylaws +4. Election Process +5. Next X Developers conference. + +1. Khronos/VESA Membership + It was suggested (and discussed among X developers attending DDC) that + it may be worthwhile for X.Org to become a member of Khronos the + organization that is currently steering OpenGL and related standards. + Standards passed by Khronos and technologies developed by X.Org may + directly affect each other, therefore it is desirealbe that X.Org + participates in the discussion of standards early. + It was decided to assing to KM and SK the taskt to explore on what + terms and conditons X.Org can cooperate with Khronos. + Furthermore it was briefly discussed if X.Org should become a member + of VESA or if it was sufficient for X.Org to have funds to purchase + relevant specifications: although there may not be a reason for X.Org + to actively drive standards it may be importand to know early in advance + what technologies to expect. SK and EE were assigned the task to explore + this issue further. + +2. Status of Corporation + LS reported on the progress of the status of the filing of the + incorporation: LS is closely working together with our legal counsel + to work out the details and obtain documents that are still missing. + +3. Status of bylaws + After receiving a reply from the lawyer the bylaw committee will + meet this week. It hopes to be able to draft a final version avaliable + before the next call. + +4. Election Process + As the election schedule is closely tied to the bylaw process + the election subcommittee will draft a schedule once the bylaw + subcomittee has completed its work. + +5. Next X Developers conference. + SK reported that he would be happy to organize another X developers + conference hosted by SUN Microsystems. + It was also noted that X.Org should to foster more local X developers + conferences in different parts of the world - like this year on FOSDEM + in Brussels by providing financial and logistical support and encourage + local community members to step up and organize such an event. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-08-15-2006.mdwn b/BodMeetingSummaries-08-15-2006.mdwn new file mode 100644 index 00000000..ab1df70b --- /dev/null +++ b/BodMeetingSummaries-08-15-2006.mdwn @@ -0,0 +1,38 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon August 15, 2006 + +Present: +Stuart Anderson (SA) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics: +======= + +1. Publication of Bylaws for Public Review +2. Members Mailing List + +1. Publication of Bylaws for Public Review + The bylaw subcommittee has finished the bylaw rewrite. The + board has approved the latest version to be publisehd for + public review and discussion pending a last legal review. + For public discussion a list bylaws_at_x_dot_org will be + created. Subscription to this list is open to the public + (not just members). The members as well as other mailing + lists will be notified of this list and people will be invited + to subscribe themselves to participate in the discussion. + The election schedule will be updated accordingly. + The revised Membership Agreement will be published to the + board after review by the counsel. + Once the board has approved it will be published for public + discussion on the same forum. + +2. Members Mailing List + SA will reinstate the members mailing list. The list will + have the name members_at_x_dot_org. instead of xf_members_at_. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-08-22-2006.mdwn b/BodMeetingSummaries-08-22-2006.mdwn new file mode 100644 index 00000000..19cf6906 --- /dev/null +++ b/BodMeetingSummaries-08-22-2006.mdwn @@ -0,0 +1,34 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon August 22, 2006 + +Present: +======== + +Stuart Anderson (SA) +Jim McQuillan (JQ) +Kevin Martin (KM) +Leon Shiman (LS) +Stuart Kreitman (SK) +Egbert Eich (EE) + +Topics: +======= + +1. Bylaw discussion and Election Schedule + +1. Bylaw discussion and Election Schedule + The results from the call from the previous week were rehashed + together with the proposed schedule. It was made clear that + the membership registration process will be opened before the + nominations for board members start so that people interested + in nominating a candidate or running can apply for membership. + + The bylaw discussion will open to everyone - if presently member + or not. + The secretary will prepare a public announcement as soon as + possible as we have already lost a week since this procedure + was agreed upon. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-08-29-2006.mdwn b/BodMeetingSummaries-08-29-2006.mdwn new file mode 100644 index 00000000..a712345a --- /dev/null +++ b/BodMeetingSummaries-08-29-2006.mdwn @@ -0,0 +1,78 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon August 29, 2006 + +Present: +======== + +Stuart Anderson (SA) +Jim McQuillan (JQ) +Jim Gettys (JG) +Kevin Martin (KM) +Leon Shiman (LS) +Stuart Kreitman (SK) +Egbert Eich (EE) + +Topics: +======= + +1. Official Financial Statement for IRS/Incorporation Filings +2. Trademark issues +3. Public By-Law Draft Discussion Announcement +4. Membership Management Infrastructure +5. Membership Application Review +6. Nomination Statements +7. Electronic Election Infrastructure +8. Administrative Issues: Mailinglist Infrastrucutre + +1. Official Financial Statement for IRS/Incorporation Filings + The board approved USD 2500 for an official financial statement + required for IRS and Incorporation filings. Our legal advisor + has (SFLC) has recommended a company to us which will provide + these services for a favorable rate. The amount is below of what + had been budgeted. + +2. Trademark issues + The letter 'X' and the term 'X11' is used in numerous contexts in + the IT world. The board needs to schedule a meeting with out legal + advisors so that we can discuss any legal implications on us. + +3. Public By-Law Draft Discussion Announcement + LS reported that the announcement for the bylaw discussion has been + sent to xorg@freedesktop.org (via Daniel Stone) as well as to the + members, the board and the sponsors. Only a few email addresses + of members were not available and bounced. + +4. Membership Management Infrastructure + SA reported that his work on the membership management infrastructure + is making progress. Some pieces are in place already and have been + made available to the board members for testing. + +5. Membership Application Review + The new board will have to extablish procedures for membership + application review. A possible solution would be to have a membership + review WG that doesn't consist of board people only but of members + who are not on the board also. + Since there is not enough time to establish this group in time before + the upcoming election the board will serve as an application review + board until the new board has constituted istself. + +6. Nomination Statements + The election subcommittee will work out the details and send out + make an announcement on Sept. 4th. This will be published to xorg@, + the the members and the board. + +7. Electronic Election Infrastrucutre + Likewise the election subcommittee will research software for an + electronic interface. It will report its findings to the board. + LS had prepared the frist electronic election and was involved in + the preparation of the election last year. He will recollect issues + that came up and note down his experience and publish this information + to the election subcommittee. + +8. Administrative Issues: Mailinglist Infrastructure + The issues mailman had with the security list are not related to + a lack of administration but to a bug in mailman. The issues will + be reported to the mailman maintainers. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-09-05-2006.mdwn b/BodMeetingSummaries-09-05-2006.mdwn new file mode 100644 index 00000000..d8202c2a --- /dev/null +++ b/BodMeetingSummaries-09-05-2006.mdwn @@ -0,0 +1,43 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon September 5, 2006 + +Present: +======== +Leon Shiman (LS) +Kevin Martin (KM) +Stuart Kreitman (SK) +Jim McQillan (JQ) +Egbert Eich (EE) + +Topics: +======= + +1. Public By-Law Review +2. X.Org Trademark Issues +3. Membership Management + +1. Public By-Law Review + Resonance on the public bylaw review has not been very big. + One issue broad up was that the new bylaws have a one minimum + year membership requirement for people who whould like to run + for the board. People found this not very realistic as they feel + that many individuals who have been active in the community may not + bother to become members until shortly before the election. + One possible solution may be to + * require membership only at the time of the election + * base eligibility on active participation (that would qualify + for membership) + * reduce the period to 6 month. + KM will draft and publish an updated wording. + +2. X.Org Trademark Issues + The discussion on this topic continued. + +3. Membership Management + SA has added some more pieces to the membership management + infrastructure. + The board would like to express its appreciation for his effords. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-09-26-2006.mdwn b/BodMeetingSummaries-09-26-2006.mdwn new file mode 100644 index 00000000..c1a20910 --- /dev/null +++ b/BodMeetingSummaries-09-26-2006.mdwn @@ -0,0 +1,56 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon September 26, 2006 + +Present: +======== +Leon Shiman (LS) +Kevin Martin (KM) +Stuart Kreitman (SK) +Stuart Anderson (SA) +Jim McQillan (JQ) +Egbert Eich (EE) + +Topics: +======= +1. Membership Applications +2. Status of IRS Filings and Incorporation +3. Debate over LS's Request for Travel Funding for LWE, Colone, Germany. + +1. Membership Applications + The new system for Membership Renewal and Application has been set up. + Requests for Renewal as well as new applications are coming in. Debate + sparked on the issue which criteria to apply to new applications. To + meet the requirements for non profit the organization may not be able + to apply too strict rules. + It was pointed out that it should be left to the Committee which decides + over the applications to determine the policies and reevaluate them from + time to time. + It was decided that the Board Members who are up for reelection this + year should not participate in the decisions over the acceptance or + rejection of applications. + +2. Status of IRS Filings and Incorporation + LS waiting for the legal counsel to finish the work and get back to him. + +3. Debate over LS's Request for Travel Funding for LWE, Colone, Germany. + LS had requested USD 500 to cover the costs for his accomodation at + Colone. + Objections were raised: X.Org did not have a sponsorship program. + Without that Board Members were at an advantage when applying for + sponsorship as they knew about this opportunity and had direct + access to the Board. + EE proposed to instead set aside a fund of USD 1000 for travel + sponsorship and advertise the sponsorship opportunity to the + community. Furthermore to bring in as many people as possible + the focus of funding should be on the local community. + LS pointed out that LWE had approached him about the booth but time + to accept the offer was running out. Therefore there wasn't enough + time to wait for the Board to decide over the distribution of the + funds. + No resolution was reached. + SK will submit an alternative motion to the BoD mailing list which + would allow to award USD 500 to LS in advance distributing the rest + to other applicants. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-10-03-2006.mdwn b/BodMeetingSummaries-10-03-2006.mdwn new file mode 100644 index 00000000..3bddcd07 --- /dev/null +++ b/BodMeetingSummaries-10-03-2006.mdwn @@ -0,0 +1,48 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon October 3, 2006 + +Present: +======== +Stuart Kreitman (SK) +Kevin Martin (KM) +Jim McQuillan (JQ) +Jim Gettys (JG) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics: +======= +1. Unified Copyright Clause +2. Progress on Election Process +3. Trademark Issues + + +1. JG broad up the issue that X.Org should: + a. come up with a unified author neutral license clause. + b. unify all license clauses of copyrights it owns. + c. should work with companies that have donated code to + the X Window System to get their consent to change or + subsume their license clauses under the common form. + d. resolve the issue with the non-GPL compatible SGI license + e. advicate that all contributors use the same license clause. + To do this a public discussion on this issue ought to be + started to come to a consenus among a. individual contributors + b. corporations that contribute or have contributed code. + JG will kick this off. + It was noted that several files still seem to contain reference + to 'The Open Group'. LS reported that all those copyrights should + have been changed to X.Org when X.Org was created as a subgroup + of X.Org. EE will reasearch which files still contain TOG copyright/ + license clauses, LS will contact TOG to confirm their consent. + +2. Progress on Election Process + By-Law committee reported that it is about to schedule a last + meeting to review results from consulting our legal counsel. + Also the outcome of the public review needs to be discussed. + A meeting will be scheduled by the By-Laws committee for later + in the same week. + +3. The Board continued discussion on issues around trademarks. +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-10-10-2006.mdwn b/BodMeetingSummaries-10-10-2006.mdwn new file mode 100644 index 00000000..39f330f3 --- /dev/null +++ b/BodMeetingSummaries-10-10-2006.mdwn @@ -0,0 +1,57 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon October 10, 2006 + +Present: +======== + +Stuart Kreitman (SK) +Stuart Anderson (SA) +Kevin Martin (KM) +Jim McQuillan (JQ) +Jim Gettys (JG) +Leon Shiman (LS) +Egbert Eich (EE) + +Topics: +======= + +1. By-Laws/Membership Agreement final version + +1. By-Laws/Membership Agreement final version + The Membership Agreement has not received any public review, therefore + it is urgent to get this out to the voters. The subcommittee has met + again and incorporated the results of the public discussions into the + By-Laws and completed the rewrite of the Membership Agreement + incorporating the results from legal review and sentiments expressed + during the By-Law public review. + Some minor issues were noted by Board Members: + 1. Minor grammar glitches were noted in the By-Laws. + 2. Grammer in section 2 of the Membership Agreement needs to be improved. + 3. The Membership Agreement doesn't mention explicitely that Members + are allowed to chair committees (as it is expressed in the By-Laws). + This will be added. + 4. Section 5a was unclear to some Board Members. It was decided to + take it to the lawyer for a rewording. Also it was expressed that + the second sentence should probably be removed as the first one + only refers to X.Org related activeties and does not touch other + contractual relationships between Members. + Since time is short it was agreed to fix points 1-3 and publish this + version for review noting that it is still preliminary and section + 5a is still under review. + +2. Incorporation Issues + LS reported that he is still waiting for the accounting data from + our treasurer. EE has agreed to work with the treasurer to help + converting it into the right format. + Furthermore it was pointed out that former Board Members need to + return their Membership Certificates. A discussion came up around + the meaning of this certificate and how it should be stored. + It was pointed out that this certificate is comparable to a share + as it certifies that one is the owner of part of the organization. + It was agreed upon that after all paperwork about registration + is done it needs to be investigated how to record this ownership + in a way that doesn't require such documents. + +"""]]
\ No newline at end of file diff --git a/BodMeetingSummaries-10-17-2006.mdwn b/BodMeetingSummaries-10-17-2006.mdwn new file mode 100644 index 00000000..641eea64 --- /dev/null +++ b/BodMeetingSummaries-10-17-2006.mdwn @@ -0,0 +1,52 @@ + + +[[!format txt """ +Notes from X.Org BoD telecon October 17, 2006 + +Present: +======== +Stuart Kreitman (SK) +Stuart Anderson (SA) +Kevin Martin (KM) +Jim McQuillan (JQ) +Jim Gettys (JG) +Leon Shiman (LS) +Egbert Eich (EE) + +1. Missed Nominee for BoD Meeting. +2. Status of Membership and By-Laws Document +3. Copyright/License Consolidation +4. Financial Reporting + +1. Nominee Missed + The Election Committee has checked log files and archives but was + not able to find any indication of a nomination of Christophe Suter + by Paul Schenker. The investigations will continue and the committee + will work with Paul Schenker to resolve the issue. It was further + noted that Christope Suter is not yet a member. Should this nomination + have been lost, the candidate will be given the opportunity to + register. + EE replied to the notification on the members mailing list asking + for more details however no answer has been received, yet. + +2. Status of Membership and By-Laws Document + The public review of the By-Laws have been completed and the text + has been amended. Public review of the Membership document is + still under way. Some clauses raised questions. Since SA is currently + involved with election preparation EE has contacted the legal counsel + about these. + The results will be posted directly to the bylaws mailing list. + +3. Copyright/License Consolidation + Questions have come up among the board about the skope of this. + It was made clear that there is no intention to change any + Copyrights which wuld not be possible. + The intention is to consolidate the different MIT license texts + that are contained in one single source file into one worded + vendor neutrally. JG has made a proposal for this. + +4. EE has reviewed the books. Since these are done in Gnucash it is + a rather tedious undertaking to generate reports. LS needs to + clearify what information is required for the incorporation. + He will communicate with EE in private. +"""]]
\ No newline at end of file diff --git a/BuildingXtest.mdwn b/BuildingXtest.mdwn new file mode 100644 index 00000000..1db794fa --- /dev/null +++ b/BuildingXtest.mdwn @@ -0,0 +1,112 @@ + + +## Check out the XTS code + +The XTS uses autotools and can be obtained with: + + +[[!format txt """ +$> git clone git://anongit.freedesktop.org/git/xorg/test/xts +$> cd xts +$> ./autogen.sh +$> make +$> make run-tests +"""]] +The first "make" command builds the sources, "make run-tests" executes all the tests. Results are stored in the results/ directory under the current timestamp (e.g. results/2010-04-19-18:19:08/). Note that XTS does not need to be installed, if you do want to do so you're encouraged to pick the appropriate installation prefix for your distribution. + +For more information, see the README in the xts repository. + + +## Running a subset of tests + +The tests are divided into protocol tests, Xlib (per chapter) and extension tests. Each of these subsection can be run separately with the _make test-<section>_ command. e.g. make test-Xlib13 will only run the Xlib13-related tests. + + +## CVS version of the XTS + +_The following information refers to the CVS, non-autotooled version of the XTS. We do not recommend using this version._ + +Anonymous CVS is available from: +[[!format txt """ +cvs -z3 -d:pserver:anoncvs@anoncvs.freedesktop.org:/cvs/xtest login +cvs -z3 -d:pserver:anoncvs@anoncvs.freedesktop.org:/cvs/xtest co xtest +cd xtest +export TET_ROOT=`pwd` +export PATH=$TET_ROOT/bin:$TET_ROOT/xts5/bin:$PATH +make +cd xts5 +"""]] +(This won't install anything outside of the checkout tree.) This creates an assortment of journal files with the output from the various build commands. Hopefully that will go away eventually, but in the meantime look in xts5/results. Use `CFLOCAL=<cflags>` to set local C compiler flags (for example `-g`) (**NOTE:** this is only supported for xts5 not for tet). + + +### Additional Requirements + +The XTS code uses a call to `_XConnectDisplay`. This function is provided by libX11, but only if libX11 was compiled **without** XCB support (`--with-xcb=no`). + + +## Build the supporting libraries and binaries + +Make sure you have a fonts.dir in your fonts directory. Which format the fonts need to be in depends on which X server you're using. If you don't know what to pick, this command will probably take care of everything for you: +[[!format txt """ +make -C fonts comp_pcf +"""]] +(I had to edit out the *.bdf entries of the fonts.dir to make Xfake happy. With other X servers, YMMV.) + + +## Running the test cases + +Start an X server to run the tests against. Remember that if you have an X server running on :0, you'll need to pick another display for this test server: let's assume you picked :1. It's also easiest to disable access control with the -ac flag. Note that you may want to run the tests with multiple screens, which can be easily accomplished using Xvfb or Xfake. Here are a few sample X server invocations: +[[!format txt """ +Xvfb -screen 0 640x480x24 -screen 1 640x480x8 -ac :1 +Xfake -screen 640x480x16 -screen 640x480x16 -ac :1 +"""]] +Now you need to make sure that tetexec.cfg matches your test X server. The xts-config script can fill in most values automatically by querying the running X server. Anything it can't handle it leaves unchanged, so you can intersperse xts-config runs with hand-edits safely, and comments are preserved as well. +[[!format txt """ +DISPLAY=:1 xts-config tetexec.cfg +"""]] +You still need to review tetexec.cfg after running xts-config, because if your xdpyinfo and xset binaries use the same Xlib that you want to test, or your X server is reporting weird values, the test suite may report PASS on tests that should have FAILed. In other words, if you don't review the resulting tetexec.cfg file, your test results may be _invalid_. + +Assuming that your X server is running locally, the default delays in tetexec.cfg are much higher than they need to be. On local tests you can safely set XT_SPEEDFACTOR and XT_RESET_DISPLAY to 1 instead of the default 5. This will make the test suite run somewhat faster. + +Finally, you can run the test suite using +[[!format txt """ +tcc -e +"""]] +You can run subsets of the test suite by picking a subset from the tet_scen file, and then passing the subset name as a parameter +[[!format txt """ +tcc -e xts5 <subset> +"""]] +A (re)build of all scenarios can be started with +[[!format txt """ +tcc -b +"""]] + +## Running and Debugging Individual Test Cases + + +[[!format txt """ +run_assert XGetGeometry 4 +"""]] + +[[!format txt """ +cd tset/Xlib5/gtgmtry +TET_CONFIG=tetexec.cfg gdb Test +"""]] +alternatively, one can run +[[!format txt """ +cd xtest/xts5/tset/path/to/testcase +xtest/xts5/src/bin/scripts/pt -i 3 # run testcase t003() of the Test binary. +"""]] + +## Reviewing the Results + +Use the vswrpt command (which should now be in your path) to see the results of the test run. + + +## Cleaning the test cases + + +[[!format txt """ +tcc -c +make clean +"""]]
\ No newline at end of file diff --git a/BylawReview.mdwn b/BylawReview.mdwn new file mode 100644 index 00000000..52379962 --- /dev/null +++ b/BylawReview.mdwn @@ -0,0 +1,29 @@ + +The X.Org Foundation has been operating under a set of Provisional By-laws since it's formation. Recently, these By-laws have undergone a thorough review, which has resulted in a major revision that better reflects the organization and how it operates. + + +## By-Laws + +The Board of Directors is pleased to present these revised By-laws for public comment and discussion. All discussion shall take place on the [[bylaws@x.org|mailto:bylaws@x.org]] mailing list, which is open to everyone. Anyone interested in commenting on these By-laws is asked to join the mailing list at [[http://x.org/cgi-bin/mailman/listinfo/bylaws|http://x.org/cgi-bin/mailman/listinfo/bylaws]]. + +The discussion period for this review shall run through 10 September 2006. The By-laws will be submitted to the members for approval in the upcoming election which will be held later this year. + +* [[ProposedBylaws.pdf|ProposedBylaws.pdf]] +Revisions to the By-laws have been made as a result of the public review. The revised version is available here + +* [[ProposedBylawsRevised20061009.pdf|ProposedBylawsRevised20061009.pdf]] +* [[ProposedBylawsRedlinedvs20060811.pdf|ProposedBylawsRedlinedvs20060811.pdf]] +Unless there a critical issue, this will most likely be the version that will be put up for ratification as part of the upcoming election. + +A couple of very minor editorial and formatting changes have been made. The version that will appear on the ballot is here + +* [[ProposedBylawsRevised20061029.pdf|ProposedBylawsRevised20061029.pdf]] +_**This version was approved on 14 November 2006**_ + + +## Membership Agreement + +The Board of Directors is also ready to present a revised Membership Agreement for public review. The discussion period for the Membership Agreement will end 20 October 2006. Discussion shall take place on the bylaws mailing list described above. + +* [[ProposedMembershipAgreement.pdf|ProposedMembershipAgreement.pdf]] +Discussion is still ongoing for the Membership Agreement, so a seperate ballot will be opened for it once the discussion and review have concluded. diff --git a/BylawReview/ProposedByLawsRevised20061029.pdf b/BylawReview/ProposedByLawsRevised20061029.pdf Binary files differnew file mode 100644 index 00000000..d33ba841 --- /dev/null +++ b/BylawReview/ProposedByLawsRevised20061029.pdf diff --git a/BylawReview/ProposedBylaws.pdf b/BylawReview/ProposedBylaws.pdf Binary files differnew file mode 100644 index 00000000..9624b72b --- /dev/null +++ b/BylawReview/ProposedBylaws.pdf diff --git a/BylawReview/ProposedBylawsRedlinedvs20060811.pdf b/BylawReview/ProposedBylawsRedlinedvs20060811.pdf Binary files differnew file mode 100644 index 00000000..62bdd6f4 --- /dev/null +++ b/BylawReview/ProposedBylawsRedlinedvs20060811.pdf diff --git a/BylawReview/ProposedBylawsRevised20060811.pdf b/BylawReview/ProposedBylawsRevised20060811.pdf Binary files differnew file mode 100644 index 00000000..9624b72b --- /dev/null +++ b/BylawReview/ProposedBylawsRevised20060811.pdf diff --git a/BylawReview/ProposedBylawsRevised20061009.pdf b/BylawReview/ProposedBylawsRevised20061009.pdf Binary files differnew file mode 100644 index 00000000..02fba4ce --- /dev/null +++ b/BylawReview/ProposedBylawsRevised20061009.pdf diff --git a/BylawReview/ProposedBylawsRevised20061029.pdf b/BylawReview/ProposedBylawsRevised20061029.pdf Binary files differnew file mode 100644 index 00000000..d33ba841 --- /dev/null +++ b/BylawReview/ProposedBylawsRevised20061029.pdf diff --git a/BylawReview/ProposedMembershipAgreement.pdf b/BylawReview/ProposedMembershipAgreement.pdf Binary files differnew file mode 100644 index 00000000..3695f7a7 --- /dev/null +++ b/BylawReview/ProposedMembershipAgreement.pdf diff --git a/CategoryCategory.mdwn b/CategoryCategory.mdwn new file mode 100644 index 00000000..c832b9cc --- /dev/null +++ b/CategoryCategory.mdwn @@ -0,0 +1,8 @@ + +A category is a [[WikiName|WikiName]] that exploits [[!c2 WikiWiki desc="WikiWiki"]]'s reverse linking. If you click on the title of a category page, you'll get a list of pages belonging to that category. To get a list of all categories, click above on the Category****Category title. + +Here is a list of all categories known to this wiki: [[!inline pages="link(CategoryCategory)" quick feeds="no" archive="yes"]] + +Here is a list of all pages containing the CategoryCategory wiki tag: + +To be consistent with the C2 category scheme, all categories start with the word "Category". For more information, see [[!c2 AboutCategoriesAndTopics desc="AboutCategoriesAndTopics"]]****. diff --git a/CategoryHomepage.mdwn b/CategoryHomepage.mdwn new file mode 100644 index 00000000..2045d34c --- /dev/null +++ b/CategoryHomepage.mdwn @@ -0,0 +1,15 @@ + +A category for [[WikiHomePage|WikiHomePage]]****s. + +Note that such pages are "owned" by the respective person, and should not be edited by others, except to leave a message to that person. To do so, just append your message to the page, after four dashes like so: + + +[[!format txt """ +---- +Just saying Hi! -- JürgenHermann +"""]] + + +--- + + [[CategoryCategory|CategoryCategory]] diff --git a/CategoryServerInternals.mdwn b/CategoryServerInternals.mdwn new file mode 100644 index 00000000..2fce4a29 --- /dev/null +++ b/CategoryServerInternals.mdwn @@ -0,0 +1,12 @@ + +The following pages describe internals of the server in some detail. + +To add a page to this category, add a link to this page on the last line of the page. You can add multiple categories to a page. + +**List of pages in this category:** [[!inline pages="link(CategoryServerInternals)" quick feeds="no" archive="yes"]] + + + +--- + + [[CategoryCategory|CategoryCategory]] diff --git a/CodingStyle.mdwn b/CodingStyle.mdwn new file mode 100644 index 00000000..7d351c39 --- /dev/null +++ b/CodingStyle.mdwn @@ -0,0 +1,22 @@ + +This page describes the X server's current coding style. While the server was recently reformatted to fit this style, most modules have varied and disparate coding styles. Above all, the cardinal rule is to fit in: make sure your changes reflect the coding style of the surrounding code. + +We use the `indent` command line in this script here: [[http://cgit.freedesktop.org/xorg/util/modular/tree/x-indent.sh|http://cgit.freedesktop.org/xorg/util/modular/tree/x-indent.sh]] with manual editing afterwards to fix the cases where indent gets hopelessly confused. + +* Four-space indents (no tabs, not even if your editor wants to collapse eight consecutive spaces down to a single tab) +* 78-column limit +* Function return type (and any modifiers, eg `static`) on a line by itself +* Opening curly brace on the same line as the control construct: `if (foo) {` + * Closing braces aligned with the keyword that opened them (K&R not GNU) + * `else` on a new line from the closing } of the preceding `if` (i.e. not cuddling) +* Opening curly brace for functions in column 0 +* Keywords punctuated like `if (x >= 0)` +* Functions punctuated like `doSomethingClever(a, b, c);` +* `case` aligned in the same column as the `switch` +* If wrapping is required, function arguments to be aligned to the opening parenthesis of that column +* Wrap structs in typedefs +* C-style <span style="display:none">foo</span> comments, rather than C++/C99-style // foo +* C89 + some extensions, see [[http://cgit.freedesktop.org/xorg/xserver/tree/doc/c-extensions|http://cgit.freedesktop.org/xorg/xserver/tree/doc/c-extensions]] +Notable objectionable things in the current coding style: + +* Most structs have a typedef both for the struct and for a pointer to the struct.
\ No newline at end of file diff --git a/ConfigurationHelp.mdwn b/ConfigurationHelp.mdwn new file mode 100644 index 00000000..485d61d8 --- /dev/null +++ b/ConfigurationHelp.mdwn @@ -0,0 +1,30 @@ + + +# Configuration Help + +If you are using a vendor-supplied Xorg (like on a Linux distribution) please follow your vendor's instruction on how to install and configure Xorg. Your vendor may have provided proprietary configuration tools. **Please consult your vendor's documentation/support** for information on how to use these tools: + +* [[Debian (wiki)|http://wiki.debian.org/Xorg]] +On how to download and install Xorg from the X.Org ftp server please check the [[Installation Instructions|http://www.freedesktop.org/~xorg/current/doc/Install.html]] on the X.Org web site. + +[[!toc ]] + + +## Configuring Xorg + +Xorg provides two ways to configure the Xserver: + +1. Autoconfiguration - Xorg probes the hardware, and if built with HAL support (default in Xorg 1.4 and later) asks HAL to provide input device configuration. +1. Xorg -configure - which can create a skeleton configuration file which should get you started if you need to change a configuration option from the autoconfigured default. + +### Xorg -configure + +The Xserver is capable of creating its own configuration file. As root just run: `X -configure`. The Xserver will then load each driver module, probe for the driver and create a configuration file. The configuration file will be stored in the home directory of the user who started the Xserver (usually `/root`). It's called `xorg.conf.new` so another config file that may exist in this directory will be overwritten. + +You may edit this file by hand to suit your needs. Generally you don't have to modify the mouse type, as the `auto` protocol should suit most needs. If your monitor is DDC capable you don't need to set up monitor ranges. This may not be true for some older cards which don't have DDC support, or if your monitor connection doesn't pass thru DDC information which is the case for some KVMs. + +In case you need to set additional driver options, all available driver options are already listed in the config file. Go to the device section and remove the `'#'` mark at the beginning of the line. If the option requires an additional argument, the type of argument is specified at the end of the line: + +* `[<bool>]` means a boolean argument. Uncommenting the option implicitly means 'True'. To disable the option you can add the string `"0"`, `"no"`, `"false"` or `"off"`. Likewise to enable the option you may use `"1"`, `"yes"`, `"true"` or `"on"`. +* Any integer `[<int>]`, float `[<float>]` value or string `[<str>]` needs to be quoted in double quotes. +* Frequencies `[<freq>]` contain a float value followed by the unit, i.e. `Hz`, `kHz` or `MHz`. Option names and values are case insensitive. For more information please consult `man 5 xorg.conf`.
\ No newline at end of file diff --git a/CrossCompilingXorg.mdwn b/CrossCompilingXorg.mdwn new file mode 100644 index 00000000..554984be --- /dev/null +++ b/CrossCompilingXorg.mdwn @@ -0,0 +1,96 @@ + +[[!toc ]] +## Introduction + +This page is an attempt to describe the process require to build the modular X.org tree using a crosscompiler. The majority of this document will assume that the reader already has a fully functioning crosscompiler on the _build_ system that can create binaries for the _host_ system. _Build_ and _host_ are the standard terms used by autoconfig to describe the system where the programs will be built (build) and the system where the programs will run (host). It would seem that the system where the programs will run should be called _target_, but that term carries a different meaning in autoconfig. _Target_ is the system for which a compiler (e.g., your crosscompiler) will generate code. Correct use of this terminology will help the process, trust me! + +For crosscompilers targeting Linux systems, [[crosstool|http://www.kegel.com/crosstool/]] is a good choice. + + +## Additional Requirements + +In addition to a crosscompiler, some libraries and headers for the host system must also be available. These can either be crosscompiled or copied from the host system. At a minimum, the following are required: + +* zlib +* libpng +* expat +* freetype +* fontconfig +* libdrm +* openssl (for SHA1) +For at least libdrm, PKG_CONFIG_PATH will need to be set to the location of that library's .pc file. Some configurations are known to build using the default system pkgconfig and simply over-ride the PKG_CONFIG_PATH. However, it may be necessary in some cases to build a "cross" pkgconfig. + + +## Cross compiling dependencies + +The below instructions assume CROSS_COMPILE is set to your toolchain (e.g. export CROSS_COMPILE=arm-none-linux-gnueabi- ) and DISCIMAGE is set to where you want to install. They also assume a Debian/Ubuntu based system - update as appropriate. + +Install zlib +[[!format txt """ + mkdir ~/sources; cd ~/sources + apt-get source zlib + cd zlib* + AR=${CROSS_COMPILE}ar CC=${CROSS_COMPILE}gcc RANLIB=${CROSS_COMPILE}ranlib ./configure --prefix=$DISCIMAGE/usr/local/ + make + make install +"""]] +Install libpng +[[!format txt """ + cd ~/sources + apt-get source libpng + cd libpng* + LDFLAGS="-L$DISCIMAGE/usr/local/lib" CPPFLAGS="-I$DISCIMAGE/usr/local/include" ./configure --prefix=$DISCIMAGE/usr --host=${CROSS_COMPILE%-} + make + make install +"""]] +Install expat +[[!format txt """ + cd ~/sources + apt-get source expat + cd expat* + AR=${CROSS_COMPILE}ar CC=${CROSS_COMPILE}gcc ./configure --prefix=$DISCIMAGE/usr/local/ --host=${CROSS_COMPILE%-} + make + make install +"""]] +Install openssl(For SHA-1) +[[!format txt """ + cd ~/sources + wget http://www.openssl.org/source/openssl-0.9.8h.tar.gz + tar -zxvf openssl-0.9.8h.tar.gz + cd openssl* + ./Configure dist --prefix=$DISCIMAGE/usr/local + make CC="${CROSS_COMPILE}gcc" AR="${CROSS_COMPILE}ar r" RANLIB="${CROSS_COMPILE}ranlib" + make CC="${CROSS_COMPILE}gcc" AR="${CROSS_COMPILE}ar r" RANLIB="${CROSS_COMPILE}ranlib" install +"""]] +Install jhbuild, on build machine (This isn't needed, but makes life easier) +[[!format txt """ + svn co http://svn.gnome.org/svn/jhbuild/trunk jhbuild + cd jhbuild + ./autogen.sh + make -f Makefile.plain install +"""]] +TODO: Other dependencies are needed depending on what you are doing. Please update these instructions if you need to install them. + + +## Using jhbuild to compile + +Copy and modify the example ~/.jhbuildrc file at [[CrossCompilingXorgJhbuild|CrossCompilingXorgJhbuild]] and then run +[[!format txt """ + jhbuild xserver +"""]] +X should now cross compile. General Jhbuild instructions are given at [[JhBuildInstructions|JhBuildInstructions]]. Feel free to mention any problems that you've come across here, along with solutions if you have them. + + +## Compiling without JHBuild + +This is not necessary if you use JHBuild to build. However if you do not want to, you will have to configure and build manually. Below are some general instructions to help you. + +To enable crosscompiling the _--host_ and _--build_ flags must be passed to configure. If the _build.sh_ script is being used, this can be done by setting CONFFLAGS. Both of these flags take a standard autoconfig system description. For example, to build on an x86-64 system running Linux for a PowerPC system running also running Linux, CONFFLAGS should be set to "--build x86_64-unknown-linux-gnu --host powerpc-unknown-linux-gnu". Based on these settings, the configure scripts will assume that the crosscompiler is named powerpc-unknown-linux-gnu-gcc and is in the path. If the compiler named something different, the name must be providied via the CC environment variable. The C++ compiler (CXX), linker (LD), ranlib (RANLIB), and ar (AR) must also be provided in this manner. + +Some components need to build and run programs on the build system that generate output used in the build process. For this compnents, CC_FOR_BUILD must be set to the name of the compiler that targets the build system. The majority of these components do not correctly use CC_FOR_BUILD, but there is a patch (see below) available. + +A number of steps in the autoconfig process implicitly assume that the build system and the host system are the same. For example, library components want to build and run test programs to determine the behavior of certain host system elements. This is clearly impossible when crosscompiling. To work around these issues, the --enable-malloc0returnsnull (or --disable-malloc0returnsnull, depending on the host system) must be passed to configure. + +In addition, the configure scripts for the video drivers use methods for detecting the availability of DRI that are incompatible with crosscompiling. Until a fix is provided, drivers must either be built on the host system or --disable-dri must be provided to their configure scripts. The issue in the drivers' configure scripts does _not_ effect the core X server. + +The -h and -b options to build.sh supply the --host and --build options to the configure scripts automatically. In addition, the value passed to -h is used in operation system and processor architecture based determinations of which drivers to build. The modifications to build.sh are based on the build.sh script that I use, but they have not been completely tested. If you encounter problems, please post to the xorg mailing list. diff --git a/CrossCompilingXorgJhbuild.moin b/CrossCompilingXorgJhbuild.moin new file mode 100644 index 00000000..e4abf6ec --- /dev/null +++ b/CrossCompilingXorgJhbuild.moin @@ -0,0 +1,78 @@ +Below is a sample ~/.jhbuildrc file to cross compile build X. Replace arm-none-linux-gnueabi with your toolchain. It assumes that you have export'ed DISCIMAGE to where you want to install to.
+
+{{{#!python
+#######################################################################################
+# This is a checkout and build configuration for building Xorg
+#
+# This can be copied to ~/.jhbuildrc and then run 'jhbuild build xserver'
+#
+#######################################################################################
+
+moduleset = 'http://cgit.freedesktop.org/xorg/util/modular/plain/xorg.modules'
+checkoutroot = '~/sources/xorg/git'
+modules = [ 'xorg' ]
+prefix = os.environ['DISCIMAGE'] +'/usr/local'
+
+autogenargs = ' --disable-static'
+autogenargs += ' --disable-dri2 --with-driver=dri'
+autogenargs += ' --cache-file=' + checkoutroot + '/autoconf-cache'
+# lots of people really like to always look in /var/log, but change if
+# you want the log files out of place
+autogenargs += ' --with-log-dir=/var/log'
+autogenargs += ' --with-mesa-source=' + checkoutroot + '/mesa'
+autogenargs += ' --enable-malloc0returnsnull'
+
+os.environ['ACLOCAL'] = 'aclocal -I ' + prefix + '/share/aclocal/'
+os.environ['INSTALL'] = os.path.expanduser('~/bin/install-check')
+
+# Enabled debugging for xserver
+os.environ['CFLAGS'] = '-g'
+os.environ['CPPFLAGS'] = '-g'
+
+# Setup environment for cross compiling
+
+os.environ['BUILD'] = 'i686-pc-linux-gnuaout'
+os.environ['HOST'] = 'arm-none-linux-gnueabi'
+os.environ['TARGET'] = 'arm-none-linux-gnueabi'
+
+cross_compile_prefix = os.environ['CROSS_COMPILE']
+tools = {'ADDR2LINE': 'addr2line',
+ 'AS': 'as', 'CC': 'gcc', 'CPP': 'cpp',
+ 'CPPFILT': 'c++filt', 'CXX': 'g++',
+ 'GCOV': 'gcov', 'LD': 'ld', 'NM': 'nm',
+ 'OBJCOPY': 'objcopy', 'OBJDUMP': 'objdump',
+ 'READELF': 'readelf', 'SIZE': 'size',
+ 'STRINGS': 'strings', 'AR': 'ar',
+ 'RANLIB': 'ranlib', 'STRIP': 'strip'}
+
+tools_args = str()
+for tool in tools.keys():
+ fullpath_tool = cross_compile_prefix + tools[tool]
+ os.environ[tool] = fullpath_tool
+
+autogenargs += ' --build='+os.environ['BUILD']
+autogenargs += ' --host='+os.environ['HOST']
+autogenargs += ' --target='+os.environ['TARGET']
+
+for tool in ('AR', 'RANLIB', 'STRIP', 'AS', 'OBJDUMP', 'NM'):
+ autogenargs += ' '+tool+'="'+os.environ[tool]+'" '
+
+module_autogenargs['libGL'] = autogenargs + ' --without-demos --with-dri-drivers="swrast" --disable-glw'
+module_autogenargs['libXt'] = autogenargs + ' --disable-install-makestrs'
+module_autogenargs['xserver'] = autogenargs + ' --enable-debug'
+module_autogenargs['pixman'] = autogenargs + ' --disable-gtk'
+module_autogenargs['hal'] = autogenargs + ' --disable-pci-ids'
+module_autogenargs['libXfont'] = autogenargs + ' --disable-freetype'
+
+# For expat and zlib
+os.environ['CFLAGS'] += ' -I' + os.environ['DISCIMAGE'] + '/usr/local/include/'
+os.environ['CPPFLAGS'] += ' -IHello -I' + os.environ['DISCIMAGE'] + '/usr/local/include/'
+os.environ['LDFLAGS'] = ' -L' + os.environ['DISCIMAGE'] + '/usr/local/lib/'
+os.environ['LDFLAGS'] += ' -Wl,--rpath -Wl,' + '/usr/local/lib/' #rpath is relative to where it is run from - DISCIMAGE
+
+# Just in case zlib or expat were installed here
+os.environ['CFLAGS'] += ' -I' + os.environ['DISCIMAGE'] + '/usr/include/'
+os.environ['CPPFLAGS'] += ' -I' + os.environ['DISCIMAGE'] + '/usr/include/'
+os.environ['LDFLAGS'] += ' -L' + os.environ['DISCIMAGE'] + '/usr/lib/'
+os.environ['LDFLAGS'] += ' -Wl,--rpath -Wl,' + '/usr/lib/'
+}}}
diff --git a/DanielStone.mdwn b/DanielStone.mdwn new file mode 100644 index 00000000..ee57e3c0 --- /dev/null +++ b/DanielStone.mdwn @@ -0,0 +1,12 @@ + + +## Daniel Stone + +[[daniel@fooishbar.org|mailto:daniel@fooishbar.org]] + [[http://fooishbar.org|http://fooishbar.org]] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/DanielVetter.mdwn b/DanielVetter.mdwn new file mode 100644 index 00000000..fcc8d3f7 --- /dev/null +++ b/DanielVetter.mdwn @@ -0,0 +1,15 @@ + + +## Daniel Vetter + +Email: daniel AT SPAMFREE ffwll DOT ch or daniel DOT vetter AT SPAMFREE ffwll DOT ch + +IRC: danvet (that's also my user name on fd.org) + +Blog: [[http://blog.ffwll.ch|http://blog.ffwll.ch]] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/DevPrivates.mdwn b/DevPrivates.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/DevPrivates.mdwn diff --git a/DeveloperStart.mdwn b/DeveloperStart.mdwn new file mode 100644 index 00000000..3974c629 --- /dev/null +++ b/DeveloperStart.mdwn @@ -0,0 +1,72 @@ + + +## Information for developers + +* Start reading the [[Development|Development]] page. +* Read the [[Developer's FAQ|DevelopersFAQ]] and the [[ModularDevelopersGuide|ModularDevelopersGuide]]. +* Read the [[ToDo|ToDo]], and add to it if you think it's lacking. +* [[RepoPolicy|RepoPolicy]] covers the general commit rules. +* [[CodingStyle|CodingStyle]] gives a guideline for the general coding style in X. +* [[XorgTriage|XorgTriage]] outlines our bugzilla workflow. + +## Module-specific information + +* [[XServer|XServer]] +* [[IntelVideoDriver|IntelVideoDriver]] +* [[Driver for Nvidia chips|http://nouveau.freedesktop.org/]] +* [[Driver for ATI/AMD Radeon chips|radeon]] +* [[Drivers for VMware virtual graphics|vmware]] + +## X.Org Foundation Workgroups + +* [[Architecture Working Group|ArchitectureWorkingGroup]] +* [[Modularization Working Group|ModularizationWorkingGroup]] +* [[Release Wranglers|ReleaseWorkingGroup]] +* [[Testing Working Group|TestGroup]] + +## Source Code + +Virtually all the source code of the server, the drivers and the default applications is hosted on the git server of freedesktop.org. It can be browsed on-line via the [[cgit interface|http://cgit.freedesktop.org/]]. For more details, refer to the [[git|http://www.freedesktop.org/wiki/Infrastructure/git]] page. + +Alternatively, all the most recent released packages can be found as tarballs at [[http://ftp.x.org/pub/individual/|http://ftp.x.org/pub/individual/]] . + + +## Specifications and reference manuals + +A lot of specifications can be found in the git tree, in [[doc/xorg-docs|http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/]]. Short documents are in plain text format, while bigger ones tends to be in troff or [[DocBook|DocBook]] format, and will therefore need to be compiled to be read easily. + +The documentation of each component is gradually split out into their respective modules. In particular: + +* [[XRandR|http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt]] +* [[DRI2|http://cgit.freedesktop.org/xorg/proto/dri2proto/tree/dri2proto.txt]] +* [[XML-XCB|http://cgit.freedesktop.org/xcb/proto/tree/doc/xml-xcb.txt]] +* [[Render|http://cgit.freedesktop.org/xorg/proto/renderproto/tree/renderproto.txt]] +* [[DAMAGE|http://cgit.freedesktop.org/xorg/proto/damageproto/tree/damageproto.txt]] +* [[XFIXES|http://cgit.freedesktop.org/xorg/proto/fixesproto/tree/fixesproto.txt]] +* [[VAAPI|http://cgit.freedesktop.org/libva/tree/src/va.h]] +You might also be interested by the [[list of specifications|http://www.freedesktop.org/wiki/Specifications]] available at freedesktop.org. + + +## Fixing bugs + +Bugs assigned to the [[freedesktop bugzilla|http://bugs.freedesktop.org]] pseudo-user [[xorg-team@lists.x.org|mailto:xorg-team@lists.x.org]] need someone to take ownership of them. If you feel qualified to fix the bug, feel free to take ownership of the bug by reassigning it to yourself. + + +## Submitting patches + +Please read the [[patch submission guidelines|http://wiki.x.org/wiki/Development/Documentation/SubmittingPatches]] + + +## Requesting features + +Please remember that X is just one component of the overall free desktop and that therefore future X enhancements should be thought through with this perspective. Also remember that the folks here are massively overloaded---by far the most reliable way to get a feature in is to put it there yourself. + + +## To Do + +See the [[ToDo|ToDo]] page for a list of tasks that need to be done specific to Xorg. A more comprehensive list [[of unfinished X related projects|http://www.freedesktop.org/wiki/FreedesktopProjects]] (not necessarily involving working on the server itself) is also available. Both of these lists may be a bit out-of-date, so do hit the email lists once you've gotten yourself oriented. + + +## The X.Org Endless Vacation of Code + +A special program to provide financial support for student contributors who are unable to participate in the bigger (and better known) program of this type, Google Summer of Code. Open all-year round. Look at [[ToDo|ToDo]] page for project ideas, and at [[the EVoC rules|XorgEVoC]], and see if you can help. diff --git a/DevelopersFAQ.mdwn b/DevelopersFAQ.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/DevelopersFAQ.mdwn diff --git a/DevelopersPages.mdwn b/DevelopersPages.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/DevelopersPages.mdwn diff --git a/Development.mdwn b/Development.mdwn new file mode 100644 index 00000000..1a52f3fd --- /dev/null +++ b/Development.mdwn @@ -0,0 +1,54 @@ + +This page has general information on X development, including how to get started. + +A common misconception is that developers need to understand all of X to get started. This is not true, and even of the "core" developers, only few actually know all the pieces that put X together. The best way to get started is to simply pick a problem and give it a try. + +There is also a new book in the Amazon Kindle format, [[Hands-on Projects for the Linux Graphics Subsystem|http://www.amazon.com/dp/B007QJKOGS/ref=rdr_ext_sb_ti_hist_1]]. This includes a number of original projects on the X.Org implementation of the Linux graphics subsystem. The book is aimed for instructors, students and any other OS internals enthusiasts. + + +## Documentation + +* [[Glossary|Development/Documentation/Glossary]]: Various terms used in X, and what they mean. +* [[Modular Developers Guide|ModularDevelopersGuide]]: For builders and developers working on the modular X.Org source tree +* [[Submitting patches|Development/Documentation/SubmittingPatches]]: How to submit a patch to an Xorg project. +* [[Making a release|Development/Documentation/ReleaseHOWTO]]: How to make an individual module release. +* [[Writing documentation|Development/Documentation/WritingDocumentation]]: How to document your work in X. +* [[Documentation being converted to DocBook|Development/Documentation/DocBookConversion]]: What needs to be converted and what is being converted +* [[X server source layout|Development/Documentation/XserverSourceLayout]]: A map to the different directories in the X server source +* [[The devPrivates system|Development/Documentation/DevPrivates]]: All about the private storage system in the server. +* [[Wrapping functions|Development/Documentation/WrappingFunctions]]: How to add hooks to functions in the server. +* [[Grab processing|Development/Documentation/GrabProcessing]]: How input grabs are dealt with in the server. +* [[Cursor handling|Development/Documentation/CursorHandling]]: Introduction into DIX cursor handling. +* [[Input event processing|Development/Documentation/InputEventProcessing]]: How input events are dealt with in the server. +* [[Security|Development/Documentation/Security]]: How to make use of the security facilities within X. +* [[Performance|Development/Documentation/Performance]]: A fairly detailed document explaining what our performance problems actually are, and things that aren't performance problems at all. +* [[Xorg input driver HOWTO|Development/Documentation/XorgInputHOWTO]]: How to write an input driver for X.Org. +* [[How video cards work|Development/Documentation/HowVideoCardsWork]]: A conceptual overview. +* [[Xorg video driver HOWTO|Development/Documentation/XorgVideoHOWTO]]: How to write a basic video driver for X.Org. +* [[Kdrive Drivers|Development/Documentation/KdriveDrivers]]: notes for making new kdrive video drivers +* [[Dri Wiki|http://dri.freedesktop.org/wiki/]]: Information about using the Direct Rendering Infrastructure (DRI) with X. +* [[Multiseat|Development/Documentation/Multiseat]]: Various informations about how to obtain and develop such model. +* [[Deprecated and obsolete|Development/Documentation/Obsolescence]]: Notes on deprecated and obsolete extensions and server-side stuff. +* [[More Xorg Documentation|XorgDeveloperDocumentation]]: Some pointers from deep in the Wiki. This page should possibly be moved into Development/Documentation. +* [[Pointer acceleration|Development/Documentation/PointerAcceleration]]: information on the pointer accel mechanism. + +#### Tools + +* [[Using git|Development/Documentation/git]]: Information on using git. +* [[Server debugging|Development/Documentation/ServerDebugging]]: How to debug the X server with gdb. +* [[Server profiling|Development/Documentation/ServerProfiling]]: How to profile the X server. +* [[Using ctags to find functions|Development/Documentation/UsingCtags]]: Some tips to find a function in vim. +* [[Using Eclipse|Development/Documentation/UsingEclipse]]: Some tips to use Eclipse to develop X.Org. + +#### Various Projects + +* [[PciReworkHowto|PciReworkHowto]]: How to fix a video driver to use libpciaccess +* [[VgaArbiter|VgaArbiter]]: Routing VGA instructions correctly. +* [[Xv2, Render API|Development/Xv2]]: a long rambling discussion about giving Pictures GCs, and moving Xv to Render + RandR. +* [[X12|Development/X12]]: a list of things we'd fix if we ever get around to a new version of the core X protocol + +## Helping out + +* [[ContributionHOWTO|Development/ContributionHOWTO]]: How to get started contributing bug reports, patches, fixes, or even entire drivers. +* [[ToDo|ToDo]]: Things that need doing. +* [[Janitor|Development/Janitor]] Xorg Janitor project page
\ No newline at end of file diff --git a/Development/Documentation/CursorHandling.mdwn b/Development/Documentation/CursorHandling.mdwn new file mode 100644 index 00000000..0ee8e688 --- /dev/null +++ b/Development/Documentation/CursorHandling.mdwn @@ -0,0 +1,48 @@ + +This is documentation about the cursor handling, not about the cursor rendering! + +Generally, a _[[CursorRec|CursorRec]]_ gets allocated only once and used multiple times to save memory. Two functions are responsible for allocating cursors: _AllocCursorARGB()_ and _[[AllocGlyphCursor|AllocGlyphCursor]]()_. The matching Xlib functions would be _XCreateCursor()_ and _XCreateGlyphCursor()_. + +The [[CursorRec|CursorRec]] contains a number of things, we will focus on the _refcnt_ here. The _refcnt_ is used to track how many instances of the cursor are used and to avoid freeing memory too early. The _refcnt_ is increased when + +1. a client gets a reference to a cursor +1. a window uses the cursor +1. a pointer uses the cursor +1. a pointer uses the cursor as part of a grab. +When you create a cursor, it will have a _refcnt_ of 1 (the client has a reference to it after all). Each time you use Xlib's _XDefineCursor()_ or _XChangeWindowAttributes()_, the window obtains a reference to the cursor and increases the _refcnt_. And each time the pointer passes into a window that has a cursor set, _[[ChangeToCursor|ChangeToCursor]]()_ will change the pointer's cursor and increase the _refcnt_. Using the cursor for a sprite does NOT change the _refcnt_! + +The _refcnt_ is decreased in _[[FreeCursor|FreeCursor]]()_. When the _refcnt_ hits 0, the memory for the cursor is freed. Make sure that when you call _[[FreeCursor|FreeCursor]]()_, nothing in your codepath references the address anymore. The usual way to do this is something like +[[!format txt """ + CursorPtr pOldCursor = device->spriteInfo->sprite->current; + device->spriteInfo->sprite->current = NULL; + FreeCursor(pOldCursor, 0); +"""]] +The value of _pOldCursor_ is undefined after _[[FreeCursor|FreeCursor]]()_. + +_[[FreeCursor|FreeCursor]]()_ is called from several points. Each time the cursor leaves a window, _[[CheckMotion|CheckMotion]]()_ call _[[PostNewCursor|PostNewCursor]]()_, which may call _[[ChangeToCursor|ChangeToCursor]]()_. When the client issues a _[[FreeCursor|FreeCursor]]_ request. Each time a window changes the cursor (_[[ChangeWindowAttributes|ChangeWindowAttributes]]()_). When a grab with a cursor is deactivated. And on _[[CloseDownClient|CloseDownClient]]()_, when all the resources are freed for the client. And quite a few more. + + +### Animated cursors + +Animated cursors are part of the XRender extension. All they are is a list of standard cursors with a delay between them. The memory is a standard _[[CursorRec|CursorRec]]_, with an _[[AnimCursorRec|AnimCursorRec]]_ and several _[[AnimCursElt|AnimCursElt]]_ attached to the end of the struct. The latter two contain the _[[CursorRec|CursorRec]]_ that make up the animated cursor's frames. Animated cursors are identified with a special pattern in the _[[CursorRec|CursorRec]]_s _bits_ field. See _[[AnimCursorCreate|AnimCursorCreate]]()_. + +So for an animated cursor with 3 frames, the memory looks something like this. +[[!format txt """ +[ CursorRec ][ AnimCursorRec ][AnimCursElt][AnimCursElt][AnimCursElt] + | | | +[ CursorRec ] <------------------- | | +[ CursorRec ] <--------------------------------- | +[ CursorRec ] <---------------------------------------------- +"""]] +Each cursor that is used in an animated cursor has the _refcnt_ increased, and likewise decreased via _[[FreeCursor|FreeCursor]]()_ when the animated cursor is deleted. If a window or pointer uses a animated cursor, they use the animated cursor struct, never directly any of the cursors that make up the frames. + +X uses a _[[BlockHandler|BlockHandler]]_ to do stuff when nothing else needs to be done. Such as redrawing mouse cursors. The animated cursor code adds itself to the block handler and _[[AnimCurScreenBlockHandler|AnimCurScreenBlockHandler]]()_ is called regularly. + +Display of an animated cursor uses set of static variables in _animcur.c_. The currently displayed animated cursor is saved, and each time the block handler is called, it checks + +* whether the current cursor is an animated cursor. +* if so, if the timeout for the next frame has passed already +* if so, display the next frame +* if so, save the timeout for the next frame in the static struct +* update wakeup handler to wake up for next timeout. +--- [[CategoryServerInternals|CategoryServerInternals]] diff --git a/Development/Documentation/DevPrivates.mdwn b/Development/Documentation/DevPrivates.mdwn new file mode 100644 index 00000000..3235c070 --- /dev/null +++ b/Development/Documentation/DevPrivates.mdwn @@ -0,0 +1,100 @@ + +devPrivates are a way to store information in a struct without modifying the header for the struct, thus keeping the ABI. + +Each major struct ([[ScreenRec|ScreenRec]], [[DeviceIntRec|DeviceIntRec]], [[WindowRec|WindowRec]], [[ClientRec|ClientRec]]) has a pointer to it's devPrivates as part of the struct. The usage of the devPrivates is as follows: + + +[[!format txt """ +#include <privates.h> + + +DevPrivatesKey myKey = &myKey; + + +void store_private(ClientPtr client) +{ + MyStruct *a = xalloc(sizeof(MyStruct)); + + /* do stuff with a */ + + dixSetPrivate(&client->devPrivates, myKey, a); +} + +void retrieve_private(ClientPtr client) +{ + MyStruct *a; + + a = (MyStruct*)dixLookupPrivate(&client->devPrivates, myKey); + + /* do stuff with a */ +} + + +/* The following will free _ALL_ devPrivates on the given client. Not just yours! */ +void delete_private(ClientPtr client) +{ + dixFreePrivates(client->devPrivates); + +} + +"""]] +devPrivates are more fully documented in the _Definition of the Porting Layer for the X v11 Sample Server_ document, sources of which are in [[xorg-docs/sgml/core/Xserver-spec.sgml|http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/sgml/core/Xserver-spec.sgml]] + + +# Deprecated information + +The following is a description of the devPrivates system before the serious overhaul. It is now outdated. + +Client devPrivates are similar to those of the [[ScreenRec|ScreenRec]] and [[DeviceIntRec|DeviceIntRec]] structures, but those have their own API to initialize and access them. Please note that there a overhaul of the devPrivates system in progress and this information may be out of date soon [[http://lists.freedesktop.org/archives/xorg/2007-March/022212.html|http://lists.freedesktop.org/archives/xorg/2007-March/022212.html]]. + +Need to be initialised at start time, as each time a client is allocated. The devPrivates are an array of [[DevUnions|DevUnions]] that are allocated when the client starts and released when the client finishes. Each client has the same size allocated for devPrivates and at the moment there are no methods to resize the array at a later point in time. Better make sure you allocate everything on server startup before the first client connects. + +_[[AllocateClientPrivatesIndex|AllocateClientPrivatesIndex]]()_ gives you an index into the array. Each time you need to access your data, access it with `client->devPrivates[MyIndex].ptr` and cast it to your specific data information. Immediately after retrieving your index, call _[[AllocateClientPrivate|AllocateClientPrivate]]([[MyIndex|MyIndex]], size)_, where size is the number of bytes you need for your private struct in bytes. You can now assume that every client that connects will have enough space for your data. + +Finally, you will probably want to add a callback to reset the data when a client starts up. Use _[[AddCallback|AddCallback]]()_ to register your function and then do stuff. The first argument is always the same (_[[ClientStateCallback|ClientStateCallback]]_), the second your callback proc and the third one some pointer data which will get passed into the callback function (argument {{closure]] in example below). Most extensions just pass in 0. You need to check the state of the client in the callback function. If client->state is [[ClientStateRunning|ClientStateRunning]] then the client has just started up, [[ClientStateGone|ClientStateGone]] or [[ClientStateRetained|ClientStateRetained]] means it has been shut down. There are a few other states. (comment by Eamon Walsh) + +I recommend looking at damageext/damageext.c, it has a low signal-to-noise ratio. The full code you need: + + +[[!format txt """ +int myIndex = AllocateClientPrivateIndex(); /* check myIndex > 0 */ +AllocateClientPrivate(myIndex, sizeof(MyStruct)); /* has to return true */ +AddCallback(&ClientStateCallback, MyCallbackProc, 0); + +static void MyCallbackProc(CallbackListPtr *list, pointer closure, pointer data) +{ + NewClientInfoRec* clientinfo = (NewClientInfoRec*)data; + ClientPtr client = clientinfo->client; + MyStruct mystruct = (MyStruct*)client->devPrivates[myIndex].ptr; + + /* do stuff */ + +} +"""]] +Finally, you want to add a _[[DeleteCallback|DeleteCallback]]()_ call to remove your callback when the extension resets. + + +## Notes + +The client that owns the root window is `serverClient` and will be created before extensions initialize. It will (most likely) not have devPrivates set to what you added, so make sure you cater for this. + + +### Window DevPrivates + +The devPrivates of a [[WindowRec|WindowRec]] are stored after the struct's memory. Each screen keeps a totalWindowSize for the memory that is to be allocated per screen. The memory for a [[WindowRec|WindowRec]] with 4 devPrivates entries looks approximately like this: + + +[[!format txt """ + ___________________________________________________________________________ +| | | | | | | | | | +| WindowRec | 1 | 2 | 3 | 4 | A | B | C | D | +|___________dP__|___|___|___|___|__________|_____________|___|______________| + | ^ | | | | ^ ^ ^ ^ + |__| | | | |__|__________|_____________|___| + | | |______|__________|_____________| + | |__________|__________| + |______________| +"""]] +With `1 = &A, 2 = &B, `etc. Before you allocate a window, you need to call _[[AllocateWindowPrivate|AllocateWindowPrivate]]()_ with the size you need for your entry. A, B, C, D have the sizes that were specified for _[[AllocateWindowPrivate|AllocateWindowPrivate]]_ + +--- [[CategoryServerInternals|CategoryServerInternals]] diff --git a/Development/Documentation/DocBookConversion.mdwn b/Development/Documentation/DocBookConversion.mdwn new file mode 100644 index 00000000..0402471b --- /dev/null +++ b/Development/Documentation/DocBookConversion.mdwn @@ -0,0 +1,23 @@ + + +## Tools + +What is needed to convert troff documents from [[DocBook|DocBook]]: + +* [[DocLifter|DocLifter]] ([[+patches|http://lists.freedesktop.org/archives/xorg/2008-June/035967.html]]) +* Time +* Luck + +## To Do + +List the document that have yet to be converted here. + +* [[XKB|XKB]] specs (xorg-docs/specs/XKB/Proto & xorg-docs/specs/XKB/XKBlib): these are in Frame``Maker format. [[AlanCoopersmith|AlanCoopersmith]] used Frame``Maker's Export options to produce several more convertible formats from them: XML (with unknown DTD), HTML & MIF - available at [[http://people.freedesktop.org/~alanc/xkb/|http://people.freedesktop.org/~alanc/xkb/]] - but someone needs to finish converting to DocBook/XML. + +## Ongoing + +There has been an interest in converting the parts of the Xorg documentation written in troff to [[DocBook|DocBook]] (or any other generic format). In order not to duplicate efforts, here is the list of what is being done and by whom. + +* [[PeterHutterer|PeterHutterer]] has converted the XInput documentation to [[DocBook|DocBook]] +* [[FrancoisDenisGonthier|FrancoisDenisGonthier]] and [[MichaelVerret|MichaelVerret]] are trying to convert from XProtocol from troff to [[DocBook|DocBook]] using doclifter. +* [[GüntherBrammer|GüntherBrammer]] is converting documentation in the Xext directory.
\ No newline at end of file diff --git a/Development/Documentation/Glossary.mdwn b/Development/Documentation/Glossary.mdwn new file mode 100644 index 00000000..17efb4cd --- /dev/null +++ b/Development/Documentation/Glossary.mdwn @@ -0,0 +1,16 @@ + +* <a name="DDX"></a>DDX: Device Dependent X. The part of X that interacts with the hardware. There have been many of these over the years:`xfree86`, `kdrive`, `xwin` (for Windows), `darwin` (for OS X), [[xgl|Development/Documentation/Glossary]], `vfb`, `xnest`, and so forth. In the X server code, each directory under [[hw|http://cgit.freedesktop.org/xorg/xserver/tree/hw]] corresponds to one DDX. One DDX may have one or more device drivers. In the `xfree86` DDX, each driver is a separate loadable module; in most of the other DDXes, each driver is compiled to its own server binary. Contrast: [[DIX|Development/Documentation/Glossary]]. +* <a name="DIX"></a>DIX: Device Independent X. The part of X that interacts with clients and implements software rendering. Basically everything in the [[server|http://cgit.freedesktop.org/xorg/xserver/tree]] except for the `hw/` directory. The event delivery is part of the DIX. +* <a name="DMX"></a>DMX: Distributed Multihead X, which allows combining several backend X servers into a single virtual X server. +* <a name="DRI"></a>DRI: Direct Rendering Infrastructure. A way for X clients to send commands directly to the graphics card. Primarily used to make [[GLX|Development/Documentation/Glossary]] go fast, but also involved in accelerating [[XvMC|Development/Documentation/Glossary]]. All the open drivers, and many of the closed drivers, use the DRI to accelerate [[GLX|Development/Documentation/Glossary]]. +* <a name="EGL"></a>EGL: Embedded-System Graphics Library. The interface between rendering APIs such as OpenGL ES and the underlying native platform window system, such as X. +* <a name="EXA"></a>EXA: Acceleration architecture with no well-defined acronym. Based on the kdrive acceleration architecture ([[KAA|Development/Documentation/Glossary]]) but with some additional features and cleanups, and designed to be used within the `xfree86` [[DDX|Development/Documentation/Glossary]]. +* <a name="git master"></a>git master: A term to refer to the master branch in the X server's git repository (see [[http://cgit.freedesktop.org|http://cgit.freedesktop.org]]). The master branch is the default when you get the X server sources, and it is where most of the development happens. +* <a name="GLX"></a>GLX: OpenGL extension for X. Provides a way to do OpenGL drawing into a window managed by the X server. Almost always available in software. The open drivers use the [[DRI|Development/Documentation/Glossary]] to accelerate GLX. +* <a name="KAA"></a>KAA: kdrive acceleration architecture. Used in the `kdrive` [[DDX|Development/Documentation/Glossary]] to accelerate core X drawing and [[Render|Development/Documentation/Glossary]]. Much simpler than [[XAA|Development/Documentation/Glossary]], but with fewer restrictions on the use of offscreen memory, which is important for effectively accelerating [[Render|Development/Documentation/Glossary]]. +* <a name="MI"></a> MI: machine independent. Routines that should run on pretty much any hardware +* <a name="OpenGL"></a>OpenGL: Open Graphics Library. The standard cross-platform API for 2D and 3D rendering. OpenGL needs a binding layer to the window system to actually display anything; relevant ones to X are [[GLX|Development/Documentation/Glossary]] and [[EGL|Development/Documentation/Glossary]]. +* <a name="Render"></a>Render: An extension to the X protocol that exposes the Porter-Duff image compositing model. Unlike the core X drawing requests, the Render extension is capable of doing alpha blending. Primarily used right now to implement antialiased fonts, but is also used by the `xcompmgr` demo to implement drop shadows and translucency. +* <a name="XAA"></a>XAA: XFree86 Acceleration Architecture. Used in the `xfree86` [[DDX|Development/Documentation/Glossary]] to accelerate core X drawing requests and [[Render|Development/Documentation/Glossary]]. Not really suitable for modern desktop usage anymore. Intended to be replaced by [[EXA|Development/Documentation/Glossary]] in the `xfree86` [[DDX|Development/Documentation/Glossary]], or by the [[XGL|Development/Documentation/Glossary]] [[DDX|Development/Documentation/Glossary]]. +* <a name="XGL"></a>XGL: X on OpenGL. A [[DDX|Development/Documentation/Glossary]] that uses an OpenGL stack to do its rendering. The XGL DDX has several drivers: Xglx to display on a [[GLX|Development/Documentation/Glossary]] surface, a la Xnest; Xegl, to display an native [[EGL|Development/Documentation/Glossary]] screen; and potentially also Xwgl and Xagl to display on win32 and OSX windows. Xgl was removed from git master on the 12 June 2008 after having been orphaned for years. +Another, larger but more X Protocol oriented glossary can be found at [[http://www.rahul.net/kenton/xglossary.html|http://www.rahul.net/kenton/xglossary.html]] diff --git a/Development/Documentation/GrabProcessing.mdwn b/Development/Documentation/GrabProcessing.mdwn new file mode 100644 index 00000000..e194d49b --- /dev/null +++ b/Development/Documentation/GrabProcessing.mdwn @@ -0,0 +1,32 @@ + + +# X Server Input Device Grabs + +Grabs are a way of forcing devices to only report to a specific client (the grabbing client). There are two different types of grabs: core grabs and device grabs (X input extension). + +Core grabs are fairly simple: when a client issues a request (e.g. [[GrabPointer|GrabPointer]]), the server takes the core pointer and initializes a [[GrabRec|GrabRec]] structure to be put in the grab field of the [[DeviceIntRec|DeviceIntRec]]. Each time the device now emits an event, it is delivered only to the client that owns the grab. Grabs are resources and thus the owner of the grab can be looked up using the rClient(grab) macro. A typical event flow would be mieqProccessInputEvent -> [[CoreProcessPointerEvent|CoreProcessPointerEvent]] -> [[DeliverGrabbedEvent|DeliverGrabbedEvent]] -> [[TryClientEvents|TryClientEvents]]. + +Device grabs are the same but require some knowledge about the role of the core pointer. Each time the client issues a [[GrabDevice|GrabDevice]] request, a grab is initialized in the same way to the core grab. The grab is stored in the device itself. + +But here is the important bit about event generation: Each time a device emits an event, it creates a device event and (maybe) a core event. The device event is put on the event queue and processed with a reference to the original device. The core event however is processed with the core pointer. After [[GetPointerEvents|GetPointerEvents]], all core events appear to have originated from the core pointer and all device events from their device. + +And suddenly all the bits with grabs fall into place. If we have a core grab, we have it on the core pointer, thus all core events, no matter which device caused them, belong to us. A device grab will only send us the Xi events, while the core events still go wherever they are supposed to. As a result, we can have multiple device grabs but only ever one core grab. This is probably also the reason why the core pointer and core keyboard could not be configured to send Xi events. + +There are always two core devices: [[VirtualCorePointer|VirtualCorePointer]] and [[VirtualCoreKeyboard|VirtualCoreKeyboard]] were added by Daniel Stone when he wrote [[InputHotplug|InputHotplug]]. Reason being is that the X server always has to have at least one keyboard and one mouse. But with hotplugging, you should be able to start X without any devices. So the solution was to add virtual devices that aren't connected to real ones and make sure they are always there. That way you can add and remove physical devices without breaking anything. They aren't physical devices! But with the event delivery described above, they still emit core events. + + +# Passive grabs + +Passive grabs are a different matter. A client can create multiple passive grabs ([[GrabButton/GrabKey|GrabButton/GrabKey]]), and they become active whenever the specified button/key is pressed, until it is released again. The server has two kinds of passive grabs, explicit and implicit ones. Explicit ones are the one requested by the client, they are stored as _[[GrabRec|GrabRec]]_ in the window's resource system. + +An implicit passive grab is activated only if there is no active grab on the device and no passive grab has been activated either. In this case, the server creates a new grab, fills it with data and sets it on the device. The purpose of the grab is to ensure that a [[ButtonRelease|ButtonRelease]] event is delivered to the same client as the [[ButtonPress|ButtonPress]] event. This grab is deactivated when the button is released again. + +There can only be one grab on a device, so the check for the activation of passive grabs only happens when the first button is pressed. Further buttons are not checked. + +A passive grab is only created once, when the client requests it. When it is activated, the grab is _copied_ into the device. Thus modifying a passive grab will not actually modify a grab that is currently active on a device. + + + +--- + + [[CategoryServerInternals|CategoryServerInternals]] diff --git a/Development/Documentation/HowVideoCardsWork.mdwn b/Development/Documentation/HowVideoCardsWork.mdwn new file mode 100644 index 00000000..80c98605 --- /dev/null +++ b/Development/Documentation/HowVideoCardsWork.mdwn @@ -0,0 +1,290 @@ + + +# Video Cards + +[[!toc ]] + +So you want to know how modern video cards work. Here goes... + +Modern video cards usually have several common features: + +* Video Ram +* Display control +* 2D engine +* 3D engine +* Overlay +* HW sprites (cursor, icon, etc.) +* AGP/PCI/PCIE +* Apertures (registers, framebuffer) + +## Video Ram + +Basically a large chunk of fast ram. This memory is used for all sorts of things: + +* Scan-out buffers (what you see on your monitor) +* Offscreen rendering buffers +* Cursor images +* Command buffers +* Vertex data +* Textures +Buffers in video ram generally have a stride (also called pitch) associated with them. The stride is the width of the buffer in bytes. For example, if you have a 1024x768 pixel buffer at 16 bits/pixel (2 bytes/pixel), your stride would be: + + +[[!format txt """ +1024 pixels * 2 bytes/pixel = 2048 bytes +"""]] +At 32 bits/pixel (4 bytes/pixel), your stride would be: + + +[[!format txt """ +1024 pixels * 4 bytes/pixel = 4096 bytes +"""]] +Stride is important as it delineates where each line of the buffer starts and ends. With a linear buffer format, each line of the buffer follows the previous linearly in video ram: + + +[[!format txt """ +framebuffer address +0 2048 4096 +|---------------|---------------|---------------| ... |---------------| +"""]] + +### Tiled framebuffers + +The above layout is called "linear", because the layout of pixels in memory is like that on the screen: the pixel to the right of the current one on the screen is the one at the next highest address in memory. Tiling is a common variation where pixel layout in memory is not linear, but instead laid out in small squares. For example, a 4x4 tile would look like: + + +[[!format txt """ + 0 1 2 3 + 4 5 6 7 + 8 9 10 11 +12 13 14 15 +"""]] +In other words, the 4th (zero-based) pixel in memory would be at screen coordinate (0, 1), whereas in linear memory it would be at screen coordinate (4, 0). The pattern then continues: the 16th (zero-based) pixel is screen coordinate (4, 0) instead of (16, 0). The reason for this alternate layout is it makes pixels that are adjacent on the screen also adjacent in memory, which improves cache locality. + +Some hardware has multiple levels of tiling. For example, Radeon hardware can have microtiles composed of pixels, and macrotiles composed of microtiles. Sometimes the GPU can hide tiling from the CPU (ie, make tiled regions appear linear to PCI bus accesses). + + +## Display control + + +### Overview + +The display cell on most video cards controls the size, timing, and type of signal sent to the monitor. There are 3 elements involved in this: + +1. CRTC or Display Controller +1. PLLs (pixel clock) +1. Outputs + +### CRTCs + +CRTC is a jargon term for "CRT controller", and CRTs are those big bulky glass things with pictures on them you see in old movies. Practically speaking, they define a region of pixels you can see. + +The crtc controls the size and timing of the signal. This includes the vertical and horizontal sizes and blanking periods. Most cards have 2 or more crtcs. Each crtc can drive one or more outputs. Generally, each crtc can have it's own set of timings. If that crtc is driving more than one output, each output is driven at the same timings. Crtcs can also scan out of different parts of the framebuffer. If you have more than one crtc pointing at the same framebuffer address you have "clone" modes. Clone modes can also be achieved by driving more than one output with one crtc. If you point the crtcs to different parts of the framebuffer, you have dualhead. + +On VGA-like signalling, this signal includes sync signals so the monitor can find the edges of the image. A modeline contains the timings (in pixels) where these sync signals are generated, relative to the active pixel times. (For the rest of this discussion we'll use "pixel" to mean "pixel interval" for brevity.) For example: + + +[[!format txt """ +Modeline "1680x1050R" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync +"""]] +Here, 1680 of 1840 total pixel in each horizontal interval contain actual pixel data, and the horizontal sync pulse runs from pixel 1728 to pixel 1760. 1050 of the 1080 total lines contain actual pixel data, and the vertical sync pulse runs from line 1053 to line 1059. The interval between the end of the active region and the beginning of the sync pulse is called the front porch; the interval between the end of the sync pulse and the end of a line or frame is called the back porch. Sync polarity is set by convention, so the monitor can know which timing formula is in use. Normal modes generated by the GTF or CVT timing formulas are -hsync +vsync. Modes generated by the CVT reduced-blanking formula or by GTF when using a secondary curve are +hsync -vsync. Other polarity combos are occasionally seen for various historical modes. + +The stride of a crtc is set to the stride of the buffer it is scanning out of. The stride of the buffer does not have to correspond the size of the crtc mode. This allows you to implement things like virtual desktops (1024x768 mode scanning out of a 2048x2048 pixel virtual desktop) or have multiple crtcs scan out of different parts of the same buffer (two 1024x768 crtcs scanning out of a 2048x768 pixel buffer). + + +### PLLs + +The PLLs controls the pixel/video clock. This is the rate at which pixels are sent to the monitor. The higher the vertical refresh rate or resolution of your screen the higher the pixel clock. + +The pixel clock is usually generated using the following formula: +[[!format txt """ +pixel clock = (ref freq) * (m/n) * (1/(1 + r)) + +ref freq = the base clock frequency provided by the hardware +m = clock multiplier +n = clock divider +r = clock post divider +"""]] + +### Outputs + +The outputs convert the data stream sent from the crtc into something the monitor understands. For example a DAC (Digital Analog Converter) converts the digital data stream into an analog signal for your monitor. Some other examples include TMDS ([[Transition Minimized Differential Signaling|http://en.wikipedia.org/wiki/TMDS]]) transmitters (converts to the digital format used by DVI and some other connectors), LVDS ([[Low Voltage Differential Signaling|http://en.wikipedia.org/wiki/LVDS]]) transmitters (commonly used to connect local flat panels like LCDs on laptops), and TV encoders (converts to an analog TV signal often with image scaling). Outputs can be integrated into the graphics chip or provided as external components (usually connected via a standard interface like DVO (Digital Video Out) or SDVO (Serial Digital Video Out)). + + +### Driver Examples + +In most Xorg drivers there are 3 sets functions (usually found in chipname_driver.c) associated with configuring the display controllers: + +* Save() - Saves the current hardware state of the output registers +* Init() - Initializes the hardware register data structures for the requested output configuration +* Restore()/Write() - Writes the initialized register values set up in the Init() functions to the hardware + +#### Radeon + +Save: + +* RADEONSaveMemMapRegisters() - saves memory map register state +* RADEONSaveCommonRegisters() - saves common register state +* RADEONSaveCrtcRegisters() - saves the registers for the primary crtc +* RADEONSaveFPRegisters() - saves the registers for the panel outputs (RMX, TMDS, LVDS) +* RADEONSaveCrtc2Registers() - saves the registers for the secondary crtc +* RADEONSavePLLRegisters() - saves the registers for the primary (crtc1) pixel clock +* RADEONSavePLL2Registers() - saves the registers for the secondary (crtc2) pixel clock +* RADEONSavePalette() - saves the palette/CLUT registers +* RADEONSaveMode() - calls the above functions +Init: + +* RADEONInitOutputRegisters() - Initializes registers for outputs and sets up the crtc to output mapping. Calls output init functions +* RADEONInitCrtcRegisters() - Initializes registers for crtc1. Calls RADEONInitOutputRegisters() to initialize the outputs driven by crtc1 and RADEONInitPLLRegisters() to set up the pixel clock. +* RADEONInitCrtc2Registers() - Initializes registers for crtc2. Calls RADEONInitOutputRegisters() to initialize the outputs driven by crtc2 and RADEONInitPLL2Registers() to set up the pixel clock. +* RADEONInitPLLRegisters() - initialize the pixel clock for crtc1 +* RADEONInitPLL2Registers() - initialize the pixel clock for crtc2 +* RADEONInit2() - calls the above functions +Restore/Write: + +* RADEONRestoreMemMapRegisters() - restore memory map register state +* RADEONRestoreCommonRegisters() - restore common register state +* RADEONRestoreCrtcRegisters() - restore the registers for the primary crtc +* RADEONRestoreFPRegisters() - restore the registers for the panel outputs (RMX, TMDS, LVDS) +* RADEONRestoreCrtc2Registers() - restore the registers for the secondary crtc +* RADEONRestorePLLRegisters() - restore the registers for the primary (crtc1) pixel clock +* RADEONRestorePLL2Registers() - restore the registers for the secondary (crtc2) pixel clock +* RADEONRestorePalette() - restore the palette/CLUT registers +* RADEONEnableDisplay() - enables/disables outputs +* RADEONRestoreMode() - calls the above functions + +## 2D Engine + + +### Overview + +The 2D engine (often called a blitter) basically moves data around in video ram. There are generally 4 operations done by the 2D engine: blits (copying data from one place to another), fills (draw a solid color), lines (draws lines), and color expansion (convert mono data to color data; e.g. convert monochrome font glyphs to the depth of your screen: usually 16 or 24 bit color). Logical operations (rops -- raster operations) can also be performed on the data. You have a source and destination buffers (often called surfaces) and these operations will use one or more surfaces. Some, like solid fills, only use a destination (where do I draw the red rectangle). Others like blits require a source and destination (copy this rectangle from address A to address B). Surfaces can (and often do) overlap. Because of this, blitting also has the concept of direction: if you are copying data from overlapping source and destination regions you need to make sure you copy the right data (e.g., top to bottom, right to left, etc.). Data from system memory can also be the source of these operations. This is referred to as a hostdata blit. With hostdata blits, host data is copied into a special region of video ram or into the command queue depending on the chip and from there it is copied to the destination in the framebuffer via the blitter. + +2D engines are usually either controlled via direct MMIO access to the relevant registers or via a command queue. With direct MMIO, the appropriate values are written the relevant registers and then the command is usually executed when the last reg in the series is written or when the command register is written (depends on HW). With a command queue, part of the framebuffer is reserved as a command queue (FIFO). Commands and associated data are written sequentially to the queue and processed via the drawing engine. + + +### Solid example + +Draw a solid red 200x400 pixel rectangle on the screen at (x,y) location (25, 75). + +1. Set the pitch of your destination surface to the pitch of the screen and set the offset to the offset in video ram where your screen buffer is located. +1. Set the rop you want to use +1. Set the color you want +1. Set the destination rectangle width and height and (x,y) location relative to the surface + +### Blit Example + +Copy a 200x400 pixel rectangle on the screen from (500, 400) to (25, 75). + +1. Set the pitch of your source surface to the pitch of the screen and set the offset to the offset in video ram where your screen buffer is located. +1. Set the pitch of your destination surface to the pitch of the screen and set the offset to the offset in video ram where your screen buffer is located. +1. Set the rop you want to use +1. Set the source rectangle width and height and (x,y) location relative to the source surface +1. Set the destination rectangle width and height and (x,y) location relative to the destination surface + +### Xorg Acceleration Examples + +* Blits: XAA [[ScreentoScreenCopy|ScreentoScreenCopy]]; EXA Copy +* Hostdata Blits: XAA [[ImageWrite|ImageWrite]], CPUToScreen functions; EXA [[UploadToScreen|UploadToScreen]] +* Solid Fills: XAA [[SolidFillRect|SolidFillRect]]; EXA Solid +* Lines: XAA [[SolidBresenhamLine|SolidBresenhamLine]], [[SolidTwoPointLine|SolidTwoPointLine]] +* Color Expansion: XAA CPUToScreenColorExpandFill + +### Driver Examples + + +#### Radeon + +EXA Solid Fill: + +* RADEONPrepareSolid() - Sets up the hardware state for the solid fill +* RADEONSolid() - Draws a solid rectangle of size w x h at location (x,y) +EXA Blit: + +* RADEONPrepareCopy() - Sets up the hardware state for the copy +* RADEONCopy() - Performs a copy of a rectangle of size w x h from (x1,y1) to (x2,y2) + +## 3D Engine + + +### Overview + +The 3D engine provides HW to build and rasterize a 3 dimensional scene. Most fixed function hardware has the following layout: + +* Small set of 3D state registers. These control the state of the 3D scene: fog, mipmapping, texturing, blending, etc. +* 3D engine offset registers. Controls where in the framebuffer the 3D engine renders to +* Texture control and offset registers. Control texture format and size and where the textures are located +* Depth buffer control and offset registers. Controls depth buffer layout and location +* Vertex registers. Used to specify the location and format of the vertexes which make up the 3D scene. + +### Buffers + +Generally 3 buffers are required for 3D: + +1. Front buffer. This is usually the buffer that is scanned out for the user to see. +1. Back buffer. This is the buffer that is rendered to while that front buffer is being scanned out. +1. Depth buffer. Also called z-buffer. This buffer is used to determine the relative depth of different object in the 3D scene. This is used to determine which elements are visible and which are obscured. +[[ToDo|ToDo]]: give driver examples + + +## Overlay + + +### Overview + +The overlay provides a mechanism for mixing data from multiple framebuffers automatically. It is most often used for mixing YUV (video) and RGB data. Most overlays contain special filtering and scaling hardware along with a colorspace converter. The streams are mixed or blended in several ways (depending on the hardware): + +* Colorkey. Overlay data is overlaid on the primary data stream where the color of the primary stream matches the colorkey RGB color. Generally used to overlay YUV or RGB data on an RGB surface. +* Chromakey. Same as colorkey but the key is a YUV value rather than RGB. Generally used to overlay RGB or YUV data on a YUV surface. +* Position/Offset. Overlay data appears at specified position in the scan out buffer. +When an overlay is enabled, data from the overlay framebuffer is automatically mixed into the output stream during the scanout of the visible framebuffer. For example, with colorkeying, the crtc scans out of the primary framebuffer until it hits a region with a color matching the colorkey. At this point, the hardware automatically scans the data out of the overlay buffer. + +Most hardware only has one overlay which is often tied to a crtc or can only be sourced to one crtc at a time. + +Overlays are most commonly used for video playback and scaling. See Xv. + + +### Driver Examples + + +#### Radeon + +* RADEONPutImage() - Prepares and copies overlay data to video ram, then calls RADEONDisplayVideo(). +* RADEONDisplayVideo() - Write the overlay configuration to hardware to display the overlay data. + +## HW sprites + + +### Overview + +HW sprites are small buffers that get blended with the output stream during scan out. The most common examples are HW cursors and HW icons. Sprites are usually limited to small sizes (64x64 or 128x128 pixels) and on older hardware they are limited to 2 colors (newer hardware supports 32 bit ARGB sprites). The cursor image is written to a location in video ram and that image is mixed into the output stream at a particular location during scan out. + +[[ToDo|ToDo]]: give driver examples + + +## PCI + +PCI is by now the standard bus for connecting video cards to computers. AGP and PCIE merely look like enhanced versions of PCI, as far as the host software is concerned. + +PCI devices can present various resources to the host, along with a standardized way of discovering and accessing them. The important ones as far as video is concerned are BARs, or bus address ranges. Each device can present up to 6 BARs, which can function as video memory or register banks. BARs can be either memory or I/O ranges, but are usually memory. There is also an optional "7th BAR", the option ROM, which most video devices support. This is used to support multiple video cards, since the ROM contains the initialization code for the chip, and most system BIOSes will not attempt to initialize more than one card at boot time. + +PCI also provides a mechanism for supporting the legacy VGA address space and I/O ports, by allowing the host software to route this space to individual PCI cards. Again, this is mostly used for multi-card setups. + + +## AGP + +[[ToDo|ToDo]]: fill me in. + + +## PCIE + +[[ToDo|ToDo]]: fill me in. + + +## Apertures + +[[ToDo|ToDo]]: fill me in. + +[[ToDo|ToDo]]: indexed vs. direct access registers + +-- Main.[[AlexDeucher|AlexDeucher]] diff --git a/Development/Documentation/InputEventProcessing.mdwn b/Development/Documentation/InputEventProcessing.mdwn new file mode 100644 index 00000000..92b275de --- /dev/null +++ b/Development/Documentation/InputEventProcessing.mdwn @@ -0,0 +1,112 @@ + +[[!toc ]] + +This is a puny attempt to explain how the X Server generates and processes input events. This document was created as part of the development for [[MPX|Projects/MPX]], the Multi-Pointer X Server. This document does not replace a good look at the source code. It just helps understanding what happens and what order functions are called. And it gives a general overview on how events are born and sent to the client. + +We do not give any warranty that the information here is complete and/or accurate. The information here concentrates on pointer events but some is the same for keyboard events. + +**Updated 17.06.2010. Reflects input processing in X servers 1.7 through to including 1.9** + + +## Overview + +Generally, input events live through two stages: Event generation and event processing. In the event generation stage, input is gathered from the connected devices and transformed into abstract input events, the so-called [[InternalEvents|InternalEvents]]. In the processing stage, these [[InternalEvents|InternalEvents]] events are converted to protocol events, depending on the event masks of the windows. An [[InternalEvent|InternalEvent]] may be converted into a core event, an XI 1.x event or an XI2 event. More events such as enter and leave events are generated during the processing stage as well. + +The event generation stage is part of the interrupt handling. The event processing stage is part of the processing loop (_Dispatch()_). + +In between those two stages, there is the event queue. Events are put on the event queue after the creation stage and taken off again at the start of the processing stage. Only [[InternalEvents|InternalEvents]] are ever on the event queue. + +There are only a few directories that are interesting for all that: + + * _xserver/dix_ ... device independent X. The events.c file is handling most of the events. + * _xserver/mi_ ... machine independent X. Mouse cursor rendering stuff. + * _xserver/hw/xfree86/common_ ... some additional stuff, especially the driver interface. + * _xserver/Xi_ ... X Input Extension protocol stuff. +The method the server spends the most time in is _Dispatch()_, and in this method the server mostly waits in _[[WaitForSomething|WaitForSomething]]()_ for requests from the clients and to send off accumulated input events from the input devices to the clients. + +Lots and lots of functions are called using function pointers. Finding them can be very frustrating. See [[how to set up ctags|Development/Documentation/UsingCtags]] to jump around in the source and find functions easier. + + +### The DESIGN document + +There is a document that describes the design of the X server. Depending on where you have the source tree the document is in xserver/hw/xfree86/doc/DESIGN.sgml or if you have the xserver-xorg package installed you should have it in /usr/share/doc/xserver-xorg/DESIGN.gz. + +It's worth a read but I did not find a lot of information about how input events are handled. + + +### An important requirement to understand events + +X has the concept of core devices. These are the devices that are visible in the core protocol (i.e. whenever a client issues a [[GrabPointer|GrabPointer]] request, the core pointer is picked). + +With the introduction of X Input in 1994, the definition of an extension device was added. These devices could also send XI events (e.g. [[DeviceMotionNotify|DeviceMotionNotify]]). A device could only be either an XI or a core device, not both - hence the need for the [[ChangePointerDevice|ChangePointerDevice]] and [[ChangeKeyboardDevice|ChangeKeyboardDevice]] requests. However, an extension device what was configured to "[[SendCoreEvents|SendCoreEvents]]" would cause both XI events on the device and core events on the core pointer device. + +X server 1.4 introduced the notion of a "virtual core pointer" and "virtual core keyboard" (VCP and VCK, respectively). These devices are hardcoded to be the core devices with all physical devices now being extension devices. This obsoleted the [[ChangePointerDevice|ChangePointerDevice]] and [[ChangeKeyboardDevice|ChangeKeyboardDevice]] request, the core devices were always the virtual ones. A device configured to "[[SendCoreEvents|SendCoreEvents]]" would send cause the VCP or VCK to generate a core event as well as the extension event on the device itself. + +X server 1.7 introduced XI2 and the master/slave device hierarchy. VCP and VCK are the first two "master devices", with all physical devices being "attached" to either one. These physical devices are referred to as "slave devices". Events are generated by the slave devices and then move up to the respective master device. A slave device may only generate XI 1.x or XI2 events, a master device may generate core events as well. With MPX, there may be more than one pair of master device but the principle remains the same. + +All event generation is in _dix/getevents.c_, see _[[GetPointerEvents|GetPointerEvents]]()_ and _[[GetKeyboardEvents|GetKeyboardEvents]]()_ as starting points. + + +## Event creation + +When a device emits events, a SIGIO is fired and the _xf86SIGIO()_ handler is called which in turn calls the _xf86SigioReadInput()_ for the given socket. The latter in turn calls the read input function for the pointer provided. For the mouse driver, this function is _[[MouseReadInput|MouseReadInput]]()_. The evdev driver has it own handler (_[[EvdevReadInput|EvdevReadInput]]()_) and so do all other drivers. + +_[[MouseReadInput|MouseReadInput]]_ is one of the functions in the _[[InputInfoPtr|InputInfoPtr]]_ of the mouse driver. It is set when the input driver is initialised and _[[MousePreInit|MousePreInit]]()_ is called (see section 5.6 in the DESIGN doc). _[[MouseReadInput|MouseReadInput]]()_ does all the processing for the different mouse protocols and then posts the event via _[[MousePostEvent|MousePostEvent]]()_ (again a function pointer in the _[[InputInfoPtr|InputInfoPtr]]_) into _[[MouseDoPostEvent|MouseDoPostEvent]]()_. + + * So, if you are using the mouse, the sequence executed on the driver's side is: _[[MouseReadInput|MouseReadInput]]()_, _[[MousePostEvent|MousePostEvent]]()_, _[[MouseDoPostEvent|MouseDoPostEvent]]()_; + * The generic sequence is _Driver-specific [[ReadInput|ReadInput]]_, _driver-specific processsing_, _xf86Post{Motion|Button|Keyboard|Proximity}Event()_ +For a motion event, the driver calls now _xf86PostMotionEvent()_ and we are back on the server's side. For button events it is _xf86PostButtonEvent()_. Those in turn call _[[GetPointerEvents|GetPointerEvents]]()_ (_[[GetKeyboardEvents|GetKeyboardEvents]]()_ for keyboard events) which creates the necessary number of events and returns them to the caller. _[[GetTimeInMillis|GetTimeInMillis]]()_ is called inside _[[GetPointerEvents|GetPointerEvents]]()_ and timestamps the OS time on the event. Inside the same function, _miPointerSetPosition()_ is called to re-paint the mouse on the screen. It calls _miPointerMoved()_. The _miPointerMoved()_ decides to **start the hw or the sw management/rendering of the cursor** (see section _Cursor rendering_). After this choose the events are put - one by one - onto the event queue using _mieqEnqueue()_. + +Note that all this is inside the SIGIO handler, this is important as you may not allocate of free memory at any time in this stage. + +_[[GetPointerEvents|GetPointerEvents]]()_ will generate a number of [[InternalEvents|InternalEvents]], for this tutorial the interesting onces are the [[DeviceEvents|DeviceEvents]] which represent physical input (motion, button, key events) + +**To sum it up in short: each time a interrupt happens on one of the sockets to an input event, the device driver reads the data, hands it back to the X Server which constructs one or more _[[InternalEvents|InternalEvents]]_ and puts it onto the event queue.** + + +## Event processing + +The event processing stage is the stage where the events are taken off the event queue, individually processed and then sent to the client. Also, more abstract input events (enter and leave notifies) are generated synthetically here. + +All input are processed in the DDX _[[ProcessInputEvents|ProcessInputEvents]]()_. The actual processing is done in _mieqProcessInputEvents()_ which runs through the event queue from beginning to end. Main entry point for DIX-specific processing is _[[ProcessOtherEvent|ProcessOtherEvent]]()_, all events pass through here. Note at this point that the XKB extension wraps _[[ProcessOtherEvents|ProcessOtherEvents]]()_ and is called before we get to POE. XKB is not subject to this tutorial. + +_[[ProcessOtherEvent|ProcessOtherEvent]]()_ does a few things. It updates the DIX-internal device state with the information from the event, then gathers some state required for the event itself. For example it grabs the modifier state from the keyboard to be put into mouse events as additional info. Finally, it calls down into the delivery paths that eventually write the protocol event onto the wire. At this point, we're still dealing with [[InternalEvents|InternalEvents]] only. + +_[[ProcessOtherEvents|ProcessOtherEvents]]()_ also calls _[[CheckMotion|CheckMotion]]()_. This function updates the cursor sprite's position and then sets the event's coordinates to the new sprite positions. Finally, we compare the window the updated sprite is over with the previous one and call _[[DoEnterLeaveEvent|DoEnterLeaveEvent]]()_ if necessary. If the window has changed, we also issue a call to _[[PostNewCursor|PostNewCursor]]()_ which basically changes to the updated cursor shape. + +Let us see what _[[DoEnterLeaveEvent|DoEnterLeaveEvent]]()_ does. If the old window is a parent of the new window, we issue a _[[LeaveNotify|LeaveNotify]]_ to the old window, then recursively send _[[EnterNotify|EnterNotify]]_ events to the ancestors of the target window (this is done in _[[EnterNotifies|EnterNotifies]]()_) and then finally a _[[EnterNotify|EnterNotify]]_ to our new window. If the old window is a child of the new window, we do the same but with the leave and enter notifies swapped around. Finally, if the window are not related, we send a _[[LeaveNotify|LeaveNotify]]_ to the old window and then recursively to its parents (using _[[LeaveNotifies|LeaveNotifies]]()_), then recursively send _[[EnterNotify|EnterNotify]]_ events (using _[[EnterNotifies|EnterNotifies]]()_ again) to the new window's parents and finally a _[[EnterNotify|EnterNotify]]_ to the new window. Remember that there are multiple types of _[[EnterNotify|EnterNotify]]_ and _[[LeaveNotify|LeaveNotify]]_ events. The ones sent to the parents are all of type _[[NotifyVirtual|NotifyVirtual]]_ (or _[[NotifyNonlinearVirtual|NotifyNonlinearVirtual]]_ if the windows are unrelated). The ones sent to the old and the new window are of types _[[NotifyAncestor|NotifyAncestor]]_ or _[[NotifyInferior|NotifyInferior]]_ for related windows and _[[NotifyNonlinear|NotifyNonlinear]]_ for unrelated windows. All enter and leave events are constructed in _[[EnterLeaveEvent|EnterLeaveEvent]]()_. A _xEvent_ is created, filled with values and then sent to the window using _[[DeliverEventsToWindow|DeliverEventsToWindow]]()_. Again, rootX and rootY is taken from the sprite coordinates. This is the simple explanation, the real implementation is somewhat more difficult as we need to synchronise Enter/Leave events to be protocol-correct even if there are multiple master devices present. + +So now that we have finished the enter/leave events we concentrate on what the final event processing consists of. The rule here is: an [[InternalEvent|InternalEvent]] may be delivered as exactly one protocol type, but possibly to multiple clients. So if two clients both selected for core events, both will get the core event. If one client selected for core events and one for XI events, only the XI event is delivered. In the final event delivery path, the client masks are checked on each window in the delivery path and the [[InternalEvent|InternalEvent]] is converted to the respective protocol event. + +The event is adopted to the window in _[[FixUpEventFromWindow|FixUpEventFromWindow]]()_ and then delivered to the window with _[[DeliverEventsToWindow|DeliverEventsToWindow]]()_. _[[FixUpEventFromWindow|FixUpEventFromWindow]]()_ adopts the window specific values to the event's window (the child, eventX and eventY values). If the delivery failed to a given window, the parent is tried until we run out of parent windows. _[[DeliverEventToWindow|DeliverEventToWindow]]()_ calls _[[TryClientEvents|TryClientEvents]]()_ to write the events to the client. If the event is a button press event, _[[DeliverEventToWindow|DeliverEventToWindow]]()_ also activates the implicit pointer grab (a grab that is deactivated automatically on the next button release event). + +Now we have completed event processing, all the events were written to the client and we jump back to the last lines of _[[ProcessInputEvents|ProcessInputEvents]]()_. What is left now is cursor rendering (if applicable), called with _miPointerUpdateSprite()_. + +**Again, a short summary of the event processing stage: the server takes the events off the queue, fills them with the right variables, generate enter and leave notifies if necessary and writes them to the client.** + + +## Cursor rendering + +Cursor rendering is a bit complicated to understand and hard to debug. It is a layered architecture to do as much in hardware as possible and pretty much everything is called via function pointers. Some need for function pointers has been removed with 1.9, but the basic priniciple is the same. + + +### hw cursor + +If the cursor is fully rendered in hardware, _xf86CursorMoveCursor()_ and _xf86MoveCursor()_ are the two first functions called. These functions are called just after the _miPointerMoved()_, the function that decides if the render will be in sw or hw, on the event creation stage. _xf86MoveCursor()_ will call the video driver function desired to take care of the hw rendering. On my case, _ATIMach64SetCursorPosition()_ is called. It do the calculations and paint the sprites on the memory mapped directly to the output stream. In other words, **exactly on this moment the mouse is moved on the screen**. + + +### sw cursor + +If it is done in sofware, the cursor has to be back-buffered. Every time it moves we restore the previous image, save the window at the target position, then render the cursor into the stream. + +We start with everything at the end of _[[ProcessInputEvents|ProcessInputEvents]]()_ and the call to _miPointerUpdateSprite()_. Here we grab the current coordinates of the pointer (remember, they were set when we called _miPointerMove()_ in the event generation stage) and call the _[[MoveCursor|MoveCursor]]_ function in the _spriteFuncs_ of the _miPointerScreenRec_ struct. Of course, if the cursor has changed screen or the shape has changed, this needs to be taken care of too. The _[[MoveCursor|MoveCursor]]_ function is set to _miSpriteMoveCursor()_ which just calls _miSpriteSetCursor()_. This function first checks whether the cursor has changed at all and then the new positions of the cursor. The cursor is then removed with _miSpriteRemoveCursor()_ and then restored at the new position with _miSpriteRestoreCursor()_. _miSpriteRemoveCursor()_ is fairly simple, it just calls the restore function _miDCRestoreUnderCursor()_, which then calls the next layer (damage) to copy the saved area into the window at a given position. _miSpriteRestoreCursor()_ saves the area under the cursor (_miDCSaveUnderCursor()_) into the buffer and then puts up the cursor again (_miDCPutUpCursor()_). If, as mentioned before, the new position is insided the saved buffer, a call to _miDCChangeSave()_ updates the saved region and a call to _miDCMoveCursor()_ will move the cursor. This moving doesn't cause any flickering, the remove and restore procedure may flicker. + +As easy as this sounds, there is more to cursor rendering. Quite a fair bit of work is done outside this explicit rendering calls that are issued when all input events have been processed. Interestingly, pretty much all other function that handle sprite rendering (everything with _miSprite..._) basically remove the cursor from the screen if necessary (i.e. when the window is moved). The one exception is the block handler function (called when there's nothing else to do and the server would block while waiting for input). _miSpriteBlockHandler()_ checks if the cursor was previously removed but should be visible and renders it to the screen again if necessary. + +**What must be clear on the cursor rendering is: hw cursor is rendered before the event be enqueued (i.e., on the event creation stage) and sw cursor is rendered after the _[[ProcessInputEvents|ProcessInputEvents]]()_ (i.e., after the event creation and after the event processing stage).** + + + +--- + + [[CategoryServerInternals|CategoryServerInternals]] diff --git a/Development/Documentation/KdriveDrivers.mdwn b/Development/Documentation/KdriveDrivers.mdwn new file mode 100644 index 00000000..4c63eaf3 --- /dev/null +++ b/Development/Documentation/KdriveDrivers.mdwn @@ -0,0 +1,10 @@ + +# moved from [[http://www.freedesktop.org/wiki/Software/KdriveDrivers|http://www.freedesktop.org/wiki/Software/KdriveDrivers]] + + * pScreenPriv->fb[] is an array of 1 or 2 KdFrameBuffers. fb[0] is primary, while fb[1] is only set up if you have an overlay. fb[0]->depth is the color depth (1, 4, 8, 15, 16, 24) for that framebuffer, while fb[0]->bitsPerPixel is how many bits are taken up for storage (?, 8, 16, 24, 32). + * The depth and bitsPerPixel won't change between the card's initAccel and finiAccel -- it was decided depth changes were too costly to do. + * If your hardware doesn't support acceleration for the 24 bitsPerPixel case, one way to get around this is to put the accelerator in 8-bit mode and multiply X coordinates by 3. However, if you do this you need to make sure for Solid fill that the pixel's values are the same for each of the bytes, and return FALSE from PrepareSolid if not (unless your hardware has ability to rotate the pixel data, as in the mach64 driver). Also make sure the planemask won't have problems with rotation, and return FALSE if so. + * Many things are not available at initScreen and scrInit time. It's okay, because almost all setup/teardown for your device should be done in initAccel/finiAccel. These two are called on entering and exiting the server's VT. Things that can be done include but are not limited to initializing extensions and allocating window/pixmap/screen/etc. privates. + * If your driver uses hw/kdrive/vesa or hw/kdrive/fbdev for card initialization and mode setting, your driver's card and screen private records must begin with the fbdev or vesa card and screen private structs, because vesa and fbdev will use the kdrive card->driver and screen->driver pointers to get at their private data. + * should kaaDrawFini() be called in the accelDrawFini() function? +-- Main.[[EricAnholt|EricAnholt]] - 20 Nov 2003 diff --git a/Development/Documentation/Multiseat.mdwn b/Development/Documentation/Multiseat.mdwn new file mode 100644 index 00000000..65d3d3ce --- /dev/null +++ b/Development/Documentation/Multiseat.mdwn @@ -0,0 +1,47 @@ + + +# Multiseat + +[[Multiseat|http://en.wikipedia.org/wiki/Multiseat]] is a model of computing that supports multiple local users using their sessions in a totally independent way. This looks quite similar to the old mainframe computer model, but with the "terminals" connected directly to single PC box. There's a lot of people that use and sell multiseat Linux systems due its low cost which qualifies it as a wonderful "techno-social" model of computing. With the current version of X (1.7.6) and wisely chosen hardware, is it possible to get working multiseat configuration by just editing few configuration files as documented for example on [[Ubuntu MultiseatX page|https://help.ubuntu.com/community/MultiseatX]] + +In this sense, the intention of this page is the following: + +* to collect all spare documentations and give a guidance to users that want to deploy such model, and; +* to help its development. + +## Information to Users + +There are different solutions to setup a multiseat system. The old -- but still used -- way is through HOWTOs, that show how to configure the xorg.conf, the display manager (e.g. gdm, kdm) and the association of devices to seats. There are a huge pile of HOWTOs in the Web. Basically the HOWTOs show two different approach of configuration: + +* multiple Xephyr servers (or Xnest) over a host Xorg, and +* multiple instances of Xorg. +The Xephyr's approach is known to work with "any" video card vendor but lacks some extensions (3D, OpenGL) and has the latency for being nested servers. The "multiple Xorg" approach is "right way", but it only work with a limited video cards. + +When each seat is just a collection of USB devices (including USB graphics, input, etc.), this multiple xorg approach works (because there are no VGA arbitration issues, etc), and multiseat has the potential to be plug and play via udev rules. Instructions and current limitations for this type of implementation on recent versions of Ubuntu are at [[http://libdlo.freedesktop.org/wiki/MultiSeatTerminal|http://libdlo.freedesktop.org/wiki/MultiSeatTerminal]]. + +The [[Multiseat Display Manager|http://wiki.c3sl.ufpr.br/multiseat/index.php/Mdm]] (MDM) tool help to automatize the process of installation and configuration for multiple PCIe graphics cards. Despite its name, MDM is actually a wrapper on the real display manager. It is used to configure multiseat environments, allowing users to change a normal machine into a multiseat machine by just installing a package. The current version of MDM is only configuring the Xephyr's based solution. + +* [[http://userful.com|http://userful.com]] (commercial solution, but [[free for personal use|http://www2.userful.com/products/downloads/free-2-user]]. Single virtualized xServer, high performance approach and widely used, over 400,000 seats deployed, supports single-chip dual-head video cards) +* [[http://en.wikibooks.org/wiki/Multiterminal_with_Xephyr|http://en.wikibooks.org/wiki/Multiterminal_with_Xephyr]] (slower performance as it relies on nested Xservers, but supports broader hardware than the MSS approaches below, over 40,000 seats deployed) +* [[http://wpkg.org/Configuring_multiseat_X_workstation|http://wpkg.org/Configuring_multiseat_X_workstation]] (Multiple Simultaneous xServers (MSS), less dependable hardware support) +* [[http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html|http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html]] (MSS) +* [[http://wiki.debian.org/Multi_Seat_Debian_HOWTO|http://wiki.debian.org/Multi_Seat_Debian_HOWTO]] (MSS) +* [[https://fedorahosted.org/multiseat/|https://fedorahosted.org/multiseat/]] (MSS) +* [[https://help.ubuntu.com/community/MultiseatX|https://help.ubuntu.com/community/MultiseatX]] (MSS) +* [[http://www.linuxtoys.org/multiseat/multiseat.html|http://www.linuxtoys.org/multiseat/multiseat.html]] (MSS) +* [[http://netpatia.blogspot.com/2006/09/multiseat-computer-with-ubuntu.html|http://netpatia.blogspot.com/2006/09/multiseat-computer-with-ubuntu.html]] (MSS) +* [[http://www.automation.dn.ua/linux/3d-multiseat_en.html|http://www.automation.dn.ua/linux/3d-multiseat_en.html]] (MSS) +* [[http://www.gentoo-wiki.info/HOWTO_Multiseat_X|http://www.gentoo-wiki.info/HOWTO_Multiseat_X]] +* [[http://vignatti.wordpress.com/2008/09/23/multiseat-roadmap/|http://vignatti.wordpress.com/2008/09/23/multiseat-roadmap/]] +Users are also encouraged to read the [[Wikipedia's article|http://en.wikipedia.org/wiki/Multiseat]] about multiseat. + + +## Development + +* [[Wikipedia's article|http://en.wikipedia.org/wiki/Multiseat]] (nice historical references) +* [[Multiseat's roadmap|http://vignatti.wordpress.com/2008/09/23/multiseat-roadmap/]] (Set 2008). +* [[VgaArbiter|VgaArbiter]] +* Integration with the rest of the system: + * [[ConsoleKit|ConsoleKit]] + * [[PulseAudio|PulseAudio]] + * hal/udev
\ No newline at end of file diff --git a/Development/Documentation/Obsolescence.mdwn b/Development/Documentation/Obsolescence.mdwn new file mode 100644 index 00000000..6fac304c --- /dev/null +++ b/Development/Documentation/Obsolescence.mdwn @@ -0,0 +1,714 @@ + + +# Notes on the status of X.Org technologies + +Jim Gettys has kindly contributed the attached long-running draft document describing the status of various X.Org technologies. This draft is from October 2008, and much of its content is from 2004, so it is a bit old. However, it still contains much useful information. If someone wants to take over its maintenance and put it up on the wiki, let me (bart at cs dot pdx dot edu) know. No fair making fun of it or critiquing it; it was very kindly donated and is known to need work. + +[[roadmap-2-clean.pdf|roadmap-2-clean.pdf]] + + +# Open Source Desktop Technology Road Map + +Jim Gettys, Version 2.0, October 23, 2008 + + +## Abstract + +Navigating the myriad technologies that comprise the desktop (and palmtop) on open source systems is daunting to say the least, for newcomers of all sorts, open source developers, developers in companies using the technologies internally, and commercial ISVs, and even difficult to navigate for those immersed in open source systems on a day to day basis. + +This document attempts to give a sketch of the names and relationships of these technologies and projects, and a glimpse into their status and development. Some technologies have never proved themselves, and/or have been rendered obsolete by later development and are available primarily for legacy code. This document attempts to clarify much of this natural evolution and market selection. Ultimately, some technologies become so rare as to enable their interment into the strata of software history, and it can be important to know which technologies are in such a fossil state, or stuck in the Labrea Tar Pits and possibly doomed to extinction, if not yet dead. A few may manage to struggle their way out of the tar to safety on dry land again. + +Some indication of the licensing terms is made. For commercial software, make sure you understand the differences between licenses. For example, GPL and LGPL'ed libraries have very different consequences; one requires that source code of applications linked against them be made available, and the other does not require such disclosure. It is also possible for software to be available simultaneously under multiple licenses, sometimes allowing the implementer to choose which applies. See the Open Source Initiative for an explanation of these licenses. + +Where known, approximate dates of expected completion are included, but there is no guarantees made. If you would like to ensure the timely completion of technologies under development, you should work with the community to determine if further resources are needed, and if so, to contribute the talent, resources and funding to do so. + +Note that this document is still a bit weak in futures and I plan further work in this area. As in a map of a physical area, having information about current areas and how they interrelate was the first goal. + + +## Acknowledgments + +This document is the work primarily of its author, and the opinions here are my own; blame me for any errors and biases. Please let me know of any inaccuracies, and in particular, pointers to road maps of projects mentioned here. I would much prefer to have good pointers to similar project road maps than my current (mis) understanding of their time lines and development state, which is, of course, in a constant state of flux. + +Similarly, if you believe I have overlooked some key piece of open source desktop middleware technology (as opposed to end user applications which are too numerous to list), please let me know. + +My thanks to Keith Packard, Jamey Sharp, Kevin Whitwell, Waldo Bastian, and Eric Raymond, Zenaan Harkness, David Alan Gilbert, Maarten Stolte, Maarten Stolte, Kurt Pfeifle, Brenda J. Butler, Zenaan Harkness, Eero Tamminen, Brian Gallaway Sergey V. Oudaltsov, John Smirl, and Vincent for constructive comments and feedback on Version 1 of this document. + + +## Table of contents + +Open Source Desktop Technology Road Map + +1. Abstract +1. Acknowledgements +1. Table of contents +1. Introduction +1. Specifications + 1. ICCCM + 1. Freedesktop specifications +1. X Window System + 1. Key protocol extensions/libraries + 1. Xlib - basic X library + 1. 3D libraries + 1. Mesa - The 3D Graphics library + 1. Direct Rendering Infrastructure (DRI) + 1. XInputExtension + 1. SHAPE + 1. XSYNC + 1. XVideo + 1. DOUBLEBUFFER + 1. The X Resize and Rotate Extension (RandR) + 1. Security + 1. Record + 1. XTest + 1. Render + 1. Xft2 library + 1. Xinerama + 1. Xnest + 1. X extensions under active development + 1. Obsolete X extensions + 1. X libraries under active development + 1. X toolkits + 1. GTK+ toolkit + 1. Qt toolkit + 1. Other toolkits + 1. Moribund X toolkits + 1. Motif + 1. TK + 1. Other key libraries + 1. Fontconfig - font configuration library + 1. Freetype 2 - font rendering + 1. Cairo - vector graphics library + 1. Hardware Abstraction Layer (HAL) + 1. DBUS - message bus system + 1. XML libraries + 1. Pkgconfig + 1. Zeroconf + 1. Multimedia + 1. Multimedia frameworks + 1. Helix community + 1. aRts + 1. Gstreamer + 1. Mplayer + 1. VideoLAN + 1. Xine and Xinelib + 1. Audio + 1. Advance Linux Sound Architecture (ALSA) + 1. Audio servers + 1. aRtsd + 1. Enlightened Sound Daemon (ESD) + 1. Jack + 1. MAS + 1. Microsoft interoperability + 1. SAMBA + 1. File systems + 1. File formats + 1. WINE + 1. Winelib + 1. DOS emulation + 1. .Net and Mono + 1. Displaying Windows applications on Open Source systems + 1. X implementations for Windows + 1. Cygwin and Cygwin/X + 1. Cygwin/X + 1. Commercial X implementations + 1. Fonts + 1. Printing + 1. Postscript and PDF + 1. Common Unix Printing System (CUPS) - print spooling system + 1. Thin clients + 1. Linux Terminal Server Project (LTSP) + 1. Athena Computing Environment + 1. Java + 1. VNC + +## Introduction + +The most visible desktop projects are the KDE and Gnome desktop projects. These projects provide the basic toolkits, window managers, menu systems and control panels found in modern user interfaces along with many end user applications. It is important to note that the work of freedesktop.org is to ensure that applications and infrastructure can be shared between projects, and to enable this sharing in a way that end users do not know or care what environment these applications may be "native" to. In large part, this goal of freedesktop.org is being met, though there is more work to be done. The Gnome project's roadmap covers its next few releases. + +Other major applications projects, which themselves may be platforms on which other applications are being built include the Open Office project (Sun's [[StarOffice|StarOffice]] suite is based on [[OpenOffice|OpenOffice]]), providing a entirely free office suite, and their plans can be found in their road map. Better integration with other applications on the desktop is high on that list; Open Office has used their own toolkit and needs better integration with Gnome and KDE. + +The Mozilla project is also of special mention, who have built a world class free web application suite supporting all the widespread Web technologies (e.g., CSS, Javascript, etc.), including browser, mail client, bug tracking system, and other technology, used not only in their applications but also by other applications in the open source desktop. Mozilla's road map covers both its recent history and current plans. Another implementation of web technologies underlies the KHTML Rendering engine of the KDE project and Apple in Mac OS X, and is now called webkit; it may be becoming a viable alternative to the Firefox gecko rendering engine. Firefox has the distinction of having seriously undermined Microsoft's control of the web; its 20% market share (along with the additional marketshare of webkit, most notably in Mac OSX Safari) has wrested back control to web standards from their proprietary technologies. + +Native plugins exist, often many, for most of the commonly used web datatypes (e.g., flash, [[RealPlayer|RealPlayer]], PDF). There are a few reasonably common datatypes for which there is no good native plugin available (fewer and fewer as the months go by). Windows plugins can often then be used via WINE. One of the interesting problems is in fact, too many plugins for a given datatype. Better user interfaces to invocation of plugins have helped ameliorate this problem in current desktops, and Linux distributions have matured and reduced the number of options presented to a naive user to a reasonable defaults to help with this embarrassment of riches. A few datatypes remain difficult, but great strides have been made since V1 of this document. + +The desktop applications themselves are far too numerous to begin to mention. A (large) subset of open source applications of all sorts numbering in the many thousands can be discovered on the Freshmeat web site, in addition to the KDE and Gnome desktop projects. All of these projects build on the technologies covered in this road map (and sometimes additionally run on Windows and Mac OS X, most particularly the X Window System, but attempting to provide a road map to those projects is outside of the scope of this document. + + +## Specifications + +Historically, the X specifications were developed and ratified in the MIT X Consortium, and its successor organization, X.org. X.org has morphed successfully from an industry consortium to an organization in which individuals, both at a personal level and as part of work they do for their companies have voice, working as part of the larger freedesktop.org and free standards community. Current X.org releases form the core of the free desktop. + +As discussed below, the X Window System was designed to allow for extension, and many extensions as outlined above have been developed, deployed, and sometimes discarded over the years. Note that an API is just one binding to the specific protocol; there are and have been multiple such APIs and implementations at times to the same underlying set of protocols. + +Besides the APIs and protocols mentioned below, there are a set of other protocols and (sometimes multiple) implementations of APIs that are involved in the overall open source desktop. Most of these are primarily of interest to toolkit, window manager, and desktop environment programmers rather than directly to most application programmers. This section attempts to outline the most important of these, and their current status. + + +### ICCCM + +The original "Inter-Client Communications Conventions Manual" outlines the original set of conventions required of applications (mostly implemented in toolkits rather than directly by applications) to "play well" in the modular environment of the X architecture, allowing for interchangable window managers, and other facilities. It was (mostly) sufficient to implement the CDE desktop, but insufficient for more modern environments. These (along with the EWMH (extended window manager hints) are built on top of the X11 core protocol using its general atom and property mechanism. + + +### Freedesktop specifications + +Freedesktop.org was founded to foster the discussions between the Gnome and KDE desktop projects to extend the ICCCM in ways required for more modern environments. It now often hosts core desktop infrastructure projects (e.g., X, dbus, etc.). + +Areas needing work to ensure further interoperability of applications build in one toolkit framework to be fully usable in others has included drag-and drop, window manager extensions, desktop entry files that describe information about applications, application embedding, UTF-8 support, bookmark exchange, menus, mime database, desktop settings, to name a few. Descriptions of the status of these specifications along with the specifications themselves are available and I recommend you look there for more information. + + +## X Window System + +The X Window System, Version 11, or X11, or most commonly called X, is the network transparent window system used on Linux, UNIX, and other platforms including Macintosh OS/X, and Microsoft Windows. It provides the basic infrastructure from which graphical user interfaces are built on Linux and UNIX. X11 was first released in 1988, and has an unrivaled reputation for stability; applications running on a MicroVAX of that era will interoperate against the latest X implementations across today's network, unchanged. This stability has been ensured by a careful, extensible protocol design framework, and attention to detail in the addition of new features. + +I gave a USENIX talk on open source software development using the X Window System history that may be of interest. + +New X extensions have been defined in recent years to bring X's original capabilities up to (and in some cases well beyond) the proprietary state of the art. Whenever possible, these programmer's APIs have been built to allow even downwards compatibility to ease deployment of modern applications to older X server implementations. A good example of this is the Xft2 library, which, while performing best on X implementations where the X Render extension is present, will in fact provide high quality anti-aliased text on old X servers. In some areas X still needs work; much of this work is underway as described below and in more detail elsewhere. + +In the X environment GUIs are built using Toolkit libraries, of which the most common at this date are Qt and GTK+. Motif based applications from the earlier generation of development on UNIX are now extremely rare (except as legacy applications inside and of corporate environments). + +A component of an X Window System based environment not found as an independent component in other window systems is the external "window manager", which allows users to control the size, location and decoration of application's windows on the screen. They are, in fact, applications like any other application in X11, though you can generally only run one window manager at a time. Window managers are, for the most part, interchangeable components, and the standards defined originally by the X Consortium such as the ICCCM, and its successor X.org, along with the new specifications developed on freedesktop.org govern the protocols between applications and window managers. Window managers in common use today include KDE's window manager, Compiz Fusion or Metacity used by Gnome, and many, many others. Those that have been kept up to date with the freedesktop.org specifications are generally interchangeable and a matter of personal taste, though both major desktop projects have window managers they prefer, and which may integrate best into that environment. Some of these (e.g., Compiz Fusion) provide amazing visual eye-candy if requested, though mercifully, its default behavior is now sane. + +Other components, such as panels, start buttons, file managers, and many basic applications are provided by the desktop systems. The largest and most well known of these projects are the Gnome desktop project, the KDE desktop project, and the CDE desktop previously used on UNIX systems. CDE is dead. A detailed road map of these projects is outside the scope of this document. The projects have a life of their own, and you are best consulting them as to their plans. They encompass many thousands of open source applications at this date. + +There are multiple implementations of the X Window System which share code, both open source and provided by commercial vendors. The commonly deployed implementation on open source systems is currently provided by X.org which hosts its development here at freedesktop.org. XFree86, while still existing, has become a relic of the past, triggered by its license change and general disgust with its policies. + +There is much mythology of X's size; this is mostly an artefact of how memory usage is reported on systems (the entire frame buffer, off screen memory and any register space is reported against the X server's process's size, even if X itself is only consuming a megabyte or two of space itself). Similarly, some applications request X to save large amounts of pixels on their behalf, when other implementation approaches often easily avoid such memory usage. X is being successfully used on systems from IBM's Linux watch with 8 megabytes of compressed flash and 8 megabytes of RAM with a tiny 96×120 screen, to current PDAs like HP's iPAQ, to DMX based projector walls containing tens of millions of pixels. With recent work, the minimal X footprint (X server and cut down Xlib) is currently just over 1 megabyte of code (uncompressed), excluding toolkits that are typically much larger, and could be cut smaller. After all, X11 was developed on VAX 11/750s that had less than one MIP with 2 megabytes of RAM. + + +### Key protocol extensions/libraries + +These protocol extensions generally come with a C language library, that is often just a wrapper around the protocol, but sometimes includes additional functionality. + +The Freedesktop.org X server and the XFree86 X server along with all base protocol libraries are MIT licensed, Commercial vendors of X technology may have additional restrictive licenses placed on their implementations as allowed by the MIT license. + + +#### Xlib - basic X library + +This library provides the basic protocol bindings and client side support for extensions, as well as a number of other facilities, some of which are useful, and some of which do not or have not seen serious use recently. The Motif toolkit uses more of these features than more modern toolkits such as GTK+ or Qt, which, for example, have found Xlib's facilities inadequate in a number of areas (e.g., internationalization). As the basic library for the X protocol, its API is very stable. + +Several sections of the Xlib API are seldom used in modern practice, either because the facilities never achieved widespread acceptance (as in the X Color management part of the API), or because modern toolkits have found that they needed more advanced facilities (as in the Locale section of the Xlib API), where the modern toolkits provide better facilities. + +A replacement for Xlib's protocol bindings called Xcb can offer better performance by making it easier to avoid round trip messages to the window system in some areas. It has recently been deployed underneath the Xlib bindings to allow a migration strategy for applications that use plug-ins. The Xlib interface remains exactly API compatible with the old implementation. Work can now begin to take advantage of this in toolkits. Xcb was also carefully designed for thread safety, which was very difficult indeed in the old Xlib implementation. + +Some work was underway to enable applications to be properly notified of connection failure with the X server (often seen when X is used over wireless networks, and sometimes over the wired internet) and allow for graceful shutdown. It was put on hold in favor of Xcb and would be nice to resurrect now that this work is maturing. This will enable the migration of running applications between X displays and movement of sessions. You would like to be able to go home and (securely) retrieve the applications running on your desktop at work. The GTK+ toolkit already has support for migration of applications, except for proper shutdown in the case of failure, and architecturally, this should be true for Qt as well. We hope that this will become usable during 2004, and widely deployed during 2005. + + +#### 3D libraries + +3D is provided in the open source environment by industry standard OpenGL. Both closed source commercial and open source implementations of OpenGL are available. With the increasing industry cooperation in providing documentation and programming resources, the open source implementations are rapidly becoming truly competitive, and may reach parity or exceed proprietary implementations during 2009 and 2010. A few vendors (e.g., Nvidia) still do not provide documents or resources for supporting their hardware and should be avoided whenever possible. + + +##### Mesa - 3D graphics library + +Mesa is an open source 3-D graphics library with an API which is very similar to that of OpenGL. Mesa is used as the core of many hardware OpenGL drivers for XFree86 within the DRI project. Software only implementations of Mesa are generally available even if hardware accelerated versions are not, but such implementations of Mesa will not be sufficient for more than very simple applications. + +GLX is the binding of OpenGL to the X protocol, to allow for network transparent OpenGL applications. Mesa has been a project for more than 10 years, and various parts of it are available under a number of open source licenses. + + +##### Direct Rendering Infrastructure (DRI) + +DRI is the direct rendering infrastructure for the X server for OpenGL direct rendering, and provides the device driver and coordination with the window system to allow 3D applications direct access to the display hardware. The DRI does not assume or require that the drivers be based on Mesa. Several non-Mesa, closed source drivers have used the DRI. + +The DRI provides direct access to graphics hardware in a safe and efficient manner. It includes changes to the X server, to several client libraries, and to the kernel. The first major use for the DRI is to create fast OpenGL implementations. + +It has been in use for a number of years, and is widely deployed with drivers for much of the common 3D hardware. DRI2 has started deployment. + + +#### MPX + +Peter Hutterer has done amazing work called "MPX", or Multi-Pointer X, enabling multiple input devices and multiple cursors in the X Window System. Part of this work has just been released in the X.org 7.5 release. + + +#### XInputExtension + +XInput provides support for "non-core" input devices, such as trackballs, dial boxes, tablets, etc. It provides adequate facilities for these devices, but work continues to extend XInput to support "hot-plug" input devices. Addition of new input devices may still require manual configuration of the X server, but probably not by the end of 2009. Work is also needed to aid use of new facilities provided by the base operating system (e.g., /dev/input) in Linux. + +This area needs some serious work. GTK+ application migration can already be demonstrated, and what is there is only adequate for session migration. Shared displays (e.g., a projector being simultaneously used by multiple users) bring to fore another issue: that of network transparent access to input devices. If I have an application I have migrated to a remote display, I may want my keyboard, mouse and other input devices to follow. While X applications like x2x help, this is really just a bandaid, and a more generic network input event mechanisms are needed, with good integration into the environment. You should be able to use devices anywhere in your environment. With hotplug a reality, building such a network environment is now possible and awaits eager hackers. + +Xinput V2 and a revision of the X keyboard extension are planned for the next year. + + +#### SHAPE + +The Shape extension provides non-rectangular windows in the X environment, and is universally deployed in X implementations. + + +#### XSYNC + +The X Synchronization Extension provides facilities for applications to synchronize with each other, and with real time. XSYNC is widely deployed and in its current form, very stable. + +Facilities to allow XSYNC to synchronize with video vertical retrace, audio sample clocks and other time bases are easy to add (and were the original intent of XSYNC), but while some work has been done to do this on Linux systems, it is not yet available in production X servers. It is also used by toolkits to synchronize repainting with the compositing manager. + + +#### XVideo + +The XVideo extension provides support for video overlays, and similar facilities desired for video playback. It is commonly available on displays with hardware support for video playback. It provides facilities for the scaling and conversion of HSV data. + +The better implementations no longer use chroma keying for display of video data, so that video can be composited as a first class citizen in the new world order. + + +#### DOUBLEBUFFER + +The DOUBLEBUFFER extension provides double-buffering facilities. It is widely available and supported. + + +#### The X Resize and Rotate Extension (RandR) + +Randr provides facilities for resizing, rotating, and reflecting the screen. It may also report root window size changes to (interested) clients. + +RandR's support depends upon the state of driver support for RandR. The XFree86 server only has support for size changes in XFree86 4.3. The Kdrive server provides full support for the extension. It is relatively new and not universally available. Applications can usually be oblivious to its existence, though window managers and toolkits should consider support. Both Gnome/GTK+ and KDE/Qt have good support for RandR at this date. + + +#### Security + +The Security extension was introduced to address the security issues of mixing trusted and untrusted clients on a single X server, according to compartmented mode workstation thinking of the early 1990s. + +The old X security extension does no serve sany useful purpose in most of today's environments, however, different facilities are needed, particularly for shared displays. Work done by Eamon Walsh of the NSA has provided X with a generic security framework into which different policies can be plugged (their plan is an SELinux like model; but others may be more usable for other environments); while this work is not quite complete, it is maturing rapidly. Our thanks for the efforts. + + +#### Record + +The Record extension provides facilities for recording the operation of the X server, and is often used in concert with the XTest extension for window system and application testing. It is stable and widely deployed. + + +#### XTest + +The XTest Extension is primarily intended to allow for pretty thorough testing of the X server, by synthesizing input. As such, it is also used in some other situations when synthetic input to the window system is needed (e.g., stroke recognition). + +There are two extensions by this name (cool, huh?). + +The small XTEST extension was developed by Unisoft as a part of their Xlib test suite development to test pieces of the system which are otherwise unreachable.It is widely deployed and very stable. The larger XTestExtension1 was developed by HP to help produce automated application testing mechanisms. This is not deployed and an architectural nightmare and can be considered extinct. Everyone uses XTEST to synthesize input instead of XTestExtension1. + +It is widely deployed and stable. + + +#### Render + +The largest visible change in X is recent, with the addition of the X Render Extension, which provides Porter-Duff image compositing to the graphics capability of the X Window System. It is now widespread and used by most modern toolkits particularly for text, which is now rendered as alpha-composited, anti-aliased glyphs cached in the X server, completely supplanting the "core" text facilities of the original X11 protocol. The old "core" text facilities (bitmaps only) are still supported for backwards compatibility, but the Xft2 library and Cairo allows for reasonably painless updating of applications to support full AA text, even on X servers that do not support the Render extension. + +The last facility of Render, not yet universally deployed, is support for AA trapezoids. Much device driver work remains to optimize the extension and use the facilities provided by modern graphics accelerators. Even so, the current usually software only implementation of Render, is fast enough for most applications. + + +#### Xft2 library + +Xft2 provides a client-side font API for X applications. It uses Fontconfig to select fonts, Freetype 2 for rendering the fonts and the X protocol for drawing them on the screen. When available, Xft uses the Render extension to accelerate text drawing. When Render is not available, Xft uses the core protocol to draw client-side glyphs. This provides completely compatible support of client-side fonts for all X servers, enabling application developers the benefits of anti-aliased, sub-pixel decimated text on all X implementations. This backward compatibility is seldom needed now, but was essential for its success. + +Xft1 is obsolete and should not be used; it did not provide AA text on old X servers, and combined this functionality with what is now Fontconfig, which has been made a separate library usable by all applications, not just X applications. Both Qt and GTK+ in versions since mid 2002 have used Xft2 for their text rendering. + +Xft2 is stable, and now widely available and deployed on open source systems. + + +#### Xinerama + +Xinerama allows multiple screens to be combined into one larger virtual X screen, mostly invisibly to most applications. + +Its major liability is that merging screens of different types force the least common denominator behavior of the capabilities of the screens. In practice, this is not a serious limitation for casual use. The new extensions under active development may allow for a more flexible Xinerama like system without its liabilities to be built. + +Xinerama is widely available and deployed, though not all X drivers are implemented to allow it. + + +#### Xnest and Xephyr + +These is not an X extensions, but an X server running in an window. This can be very useful not only for server debugging, but ensuring that your applications work well on different size X displays, for example the small screens found on PDAs. + +Xnest is widely available and deployed, though some extensions may not be present. Xephyr is more likely to be of use on today's systems and supports modern X extensions such as composite, and we recommend using Xephyr under most circumstances. + + +#### X extensions under active development + +These simple extensions together enable very sophisticated visual effects to be created by window level image compositing, along with other needed facilities such as screen magnifiers, thumbnailers, and integration of applications into 3D immersive environments. + +These are under active development and will change before completion. + +* The X Fixes extension "fixes" some problems in the X core protocol, for application embedding, cursor tracking and naming, and introduces regions as a first class resource type for general use, for example, by the X Damage extension. +* The X Damage Extension allows applications to track modified regions of drawables, useful for compositing or applications such as VNC. +* The Composite extension causes a entire sub-tree of the window hierarchy to be rendered to an off-screen buffer. Applications can then take the contents of that buffer and do whatever they like. The off-screen buffer can be automatically merged into the parent window or merged by external applications. + +#### Obsolete X extensions + +A number of X extensions have been found to be useless or so difficult to use that they never achieved serious use over the last 15 years. These extensions, while possibly present in an X server implementation, should be considered obsolete and deprecated, and cannot be relied upon being present. Some of these include: + +* PEX - the Phigs extension to X. OpenGL won the 3D war; PEX is no longer even built in current X servers. +* XIE - the X Image Extension was an attempt to turn the X server into general purpose image processing. It failed due to excessive complexity and lack of a good implementation. A simple image transport extension may still make sense in the future. The goal of XIE was "image transport and display" with the requirement that it accept arbitrary JPEG images and perform all necessary manipulation (including unsharp masking, color space conversion, gamma correction, affine transformation) in the X server. That slope wasn't just slippery, it was a grease-covered cliff ending in a complete programmable image processing system within the X server. The implementation suffered from being done under contract by the lowest bidder, and being done after the standard was ratified with no feedback loop possible to fix the worst of the problems. Bad spec., Bad process, Bad engineering, Bad standardization process. What's not to hate? +* Multibuffer extension - an early extension providing multi-buffering. Included stereo, which the double buffer extension does not have. Some sort of separate stereo extension has been needed by several projects which have ended up using Multibuffer lacking a better mechanism. On the other hand, double buffer is now almost universally implemented by allocating off-screen pixmaps and using bitblt, so it may be all we need is a stereo extension. +* LBX, while often present in current implementations, is almost always a bad idea to use, and may vanish entirely soon. SSH typically works as well or better while providing the authentication and security that LBX lacks. See "X Window System Network Performance" for more information and discussion. +* XPrint, which has seldom been seen to work, tries to turn the X server into a printing device. This is conceptually a bad idea, as, for exampe, to get document portability, the outlines of gyphs of fonts must be embedded into documents so that they scale properly across the resolution of different printers. + +#### X libraries under active development + +Xlib has been the standard C binding for the X Window System protocol for many years now, and is in need of serious rewrite in some areas. It was written before shared libraries and threading were commonly available on UNIX, and several parts of Xlib should have been implemented as fully independent libraries.Work is essentially complete to engineer replacements for the old implementation and allow for better modularity and size. + +The new basic protocol library is called XCB that has potentially very good performance properties in that it is much easier to use to avoid round trips to the X server, and is carefully written from scratch. + + +#### X toolkits + +In the X architecture, user interface elements used by applications are provided by "toolkits". There have been many X toolkits over the years (and on other systems, such as Microsoft Windows, similarly there are multiple toolkit APIs). The most well known are GTK+, [[TrollTech|TrollTech]]'s Qt, and the older Motif library. GTK+ is used as the basis of the Gnome desktop project, Qt underlies the KDE desktop project, and Motif is used in the CDE desktop commonly found on UNIX systems. New open source development generally uses either Qt or GTK+ for toolkits. Additionally, the Mozilla project has a cross platform toolkit used by its applications, though on Linux and UNIX, this work is based on top of the GTK+ library. + +At this date, the major projects including Gnome and KDE have good facilities for internationalization (I18N) and localization (L10N) of applications, and many languages are already well supported. How comprehensive the localization is will depend upon the desktop and application, and the passion of the translators; complete coverage exists for many languages. Wider and wider localization is occuring, and is a way that motivated people from around the world can make a significant contribution, even for languages not spoken by many people. Even if you are a non-programmer but are a fluent speaker of a language not well covered, you can make a difference, and I encourage your involvement. Modern UNIX and Linux systems provide facilities for shared libraries that allow multiple versions of a toolkit to be installed simultaneously without introducing problems with applications. For example, applications based on GTK+1.x can coexist comfortably with GTK+-2.x based applications. Both GTK+ and Qt allow customizing much of their look and feel via "themes". There are of themes that provide a largely similar look and feel across both toolkits. Themes can be changed while applications are running. Also of note is Winelib, which is a major aid in porting programs written to the Win32 API to X. A notable closed source, free as in beer application using these libraries is Google Earth. + + +#### GTK+ toolkit + +What is typically called GTK+ in common usage is actually a set of three libraries. Glib is a low level library used by GTK+ and Gnome to provide a portability layer and other common functions. Pango provides for very sophisticated internationalized text layout, for a very wide range of languages including Arabic and Indic languages, generally difficult for most applications to do on their own. ATK is an accessibility toolkit. By supporting the ATK interfaces, an application or toolkit can be used with such tools as screen readers, magnifiers, and alternative input devices, and with the related applications and facilities, working toward full U.S. Section 508 accessibility conformance. + +GTK+-2.x is now widely deployed, has Xft and XRandR support, and is actively maintained and developed. GTK+ is written in C, and there are bindings for GTK+ for just about all commonly (and some uncommonly) used programming languages. For more detail and future plans, see the GTK+ web site. All applications in active use have been updated to GTK2 at this date, and it provides a stable, widely deployed base for new applications development. GTK+-2 is not expected to change in incompatible ways. It has language bindings for all common (and some uncommon) programming languages. While GTK+ development is primarily X based on UNIX and Linux on desktops and PDAs (e.g., there has been work to target it at other platforms, including frame buffers and Windows. GTK+ runs on Mac OS X via that platform's support for X, now standard in the lastest version of OS X. + +GTK+-1.x is obsolete, and no longer being developed, having inadequate I18N facilities. + +GTK+ is LGPL licensed. + + +#### Qt toolkit + +The Qt library, actively developed and maintained by Trolltech, has Xft and XRandR support, and is the toolkit used by the KDE desktop project. It is a modern toolkit primarily targeted towards C++ development, although bindings have been developed by the KDE project and others including support for Perl, Python, Ruby, [[JavaScript|JavaScript]], Java, C#, Objective-C, and C. + +A main feature of Qt is its strong cross-platform support (X11, Windows, Mac OS X, Linux frame buffer on PDAs). In addition to user interface APIs, Qt provides APIs for various platform-specific tasks such as file-handling, networking, process-handling, threading, database access, etc. Qt 3.2 also has strong support for internationalization including support for Arabic, Asian, Cyrillic, Greek, Hebrew, Indic, Latin and Persian languages as well as general Unicode support. Qt 3 supports accessibility features on Windows/Mac with the rudiments of support existing for X11. Full accessibility support under X11 will be available in Qt 4. Qt 3 is the current version used on the desktop, although QtE 2 is still widespread in Qtopia PDA applications. + +Qt is available under the GPL and under a variety of licenses under different terms for commercial and non-commercial use. + + +#### Other toolkits + +Other toolkits seeing significant development that may be interesting for particular purposes include FLTK, GNUstep, and wxWindows. Fltk is cross platform and quite small and fast, (hence its name), GNUstep is Objective C based and implements much of the original [[OpenStep|OpenStep]] specifications and may be useful in porting Apple [[MacIntosh|MacIntosh]] applications, and wxWindows is an open source, cross platform C++ GUI framework. On Linux, wxWindows is GTK+ based, and will be able integrate quite well into the current desktop (when its port to GTK+ 2 is complete). + + +#### Moribund X toolkits + + +##### Motif + +Motif (now called [[OpenMotif|OpenMotif]]) is the toolkit used in the CDE desktop found on most UNIX systems, though KDE and Gnome are often also available for those UNIX systems. A clone of it, called Lesstif, was developed while Motif remained fully proprietary. No new open source applications are now being developed by open source developers using Motif, though Motif may be used in corporations. As Motif currently lacks theming support, Motif applications often look out of place on current desktops, but will continue to work into the indefinite future, and is still seen used in some older commercial UNIX and Linux applications. + +I believe that Motif/Lesstif are obsolete, but it is still used extensively in commercial settings, even if relatively little new code is written to it. It is based on a library called Xt, which attempted to define a policy free toolkit framework. In retrospect, this was a mistake. Other toolkits widget sets were built on Xt, including Xaw (the Athena Widgets), Xaw3d, and the like. I don't know if it has been ported to Windows or not (possibly via cygwin), but would still be running under X. + +Lesstif is LGPL licensed. Motif has a unique license, with different terms for commercial and non-commercial use on open source or proprietary platforms. + + +##### TK + +The TK toolkit distributed as part of the cross platform TCL/TK system has some very substantial ongoing applications built with it, particularly some commercial CAD applications (e.g., Magic). It preserved some of the original ideas of Joel Bartlett's ezd's program canvas to have been adopted by other toolkits, including GTK+. I would not currently recommend it for new applications, as TK applications do not integrate very well into today's desktops (e.g., lack of theme support, and modern window manager hint support). Similar scripting language/toolkits that do integrate well are available, for example, in PyGTK (Python bindings to the GTK toolkit), to name one of several recent options. TK's most widely visible application has been the "make xconfig" program used for configuring Linux prior to Linux 2.6, and some git applications. There are some signs that the Tcl/TK community understands that it has fallen behind the times and some steps are underway to rectify the issues, but these plans are not yet far enough along for me to believe TK will extricate itself from the tar. If you value TK, then now would be the time to aid that effort. + + +### Other key libraries + + +#### Fontconfig - font configuration library + +Fontconfig will discover new fonts when installed automatically, removing a common source of configuration problems, perform font name substitution, so that appropriate alternative fonts can be selected if fonts are missing. Fontconfig will identify the set of fonts required to completely cover a set of languages. It will efficiently and quickly find the fonts you need among the set of fonts you have installed, even if you have installed thousands of fonts, while minimizing memory usage. Fontconfig can be used in concert with the X Render Extension and [[FreeType|FreeType]] to implement high quality, anti-aliased and subpixel rendered text on a display. It is believed to be "best in class" of equivalent facilities on other operating systems. Fontconfig does not render the fonts hemselves (this is left to [[FreeType|FreeType]] or other rendering mechanisms) or depend on the X Window System in any fashion, so that printer only applications do not have such dependencies. + +Fontconfig is stable, and available on all current Linux distributions. Note that the obsolete X core font mechanism does not (yet) use fontconfig for its configuration mechanism, which is a source of configuration confusion we hope to see remedied during 2004-2005. + +Fontconfig is MIT licensed. + + +#### Freetype 2 - font rendering + +[[FreeType2|FreeType2]] is a software font engine that is designed to be small, efficient, highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries, display servers, font conversion tools, text image generation tools, and many other products as well. Note that [[FreeType|FreeType]] 2 is a font service and doesn't provide APIs to perform higher-level features, like text layout or graphics processing (e.g., colored text rendering, "hollowing", etc..). However, it greatly simplifies these tasks by providing a simple, easy to use and uniform interface to access the content of font files. Freetype's features list is very long: in short, Freetype supports most types of fonts used to date. Freetype 2 is stable, actively developed and maintained, and available on all current systems. + +Freetype 1 is obsolete and should no longer be used. + +[[FreeType|FreeType]] 2 is released under two open-source licenses: its own BSD-like [[FreeType|FreeType]] License and the GPL. + + +#### Cairo - vector graphics library + +Cairo is a cross platform vector graphics library with cross-device output support. Cairo is designed to produce identical output on all output media while taking advantage of display hardware acceleration when available (e.g., through the X Render Extension or the platform's native interfaces on Windows and Mac OSX). Cairo fills a missing piece of the unification of graphics between the window system and printing system. + +Cairo provides a statefull user-level API with capabilities similar to the PDF 1.4 imaging model. Cairo provides operations including stroking and filling Bezier cubic splines, transforming and compositing translucent images, and antialiased text rendering. It is believed to be second to none in its intended purpose. Currently supported output targets include the X Window System, in-memory image buffers and Postscript, PDF and SVG (structured vector graphics). Similarly as with Xft2, the X back end for Cairo is engineered to be able to draw on X servers that do not support the X Render extension, to enable applications to use its API everywhere. Bindings for many languages are already available, and Cairo is being used for applications. It underlies the GTK+ library, and is used by Firefox 3 on all platforms (Linux, Mac, Windows). Cairo is a free software library available under the MIT license. + + +#### Hardware Abstraction Layer (HAL) + +HAL is the infrastructure that deals with how to enable the good integration of devices into the desktop environment, so that when you plug in a new device, it "just works" in sensible ways for users. Linux 2.6 has extensive support for "hotplug" devices of all forms, not just PCMCIA and USB, and this provides the desktop integration to go with the base operating system support. + + +#### DBUS - message bus system + +D-BUS is a message bus system, a simple way for applications to talk to one another. There are bindings for multiple toolkits (e.g., Qt, GTK+). It is in common use and widespread deployment. + + +#### XML libraries + +XML is increasingly used in free software, not only for document and information markup but other related uses such as configuration files (e.g., fontconfig). Libxml2 is the XML C parser and toolkit; . It and a several other XML libraries (e.g., expat) are commonly used as the basis of XML related applications. LibXML2 is available under the MIT License, stable, very fast, and widely deployed in many applications. + + +#### Pkgconfig + +Not directly part of desktop software, but being increasingly used as part of the build environment of desktop software is the pkgconfig system. + + +#### Zeroconf + +The zeroconf work in the IETF is key to good user experience in network configuration. First to support zeroconf well is Apple Rendesvous on the [[MacIntosh|MacIntosh]]; UNIX and Linux support is well underway and beginning to ship in vendor's Linux distributions. + + +### Multimedia + +Multimedia is still in a great state of flux on open source systems. It is, however, to the point that serious applications exist and work well; the impetus is more around how to better integrate this to improve the user experience. As you will see, there is much available, and the community and users will decide which are of greatest importance, and it is probably the area of greatest ferment in desktop development. + + +#### Multimedia frameworks + + +##### Helix community + +[[RealNetworks|RealNetworks]] has made their Helix community multimedia framework that underlies their product suite and under multiple licenses, depending upon commercial or non-commercial use. Not all codecs are available open source. + + +##### aRts + +ARts is the multimedia framework used by the KDE project, is stable and is maintained by the KDE project, but has not seen much recent development. + + +##### Gstreamer + +The multimedia framework used by the Gnome project is Gstreamer. It is still working toward its first 1.0 release, but is in use in some applications. + +It is LGPL licensed. + + +##### Mplayer + +Mplayer is a movie player for LINUX and runs on many other UNIXs, and non-x86 CPUs and is being ported to Windows. It has support for a very wide variety of codecs and output devices. Multiple user interfaces have been built using Mplayer. + +It is now very stable and very capable and at its 1.0 stable release. + +Mplayer is available under the GPL. + + +##### VideoLAN + +The VideoLAN project targets multimedia streaming of MPEG-1, MPEG-2, MPEG-4 and DivX files, DVDs, digital satellite channels, digital terrestial television channels and live videos on a high-bandwidth IPv4 or IPv6 network in unicast or multicast under many OSes. VideoLAN also features a cross-plaform multimedia player, VLC, which can be used to read the stream from the network or display video read locally on the computer under all GNU/Linux flavours, all BSD flavours, Windows, Mac OS X, BeOS, Solaris, QNX, Familiar Linux... + +It is available under the GPL. + + +##### Xine and Xinelib + +Xinelib is the library underlying the Xine multimedia player. It has been so successful that many user interfaces have been built on top, and has support for a huge variety of audio and video codecs natively and provisions for use of binary commercial codecs from Windows on x86 platforms. It is very stable and very capable, and runs on Linux and most UNIX platforms and is being ported to other platforms as well. + +Xine is available under the GPL. + + +##### Totem + + +#### Audio + +Audio in open source systems is in a funny state. Amazing tools, applications, and codecs have been and continue to be developed, primarily on Linux systems, and you will find substantial parts of the computer music and audio research community using Linux. On the other hand, the tools and applications aren't all well plugged together for casual desktop use. So the good news is you'll probably find more software than you can make heads or tails of, and the bad news is you'll have to fuss with it to get it running, and may have problems when different applications need to be used simultaneously. This is not a good situation, and needs serious improvement. + +One issue for some audio applications has been latency, and particularly variance of latency. Low latency and good synchronization facilties are required by both professional audio work but even more for telephony and teleconferencing applications. Much work has gone on over the last several years to work on the Linux scheduler and get a good upper bound on latency in the system, in support of audio and other real time applications. Latency in Linux 2.4 is greatly improved over previous Linux releases, and is now quite good, and Linux 2.6 is outstanding. + +Linux has transitioned from the old OSS interface to the new, much improved ALSA driver infrastructure and implementation. + + +##### Advance Linux Sound Architecture (ALSA) + +The Advanced Linux Sound Architecture (ALSA), provides audio and MIDI functionality to the Linux operating system. It boasts: efficient support for all types of audio interfaces, from consumer soundcards to professional multichannel audio interfaces, fully modularized sound drivers, SMP and thread-safe design, user space library (alsa-lib) to simplify application programming and provide higher level functionality, support for the older OSS API, providing binary compatibility for most OSS programs. This has put the Linux audio driver interface on a very firm footing. + + +##### Audio servers + +But X is a network transparent window system, and, particularly in LTSP environments, applications need network transparent access to audio services. As yet, open source systems have not settled on a standard sound server, which with luck will happen over 2004; several earlier sound servers such as AF or NAS are no longer widely used. The AF audio server was notable in that it shows that it is possible to design network transparent audio servers with no inherent latency and with tight synchronization facilities. As AF lacked sample rate conversion (machines weren't fast enough in 1992), it is inadequate on that and other grounds for today's use. + + +##### aRtsd + +The aRts sound daemon used and maintained by the KDE project. It is also stable and not undergoing further development. + + +##### Enlightened Sound Daemon (ESD) + +ESD is widely available, maintained as part of the Gnome project, and is stable but is not undergoing further development. While adequate for routine use, it is very insufficient for advanced applications or those with demanding latency or synchronization requirements (e.g., video playback). + + +##### Jack + +JACK, the Jack Audio Connection Kit, provides low latency, high efficiency inter-process audio connectivity, as well as audio device sharing, suitable for pro-audio applications. While an audio server, it is not a network transparent server at this date, and therefore unsuitable for LTSP or other distributed X deployments. On single systems it has much to offer. + +It is under active development, not yet API stable (though may become so during 2004), and available under the GPL (server) and LGPL licenses (libraries). + + +##### Media Application Server (MAS) + +MAS, by Shiman and Associates, is a very ambitious audio server and multimedia framework. If it can be made to meet the needed latency (required by telephony and teleconference applications) and synchronization requirements (of video playback), it may be a viable contender to replace the current relatively poor audio servers. + +MAS is under active development and evaluation. + +The core of the MAS system recently became available under the MIT license. + + +#### Microsoft interoperability + + +##### SAMBA + +Samba enables UNIX and Linux systems to provide high performance file and print services to Microsoft Windows clients, and to gateway these services to open source desktops (via CUPS). + + +##### File systems + +Linux is able to read and write FAT file systems of all types, and read NTFS file systems. Read/write of NTFS file systems is in an experimental stage. + +Linux systems can mount Microsoft SMB file shares and read and write them. The desktop file browsers for Gnome and KDE have improving support for enabling browsing of a Microsoft file share network and browsing of file shares. + +Further polish of this work can be expected during 2004. + + +##### File formats + +The Microsoft file formats are a challenge, but open source programmers appear to be up to the challenge. The latest version of [[StarOffice/OpenOffice|StarOffice/OpenOffice]] can import and export Microsoft office file formats (along with many others) most of the time with great success. Generally, open source applications are moving toward XML based representations of documents, such as that used by [[OpenOffice|OpenOffice]]. + +For perfect interoperability, many releases of Microsoft Office are now running very successfully using the Wine technology. + +There will be continued incremental improvements; of course, since Microsoft is a moving target this will continue to challenge the community. + + +##### WINE + +Wine provides a Microsoft Windows execution environment on Linux and x86 based UNIX. Many key "shrink wrap" applications written for Microsoft Windows including Microsoft Office, Lotus Notes, Adobe Photoshop, Intuit Quicken can run on x86 based Linux systems using Wine. Commercial versions of Wine that provide support and easy installation and configuration are available from Codeweavers for commercial applications and Transgaming for games. The applications in general are well integrated into the open source desktop, though in this environment, certain Windows peculiarities (e.g., MSDOS drive letters and file name paths) show through. + +Your exact mileage will vary, but many of these applications (e.g., Microsoft Office) now run extremely well and stably. More and more applications will become usable with time. + +Wine is distributed under the LGPL license. + + +##### Winelib + +Winelib provides Microsoft Windows compatible APIs as an aid to porting applications, and is the underpinnings of the Wine execution environment. As such, it can be viewed as yet another toolkit. Applications for which source is available may be able to be recompiled and relinked against Winelib as a way of porting the application to become a native application on UNIX and Linux systems. + +While tracking the evolution of Microsoft APIs is a perpetual, thankless task, a higher and higher fraction of applications will find that Winelib covers their needs with time. The fact that many major Microsoft Windows applications run well under Wine shows that the coverage is actually quite good over the APIs actually used by Windows applications. + +As a porting tool of applications built to Win32 APIs, it can't be beat. + +Winelib is distributed under the LGPL license. + + +##### DOS emulation + +An easy, portable way to run old Microsoft DOS software is to use Dosbox It emulates enough of DOS to be able to run most of scripts and can automatically mount a directory as it were a DOS drive. The current 0.60 version can run (e.g., most of the older DOS games); just extract program to a directory and use 'dosbox <directory>'. + +The harder, x86 and Linux specific way is to use Dosemu and install a real MS-DOS on a disk image. Dosemu is faster than Dosbox. (The Dosemu page claims that MS-DOS is not needed, but in practice [[FreeDos|FreeDos]] is not compatible enough.) + + +##### .Net and Mono + +The Mono project is an effort to create an open source implementation of the .NET Development Framework, some of which involve desktop technologies. + +Mono includes: a compiler for the C# language, a runtime for the Common Language Infrastructure (also referred as the CLR) and a set of class libraries. The runtime can be embedded into your application. It implements of both ADO.NET and ASP.NET. It is adopting Cairo for its 2D graphics. + +Mono's licenses are GPL for tools and LGPL for Mono libraries. + +Mono's expected 1.0 release is Q2 2004, according to its road map. + + +#### Displaying Windows applications on Open Source systems + +There are both commercial and open source RDP cients for Linux available, that enable remote Windows applications usiing Windows Terminal Server to be displayed on open source desktops. + + +#### X implementations for Windows + +There are X Window System implementations for Windows. X applications can run on Windows and use X servers on any operating system (UNIX, Linux, Mac OS X, etc.) for their display, and if an X server is running on Windows, X applications on UNIX, LInux, MacOS X can be used on those Windows machines. Tools like Cygwin are make it very easy to develop cross platform tools that can be used on both Windows and UNIX/Linux/MacOSX. + +There are both commercial and non-commercial X implementations for Windows. + + +##### Cygwin and Cygwin/X + +Cygwin is a Linux-like environment for Windows, allowing for use of much Linux software on Windows. It consists of two parts: 1) A DLL (cygwin1.dll) which acts as a Linux emulation layer providing substantial Linux API functionality, 2) A collection of tools, which provide Linux look and feel. A large collection packages of software available. + +The Cygwin DLL works with all non-beta, non "release candidate", ix86 versions of Windows since Windows 95, with the exception of Windows CE. + +Cygwin is actively maintained and developed, and has been making regular releases,. Various packages are, of course under their own license terms. + + +##### Cygwin/X + +Cygwin/X is a port of the X Window System to the Microsoft Windows family of operating systems. Cygwin/X runs on all recent consumer and business versions of Windows; as of 2002-05-12 those versions are specifically Windows 95, Windows 98, Windows Me, Windows NT 4.0, Windows 2000, and Windows XP. + +Cygwin/X consists of an X Server, Xlib, and nearly all of the standard X clients, such as xterm, xhost, xdpyinfo, xclock, and xeyes. Cygwin/X, as the name implies, uses the Cygwin project which provides a UNIX-like API to Xlib and X clients, thereby minimizing the amount of porting required. + +Cygwin/X is licensed under an X style license; Cygwin is licensed under a modified GNU General Public License that specifically allows libcygwin1.a to be linked to programs that are licensed under an Open Source compliant license without such linking requiring that those Open Source programs be licensed under the GNU General Public License (see the Cygwin licensing page for more information). Source code and binaries for both projects are freely available. + +Cygwin/X is actively maintained, developed and enhanced and has been making regular releases. + + +##### Commercial X implementations + +There are a number of commercial X Window System implementations for Windows, for example, Hummingbird's Exceed. + + +#### Fonts + +Freetype 2, Fontconfig, and client side fonts have taken open source desktops from worst in class to best in class in basic font and internationalization at the core technology level, and at the toolkit level, GTK+'s Pango and recent work in Qt have finally brought X desktops from the 1980s to the modern world, with good Internationalization support, and first class linguistic layout and font rendering. + +Essentially any [[TrueType|TrueType]] or [[OpenType|OpenType]] fonts are usable. Additionally, the Postscript 35 Type1 fonts are now also available universally, courtesy a donation from URW four years ago. + +A further issue issue that most people are not familiar with is that of "metric compatibility". Unless fonts with very similar metrics are available, documents will not lay out identically across platforms. So without compatible fonts, typical documents in Microsoft format will not appear the same on open source platforms. This is a serious inhibitor to complete interoperability with Microsoft. + +The Microsoft Web fonts are available on the Internet, but their license does not permit bundling for commercial sale, which means that users have to find and install them. This has meant that when open source systems are first turned on, and until and unless the users understand how to locate and install them or other fonts, we have had a major "out of the box" problem. + +Bitstream's wonderful donation in April 2003 of the Vera font family for open source use has helped greatly in making open source systems presentable "out of the box". But the international coverage of these fonts is insufficient for the global nature of open source, and the fonts are not metric compatible with Microsoft fonts. + +So, while the open source community has spawned decent graphics artists and GUI designers, to date we have failed to establish a serious culture of font design and hinting of fonts, so fonts, particularly high quality hinted fonts for screen use, remain in short supply that can be "preinstalled" so that things "just work" in routine use. The projects building fonts seem to be are pretty fragmented and uncoordinated at the moment. Tools are available for font design and editing on Linux (and commercial tools are available on other platforms), but hinting of fonts for screen use is just slow, painful, repetitive work. Work by John Hobby a decade ago shows it may be possible to do good automatic hinting of fonts now that systems are so fast, but implementations of those algorithms are not currently available (another potential project for mathematically inclined open source programmers). Fonts require ongoing maintenance and enhancement, as language coverage and/or entirely new characters need to be added to fonts. In principle, this effort should be a lot of fun for the right person/people, involving as it does so many languages and cultures over the world. Further donations of fonts and/or funding for further font development would be greatly appreciated along with someone with the passion and ability to lead such efforts. + +Availability of high quality fonts, particularly for screen use, is therefore a significant issue. A second issue has been that Apple asserts two patents on how certain hints are implemented in [[TrueType|TrueType]]; these patents are only valid in the U.S. and Great Britian. + +As a result, commercial Linux or application distributions for desktop use now often bundle other high quality proprietary fonts with them as well, so this is less an inhibitor than one might first expect. But as this means that applications have not been able to rely on the availability of a metric compatible set of fonts, we may end up paying multiple times for the same fonts (from both application and base Linux system vendors). Better would be for the commercial open source vendor community to pool their efforts and "buy out" a set of such fonts. + + +#### Printing + +Printing has been a difficult problem on UNIX and Linux systems, but a number of changes during 2002 and 2003 are turning this from poor to quite usable. It is a very large topic, requires a document of this size to sketch, so this is just a 20,000 foot overview. Much additional information about printing on open source systems can be found on the Linux Printing web site. Open source printer drivers for almost all HP and Epson printers are available, with more spotty coverage for other vendors, and commercial support and more drivers available and tools from Easy Software Products, CUP's creator. + +UNIX/Linux printing in the past been badly hobbled by the lack of a good spooling system, which is now on its way to solution with the increasing deployment of CUPS and other developments. Berkeley lpr/lpd was really lame, System V lp similarly lame. Lprng was an improvement, but at this date, all Linux distributions, at least, are using CUPS as their default spooling system + +Desktop applications were badly hobbled by the original X Window System font design (for which I am partially to blame), which denied easy access to font files needed by applications which did anything sophisticated with text. Keith Packard's font related work has been outstanding, and the Fontconfig/Xft2/Freetype/Render combination takes us from poorest to best in class, both in quality of rendering and in internationalization on the screen, but some more work is needed in applications for printing to catch up. The widespread deployment of client side fonts using Fontconfig, Xft2, Freetype the X Render extension during 2003 marks a sea change in enabling good desktop display and printer integration. Additional work to complete integration of printer selection and management of small to moderate CUPS installations into the desktop environments is well underway. KDE's support has been complete for a while and Gnome projects and will be substantially complete in 2003, with [[StarOffice|StarOffice]] and Mozilla the remaining major application suites needing update. + +The expected uptake of Cairo in these projects during 2004 should significantly improve the generation of high quality 2D graphics for screen and printing, and allow for embedding of font information into print files that has been lacking (with the notable exception of [[StarOffice/OpenOffice|StarOffice/OpenOffice]], which has internal PDF generation already). + + +##### Postscript and PDF + +The fundamental "Lingua Franca" of printing on open source and UNIX systems has always been postscript, and there are open source and closed source PDF utilities. + + +##### Common Unix Printing System (CUPS) - print spooling system + +CUPS is now "standard" on all major currently shipping Linux distributions, Mac OS X, and available for all UNIX systems. It provides an IETF IPP (Internet Printing Protocol) print spooling system with provisions for fail-over, printing of many MIME types (though PDF and Postscript are by far the most common). Microsoft Windows XP has IPP support, but as it involves running IIS currently not typically used. CUPS makes all printers postscript capable that are not already Postscript capable, by using either Aladdin or the free versions of ghostscript, as a "Raster Image Processor". + +CUPS uses industry standard PPD files for printer descriptions, for all printers, not just Postscript printers, providing a uniform printer capabilities mechanism. CUPS provides for dynamic discovery of printers, and fail-over between printers. + +One of CUPS's other major strengths is that it has back ends for Microsoft SMB printers via SAMBA, Berkeley LPD protocols, [[JetDirect|JetDirect]] from HP, and so on, providing a fully uniform access method for applications to use for printing. Additionally SAMBA can be configured so that CUPS printers are available to Microsoft Windows desktop users. + +CUPS will continue to spread rapidly into the remaining environments. More work is needed in the management of CUPS environments, but the basic needs are now met in the latest versions of KDE and Gnome applications and those provided by Linux distributions. Commercial large enterprise management software is available from Easy Software. Integration of CUPS into desktop applications is well underway, and should be substantially complete by the end of 2003, and entirely complete by mid 2004. + +CUPS is GPL (the CUPS server itself) and LGPL licensed (the CUPS libraries). + + +#### Thin clients + +The X Window System, arguably, invented thin client computing. In their heyday, there were a significant number of hardware companies offering what were called "X Terminals" (e.g., NCD). Most/all of these are defunct, as they became less economic than commodity PC hardware, but the concept still has serious validity to reduce system management costs. Some thin client hardware for sale today can be used with X and X based applications as well, particularly since they make machines interchangable, have lower CPU and memory requirements, and can easily eliminate the disk and fans of conventional desktop machines at a somewhat lower price point. The combination can result in a much lower TCO, particularly using Linux, since Microsoft's pricing of its software licenses actively discriminates against this computing model. Also note the availability of RDP clients for open source systems as mentioned above, which allow Windows applications to display on X desktops via Windows Terminal Server. + + +##### Linux Terminal Server Project (LTSP) + +The Linux Terminal Server Project is building "thin client" versions of Linux. Most applications are run remotely on servers (via X's network transparency), but there are also provisions for locally run clients. This provides much better manageability of desktops and is very cost effective in many environments, making machines truly interchangable and obviating the need for "sneaker-net" system management. One view is that this is a reinvention of X terminals, but as there is provision for local clients it goes beyond that, and can take advantage of commodity PC hardware, thin client hardware, and old systems you thought were just junk. The K12LTSP makes a version specifically targeted toward use in schools. + +LTSP is in widespread use, has been through four major releases, and has an active developer and user community, and supports multiple Linux distributions. + + +##### Athena Computing Environment + +A similar style of not-quite-so thin computing is typified by the Athena computing environment at MIT (where both the X Window System and Kerberos have their roots). In this model, machines are also interchangable, but rely on distributed file systems and good authentication to keep any permanent data off the local machine. Local disks are used as caches for files and for swap, but never for long term data storage. As an integrated whole, this is not seen much outside of MIT, though X11 and Kerberos are reasonably widespread. As a interesting historical note, Athena's "Zephyr" system was arguably the first instant message system. + + +#### Java + +Java is available from Sun for Linux, and there are several static Java compilers (e.g., GCJ, part of the GCC compiler suite and Jikes from IBM), and may be preinstalled. The Blackdown project provides community source distributions of Sun's Java for additional platforms that Sun may not. Java release 1.4.2 introduces Swing support based on GTK2 look and feel, which aids in the natural integration of GUI applications built with Java on the open source desktop. As this deploys widely over 2004, Java applications using Sun's VM will share the look and feel of Gnome desktops. + + +#### VNC + +VNC stands for Virtual Network Computing. It is remote control software which allows you to view and interact with one computer (the "server") using a simple program (the "viewer") on another computer anywhere on the Internet. The two computers don't even have to be the same type, so for example you can use VNC to view an office Linux machine on your Windows PC at home. VNC is freely and publicly available and is in widespread active use by millions throughout industry, academia and privately. Note that VNC can be trivially replaced with a simple X application along with "ssh -X -C" in concert with the Damage extension. diff --git a/Development/Documentation/Obsolescence/roadmap-2-clean.pdf b/Development/Documentation/Obsolescence/roadmap-2-clean.pdf Binary files differnew file mode 100644 index 00000000..14b34db3 --- /dev/null +++ b/Development/Documentation/Obsolescence/roadmap-2-clean.pdf diff --git a/Development/Documentation/Performance.mdwn b/Development/Documentation/Performance.mdwn new file mode 100644 index 00000000..e4c2e23c --- /dev/null +++ b/Development/Documentation/Performance.mdwn @@ -0,0 +1,125 @@ + +[[!toc ]] + +X performance is extremely difficult to quantify, and there is a large amount of work to be done in this space. The following are some collected notes on what needs doing. + +Discussion and questions about work in these areas should be held on the [[xorg mailing list|http://lists.freedesktop.org/mailman/listinfo/xorg]]. + + +## Transport Performance + + +### In General + +X is a fairly compact protocol, with the exclusion of image transport which is done uncompressed. The dominating factor in many aspects of X performance is transport latency - how long it takes for a response to make a round trip. This is exacerbated by the design of Xlib, which is effectively synchronous for most of its operation. + +[[XCB|http://xcb.freedesktop.org/]] is an effort to rearchitect the network layer of X to hide latency by providing an asynchronous interface to the protocol. The effort is stabilising rapidly, and needs both wider testing and for toolkits to be ported to it. + + +### Over the Network + +While [[XCB|http://xcb.freedesktop.org/wiki/xcb]] addresses the latency requirements of X, there is no great solution to the bandwidth requirements. Several good (and not so good) solutions do exist. + +* The [[SSH|http://www.openssh.com]] suite allows for tunnelling X sessions over a secure channel, which can also be compressed. This is adequate for technical users, but it is suboptimal for terminal servers and novice users. +* The [[LBX|http://keithp.com/~keithp/talks/lbxpost/index.html]] protocol is generally inadequate for modern X usage. See the linked paper for details. LBX is no longer built by default in 7.1. +* [[Xpra|http://xpra.org/]] acts as compositing window manager to forward individual windows from a virtual server to the client that connects to it (over sockets, tcp or ssh). +* [[NX|http://www.nomachine.com/]] is a software compression suite based on the earlier [[DXPC|http://www.vigor.nu/dxpc/]] protocol. It also leverages ssh to provide security services. There are open issues regarding integrating it into the base suite - licensing being among them, as much of NX is LGPL, version 4 is now closed-source. + +### On the Local Machine + +Several commercial X servers use shared memory transports on the local machine to improve performance. Rik Faith [[researched shared memory transports|http://dri.freedesktop.org/wiki/SharedMemoryTransport]] for the DRI project several years ago. The conclusion then was that it would improve performance for those operations where the time to render the request was dominated by the transport latency, and then by less than 10%. + +This may not be true anymore. The balance of the typical machine's memory architecture has shifted, and many operating systems provide advanced high performance synchronization primitives (like futexes on Linux) that may address some of the sync overhead he experienced. This would be an excellent research project. + + +## Driver Performance + + +### 2D Rendering + + +#### The Important Bits + +Most of the core X protocol's rendering routines simply do not get used very often. This is not so much because they are slow, but because they aren't useful on the modern desktop. Empirically, better than 90% of the drawing operations that X sees today are solid fills, blits, and Render operations. Attempting to accelerate 2D operation outside this set is very likely a waste of effort. + + +#### XAA + +XAA is largely inadequate for accelerating modern desktop usage. + +* XAA goes to great lengths to accelerate operations like patterned fills and Bresenham lines, which are rarely used. +* XAA's support for accelerating the Render extension is poor, because the design of XAA's memory manager only allows for offscreen pixmaps that are exactly the format of the displayed screen. +* Render acceleration in XAA only works when the source image is in host memory and the destination is in card memory; to be truly performant it needs to be able to handle the case where both source and destination are in card memory. This is the reason xcompmgr is slow; it uses Render heavily, and XAA simply can not make Render go fast. + +#### EXA/UXA + +XAA is really not worth fixing. The better approach is to start from the lessons learned from [[KAA|http://www.anholt.net/papers/kdrive-2004/]], the kdrive acceleration architecture, and port drivers over to that (leaving XAA in place for old or unmaintained drivers). + +As of about Xorg 6.8.99.14, there is a new acceleration architecture called EXA that achieves this. EXA is derived from the KAA code, but has been ported to the loadable server design and includes some additional features for improved performance. UXA is a variation on the EXA theme that assumes a unified memory architecture and kernel memory management support. + +The [[ExaStatus|ExaStatus]] page contains the current driver support status. + +EXA continues to be tuned for performance. In particular, the pixmap scoring and migration algorithm is still fairly naive. The lessons learned from tuning EXA will apply to Xgl servers as well in the future. + + +#### Framebuffer Layout + +Most modern graphics cards can be run in either linear or tiled framebuffer modes. Linear modes are simple, you start in the top-left corner and move to the bottom-right, all the way across a single row before changing rows. In tiled modes the framebuffer is broken up into a series of small tiles, usually 8x8 or so, and memory is laid out such that the first 64 pixels belong to the first tile, then the next 64 to the second tile, etc. You can think of linear framebuffer being a tiled framebuffer where each tile is 1x1. + +Tiled framebuffers have a performance benefit because they better model the layout of objects on the screen. They give better locality of reference because each tile is packed tightly in memory, where in a linear framebuffer you might have to skip a thousand pixels ahead to get to the same horizontal offset one line down. Since your spatial locality is better with a tiled framebuffer, your working set fits in your cache better. + +Despite this, X's framebuffer cores use linear modes, even if the framebuffer appears to be tiled from the GPU's perspective. There may be a performance benefit to making the system framebuffer shadow match the GPU's tile layout. The wfb software renderer is designed to allow this, but no (open) driver is seriously using it at the moment. + + +#### Framebuffer Access + +In general, framebuffer reads absolutely kill performance. Any XAA replacement should do as much work as possible in the write direction only. For the cases where framebuffer reads are unavoidable, the new acceleration architecture should make it possible to use DMA to transfer data out of the framebuffer. EXA has hooks for DMA support. + +Even when DMA is unavailable, it is usually more performant to tranfer large blocks of data in and out of framebuffer memory rather than operating on single pixels at a time. + +Thrashing can occur when mixing operations that the hardware can accelerate with ops it can't. It remains an open question as to how to best deal with this. EXA/UXA take the attitude that the card can accelerate pretty much anything you throw at it, which seems pretty reasonable. + + +#### Algorithmic Issues + +EXA's Render acceleration is adequate, but lacks support for a few things. Source-only pictures (solids and gradients) are currently not accelerated in hardware. Source IN Mask OP Dest combination could be implemented in multiple passes for cards that only have one texture image unit. External alpha is basically unaccelerated. + +Trapezoid rasterisation in Render is not hardware accelerated. It's not even clear that it can be. The software implementation has been reasonably well tuned, but could certainly be better. + + +### 3D Rendering + + +#### DRI Drivers + +TODO: Fill me in. + + +#### Mesa Core + +The observation about tiling for 2D also applies to Mesa's software rasteriser. + + +## Interactive Performance + +Because the X server is single-threaded, any operation in the server that takes a significant amount of time to complete will make the server feel laggy. This is common for the Mesa software renderer and the software Render code, but any part of the server could trigger this in theory. While we should work to maintain fast execution of all code paths, there may be significant benefit to reworking the server to be multithreaded. + +One of the worst performance issues X has is making opaque resizes fast. Since the window manager is in a separate process from the application, there are two round trip cycles involved, which makes the latency issues described above worse. There are several possibilities for working around this. One is to move responsibility for window decorations into the client. Another would be to load some portion of the window manager in-process with the X server. + + +## Perceptual Performance + +Most X drivers do not synchronize their drawing to the vertical retrace signal from the monitor. (To be fair, very few windowing systems do this consistently, even MacOS X.) This leads to a tearing appearance on some drawing operations, which looks slow. If the vertical retrace signal could be exposed through the SYNC extension, applications could defer their rendering slightly and reduce or eliminate tearing. This requires extending each driver to support this, as well as adding a little support code to the server itself. + +The un-Composited model of X operation requires many round trip operations to redraw areas when they are exposed (window move, etc.). It is important that X be able to make Composited operation fast in the future. + + +## Platform and Operating System Support + +On x86 hardware, MTRRs are used to specify the memory access policy for ranges of memory. Setting the framebuffer to write-combining has a significant performance benefit. However, on PCIE systems, there are more memory ranges than MTRRs. PAT stands for Page Attribute Table, which allows you to specify the access policy for individual pages at a time. + +Other platforms may have similar memory access mechanisms. + +As mentioned above, OS-specific synchronization primitives could have significant performance benefit for shared memory transports. These include futexes on Linux and possibly doors on Solaris. + +High performance graphics increasingly requires some kernel support for synchronization and security reasons. The DRM provides this support for Linux and BSD systems, but it could reasonably be ported to other suitable platforms like Darwin and Solaris. diff --git a/Development/Documentation/PointerAcceleration.mdwn b/Development/Documentation/PointerAcceleration.mdwn new file mode 100644 index 00000000..7e5df56b --- /dev/null +++ b/Development/Documentation/PointerAcceleration.mdwn @@ -0,0 +1,488 @@ + +**Index** [[!toc 3]] + + +## Introduction + +The predictable pointer acceleration code is an effort to remove the deficiencies of the previous acceleration code. It is intended as a drop-in replacement. Most users probably won't note it, which is ensured by reusing existing controls and aligning closely to them. + +It provides nice features like downscaling (constant deceleration) independent of the device driver, adaptive deceleration, different acceleration profiles, and more. + +However, the main difference is _predictability_. See [[Postulate|Development/Documentation/PointerAcceleration]] for an explanation. + +The behaviour of the code can be configured on a per-device basis in xorg.conf, HAL fdi's or at runtime. A user may also choose to use the previous method or no pointer acceleration at all. + +It also features an optional interface to device drivers to coordinate on acceleration, should one provide its own. + +See [[here|Development/Documentation/PointerAccelerationAsOf16]] for notes regarding Server 1.6 + +<a name="Postulate"></a> +### Postulate + +When the pointer gets accelerated with respect to device motion, it becomes important for the user to be able to predict the acceleration. Without this, the user is unable to intuitively use his device. + +Predictability depends on knowledge. The primary information the user's brain has to build its knowledge about the applied translation from hand (device) to eye (screen) is the velocity of motion. In order to not disturb this feedback loop, it is anticipated that the most critical part is doing a sophisticated estimate for the velocity of the device in the users hand. + +Based on a good estimate, acceleration profiles can be easily learned by the brain and thus be predicted. Because this is an intuitive process, easing it just 'feels better'. + + +### Intent + +Focus was given to the following aspects: + +* improving heavy-load behaviour (no overshooting pointer) +* enabling accuracy and fluid motion with a wide range of pointing devices +* providing a better 'feel' for pointing devices +* similarity in behaviour to the previous code +* don't introduce any lag in the process + +### Basic concepts + +The code serves 3 complementary functions: + +1. provide a sophisticated ballistic velocity estimate to improve the relation between velocity (of the device) and acceleration + +2. make arbitrary acceleration profiles possible + +3. decelerate by two means (constant and adaptive) if enabled + +Important concepts are: + +* **Scheme** + * which defines the basic algorithm. It can be summarized as 'means of translating relative device valuators in-place'. 'Predictable' refers to the new method (discussed here), 'lightweight' to the old one, and there's 'none'. +* **Profile** + * which returns an acceleration _factor_ (not to be confused with the acceleration _control_) for a given velocity estimate. Users are expected to choose the one they can work best with. +The point of profiles is in the following issue: There is a single 'profile' that is the easiest for all users to learn: _unaccelerated_. + +However this isn't too helpful; many people prefer an accelerated pointer. X has traditionally had acceleration activated by default, presumably for this reason. Since there is no single 'best' accelerated profile, this is a very individual option. + +Therefore, having a variety of profiles is essential. 5 of them are currently implemented (one can't really count 'classic' or 'device-dependent' since they are not profiles themselves). + +The 'classic' profile (default) is intended to perform old-style function selection (threshold =/!= 0) so most users won't note a difference. There is a special 'device dependent' profile (Nr. 1) reserved should drivers want to specify one. See [[here|Development/Documentation/PointerAcceleration]] for a short overview. + + +### Problems of the previous method + +The previous method ('lightweight scheme') did not have a velocity concept. It is based directly on the motion report's values ('mickey'), which at best correlates to velocity. Since the brain knows about velocity, not mickeys, this is disturbing. + +For polynomial acceleration: On slow movements, this code infers 3 'velocities': 1, 1.41, and 2. As 1 remains unaccelerated (or is even slowed down), we're left with just two acceleration levels. It is hard to foresee what exactly will happen. + +Worse when using the simple accelerated/unaccelerated function: Acceleration either comes to effect or it doesn't, providing no predictability around the threshold. The higher acceleration, the less predictability you get. + +If a system is under load, a device (or the driver/kernel) may accumulate its movement delta while the system does not query the device. This invalidates the assumed mickey-velocity relationship, causing irrational high cursor movement subsequently. This is particularly annoying when caused by focus changes during a mouse stroke (modern toolkits luckily don't exhibit this behaviour anymore). + +Some people own very responsive devices, creating a need to reduce speed on precise tasks or even in general. This often required driver-side or hardware support which was missing. + +With the simple acceleration scheme, acceleration is more sensitive on diagonal movements than on axis-aligned ones. + +These problems result in a reduced ability for our intuition to predict a matching hand movement for desired screen movement, thus causing more correctional moves than necessary. Put simply, the mouse 'feels bad'. + + +### Benefits of the new code + +Mostly, the polynomial acceleration becomes more usable. It can be used with higher acceleration coefficients (acc > 2), still providing enough control. But also the classic acceleration should become less jumpy since it now ascends softly towards accelerated motion. + +Users with too precise (or fast) devices can slow them without losing precision, independent of hardware driver support. Also, an acceleration function may decelerate on slow movements, giving (sub)pixel precision without sacrificing on pointer speed. + +The code is more robust towards different devices: One could imagine a mouse reporting very often, but only 1 dot per event. Old code would not accelerate such a device at all. While this is a theoretical case, there is robustness against jitter in device event frequency (as could be caused by system load, for example). In general, the number of problematic devices (wrt acceleration) is expected to shrink significantly. + +A driver which wants to roll its own acceleration now can do so without risk of distributing stale data along the event chain. See 'Driver side' below. + +Users disliking all this can switch it off. + + +### Basic useage + +Type e.g. + + +[[!format txt """ +xset m 18/10 0 +"""]] +to set a moderate polynomial acceleration (threshold = 0, acceleration = 1.8). The **xinput** tool has equivalent functionality to _xset m_: + + +[[!format txt """ +xinput set-ptr-feedback <device> 0 18 10 +"""]] +would be the equvalent to the xset example. This works without the patch too, but the previous acceleration scheme is not very nice. + +More features are available via device properties or config files. + + +## Configuration + +The defaults should suffice if you had no problems before, and feel quite similar. The settings discussed here are the coarse and the very subtle settings, not the usual xset or GUI panel controls you might know. + +Because this is a drop-in enhancement, the usual threshold and acceleration controls work as expected and are not planned to be replaced. However, different profiles might react different to them. + +The settings described below are all device-specific. You may set them in an appropriate HAL file (typically /etc/hal/fdi/policy/10-x11-input.fdi) using +[[!format txt """ +<match key="info.capabilities" contains="input.mouse"> + <merge key="input.x11_options.AdaptiveDeceleration" type="string">2</merge> +</match> +"""]] +or similar. Type 'string' is required, since the server won't accept others. + +If you still use a xorg.conf, add options in the approriate "[[InputDevice|InputDevice]]" section in xorg.conf. Usually it looks like: +[[!format txt """ +Section "InputDevice" + Identifier "Mouse0" + Driver "mouse" + [...] +EndSection +"""]] +For example to enable the adaptive deceleration feature, put in a line reading +[[!format txt """ + Option "AdaptiveDeceleration" "2" +"""]] +or similar. + +Some options are runtime-adjustable. The _xinput_ tool can change them: +[[!format txt """ +xinput set-prop "My Mouse" "Device Accel Profile" 2 +"""]] +activates profile 2 on a device named "My Mouse". xinput is quite self-explanatory; however device properties have different names than options, and not all options are available as device properties. This is available in the X.org server 1.7 and higher. + + +### Scenarios + +If _your mouse moves far too fast_, [[ConstantDeceleration|ConstantDeceleration]] is your friend. Set to 2 or higher to divide speed accordingly. This will not discard precision (at least only on nv-reset, see Velocity approximation or below). + +If your _high-performance device does not repond well to acceleration_, you might need to reduce [[velocity scaling|Development/Documentation/PointerAcceleration]] first. + +If you like the speed but need some _more control at pixel-level_, you should set [[AdaptiveDeceleration|AdaptiveDeceleration]] to 2 or more. This allows to decelerate slow movements down to the given factor. You might want to keep nv-resets away by setting [[VelocityReset|VelocityReset]] to e.g. 500 ms, and maybe tweak [[velocity scaling|Development/Documentation/PointerAcceleration]] to tune results. + +If you want _only adaptive deceleration_ and have the default profile (or simple, for that matter), the easiest way is '> xset m 1 1'. + +If you are picky about a _smooth kick-in of acceleration_, for example to ease doing art, I suggest using profile 2 or 3 (the latter being equivalent to xset m x/y 0), enabling adaptive deceleration and tweaking [[VelocityScale|Development/Documentation/PointerAcceleration]] (in that order). Maybe playing with velocity [[AbsDiff/RelDiff|AbsDiff/RelDiff]] also yields some improvement. + +If you want _no acceleration_, use the 'None' profile. You can set it live in xinput or via static configuration. + +If you're _not even willing the spend CPU cycles on this_, set the [[AccelerationScheme|AccelerationScheme]] to none. + + +### Options + + +#### AdaptiveDeceleration [integer] + +_device property: Device Accel Adaptive Deceleration_ + +Allows the acceleration profile to actually decelerate the pointer by the given factor. Adaptive deceleration is a good tool allowing precise pointing, while maintaining pointer speed in general. A good thing even if you don't need it badly. + +Note however that for some profiles and/or acceleration control settings, adaptive deceleration may not come to effect. For example, the polynomial profile with an acceleration control setting of 1.0 will neither accelerate nor decelerate. Thus, there is no deceleration that could be allowed for. + +Default is 1 (no deceleration), mainly not to impose changes on unaware users. + + +#### ConstantDeceleration [integer] + +_device property: Device Accel Constant Deceleration_ + +Constantly decelerates the mouse by given factor. + +Using [[ConstantDeceleration|ConstantDeceleration]] should be preferred over corresponding device driver options (if any) since these retain data which could worsen the prediction of device velocity. An exception is the case where device data contains some error, which you may not want to affect velocity estimation. + +Implemetation note: This factor is applied onto the device velocity estimate, so the actual acceleration relates more to unaccelerated on-screen motion than to device motion. + +<a name="AccelerationProfiles"></a> +#### AccelerationProfile [integer] + +_device property: Device Accel Profile_ + +Select the acceleration profile by number. Default is 0, except if the driver says otherwise (none currently does). + +In this section, _threshold_ and _acceleration_ specify the corresponding X controls (xset m acc_num/acc_den thres). + +0. **classic** (the default) similar to old behaviour, but more predictable. Selects between 'polynomial' and 'simple' based on threshold =/!= 0. + +-1 **none** + + * no velocity-dependent pointer acceleration or deceleration. If constant deceleration is also unused, motion processing is suppressed, saving some cycles. +1. **device-dependent** + + * available if the hardware driver installs it. May be coming for synaptics. +2. **polynomial** + + * Scales polynomial: velocity serves as the coefficient, acceleration being the exponent. Very useable, the recommended profile. +3. **smooth linear** + + * scales mostly linear, but with a smooth (non-linear) start. +4. **simple** + + * Transitions between accelerated/unaccelerated, but with a smooth transition range. This has the fundamental problem of accelerating on two niveaus, on which acceleration stays independent of velocity. Traditionally the default however. +5. **power** + + * accelerates by a power function. velocity is the exponent here. Adheres to threshold. Will easily get hard to control, so it is important you have properly tuned your velocity estimation. +6. **linear** + + * just linear to velocity and acceleration. Simple and clean. +7. **limited** + + * smoothly ascends to acceleration, maxing out at threshold, where it becomes flat (is limited). +<a name="VelocityScale"></a> +#### VelocityScale [real] or + + +#### ExpectedRate [real (Hz)] + +_device property: Device Accel Velocity Scaling_ + +In short, this controls sensitivity of acceleration. + +It is **not** a direct speed control like constant deceleration. It scales the velocity estimate, which may or may not have an effect. That depends solely on the profile. + +This setting is designed to be device-dependent, i.e. you set it once to match your device, then modify behaviour using the established X controls (e.g. xset m nom/den thr) or the profile. + +It is important to note there is no 'correct' factor, just one that bears the nice property of matching to X controls just like the old code did. The [[ExpectedRate|ExpectedRate]] option can be used to set velocity scale according to this criteria. Be aware that this is not a good criteria for high-rate (>500hz) devices. + +You may need this setting if you find it hard to use even moderate acceleration settings/profiles (indicates scale is too high) or you don't seem to get any acceleration (indicates scale is too low). + +Default is 10, which is suitable for devices reporting at approximately 100hz. The relation between the two ways to set scaling is: +[[!format txt """ +VelocityScale = 1000/ExpectedRate +"""]] +Currently, no attempt is made to guess the rate. Thus, high-rate (i.e. gaming) devices _may_ be problematic to accelerate without this tweak. See [[below|Development/Documentation/PointerAcceleration]] for some background info. + +Be aware that constant deceleration is also multiplied into the velocity estimate, so avoid to mess with both at once. + + +### Advanced options + +The following options affect how the velocity estimate is calculated and require some understanding of the algorithm. + + +#### VelocityTrackerCount [integer] + +The number of mickeys tracked. Most likely won't buy you anything to tweak it, but if, you'd best stay between 4 and 40. Default 16. + + +#### VelocityInitialRange [integer] + +The initial velocity is comprised of results up to this offset. 1, the default, means initial velocity will be calculated from the first two mickeys for the most time. 0 may buy you a tiny bit of response, but increases the likelihood of jumps in acceleration. For mice reporting very often (>250 hz), larger values may make sense. + + +#### VelocityAbsDiff [real] + +The absolute difference between an initial velocity and the resulting velocity allowed. Default 1. + + +#### VelocityRelDiff [real] + +The relative difference between an initial velocity and the resulting velocity allowed. Default 0.2. + + +[[!format txt """ +fabs(resulting_velocity - tracker_velocity) <= ((resulting_velocity + tracker_velocity) * relative_difference) +"""]] + +#### VelocityReset [integer] + +Specifies after how many milliseconds of inactivity non-visible state (i.e. subpixel position) is discarded. This affects three issues: + +1) Two mouse strokes do not have any effect on each other if they are + + * [[[VelocityReset|VelocityReset]]] miliseconds from each other. This would be neglible though. +2) Velocity estimate remains correct within this time if the pointer/X is + + * stuck for a short moment, not querying the moving device. +3) slow movements are guessed correctly if all device movement events are + + * inside this time from each other. An increment might be neccessary to fully take advantage of adaptive deceleration. +Default 300 ms. + + +#### Softening [boolean] + +Tweaks motion deltas from device before applying acceleration to smooth out rather constant moves. Tweaking is always below device precision to make sure it doesn't get in the way. Also, when [[ConstantDeceleration|ConstantDeceleration]] is used, Softening is not enabled by default because this provides better (i.e. real) subpixel information. + + +#### AccelerationProfileAveraging (boolean) + +By default, acceleration profiles are averaged between the previous event's velocity estimate and the current one. This is meant to improve predictability. However it has only small impact (practically zero for linear profiles), and can be viewed as inceasing response times, so you can save some cycles if you care. + + +#### AccelerationScheme [string] + +Select Scheme. All other options only apply to the predictable scheme (default). +predictable +: + * the scheme discussed here (default) + +lightweight +: + * previous scheme (i.e. exactly as in X server 1.5 and before). If you prefer saving some cycles over increased useablilty, choose this. + +none +: + * disable acceleration/deceleration + + + +## Technical details + + +### Acceleration profiles (for the inclined programmer) + +Acceleration profiles translate device velocity into an acceleration to be imposed on the pointer. X.Org previously offered two functions: A simple accelerated/unaccelerated switch and polynomial. They are selected somewhat strange through the threshold control: threshold = 0 means polynomial, simple otherwise. + +The simple acceleration function is now continuous, and the polynomial maintains f(1) = 1. They are designed to mimic previous behaviour, so they are wrapped in the classic profile which does the above selection. Just copying old functions would not provide much benefit: The patch would make the point when acceleration is performed be more predictable, but not cause the pointer to cease jumping around that point. In other words, _predictability depends on the profile a lot._ + +If you like to play with the functions, a few nice properties are: + +1. _f(1) ~ 1_ + + * a fixed point, to enable exchanging functions +2. _continuous_ + + * very nice-to-have since we would otherwise throw away our estimate (probably causing jumps) +3. _continuous over derivative(s) or Cn_ + + * nice to have for smoothness. +4. _f'(min_acceleration) = 0_ + + * Ensures a soft kick-in of acceleration +5. _f( < 1) < 1_ + + * enables adaptive deceleration +* although it is possible to hold all of the properies, included functions + * only hold (1), (2), (5), and some also (3). +* acceleration profiles are not meant to enforce constant or adaptive + * deceleration. This is done in a separate step. +* notwithstanding the former, functions might adapt to min_acceleration + * in order to uphold (4). +* In X an acceleration coefficient of 1 is unaccelerated, not 0. + * It can be specified a a rational but we convert it to float. +* usual control values should not make your fn go havoc. See [[PowerProfile|PowerProfile]]() + * for a measure one can take. +If you want to do freaky new functions, you best put them in an own profile. Add your function to [[SetAccelerationProfile|SetAccelerationProfile]](), along with init/uninit code, and you're done. + +Profiles are meant to be exchanged arbitrarily. There are some parts of the code assuming you use profiles solely for acceleration, and not to scale the device in general (or whatever else). Be nice and it will work. Probably. + +While tempting, runtime-defined profiles are currently not possible. This may come with input properties. + + +### Driver side API + +In general, a driver does not need to act in any way. The acceleration is initialized during dix's [[InitValuatorClassDeviceStruct|InitValuatorClassDeviceStruct]], user settings on acceleration are loaded when a driver calls xf86InitValuatorDefaults. These are already called by about every driver. In general, driver-specific interaction should be before xf86IVD, so user settings take precedence. + +But of course it depends on what you want. This small API essentially lets the driver have its say on acceleration and scaling related issues. Proper use could improve the user experience, e.g. by avoiding to double-accelerated synaptics pads. + +The relevant header is _ptrveloc.h_. Most interaction requires a [[DeviceVelocityPtr|DeviceVelocityPtr]]. Use +[[!format txt """ + GetDevicePredictableAccelData(DeviceIntPtr) +"""]] +to obtain it (may return null). After xf86IVD, this may be used as an indicator on whether the predictable scheme is in effect. + + +#### Reporting rate + +If a driver knows the anticipated reporting rate of the device in advance, it might choose to override the default [[VelocityScaling|VelocityScaling]] to improve velocity estimates: +[[!format txt """ + your_velocityPtr->corr_mul = 1000/rate; +"""]] +This is especially worth the effort when the rate differs significantly from the default 100hz. + + +#### Scaling issues + +Also, if your device has very high precision, you can postpone downscaling: +[[!format txt """ + your_velocityPtr->const_acceleration *= 0.5f; +"""]] +This makes the full device precision available to guess velocity, and has potentially more benefits (like not distributing stale remainders all along the event loop). Plus, you don't have to do downscaling yourself :) + +Caveat: Since there is no error correction on dix side, a driver whose device has some error in the signal (like synaptics, on my laptop at least) should downscale just enough for the error to become insignificant. Any surplus scaling might still be done in dix then. + + +#### Device-specific profile + +A hardware driver may use its knowledge about the device to create a special acceleration profile. This can be installed using +[[!format txt """ + SetDeviceSpecificAccelerationProfile() +"""]] +In order to make it the default for the device, simply call +[[!format txt """ + SetAccelerationProfile(velocityPtr, AccelProfileDeviceSpecific); +"""]] +The user may always select it using profile 1. + + +#### Leave me alone + +If you ultimately want no server-side acceleration to be performed, call +[[!format txt """ +InitPointerAccelerationScheme(dev, PtrAccelNoOp). +"""]] +This disables constant deceleration too. + + +### Velocity approximation + +Device velocity, the only dynamic profile input, determines the amount of pointer acceleration. Getting that right thus is crucial to actually improve the state of affairs. + +The velocity discussed here is: +[[!format txt """ +(device_units / milliseconds) * velocity_scale / constant_deceleration +"""]] +By pre-multiplying constant deceleration, the velocity is expected to be comparable across devices. This intends to ease fine-tuning profiles to your likes. + + +#### How it works + +The algorithm keeps a record of (by default) 16 trackers. Each 'knows' a relative device position and when it was in effect. It's a short motion history. So when the user moves the mouse, the accumulated motion of up to 16 mickeys may be used in a distance by time velocity calculation. + +Of course, there are many reasons to not use such a large amount. Using a common 100hz device, this would add ~ 1/8th seconds of delay. For this and other reasons, a few common-sense heuristics are applied. Most importantly, a tracker must be on a roughly linear motion segment towards the current position. Also, trackers mustn't be too old ([[VelocityReset|VelocityReset]]) or result in a velocity too much off the initial velocity (which, by default, is made up from the two latest mickeys). + + +### Other things to ensure predictability + + +#### Continuous profiles + +Acceleration functions, called profiles, are made continuous. That avoids sudden jumps in the amount of acceleration, thus enhancing intuitivity. + +Continuous profiles are complemented by averaging profiles over the interval between the previous and current event's velocity estimate. This exploits the assumption that the real velocity also happened to fall in this range (and went somewhat linear). Not guaranteed, but a very likely case. + + +#### Mickeys are slightly flattened + +This aims to improve evolving-speed movements such as 'painting' with a mouse typically requires. To not get in the way, it happens just below device precision, only if acceleration is actually performed (that is, the profile returned an acceleration greater 1), and not on insignificant mickeys. It can be turned off (Softening option). + +It works simply by comparing previous and current mickey per-axis, and shifting current by 1/2 towards the previous - given they are different and the above conditions are met. + +Example (for one axis only): +[[!format txt """ +1 2 3 2 3 1 +"""]] +would become +[[!format txt """ +1 1.5 2.5 2.5 2.5 1 +"""]] +That's arguably smoother. + + +### Rationale for velocity scaling + +<a name="VelocityScalingRationale"></a> Device motion deltas are being divided by delta milliseconds before being filtered, so they are about _n_ times smaller than the raw input of a device reporting every _n_ ms. Because the reporting rate is usually unknown in advance, this is the only way to scale up to 'normal' values. + +Normalized values are required to sensibly compare against the _threshold_ control, which is an integer. This fact is the main reason for [[VelocityScale|VelocityScale]] to exist - the acceleration control is a rational, so it would in priciple bear enough precision by itself. + +There is, however, one rather soft figure: A velocity estimate of 1.0 should correspond to a rather slow move, which you want to be neither accelerated nor decelerated. _When untranslated_, this corresponds to a move of 100 pixels per second. So for some devices, you may want to set velocity scaling or constant deceleration to keep the estimate in check. + + +## Final notes + + +### Interaction with synaptics / about any smart driver + +I noticed two important things to consider when using the synaptics driver (or any other driver doing substantially more than decoding mickeys): + +It seems synaptics driver implements its own acceleration, which can be switched off. Two ways of accelerating the pointer certainly don't do good. This can be accomplished by setting 2 options, '[[MaxSpeed|MaxSpeed]]' and '[[MinSpeed|MinSpeed]]' to the same. + +I chose [[MaxSpeed|MaxSpeed]] = [[MinSpeed|MinSpeed]] = 1, which seemingly made the native touchpad resolution available to X, which in turn was far too responsive. I had to apply a [[ConstantDeceleration|ConstantDeceleration]] of 8 to work with it. This also makes the full device precision available to guess velocity. + +A good compromise is thus to downscale only so much in the driver as to make the contained error insignificant, and leave the rest to dix. + +As said, you have the choice on who scales down, and the driver could well be the better choice because it knows its stuff. But if it isn't better, choosing X to scale down will result in better velocity approximation, which may be advantageous. diff --git a/Development/Documentation/ReleaseHOWTO.mdwn b/Development/Documentation/ReleaseHOWTO.mdwn new file mode 100644 index 00000000..b14e9a3d --- /dev/null +++ b/Development/Documentation/ReleaseHOWTO.mdwn @@ -0,0 +1,54 @@ + +This page is about how to make a module release, for maintainers. If you are wondering about where to download the latest release of X.Org, please see [[XorgReleases|XorgReleases]]. + + +## Packages needed for releases + +Make sure you have up-to-date **released** versions of these packages before making module or katamari releases. + +* util/macros +* util/modular +* doc/xorg-sgml-doctools +* lib/libxtrans (when building modules such as libX11 or xserver that rely on it) + +## Making module releases + +You **must** make a release if you have changed the ABI or API of your module and other modules rely on it. Likewise, the module to be released must not depend on unreleased code changes in any of its dependencies. Assuming the development and test (including _make distcheck_) have completed successfully and all commits have been pushed to the remote repository, the following steps will perform a _version bump_. + +* Pick a suitable version number, according to the [[X.org version number scheme|Development/Documentation/VersionNumberScheme]]. +* Apply that version number to configure.ac. +* For the xserver module, update RELEASE_DATE variable as well. +* Commit and push your _version bump_ to the remote repository. +Repeat the above steps for each module you wish to release. The module source from the repository is now ready to be released, meaning the _version bump_ commit is to be tagged, a set of tarballs is to be created and uploaded to the X.Org web site and an announce mail template is to be created which you can send to the xorg-announce mailing list. + +The script `util/modular/release.sh` will perform those steps for each module to be released. Invoke the `release.sh` script from any parent directory where the git modules to be released can be reached. +[[!format txt """ +util/modular$ ./release.sh --help + +Usage: release.sh [options] path... +Where "path" is a relative path to a git module, including '.'. +"""]] +* For a single module this would typically be `../../util/modular/release.sh .`. +* For multiple modules, this could be `util/modular/release.sh app/xfs app/xdm`. +* The tarballs are created by _make dist_ or _make distcheck_. +* The tag name is computed by the script as it is different for each module. +* The tarballs are uploaded to the X.Org web site in the appropriate section. +* The annotated tag is pushed to the remote repository. +* The announce e-mail template with check-sum is created. +Consult the help text for the available options. Consider running with `--dry-run` first. +## Making katamaris + +How to make badged semi-annual rollup releases, for release managers. This is basically what happened for 7.3, only that involved more flailing around. + +* on annarchy: + * create /srv/xorg.freedesktop.org/archive/X11R7.x/src + * $EDITOR ~/util/modular/module-list.txt to update the list of modules for this release + * cd /srv/xorg.freedesktop.org/archive/X11R7.x/src + * ~/util/modular/roll-it-up.sh < ~/util/modular/module-list.txt + * cp [[../X11R7|Development/Documentation/X11R7]].3/index.html [[../X11R7|Development/Documentation/X11R7]].3/logo.png . + * $EDITOR index.html + * mkdir doc + * $EDITOR doc/RELNOTES.txt +* update [[http://wiki.x.org/wiki/Releases/7.x|http://wiki.x.org/wiki/Releases/7.x]] +* update [[http://wiki.x.org/wiki/|http://wiki.x.org/wiki/]] to point to the new release +* send mail to the list
\ No newline at end of file diff --git a/Development/Documentation/Security.mdwn b/Development/Documentation/Security.mdwn new file mode 100644 index 00000000..b6fc99cd --- /dev/null +++ b/Development/Documentation/Security.mdwn @@ -0,0 +1,32 @@ + +This page describes access control and authentication mechanisms in X - and how you can implement your own. + +This page does not describe security advisories. For that, see the [[SecurityPage|SecurityPage]]. + +[[!toc ]] + + +## Server Authentication + +The core X protocol includes simple, host-based authentication. The familiar "xhost" client program is used to manipulate the list of allowable hosts. + +The server supports a variety of additional authentication methods as add-ons. Authentication data is delivered to the server in the initial data that is sent by the connecting client. A string identifies the authentication method being used. The authentication methods currently supported in the X.Org xserver are: + +* MIT-MAGIC-COOKIE-1: The most popular scheme, in which a certain string of bytes (the "cookie") must be presented. The server is started up with a file that contains the cookies, and Xlib reads cookies from a file, typically ~/.Xauthority. The "xauth" client program can be used to manipulate the cookies. Most desktop distributions make use of this method. +* XDM-AUTHORIZATION-1 +* SUN-DES-1 +* MIT-KERBEROS-5 +* XC-QUERY-SECURITY-1: A pseudo method used to find out whether the server supports certain extensions in trusted mode or "site policy" strings. This method is unused in all X implementations that this author is aware of (if you know otherwise, please make a note here - deprecation is being considered). +The authentication code is located in the os directory of the xserver, in auth.c and other files. An update being considered would move the authentication methods out of the xserver and implement them as PAM modules (libraries). + + +## Server Access Control + +The X server has long included an extension, SECURITY, which provides support for a simple trusted/untrusted connection model. Untrusted clients are restricted in certain ways to prevent them from reading window contents of other clients, stealing input events, etc. Documentation for this extension is located in the xorg-docs package. This extension has several limitations: + +* X server extensions are not well protected. They can only be turned off entirely. +* Creating untrusted clients is cumbersome since cookie authentications must be "generated" using a protocol request. However, recent version of ssh do make use of this functionality. +* Some portions of the extension, including the property configuration file and the query security authentication method described above, remain unused. +Starting with release 7.2 the X server includes a general framework for building security extensions, the X Access Control Extension. The best place to start if you are a security extension writer is with the XACE documentation, which can be found in the xorg-docs package. XACE inherits from the SECURITY extension and has the same coverage problems, but work is ongoing to verify its coverage and extend it to new places, such as protocol extensions. + +--- [[CategoryServerInternals|CategoryServerInternals]] diff --git a/Development/Documentation/ServerDebugging.mdwn b/Development/Documentation/ServerDebugging.mdwn new file mode 100644 index 00000000..d21853a5 --- /dev/null +++ b/Development/Documentation/ServerDebugging.mdwn @@ -0,0 +1,220 @@ + + +# Debugging the Xserver + +[[!toc ]] + +This minihowto attempts to explain how to debug the X server, particularly in the case where the server crashes. It assumes a basic familiarity with unix and a willingness to risk deadlocking the machine. + +Just as a warning, if you try this with a closed-source driver, the output is not likely to be very useful. + + +## Prerequisites + +You'll really want to have a second machine around. It's very difficult to debug the X server from within itself; when it stops and returns control to the debugger, you won't be able to send events to the xterm running your debugger. ssh is your friend here. If you don't have a second machine, see the [[Debugging with one machine section|Development/Documentation/ServerDebugging]], and good luck. + +Your gdb needs to be reasonably recent, 5.3 or better is probably good. + +And of course, you'll need a reproduceable way of crashing the X server, but if you've read this far you've probably got that already. This is your testcase. + + +### Debug support + +If you're debugging with a modern distribution, then they probably already have 'debuginfo' packages available. These packages (usually quite large) include the debugging symbols for the software you have installed, which makes tools like gdb much more useful. Refer to your distro's documentation for details on how to install these. You'll probably want at least the debuginfo for the X server itself, and for the video driver you're using. For example, on a Fedora machine, you'd say: + + +[[!format txt """ +debuginfo-install xorg-x11-server-Xorg xorg-x11-drv-ati +"""]] +On Debian or Ubuntu you'd say +[[!format txt """ +apt-get install xserver-xorg-core-dbg xserver-xorg-video-ati-dbg +"""]] +Otherwise, if you're building X yourself, you'll need to have built X with debugging information. To pass compiler flags in at build time, say: +[[!format txt """ + CFLAGS='-O0 -g3' ./configure --prefix=... +"""]] +All the normal configure options should work as expected. You may want to put your debuggable server in a different prefix. Be careful of `ModulePath` and other such path statements in your `xorg.conf`. + +Remember that if you're trying to debug into a driver, you'll want to repeat this step for the driver as well as for the server core. + + +## The basics + +Start the server normally. Go over to your second machine and ssh into the first one. `su root`, and type +[[!format txt """ +gdb /opt/xorg-debug/Xorg $(pidof Xorg) +"""]] +or +[[!format txt """ +gdb /usr/bin/Xorg $(pidof X) +"""]] +depending on your setup. + +Note that even when running with a ssh, X might cripples the console. You can avoid this by passing this option: +[[!format txt """ + -keeptty don't detach controlling tty (for debugging only) +"""]] +gdb will attach to the running server and spin for a while reading in symbols from all the drivers. Eventually you'll reach a `(gdb)` prompt. Notice that the X server has halted; type `cont` at the gdb prompt to continue executing. + +Go back to the machine running X, and run your testcase. This time, instead of the server crashing, it should freeze, and gdb should tell you the server got a signal (usually SIGSEGV), as well as the function and line of code where the problem happened. An example looks like: + + +[[!format txt """ + Program received signal SIGSEGV, Segmentation fault. + 0x403245a3 in fbBlt (srcLine=0xc1a1c180, srcStride=59742, srcX=0, + dstLine=0x4240cb6c, dstStride=1152, dstX=0, width=32960, height=764, + alu=-1046602744, pm=1111538028, bpp=32, reverse=0, upsidedown=0) + at fbblt.c:174 + 174 *dst++ = FbDoDestInvarientMergeRop(*src++); +"""]] +This by itself is pretty helpful, but there's more info out there. At the gdb prompt, type `bt f` for a full stack backtrace. (Warning, this will be long!) This dumps out the full call chain of functions from `main()` on down, as well as the arguments they were called with and the value of all local variables. Keep hitting enter until you get back to the gdb prompt. + +Get your mouse out, copy all the output from "Program received..." on down, and paste it into a file on your second machine. Type `detach` at the gdb prompt to detach gdb from the server and let it finish crashing. Go to [[http://bugs.freedesktop.org/|http://bugs.freedesktop.org/]] and file a new bug describing the testcase. Attach the gdb output to the bug (please don't just paste it into the comments section). + + +## All the gdb commands you'll ever need + +For any gdb command, you can say "help <command>" at the (gdb) prompt to get a (hopefully informative) explanation. + + * `bt` - Prints a stack backtrace. This shows all the functions that you are currently inside, from `main()` on down to the point of the crash, along with their arguments. Appending the word `full` (or just the letter `f`) also prints out the value of all the local variables within each function. + * `list` - Prints the source around the current frame. When invoked multiple times, it will print the next lines, making it useful for quick code inspection. "`list -`" prints the source code backwards (starting from the current frame). This is useful to inspect the lines of code that led to an error. + * `break` / `clear` - `break` sets a breakpoint. When execution reaches a breakpoint, the debugger will stop the program and return you to the gdb prompt. You can set breakpoints on functions, lines of code, or individual instructions; see the help text for details. `clear`, naturally, clears a breakpoint. + * `step` / `next` - `step` and `next` allow you to manually advance the program's execution. `next` runs the program until you reach a different source line; `step` does the same thing, but also descends into called functions. + * `continue` - continue the program normally until the next breakpoint is hit. + * `print` - Prints the expression. You can specify variable names, registers, and absolute addresses, as well as more complex expressions (`help print` for details). Variable names have to be resolveable, which means they either have to be local variables within the current stack frame or global variables. Register names start with a `$` sign, like `print $eax`. Addresses are specified as numbers, like `print 0xdeadbeef`. + * Expressions can be fairly complex. For example, if you have a pointer to a structure named `foo`, `print foo` will print the memory address that foo points to, `print *foo` will print the structure being pointed too, and `print foo->bar` will print the bar member of the foo structure. + * `handle` - Tells the debugger how to handle various signals. The defaults are mostly sensible, but there are two you may wish to change. SIGPIPE is generated when a client dies, which you may not always care about, and SIGUSR1 is generated on VT switch. By default, the debugger will halt the running process when it receives these signals; to change this, say `handle SIGPIPE nostop` and `handle SIGUSR1 nostop`. (Note: Don't use `handle SIGUSR1 ignore` or you can confuse things quite badly---for example, having multiple X servers simultaneously active on the same VT can be very confusing.) + * `set environment` - Sets environment variables. The syntax is `set environment name value`; don't use an = sign like in bash, it won't do what you expect. + * `run` - Runs the program. If you only specify a program name on the command line (and not a process ID or a core file), gdb will load the program but not start running it until you say so. Arguments to `run` are passed verbatim to the child process, eg `run :0 -verbose -ac`. + * `kill` - Kills the program being debugged. Not always useful, you'd often rather say... + * `detach` - which detaches the debugger from the running program, which can then shut down gracefully. + * `disassemble` - Prints the assembly instructions being executed, starting at the current source line. You can also specify absolute memory references or function names to start disassembly somewhere other than the default. Only useful if you can read the assembly language of your CPU. + * `finish` - Continue until exit of current function. Will also print the return value of the function (if applicable).\ +Note that most commands can be used in an abbreviated version (e.g. `n` instead of `next`). Just try it yourself! + + +## Things that can go wrong + +The biggest thing to watch out for is attempting to print memory contents when that memory is located on the video card. It won't work, on x86 anyway, for some not-very-interesting reasons. You'll know when you did it because the machine will deadlock and you'll have to reboot. See the Debugging``Hints file (below) for workarounds. + +Some issues with running X under gdb may be resolved by passing the `-dumbSched` option to the X server. This worked for me to resolve crashes of gdb 6.3 and strange loops in gdb 5.3. You'll know if you need this option because gdb will get very confused by SIGALRM. Even if gdb isn't misbehaving, the -dumbSched option can be very helpful to avoid the SIGALRM peridocially interrupting your debugging session. + +Likewise, some gdb versions crash when starting the X server when attempting to run xkbcomp. This is, amazingly enough, a bug in the kernel's DRM code for suppressing some signals; it should be fixed in 2.6.28 if not earlier. You can disable XKB by passing the `-kb` option on the server's command line; obviously if you're trying to debug XKB this may cause you some problems and you're probably better off attaching gdb to a running X instead. Alternatively, disable DRI, but again, if DRI is the thing you're trying to debug, that won't help. + +When you compile with optimization, the values printed by bt can sometimes be confusing. Some variables can get optimized out of existance, some variables occupy the same position on the stack during different parts of a function's execution, and some functions might not show up on the stack at all. Also, single-stepping can be confusing because the function might get executed in a different order than listed in the source if the compiler determines that's safe to do. gcc 4.0 seems to be **much** more aggressive at confusing the debugger than earlier versions, although it does emit more debugging information such that you'll at least know when variables have been optimized away. As always, lowering the optimization level improves debuggability. + + +## Further information + +There is a Debugging``Hints file available [[online|http://freedesktop.org/cgi-bin/viewcvs.cgi/*checkout*/xorg/xc/programs/Xserver/hw/xfree86/DebuggingHints]]. It contains a lot of helpful (if slightly dated) information on how to debug the server, including how to dump PCI memory without deadlocking the machine. In particular, you'll want to read this if you're trying to debug a server older than 6.9. + +<a name="OneMachine"></a> +## Debugging with one machine + + +### Version 1 + +The script below allows you to run the server in gdb and catch the gdb output in a file. You cannot interactively control gdb, however the Xserver should not hang gdb by stopping inside the debugger while you cannot control it from a terminal. Store the following script in some file (for example: `/tmp/Xdbg`: +[[!format txt """ +#!/bin/sh + +#GDB=... +#XSERVER=... + +ARGS=$* +PID=$$ + +test -z "$GDB" && GDB=gdb +test -z "$XSERVER" && XSERVER=/usr/bin/Xorg + +cat > /tmp/.dbgfile.$PID << HERE +file $XSERVER +set confirm off +set args $ARGS +handle SIGUSR1 nostop +handle SIGUSR2 nostop +handle SIGPIPE nostop +run +bt full +cont +quit +HERE + +$GDB --quiet --command=/tmp/.dbgfile.$PID &> /tmp/gdb_log.$PID + +rm -f /tmp/.dbgfile.$PID +echo "Log written to: /tmp/gdb_log.$PID" +"""]] +Then (as root) do: +[[!format txt """ +chmod u+x /tmp/Xdbg +mv /usr/X11R6/bin/X /usr/X11R6/bin/X.org +ln -sf /tmp/Xdbg /usr/X11R6/bin/X +"""]] +If you are using a module aware debugger you should remove the comment sign `#` form the line starting with `#GDB` and add the full path to your debugging gdb. You can now start your Xserver like normal. Note, that if you use `startx` you should do so as root. When the Xserver crashes the output of the server should have been written to `/tmp/gdb_log.<number>` together with a backtrace. If your Xserver resides at some other place you can use the `XSERVER` environment variable to specify the path. To restore the previous setup do: +[[!format txt """ +mv /usr/X11R6/bin/X.org /usr/X11R6/bin/X +"""]] + +### Version 2 + +If you only have one machine available, you might be able to pry some useful information from the server when it crashes. The downside is that it will probably halt your machine entirely rather than just crashing X. + +Edit your xorg.conf file and find the [[ServerFlags|ServerFlags]] section. Uncomment the +[[!format txt """ + Option "NoTrapSignals" +"""]] +line (or add it if it doesn't exist). This will prevent the server from catching fatal signals, which should cause core dumps instead. (You need to make sure you have core dumps enabled for the server by removing the appropriate ulimit; see the `ulimit` command in the bash man page for details.) + +The problem here is the same as mentioned earlier; the core dump will attempt to included mmap()'d sections of card memory, which will make the machine freeze. Usually the core dump is informative enough to at least give a partial backtrace. + +Once you've crashed the machine, find the core file and load it in gdb: +[[!format txt """ + gdb `which Xorg` /path/to/core/file +"""]] +and try to `bt f` like normal. Fortunately at this point you can't make the machine crash again. + +<a name="GdbServer"></a> +## Debugging with gdbserver + +Run X on the target using gdbserver, listening on (for example) port 2500: +[[!format txt """ + gdbserver :2500 /usr/bin/X +"""]] +Attach to the running process from gdb, running it from an environment in which you have Xorg installed. In my case, this is a chroot environment. If I try to debug the program from the host environment, without chrooting into my Xorg build environment, gdb cannot find the symbols correctly. + + +[[!format txt """ +root:/usr/src/xc-build# gdb +GNU gdb 6.3 +Copyright 2004 Free Software Foundation, Inc. +GDB is free software, covered by the GNU General Public License, and you are +welcome to change it and/or distribute copies of it under certain conditions. +Type "show copying" to see the conditions. +There is absolutely no warranty for GDB. Type "show warranty" for details. +This GDB was configured as "i686-pc-linux-gnu". +(gdb) file programs/Xserver/Xorg +Reading symbols from /usr/src/xc-build/programs/Xserver/Xorg...done.Using host libthread_db library "/lib/libthread_db.so.1". +(gdb) target remote 192.168.0.134:2401 +Remote debugging using 192.168.0.134:2401 +0xb7fed7b0 in ?? () +(gdb) c +Continuing. + +Program received signal SIGSEGV, Segmentation fault. +0xb7a92524 in GXDisplayVideo (pScrni=0x828bd38, id=0xb7aa9490, offset=0x17, + width=0x82a, height=0xe730, pitch=0xb7aa946c, x1=0x8289920, y1=0x0, + x2=0x0, y2=0x0, dstBox=0x82ae680, src_w=0x82a, src_h=0xe794, drw_w=0x828, + drw_h=0x8638) at amd_gx_video.c:849 +849 GFX(set_video_enable(1)); +(gdb) +"""]] +Note in this example that I specify the program to be debugged with a gdb command to read the Xorg symbols: +[[!format txt """ + (gdb) file programs/Xserver/Xorg +"""]] +This is simply an alternative to running gdb like this: +[[!format txt """ + gdb programs/Xserver/Xorg +"""]]
\ No newline at end of file diff --git a/Development/Documentation/ServerProfiling.mdwn b/Development/Documentation/ServerProfiling.mdwn new file mode 100644 index 00000000..88150518 --- /dev/null +++ b/Development/Documentation/ServerProfiling.mdwn @@ -0,0 +1,22 @@ + +If you're on a Linux system, sysprof is your best friend. First, make sure you've got the kernel development headers, and debugging information for the things you're trying to profile. On a Fedora system, that looks like: + + +[[!format txt """ +% sudo yum -y install kernel-devel +% sudo debuginfo-install -y xorg-x11-server-Xorg xorg-x11-drv-savage +"""]] +Then, build sysprof: + + +[[!format txt """ +% git clone git://git.gnome.org/sysprof +% cd sysprof +% ./autogen.sh +% make +% sudo make install +% sudo sysprof & +"""]] +Click "Start", do some stuff, click "Profile", and revel in the glorious CPU time accounting. + +Note that sysprof is itself an X application, so you may want to run it forwarded to another display so it doesn't end up profiling its own animation. diff --git a/Development/Documentation/SubmittingPatches.mdwn b/Development/Documentation/SubmittingPatches.mdwn new file mode 100644 index 00000000..c56c419e --- /dev/null +++ b/Development/Documentation/SubmittingPatches.mdwn @@ -0,0 +1,199 @@ + +X.Org uses patches to do code development. This page describes the required format of a patch as well as the workflow to create, send and apply it. We assume you have a git cloned repository and are familiar with making code changes and commits. + +Take a look at this [[example commit|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9fe9b6e4ef669b192ee349e3290db5d2aeea273c]] from which this [[patch|http://lists.freedesktop.org/archives/xorg/2009-February/043171.html]] has been created. Open them in separate browser windows and refer to them while you read the rest of the page. + + +# Workflow overview + +**Note:** This workflow illustrates the lifecycle of a patch and does not constitute a development process. If you intend to develop patches for the X Server, consult their [[development process|http://www.x.org/wiki/XServer]]. + +The patch submitter does the following: + +* Commit code changes to the local repository using the [[git-commit|http://www.kernel.org/pub/software/scm/git/docs/git-commit.html]] command +* Create a patch using the [[git-format-patch|http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html]] command +* E-mail the patch to the xorg-devel list using the [[git-send-email|http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html]] command +The xorg-devel list reviewers do one of the following: + +* Signify their approval or disapproval (Acked-by or Nacked-by) +* State an opinion about the appropriateness of the patch (Reviewed-by) +* Test the patch (Tested-by) +The module maintainer does the following: + +* Obtain the patch from the bug report or from the xorg-devel list +* Apply the patch to a local repository using the [[git-am|http://www.kernel.org/pub/software/scm/git/docs/git-am.html]] command +* Push the patch to the git remote repository using the [[git-push|http://www.kernel.org/pub/software/scm/git/docs/git-push.html]] command + +# Making code changes + +This is where it all starts. Think about the reviewers when you are organizing code changes. Focus on one issue and change one or more files to resolve the issue. In our [[example patch|http://lists.freedesktop.org/archives/xorg/2009-February/043171.html]], the code change only deals with fixing the wrong behavior of the mouse buttons reported by the user. + +Changes should follow the [[coding style guidelines|CodingStyle]]. + +Before creating a commit, ensure your git user name and e-mail is configured correctly using the [[git-config|http://www.kernel.org/pub/software/scm/git/docs/git-config.html]] command. Use your real name as opposed to a nickname as you will be signing off your patches, indicating that you are able to release the patch under the licensing terms of the module. +[[!format txt """ +$> git config --global --get user.name +$> git config --global --get user.email +"""]] + +# Creating a commit + +Once the code changes are implemented and tested on your local repository, they must be _committed_. A _commit object_ is created which wraps your code changes with various git information. It is included in the patch you will create later. Nothing is sent to the remote git repository on the freedesktop.org server. + +You tell git to add the files you changed using the [[git-add|http://www.kernel.org/pub/software/scm/git/docs/git-add.html]] command. You then commit the changes using the [[git-commit|http://www.kernel.org/pub/software/scm/git/docs/git-commit.html]] command. +[[!format txt """ +$> git add mipointer.c # file changed to fix the bug +$> git commit -s # -s adds the sign-off tag in the commit text +"""]] +The git commit command raises the nano editor for you to enter the _commit message_ that is describe in the next section. When you exit the editor, the _commit object_ is created. Monitor the changes to the local repository using the [[git-status|http://www.kernel.org/pub/software/scm/git/docs/git-status.html]] command and the [[git-show|http://www.kernel.org/pub/software/scm/git/docs/git-show.html]] command. + + +## Commit message format + +Begin the commit message with a single short (less than 78 character) line summarizing the changes, followed by a blank line and then a more thorough description. Tools that turn commits into email, for example, use the first line on the _Subject:_ line and the rest of the commit in the body. + +When referencing a reported bug, use the bug number from [[FreeDesktop Bugzilla|https://bugs.freedesktop.org/]]. If there is no corresponding bug, you should upstream the bug from your distribution to freedesktop.org. + +An example of how to reference a reported bug in the commit message: +[[!format txt """ +Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=29049 +"""]] + +### Subject line + +The subject line summarizes the code changes contained in the patch. For large components such as the X Server, prefix with the subsystem (e.g. dix, Xi, xfree86, kdrive, etc.). Look at the xserver's git log to give you guidance. The subject line should also include the bug number if available. + +The subject line from the example, as it appears in the _commit object_: +[[!format txt """ +mi: don't call UpdateSpriteForScreen if we have Xinerama enabled. #18668 +"""]] +Do not type the word [PATCH] in the subject line, it gets added later when the patch is created. + + +### Message body + +Explain in sufficient detail what the patch does and why this is necessary. This does not mean you need to describe the actual source changes (e.g. "changed x to be 10, then added x to y"). Use common sense and look at git logs for guidance. See also [["on commit messages"|http://who-t.blogspot.com/2009/12/on-commit-messages.html]] + +The message body also contains your sign-off tag, so in our example: +[[!format txt """ +Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> +"""]] +Other tags may be added after the patch review as hinted in the workflow overview. + + +# Creating a patch + +Once the _commit object_ has been created with the proper subject line and message body, you can create a patch for it in order to either attach it to the bug report or e-mail it to the list. + + +[[!format txt """ +$> git format-patch HEAD~1 # create a patch for the last commit +"""]] +This will create a file named "0001-_description-of-my-change_.patch". Git uses the first line of the commit message (massaged for path-name safety) as the file name. + +The subject line of the example patch: + + +[[!format txt """ +[PATCH] mi: don't call UpdateSpriteForScreen if we have Xinerama enabled. #18668 +"""]] +The git format-patch command has prefixed the commit _subject line_ with the word [PATCH] on your behalf. If you haven't signed-off in the commit message body, you can do so with the --signoff option. + +If you are submitting a patch for applications, drivers or libraries to xorg-devel list, you should add the component name next to the PATCH word using the --subject-prefix option. + +Examples: +[[!format txt """ +[PATCH evdev] fix crash on VT switch #12345 +[PATCH libXi] convert to ANSI +"""]] +The reviewers need to know for which component this patch is for when reading the e-mail (there are over 200 of them). You can configure the git format-patch command to always do it for you: + + +[[!format txt """ +$> git config format.subjectprefix "PATCH evdev" +"""]] + +## Extra info + +If you are sending the patch to the list, you may include additional information (benchmark results, a method how to reproduce it) after the -- in the git formatted patch. When the patch is applied, this information is omitted. If you are submitting a patch for a specific server version (not git master), then please note your version here. If this bug affected previous released versions of the X server it helps to say so too. + + +## Plain text format + +Always attach patches as plain text files - if emailed then either attached or in-line. Never attach a zip file, tarball or any other archive with patches. Posting a link to a pastebin is permissible on IRC, don't post links on mailing lists, just attach the patch directly to the email. + +Apply common sense: make it as easy as possible for others to look at the patch. The more steps required to look at your patch and write a review, the more likely it will be ignored. + + +# E-Mailing a patch + +E-mail the patch you have just created to the xorg-devel list for review and approval. Let's use the [[git-send-email|http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html]] command for that. Of course, you can use other e-mail clients to attach your patch. If you decide to use a mailer, make sure your mailer isn't altering the spaces or lines of the patch, or the patch won't work. + +Configure the send-email client using the same git config command we have used so far. The example patch can be e-mailed using this command: +[[!format txt """ +$> git send-email --to xorg-devel@lists.x.org 0001-mi-don-t-call-UpdateSpriteForScreen-if-we-have-Xine.patch +"""]] +You can use the --dry-run option and/or send it to yourself to try it out first. + +Configuring send-email: +[[!format txt """ +git config --global sendemail.confirm always +git config --global sendemail.smtpserver <your mail server> +git config --global sendemail.supresscc self +git config --global sendemail.from "First Last <myself@example.com>" +"""]] +Patches sent to the mailing list are tracked by [[Patchwork|http://ozlabs.org/~jk/projects/patchwork/]] patch tracking system. The [[patchwork.freedesktop.org|http://patchwork.freedesktop.org/]] is now available for general use. + +If you are already subscribed to xorg-devel using the address the patch comes from, and it's smaller than the list's size limit, it should be delivered immediately - otherwise it goes into a moderation queue which is usually manually processed at least once a day. If you send many patches from an address that you don't want all xorg-devel mail to come to, you can subscribe to the list and then go to the list options page in mailman to turn off mail delivery. + + +# Signing off and reviewing + +X.Org developers may use a number of tags to acknowledge patches, both in a commit message and when reviewing patches. Here's a short summary for each tag, please refer to [[the Linux kernel's Documentation/SubmittingPatches|http://lxr.linux.no/linux/Documentation/SubmittingPatches]] file for details. The summaries below are copied from that file. + + * **Signed-off-by:** certifies that you wrote it or otherwise have the right to pass it on as a open-source patch. + * **Acked-by:** If a person was not directly involved in the preparation or handling of a patch but wishes to signify and record their approval of it then they can arrange to have an Acked-by: line. Acked-by: does not necessarily indicate acknowledgement of the entire patch. + * **Tested-by:** A Tested-by: tag indicates that the patch has been successfully tested (in some environment) by the person named. This tag informs maintainers that some testing has been performed, provides a means to locate testers for future patches, and ensures credit for the testers. + * **Reviewed-by:** A Reviewed-by tag is a statement of opinion that the patch is an appropriate modification without any remaining serious technical issues. Any interested reviewer (who has done the work) can offer a Reviewed-by tag for a patch. +Whenever you review a patch on the mailing list or in a bugzilla, feel free to provide the appropriate tag as a reply email (or a comment on bugzilla). + + +## Getting no response + +We don't have an abundance of developers and sometimes bugs or patches get dropped. If this happens to your patch, ping the list/bug again after a sufficient period (a few days at the very least). CC the [[maintainer|http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/MAINTAINERS]] of the matching subsystem. + + +## Changing a patch + +Likely, a developer will tell you to make some changes to the code or the commit message. Although you have committed your changes locally, you can still edit them. + +_git commit --amend_ lets you edit the last commit. By default, this only edits the commit message (e.g. _git commit --amend -s_ adds the signed-off-by if you've forgotten it). Any code changes you want to incorporate into the commit, use _git add filename_ before amending the commit. Then re-send/attach the new patch. + +If your patch is not the last commit in your local tree, consider using the [[git-rebase|http://www.kernel.org/pub/software/scm/git/docs/git-rebase.html]] command in interactive mode. + + +# Applying a patch + +Although not the subject of this wiki page, it helps making better patches when you understand those on the other side of the fence. You may also want to test your own patch, round trip, by sending it to yourself. + +Download the patch from your favorite e-mail client as plain text file in the appropriate git local repository. Use the [[git-am|http://www.kernel.org/pub/software/scm/git/docs/git-am.html]] command to apply this patch. + + +# Using git + +Always use git to generate a patch. Why? All X.Org developers work with git and a git-formatted patch is easiest to apply and preserves ownership (which is in your interest). If you are working from a tarball or a distribution package, read [[generating git patches from tarballs|http://who-t.blogspot.com/2009/06/git-patches-from-tarballs.html]] to find out how to set up a temporary git repository. + +This summarizes the commands needed to create and e-mail a patch such as the example used: +[[!format txt """ +$> # Edit files to make code changes +$> git add file.c # Add changed files to be committed +$> git commit -s # Sign-off and commit changes, write commit message +$> git format-patch HEAD~1 # create a patch for the last commit +$> git send-email --to xorg-devel@lists.x.org 0001-*.patch +"""]] + +# Further reading + +* [[List of Xorg maintainers|http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/MAINTAINERS]] +* [[Kernel patch submission process|http://kernelnewbies.org/UpstreamMerge/SubmittingPatches]]: details about patch format and contents equally apply to X.Org patches. +* [[Git User's Manual|http://www.kernel.org/pub/software/scm/git/docs/user-manual.html]]
\ No newline at end of file diff --git a/Development/Documentation/UsingCtags.mdwn b/Development/Documentation/UsingCtags.mdwn new file mode 100644 index 00000000..d9b0fdbb --- /dev/null +++ b/Development/Documentation/UsingCtags.mdwn @@ -0,0 +1,30 @@ + + +## Using ctags to find functions + +Finding functions in X is hard. One way to search for the actual definition of a data type is to grep the source directory and then open the file. This can take forever, especially when you don't quite know where to look for. + +However, vim's support for ctags makes it easier. It is possible to create a tags file for the whole system and then just use it from within vim. That way, in vim you only have to go to the occurence of the data type, press CTRL+] and it will open the matching definition. With CTRL+T you jump back to the original file. + +I created my tags file somewhere in my .vim directory. + + +[[!format txt """ +$> mkdir .vim/tags/ +$> cd .vim/tags/ +$> ctags -R /usr/include/* /path/to/X/source/code +"""]] +ctags will create a file "tags" in the current directory ($HOME/.vim/tags in this case). This way I got pretty much all defintions I need at the moment. + +Now you need to tell vim to include this file. Add the following line to your $HOME/.vimrc. +[[!format txt """ +set tags=./tags,tags,/home/username/.vim/tags/tags +"""]] +On your next startup of vim, everything will be available with CTRL+]. If you use tags heavily, you will find CTRL+G helpful. It shows the name of the file in the current buffer. + +A recommendation is to write a little script to update your ctags and run it as a cron job every night. Your computer will not be very responsive while recursively searching for ctags in a multi-GB directory. + + +#### Warning + +This can be a hazardous setup as the ctags are absolute. If you are working on two different source trees (i.e. two releases of the same software), using CTRL+ ] will jump to the functions as defined in ctags. So you might be editing the wrong source tree. diff --git a/Development/Documentation/UsingEclipse.mdwn b/Development/Documentation/UsingEclipse.mdwn new file mode 100644 index 00000000..e2d85d4f --- /dev/null +++ b/Development/Documentation/UsingEclipse.mdwn @@ -0,0 +1,142 @@ + + +# Using Eclipse CDT to develop Xorg + +[[!toc ]] + + +## Benefits + +* **Code Navigation** + * CDT 4.0 includes a fast code indexer and navigator which allows you browse call hierarchy, and quickly jump to the symbol declarations. +* **Debugging** + * acts as an interactive frontend to the GDB debugger + * allows remote debugging via gdbserver +* **It doesn't get in the way** + * it doesn't require any particular directory layout + * it doesn't require any particular build system, i.e., it plays nicely with autotools, hand-written Makefiles, or any build system which can output a build log + * it has a configurable C coding style + * it provides access to the GDB console while debugging + * it has powerful regular expressions searching and replacing abilities + +## Screenshots + +[[!img http://people.freedesktop.org/~jrfonseca/eclipse/eclipse-cdt-main.png] + +[[!img http://people.freedesktop.org/~jrfonseca/eclipse/eclipse-cdt-remote-debug.png] + + +## Installation How-to + +If you're only interested in C/C++ development the simplest option is to download [[Eclipse IDE for C/C++ Developers|http://www.eclipse.org/downloads/moreinfo/c.php]] and extract it into /opt. + +Otherwise, you can always install CDT from the Eclipse Update Manager. + +Then install the [[Eclipse-Autotools integration plugin|http://sourceware.org/eclipse/autotools/]], which provides assistance for projects using autotools. + + +## Introduction + +Eclipse organizes code in _projects_ and _workspaces_. + +* A _project_ is equivalent to a X.Org module. Projects have different build settings and separate source repositories. +* A _workspace_ is a set of related projects. Workspaces have different settings, and a workspace can only be opened by a single instance of Eclipse at any given time. +NOTE: You don't need to create a project for every single X.Org module, and that would be overkill. The modules you are planning to actively develop and debug are perfectly sufficient, as you can still open and debug through files outside the projects. + +Eclipse organizes windows in _views_ and _perspectives_. + +* A _view_ is a display. You can add and re-arrange existing views. +* A _perpective_ is a set of views in a given layout. You can switch perspectives. The most interesting are the C/C++ and the Debug perspective. + +## Xorg How-to + +It is assumed you have installed the xorg development packages from your distribution, or you have built xorg from source as explained in the [[ModularDevelopersGuide|ModularDevelopersGuide]] in /opt/xorg. + +* Initial configuration + * Start eclipse and enter the path to your workspace (it can be an inexistent directory as Eclipse creates one for you) + * You'll be presented with the welcome screen. Click to go to the workbench. + * Switch to the _C/C++ Perspective_ by going to _Window > Open Perspective > Other... > C / C++_ + * In _Window > Preferences > C/C++ > Environment_ dialog set the following environment variables [[!format txt """ +LD_LIBRARY_PATH=/opt/xorg/lib +ACLOCAL="aclocal -I /opt/xorg/share/aclocal" +CPPFLAGS="-I /opt/xorg/include" +CFLAGS="-O0 -g3 -fmessage-length=0" +CXXFLAGS="-O0 -g3 -fmessage-length=0" +"""]] +* Create a project for `xserver` + * In a terminal do: [[!format txt """ +cd /path/to/your/workspace +git clone git://anongit.freedesktop.org/git/xorg/xserver +"""]] + * File > New > GNU C Autotools Project + * Set `xserver` as the project (the same as the git module) + * In _Project > Properties_ dialog, _C/C++ Build > Settings > Tool Settings_ tab + * Under _configure > General > Directory specifiers_ set the installation directory (--prefix) to `/opt/xorg` + * Under _configure > Features and packages_ set _Enable maintainer mode (--enable-maintainer-mode)_ and enter any other configuration options you wish to pass to `configure` + * Press Ctrl+B to build the project. + * To switch between `configure` output and the `make` output go to the _Console_ view, and click on the _Display Selected Console_ button. + * Double-click install target of the _Make Targets_ view. +* Debug Xnest locally + * In the _Debug > Debug settings..._ dialog, under _C/C++ Local Application_ click on the _New_ button + * Set `/opt/xorg/bin/Xnest` as the application path + * Set as arguments `:1` + * Click on the _Debug_ button. + * The gdb console is available from the _Console_ view, _Console_ by clicking on the _Display Selected Console_ button. +* Debug Xorg remotely + * rsync the `/opt/xorg` directory to the remote machine [[!format txt """ +rsync -av --delete /opt/xorg/ your-remote-machine:/opt/xorg/ +"""]] + * in the remote machine run [[!format txt """ +gdbserver :10000 /opt/xorg/bin/Xorg +"""]] + * In the _Debug > Debug settings..._ dialog, under _C/C++ Local Application_ click on the _New_ button + * Set `/opt/xorg/bin/Xorg` as the application path + * Choose gdbserver in the Debugger tab + * Enter the hostname and of the remote machine and the port that gdb is listening to + * Click on the _Debug_ button. +You can add more modules and/or debug targets in a similar fashion. + + +## Code Formatting + +CDT allows to specify the C code style from _Window > Preferences > C/C++ > Code style_ property page. + +You can import [[this profile|http://people.freedesktop.org/~jrfonseca/eclipse/xorg-code-style.xml]], which was made to follow [[these (un)official guidelines|http://lists.freedesktop.org/archives/xorg/2004-October/003673.html]] as close as possible. + +There is also a [[code style for Mesa|http://people.freedesktop.org/~jrfonseca/eclipse/mesa-code-style.xml]]. + + +## Full tree setup + +You can add the whole tree as a project, which is advantageous when cross-module work is done, or you are interested in module interdependecies. However, index generation can get darn slow then. Manually specifying include directories and disabling _automated discovery_ in the project's discovery options may be helpful. + +Also, eclipse prior to ganymede had the tendency to spend a few minutes on collecting the (admittedly huge) index whenever you'd type a member access operator (. or ->). Disabling _Content Assist_ should help that. + + +## Tips + +* To avoid out-of-memory errors change the last lines of `eclipse.ini` to [[!format txt """ +-vmargs +-Xms64m +-Xmx1024m +"""]] +* The autotools plugin simplifies the invocation of autoconf and automake, but it has some bugs that you should watch out for: + * [[https://bugzilla.redhat.com/show_bug.cgi?id=324681|https://bugzilla.redhat.com/show_bug.cgi?id=324681]] +* In _Window > Preferences > General > Keys_ bind Ctrl+B to build the current project, instead of all projects. +* In _Window > Preferences > General_ set to _Always run in background_ +* In _Window > Preferences > Run/Debug > Launching_ set to Launch the previous launched application +Check more tips in: + +* [[http://tkramar.blogspot.com/2007/10/effective-eclipse-i-setup.html|http://tkramar.blogspot.com/2007/10/effective-eclipse-i-setup.html]] +* [[http://dmy999.com/article/29/using-eclipse-efficiently|http://dmy999.com/article/29/using-eclipse-efficiently]] + +## Other plugins + +Must have: + +* [[Extended VS Presentation plugin for Eclipse|http://andrei.gmxhome.de/skins/index.html]] -- this plugin modifies Eclipse's look and feel to make it waste less screen space, and easier to use. +* [[Rectangular edit plugin|http://lunar-eclipse.sourceforge.net/editor-tutorial/index.html]] -- provides rectangular editing abilities, like VIM and Emacs. +Optional: + +* [[Target Management plugin|http://www.eclipse.org/dsdp/tm/]] -- simplifies remote debugging and testing by allowing to seemingly manipulate remote files and shells. +* [[egit|http://git.or.cz/gitwiki/EclipsePlugin]] -- git integration plugin -- is still on early stages of development with very limited functionality and must be compiled from source, but it already provides a visual history viewer similar to gitk.
\ No newline at end of file diff --git a/Development/Documentation/WrappingFunctions.mdwn b/Development/Documentation/WrappingFunctions.mdwn new file mode 100644 index 00000000..735e1898 --- /dev/null +++ b/Development/Documentation/WrappingFunctions.mdwn @@ -0,0 +1,38 @@ + +# Moved from [[http://www.freedesktop.org/wiki/Software/WrappingFunctions|http://www.freedesktop.org/wiki/Software/WrappingFunctions]] + + +## Wrapping Functions + +_XXX: Add some information about prologues/epilogues_ + +Sometimes you want to override or hook into a certain function and have it do something else. For example, you might want to use an accelerated function for drawing triangles. This is done by replacing the function pointers in the data structures + + +[[!format txt """ +/* Don't forget to save the original function */ +pMyScreenData->CreatePixmap = pSCreen->CreatePixmap; + +/* Replace the function */ +pScreen->CreatePixmap = MyCreatePixmap; +"""]] +Now the function `MyCreatePixmap` will be called instead of the regular `CreatePixmap` function. This is good if we're superstitious: +[[!format txt """ +static PixmapPtr +MyCreatePixmap (ScreenPtr pScreen, int w, int h, int depth) +{ + MyScreenDataPtr pMyScreenData = GET''MY''SCREEN_DATA (pScreen); + + if (w == 13 && h == 13) + { + /* Refuse to create pixmaps with size 13x13 */ + return NULL; + } + + /* Call the original function */ + return (* pMyScreenData->CreatePixmap) (pScreen, w, h, depth); +} +"""]] +(See [[Development/Documentation/DevPrivates|Development/Documentation/DevPrivates]] for information on where the `MyScreenDataPtr` comes from) + +-- [[AndersCarlsson|AndersCarlsson]] - 23 Sep 2003 diff --git a/Development/Documentation/WritingDocumentation.moin b/Development/Documentation/WritingDocumentation.moin new file mode 100644 index 00000000..31f795a9 --- /dev/null +++ b/Development/Documentation/WritingDocumentation.moin @@ -0,0 +1,156 @@ +This page describes which tools are available for the various types of documentation one can contribute to.
+
+== Doxygen ==
+
+If you're describing an API, the best choice is probably [[http://www.doxygen.org|Doxygen]]. Doxygen allows you to comment your C files and headers inline, and later generates documents from same. For a good example of how to use Doxygen, take a look at the X server [[http://cgit.freedesktop.org/xorg/xserver/tree/hw/dmx/doc|Distributed Multihead X Design]].
+
+== DocBook ==
+
+Larger documents are maintained in [[http://www.docbook.org|DocBook/XML]] format. As of X11``R7.6, almost all documentation have been converted from DocBook/SGML, Framemaker, troff, Linuxdoc and TeX to DocBook/XML. The doc/xorg-docs module contains general X Window System documentation, anything specific has been moved to the appropriate module.
+
+== Man Pages (troff with "man" macros) ==
+
+Commands and public API in client-side libraries are documented in the traditional ''roff'' man page format which involves a significant learning curve.
+
+=== Commands: ===
+ * `.\"` Comment: the rest of the line is a comment.
+ * `.TH` Text Header: This is the header of a line. It contains the name of the page in capital letters followed by the section the page is to be located in. Then it contains `''''vendorversion''''` which is replaced by the vendor version when the system is built.
+ * `.SH` Section Header: Man pages contain several sections. Some are ordered according to a standard conventions. Their names are capitalized.
+ * `.B` : Boldface: Print following text in boldface.
+ * `.I` : Italic: Italic/underline the following text.
+ * `.P` : Paragraph: Start a new paragraph.`.PP` Double paragraph (?).
+ * `.br` : Break: insert a linebreak.
+ * `.R` : Roman: Non-italic non-bold font
+ * `.BR : alternating bold and regular font
+ * `.RB : alternating regular and bold font
+ * `.TP` Tabulator: May optionally be followed by a indentation width. The next line is indented normally, any lines following this line up to the next paragraph command (ie. `.SH`, `.TP`, `.P` are indented according to the number following the command relative to the normal indentation.
+ * `.fi`: (?)
+ * `.nf`: (?)
+ * Characters `.`,`-`, `\` need to be escaped with a `\`. Ie: `\.`,`\-`.
+
+=== Man Page Skeleton ===
+{{{
+.TH THISCOMMAND 1 ''''vendorstring''''
+.SH NAME
+thiscommand \- describe this command
+.SH SYNOPSIS
+.B "thiscommand"
+.RB [ -help ]
+.SH DESCRIPTION
+Here we describe what
+.I thiscommand
+does.
+.PP
+.SH OPTIONS
+The following options are supported:
+.TP
+.B \-h
+Help.
+.SH FILES
+.SH KNOWN BUGS
+.SH "SEE ALSO"
+OTHERCOMMAND(1)
+}}}
+
+One may add additional commands between *DESCRIPTION* and *FILES* section as fit.
+
+=== Conditional Text ===
+Just like C code is conditionally included using #ifdef, manual page text can be conditionally included as well.
+Use ''.if'' to test a variable and place the text between ''.ig'' and '..'.
+
+{{{
+.if !'x.VARNAME'x.' .ig
+If $(VARNAME) is empty, this text is shown
+..
+}}}
+
+{{{
+.if 'VARNAME'' .ig
+If $(VARNAME) is empty, this text is skipped
+..
+}}}
+
+== Current Module Documents (June 2011) ==
+
+This table summarizes modules with User's documentation, Developer's documentation or functional specifications in DocBook/XML format. The DocBook/XML input format is converted to HTML, PDF, PS and plain text. When installed, the documentation input source (xml) is also installed as it can be read directly by platform help delivery system such as gnome-help.
+
+||<rowbgcolor="#80FF80">Module||<:>Dir||<:>In Fmt||<:>Tool||<:>Out Fmt||<:>Inst Fmt||<:>Dist Fmt||<:>Options||
+||app/xfs||doc||xml||xmlto||txt/ps/pdf/html||not installed||xml||enable-devel-docs||
+||app/xrx||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||app/rstart TBD||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||<rowspan=2>doc/xorg-docs||general||<rowspan=2>xml||<rowspan=2>xmlto||<rowspan=2>txt/ps/pdf/html||<rowspan=2>txt/ps/pdf/html/xml||<rowspan=2>xml||enable-docs||
+||specs||enable-specs||
+||<rowspan=2>lib/libICE||doc||<rowspan=2>xml||<rowspan=2>xmlto||<rowspan=2>txt/ps/pdf/html||<rowspan=2>txt/ps/pdf/html/xml||<rowspan=2>xml||enable-docs||
+||specs||enable-specs||
+||lib/libSM||doc||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-docs||
+||lib/libX11||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||lib/libXaw||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||lib/libXdmcp||doc||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-docs||
+||lib/libXext||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||lib/libXfont||doc||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-devel-docs||
+||<rowspan=2>lib/libXi||doc||<rowspan=2>xml||<rowspan=2>xmlto||<rowspan=2>txt/ps/pdf/html||<rowspan=2>txt/ps/pdf/html/xml||<rowspan=2>xml||enable-docs||
+||specs||enable-specs||
+||lib/libXmu||doc||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-docs||
+||lib/libXt TBD||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||lib/libxtrans||doc||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-docs||
+||lib/libXtst||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/bigreqsproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/fontsproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/inputproto||specs||txt||asciidoc||txt/html||txt/html||txt||enable-specs||
+||proto/kbproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/recordproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/scrnsaverproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/x11proto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/xcmiscproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||proto/xextproto||specs||xml||xmlto||txt/ps/pdf/html||txt/ps/pdf/html/xml||xml||enable-specs||
+||xserver/doc||xml||xml||xmlto||txt/pdf/html||not installed||xml||enable-devel-docs||
+||xserver/doc||dtrace||xml||xmlto||txt/pdf/html||installed||xml||enable-docs||
+||xserver/hw/dmx||doc||xml||xmlto||txt/pdf/html||not installed||xml||enable-devel-docs||
+||xserver/hw/xfree86||doc||xml||xmlto||txt/pdf/html||not installed||xml||enable-devel-docs||
+
+This table summarizes modules with ''man pages'' that are not hand written in the ''troff'' format. The input format may be DocBook/XML or asciidoc. The generated man pages files are included in the tarball.
+
+||<rowbgcolor="#80FF80">Module||<:>Dir||<:>In Fmt||<:>Tool||<:>Mid Fmt||<:>Tool||<:>Out Fmt||<:>Inst Fmt||<:>Dist Fmt||
+||lib/libXcomposite||man||xml||N/A ||N/A ||xmlto||troff||troff||xml+'''troff'''||
+||lib/libXi||man||txt||asciidoc||xml||xmlto||troff||troff||txt+'''troff'''||
+||lib/libXtst||man||xml||N/A||N/A||xmlto||troff||troff||xml+'''troff'''||
+
+This table summarizes modules with API Developer's documentation generated from Doxygen format using DocBook/XML as intermediate format. The source for the generated HTML files is the C code which is already included in the tarball.
+
+||<rowbgcolor="#80FF80">Module||<:>Dir||<:>In Fmt||<:>Tool||<:>Mid Fmt||<:>Tool||<:>Out Fmt||<:>Inst Fmt||<:>Options||
+||xserver/hw/dmx||doc||*.[hc]||doxygen||xml||xmlto||html||not installed||enable-devel-docs||
+
+ In Fnt:: the original source format stored in git (xml refers to docbook xml)
+ Mid Fmt:: an intermediate format that is sometimes distributed in the tarball with the original source format
+ Out Fmt:: the final format generated by the named tool
+ Inst Fmt:: the formats in which the documents are installed in $docdir
+ Dist Fmt:: the formats in which documents are included in the tarball. May contain generated formats (shown in bold)
+ Options:: the name of the (./configure --help) option used to control the generation of documents
+ Default:: the default value of the configure option if none is supplied
+=== Documentation Tooling ===
+A number of tools are required to generate the documentation. They are not all available on all platforms, and if they are, not always at a recent enough level. It is already common practice to skip the generation process if a tool is missing. In addition, some platforms have asked for a configure option to turn any tool off. This prevents breaking the build when the level of the tool is known to be too old.
+
+A number of macros have been written in the util-macros package which provide such facility. When used consistently, it makes controlling the documentation build process easier. Some macros can be invoked with a desired minimum version. The documentation will not be generated if the installed tool does not meet this request. Consult util/macros/xorg-macros.m4.
+
+{{{
+XORG_WITH_XMLTO --with-xmlto
+XORG_WITH_ASCIIDOC --with-asciidoc
+XORG_WITH_DOXYGEN --with-doxygen
+XORG_WITH_FOP --with-fop
+XORG_WITH_XSLTPROC --with-xsltproc
+XORG_CHECK_SGML_DOCTOOLS
+}}}
+
+=== Installing and Distributing ===
+In the simpler scenario, when a document is generated in it's output format, say pdf, it is installed in a location known by it's makefile variable $docdir. This is done by the makefile target {{{install}}}.
+
+Distributing refers to the creation of a compressed archive file (tarball) containing all the package source suitable to be independently built by a third party. These are published on the X.Org web site. It must contain the documentation input format, so the output can be regenerated and installed on the target computer.
+
+=== Generated files in the tarball ===
+As discussed above, some platforms do not have all the documentation tools to generate the documents from a tarball. This prevents them from installing the documents to the target computer. To solve this issue, generated files have been added in the tarball, either in the final output format or in a format for which tools are known to be available on all platforms.
+
+The makefiles have to tweak the targets to take the availability of the tools into consideration. This is where the macros are useful in providing the necessary makefile variables. It is understood that platforms lacking documentation tools will not be able to create a tarball for distribution, as it would be missing the generated files.
+
+==== Directory structure ====
+The wiki [[NewModuleGuidelines|New Module Guidelines]] describes the directory structure for each module. It generally states that man pages are to be in the {{{man}}} directory and that documents of any kind go in the {{{doc}}} directory.
+There are a number of modules where documents and man pages are in the same directory. Sometimes {{{man}}} is under {{{doc}}}, sometimes {{{doc}}} is named {{{spec}}} or {{{specs}}}. The guidelines should be followed. When multiple documents are to be generated, subdirectories can be used as appropriate.
diff --git a/Development/Documentation/XServerStableBranchManagement.mdwn b/Development/Documentation/XServerStableBranchManagement.mdwn new file mode 100644 index 00000000..f4690dcc --- /dev/null +++ b/Development/Documentation/XServerStableBranchManagement.mdwn @@ -0,0 +1,58 @@ + +This page describes the process used by stable branch maintainers for the [[XServer|XServer]]. + + +## A note to Maintainers + +DONT PANIC! + +As maintainer, you get to decide the schedule of the stable branch series as well as what patches you will accept in the tree. We ask that once you decide on a schedule for the next release, you stick to that schedule (within a reasonable margin). Sometimes things get in the way though. If there is a need for changing the schedule announce it so others are aware of the change. Of course, the further ahead this can be announced the better. An email along the lines of "the 1.x.y+1 release will follow a 8 week release schedule" is perfect. + +Either way, the point of a stable branch is to provide stable fixes. Any scheduling issues are less important. + + +## Patches for the stable branches + +A patch **must** be on the master branch unless the specific issue is either diverged too much from master or only occurs on the stable branch to begin with. If the master branch suffers from the same bug but a different patch is required (due to differences to the stable branch), the bugfix must be on master first. This allows us to detect potential side-effects from fixing a bug. + +Getting a patch onto the stable branch is largely the job of the developers, but they usually need a bit of prodding. As branch maintainer, don't shy away from asking people to send you pull requests or clarify if a specific patch proposed for master is suitable for stable. + + +## git commands + +Creation of the stable branch (only needed once) should be done based on the released tag +[[!format txt """ + git checkout xorg-server-1.13 + git checkout -b server-1.13-branch + git push origin server-1.13-branch +"""]] +The stable branch is now visible on the remote. + +Patches can be cherry-picked onto the branch from master. Always use -x to record the original commit +[[!format txt """ + git cherry-pick -x 1234deadbeef +"""]] +And once the branch is ready to push +[[!format txt """ + git push origin server-1.13-branch +"""]] +Alternatively, in the case of a pull request simply run git pull on the remote (with the branch name) +[[!format txt """ + git pull git://people.freedesktop.org/~jbond/xserver.git server-1.13-fixes +"""]] +Before pushing, the maintainer should ensure that the tree builds and performs adequate on their machine. + + +## Releasing a stable branch update + +See the [[ReleaseHOWTO|Development/Documentation/ReleaseHOWTO]] for instructions on how to invoke the release script. To make releases, the maintainer must have a gpg key to sign tags and announce emails. + +Each release has a version number and a git tag named after the module. The version number is set in configure.ac, the module name (and thus git tag prefix) for the [[XServer|XServer]] is _xorg-server_. + +The patchlevel version increases once with each stable release, release candidates for future stable releases use a trailing 901, 902, etc. Example tag names for the 1.13 stable branch series +[[!format txt """ + xorg-server-1.13.0 # stable release + xorg-server-1.13.0.901 # 1.13.1RC1 + xorg-server-1.13.0.902 # 1.13.1RC1 + xorg-server-1.13.1 # 1.13.1 stable update +"""]]
\ No newline at end of file diff --git a/Development/Documentation/XorgInputHOWTO.mdwn b/Development/Documentation/XorgInputHOWTO.mdwn new file mode 100644 index 00000000..591fecfe --- /dev/null +++ b/Development/Documentation/XorgInputHOWTO.mdwn @@ -0,0 +1,481 @@ + + +## X Input Driver HOWTO + +This is a tutorial to write a new input driver for X. Knowledge of C is a prerequisite, experience with X server development is handy but not required. + +If you're planning to invent a new device, you will most likely also need a matching driver for the linux kernel. This is not covered in this tutorial. Note that if you think about writing a new input driver for a "common" device (e.g. touchscreen, mouse, keyboard, etc.), please don't. Time is much better spent writing a kernel driver instead, and then your device will be picked up automatically. This tutorial is for those seeking to understand input drivers, or having special devices that cannot be used through the kernel's evdev interface. + +This tutorial will explain the "random" driver for a pointing device that feeds from /dev/random. This driver will be useless. It's job is to introduce you to the way how drivers are written, not to provide an actual driver for your device. All this driver will do is randomly move the cursor along the x axis. + +The full source is available from [[git://people.freedesktop.org/~whot/xf86-input-random|http://cgit.freedesktop.org/~whot/xf86-input-random]]. The X server and most of the drivers are kept in git. It is a good idea to familiarise yourself with git when you start developing a new driver. It is recommended that you put your own driver into a git repository, especially if you want to bundle it with the X server distributions. + + +#### Origin + +This document was originally written by Peter Hutterer to have a tutorial that'll teach him how to write an input driver. + +This tutorial is heavily influenced by the evdev codebase, written by Zephania E. Hull and Kristian Hogsberg. + + +#### Amendments + +* 2009-10-26: Use xf86SetStrOption instead of xf86CheckStrOption, update link to git repo (even if repo is MIA right now) + + +### The Directory Setup + +The naming convention for input drivers is xf86-input-devicename. We set the directory up, and provide the minimum amount of files. Our initial directory tree should look like this: + + +[[!format txt """ +xf86-input-random/COPYING + Makefile.am + configure.ac + autogen.sh + man/Makefile.am + man/random.man + src/Makefile.am + src/random.h + src/random.c +"""]] +We don't want to write the automake files from scratch, so we copy them from some other driver, and replace all occurances of the other driver's name with our name. The evdev driver would be a good source for this, as it is very actively maintained. + +If you are compiling input drivers without the full X source tree, instead using your distribution's development libraries, you may need to install the xorg-util-macros to get the automake scripts to work properly. These macros provide the DRIVER_MAN_SUFFIX variable and the PACKAGE_VERSION_* variables amongst others. + +Our source files random.h and random.c will become our driver implementation. The random.man should be your man file. Writing the man page is not covered in this tutorial. + +By the way, now's a good time to init your git repository. + + +### Some basic knowledge + +An X driver has to handle three different entities: modules, drivers and devices. A module is a container for multiple drivers (In fact, our xf86-input-random is actually not a driver, but a module). The driver is responsible for setting up a device. Which driver is picked, depends on the configuration of your X server. Once a device is set up, it is responsible for posting events up to the server. + +In other terms: A module is loaded once. A driver is loaded each time a section in the xorg.conf refers to it. A device is created when the driver is loading. The rest is the device's problem. + +Now let's get down to hacking. + + +### Module information + +Our module needs to provide some basic information to the X server. This information is in the XF86ModuleData (xf86Module.h). + + +[[!format txt """ +typedef pointer (*ModuleSetupProc)(pointer, pointer, int *, int *); +typedef void (*ModuleTearDownProc)(pointer); + +typedef struct { + XF86ModuleVersionInfo * vers; + ModuleSetupProc setup; + ModuleTearDownProc teardown; +} XF86ModuleData; +"""]] +The first field of the struct is the module's version info. I won't go into details explaining it, just copy it from some driver and replace the name. Be reminded that this information has to be available before any of your module's functions are called, so put it as a global static into your file. + +The [[ModuleSetupProc|ModuleSetupProc]] is called when the module is loaded. Any module-specific data initialisation needs to go in here. + +The [[ModuleTearDownProc|ModuleTearDownProc]] will be called when our module is unloaded. Anything ever allocated by our module needs to be freed here. + +With this information, we can write our first few lines of code. (Copyright headers and #includes are skipped for brevity. Please refer to the full source code.) + + +[[!format txt """ +static XF86ModuleVersionInfo RandomVersionRec = +{ + "random", + MODULEVENDORSTRING, + MODINFOSTRING1, + MODINFOSTRING2, + XORG_VERSION_CURRENT, + PACKAGE_VERSION_MAJOR, PACKAGE_VERSION_MINOR, + PACKAGE_VERSION_PATCHLEVEL, + ABI_CLASS_XINPUT, + ABI_XINPUT_VERSION, + MOD_CLASS_XINPUT, + {0, 0, 0, 0} +}; + +_X_EXPORT XF86ModuleData randomModuleData = +{ + &RandomVersionRec, + RandomPlug, + RandomUnplug +}; + +static void +RandomUnplug(pointer p) +{ +} + +static pointer +RandomPlug(pointer module, + pointer options, + int *errmaj, + int *errmin) +{ + xf86AddInputDriver(&RANDOM, module, 0); + return module; +} +"""]] +All the defines in the [[VersionInfo|VersionInfo]] will be replaced by our automake build scripts. + + +### Driver information + +In the previous listing you can see the call to _xf86AddInputDriver()_. This call tells X information about a new available driver. As said before, a module may contain multiple drivers. + +The RANDOM variable we refer simply contains the information we to initialize our driver. Its of type [[InputDriverRec|InputDriverRec]]. + + +[[!format txt """ +typedef struct _InputDriverRec { + int driverVersion; + char * driverName; + void (*Identify)(int flags); + struct _LocalDeviceRec *(*PreInit)(struct _InputDriverRec *drv, + IDevPtr dev, int flags); + void (*UnInit)(struct _InputDriverRec *drv, + struct _LocalDeviceRec *pInfo, + int flags); + pointer module; + int refCount; +} InputDriverRec, *InputDriverPtr; +"""]] +Some of the fields here are important, others aren't quite as important. Identify is never called for input drivers anyway, so none of the X.org input drivers use it. All drivers use a driverVersion of 1. + +Other fields are more important. driverName needs to be substituted with our driver's name. This doesn't have to be the same name as the module. The driver name is what you will need to refer to it in the Section "[[InputDevice|InputDevice]]" in your xorg.conf. [[PreInit|PreInit]] will be called when your device has been added to the server. It will be called once per device and allows you to initialize internal structs you need for your driver to function correctly. [[UnInit|UnInit]] will be called when your device is removed from the server. Clean up your mess here. + +module and refCount are used by the server. Don't touch them. + +For our driver, the code looks like this: + + +[[!format txt """ +static InputInfoPtr +RandomPreInit(InputDriverPtr drv, + IDevPtr dev, + int flags) +{ + return NULL; +} + +static void +RandomUnInit(InputDriverPtr drv, + InputInfoPtr pInfo, + int flags) +{ +} + +_X_EXPORT InputDriverRec RANDOM = { + 1, + "random", + NULL, + RandomPreInit, + RandomUnInit, + NULL, + 0 +}; +"""]] +With all this code in place we already have a driver that compiles and can be loaded up. However, it won't do anything, except wasting a few CPU cycles. And it's not particularly good at that either. + + +### Initialising a new device + +In this section we'll discuss what should happen in the [[PreInit|PreInit]] and [[UnInit|UnInit]]. + +[[PreInit|PreInit]] is called when a new device is added to the server. This can happen at server startup (the device has an entry in the config file) or during runtime (hotplugged). For us as driver developers this doesn't really matter. Note that [[PreInit|PreInit]] will be called for each device using our driver! + +What the [[PreInit|PreInit]] should do: + + * an [[InputInfoRec|InputInfoRec]] needs to be allocated. This struct will contain important information about our device. + * configuration options need to be parsed + * the device should be tested for availability and accessability. + * internal data needs to be initialised, if the driver needs to. +I'll just throw some code at you: +[[!format txt """ +static InputInfoPtr RandomPreInit(InputDriverPtr drv, + IDevPtr dev, + int flags) +{ + InputInfoPtr pInfo; + RandomDevicePtr pRandom; + + if (!(pInfo = xf86AllocateInput(drv, 0))) + return NULL; + + pRandom = xcalloc(1, sizeof(RandomDeviceRec)); + if (!pRandom) { + pInfo->private = NULL; + xf86DeleteInput(pInfo, 0); + return NULL; + } + + pInfo->private = pRandom; + +"""]] +First we let the server allocate information, then we allocate a [[RandomDeviceRec|RandomDeviceRec]] for our own information and attach it to the device's private field. The [[RandomDeviceRec|RandomDeviceRec]] (look at the source) is just the struct we need to store device-internal stuff for our driver. Our driver is so simple, it won't contain much. The more complicated your driver is, the more you will have to store in this private struct. + +If an error occurs, [[PreInit|PreInit]] should clean up and return NULL. + + +[[!format txt """ + pInfo->name = xstrdup(dev->identifier); + pInfo->flags = 0; + pInfo->type_name = XI_MOUSE; /* see XI.h */ + pInfo->conf_idev = dev; + pInfo->read_input = RandomReadInput; /* new data avl */ + pInfo->switch_mode = NULL; /* toggle absolute/relative mode */ + pInfo->device_control = RandomControl; /* enable/disable dev */ +"""]] +Important for us are + + * read_input: will be called when new data is available. + * switch_mode: will be called when a client requests to switch between absolute and relative mode of a device. (Not applicable for our random device). + * device_control: will be called when the device is switched on or off. +Now we need to process some options. +[[!format txt """ + /* process driver specific options */ + pRandom->device = xf86SetStrOption(dev->commonOptions, + "Device", + "/dev/random"); + + xf86Msg(X_INFO, "%s: Using device %s.\n", pInfo->name, pRandom->device); + + /* process generic options */ + xf86CollectInputOptions(pInfo, NULL, NULL); + xf86ProcessCommonOptions(pInfo, pInfo->options); +"""]] +So first we check for a driver-specific options. If the "Device" option is set, we extract it (if not, we use the default provided). The same interface is available to get other data types. xf86Set{Int|Real|Str|Bool}Option(), returns us the value we need (with an optional default provided). Using xf86SetStrOption marks the option as used and also prints it to the log file. + +After we're done processing our special options, we just tell the server to process all generic options (e.g. "[[SendCoreEvents|SendCoreEvents]]"). + +Now we should test if the device is available and accessible. + + +[[!format txt """ + /* Open sockets, init device files, etc. */ + SYSCALL(pInfo->fd = open(pRandom->device, O_RDWR | O_NONBLOCK)); + if (pInfo->fd == -1) + { + xf86Msg(X_ERROR, "%s: failed to open %s.", + pInfo->name, pRandom->device); + pInfo->private = NULL; + xfree(pRandom); + xf86DeleteInput(pInfo, 0); + return NULL; + } + + /* do more funky stuff */ + + close(pInfo->fd); + pInfo->fd = -1; +"""]] +We use SYSCALL to make sure our call isn't interrupted. Once the device is open, you may want to do some additional funky stuff (have a look at evdev) to get information from the device. Finally we close the file again, after all it was just a test to see if it's there. + +Let's set some flags and finish up. Note that if we don't set the XI86_CONFIGURED flag, the server thinks something failed and will clean up our device. +[[!format txt """ + pInfo->flags |= XI86_OPEN_ON_INIT; + pInfo->flags |= XI86_CONFIGURED; + + return pInfo; +} +"""]] +The [[UnInit|UnInit]] is not overly exciting and doesn't need further explanation. + + +[[!format txt """ +static void RandomUnInit(InputDriverPtr drv, + InputInfoPtr pInfo, + int flags) +{ + RandomDevicePtr pRandom = pInfo->private; + + if (pRandom->device) + { + xfree(pRandom->device); + pRandom->device = NULL; + } + + xfree(pRandom); + xf86DeleteInput(pInfo, 0); +} +"""]] +Recap: we now have a driver that initialises and tests for our device on startup. + + +### Starting and stopping our device + +Key to using our device is starting and stopping it when necessary. If your driver does not do this, it may cause havoc when your device is hotplugged or removed at runtime. + +The device_control field in the [[InputInfoRec|InputInfoRec]] is used to notify a device about state changes. It takes two arguments, the first being the device, the second being what the device should do (one out of DEVICE_INIT, DEVICE_ON, DEVICE_OFF, DEVICE_CLOSE). + +Again, here's some code. + + +[[!format txt """ +static int RandomControl(DeviceIntPtr device, + int what) +{ + InputInfoPtr pInfo = device->public.devicePrivate; + RandomDevicePtr pRandom = pInfo->private; + + switch(what) + { + case DEVICE_INIT: + _random_init_buttons(device); + _random_init_axes(device); + break; + +"""]] +DEVICE_INIT is called when the device is added to the server. The server expects the device to allocate all necessary information to figure out what type of device it is. + +Here's the code we use to init a device hardcoded to two buttons. Your device should include some option to switch the button map around, but we don't bother for it here. +[[!format txt """ +static int +_random_init_buttons(DeviceIntPtr device) +{ + InputInfoPtr pInfo = device->public.devicePrivate; + CARD8 *map; + int i; + int ret = Success; + const int num_buttons = 2; + + map = xcalloc(num_buttons, sizeof(CARD8)); + + for (i = 0; i < num_buttons; i++) + map[i] = i; + + if (!InitButtonClassDeviceStruct(device, num_buttons, map)) { + xf86Msg(X_ERROR, "%s: Failed to register buttons.\n", pInfo->name); + ret = BadAlloc; + } + + xfree(map); + return ret; +} +"""]] +And here's the code to init a device hardcoded to two axes. And we're hardcoded to Relative mode too. +[[!format txt """ +static int +_random_init_axes(DeviceIntPtr device) +{ + InputInfoPtr pInfo = device->public.devicePrivate; + int i; + const int num_axes = 2; + + if (!InitValuatorClassDeviceStruct(device, + num_axes, + GetMotionHistory, + GetMotionHistorySize(), + 0)) + return BadAlloc; + + pInfo->dev->valuator->mode = Relative; + if (!InitAbsoluteClassDeviceStruct(device)) + return BadAlloc; + + for (i = 0; i < pRandom->axes; i++) { + xf86InitValuatorAxisStruct(device, i, -1, -1, 1, 1, 1); + xf86InitValuatorDefaults(device, i); + } + + return Success; +} + +"""]] +In general, a driver does not need to act in any way with pointer acceleration. The acceleration is initialized during [[InitValuatorClassDeviceStruct|InitValuatorClassDeviceStruct]], user settings on acceleration are loaded when a driver calls xf86InitValuatorDefaults. But of course it depends on what you want, and a small API is available, as described in [[Pointer acceleration|Development/Documentation/PointerAcceleration]]. + +Back to the device control. We continue with the switch statement. + +DEVICE_ON is the signal that we should open the device now and start sending events. + + +[[!format txt """ + /* Switch device on. Establish socket, start event delivery. */ + case DEVICE_ON: + xf86Msg(X_INFO, "%s: On.\n", pInfo->name); + if (device->public.on) + break; + + SYSCALL(pInfo->fd = open(pRandom->device, O_RDONLY | O_NONBLOCK)); + if (pInfo->fd < 0) + { + xf86Msg(X_ERROR, "%s: cannot open device.\n", pInfo->name); + return BadRequest; + } + + xf86FlushInput(pInfo->fd); + xf86AddEnabledDevice(pInfo); + device->public.on = TRUE; + break; +"""]] +xf86AddEnabledDevice() will add our device's fd to the list of SIGIO handlers. When a SIGIO occurs, our read_input will get called. And of course we need to mark the device as being switched on, so the server knows we're doing our work here. + +DEVICE_OFF should close the device, DEVICE_CLOSE free whatever is left.. +[[!format txt """ + case DEVICE_OFF: + xf86Msg(X_INFO, "%s: Off.\n", pInfo->name); + if (!device->public.on) + break; + xf86RemoveEnabledDevice(pInfo); + close(pInfo->fd); + pInfo->fd = -1; + device->public.on = FALSE; + break; + case DEVICE_CLOSE: + /* free what we have to free */ + break; + } + return Success; +} +"""]] +Note that a client can cause DEVICE_ON and DEVICE_OFF to be called repeatedly. DEVICE_CLOSE however signals that the device is to be removed now and will not be switched on again. + +Well, that's basically it. All we need to do now is read data and post events. + + +### Reading Input + +We know that our read_input will be called when data is available. So that's all we need to do now. + + +[[!format txt """ +static void RandomReadInput(InputInfoPtr pInfo) +{ + char data; + + while(xf86WaitForInput(pInfo->fd, 0) > 0) + { + read(pInfo->fd, &data, 1); + + xf86PostMotionEvent(pInfo->dev, + 0, /* is_absolute */ + 0, /* first_valuator */ + 1, /* num_valuators */ + data); + } +} +"""]] +So each time we get an interrupt, we read one byte of the device and pass it on as a motion event with an attached x value. The pointer will erratically move around on the x-axis (You may need to move your other mouse around, so /dev/random will generate enough data). + +Now of course you need to do error checking, or some more sophisticated event generation. The DDX interfaces for posting events are: xf86PostMotionEvent(); xf86PostButtonEvent(); xf86PostKeyboardEvent(); xf86PostProximityEvent(); xf86PostKeyEvent(); (for key events with attached valuator values) + +You can find them in the xf86Xinput.h. + +When you're posting an event, the server takes care of creating XInput events and puts all events onto the event queue. At a later point in time, the server will take them out and process them. If you're feeding too many events in too short time, the queue might overrun and events will get lost. This is generally not a problem with input drivers, unless the server is really really busy with drawing. Building a /dev/urandom driver may flood the server though. + + +### The Big Picture + +Let's recap. We have modules. Modules can provide multiple drivers, each with their own capabilities. We have drivers. Drivers reside in modules and are responsible for setting up and talking to devices. + +We have devices. Each device should be independent of each other, and they can have different read_input/device_control/etc. procs. The device's read_input will be called when data is available. The device's device_control will be called when the device is activated/deactivated etc. + +A device needs to post events to the DDX, and from then on it's the responsibility of the server to do the right job. + + +### Final words + +That's it. You should now understand how a driver works and be able to write your own. Good luck. diff --git a/Development/Documentation/XorgVideoHOWTO.mdwn b/Development/Documentation/XorgVideoHOWTO.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/Development/Documentation/XorgVideoHOWTO.mdwn diff --git a/Development/Documentation/XserverSourceLayout.mdwn b/Development/Documentation/XserverSourceLayout.mdwn new file mode 100644 index 00000000..cd791984 --- /dev/null +++ b/Development/Documentation/XserverSourceLayout.mdwn @@ -0,0 +1,30 @@ + +# Moved from [[http://www.freedesktop.org/wiki/Software/Directories|http://www.freedesktop.org/wiki/Software/Directories]] + + + + +## Xserver Directory Layout + +_XXX: Add more directories, such as miext/ and the hw/kdrive/ subdirectories._ +[[!table header="no" class="mointable" data=""" + *Name* | *Explanation* + dix/ | The device independent parts of X, for example the code used for dispatching requests (see Dispatch() in dix/dispatch.c) and handling resources. main() is located in this directory in main.c. + doc/ | Less documentation than would be expected - contains the X server man page and an explanation of the scheduler. + fb/ | Code for doing graphical operations on framebuffer surfaces, for example blitting and compositing images. + hw/ | Hardware dependent code, driver APIs and configuration file operations. + hw/dmx/ | Distributed Multi-Head X code - well documented in hw/dmx/doc/html/index.html. + hw/kdrive/ | The [[kdrive server|http://en.wikipedia.org/wiki/KDrive]] and associated code. + hw/xfree86/ | Code associated with unix-like OSes, such as Linux or BSD. + hw/xquartz/ | Mac OS X specific code. + hw/xwin/ | Cygwin/X code, for running on Windows machines. + include/ | Xserver include files lie here. + mi/ | Machine independent code, used for things like high-level graphical operations. Makes calls down to the fb/ code through function pointers in screens, windows or gcs. + os/ | Operating system dependent code that does not control hardware, things like authentication, or processing arguments passed to the server (see Process``Command``Line() in util.c for example). + randr/ | Code for the [[RandR|Projects/XRandR]] extension. + render/ | Code for the Render extension. + Xext/ | Code for various extensions, for example Xinerama and Xv. + xtrans/ | Code for handling network connections. +"""]] + +-- Main.[[AndersCarlsson|AndersCarlsson]] - 23 Sep 2003 diff --git a/Development/Documentation/git.mdwn b/Development/Documentation/git.mdwn new file mode 100644 index 00000000..be9a7b8f --- /dev/null +++ b/Development/Documentation/git.mdwn @@ -0,0 +1,11 @@ + +General instructions on using git can be found on fd.o's [[Git pages|http://www.freedesktop.org/wiki/Infrastructure/git]]. + +For a quick getting started guide, there is the [[Everyday Git With 20 Commands Or So|http://www.kernel.org/pub/software/scm/git/docs/everyday.html]] guide from the Git homepage. For more in depth git documentation, see the resources on [[the Git community documentation page|http://git-scm.com/documentation]]. + +A quick [[guide|http://www.x.org/wiki/ModularDevelopersGuide#head-c108c1fd0be50c522e5dd12cf62814cd8d2f7234]] on how to get the complete xorg modular tree. + + +## Branches + +Instead of using a kernel-style personal repository model for long-lived branches, we favour actually using branches (e.g. mpx, input-hotplug, pci-rework, randr-1.2) within the repository. Ideally, these should not be created on a whim, as they will stick around forever once pushed. diff --git a/Development/Janitor.mdwn b/Development/Janitor.mdwn new file mode 100644 index 00000000..06b4161b --- /dev/null +++ b/Development/Janitor.mdwn @@ -0,0 +1,28 @@ + +The aim of this sub-project is to clean up Xorg tree as much as possible in the same way as it is done by the Linux Kernel Janitor project. It is also a good start for newcomers to get more familiar with Xorg development. + + +## Tasks + +It may be good to first read [[Modular Developers guide|http://wiki.x.org/wiki/ModularDevelopersGuide]] in case you still don't have a manually built xorg tree at your disposal. Here is a small list of tasks anyone is encouraged to update : + +* Check for unaudited return codes. There are places where return values for functions like xalloc() & others are not checked. (example [[https://bugs.freedesktop.org/show_bug.cgi?id=12531|https://bugs.freedesktop.org/show_bug.cgi?id=12531]]) +* Code with old C function prototype definitions should be changed. Example : (taken from xcalc.c) + +[[!format txt """ + 114 int + 115 main(argc, argv) + 116 int argc; + 117 char **argv; +"""]] + * should be changed to + +[[!format txt """ + 114 int + 115 main(int argc, char **argv) +"""]] +But be careful when you do make changes that you don't change the types of arguments of functions called from other packages/programs/modules due to different rules applied the to the two types of prototypes - see [[http://invisible-island.net/ansification/index.html|http://invisible-island.net/ansification/index.html]] for more details. + +* Fix compiler warnings : There are many compiler warnings ranging from signedness problems to unused variables waiting to be fixed. It may be helpful to note that an unused variable is not necessarily for removal (as it may just be that a proper #ifdef is missing) - it is therefore wise to check the code, and ask for approval before removing a variable! Another good thing to fix is missing function prototypes. +* See : [[bugzilla Janitor list|http://tinyurl.com/38ws2l]] +* TODO add other tasks here :-)
\ No newline at end of file diff --git a/Development/Security.mdwn b/Development/Security.mdwn new file mode 100644 index 00000000..35333abe --- /dev/null +++ b/Development/Security.mdwn @@ -0,0 +1,69 @@ + + +# Security Advisories + +This page details security issues that have been found in X.Org, and their remedies. + +Please contact [[xorg-security@lists.x.org]] to report security issues in the X.Org codebase. + + +## X.Org 7.7 + +* May 23, 2013 - Protocol handling issues in X Window System client libraries + * CVE-2013-1981..2005, CVE-2013-2062..2066: X client libraries can overflow buffers or corrupt memory in clients if servers send invalid replies +Please see [[the advisory|Development/Security/Advisory-2013-05-23]] for more information. + +* Apr 17, 2013 - vulnerability in VT-switch on Linux: + * CVE-2013-1940: Xservers receive input from hot-plugged devices when user has switched to another VT on Linux systems. The fix was included in [[xorg-server 1.13.4|http://lists.x.org/archives/xorg-announce/2013-April/002199.html]] and [[xorg-server 1.14.1|http://lists.x.org/archives/xorg-announce/2013-April/002200.html]]. Please see [[http://who-t.blogspot.com/2013/04/cve-2013-1940-vt-switched-servers.html|http://who-t.blogspot.com/2013/04/cve-2013-1940-vt-switched-servers.html]] for more information. + +## X.Org 7.6 + +* Jan 19, 2012 - vulnerability in default keyboard maps: + * CVE-2012-0064: It is possible to bypass a screen locking application when displayed on Xorg 1.11 or later by using the input grab killing keystrokes, which were enabled by default. The fix was included in [[xkeyboard-config 2.5|http://lists.x.org/archives/xorg-announce/2012-January/001797.html]] to not enable those key mappings unless requested. Please see [[http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-2012-0064.html|http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-2012-0064.html]] for more information. +* Oct 18, 2011 - 2 vulnerabilities related to X server lock files: + * CVE-2011-4028: File disclosure vulnerability: It is possible to deduce if a file exists or not by exploiting the way that Xorg creates its lock files. + * CVE-2011-4029: File permission change vulnerability: It is possible for a non-root user to set the permissions for all users on any file or directory to 444, giving unwanted read access or causing denies of service (by removing execute permission). This is caused by a race between creating the lock file and setting its access modes. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2011-October/001744.html]] for more information. Patches are available: [[CVE-2011-4028|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6ba44b91e37622ef8c146d8f2ac92d708a18ed34]] [[CVE-2011-4029|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b67581cf825940fdf52bf2e0af4330e695d724a4]] Fixes are included in [[xserver 1.11.2RC2|http://lists.x.org/archives/xorg-announce/2011-October/001747.html]] and later. +* Aug 10, 2011 - CVE-2011-2895: A specially crafted LZW compressed font file may be used by a user who can connect to the X server to overflow a buffer in the X server, possibly leading to a local privilege escalation. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2011-August/001721.html]] for more information. Patch is available: [[CVE-2011-2895|http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=d11ee5886e9d9ec610051a206b135a4cdc1e09a0]] Fix is included in [[libXfont 1.4.4|http://lists.freedesktop.org/archives/xorg-announce/2011-August/001722.html]] and later. +* Apr 5, 2011 - CVE-2011-0465: By crafting hostnames with shell escape characters, arbitrary commands can be executed in a root environment when a display manager reads in the resource database via xrdb. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2011-April/001636.html]] for more information. Patch is available: [[CVE-2011-0465|http://cgit.freedesktop.org/xorg/app/xrdb/patch/?id=1027d5df07398c1507fb1fe3a9981aa6b4bc3a56]] + +## X.Org 7.3 + +* Jun 11, 2008 - CVE-2008-1377, CVE-2008-1379, CVE-2008-2360, CVE-2008-2361, CVE-2008-2362: Several vulnerabilities have been found in the server-side code of some extensions in the X Window System. Improper validation of client-provided data can cause data corruption. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2008-June/000578.html]] for more information. Patches are available: [[CVE-2008-1377|ftp://ftp.freedesktop.org/pub/xorg/X11R7.3/patches/xorg-xserver-1.4-cve-2008-1377.diff]] [[CVE-2008-1379|ftp://ftp.freedesktop.org/pub/xorg/X11R7.3/patches/xorg-xserver-1.4-cve-2008-1379.diff]] [[CVE-2008-2360|ftp://ftp.freedesktop.org/pub/xorg/X11R7.3/patches/xorg-xserver-1.4-cve-2008-2360.diff]] [[CVE-2008-2361|ftp://ftp.freedesktop.org/pub/xorg/X11R7.3/patches/xorg-xserver-1.4-cve-2008-2361.diff]] [[CVE-2008-2362|ftp://ftp.freedesktop.org/pub/xorg/X11R7.3/patches/xorg-xserver-1.4-cve-2008-2362.diff]] +* Jan 17, 2008 - CVE-2007-5760, CVE-2007-5958, CVE-2007-6427, CVE-2007-6428, CVE-2007-6429, CVE-2008-0006: Several vulnerabilities have been identified in server code of the X window system caused by lack of proper input validation on user controlled data in various parts of the software, causing various kinds of overflows. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2008-January/000441.html]] for more information. Patches are available for [[X11R7|X11R7]].2 [[libXfont 1.2.7|http://xorg.freedesktop.org/archive/X11R7.2/patches/xorg-libXfont-1.2.7-pcf-parser.diff]] and [[xserver 1.2|http://xorg.freedesktop.org/archive/X11R7.2/patches/xorg-xserver-1.2-multiple-overflows.diff]] as well as for [[X11R7|X11R7]].3: [[libXfont 1.3.1|http://xorg.freedesktop.org/archive/X11R7.3/patches/xorg-libXfont-1.3.1-pcf-parser.diff]] and [[xserver 1.4|http://xorg.freedesktop.org/archive/X11R7.3/patches/xorg-xserver-1.4-multiple-overflows.diff]]. +* **Update** Jan 21, 2008 - The patch for the MIT-SHM vulnerability (CVE-2007-6429) introduced a regression for applications that allocate pixmaps with a less than 8 bits depth. New patches are available for [[xserver 1.2|http://xorg.freedesktop.org/archive/X11R7.2/patches/xorg-xserver-1.2-multiple-overflows-v2.diff]] and [[xserver 1.4|http://xorg.freedesktop.org/archive/X11R7.3/patches/xorg-xserver-1.4-multiple-overflows-v2.diff]]. MD5: 8e3f74c2cabddd3d629018924140e413 [[xorg-xserver-1.2-multiple-overflows-v2.diff|http://xorg.freedesktop.org/archive/X11R7.2/patches/xorg-xserver-1.2-multiple-overflows-v2.diff]] + SHA1: 38ad95d97e83861c309276a27296787e6d0d1b54 [[xorg-xserver-1.2-multiple-overflows-v2.diff|http://xorg.freedesktop.org/archive/X11R7.2/patches/xorg-xserver-1.2-multiple-overflows-v2.diff]] MD5: ded4bc31104aedada0155514a968b45f [[xorg-xserver-1.4-multiple-overflows-v2.diff|http://xorg.freedesktop.org/archive/X11R7.3/patches/xorg-xserver-1.4-multiple-overflows-v2.diff]] + SHA1: af92fd389e72a3bb59d25dbf9cbb06e827b75d7d [[xorg-xserver-1.4-multiple-overflows-v2.diff|http://xorg.freedesktop.org/archive/X11R7.3/patches/xorg-xserver-1.4-multiple-overflows-v2.diff]] +* Oct 2, 2007 - CVE-2007-4568: Multiple vulnerabilities in the X font server can lead to head corruption or overflow from a client. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2007-October/000416.html]] for more information. This is fixed in [[xfs 1.0.5|http://xorg.freedesktop.org/archive/individual/app/xfs-1.0.5.tar.bz2]]. A Patch is available for [[xfs 1.0.4|http://xorg.freedesktop.org/archive/X11R7.3/patches/xorg-xfs-1.0.4-query.diff]]. + +## X.Org 7.2 + +* April 3, 2007 - CVE-2007-1003 CVE-2007-1351 CVE-2007-1352 CVE-2007-1352: Lack of validation of parameters passed to the X server and libX11 by client application can lead to various kinds of integer overflows or stack overflows that can be used to overwrite data in the X server memory. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2007-April/000286.html]] for more information. Patches are available for [[7.2|http://xorg.freedesktop.org/archive/X11R7.2/patches]]. + +## X.Org 7.1 + +* January 9, 2007 - CVE-2006-6101 CVE-2006-6102 CVE-2006-6103: The ProcDbeGetVisualInfo(), ProcDbeSwapBuffer() and ProcRenderAddGlyphs() functions in the X server, implementing requests for the dbe and render extensions, may be used to overwrite data on the stack or in other parts of the X server's memory. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2007-January/000235.html]] for more information. Patches are available for [[6.8.2|Releases/6.8.2]], [[6.9.0|Releases/6.9]], [[7.0|Releases/7.0]] and [[7.1|Releases/7.1]]. +* September 12, 2006 - It may be possible for a user with the ability to set the X server font path, by making it point to a malicious font, to cause arbitrary code execution or denial of service on the X server. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2006-September/000128.html]] for more information. Patches are available for [[6.8.2|Releases/6.8.2]], [[6.9.0|Releases/6.9]], [[7.0|Releases/7.0]] and [[7.1|Releases/7.1]]. + +## X.Org 6.9.0/7.0 + +* June 20, 2006 - A lack of checks for setuid() failures when invoked by a privileged process (e.g., X server, xdm, xterm, if installed setuid or setgid) may cause the process to execute certain privileged operations (file access) as root while it was intended to be executed with a less privileged effective user ID, on systems where setuid() called by root can fail. This can be used by a malicious local user to overwrite files and possibly elevate privileges in some corner cases. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2006-June/000100.html]] for more information. Patches are available for [[6.8.2|Releases/6.8.2]], [[6.9.0|Releases/6.9]], [[7.0|Releases/7.0]] and [[7.1|Releases/7.1]]. +* May 2, 2006 - A security vulnerability has been found in the X.Org server as shipped with X11R6.8.x, X11R6.9.0 and X11R7.0 (xorg-server 1.0.x) -- this is [[CVE-2006-1526|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1526]]. Clients authorized to connect to the X server are able to crash it and to execute malicious code within the X server. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg/2006-May/015136.html]] for more information. Patches are available for [[6.8.2|Releases/6.8.2]], [[6.9.0|Releases/6.9]] and [[7.0|Releases/7.0]]. +* March 20, 2006 - A security vulnerability has been found in the X.Org server as shipped with X11R6.9.0 and X11R7.0 (xorg-server 1.0.0 and 1.0.1) -- this is [[CVE-2006-0745|http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0745]]. Local users were able to escalate privileges to root and cause a DoS if the Xorg server was installed setuid root (the default). Note that earlier releases are not vulnerable. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg/2006-March/013858.html]] for more information. Patches are available for [[6.9.0|Releases/6.9]] and [[7.0|Releases/7.0]]. If you are running X11R7.0, you can upgrade xorg-server to 1.0.2 or later ([[release announcement|http://lists.freedesktop.org/archives/xorg/2006-March/013993.html]]). + +## X.Org 6.8.2 + +* September 12, 2005 - Due to missing range checks for the pixel size of the pixmap subsequent pixmap read/write functions can access memory outside of the allocated pixmap by any X client that can connect to the affected X server. This way any user having access to the server can access memory that is accessible from within the X server and/or crash the server. The CVE number for these vulnerabilities is [[CAN-2005-2495|http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2495]]. A patch against [[6.8.2|Releases/6.8.2]] is available. + +## X.Org 6.8.1 + +* November 17, 2004 - X.Org was made aware of additional security vulnerability in libXpm, the X Pixmap library, which is shipped as part of the X Window System. The affected library is used in many popular application for image viewing and manipulation. The Common Vulnerabilities and Exposures (CVE) project has assigned the name [[CAN-2004-0914|http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0914]] to these issues. Patches are provided for [[6.8.0|Releases/6.8.0]] and [[6.8.1|Releases/6.8.1]]. The problem is fixed in 6.8.2 and later. + +## X.Org 6.8.0 + +* September 15, 2004 - A security vulnerability has been found in libXpm, the X pixmap library which is shipped as part of the X Window System. Please check [[here|http://ftp.x.org/pub/X11R6.8.0/patches/README.xorg-CAN-2004-0687-0688.patch]] for further information. This problem has been fixed in [[6.8.1|Releases/6.8.1]]. We also provide a patch for [[6.8.0|Releases/6.8.0]] and earlier. + +## X11R6.6 and older + +_This is not a complete listing of older security issues, just those discovered more recently_ + +* July 24, 2012 - CVE-2012-1699: A vulnerability has been found in the X11****R6 font server code in the handling of the Set****Event****Mask request in xfs which can lead to either denial of service or a leak of information from the xfs process address space. Please see [[the advisory|http://lists.freedesktop.org/archives/xorg-announce/2012-July/002040.html]] for more information. Patch is included in the advisory. Fix is included in XFree86 3.3.3 and later, and X.Org [[X11R6|X11R6]].7 and later.
\ No newline at end of file diff --git a/Development/X12.mdwn b/Development/X12.mdwn new file mode 100644 index 00000000..6f8c18c7 --- /dev/null +++ b/Development/X12.mdwn @@ -0,0 +1,294 @@ + + +# X12 + +[[!toc ]] + +X11 was defined in the middle of the 1980's. Since then, computers have changed _almost_ beyond recognition; the simple framebuffer model used by computers at the time has been replaced programmable graphics hardware that is both complex and powerful. Not only has graphics hardware changed, but the basic processing model has and continues to change; parallelism in core system design is becoming the norm, rather than a special case for 'large' systems. + +And that's just talking about desktop systems; now there are smart phones, netbooks, tablets and probably will shortly be other device types that this author can't imagine (else I'd be working on them...). + +In short, X11 was designed for a different era of computing. + + +## Requirements for the Successor to the X11 Protocol - "X12" + +This section is a discussion of the broad requirements for X12; discussion of the specific failings of X11 are addressed in later sections. + +To call this subject controversial would be an understatement; there have been and continue to be many attempts to either freeze 'X11' in time or discard it completely. Clearly, this author believes this to be wrong. + + +### What is Good about X11 + +Network transparency. Network transparency rocks! Run a program on a remote system and interact with it on your local terminal; write a program an not **need** to care whether it's going to be run on a full workstation or a dumb terminal. Some may say this is unimportant, but when one looks at the development of Windows and the evolution of RDP, it starts to look a lot more like X in terms of its features. + + +### A Rough List of Requirements + + +#### Security designed-in from the start + +Systems need to be secure. X12 needs to be designed with security in mind. + + +#### Multiple Platform Support + +X12 should be designed with mobile phones, tablets, dumb terminals, netbooks and desktop workstations in mind; if it is to succeed, it must work well on all these systems. + + +#### Maintain Network Transparency + +The future will be more interconnected and network-oriented, not less. Network transparency makes things easier for users and can't be considered an 'optional extra'. + + +#### Support Modern Graphics Hardware and Rendering + +Programmable hardware, composition; all that good stuff. X12 needs to naturally support modern hardware in a way that allows developers to gain access to the hardware without having to completely bypass X (as happens currently). + + +#### The Framebuffer is dead, Long Live the Framebuffer + +For all the talk of modern hardware, let's not forget that the framebuffer concept is still extremely useful in certain situations; killing it off completely is likely to be serious mistake. + + +#### Be as Efficient as Possible + +X has always been a low-level protocol; inefficiencies here will hurt applications. + + +#### Think Parallel + +This is perhaps the hardest part of the design of X12; the approach to computation and rendering is changing with a greater emphasis parallelism. X12 should be sympathetic to being implemented on massively-parallel systems, if not actively support such systems. + +On the other-hand, trying _too_ hard in this regard is likely to be serious cause of difficulties in finalising the design of the protocol; if in doubt, the designers should work to the standards of the day, rather than attempting to predict the future. + + +## Errors, Oversights and Omissions + +This section attempts to document the failings of the X protocol and rendering model. Learn from history, or be doomed to repeat it. + +This is not to say that there's an X12 project. There isn't. But if one day there is... + + +### Object model + + +#### Windows can not be zero-sized + + +#### Color maps are non-obvious + + +#### Grabs can block too much + +Popping up a menu and walking away can leave your screenlock unable to lock the screen since it won't be able to grab the pointer. + +Server grabs are even worse when they lock out all other clients including those necessary for user interaction like compositing managers and accessibility helpers. + +Current theory: Multiple clients can grab; when any grabs are active, only clients with grabs receive events. + + +#### Windows and Pixmaps aren't split correctly + +You can't resize a pixmap in the X11 protocol, because you can't get events on things that aren't windows. Lame. Really a Window should only be an IPC name, with one or more associated pixmaps and etc. + + +#### Fine grained events + +[[PropertyNotify|PropertyNotify]] is a disaster. And we probably want to be able to get events on things other than Windows. + + +#### Infeasible to change color depth with clients running + +Possibly not worth fixing. However, composited by default might make it reasonable. + + +### Rendering model + + +#### Composited by default + +Probably. Note that we can more or less accomplish this within X11, but there are probably simplifications to be had by making this explicit in the protocol. + + +#### No override-redirect + + +#### Core rendering is largely useless + + +#### Wide lines bite + + +#### BackgroundNone makes security geeks cry + +See [[EamonWalsh|EamonWalsh]]'s talk from [[XDevConf 2008|http://wiki.x.org/wiki/Events/XDC2008/Notes]]. + + +#### Borders are stupid + +Which is really a special case of... + + +#### Implicit rendering is stupid + +Borders and window backgrounds and the bg=None trick and backing store and saveunders and all that. + +There's a speed/complexity tradeoff here, of course. Any time that implicit server rendering works, it saves you exposures and round trips. But the implicit mechanisms we have are poor fits for a composited model. Think very carefully about adding implicit rendering to the server process; it's probably a mistake. + + +### Encoding bugs + + +#### Extension space is too small + +The first 128 requests are core protocol; the remaining 128 are single-entry multiplex functions for extensions. It's sort of ridiculous to have XPolyFillArc on the same footing as GLX. + +The minor opcode "convention" should be formalized and made part of the standard. The core protocol should be assigned major number zero and use minor numbers. + + +#### XIDs are too small + +XIDs are 29 bits for some inexplicable lisp-related reason. Client-side allocation seems like a reasonable idea for avoiding round-trips, but the need to slice the 29-bit space into client and resource parts means we have an unpleasant tradeoff. Right now most X servers have a 256 client limit, which is uncomfortably close. + +Should probably just bump this to uint32 for client ID and uint32 for resource ID. + + +#### Sequence numbers are too small + +It's pretty easy to hit 16-bit sequence number wrap without getting any responses from the server, which can make interpreting later events or errors impossible. Although perhaps it would be better to introduce a [[SequenceWrap|SequenceWrap]] event sent every 64k requests than to grow the sequence numbers. + + +#### 15 bit coordinate limit + +Ouch. 32768 pixels at 100dpi is 8.3 meters. + + +#### 64 bit, nanosecond-precision timestamps + +585 years ftw. The server time should be included in every event, reply, and error. It should also be present in every request (but with the "[[CurrentTime|CurrentTime]]" option available). + + +#### Cursor image encoding + +Cursors are encoded as rectangular bitmaps, so a full-screen crosshairs would be a bitmap 4 times the size of the screen. Allowing a more flexible format, such as SVG, would be good, as well as allowing smoother scaling for screen magnifiers. + + +#### ListFontsWithInfo-style requests with multiple replies + +Kill them or standardize them, preferably the former. Note that XCB-style asynchronous requests with replies make some uses of these less important. + + +#### The KeymapNotify event special-case should go away + +All events provide a sequence number, except for the [[KeymapNotify|KeymapNotify]] event which wants the space for more data. + + +#### XGE by default + +Events and errors are a fixed packet size to make parsing easy, but they aren't big enough to convey all the information you want. Some extensions like Xinput literally use every byte, and then some. The X Generic Events (XGE) extension adds a mechanism for larger events. + +XGE should become the default, rather than fixed-size events. + + +#### CHAR2B + +Kill this off. It's only used for core text, which should die. + + +#### Responses should assume less client state + +Replies, and probably errors, should include the major and minor opcode of the request that triggered them, to ease debugging. + + +#### Latin-1 (ISO 8859-1) + +Strings for Atom names and the like are required to be in Latin-1 encoding - should be replaced with UTF-8. + + +#### Length fields require constant conversion + +All requests and replies in X11 have a length field. This is cleverly encoded as number of 32-bit words, since all packets are padded to 32-bit alignment. This annoyingly results in tons of << 2 and >> 2 conversions everywhere to get into useful byte counts for reading & writing across the sockets. + + +### Input + + +#### Core input is useless + +Xi and (at least some elements of) XKB need to be folded in to the core protocol and made mandatory. + + +#### Resource limits + +We need more than 255 keycodes, and more than 4 groups. We also need a better mechanism for expressing state than the current field, which limits us to 5 buttons and 4 modifiers, or so. + + +#### Redirection should be integrated + +The current deep binding of input delivery to window coordinates is garbage. The redirection mesh idea is nice but it should be the only way. + + +#### Keysym names are a mess + +Come up with a vastly more coherent set of keysym names than the current scattergun approach. + + +### Design issues + + +#### Circulation APIs in core protocol are emacs disease + +These are wildly unhelpful. [[CirculateWindow|CirculateWindow]] and [[RotateProperties|RotateProperties]] can taste the curb. + + +#### Screens are not helpful + +(Screens is used in the protocol sense, with displays used in the physical output device sense.) + +This is part intractably large implementation problem (of not allowing resource sharing among screens, nor screen hotplugging), and part protocol problem (screens as defined are static, and there's no expressed relationships). Pushing most of RandR down will help this, as well as rewriting core code. + + +#### Events should always go to a window + +Events should have a fixed destination window field, to support the idea of events delivered to windows, not to clients directly. + + +#### Move stuff from the "random fixes" extensions into core + +Decide what from XC-Misc, MIT-SUNDRY, XFree86-Misc, and XFixes needs to go in core. + + +#### Don't split or duplicate a class of requests across core and extensions + +For instance, the core [[ForceScreenSaver|ForceScreenSaver]] and the MIT-SCREEN-SAVER extension. + + +#### Predefined atoms + +ICCCM gets special pre-defined atoms, but newer standards like EWMH don't. One approach would be to identify a set of predefined atoms by the hash of the names of the atoms, allowing extensibility in which atoms to predefine in the future. The connection setup response could include a list of the atom-sets this server provides, eliminating a round-trip at startup in the common case that all the atoms a client wants are already known. + + +#### Extension initialization + +With XCB we can, in principle, initialize all the extensions a client needs in two round-trips. But there aren't so many extensions in a server that we couldn't just provide the list in the connection setup reply. If that list included all the data that [[QueryExtension|QueryExtension]] returns, that would eliminate one round-trip. If we standardize that every extension has a major and minor version number, and include those in the setup data as well, we can eliminate the other round-trip. + + +### Race Conditions + + +#### Need a basic sync request + +Need a dedicated request that just sends back an empty reply. + + +#### Implement the ICCCM suggestions + +An appendix to the ICCCM lists mostly trivial improvements that would simplify the procedures set forth in that document. + + +## Reference material + +* [[Why X Is Not Our Ideal Window System|http://www.std.org/~msm/common/protocol.pdf]] +* [[Window System Design: If I had it to do over again in 2002|http://hack.org/mc/texts/gosling-wsd.pdf]] +etc. diff --git a/Development/Xv2.mdwn b/Development/Xv2.mdwn new file mode 100644 index 00000000..5d2b1531 --- /dev/null +++ b/Development/Xv2.mdwn @@ -0,0 +1,140 @@ + + +# Xv2 + +Xv2 is a hypothetical family of two updates to support video displaying that isn't Xv. + +* Render: Allow dest-only pictures, add YUV formats +* Randr: Add overlay objects beside CRTCs: enable, disable, property mangling, mandatory formats supported and acceptable CRTC mask properties, as well as a 'current backing Picture' property. +Drivers wrap Render context creation and set ShmPutImage/Composite to their former Xv paths. Port properties become Randr overlay properties. + + +## Rambling IRC braindump + +I should clean this up and summarise, but right now it's here for posterity. Also encompasses server development, future driver API, and future render API discussions. + + +[[!format txt """ +< ajax> exa is giving me vertigo +< daniels> maybe if we do fold the drivers into the server to start smashing up the api, people won't notice drm because it'll still be two steps. win. +* daniels draws for the epsom salts. +< ajax> i think i'm just going to smash the api and tell people to cope +< ajax> doing shatter well essentially requires breaking the ScreenRec +< daniels> ajax: i was thinking more along the lines of actually creating an api first. +< ajax> daniels: madness. +< daniels> as opposed to, y'know, what we have now. +< ajax> yeah we should have one of those, shouldn't we. +< daniels> if we say in advance that 7.6 + 2.0 are going to be this big break and that master may not always be buildable due to active development, then i think we can more than get away with it. +< ajax> i've been hoping to slowly morph towards having something sensible, but i might be losing patience +< daniels> ajax: right, but morphing from here to there essentially requires creating an api, no? +< ajax> daniels: evolving, but yeah. the advantage being that you don't have to hope you design it right up front +< ajax> which we are manifestly shit at +< ajax> HI MEMORY MANAGER HOW ARE YOU +< daniels> of course there are still renovations like the i2c api of shame, but most of it is going to be fbScreenInit + mangle masks + gamma init + picture init + randr init + create visuals list + OH GOD I DON'T CARE -> xorg_create_a_screen_for_the_love_of_god()) +< jcristau> which one? :) +< daniels> ajax: oh god no. it comes organically or it comes xkb. +< daniels> ajax: but i get the sense that a new api is mostly going to look like a new header file with a whole host of new functions which replace almost all the old functions (and then your mode + video + etc helpers) +< ajax> also, you're talking about driver api, and i'm talking about rendering api. they're related but not identical. +< daniels> yes, that also. that's not on my immediate hitlist though. +< daniels> what did you have in mind? +< daniels> (also, our input driver api is, surprisingly crap. need to fix that, and lift a raft of stuff into the dix.) +< daniels> InputDriverRec + IDrvRec + maybe DeviceIntRec if you're lucky -> OH GOD NOT THE FACE +< ajax> we still expose basically the whole gc/picture/xvctx to the driver. drivers shouldn't have to know about the protocol's semantics, we should be giving them a much smaller rendering task. +< daniels> \o/ +< daniels> exa isn't tooo bad in that sense though. +< ajax> it's better but still not good +< ajax> the Picture is a disaster of a struct +< daniels> i don't know if you know, but in x terms, that's called a celebration. +< ajax> the _one_ thing that the core rendering model got right is that the chalkboard is not the chalk +< daniels> the what isn't the what? +< ajax> the GC isn't the Drawable +< ajax> but in the Picture they're bound together +< daniels> yeah, they did get the model right there. +< daniels> heh. progress! +< daniels> hmm, i should fix up render-arg-reduction if we're breaking this api anyway, because seriously. +< daniels> gtkperf got something like 33% in some tests just from fb-internal arg reduction, not even the entire chain. +< ajax> render-argh-reduction +< daniels> (hi! my name is arm! please don't have 12 arguments for deeply-wrapped functions, because it makes me sad.) +< ajax> x86 doesn't like it either, for that matter +< ajax> we just hide it with l1 +< daniels> sure, but the overall performance penalty isn't so bad. +< daniels> right. +< daniels> plus a hojillion more cycles per second. +< ajax> so yeah. render and xv need proper contexts, and so does the Screen for getimage and possibly the implicit window rendering shit. +< ajax> which i'm considering tossing altogether and just forcing CompositeRedirectAutomatic +< ajax> (or equivalent semantics) +< ajax> i hate the window rendering rules so very hard +< daniels> meh, if you're doing that, just add YUV formats to Render and implement Xv as a wrapper for that. +< ajax> it's not clear how you keep the overlay fastpath for that +< daniels> plus, is there any reason _not_ to force automatic redirection? all the consumer-device kids are getting on compositing (including us), so that's the main argument gone ... +< ajax> depends how much memory pressure you're willing to accept, i guess +< daniels> ajax: overlay> how not? +< daniels> i guess you'd need a way to route to ports, but that gives us a one-extension xv. +< daniels> 'bind this render yuv texture to this overlay', which also lets you deassociate. that's grabport and stopvideo in one, and putimage is nothing if not composite dst. +< daniels> dberkholz: oh? +< dberkholz> on one hand, we're assuming people are running distros by defaulting to black +< daniels> s/one-extension/one-request/ +< daniels> okay, listports and port properties. blah blah i'm not listening anymore. +< daniels> or, wait. randr! aha. every gpu gets some overlays, which can have an acceptable crtc mask. so we punt the hard decisions to the client. win. +< daniels> ajax: anyway, so. render gets yuv picture support. randr gets overlays at the same level as crtcs, and behave like them (enable/disable/props), but also have acceptable crtc & format masks. you have one request to bind a picture to a port, and rendering is just composite. sound okay? +< ajax> what do you composite _to_? +< ajax> i guess have an internal picture type that means "overlay port"? +< daniels> well, you've given render a GC, so at context creation time, you set Composite to your overlay path if it's an overlay. +< ajax> heh. dest-only picture. yeah, that sounds plausible +< marcheu> the major difference between xv and yuv render is the semantics. and we need it to optimize the upload +< ajax> you just don't expose that picture type to clients through render +< daniels> you even get to use the general fb code, because dst with no mask is easy. if they want to alpha-blend on the client side, they can cop the slow path. +< ajax> marcheu: ShmPutImage not enough for you? +< ajax> daniels: i guess the one remaining bugbear is "magic encrypted content stream" as a picture format. but that should be fine, just looks like another format. +< daniels> marcheu: i don't see how it's a problem if you have shm and you get a say in ctx creation? if it's on an overlay, wrap ->ShmPutImage and ->Composite and set them to your fastpaths. +< daniels> ajax: PICT_BULLSHIT32 +< marcheu> ajax: getting the best performance is quite card-dependent +< daniels> ajax: specified as always passing through unmolested, and any attempt at manipulation fails. +< daniels> marcheu: ... and? +< daniels> marcheu: i just don't see how this is even remotely different from the Xv api. you could even make it look exactly the same if you wanted. +< marcheu> well then you have to keep the xv api, basically +< daniels> ... why? +< ajax> yeah, i was anticipating leaving Xv in place as the only thing allowed to create dest-only pictures +< marcheu> because if you keep the semantics, you might as well keep the api +< daniels> marcheu: you _can_ keep the semantics. +< ajax> (well, not the only thing, but as an api compat thing it'd be desirable to keep) +< daniels> ajax: i don't see how it's too much different from render, where you already have to pay attention to the format, with the exception of some Pictures being dest-only. i mean, the server implementation of Xv would surely be a tiny shim over render, so why do they have to be so different client-side? +< daniels> ajax: mm, you can do api compat forever by having libXv just call out to libXv2, though yeah, that doesn't solve this whole client<->server issue. +< ajax> i really can't break libXv +< ajax> though lord do i wish +< marcheu> daniels: I'm saying you have to basically keep the xv implementation driver-side anyway... +< daniels> sure, so that can just call out to the new code. nothing saying that libXv has to implement XVIDEO. +< marcheu> yeah, but that's duplication +< daniels> marcheu: true for overlays, but it probably means a lot _less_ duplication for textured video. +< ajax> daniels: there's a small "hard problem" around making sure the XV object types exist in the protocol somewhere and can be passed around between clients, just in case someone did that. +< daniels> ajax: hmm? +< ajax> daniels: it's legal to get an XvPortID from one process and use it in another and expect them to be numerically identical +< ajax> it's crack but it's an XID +< ajax> libXv backending onto this new Render hotness would need to manage that somehow. could be root window properties for all i care, but. +< daniels> atoms. +< daniels> do they share a space with xids? +< daniels> (i should know this.) +< ajax> not sure. doesn't really matter that they be legal XIDs, just that the opaque value mean the same thing in all clients. +< daniels> okay, atom of (int gpuid, int portid) +< ajax> also, as a sloth argument, it's easier to compat it in the server than both: compat on client, rewrite in server +< daniels> sure, but i'm talking new driver api + new render api, not when i'm bored next week. :) +< daniels> i mean, if your argument is that it's a crap api, sure, but if your argument's that someone needs to do it, then i'll do it because i've written an xv implementation and looked into that code. +< ajax> i'm happy to see xv backended on to render, sure. i just don't see a lot of value in moving xv api compat from the server to libXv. +< daniels> assuming that we care about the server codebase being both reasonably sized and mostly decrufted, slicing xv off can't be that bad an idea. +< daniels> and that bitrotting libraries is something no-one really cares about. +< ajax> i suppose i'm being paranoid about xv-on-the-wire mattering for someone +< ajax> but, like you said: xv compat in server would _not_ be a large chunk of code +< ajax> positing all the stuff mentioned above, it's like... thousand lines or so? most of which is protocol banging? +< daniels> sure. +< ajax> (also, anyone doing xv on the wire is already a bit barmy, seriously just do mpeg frames, it's less work for both sides) +< ajax> i buy the decrufting argument, and --disable-xv for server should still work, but unlike a lot of the other bullshit we've deleted we're starting to approach things that people actually use +< daniels> meh, anything other than YUV in requires dealing with the DSP in the X server, and no. +< daniels> ajax: yeah. +< daniels> ajax: consider me talked over. +< ajax> also when i say "on the wire" i mean "between different machines" +< ajax> if client and server are same machine, fix the damn player +< ajax> if they're not the same machine, you're using more bandwidth than you ought to be +< ajax> hopefully in N years everyone will be using gstreamer and we can fix the bottom layer of it at will +< ajax> right, so this sounds like a plan then. +< daniels> indeed. +"""]]
\ No newline at end of file diff --git a/Development/git.mdwn b/Development/git.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/Development/git.mdwn diff --git a/DisplayPort.mdwn b/DisplayPort.mdwn new file mode 100644 index 00000000..45c2469b --- /dev/null +++ b/DisplayPort.mdwn @@ -0,0 +1,37 @@ + + +## DisplayPort + +DisplayPort is a new digital output format. It has support for higher resolutions than DVI, a connector that doesn't fall out all the time like HDMI, backwards compatibility with DVI and (in principle) VGA, better power management, daisy-chained displays, partial screen updates, cheaper transcievers, and probably more things the author is forgetting. + +Support for DP in open drivers is a work in progress. This page attempts to document the current status. + +For all drivers, the ability to drive a DisplayPort sink (monitor) using a DVI source is entirely a function of the feature set of the sink. No amount of change to the driver is going to make this work for you if it doesn't already. + + +### ATI + +Prior to DCE 3.0 (RV620, RV635, RS780), the GPU does not have DisplayPort connectivity natively, only over DVO. This does not work at all yet. + +For DCE 3.0 (RV620, RV635, RS780) and later chips (RV710, RV730, RV770, etc.) using the UNIPHY transmitters, DisplayPort sources can drive DVI sinks using the radeon driver. Native DisplayPort connections work with xf86-video-ati from git master and with KMS. + + +### Intel + +The G40-series chips and later have native DisplayPort support. There is a [[branch|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/?h=display-port]] of the intel driver that attempts DP setup. It's not clear whether this branch supports DP->DVI connections, but it certainly doesn't support DP->DP connections yet. + +Prior to G40, DP support would be theoretically possible over SDVO. So far, no DP SDVO devices have been seen in the wild. + + +### NVIDIA + +On G98, DP->DVI connections work out of the box with the nouveau driver. The nv driver has not been tested yet. + +It's not clear that any earlier chips support DP. + + +### Other + +S3 makes a DisplayPort card, but there's no open driver for it at all. + +No other vendors (VIA, Matrox, etc) are known to make a DisplayPort product at this time. diff --git a/DistroFAQList.mdwn b/DistroFAQList.mdwn new file mode 100644 index 00000000..c5db573a --- /dev/null +++ b/DistroFAQList.mdwn @@ -0,0 +1,33 @@ + + +# Links to Support provided by Distribution Vendors + + +## Mailing Lists / Forums + + * [[Debian's X Mailing list|http://lists.debian.org/debian-x/]] + * [[The Ubuntu Forum Community|http://ubuntuforums.org/]] and [[Ubuntu Mailing Lists|http://www.ubuntu.com/support/community/mailinglists]] + * FreeBSD's X Mailing List: [[Subscription|http://lists.freebsd.org/mailman/listinfo/freebsd-x11]] [[Archive|http://lists.freebsd.org/pipermail/freebsd-x11/]] + * [[Gentoo's Mailing Lists|http://www.gentoo.org/main/en/lists.xml]] + * [[Mandrake's Mailing Lists|http://www.linux-mandrake.com/en/flists.php3]] + * [[OpenBSD's Mailing Lists|http://www.openbsd.org/mail.html]] + * [[OpenSolaris X Mailing List|http://mail.opensolaris.org/mailman/listinfo/xwin-discuss]] + * [[Red Hat's X Mailing list|http://www.redhat.com/mailing-lists/xfree86-list/index.html]] + * [[SuSE's X Mailing List|http://lists.suse.com/archive/opensuse-xorg/]] + +## Documentation + + * [[Debian Documentation|http://www.debian.org/doc/]] + * [[FreeBSD X Server Configuration|http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11.html]] + * [[Gentoo X Server Configuration HOWTO|http://www.gentoo.org/doc/en/xorg-config.xml]] + * [[Mandrake Documentation|http://www.linux-mandrake.com/en/fdoc.php3]] + * [[Ubuntu X Configuration|https://wiki.ubuntu.com/X/Config]] and [[Ubuntu Video Documentation|https://help.ubuntu.com/community/Video]] + +## Other + + * [[Debian X Strike Force|http://wiki.debian.org/XStrikeForce]] + * [[Gentoo X11 Herd|http://www.gentoo.org/proj/en/desktop/x/x11/]] + * [[KNOPPIX English Language Mailing Lists/Documentation|http://www.knoppix.net/]] + * [[OpenSolaris X Window System community page|http://opensolaris.org/os/community/x_win/]] + * [[Red Hat's Support Page|http://www.redhat.com/apps/support/]] + * [[Ubuntu X team|https://wiki.ubuntu.com/X]]
\ No newline at end of file diff --git a/Documentation.mdwn b/Documentation.mdwn new file mode 100644 index 00000000..539dc176 --- /dev/null +++ b/Documentation.mdwn @@ -0,0 +1,17 @@ + + +# Running X + +[[User documentation|UserDocumentation]] contains documentation for running the X server and basic X clients, as well as protocol specifications and basic client programming documentation. + + +# Developing X applications + +Rather than develop directly for X, we recommend you use a toolkit such as [[GTK+|http://www.gtk.org/documentation.php]] or [[Qt|http://doc.qt.nokia.com/latest/]]. There are many other popular toolkits, some special-purpose, such as [[Clutter|http://www.clutter-project.org]] and [[Enlightenment/EFL|http://www.enlightenment.org]]. + +For low-level X development, [[XCB|http://xcb.freedesktop.org/tutorial/]], the X C Bindings provide a clean low-level protocol binding. Its older cousin Xlib (or libX11), is not recommended for new development, but is still very widely used. Xt is a similarly deprecated library for building toolkits. [[Documentation for Xlib and Xt|ProgrammingDocumentation]] is available. + + +# Downloading, running, and developing X.Org code + +The [[development documentation|Development]] describes how to download and build the X.Org code (including the X server and drivers), and rough notes on their internals. diff --git a/EgbertEich.mdwn b/EgbertEich.mdwn new file mode 100644 index 00000000..4417d6ca --- /dev/null +++ b/EgbertEich.mdwn @@ -0,0 +1,39 @@ + + +## Egbert Eich + +Email: eich AT SPAMFREE freedesktop DOT org + + +### X.Org Board Elections + +I've been involved in the development of the X Window System since 1995. + I helped bootstrapping the X.Org Foundation. In the past two years I served on the Board of Directors of the X.Org Foundation. There I helped to ensure that the Boards focuses as an overseer on organizational issues and abstained from undue involvement in technical matters. + I was involved in drafting in our new By-Laws and Membership Agreement and I drafted the 2006 budget. + +My strong focus rests in development. As a Board Member I see my most important duty to support our community of contributors and bring its issues to the attention of the Board. + +A number of issues need to be addressed urgently: + +1. Create a Membership Committee to promptly deal with reviewing and accepting Membership applications thru an open process. +1. Establish a sponsorship program + This involves identifying funding opportunities and budget for them: + * Event Funding + * Set up travel fund program for X related events and coordinate with event organizers. + * Individual funding + * Set up Budget and policies to sponsor travel for X-related presentations + * Budget for and develop polices for sponsorship of individual contributors to attend meetings relavant to their area of contribution. + * Marketing + * Determine if and in which marketing activeties X.Org should be involved in and what their goals and intended target audiences are. From this develop a policy to fund such events. +1. Put X.Org server infrastructure fully in place: + 1. Installation of the donated machines from SUN. + 1. Identify services that can be shared with freedesktop.org. + 1. Establish a backup and mirroring system for the freedesktop.org infrastructure. + 1. Make sure that the administrational workload can be dealt with effectivly. + + +--- + + + +* [[CategoryHomepage|CategoryHomepage]]
\ No newline at end of file diff --git a/Events.mdwn b/Events.mdwn new file mode 100644 index 00000000..94811993 --- /dev/null +++ b/Events.mdwn @@ -0,0 +1,21 @@ + + +## Upcoming Events + +* [[linux.conf.au 2013|http://lca2013.linux.org.au/]], Canberra, Australia, January 28 through February 2, 2013 +* [[FOSDEM 2013|fosdem2013]], Brussels, Belgium, February 2 through 3, 2013 +* X.Org Developer's Conference: XDC2013 - TBD (Portland?) + +## Recent Events + +* [[X.Org Developer's Conference: XDC2012|Events/XDC2012]], Nuremberg, Germany, September 19 through 21, 2012 +* [[Book Sprint 2012|Events/BookSprint2012]], Nuremberg, Germany, September 17 and 18, 2012 +* [[GUADEC 2012|http://www.guadec.org/]], A Coruña, Spain, July 26 through August 1, 2012 +* [[FOSDEM 2012|fosdem2012]], Brussels, Belgium, February 4 through 5, 2012 + * [[X/Graphics Dev Room Call for Participation|http://lists.x.org/archives/xorg-devel/2011-September/025000.html]], [[Followup|http://lists.x.org/archives/xorg-devel/2011-October/025953.html]] + * [[X.Org/Wayland/OpenICC Dev Room schedule|http://fosdem.org/2012/schedule/track/xorgopenicc_devroom]] +* [[linux.conf.au 2012|http://lca2012.linux.org.au/]], Ballarat, Australia, January 16 through 20, 2012 + +## Older Events + +* Events more than a year old are [[archived|Events/History]].
\ No newline at end of file diff --git a/Events/BookSprint2012.mdwn b/Events/BookSprint2012.mdwn new file mode 100644 index 00000000..f89d7067 --- /dev/null +++ b/Events/BookSprint2012.mdwn @@ -0,0 +1,28 @@ + +**Summary**: In order to help with documentation and guides for developers, both existing and new, we will have a book sprint the two days prior to [[XDC2012|Events/XDC2012]]. + +**When**: Monday Sept 17 & Tuesday Sept 18. Opening hours will be early in the morning (TBD, 8am?) until we call it a day (but certainly no longer than 10pm). + +**Where**: [[Keßlerstraße 1|http://maps.google.de/maps?f=q&source=s_q&hl=de&authuser=0&q=Keßlerstraße+1,+90409+Nürnberg,+Bayern&aq=&vps=1&jsv=402e&sll=51.151786,10.415039&sspn=14.100269,34.936523&vpsrc=1&ie=UTF8&oi=georefine&ct=clnk&cd=2&geocode=FT2y8gIdqRupAA&split=0]]. Room 4020 (4th floor, which would be 5th floor in American way of counting), a small part of the Georg-Simon-Ohm-University, in the old "[[Postbank|http://www.postbank.com/]]". It's the building at the corner, the yellow "Postbank" sign is still widely visible. In approximately the middle of the same building there is another "Postbank", with the same sign, that is the new (wrong) one. + +**What**: Driver Developers Guide (tentative) + +**Who**: The X Book Posse + +**Details**: + +Marcheu has a very nice start on a Guide. This sprint will be to review and fill in anything missing. + +Current Guide: [[http://people.freedesktop.org/~marcheu/linuxgraphicsdrivers.pdf|http://people.freedesktop.org/~marcheu/linuxgraphicsdrivers.pdf]] + +git: [[http://cgit.freedesktop.org/~marcheu/lgd/|http://cgit.freedesktop.org/~marcheu/lgd/]] +[[!table header="no" class="mointable" data=""" +**Proposed Schedule (_**very_** rough storyboard. It's at least something):**|| +Mon 9am-noon | Review existing Guide and create TODO list (identify holes and what needs polish) +Mon noon~1pm | lunch +Mon 1pm-5pm | Fill in any holes +Tues 9am-noon | Begin polish +Tues noon-1pm | lunch +Tues 1pm-5pm | finish polish +Tues 5pm-? | beer +"""]] diff --git a/Events/History.mdwn b/Events/History.mdwn new file mode 100644 index 00000000..3a7b2196 --- /dev/null +++ b/Events/History.mdwn @@ -0,0 +1,64 @@ + +A collection of older events that X.Org has held, presented at, or had significant presence at. Move things here from the [[current events page|Events]] when they get too old, and if possible, link to what we did there. + + +### 2011 + +* [[X.Org Developers' Conference (XDC2011)|Events/XDC2011]]. Chicago, USA, September 12 through 14, 2011. +* [[Linux Plumbers Conf 2011|http://www.linuxplumbersconf.org/2011/]], Santa Rosa, California, USA, September 7 through 9, 2011 +* [[GNOME/KDE Desktop Summit|http://www.desktopsummit.org/]], Berlin, Germany, August 6 through 12, 2011 +* [[linux.conf.au 2011|http://lca2011.linux.org.au/]], Brisbane, Australia, January 24 through 29, 2011 + +### 2010 + +* [[Linux Plumber's Conference|http://events.linuxfoundation.org/events]], Cambridge, Massachusetts, USA, November 3 through 5, 2010 +* [[X.Org Developers' Summit (XDS2010)|Events/XDS2010]]. Toulouse, France, September 16 through 18, 2010. +* [[GUADEC 2010|http://www.guadec.org/index.php/guadec/2010]], The Hague, The Netherlands, July 24 through 30, 2010 +* [[Akademy 2010|http://akademy.kde.org/]], Tampere, Finland, July 3 through 10, 2010 +* [[FOSDEM 2010|fosdem2010]], Brussels, Belgium, February 6 and 7, 2010 +* [[linux.conf.au 2010|http://www.lca2010.org.nz/]], Wellington, New Zealand, January 18 through 23, 2010 + +### 2009 + +* [[VideoHackfest|http://gstreamer.freedesktop.org/wiki/VideoHackfest]], Barcelona, Spain, November 19th through 22nd, 2009 +* [[X.Org Developers' Conference 2009|Events/XDC2009]], Portland, Oregon, USA, September 28 through 30 +* [[Linux Plumber's Conference|http://linuxplumbersconf.org/2009/]]: [[X Window System track|http://linuxplumbersconf.org/ocw/events/2009/tracks/3]], Portland, Oregon, USA, September 23 through 25 +* [[Gran Canaria Desktop Summit: GUADEC & Akademy 2009|http://www.grancanariadesktopsummit.org/]], Las Palmas, Gran Canaria, July 3 through 11, 2009 +* [[FOSDEM 2009|fosdem2009]], Brussels, Belgium, February 5 through 8, 2009 +* [[linux.conf.au|http://linux.conf.au/]], Hobart, Tasmania, January 19 through 24, 2009 + +### 2008 + +* [[Gnome Boston Summit|http://live.gnome.org/Boston2008]], Cambridge, Massachusetts, October 10 through 13. +* [[X.Org Developers' Summit 2008|Events/XDS2008]], Edinburgh, Scotland, September 3 through 5. +* [[GUADEC 2008|http://2008.guadec.org/]], Istanbul, Turkey, July 7th through 12 +* [[X.Org Developers' Conference 2008|Events/XDC2008]], Mountain View, California, April 16 through 18. +* [[xorg@fosdem 2008|fosdem2008]], February 23 - 24. Brussels, Belgium. +* [[linux.conf.au|http://linux.conf.au/]], Melbourne, Australia, Jan 28 - Feb 2 + +### 2007 + +* [[Gnome Summit|http://live.gnome.org/BostonSummit]], Cambridge, Massachusetts, October 6 through 8. +* [[X.Org Developers' Summit 2007|Events/XDS2007]], Cambridge, England, September 10 through 12. +* [[GUADEC 2007|http://2007.guadec.org/]], Birmingham, England, July 15 through 21. +* [[xorg@fosdem 2007|fosdem2007]], February 24-25. Brussels, Belgium. +* [[Xorg Developer's Conference 2007|Events/XDC2007]] was held on February 7, 8, and 9 in the San Francisco Bay Area. See [[XDC2007Notes|XDC2007Notes]] for the talk transcript. + +## 2006 + +* An X.Org BOF was held at [[SIGGRAPH 2006|http://www.siggraph.org/s2006/index.php]] (August 1 through 3, 2006) in Boston. +* The [[Desktop Developers' Conference|http://lanyrd.com/2006/desktop-developers-conference/]] was held July 17 and 18, 2006, in Ottawa prior to OLS 2006. +* X.Org presented at [[LinuxTag|LinuxTag]] 2006 in Wiesbaden, Germany May 3 - 6 2006. +* X.Org had an [[X Developers HotHouse and X DevRoom|fosdem2006]] on February 24-26 at FOSDEM 2006 in Brussels, Belgium. +* [[X Developers' Conference 2006|Events/XDC2006]] was held on February 8-10 2006 at the Sun Microsystems campus in Santa Clara, CA. + +## 2005 + +* [[Desktop Developers' Conference|http://lanyrd.com/2005/desktop-developers-conference/]], July 18 and 19, 2005, Ottawa, prior to OLS 2005. +* X.Org had its first European Developers meeting in Karlsruhe, Germany from June, 19 to June, 20, right before [[LinuxTag 2005|http://www.linuxtag.org]]. (Read more at [[LinuxTagMeeting2005|LinuxTagMeeting2005]]) +* [[X Developers' Conference 2005|Events/XDC2005]], February 12 through 14, in Cambridge, Massachusetts. + +## 2004 + +* [[Desktop Developers' Conference|http://lanyrd.com/2004/desktop-developers-conference/]], July 19 and 20, 2004, Ottawa, prior to OLS 2004. +* The first X Developers' Conference (well, first for the X.Org Foundation) was April 28 through 30, 2004 in Cambridge, Massachusetts.
\ No newline at end of file diff --git a/Events/XDC2005.mdwn b/Events/XDC2005.mdwn new file mode 100644 index 00000000..9b06f0e0 --- /dev/null +++ b/Events/XDC2005.mdwn @@ -0,0 +1,143 @@ + + +## X Developer's Meeting 2005 +[[!table header="no" class="mointable" data=""" + **XDC 2005** | [[XDC 2006 >>|Events/XDC2006]] +"""]] + +We have scheduled a three day X Developer's meeting from Saturday, February 12, through Monday, February 14, at the Cambridge Research Laboratory (CRL) in Cambridge, Massachusetts. + +**** The meeting is now full!!! *** + +This meeting is intended to cover a wide variety of topics about X Window System technologies, and the as yet unmet needs of the technologies that depend on the X Window System. As a result, this meeting is intended for people working across the entire X Window System stack, including toolkits and window managers and desktop infrastructure. This meeting is not, however, intended to cover general X application development topics or concepts. + +There will be a number of people giving presentations or leading discussions. These presentations will likely consume no more than half of the overall meeting time so the remaining time can be spent with informal discussions, hacking, breakout sessions, etc. + +If you wish to volunteer to give a presentation or lead a discussion, please send e-mail to [[xdevconf@lists.freedesktop.org|mailto:xdevconf@lists.freedesktop.org]]. In addition, if you have specific topics you'd like to see discussed in a presentation or during informal sessions, please send e-mail with your suggestions to that address as well. + + +### Attend via Phone + +The phone bridge is not working. See below for Audio streaming. + + +### Attend via IRC + +IRC: freenode, #xdevconf + + +### Attend via Audio/Video feeds + +X developer's meeting audio and video feeds: + +* Audio: Point gnomemeeting at gabe.freedesktop.org. First, go into Audio Codecs and disable everything but G.711-uLaw and G.711-ALaw; needs a bit more bandwidth but means you can actually hear what people are saying. +* Vide:o Depending on your browser click on [[http://freedesktop.org:9192/|http://freedesktop.org:9192/]] or [[http://freedesktop.org/~keithp/webcam.html|http://freedesktop.org/~keithp/webcam.html]]. +Will video presentations be available somewhere? Are them recorded? + + +### Presentation Agenda + +Current presentations for the X Developer's Meeting include: + + +#### Saturday, February 12 + +* Starting at 9:00 +* Welcome, logistics, agenda, schedule bashing + * Freedesktop Forum: What Problems Do We Need To Solve - Havoc Penningon, George Staikos, Jim Gettys + * DND, Other Specification Issues - Owen Taylor and George Staikos + * xrestop, xephyr, and X on handhelds - Mathew Allum ([[slides|http://www.o-hand.com/xmeet/]], [[demo|http://projects.o-hand.com/matchbox/demos.html]]) + * Testing Strategies - Stuart Anderson, Free Standards Group and X.org + * Short Topics - All + +#### Sunday, February 13 + +* Starting at 9:00 + * X Proxy and Multicast Demo - David Flynn, Realm Systems +* A Unified View of Improving X Desktop Rendering - The Owen Taylor, Søren Sandmann, Kristian Høgsberg and Diana Fong show + * Cairo Status - Carl Worth, Red Hat (Slides: [[SVG|http://cairographics.org/talks/xdevconf_2005_02_13/svg]], [[HTML|http://cairographics.org/talks/xdevconf_2005_02_13/html]] [[PDF|http://cairographics.org/talks/xdevconf_2005_02_13/cairo.pdf]]) + * X Input Redirection - Deron Johnson, Keith Packard ([[Intro & Slides|http://lists.freedesktop.org/archives/xevie/2005-February/000039.html]]) + * A New Input System - Kristian Hogsberg, Jim Gettys + * Polling And Scheduling in the X Main Loop - Kristian Høgsberg, Red Hat + * Reworking the X server main loop, with proposed changes. + * X and Media Support - Leon Shiman + * 3D Graphics Pipelines - Nick Triantos, NVidia + +#### Monday, February 14 + +* Starting at 9:00 + * Open Source Legal discussion, Patents and Copyrights - Scott Peterson, Greg Jones, Linda Hamel, General Counsel, MA ITD (Information Technology Division) + * X on GL - David Reveman, Novell + * Mesa Solo - Jon Smirl + * Merging fbdev and DRM - Jon Smirl + * X.org Update - Audience +Please all the people leave your presentations here so other people can see them. + + +### Limited In-Person Attendance + +Due to space limitations, attendance will be limited to no more than 40 people, and we are almost full. If you would like to attend, please send mail to [[xdevconf@lists.freedesktop.org|mailto:xdevconf@lists.freedesktop.org]]. Having the names of attendees in advance eases building security, as we share the building with other companies. + +An audio feed will be made available for those attending remotely or unable to attend due to limitations on space. The meeting venue provides networking support with high speed Internet access. + +The hotels recommended near CRL are The Kendall Hotel, the Cambridge Marriott, and the Residence Inn. All three of these are a short walk from CRL and easily accessible via public transportation from the Kendall Square subway stop next to MIT. We have not negotiated any special rates with these hotels, so you'll need to shop around for the best rates, as they vary. A longer list of hotels is available at [[http://www.ai.mit.edu/visiting/hotels/hotels.shtml|http://www.ai.mit.edu/visiting/hotels/hotels.shtml]] . Directions to the lab can be found at: [[http://www.crl.hpl.hp.com/who/lab/directions.htm|http://www.crl.hpl.hp.com/who/lab/directions.htm]] + + +### Currently Registered Attendees + +Currently registered attendees include: + + 1. Bill Abt + 1. Matthew Allum + 1. Paul Anderson + 1. Stuart Anderson + 1. Scott Balneves + 1. David Boloker + 1. Phil Blundell + 1. Mirko Boehm + 1. Alan Coopersmith + 1. Egbert Eich + 1. Mike Emmel + 1. David Flynn + 1. Nat Friedman + 1. Diana Fong + 1. Bdale Garbee + 1. Jim Gettys + 1. Jim Glutting + 1. Linda Hamel + 1. Mike A. Harris + 1. Kristian Høgsberg + 1. Mattias Hopf + 1. Harold Hunt + 1. Miguel de Icaza + 1. Lars Knoll + 1. Tommi Komulainen + 1. Adam Jackson + 1. Deron Johnson + 1. Eric Kunze + 1. Stewart Kreitman + 1. Paul Litvak + 1. Chris Lee + 1. Lubos Lunak + 1. Duncan Mak + 1. Kevin Martin + 1. Jim [[McQuillan|McQuillan]] + 1. Nhan Nguyen + 1. Keith Packard + 1. Tapani Pälli + 1. Havoc Pennington + 1. Larry Rau + 1. David Reveman + 1. Andy Ritger + 1. Robin Rowe + 1. Zack Rusin + 1. George Staikos + 1. Søren Sandmann + 1. Leon Shiman + 1. Owen Taylor + 1. Nick Triantos + 1. Peter Winston + 1. Carl Worth + 1. Scott Peterson + 1. Greg Jones +-- [[JimGettys|JimGettys]] - Feb. 13, 2005 diff --git a/Events/XDC2006.mdwn b/Events/XDC2006.mdwn new file mode 100644 index 00000000..128568ff --- /dev/null +++ b/Events/XDC2006.mdwn @@ -0,0 +1,132 @@ + + +# X Developers Conference 2006 +[[!table header="no" class="mointable" data=""" + [[<< XDC 2005|Events/XDC2005]] | **XDC 2006** | [[XDC 2007 >>|Events/XDC2007]] +"""]] + + +### Overview + +As a followon to previous conferences, we invite presentations on all topics related to the development and furtherance of X Window System technologies. + +If you wish to volunteer to give a presentation or lead a discussion, please send e-mail to [[xdevconf@lists.freedesktop.org|mailto:xdevconf@lists.freedesktop.org]]. In addition, if you have specific topics you'd like to see discussed in a presentation or during informal sessions, please send e-mail with your suggestions to that address as well. + + +### Location and Dates + +The next X.Org Developer's Conference will be held from February 8, 2006 to February 10, 2006 at the [[Sun Microsystems Santa Clara (Agnews) Campus|http://www.cr.nps.gov/nr/travel/santaclara/agn.htm]] in Santa Clara, CA, USA. ([[Driving Directions|http://www.sun.com/aboutsun/media/presskits/directions.html#sc]]) + + +#### Building Change + +Same Sun Santa Clara Campus, but we have acquired a room inside the Fortress. The Building Name is SCA15, room "HARVARD" on the first floor. This building is accessed from the North``East side of the campus, a short, direct walk from the River``Mark Plaza shopping area/Sierra Suites area. + +([[Google Map of the Sun Campus, Centered on SCA15|http://maps.google.com/?t=k&ll=37.394948,-121.952373&spn=0.003077,0.005456&t=k]]) + +We have an attended lobby with badges for everyone listed on this Wiki page. If you do not see your name here, let me know ASAP or you will not gain admittance to the conference. + + +### Registration + +REGISTRATION IS CLOSED + +Simple: Send email to [[stuart.kreitman@sun.com|mailto:stuart.kreitman@sun.com]] + + +### Conference Notes + +Notes from the presentations are being maintained by Adam Jackson ([[Presentation Notes|http://people.freedesktop.org/~ajax/xdc2006-notes.txt]]). (thanks, Adam! skk) + + +### Conference Schedule + + +#### Wednesday, February 8, 2006 + + * 8:00 AM Room Open, Get Togethers, Continental Breakfast 9:00 AM Real Start: Welcome, logistics, agenda, schedule bashing 9:30 AM Board of Directors Introductions + * 10:00 AM "Xgl" - David Reveman, Novell ([[Slides|http://www.freedesktop.org/~davidr/xdevconf06/]]) 11:00 AM "Avalon" - Matthias Hopf 12:00 AM Lunch 1:00 PM "Status Update on Project Looking Glass" - Deron Johnson, Sun 1:30 PM "Coordinate Redirection" - Keith Packard 2:00 PM "NVIDIA Driver Internals" - Andy Ritger, Nvidia ([[Slides|http://developer.nvidia.com/object/xdevconf_2006_presentations.html]]) 3:00 PM "Development Challenges for X and GL" - Kevin Martin, Red Hat ([[Slides|http://people.freedesktop.org/~kem/kem-xdevconf2006.pdf]]) 4:00 PM "Device Driver Issues TBD" - David Airlie 5:00 PM "X on Small Devices, Nokia 770" - Tapani Pälli, Nokia ([[Slides|https://stage.maemo.org/svn/maemo/projects/haf/doc/presentations/xdevconf2006_770.pdf]]) 6:00 PM Shuttle to El Torito's Mexican Restaurant (2950 Lakeside Dr, Santa Clara), Dinner Hosted by [[StarNet|StarNet]] Communications 9:00 PM Shuttle back to Campus, Hotels + +#### Thursday, February 9, 2006 + + * 9:00 AM Soft Start (joint Board/Sponsor's headbashing from 7:30 to 10:00) + * 10:00 AM Real Start 10:00 AM "What Accessibility Needs from X" - Peter Korn, Sun 11:00 AM Open Time Slot - BREAKOUT SESSIONS + * XCB status update - Keith Packard + * GLX_EXT_texture_from_pixmap spec wrangling - numerous people 12:00 AM Lunch "Open Solaris, Open Source Development at Sun" + * - Stephen Harpster, Director of Open Solaris, Sun Microsystems +1:00 PM "Accelerated Indirect GLX" - Kristian Høgsberg, Red Hat ([[slides|http://people.freedesktop.org/~krh/aiglx.pdf]]) +2:00 PM "A preview of the GNOME compositing manager" - Søren Sandmann Pedersen, Red Hat +3:00 PM "Deconstructing X Server Configuration" - Adam Jackson, Red Hat ([[slides|http://people.freedesktop.org/~ajax/xdc2006.pdf]]) +4:00 PM Break, Depart for Intel computer museum 6:00 PM Shuttle to Mountain View Castro Street Restaurant District 8:30 PM Everyone meet at Tied House Brewery off of Castro 10:00 PM Shuttle back to conference center + +#### Friday, February 10, 2006 + + * 8:00 AM Continental Breakfast 9:00 AM Start 9:00 AM "Power Management for Graphics Subsystems" - Jay Cotton, Sun ([[slides|http://mediacast.sun.com/share/alanc/xdevconf06-fbpm.pdf]]) + * 10:00 AM "Beyond Modelines: Xorg Display Configuration" - Stuart Kreitman, Sun 11:00 AM "Challenges of [[OLPC|http://www.laptop.org/]] Graphics" - Jim Gettys, OLPC 12:00 AM Lunch 1:00 PM "New DRI memory manager and i915 driver update" - Keith Whitwell & Thomas Hellstrom, Tungsten Graphics ([[slides|http://www.tungstengraphics.com/xdevconf2006.pdf]]) 2:00 PM "Evolving" - Zack Rusin (cancelled) 3:00 PM TALKS ARE OVER! Beer by the case. We'll keep the room open till 6 6:00 PM BYE ALL!! + +##### Hackfesting, Brainstorming, and Beer + +In response to feedback from previous Developer Conferences, we will enable good amounts of time, infrastructure, and space for getting actual work done. + +Proposed Breakout Sessions/Hacking Focus on: + +* Display configuration +* Accessibility +* Composite-aware managers +* Composite-aware screen magnification +* Live Video +* Security +* Thin Client and workstation performance analysis +* Composite / OpenGL compatibility +* Composite / XVideo compatibility +* Making X pixmaps directly usable as textures by OpenGL clients +* A session on improvements that should be made to OpenGL texture resource management in order to gracefully operate in an environment where all running programs are using textures +Please submit your interest in these and other topics. + + +#### Confirmed Attendees + +Mahmood Ali, David Airlie, Paul Anderson, Stuart Anderson, Jesse Barnes, Billy Biggs, Eric Boucher, David J. Brown, Ignacio Castano, Jesse Clayton, Alan Coopersmith, Jay Cotton, Jim Gettys, Alexandre Gouaillard, Thomas Hellstrom, Jay Hobson, Kristian Høgsberg, Alan Hourihane, David Hoover, Matthias Hopf, Harold Hunt, Adam Jackson, Deron Johnson, James Jones, Joe Kain, Stuart Kreitman, Tommi Komulainen, Peter Korn, Carol Lavelle, Phillip Langdale, Sam Lau, John M. Martin Jim Mc``Quillan, Kevin E. Martin, Valery Moya, Shrijeet Mukherjee, Jens Owen, Keith Packard, Tapani Palli, Stuart Parmenter, Søren Sandmann Pedersen, Aaron Plattner, Martin Porcelli, Nivedita Rao, Andy Ritger, Zack Rusin, Bankim Shah, Jamie Sharp, David Schleef, Steve Schoch, Leon Shiman, Edward Shu, Paul Swart, Carl Switzky, Vladimir Vukicevic, Keith Whitwell, Henry Zhao, Daniel Zhu, + +Count: 59 + + +#### Logistics + +The nearest airport is San Jose Mineta ("SJC"). Distance to Sun Santa Clara Campus Bell Tower is 3 miles. San Francisco Airport ("SFO") is larger and be more accessible by air. It is about 45 miles north of the Bell Tower, but you can take the Caltrain shuttle down to Santa Clara or up to San Francisco. The Sunway shuttle stops at various caltrain stations near Santa Clara and Menlo Park. Bicycles are permitted on the caltrain and Sunway. + +[[http://www.caltrain.com/caltrain_map.html|http://www.caltrain.com/caltrain_map.html]] + +Stay tuned for a list of closeby hotels with favorable rates and shuttle bus availability + +This is California. Public transportation is mostly nonexistant.You don't get anywhere without wheels. Therefore, we are working on attaching the [[SunWay|SunWay]] shuttle fleet to help move willing groups of people to the selected evening events. We will make every attempt to minimize the need for having a car during this conference. Carpooling will figure large in this endeavor, so please indicate whether you will have seats available, or will need a seat during your stay here. + +Update, Dec 13, 2005: + +It looks like we will be able to provide Sunway Shuttle service for airport pickups, hotel sweeps, and evenings out. We do need headcount for these resources ASAP. Feb 6,2006: Having received zero requests for ground transportation, this option is no longer being offered. + + +#### Recommended Hotels + +***Sierra Suites, 3915 Rivermark Plaza, Santa Clara, CA (408) 486-0800 + + * +++ 3 miles from SJC, Walking Distance to Conference. +++ +*Biltmore Hotel, 2151 Laurelwood Road, Santa Clara (408) 988-8411, (800) 255-9925 + +*Double``Tree Hotel, 2050 Gateway Place, San Jose (408) 453-4000 + +*Embassy Suites, 2885 Lakeside Drive, Santa Clara (408) 496-6400 + +*Hyatt San Jose, 1740 North 1st Street, San Jose (408) 993-1234, (888) 975-1234 + +*Marriott Santa Clara, 2700 Mission College Boulevard, (408) 988-1500 + +*Santa Clara Hilton, 4949 Great America Parkway, Santa Clara (408) 330-0001 + +*Staybridge Suites, 900 Hamlin Court, Sunnyvale (408) 745-1515 + +*Staybridge Suites, 1602 Crane Court, San Jose (408) 436-1600 + +*Westin Santa Clara, 5101 Great America Parkway, Santa Clara (408) 986-0700 + +*Wyndham Hotels, 1350 North 1st Street, San Jose (408) 453-6200 diff --git a/Events/XDC2007.mdwn b/Events/XDC2007.mdwn new file mode 100644 index 00000000..491146b2 --- /dev/null +++ b/Events/XDC2007.mdwn @@ -0,0 +1,139 @@ + + +# XDC2007: Xorg Developer's Conference +[[!table header="no" class="mointable" data=""" + [[<< XDC 2006|Events/XDC2006]] | **XDC 2007** | [[XDS 2007 >>|Events/XDS2007]] +"""]] + + +## February 7,8,9 2007 San Francisco Bay Area + +Conference organizer: [[Stuart Kreitman|mailto:stuart.kreitman@sun.com]] + +Live notes are going up at [[XDC2007Notes|XDC2007Notes]]. Play along! + + +## Location + +We're a go for the [[TechShop|http://techshop.ws./]], a very cool Maker's workshop very near Sun's Menlo Park campus, and close to Palo Alto and Menlo Park Hotels and dining. + +Address/Map: [[120 Independence Drive, Menlo Park, CA 94025|http://maps.google.com/maps?q=120+Independence+Dr,+Menlo+Park,+CA+94025]] + + +## Getting There, Getting Around There + +[[San Jose (SJC) Airport|http://www.sjc.org/]] is 16 miles south of Menlo Park airporter shuttle (1-800-XXX XXXX) + +[[San Francisco (SFO) Airport|http://www.flysfo.com/]] is 20 miles north of Menlo Park + + +## Recommended Hotels + +* Hampton Inn, 390 moffett blvd, Mountain View CA +* Marriot Residence Inn, 4460 El Camino Real, Los Altos +* Marriot Residence Inn, # 1854 El Camino Real West Mountain View , CA +* Sheraton Palo Alto +* Westin Palo Alto +* Stanford Park Hotel +_range of price/convenience options, The above listed are good places in good locations_ + + +## Agenda (Presenters: Get your talk listed here. If you need a change, negotiate directly with other presenters and update the wiki) + +_each item corresponds roughly to one hour of programming_ _Each day, we're planning 3 1 hr slots before lunch, and 2 1 hr slots after lunch, then breakouts_ + +_In response to feedback from last year's conference, we are leaving more open space in the schedule for structured and unstructured un-conferencing each day_ + + +### Wednesday 9AM -> 5 PM + +* Introductions, Overview - Stuart Kreitman +* [[MultiPointer|MultiPointer]] X - Peter Hutterer +* Virtual Multihead - Philip Langdale, VMware +* Lunch +* Randr 1.2 - Keith Packard, Intel +* 7.2/7.3 Roadmap - Adam Jackson, Red Hat +* Breakout Sessions - All +* Breakout Reports - All + +### Thursday 9AM -> 5 PM + +* Board of Directors Report, Q&A +* Display Technology, EDID, VESA - Joe Miseli (Sun) +* Lunch +* Secure X - Eamon Walsh ([[SecurityTalkAgenda|SecurityTalkAgenda]]) +* Cut&Paste - Bart Massey +* Breakout Sessions - All +* Breakout Reports - All + +### Friday 9AM -> 5 PM + +* Compiz - David Reveman +* Beryl - Quinn Storm +* Mesa - Brian Paul +* Lunch +* NVIDIA, Xinerama - Andy Ritger, NVIDIA +* Xcb - Bart Massey, Portland State U. +* Breakouts +* Bash! Gunn High School's award winning Jazz Combo will play for us! + +### Items not covered + +* Virtualization (Xen) +* (auto)-configuration +* Open Source drivers vs Vista-certified +* Display Port / HDMI / replacing VGA/DVI +* Nouveau +* One Laptop Per Child - Jim Gettys, olpc (Cancelled) + +## Attendees + +_insert your name on a separate line_ + +* Eric Anholt, Intel +* Jesse Barnes, Intel +* Ben Byer, Apple +* Erwann Chénedé, Sun +* [[Alan Coopersmith|AlanCoopersmith]], Sun +* Jay Cotton, Sun +* Alex Deucher +* Egbert Eich, SuSE +* Behdad Esfahbod, [[RedHat|RedHat]] +* Matthias Hopf, SuSE +* Peter Hutterer, UniSA +* Adam Jackson, Red Hat +* James Jones, Nvidia +* Stuart Kreitman, Sun +* Philip Langdale, VMware +* Chris Lee, VMware +* Kevin Martin, Red Hat +* Bart Massey, Portland State University +* Jim [[McQuillan|McQuillan]], ltsp.org +* Joe Miseli, Sun +* Keith Packard, Intel +* Brian Paul, Tungsten Graphics +* Aaron Plattner, Nvidia +* Niveditha Rau, Sun +* David Reveman, Novell +* Andy Ritger, Nvidia +* Bankim Shah, Attachmate +* Carl Switzky, Sun +* Roberto Tam, Sun +* Bernard Traversat, Sun +* Kevin Van Vechten, Apple +* Eamon Walsh, NSA (SELinux developer) +* NOT ATTENDING: + * Carl Worth, Red Hat, (I had been planning to attend, but due to unforeseen circumstances will not be available. Have fun, everybody!); + * Daniel Stone, Nokia (cannot attend due to schedule clashes -- sorry!) + * Jim Gettys, OLPC (Thursday only) + +## Sharing Stuff + +Folks in need, and folks in a generous mood, please list your interests (or send me email if you want me to help you get matched up) + + +## Other Stuff + +If you're finishing up the Xorg Developer's Conference, and haven't had your fill of geek stuff, head down the coast to Los Angeles on Friday. The Fifth Annual [[SoCal|SoCal]] Linux Expo will be February 9th-11th at the Westin LAX Hotel (which is a short shuttle ride from LAX). There are four speaker tracks on both Saturday and Sunday, plus BOFs and a couple of mini-conferences on Friday. If you'd like a BOF for any reason, contact [[g@socallinuxexpo.com|mailto:g@socallinuxexpo.com]] . For more info on the Expo, see [[http://socallinuxexpo.org|http://socallinuxexpo.org]] + +Thanks to Stu for the commercial space! diff --git a/Events/XDC2008.mdwn b/Events/XDC2008.mdwn new file mode 100644 index 00000000..4a9c6048 --- /dev/null +++ b/Events/XDC2008.mdwn @@ -0,0 +1,39 @@ + + +# XDC 2008 +[[!table header="no" class="mointable" data=""" + [[<< XDS 2007|Events/XDS2007]] | **XDC 2008** | [[XDS 2008 >>|Events/XDS2008]] +"""]] + +The X Developers' Conference for 2008 was hosted by Google in Mountain View, California, from the 16th through the 18th of April, 2008. The event will be held at [[1501 Salado Drive|http://maps.google.com/maps?f=q&hl=en&geocode=&q=1501+salado,+mountain+view&jsv=107&sll=37.0625,-95.677068&sspn=50.291089,80.15625&ie=UTF8&z=16]]. This is on the opposite side of the Ampitheater Parkway/Rengstorff Ave offramp from US-101 than the rest of the Google complex. Please make a note of how to get there. + +* [[Attendees|Events/XDC2008/Attendees]] +* [[Program|Events/XDC2008/Program]] +* [[Notes from the talks|Events/XDC2008/Notes]] +We will run the 3-day summit as a normal conference, with presentations and also birds-of-a-feather group sessions, as well as informal 'corridor sessions', and plenty of time for after-hours social activities. + +Attendance is free, but you must register beforehand, by putting your name on the Attendees page. + + +## Accommodation + +There are [[several hotels|http://maps.google.com/maps?near=1600+Amphitheatre+Parkway,+Mountain+View,+CA+94043+(Google)&geocode=6913274534084284730,37.423398,-122.086507&q=hotels&f=l&hl=en&dq=google+loc:+Mountain+View,+CA&ie=UTF8&t=h&z=13]] near the Google offices. Many of them are filling up and most have said that they are usually full a week before the day you arrive, so don't wait til the last minute. The [[Best Western Mountain View|http://book.bestwestern.com/bestwestern/productInfo.do?propertyCode=05355]] is where several of us are staying, and as of 2008 Apr 11, they still had several rooms available. + + +## Travel + +The nearest airport to Mountain View is San Jose, California (SJC), but the one most attendees will likely be flying into is San Francisco International (SFO). SFO is about 30 miles from Mountain View, and as such, a taxicab would be rather expensive. Other options are renting a car (advised, since any hotel would be a few miles from Google) or using the BART/CalTrain to get to Mountain View, and then taking a taxicab to your hotel from there. + +The event will be held at 1501 Salado Drive, Mountain View. [[Map|http://maps.google.com/maps?f=q&hl=en&geocode=&q=1501+salado,+mountain+view&jsv=107&sll=37.0625,-95.677068&sspn=50.291089,80.15625&ie=UTF8&z=16]] directions are available from this point. + + +## Meals + +Breakfast, (starting at 10:00 AM), lunch, and an afternoon snack will be kindly provided by Google, at the location. You may make your own dinner plans for Wednesday and Friday. + +Thursday evening, the X.org Foundation is sponsoring a dinner for all attendees. We'll meet at 7:00 PM [[Don Giovanni Ristorante|http://www.dongiovannis.com]] which is at [[235 Castro St, Mountain View, CA 94041|http://maps.google.com/maps?hl=en&ie=UTF-8&um=1&q=don+giovanni%27s&near=Mountain+View,+CA&fb=1&cid=0,0,14678227340696319431&sa=X&oi=local_result&resnum=1&ct=image]]. + + +## Registration, talks + +If you are coming, or just interested, please subscribe to a [[low-volume mailing list|http://lists.x.org/mailman/listinfo/xdc2008]] for updates. Also, please add your name to the [[Attendees|Events/XDC2008/Attendees]] and if you are thinking about giving a talk, add your ideas to the bottom of the [[Program|Events/XDC2008/Program]] page. diff --git a/Events/XDC2009.mdwn b/Events/XDC2009.mdwn new file mode 100644 index 00000000..5a6a3f94 --- /dev/null +++ b/Events/XDC2009.mdwn @@ -0,0 +1,39 @@ + + +# XDC 2009: Portland, Oregon September 28-30 +[[!table header="no" class="mointable" data=""" + [[<< XDC 2008|Events/XDC2008]] | **XDC 2009** | [[XDS 2010 >>|Events/XDS2010]] +"""]] + +The X Developers' Conference for 2009 will be held at Portland State University (PSU) in Portland, Oregon, from Monday September 28 through Wednesday September 30. PSU is within walking distance of Portland's downtown area and a wide variety of dining, lodging, and public transportation options. + +The conference is scheduled to follow directly after [[Linux Plumbers Conference 2009|http://linuxplumbersconf.org/2009/]] so that people attending both LPC and XDC can do that with a single trip. + +The conference will be held at the [[University Place|http://cegs.pdx.edu/stay/upl/]] hotel and conference center on the edge of the PSU campus. + +* [[Attendees|Events/XDC2009/Attendees]] +* [[Program|Events/XDC2009/Program]] +* [[Notes from the talks|Events/XDC2009/Notes]] +We will run the 3-day summit as a normal conference, with presentations and also birds-of-a-feather group sessions, as well as informal 'corridor sessions', and plenty of time for after-hours social activities. + +Attendance is free, but you must register beforehand, by putting your name on the Attendees page. + + +## Accommodation + +We encourage attendees to stay at the conference hotel ([[University Place|http://cegs.pdx.edu/stay/upl/]]) for convenience. We have initially reserved a block of 20 rooms for the conference, (so let them know you're with the conference when making a reservation). We will attempt to increase that block size as needed, (so please make your reservation as early as possible). + + +## Travel + +Portland is easily accessed by the [[Portland International Airport(PDX)|http://flypdx.com]]. Portland has a very nice public transportation system, ([[TriMet|TriMet]]), including the MAX light-rail system with the red line service between the airport and downtown, and the green line serving PSU. Use [[TriMet's trip planner|http://ride.trimet.org/]] to find good transportation options. And note that you can simply enter "PDX" for the airport and "PSU" for the University. + + +## Meals + +Portland is a city of many food carts, and there is a large selection (Thai, Mexican, vegan African-Caribbean, soup, sandwiches, etc) right outside PSU, in the parking lot at the corner of 4th & College Sts. + + +## Registration, talks + +If you are coming, or just interested, please subscribe to a [[low-volume mailing list|http://lists.x.org/mailman/listinfo/xdc2009]] for updates. Also, please add your name to the [[Attendees|Events/XDC2009/Attendees]] and if you are thinking about giving a talk, add your ideas to the bottom of the [[Program|Events/XDC2009/Program]] page. diff --git a/Events/XDC2011.mdwn b/Events/XDC2011.mdwn new file mode 100644 index 00000000..07342372 --- /dev/null +++ b/Events/XDC2011.mdwn @@ -0,0 +1,120 @@ + + +# XDC2011: Chicago, United States +[[!table header="no" class="mointable" data=""" + [[<< XDS 2010|Events/XDS2010]] | **XDC 2011** | [[XDC 2012 >>|Events/XDC2012]] +"""]] + +* [[Attendees|Events/XDC2011/Attendees]] +* [[Program|Events/XDC2011/Program]] +* [[Notes|Events/XDC2011/Notes]] +XDC2011 is to take place in from the 12th through the 14th of September in Chicago, Illinois, United States. The event is being hosted at the Illinois Institute of Technology within the [[McCormick|McCormick]] Tribune Campus Center in the Ballroom. + +The [[Chicago XDS proposal|http://www.michaellarabel.com/misc/xds-chicago-proposal.pdf]] has additional information that was prepared for the foundation board. + + +## Venue + +The XDC2011 event is taking place at the Illinois Institute of Technology at the [[McCormick Tribune Campus Center|http://en.wikipedia.org/wiki/McCormick_Tribune_Campus_Center]]. It's immediately due-south of downtown Chicago by just a few minutes with easy public transportation. Thanks go out to the Association for Computing Machinery in helping X.Org secure this venue at an affordable rate in conjunction with IIT. + + +## Program + +If you would be interested in providing a talk during the event, please add it to the [[program page|Events/XDC2011/Program]]. + +_For anyone arriving the weekend prior to XDC2011, [[MichaelLarabel|MichaelLarabel]] will already be showing around a few attendees various places around Chicago and various pubs in the evening. Contact him and you're more than welcome to meet-up with other attendees. His locations will also be [[tweeted|http://twitter.com/MichaelLarabel]] for those that may be showing up at a moment's notice. Sunday evening there might also be a pre-XDC2011 gathering at a local establishment._ + + +## Travel + +Chicago has two main airports, Chicago O'Hare (ORD) and Chicago Midway (MDW). Most attendees, especially international visitors, will likely arrive at O'Hare. Midway is common for the budget domestic airlines and other general aviation traffic. ORD is one of the lowest-cost airports in the United States to fly in from Europe with direct flights. + +Both airports are connected to the city via local train. There are also shuttle buses to major hotels within the city. + + +## Local Transit + +Chicago is much better than most cities in the United States with regard to public transportation. There's buses and trains (also referred to as 'El') that go under and above ground depending upon location. Trains are generally on time and most preferred as buses are often late, missing, or crowded, but still better than most US locations. + +All events should be within close proximity to a train line for a quick and easy commute around the city. + +Public transportation is served by the [[Chicago Transit Authority|http://www.transitchicago.com/]]. Local routes can also be planned using [[Google Maps|http://maps.google.com/]], which tends to provide accurate information for the city. + +The event itself at the [[McCormick|McCormick]] Tribune Campus Center is located along [[the CTA green line|http://en.wikipedia.org/wiki/Green_Line_%28Chicago_Transit_Authority%29]] directly at the [[35th–Bronzeville–IIT|http://en.wikipedia.org/wiki/35th%E2%80%93Bronzeville%E2%80%93IIT_%28CTA%29]] stop. There is also a red line Sox-35th stop within walking distance too, which is the train stop used for accessing the White Sox baseball stadium (Cellular Field). + +"The bus lines that run to IIT are the 29 (directly to MTCC from Navy Pier/Loop), the 24 (from the Loop down Wenworth/LaSalle, one block west of MTCC) and the 4 (from downtown on Michigan to one block east of MTCC). They are often slow, but they may be more convenient than the train depending on where you are staying." + +"There is a free IIT shuttle bus that takes people directly from the IIT downtown campus to the MTCC. The information is at [[http://www.iit.edu/directory/2011-2012IITShuttleBusSchedule.pdf|http://www.iit.edu/directory/2011-2012IITShuttleBusSchedule.pdf]] Technically it's only for IIT students/faculty but you might be able to hop on by saying you're with the CS department." + + +## Accommodations + +With Chicago being a popular tourist destination, there's a variety of accommodations in and around the city of Chicago for all price ranges. [[Hotels.com|http://www.hotels.com/]] is able to provide a list of Chicago area hotels. For those on a budget, the accommodations near O'Hare International Airport may be most economical (with an easy 20~30 minute train ride to reach the center of the city) while the hotels in the proper city center are the most expensive options. + +* [[Central Loop Hotel|http://www.centralloophotel.com/]] - heart of downtown right in the "loop" whereby all the public train lines wrap around. Convenient location. Circa $170~180 USD per night. +* [[Club Quarters Chicago|http://www.clubquarters.com/loc_chicago.php]] - Same as Central Loop Hotel in terms of price / central location. +* [[Travelodge Downtown Chicago|http://www.travelodge.com/Travelodge/control/Booking/property_info?propertyId=10073]] - In the center of downtown Chicago as well. Likely the least expensive hotel that one can find while still being in a very central location; circa $100~140 a night (as of 14 May on Hotels.com is $100 USD per night at a supposed discount of $40) +* [[Chicago South Loop Hotel|http://www.chicagosouthloophotel.com/]] - Same central location, slightly south / closer to IIT. $169 USD per night. The area around the hotel, however, has been reported to not be a nice area. It's been advised now that it's advised not to walk around in this neighborhood... So ideally better to be elsewhere or to use only taxi/bus for commuting. An IIT professor writes, "the Chicago South Loop Hotel used to be shady, but that whole neighborhood is much better than it was 5 years ago. That would definitely be the closest (8 minute walk) safe place to stay. It's a little far from the train, but there are cabs coming directly to it because many people who have conferences at the [[McCormick|McCormick]] Place stay there." + +## Chicago Dining + +Chicago has many dining options for all price ranges. Chicago is particularly known for unique styles of pizza and hot dogs. According to [[WikiTravel|http://wikitravel.org/en/Chicago]], Chicago is evidently also known for greasy, large sandwiches that are simply called "Italian Beef." + +Beer in America is an unfortunate travesty. Particularly for European visitors, if beer quality is even the smallest concern, avoid most restaurants near Wrigley Field and other sporting venues. For any other recommendations, consult [[MichaelLarabel|MichaelLarabel]]. + +The XDC2011 dinner and social event is TBD. + +Below are some unofficial recommendations on particular establishments. + +* Resi's Bierstube [2034 W Irving Park Road] - Good place. Small biergarten. Decent selection of good beer and food. Favorite local German beer hall. +* Laschet's Inn [2119 W Irving Park Road] – This along with Resi's is the best German food you'll be able to find in Chicago. +* The Berghoff Restaurant [17 W. Adams Street] - Another German restaurant, but this one at least is downtown. +* Fogo de Chao [661 N [[LaSalle|LaSalle]] Blvd] – A good Brazilian Steakhouse. It's expensive by American standards, but well worth it. +* Moto [945 W Fulton Market] - Favorite restaurant in Chicago, one of my favorites in the world. Quite a unique experience, but expensive and can be difficult to obtain a reservation in short notice. +* Hot Doug's [3324 N California] - Likely the best hot dogs in Chicago. +* English [444 N La Salle] - Decent bar downtown. +* Moe's Cantina [155 W Kinzie] - Good Mexican restaurant. +* Gibsons [1028 N Rush] - Good steakhouse. +* Portillo's [100 W Ontario Street] - Inexpensive restaurant and beer. +* Hopleaf [5148 N Clark] - Good bar and restaurant, good food. Bit far north, however. +* Goose Island [1800 N Clybourne or 3535 N Clark] – Decent local brewery and restaurant. +* Gino's Pizza [Multiple Locations] - Chicago style deep dish pizza. +* Giodano's Chicago Pizza [Multiple Locations] - Chicago style deep dish pizza. +* Kingston Mines [2548 N Halstead] - One of the oldest and most well known Chicago Blue's music joints. +If you would like any other recommendations about particular places or bars, ask [[MichaelLarabel|MichaelLarabel]]. + + +## Dining Near The Venue + +Below are a few restaurants / bars located near the IIT [[McCormick|McCormick]] Tribune Campus Center itself, if looking for additional food or drink during the event itself. Additional places can easily be found with Google Maps using "restaurant loc: The [[McCormick|McCormick]] Tribune Campus Center, Chicago, IL 60616" + +* 7-Eleven - There's a convenience store at the venue itself. +* Starbucks [3506 South State Street] +* Einstein Bros Bagels [3241 S Federal Street] - A cafe / bagel shop right near the venue. +* Cork & Kerry at the Park [3258 South Princeton Avenue] - Bar restaurant. +* Rocky's Bar & Grill [234 West 31st Street] - Bar restaurant, plus an outdoor "biergarten". +* Fratellini Pizza & Pasta [3258 South Wells Street] - Pizza and pasta. +* Miller Pizza Company [17 West 35th Street] - Normal pizza. +* Jimmy John's [3506 South State Street] - Cheap sandwiches. +* "Chinatown" is a short distance away from IIT with a wide selection of Chinese food. + +## Registration + +If you will be attending XDC2011, add your name to the [[attendees page|Events/XDC2011/Attendees]]. Additionally, subscribe to the [[X.Org events mailing list|http://lists.x.org/mailman/listinfo/events]] for further details. This is a low-volume mailing list. + + +## Remote Participation + +If physical participation is not possible but would be interested in participating remotely via IRC and ideally live audio / video streams, make your interest known to [[MichaelLarabel|MichaelLarabel]] that you would like live streaming of the event. + + +## Miscellaneous + +The United States uses standard North American 120V / 60Hz power plugs. American Express, VISA, and [[MasterCard|MasterCard]] are all common in Chicago and accepted by most retailers and restaurants. + +[[Wikitravel|http://wikitravel.org/en/Chicago]] and [[TripAdvisor|http://www.tripadvisor.com/Tourism-g35805-Chicago_Illinois-Vacations.html]] are great sources for other travel advice and recommendations. + + +## Contact + +Feedback and any other inquiries regarding the organization of the event -- or questions if encountered when in Chicago at the event -- can be directed to Michael Larabel <[[michaellarabel.com|http://www.michaellarabel.com/]]> or via SMS / voice-mail at +1.601.871.0456 (US) or +49.089.8091.2991 (DE). Note: these telephone numbers are screened for public callers. Michael can also be contacted on [[FreeNode|FreeNode]] IRC via the michaellarabel handle. diff --git a/Events/XDC2012.mdwn b/Events/XDC2012.mdwn new file mode 100644 index 00000000..2c54436b --- /dev/null +++ b/Events/XDC2012.mdwn @@ -0,0 +1,135 @@ + + +# XDC2012: Nürnberg, Germany +[[!table header="no" class="mointable" data=""" + [[<< XDC 2011|Events/XDC2011]] | **XDC 2012** | XDC 2013 +"""]] + +* [[Attendees|Events/XDC2012/Attendees]] +* [[Program|Events/XDC2012/Program]] +* [[BookSprint|Events/BookSprint2012]] +* [[Weekend Event|Events/XDC2012/Weekend]] +* [[Proceedings and Recorded Videos|Events/XDC2012/Proceedings]] +* Experimental Live Video - Closed +The 2012 X.Org Developer Conference (XDC2012) is to be held from September 19th thru 21st 2012 in Nürnberg (Nuremberg), Germany. The event will be hosted by [[SUSE|http://www.suse.com]] at their company headquarters in Nuernberg. Please join us to celebrate the 25th anniversary of the first [[X11 release|http://groups.google.com/group/comp.windows.x/browse_thread/thread/3454f7031d88a3b8#]] (15 September 1987, but we'll round a bit) during this conference, we are looking forward to seeing you. An after-conference weekend event will be organized to honor this date [[(check below)|Events/XDC2012]]. + + +## Venue + +The conference will be held in the main conference room at the SUSE headquarters at [[Maxfeldstrasse 5|http://maps.google.de/maps?f=q&source=s_q&hl=de&authuser=0&q=Maxfeldstra%C3%9Fe+5,+Altstadt+und+Engere+Innenstadt+90409+N%C3%BCrnberg,+Bayern&aq=&vps=1&jsv=402e&sll=51.151786,10.415039&sspn=14.100269,34.936523&vpsrc=1&ie=UTF8&oi=georefine&ct=clnk&cd=2&geocode=FT2y8gIdqRupAA&split=0]]. + +The conference room is easy to find: it is directly accessible from the outside. If you are coming from Pirckheimerstrasse turn into Maxfeldstrasse and walk uphill along the blue building on the right until you get to a free area on your right. From there you can enter the conference room directly. You will find a sign at the door. + +Please note: for security reasons the door is locked. The door will be open in the morning before the conference and after lunch. If you need to get in at other times and you find the door locked you will find my mobile number on a sign at the door. Please call me so I can let you in. As attendee you will get a conference badge, please carry the badge with you at all times when you are inside the building. + + +## Program + +There are two ways to submit a presentation for this event: + +1. There is a [[Call for Papers|http://www.x.org/wiki/Other/Press/CFP2012_supplemental]]. The deadline for submission is August, 15, 2012. +1. For more informal presentations you may add your talk to the [[program page|Events/XDC2012/Program]]. The deadline for submission here is September 14, 2012. +For more information please also check [[here|http://www.x.org/wiki/Other/Press/CFP2012_supplemental]]. A schedule will be available shortly. + + +## Videos + +Recorded videos of the session are available from [[YouTube|http://www.youtube.com/phoronix]]. + + +## Registration + +If you want to attend XDC2012 please add your name to the [[attendees page|Events/XDC2012/Attendees]]. Additionally please subscribe to the [[X.org events mailing list|http://lists.x.org/mailman/listinfo/events]] where we will post regular updates. + + +## Accommodation + +There are a number of affordable hotels in Nuernberg (especially since we painstakingly avoided any week with a major trade show), many close to the conference venue. + +We have a recommended conference hotel as we are in the process of negotiating a special conference rate. This hotel should not only offer you good rates it is also at a convenient 5 minute walking distance from the conference venue. There is a separate [[hotel page|Events/XDC2012/Hotels]]. + + +## Travel + +Nuernberg can be reached: + +* By **plane**. The Nuernberg Airport is close to the city and can be reached by local transportation in just a few minutes. Nuernberg airport is serviced from some international locations, still expect to travel via Franfurt or Munich. If possible you should avoid Munich at that time as Octoberfest will start directly following the event. If you fly via Frankfurt, you have the choice between flying on to Nuernberg or taking the train and enjoying a bit of the countryside: An railroad station is located right at the airport (Frankfurt(M) Flughafen Fernbf.) where you can board a high speed train going to Nuernberg at least every hour. The train offers more comfort and leg room than coach class on airplanes and also provides electrical power outlets. +* By **train**. Nuernberg is located conveniently on a major high speed train line (ICE) running to Munich (1 hour), Frankfurt (2h), Cologne, Berlin and several other major cities. It can also be reached conveniently by train from anywhere else in Europe, too. You can search for [[connections|http://www.bahn.de]] and [[purchase tickets|http://www.bahn.de]] ([[English website|http://www.bahn.com/i/view/USA/en/index.shtml]]) on-line with any major credit card. The train station is just a few subway stops away from the conference venue and preferred hotel. The train station in Nuernberg is **Nürnberg Hbf**, and the train station at the Frankfurt airport is **Frankfurt(M)Flughafen** +* By car. The conference hotel offers guest parking (for an additional charge). Those of you who do plan to take the car will figure out the rest ;-) + +## Local transportation + +Nuernberg has an excellent public [[transportation system|http://www.vng.de]]: Most locations in Nuernberg can easily be reached by public transportation. + +Tickets are available from vending machines at any stop (see also our hints on using public transportation). The conference venue and hotel can be reached on subway line 3. Please also check out our [[tips on public transportation|Events/XDC2012/PublicTransportation]]. + +It is unlikely that you will need any public transportation during the time of the conference, though, as the venue is conveniently located just north of the inner city. The inner city can conveniently be accessed by foot: it is only roughly 1km from east to west and 1.5km from north to south. For lines please check [[here|http://www.vgn.de/liniennetze/schienennetz_nuernberg_furth/]]. + + +## Local Dining + +The conference venue is right outside the old city wall, thus in close walking distance from the city center. There are many restaurants close-by as well as towards the city center. Just walk down the street or ask for recommendations on site. + +Also check out the [[Nuernberg Tourist Information|http://tourismus.nuernberg.de/]]. + + +## Remote Participation + +For those who cannot make it to the conference we are planning to record the sessions. We may even have a live stream, also participation via IRC should be available. + + +## Travel Sponsoring + +If you are not on a corporate budget but have something to present, please contact the X.Org Foundation Board of Directors [[board@foundation.x.org]] for travel sponsorship. + + +## Miscellaneous + +Germany uses Type E/F [[hybrid plugs (CEE7/7)|http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets]] and [[Euro plugs|http://en.wikipedia.org/wiki/Euro_plug]] at 230V/50Hz. People should remember to bring their own adapters. + +The currency is Euro (EUR), language is German. Hotel and restaurant staff should speak some English, since Nuernberg is a tourist town many restaurants have English menus available. + +Major credit cards (AMEX, Visa and M****asterCard) are accepted at most hotels and restaurants. Some pubs and beer gardens may require cash. + + +## After Conference Events + +<a name="beer_hiking_trip"></a> If you can spare the weekend after the conference - hang around with us to celebrate the 25th anniversary of the first release of X11 and join us for [[a beer hiking trip thru the 'Fraenkische Schweiz'|Events/XDC2012/Weekend]] on Saturday. On Sunday, [[a visit to the Nazi Party Rally Grounds|Events/XDC2012/Weekend]] will take place. + +In nearby Munich, from 22 September to 7 October is Oktoberfest. [[Michael Larabel|http://www.michaellarabel.com/]] is able to provide tours of München / the wiesn (with either a historical and/or beer focus) at any point after the first Saturday (22nd). + + +## Further Inquiries + +If you have any questions regarding the event please feel free to contact me at [[egbert.eich@gmail.com]]. + + +## Thanks + +The organizers want to thank: + +* the 'SUSE Linux Products GmbH' which provided the venue as well as funds for coffee breaks. +* 'Phoronix' for the beer. +Our Helpers + +* [[Omar Gomez Rey|http://omar-gomez-rey.de]] for setting up the conference room +* Oliver Fecher for organizing the conference room +* Salvatorica Serra for organizing the catering +* Iwona Maher for infrastructure support +* Christian Deckelmann for setting up the network +* Jürgen Weigert for video recording +* Gerhard Schlotter for helping out keeping the room open and getting some last minute printing done. + +## Links + +[[Email Announcement|http://lists.x.org/archives/xorg-devel/2012-March/030164.html]] + +[[Email Update #1|http://lists.x.org/archives/xorg-devel/2012-August/033131.html]] + +[[Email Update #2|http://lists.x.org/archives/xorg-devel/2012-August/033360.html]] + +[[Email Update #3|http://lists.x.org/archives/xorg-devel/2012-September/033634.html]] + +[[Email Update #4|http://lists.x.org/archives/xorg-devel/2012-September/033641.html]] + +[[Email Update #5|http://lists.x.org/archives/xorg-devel/2012-September/033642.html]] diff --git a/Events/XDS2007.mdwn b/Events/XDS2007.mdwn new file mode 100644 index 00000000..207c3c6c --- /dev/null +++ b/Events/XDS2007.mdwn @@ -0,0 +1,54 @@ + + +# XDS 2007 +[[!table header="no" class="mointable" data=""" + [[<< XDC 2007|Events/XDC2007]] | **XDS 2007** | [[XDC 2008 >>|Events/XDC2008]] +"""]] + +The X Developers' Summit for 2007 was held at [[Clare College|http://www.clare.cam.ac.uk]], [[Cambridge|http://wikitravel.org/en/Cambridge_(England)]], UK (not the one near Boston), from the 10th-12th September. + +* [[Attendees|Events/XDS2007/Attendees]] +* [[Program|Events/XDS2007/Program]] +* [[Notes from the talks|Events/XDS2007/Notes]] +We will run the 3-day summit as a normal conference, with presentations and also birds-of-a-feather group sessions, as well as informal 'corridor sessions', and plenty of time for after-hours social activities. + +Attendance is free, but you must register beforehand, by putting your name on the Attendees page. + + +## Accommodation + +Accommodation has been arranged through Clare College for around £70 per night, please take advantage of this if possible to help defray the costs of the meeting. The rooms are single rooms with a private ensuite (i.e. own bathroom and toilet). Currently, everyone who has listed themselves on the attendees page without 'non-college accommodation' next to their name is assumed to be staying in the college. We'll have a system set up for you to provide your details and payment shortly. The rooms will have wireless internet access. + +The rooms are available for checkin on Sunday afternoon (the 9th, at 2pm), and checkout on Thursday morning (the 13th, at 9:30pm). Luggage storage will be available. + + +## Travel + +Cambridge is located closest to London Stansted airport (STN), a major hub for low-cost carriers, but is also reachable from London Heathrow (LHR) via train (approximate travel time: two, to two and a half, hours). More travel information is available from Wikitravel. Clare College itself is accessible from Cambridge railway station. + +* From Stansted, there's an hourly train service from underneath the airport, to Cambridge, and a bus during the night/early morning. +* From Heathrow, you have a few choices: + * Take the tube (Underground, any Picadilly line train) direct to Kings Cross (~75m, ~£6), or the Heathrow Express to Paddington (~15m, £13) and then the tube (Underground, Hammersmith & City or Circle line) to Kings Cross (~20m, ~£2). Once at Kings Cross: + * Saturday & Sunday: Take a mainline train service from Kings Cross to Peterborough, changing at Stevenage for a bus service to Cambridge (~2h, ~£15); the train is unavailable due to engineering works. + * Monday-Friday: Take a mainline train service from Kings Cross to Cambridge (~45m, ~£15). + * Take a National Express bus directly from Heathrow to Cambridge (~2-3h, ~£25.50). +* From Gatwick, take the Gatwick Express (~30m, £15) to Victoria, then the tube (Victoria line, going north, ~20m, ~£4) to Kings Cross. See above for how to get from Kings Cross to Cambridge. +* From Luton, a bus runs straight from Luton airport (~90m, £14) to Cambridge bus station. +* From Paris/Belgium/Netherlands/Köln: Eurostar (~2h15/2h30) to Waterloo, then the tube (Northern line going north, changing to either Picadilly or Victoria lines, ~30m, ~£4) to Kings Cross, and see above for how to get from Kings Cross to Cambridge. You get power sockets, GSM reception, and less hassle than the plane. +For train times, please see nationalrail.co.uk, and nationalexpress.com for bus times. Nationalrail has a [[Printable Pocket Timetable|http://ojp1.nationalrail.co.uk/en/pj/jp]] that seems quite useful. + +You should probably plan to arrive on Sunday night, and leave late Wednesday night or early Thursday morning, as there is a (free for attendees) four-course dinner at the college on Wednesday night. The conference itself will run from roughly 9am to 6pm during the three days. We're also planning some optional social activities for the nights: Cambridge, however, has a stupendous number of pubs, and a great many restaurants, cafés, and other places to hang out (all non-smoking now). + + +## Registration, talks + +If you are coming, or just interested, please subscribe to a [[low-volume mailing list|http://lists.x.org/mailman/listinfo/xds2007]] for updates. Also, please add your name to the [[Attendees|Events/XDS2007/Attendees]] and if you are thinking about giving a talk, add your ideas to the bottom of the [[Program|Events/XDS2007/Program]] pagee. + + +## Links + +* [[Clare College|http://maps.google.com/maps?f=q&hl=en&geocode=&q=trinity+lane,+cambridge,+uk&sll=52.202544,0.131236&sspn=0.085007,0.233459&ie=UTF8&ll=52.207686,0.116258&spn=0.010625,0.029182&t=h&z=15&iwloc=addr&om=1]] map +* [[Clare College information|http://www.clare.cam.ac.uk]] +* [[Cambridge travel information|http://wikitravel.org/en/Cambridge_(England)]] from Wikitravel +* [[Cambridge information|http://en.wikipedia.org/wiki/Cambridge]] from Wikipedia +* [[UK Train Times|http://www.traintimes.org.uk]]
\ No newline at end of file diff --git a/Events/XDS2008.mdwn b/Events/XDS2008.mdwn new file mode 100644 index 00000000..38b6934c --- /dev/null +++ b/Events/XDS2008.mdwn @@ -0,0 +1,52 @@ + + +# XDS 2008 +[[!table header="no" class="mointable" data=""" + [[<< XDC 2008|Events/XDC2008]] | **XDS 2008** | [[XDC 2009 >>|Events/XDC2009]] +"""]] + +The X Developers' Summit for 2008 was held at [[Edinburgh Zoo|http://www.edinburghzoo.org.uk]], [[Edinburgh|http://wikitravel.org/en/Edinburgh]], UK, from the 3rd-5th September. + +* [[Attendees|Events/XDS2008/Attendees]] +* [[Program|Events/XDS2008/Program]] +* [[Notes from the talks|Events/XDS2008/Notes]] +* [[Audio Recordings of the talks|Events/XDS2008/Recordings]] (courtesy of [[Phoronix|http://phoronix.com/]]) +We will run the 3-day summit as a normal conference, with presentations and also birds-of-a-feather group sessions, as well as informal 'corridor sessions', and plenty of time for after-hours social activities. + +Attendance is free, but you must register beforehand, by putting your name on the Attendees page; attendance is currently limited to 60 people. + + +## Accommodation + +Unlike XDS 2007, on-venue accommodation has not been arranged. We will, however, arrange a group booking rate with an affordable and accessible hotel: hold tight. + + +## Travel + +Edinburgh has its [[own airport|http://en.wikipedia.org/wiki/Edinburgh_Airport]] (EDI), 10 miles west of the city. Edinburgh is not an enormous international hub, but there are very frequent services from all London airports (Heathrow, Gatwick, Stansted, City, Luton) with all alliances, decent European connectivity, plus Continental and Delta flights to JFK/Newark. A full list of destinations is available from the airport site. From the airport, the 100 and 35 buses connect you to the city. + +Edinburgh Waverley train station is very close to the city centre, and has good connections to the rest of the UK, including a 4h30m fast east coast service to London, and a ~7h overnight sleeper service. For more details, as well as booking, please check the [[Scotrail site|http://www.firstgroup.com/scotrail/]]. For those under the age of 25, buying a 16-25 Railcard (£20, valid for a year, can halve ticket prices) will likely save you a great deal on a long train journey: more information is available from nationalrail.co.uk. + +Edinburgh Zoo is easily accessible from the centre of the city, with the 12, 26, 31 and 100 (Airlink) [[Lothian buses|http://lothianbuses.com/]] all departing from Princes St; the trip is roughly 15 minutes. + + +## Sponsorship + +As usual, we will be running a travel sponsorship program. If you are unable to afford travel/accommodation on your own, please investigate the cheapest reasonable way for you to get to Edinburgh, and let us know a ballpark price. Full details are in the [[list post|http://lists.x.org/archives/events/2008-July/000000.html]] (note that the deadline is Wed 6th Aug). + + +## Registration, talks + +If you are coming, or just interested, please subscribe to a [[low-volume mailing list|http://lists.x.org/mailman/listinfo/events]] for updates; note that as a general-purpose mailing list, this will be reused for future events, so please remember to unsubscribe afterwards if you don't plan on attending future events. Also, please add your name to the [[Attendees|Events/XDS2008/Attendees]] and if you are thinking about giving a talk, add your ideas to the bottom of the [[Program|Events/XDS2008/Program]] page. + + +## Misc, other + +Scotland uses UK plugs. There will no doubt be all kinds of foreign power boards and adaptors floating around, but please do remember to bring your own. The currency is the British Pound (GBP), and the language mostly resembles English. + +[[Google Maps: Edinburgh Zoo|http://maps.google.co.uk/maps?f=q&hl=en&geocode=&q=edinburgh+zoo&sll=53.800651,-4.064941&sspn=12.061542,28.212891&ie=UTF8&ll=55.946701,-3.225861&spn=0.044602,0.110207&z=13]]. + + +## Contact + +If you have any problems or questions, please contact Daniel Stone -- [[daniel@fooishbar.org|mailto:daniel@fooishbar.org]]. diff --git a/Events/XDS2010.mdwn b/Events/XDS2010.mdwn new file mode 100644 index 00000000..1bbbedac --- /dev/null +++ b/Events/XDS2010.mdwn @@ -0,0 +1,74 @@ + + +# XDS2010: Toulouse, France, September 16-18 +[[!table header="no" class="mointable" data=""" + [[<< XDC 2009|Events/XDC2009]] | **XDS 2010** | [[>> XDC 2011|Events/XDC2011]] +"""]] + +[[!img xds2010-color-small.png] + +The last X Developers' Summit was held at the University of Toulouse 1 Capitole, in France, during September 16th-18th. + +* [[Attendees|Events/XDS2010/Attendees]] +* [[Program|Events/XDS2010/Program]] +* [[Notes|Events/XDS2010/Notes]] +We ran the 3-day summit as a normal conference, with presentations and also birds-of-a-feather group sessions, as well as informal 'corridor sessions', and plenty of time for after-hours social activities. + + +## Venue + +The conference has been held in the "_Colloque - Guy Isaac_" Amphiteather at the old Tobacco Factory (_manufacture des tabacs_ in french) a few hundred meters from the initially planned location. + +See the map below for details. + +The _Guy Isaac_ amphitheater is in the building **I** on [[this map of the Manufacture des Tabacs|http://www.univ-tlse1.fr/94522330/0/fiche___pagelibre/&RH=FR_01-06]]. + + +## Accommodation + +On-venue accommodation will not be arranged. However we provide a [[list of hotels|Events/XDS2010/Hotels]] where you should be able to find rooms at reasonable rates. Use the wiki or the mailing list if you'd like to share rooms and need to find roomates. + + +## Travel + +Toulouse can be reached: + +* By **plane** to the [[Toulouse-Blagnac|http://www.toulouse.aeroport.fr/en]] (TLS) airport. From there you can take the [[flybus|http://www.toulouse.aeroport.fr/airport/access-transport-car-park/access/public-transportation/navette-city-centre]] bus shuttle or a taxi to downtown. + The airport of [[Carcassonne|http://www.carcassonne.aeroport.fr/uk/]] (CCF) hosts a low cost company. It's 90km away from Toulouse, but has good train connections. +* By **train** to the [[Toulouse-Matabiau|http://www.gares-en-mouvement.com/gare.php?gare=frxyt]] station, TGVs run from Paris in 5-6 hours, depending on the schedule. Tickets can be [[purchased on-line|http://www.voyages-sncf.com/]]; as of 2010-08-12, it was possible to get a Paris<->Toulouse round trip in first class for €104, from tgv-europe.com or the much more reliable voyages-sncf.com. Note that the iDTGV is a special 'youth' train, so expect lots of hair gel and bad house music if you book that. +* Avoid the car if possible. It's difficult and expensive to park in the city center and driving in Toulouse may be a nightmare for those who are only used to large and straight avenues. + +## Sponsorship + +As usual, we will be running a [[travel sponsorship program|http://lists.freedesktop.org/archives/xorg-devel/2010-August/011776.html]]. If you are unable to afford travel/accommodation on your own, please investigate the cheapest reasonable way for you to get to Toulouse, and let us know a ballpark price. + + +## Registration, talks + +If you are coming, or just interested, please subscribe to a [[low-volume mailing list|http://lists.x.org/mailman/listinfo/events]] for updates; note that as a general-purpose mailing list, this will be reused for future events, so please remember to unsubscribe afterwards if you don't plan on attending future events. Also, please add your name to the [[Attendees|Events/XDS2010/Attendees]] and if you are thinking about giving a talk, add your ideas to the bottom of the [[Program|Events/XDS2010/Program]] page. + + +## Misc, other + +Toulouse uses [[Type E/F hybrid|http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#Type_E_.2F_F_hybrid]] plugs (CEE7/7) and [[Euro plugs|http://en.wikipedia.org/wiki/Euro_plug]] at 230V/50Hz. There will no doubt be all kinds of foreign power boards and adaptors floating around, but please do remember to bring your own. The currency is the Euro (EUR), and the language is french. Many shops, bars and restaurant speak some level of English. + +[[A Map of Toulouse with the University and a few hotels nearby|http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=109509719165610042544.00046bd61e2c98b82d61e&z=15]] + +[[Touristic informations|http://www.toulouse-tourisme.com/accueil/index_en.php]] to visit Toulouse and the area after/before the summit. + + +## Thanks + +The X.Org foundation thanks the following sponsors who made the event possible: + +* [[Intel|http://www.intel.com]] +* [[Arcapos.ch|http://www.arcapos.ch]] + +## Contact + +If you have any problems or questions, please contact Matthieu Herrb -- matthieu DOT herrb AT laas DOT fr + + +## Downloads + +* [[XDS2010 SVG logo|xds2010-color.svg]]
\ No newline at end of file diff --git a/Events/XDS2010/xds2010-color-small.png b/Events/XDS2010/xds2010-color-small.png Binary files differnew file mode 100644 index 00000000..4a28b924 --- /dev/null +++ b/Events/XDS2010/xds2010-color-small.png diff --git a/Events/XDS2010/xds2010-color.svg b/Events/XDS2010/xds2010-color.svg new file mode 100644 index 00000000..b7dcc628 --- /dev/null +++ b/Events/XDS2010/xds2010-color.svg @@ -0,0 +1,350 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> + +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + width="588.58331" + height="557.48865" + id="svg2547" + sodipodi:version="0.32" + inkscape:version="0.47pre4 r22446" + sodipodi:docname="xds2010-color.svg" + inkscape:output_extension="org.inkscape.output.svg.inkscape" + version="1.1"> + <defs + id="defs2549"> + <linearGradient + id="linearGradient3676"> + <stop + style="stop-color:#e0e0e2;stop-opacity:1;" + offset="0" + id="stop3678" /> + <stop + style="stop-color:#e00000;stop-opacity:0;" + offset="1" + id="stop3680" /> + </linearGradient> + <linearGradient + inkscape:collect="always" + id="linearGradient3662"> + <stop + style="stop-color:#e00000;stop-opacity:1;" + offset="0" + id="stop3664" /> + <stop + style="stop-color:#e00000;stop-opacity:0;" + offset="1" + id="stop3666" /> + </linearGradient> + <linearGradient + id="linearGradient3654"> + <stop + style="stop-color:#000000;stop-opacity:1;" + offset="0" + id="stop3656" /> + <stop + style="stop-color:#000000;stop-opacity:0;" + offset="1" + id="stop3658" /> + </linearGradient> + <linearGradient + id="linearGradient4130"> + <stop + id="stop4132" + offset="0" + style="stop-color:#ffff4f;stop-opacity:0.86274511;" /> + <stop + id="stop4134" + offset="1" + style="stop-color:#fff600;stop-opacity:0;" /> + </linearGradient> + <linearGradient + id="linearGradient4122"> + <stop + style="stop-color:#ff0000;stop-opacity:1;" + offset="0" + id="stop4124" /> + <stop + style="stop-color:#e6af00;stop-opacity:0;" + offset="1" + id="stop4126" /> + </linearGradient> + <inkscape:perspective + sodipodi:type="inkscape:persp3d" + inkscape:vp_x="0 : 372.04724 : 1" + inkscape:vp_y="0 : 1000 : 0" + inkscape:vp_z="1052.3622 : 372.04724 : 1" + inkscape:persp3d-origin="526.18109 : 248.03149 : 1" + id="perspective2556" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient4130" + id="radialGradient3634" + cx="453.75146" + cy="355.98727" + fx="453.75146" + fy="355.98727" + r="266.65195" + gradientTransform="matrix(1,0,0,1.0086379,0,-3.074984)" + gradientUnits="userSpaceOnUse" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient4130" + id="radialGradient3642" + cx="452.02399" + cy="354.8356" + fx="452.02399" + fy="354.8356" + r="274.1377" + gradientTransform="matrix(1,0,0,1.0021004,0,-0.74530549)" + gradientUnits="userSpaceOnUse" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3654" + id="radialGradient3660" + cx="419.20187" + cy="347.34985" + fx="419.20187" + fy="347.34985" + r="279.32016" + gradientTransform="matrix(1,0,0,0.91135425,0,30.791089)" + gradientUnits="userSpaceOnUse" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3662" + id="radialGradient3668" + cx="419.20187" + cy="347.34985" + fx="419.20187" + fy="347.34985" + r="279.32016" + gradientTransform="matrix(1,0,0,0.91135425,0,30.791089)" + gradientUnits="userSpaceOnUse" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3676" + id="radialGradient3682" + cx="382.9248" + cy="344.4707" + fx="382.9248" + fy="344.4707" + r="286.80588" + gradientTransform="matrix(1,0,0,0.94579145,-4.6066138,-31.999495)" + gradientUnits="userSpaceOnUse" /> + </defs> + <sodipodi:namedview + inkscape:document-units="mm" + pagecolor="#ffffff" + bordercolor="#666666" + borderopacity="1.0" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:zoom="0.86831673" + inkscape:cx="623.62297" + inkscape:cy="299.26351" + inkscape:current-layer="layer2" + id="namedview2551" + showgrid="false" + inkscape:window-width="1280" + inkscape:window-height="778" + inkscape:window-x="-1" + inkscape:window-y="0" + inkscape:window-maximized="0" /> + <metadata + id="metadata2553"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <dc:title /> + </cc:Work> + </rdf:RDF> + </metadata> + <g + inkscape:groupmode="layer" + id="layer2" + inkscape:label="Fond" + transform="translate(-152.54991,-76.667113)"> + <rect + style="opacity:0.77777782;fill:#e00000;fill-opacity:1;stroke:#000000;stroke-width:3.54330707;stroke-miterlimit:4;stroke-opacity:0.21076235;stroke-dasharray:none" + id="rect3672" + width="585.03998" + height="553.94531" + x="154.32156" + y="78.438766" /> + <rect + style="opacity:0.77777782;fill:url(#radialGradient3682);fill-opacity:1;stroke:none" + id="rect3674" + width="570.06848" + height="538.97382" + x="93.283936" + y="24.311049" /> + </g> + <g + inkscape:label="Layer 1" + inkscape:groupmode="layer" + id="layer1" + style="display:inline" + transform="translate(-152.54991,-76.667113)"> + <path + d="m 451.96875,343.90625 0,-71.21875 L 340.375,106.75 230.59375,106.65625 392.0625,349.9375 l 55.65625,0 4.25,-6.03125 z" + id="path2737" /> + <path + d="m 450.34375,359.875 0,73.625 109.84375,164.71875 109.78125,0 -159.90625,-241.75 -57.3125,0 -2.40625,3.40625 z" + id="path4040" /> + <g + style="fill:#fcef3c;fill-opacity:1;stroke:#000000;stroke-width:1.88821995;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;display:inline" + transform="matrix(1.588788,0,0,1.588808,-3046.2811,-670.20233)" + id="g16252"> + <path + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.88821995;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + d="m 2201.4845,500.70333 c -4.7445,0 -9.4057,0.2639 -14.0313,0.71875 -0.2868,12.97986 -10.9206,23.43752 -23.9687,23.4375 -5.1093,-8e-5 -9.8347,-1.63974 -13.7188,-4.375 -2.2056,-2.45229 -4.4786,-4.85284 -6.8125,-7.1875 -5.4822,2.48316 -10.7899,5.30529 -15.875,8.4375 1.8116,1.69271 3.5803,3.41917 5.3125,5.1875 0.9351,1.11745 1.9518,2.14558 3,3.15625 0.068,0.0658 0.1188,0.15342 0.1875,0.21875 22.38,24.1556 37.657,54.94886 42.5,89.125 -38.3346,-5.42977 -72.4383,-23.98976 -97.6562,-50.96875 -3.1307,5.08128 -5.9862,10.36584 -8.4688,15.84375 2.0007,1.9988 4.0376,3.96832 6.125,5.875 3.3757,4.13081 5.4062,9.41583 5.4063,15.15625 -1e-4,13.06932 -10.491,23.68449 -23.5,23.9375 -0.425,4.47328 -0.6251,9.00982 -0.625,13.59375 0,4.89355 0.2352,9.73331 0.7187,14.5 12.9652,0.30349 23.4062,10.93119 23.4063,23.96875 -1e-4,4.66188 -1.3433,9.01161 -3.6563,12.6875 -2.694,2.39906 -5.3195,4.86243 -7.875,7.4063 2.5682,5.6668 5.5205,11.1335 8.7813,16.375 25.1633,-26.77177 59.0893,-45.19557 97.2187,-50.62505 -5.5898,37.99185 -24.0768,71.78525 -50.875,96.81255 5.093,3.1371 10.4149,5.9515 15.9063,8.4375 2.038,-2.0283 4.0306,-4.0928 5.9687,-6.2188 4.1126,-3.3169 9.3155,-5.3124 15,-5.3125 13.0587,10e-5 23.6679,10.4742 23.9375,23.4688 4.4835,0.4269 8.999,0.6562 13.5938,0.6562 4.8935,0 9.7333,-0.2665 14.5,-0.75 0,-3e-4 0.031,3e-4 0.031,0 0.3203,-12.9502 10.9108,-23.375 23.9375,-23.375 4.6794,10e-5 9.0341,1.3899 12.7188,3.7188 2.3852,2.6766 4.844,5.2811 7.375,7.8125 5.6759,-2.571 11.1569,-5.5156 16.4062,-8.7813 -26.5665,-24.9688 -44.9135,-58.5778 -50.5,-96.34375 37.7562,5.58971 71.3818,23.91034 96.3438,50.46875 3.2615,-5.2462 6.1822,-10.7342 8.75,-16.4062 -2.3226,-2.32558 -4.7095,-4.58075 -7.1563,-6.7813 -2.7264,-3.88977 -4.3437,-8.61826 -4.3437,-13.71875 10e-5,-13.03745 10.441,-23.63489 23.4062,-23.9375 0.4548,-4.62558 0.6875,-9.31801 0.6875,-14.0625 0,-4.73391 -0.2347,-9.4157 -0.6875,-14.03125 -12.9653,-0.30344 -23.4062,-10.93116 -23.4062,-23.96875 10e-5,-5.12497 1.6243,-9.8592 4.375,-13.75 2.4304,-2.18711 4.8158,-4.43881 7.125,-6.75 -2.486,-5.49134 -5.3004,-10.81321 -8.4375,-15.90625 -1.7668,1.89537 -3.5818,3.7532 -5.4375,5.5625 -1.0978,0.93785 -2.1643,1.92066 -3.1563,2.96875 -23.9289,22.14845 -54.3982,37.33603 -88.1875,42.3125 5.4331,-38.12885 23.8756,-72.06549 50.6563,-97.21875 -5.2482,-3.26636 -10.7314,-6.20943 -16.4063,-8.78125 -2.3091,2.31661 -4.5599,4.69301 -6.75,7.125 -3.9111,2.77508 -8.6935,4.43741 -13.8437,4.4375 -13.0481,-1.7e-4 -23.6514,-10.45766 -23.9375,-23.4375 -4.6256,-0.45485 -9.3181,-0.71875 -14.0625,-0.71875 z m 0,14.40625 c 5.4852,14.65345 19.2193,25.25893 35.5312,26.25 -18.591,27.8166 -29.7948,60.96631 -30.7187,96.6875 35.7195,-0.91794 68.9048,-12.07803 96.7187,-30.65625 1.0096,16.28659 11.6475,29.97823 26.2813,35.46875 -14.6483,5.48332 -25.2839,19.1956 -26.2813,35.5 -27.8138,-18.5782 -60.9991,-29.76931 -96.7187,-30.6875 0.9235,35.7122 12.1362,68.87535 30.7187,96.68755 -16.1071,1.1604 -29.6178,11.7696 -35.0625,26.2812 -5.5304,-14.7738 -19.4178,-25.4737 -35.9062,-26.3125 18.5586,-27.8036 29.7016,-60.9561 30.625,-96.65625 -35.7135,0.92401 -68.8445,12.13636 -96.6563,30.71875 -1.1604,-16.10716 -11.7698,-29.6178 -26.2812,-35.0625 14.7805,-5.53279 25.4823,-19.43906 26.3125,-35.9375 27.8043,18.56783 60.9271,29.73277 96.625,30.65625 -0.9242,-35.72327 -12.0746,-68.8717 -30.6563,-96.6875 16.2943,-1.00304 29.9763,-11.61102 35.4688,-26.25 z" + id="path14367" /> + <g + style="fill:#fcef3c;fill-opacity:1;stroke:#000000;stroke-width:1.88821995;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="g16238"> + <path + transform="matrix(0.775253,0,0,0.81501,1089.4,186.8612)" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + sodipodi:ry="19.5" + sodipodi:rx="20.5" + sodipodi:cy="387.86218" + sodipodi:cx="1434.5" + id="path14388" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546897;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + sodipodi:type="arc" /> + <path + transform="matrix(0.671389,-0.387627,0.407505,0.705818,1010.393,804.0035)" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + sodipodi:ry="19.5" + sodipodi:rx="20.5" + sodipodi:cy="387.86218" + sodipodi:cx="1434.5" + id="path14390" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37547016;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + sodipodi:type="arc" /> + <path + transform="matrix(-0.671389,-0.387627,0.407505,-0.705818,2936.607,1593.817)" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + sodipodi:ry="19.5" + sodipodi:rx="20.5" + sodipodi:cy="387.86218" + sodipodi:cx="1434.5" + id="path14392" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37547016;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + sodipodi:type="arc" /> + <path + transform="matrix(-0.775254,-4.402797e-7,4.628583e-7,-0.815011,3313.6,1098.86)" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + sodipodi:ry="19.5" + sodipodi:rx="20.5" + sodipodi:cy="387.86218" + sodipodi:cx="1434.5" + id="path14394" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546611;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + sodipodi:type="arc" /> + <path + transform="matrix(-0.671389,0.387627,-0.407505,-0.705819,3392.606,481.716)" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + sodipodi:ry="19.5" + sodipodi:rx="20.5" + sodipodi:cy="387.86218" + sodipodi:cx="1434.5" + id="path14396" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546873;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + sodipodi:type="arc" /> + <path + sodipodi:type="arc" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546802;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path14398" + sodipodi:cx="1434.5" + sodipodi:cy="387.86218" + sodipodi:rx="20.5" + sodipodi:ry="19.5" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + transform="matrix(-0.387628,0.671389,-0.705819,-0.407505,3152.458,-92.24858)" /> + <path + sodipodi:type="arc" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546611;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path14400" + sodipodi:cx="1434.5" + sodipodi:cy="387.86218" + sodipodi:rx="20.5" + sodipodi:ry="19.5" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + transform="matrix(-4.402797e-7,0.775254,-0.815011,-4.628583e-7,2657.502,-469.2423)" /> + <path + sodipodi:type="arc" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546873;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path14402" + sodipodi:cx="1434.5" + sodipodi:cy="387.86218" + sodipodi:rx="20.5" + sodipodi:ry="19.5" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + transform="matrix(0.387627,0.671389,-0.705819,0.407505,2040.357,-548.2492)" /> + <path + transform="matrix(0.671389,0.387628,-0.407505,0.705819,1466.393,-308.0995)" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + sodipodi:ry="19.5" + sodipodi:rx="20.5" + sodipodi:cy="387.86218" + sodipodi:cx="1434.5" + id="path14404" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546802;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + sodipodi:type="arc" /> + <path + sodipodi:type="arc" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37547016;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path14406" + sodipodi:cx="1434.5" + sodipodi:cy="387.86218" + sodipodi:rx="20.5" + sodipodi:ry="19.5" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + transform="matrix(0.387627,-0.671389,0.705818,0.407505,1250.543,1377.968)" /> + <path + sodipodi:type="arc" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37546897;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path14408" + sodipodi:cx="1434.5" + sodipodi:cy="387.86218" + sodipodi:rx="20.5" + sodipodi:ry="19.5" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + transform="matrix(1.565175e-7,-0.775253,0.81501,1.645442e-7,1745.499,1754.96)" /> + <path + sodipodi:type="arc" + style="fill:#fcef3c;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:2.37547016;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path14410" + sodipodi:cx="1434.5" + sodipodi:cy="387.86218" + sodipodi:rx="20.5" + sodipodi:ry="19.5" + d="m 1455,387.86218 c 0,10.76956 -9.1782,19.5 -20.5,19.5 -11.3218,0 -20.5,-8.73044 -20.5,-19.5 0,-10.76955 9.1782,-19.5 20.5,-19.5 11.3218,0 20.5,8.73045 20.5,19.5 z" + transform="matrix(-0.387627,-0.671389,0.705818,-0.407505,2362.644,1833.966)" /> + </g> + </g> + <path + d="m 450.34375,359.875 -25.3125,35.65625 25.3125,37.96875 0,-73.625 z" + id="path4071" /> + <path + d="m 451.96875,343.90625 24.5,-34.78125 -24.5,-36.4375 0,71.21875 z" + id="path4065" /> + <path + d="M 630.21875,106.4375 452.75,356.46875 l 57.3125,0 -9.84375,-14.875 166.5625,-235.15625 -36.5625,0 z" + id="path2644" /> + <path + d="m 447.71875,349.9375 -55.65625,0 L 401.40625,364 235.5,598.0625 l 37.5,0 174.71875,-248.125 z" + id="path4034" /> + </g> +</svg> diff --git a/ExaStatus.mdwn b/ExaStatus.mdwn new file mode 100644 index 00000000..cfdce729 --- /dev/null +++ b/ExaStatus.mdwn @@ -0,0 +1,66 @@ + +[[EXA|http://lists.freedesktop.org/archives/xorg/2005-June/008356.html]] support status for various drivers. To help out, take a driver that isn't started, or improve one of the patches below, or port the code from KAA or XAA. Documentation is in xorg git under xserver/xorg/hw/xfree86/doc/devel/exa-driver.txt and found in doxygen from in the exa.h header. + +If you want to test, you will need at least +[[!format txt """ + Option "AccelMethod" "exa" +"""]] +in your card's `Device` section in `xorg.conf`. Do *not* try `Load "exa"` because it will fail. You may also want to enable Composite, by saying +[[!format txt """ +Section "Extensions" + Option "Composite" "enable" +EndSection +"""]] +Supported: + +* i128 (Solid and Copy only so far, incompatible with DGA, only tested on T2``R4 cards) +* radeon (r1xx-r7xx with Render accel) +* sis (sis/xgi; Solid and Copy only) +* trident cyberblade and xp4 (Solid and Copy only) +* via (Solid, Copy, Render) +* savage (Solid, Copy, UTS) +* mach64 (Solid, Copy, Render. [[DFS|https://bugs.freedesktop.org/show_bug.cgi?id=8414]] pending) +* mga (Solid, Copy, UTS. [[Render|https://bugs.freedesktop.org/show_bug.cgi?id=1293]] pending) +* siliconmotion (Solid, Copy. UTS pending) +* i810/intel (Solid, Copy, Render) +* nouveau (Solid, Copy, UTS/DFS on nv0x, Render on newer cards) +* geode (GX and LX variants, Copy/Solid/Composite) - [[README|http://cgit.freedesktop.org/xorg/driver/xf86-video-geode/tree/README]], [[code|http://cgit.freedesktop.org/xorg/driver/xf86-video-geode/tree/src]] +Work in progress: + +* [[tdfx|http://c133.org/tmp/tdfx_exa.patch]] +* [[s3virge|http://git.sh0n.net/]] (Copy only currently) <-- link died ? +* [[r128|http://www.botchco.com/alex/2006soc/]] Joseph Garvin SoC +No work started, but capable of Render acceleration: + +* glide +* glint (supported in KAA), Coming soon ([[ShawnStarr|ShawnStarr]]) +* i740 +* imstt +* newport +* impact +* rendition +* trident (supported in KAA) +* voodoo +No work started, some chips might be capable of Render acceleration: + +* apm (via the voodoo rush) +* cirrus (laguna?) +* neomagic (256XL+ was the only one with a 3D engine) (supported in KAA) +* cyrix/nsc (new GX2s have an alpha combiner) +* sun{ffb,leo} +No work started, no Render acceleration possible: + +* ark +* chips (supported in KAA) +* s3 (supported in KAA) +* sun{bw2,cg14,cg3,cg6,tcx} (tcx has some EXA support in NetBSD tree: [[WebCVS Link|http://cvsweb.netbsd.org/bsdweb.cgi/xsrc/external/mit/xf86-video-suntcx/dist/src/?only_with_tag=MAIN]]) +* tga +* tseng +Probably unsuitable for EXA support: + +* dummy +* fbdev +* vesa +* vga +* vmware +* wsfb
\ No newline at end of file diff --git a/FAQ.mdwn b/FAQ.mdwn new file mode 100644 index 00000000..ee5c1a2f --- /dev/null +++ b/FAQ.mdwn @@ -0,0 +1,87 @@ + + +# X.Org User FAQ + + * If you have problems getting X to start please make sure you have configured your X using one of the available configuration tools. If you are uncertain you did please check the [[ConfigurationHelp|ConfigurationHelp]] before you read any further. + * You can find driver related information in the [[KnowledgeBase|KnowledgeBase]]. + * If you are using a version of X.Org shipped by a distribution you should check there [[DistroFAQList|DistroFAQList]], too, before you report an error. + * If you cannot find an answer to your problem here feel free to subscribe to our [[SupportMailingList|SupportMailingList]]. Please follow the instructions given there on how to post a support question. + * X server information is usually logged in **/var/log/Xorg.0.log**, which can be consulted for errors or warnings if the server does not function as expected. + * If you want to add information don't add it to this page. Try to find a category it belongs to. If you cannot find any that fits feel free to create a new one on this page. + +# FAQ + +<a name="networktransparencyisslow"></a> +## hay guys why do u still hav network transparency dont you know its making everyfing slow + +Network transparency is actually not the problem: pretty much all inter-process communication uses local UNIX sockets and shared memory, which is ... exactly what X uses! Shocked. + +A lot of the problems with X are related to round trips: many events that X sends to clients are actually just prompts for clients to send another request, block, and wait for a reply actually containing the information you need. In turn, those requests will probably get stuck behind rendering requests from other clients, adding huge amounts of latency. Also, many operations look something like this: request from client A -> event sent to client B -> request sent from client B -> reply sent to client B -> request sent from client B -> client A's original request fulfilled. So, by the time you've scheduled ten times, a perceptible amount of time has actually passed. + +tl;dr: It doesn't. + + +## How to clone and build Xorg + + * See Peter's instructions at: [[Quickstart for those that do not use jhbuild|http://lists.x.org/archives/xorg-devel/2009-August/001826.html]] + +[[!format txt """ + # Quickstart for those that do not use jhbuild: + export PREFIX=/opt/xorg + export LD_LIBRARY_PATH=$PREFIX/lib + export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig + export PATH=$PREFIX/bin:$PATH + export ACLOCAL="aclocal -I $PREFIX/share/aclocal" + + git clone git://anongit.freedesktop.org/git/xorg/util/modular/ util/modular + echo "util/macros" > built.modules + ./util/modular/build.sh --clone -p -f built.modules -r `tail -n 1 built.modules` $PREFIX + + # Re-run the last command until a build succeeds. +"""]] + +## How to use XRandR 1.2 (for Dual-Head etc) + + * See the links on the [[XRandR Documentation|http://wiki.x.org/wiki/Projects/XRandR]] page + +## How to set-up a multiseat configuration (aka zaphod mode) + + * See the [[Multiseat|Development/Documentation/Multiseat]] page + +## Server doesn't start and generates an error message + + * [[FAQErrorMessages|FAQErrorMessages]] + +## Server generates warning messages + + * [[FAQWarningMessages|FAQWarningMessages]] + +## Server doesn't set the video mode I would like to use + + * [[FAQVideoModes|FAQVideoModes]] + +## Video Driver FAQ + + * [[VideoDriverFAQ|VideoDriverFAQ]] + +## Migration FAQ + + * [[FAQMigration|FAQMigration]] + +## Proprietary Drivers + + * [[ATI|ATIProprietaryDriver]] + * [[NVIDIA|NVIDIAProprietaryDriver]] + +## Miscellaneous + + * [[FAQMiscellaneous|FAQMiscellaneous]] + * [[UpdateProblems|UpdateProblems]] - Issues that may occur after updating. + +## Advanced Topics + + * [[AdvancedTopicsFAQ|AdvancedTopicsFAQ]] - This is a collection of solutions to advanced setup and configration problems and customizations for special purposes. + +# More FAQs + +For your convenience we collected some links to X related informations on [[OtherFAQs|OtherFAQs]]. diff --git a/FAQErrorMessages.mdwn b/FAQErrorMessages.mdwn new file mode 100644 index 00000000..a9db67a0 --- /dev/null +++ b/FAQErrorMessages.mdwn @@ -0,0 +1,336 @@ + +**If you have a question not listed here, don't post your question here, please use the bugzilla or the mailing list.** + + +# Server doesn't start and generates an error message + +Error messages that don't immediately lead to a fatal server error (and the termination of the server) are marked in the log file by a `(EE)` at the beginning of the line. An error that leads to immediate server termination usually prints the line `Fatal server error:` followed by some explanation. + + +[[!toc ]] + + +## I keep getting the error message: could not open default font 'fixed' + +This is by far the most popular Frequently Asked Question :( + To run X you need at least the font 'fixed' and 'cursor' to display a cursor image and be able to print meaningful error messages. If these fonts are not present the server doesn't start. My Xserver refuses to start and gives me the error message: + + +[[!format txt """ +Fatal server error: +could not open default font 'fixed' +When reporting a problem related to a server crash, please send +the full server output, not just the last messages. +This can be found in the log file "/var/log/Xorg.0.log". +Please report problems to xorg@lists.freedesktop.org. +"""]] +There may be different reasons for this: + + +Somewhere (pretty much at the beginning of the log) there is a message: + + +[[!format txt """ + Could not init font path element unix/:7100, removing from list! +"""]] +This message tells that the Xserver is trying to contact a font server which appearantly isn't running. So you need to get your font server up and running before you start X. How this is done depends heavily on the OS and/or the distribution you use. Please contact your vendor support on how to do this! + Please note: The use of the font server `xfs` is deprecated due to several bugs in it. It is recommended that the Xserver loads the fonts directly. To do so add at least the lines: + + +[[!format txt """ + FontPath "/usr/X11R6/lib/X11/fonts/misc/" + FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" + FontPath "/usr/X11R6/lib/X11/fonts/Type1/" + FontPath "/usr/X11R6/lib/X11/fonts/CID/" + FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" + FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" +"""]] +to the `"Files"` section of your `xorg.conf` file. + + +The Debian package xfonts-base puts these fonts in /usr/share/fonts/X11. If this is the package you are using, the [[FontPaths|FontPaths]] should instead be + + +[[!format txt """ + Fontpath "/usr/share/fonts/X11/misc" + FontPath "/usr/share/fonts/X11/Type1/" + FontPath "/usr/share/fonts/X11/75dpi/" + FontPath "/usr/share/fonts/X11/100dpi/" +"""]] +There is also a possibility that the [fontpath]/misc/fonts.alias file is missing. This can cause the X server to not find the alias of 'fixed' to whatever is the actual fixed font. + + +[[!format txt """ + fixed -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-1 +"""]] + + +--- + + + +* If you see a messages like: + +[[!format txt """ +(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist. + Entry deleted from font path. +"""]] +it means that this font path element either does not exist or isn't readable. Normally it is no problem if some font path elements listed in your `xorg.conf` are missing. However if `/usr/X11R6/lib/X11/fonts/misc/` is missing the `cursor` and the `fixed` fonts are missing, too, therefore the server cannot start. Therefore please make sure that this directory exists and is readable. To have a good selection of standard fonts you should have at least the directories listed above. If you need non-latin character sets more fonts may be required. + + + +--- + + + +* Please also check for messages like: + +[[!format txt """ + (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local/"\ +. + Entry deleted from font path. + (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local/"). +... + Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from\ + list! +"""]] +These tell you that the fonts were probably not installed correctly. Please do as suggested and run + + +[[!format txt """ + mkfontdir /usr/X11R6/lib/X11/fonts/local/ +"""]] +Please replace `/usr/X11R6/lib/X11/fonts/local/` with the directories listed in your log file. You should do this for every directory listed. + + + +--- + + If adjusting the paths in the xorg.conf file didn't fix it, try the following. It essentially rebuilds the fonts.dir and fonts.scale files and force refreshes the cache. + + +[[!format txt """ + cd /usr/share/fonts/misc + mkfontscale . + mkfontdir -e /usr/share/fonts/encodings -e /usr/share/fonts/encodings/large . + /usr/bin/fc-cache -f +"""]] + + +--- + + + +* Some additional resources: +* [[XFree86 Font De-uglification HOWTO|http://feenix.burgiss.net/ldp/fdu/]] +* [[XFS man page for X 4.3.0|http://www.freedesktop.org/~xorg/current/doc/xfs.1.html]] +* [[Red Hat v9.0 documentation regarding fonts|http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-x-fonts.html]] +* [[Xorg man page for X 4.3.0|http://www.freedesktop.org/~xorg/current/doc/Xorg.1.html]] + +## I keep getting the message: "kernel module version is 1.1.1 but 1.3.1 or later is preferred." + +Your DRM kernel driver version is older than the one desired by your Xorg driver. You should get a later DRM module version. + If you are using a distribution and X and your kernel were shipped by your distribution vendor you should contact your vendor support to find out how to fix this problem. + If you've built X and/or the kernel yourself you should make sure the kernel is recent enough. + + +## I keep getting the message: "AddScreen/ScreenInit failed for driver 0" + +You get an error message like: + + +[[!format txt """ +(EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 12012) +Fatal server error: +AddScreen/ScreenInit failed for driver 0 +"""]] +This kind of problem typically occurs when you're using a big monitor with an old graphics card. You can solve it by deleting some of the highest resolutions of the deepest colour mode in the `Screen` section of your `xorg.conf`, or even the whole last `Display` subsection. + + +## I keep getting the message: "failed to initialize core devices" + +You get an error message like: + + +[[!format txt """ +(EE) xf86OpenSerial: Cannot open device Logitech + No such file or directory. +(EE) Mouse1: cannot open input device +(EE) PreInit failed for input device "Mouse1" +(II) UnloadModule: "mouse" +(II) Keyboard "Keyboard1" handled by legacy driver +(WW) No core pointer registered +No core pointer +Fatal server error: +failed to initialize core devices +"""]] +The message `xf86OpenSerial: Cannot open device Logitech` tells you that the input device 'Logitech' cannot be opened. The next line tells you why: `No such file or directory.` There is no such device. Device names usually start with `/dev/`. The device name itself depends on the device you use, your OS and the distribution you use. Usually there os a symlink from `/dev/mouse` to the correct device. If you are using a distribution it usually comes with a configuration tool for X, so you may just want to rerun the configuration tool to correct the setup. + Please note: Usually the server refuses to start if there is no core pointer device. You can change this by adding the line: + `Option "AllowMouseOpenFail" "1"` + to the `ServerFlags` section of your `xorg.conf`. + +Note: Be sure you have either hotplug or udev installed. If you don't, you will have problems detecting mice and video hardware. + + +## I keep getting the message: "Server is already active for display 0" + +<a name="AlreadyActive"></a> You get an error message like: + + +[[!format txt """ +Fatal server error: +Server is already active for display 0 + If this server is no longer running, remove /tmp/.X0-lock + and start again. +"""]] +The number denotes the display number (in this case 0). This number needs to be unique on the system, so you cannot run two servers on one system with identical display numbers. This message indicates that there is already a server with this number running on the system. You can verify this by running + + +[[!format txt """ + ps aux | grep `cat /tmp/.X0-lock` +"""]] +If you see an output like: + + +[[!format txt """ +root 2283 0.5 5.1 27796 6536 ? S Apr21 59:03 [X] +"""]] +it indicates that there is indeed an Xserver running under this PID. To start a second server on the same system you have to give it a different dislay number. If you start your servers using startx you can do + + +[[!format txt """ +startx -- :1 +"""]] +to start a server with display number 1. If you are sure there is no other server running on your system and above ps command indicates that no server with this PID is running, you should remove the file `/tmp/.X0-lock` by doing (as 'root'): + + +[[!format txt """ +rm -rf /tmp/.X0-lock +"""]] + +## I keep getting the message: "Cannot establish any listening sockets..." + +You get an error message like: + + +[[!format txt """ +_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed +_XSERVTransMakeAllCOTSServerListeners: server already running +Fatal server error: +Cannot establish any listening sockets - Make sure an X server isn't already running +"""]] +This problem is very similar to the [[previous one|FAQErrorMessages]]. You will get this message possibly because the lock file was removed somehow or some other program which doesn't create a lock file is already listening on this port. You can check this by doing a `netstat -ln`. Xservers usually listen at tcp port 6000+<Display Number>, therefore if you have started your Xserver with the command line option `:1` it will be listening on port 6001. + Please check the [[article above|FAQErrorMessages]] for further information. + + +## I keep getting the message "Unable to load required base modules, Exiting..." + +You get an error message like: + + +[[!format txt """ +(II) Loading /usr/X11R6/lib/modules/libpcidata.a +(II) Module pcidata: vendor="The X.Org Foundation" + compiled for 6.7.0, module version = 1.0.0 + ABI class: X.Org Video Driver, version 0.6 +Fatal server error: +Unable to load required base modules, Exiting... +"""]] +This means that the server has problems loading a module. The message immediately above tells you which module it was. The most likely cause is that the module doesn't exist. You may therefore try to reinstall your Xserver modules. + + +## I keep getting the message: "no screens found" + +This is a very general message telling you that something went wrong and there is no screen left which the server can successfully drive. Usually you'll see another error message describing what went wrong in more detail: + + +### Message: "No devices detected" + +You get an error message like: + + +[[!format txt """ +(EE) No devices detected. +Fatal server error: +no screens found +"""]] +It is very likely that your `xorg.conf` file doesn't contain the correct driver(s) for the chipset(s) in your system or that your chipset isn't supported by any of the drivers. + You can check for the detected devices in the log file (in most cases `/var/log/Xorg.0.log`) by looking for lines like: + `(--) PCI:*(1:0:0) Neomagic Corporation NM2200 [MagicGraph 256AV] rev 32, Mem @ 0xfd000000/24, 0xfe800000/22, 0xfec00000/20` + In this example the active video device (the one with the `*`) is a Neomagic NM2200 video chip. In order to get this chipset to work you'd have to use the _neomagic_ driver. + <a name="ConfigurationHelp"></a> If you are using a distribution you should rerun its configuration tool. If there is no such tool, or if it keeps configuring your Xserver wrong you may want to try `xorgcfg`, the graphical tool shipped with Xorg. You can also let the server generate a config file: as root just run `X -configure`. + Please note: If you appear to use the correct driver and you still keep getting this message it is very likely that your chipset isn't supported (yet). In this case you may try the `vesa` driver or - if this doesn't work - the `vga` driver. However both are entirely unaccellerated. + + +### Message: "Screen(s) found, but none have a usable configuration. + +You get an error message: + + +[[!format txt """ +(EE) Screen(s) found, but none have a usable configuration. +Fatal server error: +no screens found +"""]] +In most cases this means there are no video modes available for your configuration. Each entry in the list of specified or default video modes gets checked if it lies withing the limit or the hardware: if it lies within the sync range specified or probed for the monitor, if it will work with the memory available on the video card or if the pixel clock lies within the range supported by the chipsets. There are many more limits. For each rejected mode you can see in the log file the reason for rejection: + + +[[!format txt """ +... +(II) VGA(0): Not using default mode "320x200" (vrefresh out of range) +(II) VGA(0): Not using default mode "720x400" (insufficient memory for mode) +(II) VGA(0): Not using default mode "360x200" (hsync out of range) +... +"""]] +In most cases the monitor ranges are the reason why your modes where rejected. Please try to extend these ranges carefully until you get a working mode. Please note: on older monitors you need to be careful extending the ranges as it can be easily destroyed. There may be other reasons why you get this message. + +* If the specified depth is not supported with your hardware. In this case try depth 8, or if you +* are using the `vga` driver even depth 4. + * If you specified a combination of options the driver cannot handle. + * If loading of a required sub module wasn't successful. In this case you'll get a message that the loading failed. Please try to investigate, why. The message may give you a clue: you may be using the wrong version of the module, or the file may not exist. + +### Message: "Unable to locate/open config file" + +You are getting the message: + + +[[!format txt """ +(EE) Unable to locate/open config file +(EE) Error from xf86HandleConfigFile() +"""]] +This means that the Xserver cannot find a configuration file because it has not been properly configured. Please check [[FAQMiscellaneous|FAQMiscellaneous]] for information how to configure your Xserver. + Another reason for this error may be that you have created a configuration file but it is not in the correct location. The Xserver checks for configuration files at different locations. The usual locations are: `/etc/X11/xorg.conf` or `/etc/X11/XF86Config-4`. + Another reason for this message may be that your Xserver cannot read the file because the server binary has the wrong permission. On UN*X like systems the server is usually owned by `root` and runs with the SUID bit set so that it runs with root privileges even if started by an ordinary user. Therefore it should be able to open the configuration file regardless of who owns it or of its permissions. Please check "How do I check if my server bianry has the correct permissions?" on the [[FAQMiscellaneous|FAQMiscellaneous]] page for futher information + + +### Message: "Error from xf86HandleConfigFile()" + +You are getting the message: + + +[[!format txt """ +(EE) Unable to locate /open config file +(EE) Error from xf86HandleConfigFile() +Fatal server error +no screens found +"""]] +This indicates that you have a problem with your config file. It either doesn't exist, in which case you'll additionally see the message: + + +[[!format txt """ +(EE) Unable to locate /etc/X11/xorg.conf config file +"""]] +or your config file contains a typo. In this case you see the message: + + +[[!format txt """ +(EE) Problem parsing the config file +"""]] +You are even told where the error was: + + +[[!format txt """ +Parse error on line 3 of section ServerLayout in file /etc/X11/xorg.conf + "Idntifier" is not a valid keyword in this section. +"""]] +You can then either correct the config file or regenerate the config file. How to do this is described [[here|FAQErrorMessages]]. diff --git a/FAQMigration.mdwn b/FAQMigration.mdwn new file mode 100644 index 00000000..84646aeb --- /dev/null +++ b/FAQMigration.mdwn @@ -0,0 +1,28 @@ +## I want to migrate to X.Org, what do I have to do? + +### I've used XFree86 [TM] before now I want to use X.Org. + +If you have a working setupt for XFree86[TM] you can reuse it without many changes. Just build and install the X.Org source tree. + +Files and option names that contain `xf86` or `xfree86` have been replaced but the old names are still accepted. Therefore your old configuration files and startup scripts don't have to be modified.<br> There is one exception, though: The server binary is not called `XFree86` any more but `Xorg` therefore you may have to change the soft link that points to your real Xserver binary. This soft link usually lives under `/var/X11R6/bin`. If your Xserver binary is located in /usr/X11R6/bin/ simply do: + + ln -sf /usr/X11R6/bin/Xorg /var/X11R6/bin/X + +#### Which options and file names have changed now? + +* The server name has been changed to `Xorg`. +* The keyboard rules file (usually under `/usr/X11R6/lib/X11/xkb/rules`) is now called xorg (a softlink is created to the file name that has been used by XFree86[TM] for backward compatibility. +* The command line option to specify the server config file name has been changed to `-config`. +* The default configuration file is now called `xorg.conf`. The search path and appendices have not changed. + +#### Are there known problems so far? + +Some programs seem to make use of the description files for the xkb rules and have the file names hardcoded to the names used bu XFree86[TM](`xfree86.lst` and `xfree86.xml`). The names of those files have also been changed but the installation procedure for X.Org Release 6.7 doesn't create a compatibility link. Therefore you should create these links by hand: + + ln -sf /usr/X11R6/lib/X11/xkb/rules/xorg.lst /usr/X11R6/lib/X11/xkb/rules/xfree86.lst + ln -sf /usr/X11R6/lib/X11/xkb/rules/xorg-it.lst /usr/X11R6/lib/X11/xkb/rules/xfree86-it.lst + ln -sf /usr/X11R6/lib/X11/xkb/rules/xorg.xml /usr/X11R6/lib/X11/xkb/rules/xfree86.xml + +### I'm using a vendor supplied system, what else do I have to change? + +If you have a working configuration of XFree86[TM] running on your system just follow the steps described. Some vendors use configuration utilities which make assumptions about the name of the server binary and the name of the server log file. Those utilities may not work any longer after you have installed X.Org. Please contact your system vendor for a updated versions of these tools. -- Main.[[EgbertEich]] - 11 Jun 2004 diff --git a/FAQMiscellaneous.mdwn b/FAQMiscellaneous.mdwn new file mode 100644 index 00000000..2057227e --- /dev/null +++ b/FAQMiscellaneous.mdwn @@ -0,0 +1,109 @@ + + +# Miscellaneous + +[[!toc ]] + + +## I don't know my hardware, how can I configure X? + +Don't worry, todays configuration tools do a pretty good job detecting hardware automatically. If you are using a distribution you will want to try the configuration tools provided by your distribution vendor first. If these don't work or if your vendor doesn't provide any you can use the tools shipped with X.Org. You may want to use the graphical tool `xorgcfg` to do your Xserver configuration or you may let the server generate it's own configuration file by running: `X -configure` as root. It will create the configuration file `xorg.conf.new` in the home directory of the user who ran it (usually root). You should then copy this file to the default location `/etc/X11/xorg.conf`. + +Please note: Xorg can only autodetect PCI and AGP video chipsets. If you still use an ISA/EISA/VL chipset you need to at least know the chipset vendor to specify the correct driver. Most drivers can then autodetect the chipset model. + + +## How do I set the correct permissions of my Xserver binary? + +On UN*X like systems the server is usually owned by `root` and runs with the SUID bit set so that it runs with root privileges even if started by an ordinary user. To check if your Xserver has the right permissions you have to locate the server binary. Usually the soft link `/var/X11R6/bin/X` points to the binary. Please do +[[!format txt """ + ls -l /usr/X11R6/bin/X +"""]] +obtain the binary the link points to (usually `/usr/X11R6/bin/Xorg` and do a: +[[!format txt """ + ls -l /usr/X11R6/bin/Xorg +"""]] +(Replace `/usr/X11R6/bin/Xorg` with the name of the binary pointed to by the link.) The result should look something like this: +[[!format txt """ + -rws--x--x 1 root root 2019033 2003-03-17 14:26 /usr/X11R6/bin/Xorg +"""]] +This file is owned by the user 'root' and has the SUID bit set (the 's' in `-rws--x--x`. If either one isn't true you need to fix this. Do +[[!format txt """ + chown root:root /usr/X11R6/bin/Xorg +"""]] +To make root owner of the file. (You have to be 'root' to do so). And +[[!format txt """ + chmod u+s /usr/X11R6/bin/Xorg +"""]] +to set the SUID bit. (Here again you may have to replace `/usr/X11R6/bin/Xorg` by the name of the binary you are using.) + + +## When I start X can I get the root window display a solid color instead of the 'root cross stitch'? + +Starting with version XFree86 4.3 there is the command line switch `-br` for the Xserver that changes the root window to a solid black. If you use `startx` please do: +[[!format txt """ +startx -- -br +"""]] +Please note: It is not easy to use any other color than black or white. At this point there is no other colormap entry than black or white in the colormap. + + +## My keyboard is dead, what can I do? + + +### I've upgraded to Xorg R6.7, now my keyboard is dead. + +You need a new set of keyboard description files in `/usr/X11R6/lib/X11/xkb/` that come with Xorg R6.7. Chances are that when you upgraded these files didn't get installed correctly. Try to reinstall these files and restart your Xserver. + + +### My keyboard is still dead. + +There may be several reasons for this: You have an entry for a PS/2 mouse (on Linux on /dev/psaux) in your `xorg.conf` however you don't have a PS/2 mouse connected. This is actually a kernel problem. You should remove this device from your `xorg.conf`. + + +## I seem to be unable to allocate a sufficient number of colors in 8 bit. + +The RENDER extension preallocates some entries in the default colormap of the PseudoColor modes. This limits the number of entries available to clients. Some older 8bit clients are optimized for 254 entries in the 8bit palette (two are aloways set to white and black). If they cannot allocate all their colors they don't display correctly. In some cases changing a colormap entry is used to make certain objects blink. If there are not sufficient entries this blinking may not work. <br> You should make your software use a private colormap. If this isn't possible you can reduce the number or preallocated entries with a command line option to the Xserver: if you use `startx` to start your Xserver you can do: <br> +[[!format txt """ +startx -- -render mono +"""]] +Please note that transparency or antialiasing may not work in this case. + + +## How do I set up a multihead configuration? + +I think there was a multihead FAQ someplace. I wonder where that's at? <br> Basically, you can have in the `xorg.conf` file: + + 1. monitor section for that monitor. + 1. device sections. One for each card. Use the !BusID token to specify which card is which. + 1. screen sections. Each referencing the separate card, but both can reference the single monitor section. + 1. server layout section that references both screens, eg: + +[[!format txt """ +Section "ServerLayout" + Identifier "DualHead" + Screen 0 "Screen0" 0 0 + Screen 1 "Screen1" RightOf "Screen0" + InputDevice "Mouse0" "CorePointer" + InputDevice "Keyboard0" "CoreKeyboard" +EndSection +"""]] +Start with a working single head configuration and create the second device and screen sections by cutting and pasting but assigning different Identifiers and, in the case of the device sections, different !BusIDs. Change the layout section to something like above. <br> If you have a single card with one chipset but two (or more) display connectors you have to create device sections for each connector with identical busID. To distinguish between the connectors you need to add the line +[[!format txt """ +Screen n +"""]] +* where `n` is replaced by the number of the connector. (ie. `n`0,1,2...=). + +## How can I configure the Xserver bell (xkbbell) to use the sound subsystem of my computer? (ALSA, OSS, etc.) + +Answer (hopefully) goes here.. :) + + +## How do I find out which process owns a given window? + +The answer to this is not straightforward and depends on which assumptions you are willing/able to make and what your usage model is. The first thing that should be noted is that X is a network service, so it is not enough to simply know the PID alone, you will need to know both the PID and hostname of the client, in case the client is running on a remote machine. + +That said, there is a standard method for X clients to report their hostname and PID. This is via two properties, _NET_WM_PID and WM_CLIENT_MACHINE. The idea behind these properties is that window managers can query them and use them to label windows graphically or otherwise make use of them. Your application code can also query them. However, there are several caveats: + + 1. Their use is recommended but not required. Not all X clients set them. + 1. Applications and toolkits that do set them often do so only on a single window which may not be anywhere close to either the root window or the "leaf" windows reported by mouse events. In this case, use of XQueryTree is required to traverse the window hierarchy to find it. + 1. **Most Importantly, the contents of the properties is entirely within the control of the application itself!** This means that a malicious application could easily report false values! +For anything more secure/robust you will need a server-side solution. Many local socket implementations provide a way to find out the PID of the remote end of a connection, such as getpeerucred(), which are kernel-based and cannot be spoofed. The server has a [[LocalClientCred|LocalClientCred]]() function that will return the values if supported. However, this will not work on remote connections. diff --git a/FAQVideoModes.mdwn b/FAQVideoModes.mdwn new file mode 100644 index 00000000..6e12d3cb --- /dev/null +++ b/FAQVideoModes.mdwn @@ -0,0 +1,164 @@ + + +# Video Modes FAQ + +[[!toc ]] + + +## When I change modes with ctrl-alt-(keypad''+) or ctrl-alt-(keypad''-) I get a virtual screen. I don't want that + +In X the size of the root window (ie. your desktop) is fixed. When you change the video mode using the hotkey sequence of `xvidtune` you therefore get a 'virtual' screen, ie. a screen that is bigger than your desktop and you can use your mouse to 'pan' thru it. + +There now is an extension which allows to change the video mode along with the size of the root window. It is called the _RandR_ extension. You can use `xrandr` to set the desired mode. Use `xrandr --query` to get a list of available modes. With `xrandr --size <width>x<height>` you can pick one of the available resolutions. Try `man 1x xrandr` or `xrandr -help` to get more information on `xrandr`. + +**Please note!** If your application/window manager doesn't support the _RandR_ extension you are likely to lose those windows which are entirely located outside of your new desktop. You can get them back when you restore your desktop to the original size. + + +## Why can't I get a 1400x1050 video mode (or some other size) + +Some drivers are limited to the set of modes in the video BIOS. The most common examples is vesa. Usually there's nothing you can do in this situation, because it's not possible to modify the BIOS. Sorry. The exception is some Intel chips, where you can use the 855resolution or 915resolution hacks, and it might work and it might not. + + +## Obtaining modelines from Xorg log + +The Xorg log may contain the information needed to manually create an optimized modeline. Usually the more user friendly automatic setup tools will do this job for you. But sometimes those tools fail. In those cases you are left with the task of reading the Xorg log file to figure out what to do. + +Using this information does require manually editing the configuration file, but this is not a terribly difficult process. The key is to have a mostly correct configuration file as a starting point. In my situation I had a valid configuration file, but it was for the old monitor. The new LCD panel has a much more limited frequency range than the old monitor, and it could not accept the previous setup. I could have done a full re-install of X (I think), but it was easier to just edit the configuration file. + +I switched into a text mode VT (CTL-ATL-F2), edited the config file, and restarted X. Voila. + +The Xorg log contained + + +[[!format txt """ +(II) R128(0): Supported additional Video Mode: +(II) R128(0): clock: 162.0 MHz Image Size: 432 x 324 mm +(II) R128(0): h''active: 1600 h''sync: 1664 h''sync''end 1856 h''blank''end 2160 h_border: 0 +(II) R128(0): v''active: 1200 v''sync: 1201 v''sync''end 1204 v''blanking: 1250 v''border: 0 +(II) R128(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 170 MHz +(II) R128(0): Monitor name: SyncMaster +(II) R128(0): Serial No: H4JW502073 +(``) R128(0): Using gamma correction (1.0, 1.0, 1.0) +(II) R128(0): Monitor[0]: Using hsync range of 30.00-81.00 kHz +(II) R128(0): Monitor[0]: Using vrefresh range of 56.00-75.00 Hz +(II) R128(0): Clock range: 12.50 to 250.00 MHz +"""]] +I used this information to update the Monitor section and add the appropriate modeline to the Modes section: + + +[[!format txt """ +Section "Monitor" + Option "CalcAlgorithm" "UseFrameBufferTiming" + DisplaySize 432 324 + HorizSync 30-81 + Identifier "Monitor[0]" + ModelName "SyncMaster" + Option "DPMS" + VendorName "Samsung" + VertRefresh 56-75 + UseModes "Modes[0]" +EndSection +"""]] +The `VertRefresh` range, `HorizSync` range, and `DisplaySize` were obtained from the log. I copied the `ModelName` and `VendorName` but these do not really matter. + + +[[!format txt """ + Modeline "1600x1200" 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +"""]] +The name 1600x1200 is just a normal convention. The recommended clock speed of 162.00 and the pixel timings are taken from the log. + + +## Obtaining modelines from Windows program PowerStrip + +If you have a dual boot system and a monitor / graphics card that works fine under MS Windows but you can't figure out the equivalent modeline parameters for Linux, you can use the Windows program Power``Strip. + +I used this to configure X.org to work correctly with my Sun X7200A 20.1" LCD monitor and my Dell C400 Latitude notebook. + +Download and install Power``Strip from + + * [[http://entechtaiwan.net/util/ps.shtm|http://entechtaiwan.net/util/ps.shtm]] +Once installed and running you will see a Power``Strip icon in the system tray. + +With the display using the required settings (for me this was 1600x1200). + +Right Click on the Power``Strip icon in the system tray to display the pop up menu. + +Select sub menu "Display Profiles" then select menu item "Configure" + +The "Display profiles" window will be displayed, click button "Advanced timing options". + +The "Advanced Timing Options" window will be displayed, click button copy timings to clip board (this button is the icon to the right of the "Cancel" button. + +Paste your clipboard somewhere (notepad will do) and have a look. You will see at the end of the pasted data will be the information you need for an Xorg modeline. + +For my setup Power``Strip put the following information in the clipboard +[[!format txt """ +PowerStrip timing parameters: +1600x1200=1600,8,64,104,1200,5,10,24,132000,512 + +Generic timing details for 1600x1200: +HFP=8 HSW=64 HBP=104 kHz=74 VFP=5 VSW=10 VBP=24 Hz=60 + +VESA detailed timing: +PClk=132.00 H.Active=1600 H.Blank=176 H.Offset=-8 HSW=64 V.Active=1200 V.Blank=39 V.Offset=5 VSW=10 + +Linux modeline parameters: +"1600x1200" 132.000 1600 1608 1672 1776 1200 1205 1215 1239 +hsync +vsync +"""]] +As you can see the last line is all you need to know to create a modeline. + +With that information you can boot back into Linux and add the modeline to the monitor section. Within my xorg.conf file I now have: +[[!format txt """ +Section "Monitor" + Identifier "Generic Monitor" + VendorName "Sun" + ModelName "X7200A" + Option "DPMS" + ModeLine "1600x1200" 132.000 1600 1608 1672 1776 1200 1205 1215 1239 +hsync +vsync +EndSection +"""]] + +# Setting up a Dell 2001FP LCD + +Above was followed pretty much as a guide. + +This information is provided to show the variation of Log messages which may appear. + +**Monitor** Dell 2001FP (for 1600x1200) on X.org (Ubuntu Linux) + +**Graphics Card** Intel i810 Card + +The [[ModeLine|ModeLine]] entry needs to go in the +[[!format txt """ + Section "Monitor" +"""]] +The X.org Log entry showed # from the /var/log/Xorg.0.log +[[!format txt """ + (II) I810(0): clock: 162.0 MHz Image Size: 367 x 275 mm + (II) I810(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0 + (II) I810(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0 + (II) I810(0): Serial No: XXXXXXXXXXXX (removed serial number) + (II) I810(0): Monitor name: DELL 2001FP + (II) I810(0): Ranges: V min: 56 V max: 76 Hz, H min: 31 H max: 80 kHz, PixClock max 160 MHz + (II) I810(0): Using detected DDC timings + (II) I810(0): HorizSync 31-80 + (II) I810(0): VertRefresh 56-76 + (WW) I810(0): config file vrefresh range 56-86Hz not within DDC vrefresh range 56-76Hz + (II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs. + (--) I810(0): Maximum space available for video modes: 12288 kByte +"""]] +I modified my Monitor section to the following +[[!format txt """ +Section "Monitor" + Identifier "DELL 2001FP" + DisplaySize 367 275 + HorizSync 31-80 + VertRefresh 56-76 + Option "DPMS" + ModeLine "1600x1200" 160.00 1600 1664 1856 2160 1200 1201 1204 1250 +EndSection +"""]] +[[DisplaySize|DisplaySize]], if included really should be the actual size of your display in mm. This is best assessed by determining the LCD's native resolution and dotpitch and multiplying the two. For a Dell 2001FP, the native resolution is 1600x1200 and the dotpitch is .255 mm, thus the display size should be 408 306. The display size listed above will not correctly display paper sizes in word processing or other programs (e.g., openoffice, gv). +[[!format txt """ + DisplaySize 408 306 +"""]]
\ No newline at end of file diff --git a/FAQWarningMessages.mdwn b/FAQWarningMessages.mdwn new file mode 100644 index 00000000..966a12ba --- /dev/null +++ b/FAQWarningMessages.mdwn @@ -0,0 +1,23 @@ + + +# Server issues warning messages + +[[!toc ]] + +The Xserver can report warning messages to the log file. They can be identified by the `(WW)` string at the beginning of the line. There are hundreds of possible warning messages and most of them may be ignored, however some may help to explain why things don't work as expected. We try to explain these here. + + +## No matching Device section for instance ??? found + +Your Xserver reports the warning like: +[[!format txt """ +(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:0) found +"""]] +This means that the driver is able to drive the PCI device (chip) mentioned (here the one with the ID: 1:0:0) but the Xserver cannot find a valid device section for it in the Xserver config file. Without a device section this chip cannot be used. If the config file doesn't contain any other valid device section the server will terminate with the error message: `(EE) No devices detected.` + +Many devices include multiple device IDs on the same slot. Multi-head Radeons, for example, will often show up as both 1:0.0 and 1:0.1. The second device is totally fake, it only exists so the multihead support on certain other OSes will work. You can safely ignore these kinds of warnings. + + +## Open APM failed (/dev/apm_bios) (No such file or directory) + +The X server will check for the presence of APM power management support on startup. If your system does not have APM support, either in the BIOS or in the kernel, or if the device node simply doesn't exist, then you'll get this error message. This is not fatal to server startup, but if you're using APM for power management **and** you get this message, the server may get confused on power events. diff --git a/FindPage.moin b/FindPage.moin new file mode 100644 index 00000000..66b0e316 --- /dev/null +++ b/FindPage.moin @@ -0,0 +1,24 @@ +##language:en
+You can use this page to search all entries in this WikiWikiWeb. Searches are not case sensitive.
+
+Good starting points to explore a wiki are:
+ * RecentChanges: see where people are currently working
+ * FindPage: search or browse the database in various ways
+ * TitleIndex: a list of all pages in the wiki
+ * WordIndex: a list of all words that are part of page title (thus, a list of the concepts in a wiki)
+ * WikiSandBox: feel free to change this page and experiment with editing
+
+Here's a title search. Try something like ''manager'':
+
+ <<TitleSearch>>
+
+Here's a full-text search.
+
+ <<FullSearch>>
+
+You can also use regular expressions, such as
+
+{{{ seriali[sz]e}}}
+
+Or go direct to a page, or create a new page by entering its name here:
+ <<GoTo>>
diff --git a/FindPage/Capacitor.pdf b/FindPage/Capacitor.pdf Binary files differnew file mode 100644 index 00000000..77612adb --- /dev/null +++ b/FindPage/Capacitor.pdf diff --git a/Fosdem2006DevRoomAttendants.mdwn b/Fosdem2006DevRoomAttendants.mdwn new file mode 100644 index 00000000..8bc96129 --- /dev/null +++ b/Fosdem2006DevRoomAttendants.mdwn @@ -0,0 +1,8 @@ + + +# X@FOSDEM2006 DevRoom Visitors: + +The [[DevRoom|DevRoom]] doesn't require registration of any kind. This list is nothing more than a poll which allows the organisers to know the number of possible attendants. It might also allow people to find out who they might encounter. + +* Luc Verhaegen +* Mirco Müller
\ No newline at end of file diff --git a/Fosdem2006HotHouseParticipants.mdwn b/Fosdem2006HotHouseParticipants.mdwn new file mode 100644 index 00000000..f1787ed9 --- /dev/null +++ b/Fosdem2006HotHouseParticipants.mdwn @@ -0,0 +1,17 @@ + + +### Confirmed Participants to the X@FOSDEM2006 Developers HotHouse on Friday, 24th of February: + +* Egbert Eich +* Keith Packard +* Luc Verhaegen +* Jerome Glisse +* Matthieu Herrb +* Stephane Marchesin +* Stuart Kreitman +* Matthias Hopf +* Jay Hobson +* Zack Rusin +* Lars Knoll +* Michel Daenzer +* Daniel Stone
\ No newline at end of file diff --git a/GSoCApplication.mdwn b/GSoCApplication.mdwn new file mode 100644 index 00000000..5fd16ead --- /dev/null +++ b/GSoCApplication.mdwn @@ -0,0 +1,41 @@ + + +## Project Proposal Guidelines + +We expect more project proposals than Google will be able to fund. Here is our list of suggestions about how to write a Summer of Code proposal that will stand a chance of rising to the top of the heap. + + +## Requirements + + * Applicants meet Google's requirements for participation in Summer of Code. + * Applicants are in regular and close contact with their X.Org mentors. + * Applicants know their target programming language. + +## Proposal Outline + + * Name and Contact Information + * Title + * Synopsis. A short summary. + * Benefits to the Community. What novel technologies or approaches will be demonstrated? + * Deliverables. Give a brief, clear work breakdown structure with milestones and deadlines. Make sure to label deliverables as optional or required. You may want plan to start by producing some kind of whitepaper, or planning the project in traditional software engineering style. Work should include + * investigation + * programming + * documentation + * dissemination + * Description. A list of project details (rough architecture, etc). + * Related Work. A list of other people's work. Could be as simple as a URL with one sentence description. Be sure to explain how the proposed work is different from similar related work. + * Biographical Information. + * Summarize your education, work, and open source experience. + * List your skills and give evidence of your qualifications. + * List published papers, successful open source projects, etc. + * Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments. + +## General Notes + +Your proposal should be around 1500-4000 words in plain text and should clearly state what you intend to do and the necessary steps to get there. There is no limit on the number of submitted proposals, if you have several ideas, please submit several proposals. Do include URLs pointing to information that would help convince us of your chances of success: preliminary project plans or progress, other projects you've been involved with that were successful, code samples, etc. + +It is better if your project is under-scoped and sure to complete; as opposed to a largeish project which may not get done. + +One of the features of Google/X.Org Summer of Code is that it is a organization to help with projects involving integrating free software and hardware from different sources. + +See [[SummerOfCodeIdeas|SummerOfCodeIdeas]] for project ideas. diff --git a/GalliumStatus.mdwn b/GalliumStatus.mdwn new file mode 100644 index 00000000..55437f8e --- /dev/null +++ b/GalliumStatus.mdwn @@ -0,0 +1,67 @@ + + +## Current Status of Gallium3D Pipes and State Trackers + +This table lists the current combinations of state trackers and pipe drivers. + +Explanation: + +* d3d1x: Direct 3D 10/11 +* g3dvl: Generic GPU-Accelerated Video Decoding +* vega: OpenVG - The Standard for Vector Graphics Acceleration +* egl: Windowing system trackers similar to dri of EGL standard. +* wgl: Windowing system trackers similar to dri for MS Windows. +Unlisted drivers: + +* identity: This is a skeleton driver, used for passthrough and wrapping of pipes. +* nouveau: This is not actually a driver, but a set of routines common to all nv pipes. +* trace: This is a passthrough driver that traces Gallium library calls. +State tracker conformance tests: + +* mesa: tri, gears, piglit. tri and gears must render correctly and not crash; piglit must pass. +* vega: None. +* exa: rendercheck. This should be a goal for improving exa, drivers bound to exa, and rendercheck. +* g3dvl: None. +* dri: glxinfo. Must say that direct rendering is enabled. +* xorg: Xorg. X server must come up. Input drivers do not matter. +* egl: eglinfo, eglscreen, egltri. egltri must render correctly. +* wgl: None. +What do these mean? + +* "**DONE**" means that it is implemented and passes the state-tracker-specific conformance test. +* "**MOSTLY**" means that it is implemented but does not pass the conformance test. +* "**WIP**" means that the implementation is being worked on, but should not be considered ready for general testing. +* "**SLOW**" means that the feature is DONE, but not performant due to known deficiencies in the code. +* "**TODO**" means that the implementation is incomplete and nobody is working on it. +* "**UNKNOWN**" means that the current status of this item isn't known. +If you're the maintainer of any of this code, please update these when you can, especially UNKNOWN slots. +[[!table header="no" class="mointable" data=""" + | **mesa** | **vega** | **exa** | **g3dvl** | **d3d1x** | **opencl** | | **dri** | **xorg** | **egl** | **wgl** +i915 (Intel i915/i945) | DONE | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | TODO | | DONE | DEPRECATED | DONE | UNKNOWN +nv30 (nVidia NV30 and NV40) | WIP | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | N/A | | MOSTLY | DEPRECATED | DONE | UNKNOWN +nv50 (nVidia NV50/G80) | DONE | UNKNOWN | UNKNOWN | WIP<sup>1</sup> | WIP | WIP | | MOSTLY | DEPRECATED | DONE | UNKNOWN +nvc0 (nVidia NVC0/Fermi) | DONE | UNKNOWN | UNKNOWN | WIP | DONE | TODO | | MOSTLY | DEPRECATED | DONE | UNKNOWN +r300 (ATI R300/R400/R500) | DONE | WIP | WIP | WIP | UNKNOWN | TODO | | DONE | DEPRECATED | DONE | TODO +r600 (ATI R600/R700/R800/R900) | DONE | WIP | WIP | WIP | UNKNOWN | WIP | | DONE | DEPRECATED | DONE | TODO +radeonsi (AMD Southern Islands) | WIP | UNKNOWN | UNKNOWN | WIP | UNKNOWN | TODO | | WIP | DEPRECATED | WIP | UNKNOWN +softpipe | MOSTLY | MOSTLY | UNKNOWN | UNKNOWN | UNKNOWN | TODO | | DONE | DEPRECATED | DONE | DONE +svga (VMware Virtual GPU) | DONE | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | TODO | | MOSTLY | DEPRECATED | DONE | UNKNOWN +"""]] + + +### Notes + +1 - mpeg2 hardware (not shaders) decoding DONE + + +### Feature stacks that give equivalent functionality to the classic MESA implementation + + +[[!format txt """ +Gallium3D Classic MESA +--------------------------------- +xorg + exa DDX + Xv +dri + mesa GL + GLSL +dri DRI2 +KMS + Gallium3D DRM + DRI + DDX +"""]]
\ No newline at end of file diff --git a/GoingModular.mdwn b/GoingModular.mdwn new file mode 100644 index 00000000..4f45505f --- /dev/null +++ b/GoingModular.mdwn @@ -0,0 +1,58 @@ + + +## Going Modular + +This is an outline of a scheme for incrementally migrating the X.org tree from a monolithic build based on imake to a modular build based on automake, autoconf and libtool. The goal is to accurately reproduce the existing binaries as closely as possible. + + + +--- + + + + +### Goals + +The goal of this process is to produce separately distributable �packages� for various parts of the system, including (but not limited to) + + * Individual libraries + * Individual video drivers + * Collections of Applications + * The core X server binary +In my opinion, we should strive to break things up enough so that no distribution feels the need to break things up further. This limits the downstream impact for any given patch. I also believe we should permit either the X server or libraries to be built without requiring the other; this means that all shared include files must be packaged separately. + +With this in mind, I believe the correct order of execution is something like: + +1. Move include files. + 1. global includes move to new packages for each sub-system + 1. library-specific headers move into the library in such a way as to not require any additional work before the library itself can be built -- e.g. in Xlib, a subdirectory 'X11' must hold the various Xlib headers so that -I. will permit #include <X11/Xlib.h> to work. +1. Fix the 'make includes' pass to actually install the header files in $(DESTDIR)/... +1. Fix Imakefiles so that these new locations work everywhere. Yes, this is busy work given the goal of eliminating the Imakefiles shortly, but it means that we can still build the tree in the interim. +1. Autotool the global include packages. We can steal liberally from the debrix and xlibs projects here. +1. Autotool the libraries, starting at the bottom of the stack and moving upwards. As each is autotooled, the imake bits need to be changed to locate the library in the installed location ($(DESTDIR)/...) and that library should be removed from the imake system. +1. Select appropriate modularization boundaries for the various X applications, modularizing them on an as-needed basis. +1. Borrowing liberally from debrix, construct autotool packages for the X server headers. +1. Convert the server over to use the installed server headers +1. autotool the X server drivers. Can we do this first? +1. autotool the X server core. Do we do this first? +Lots of this is just speculation at this point. I think the key points are: + + * Use imake to transition to a modular system; make sure the unfinished parts remain buildable from the monolithic imake system. + * Leave Imakefiles around in each finished module. This should make 'xmkmf -a' work in a lot of cases. + * Ensure binary compatibility at each stage by checking the results against the monolithic build. I think the actual binaries will be slightly different as libtool will end up passing different options to ld than imake does. If we could avoid this difference, we could actually compare the modular vs monolithic builds of each piece rather easily. +I'd like to see comments and suggestions for change, and I expect as we follow through this process that we'll have to come back here and make changes, so treat this as a working document, not a finished plan. + +-- Main.[[KeithPackard|KeithPackard]] - 19 Oct 2004 + + +### Questions and Comments + +Here are a few questions/comments I have after reading this page: + + * What is the target version of autotools? 2.59 with shiny new features or 2.13 for backwards compatibility with older systems? + * Autoconf has the ability to configure sub-projects using AC_CONFIG_SUBDIRS. I've found it useful in the past to create a toplevel project that does nothing but configure all the subprojects with identical configure lines, using a shared config.cache file. + * Reading the above text, it sounds like the idea is to create autotools packages for header files, separate from the code that actually implements each library. Is that the plan, or am I mis-reading the text? + * For comparing the resulting binaries, I think the easiest way would be to clean up the output of 'objdump -t' for each object and make a note of added/missing symbols or of symbols which have changed size unexpectedly. + * It isn't stated explicitly above, but I assume the goal is to support separated build directories? It's probably worth stating upfront, since it's quite easy to miss a $(srcdir) somewhere in the Makefile.am which would break this functionality. + * Most projects seem to have local .m4 files for project-specific things. Would it make sense to have an X.org-wide M4 module so that all projects have the same supporting macros? +-- Main.[[RayLehtiniemi|RayLehtiniemi]] - 20 Dec 2004 diff --git a/GrabsProcessing.mdwn b/GrabsProcessing.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/GrabsProcessing.mdwn diff --git a/HelpContents.mdwn b/HelpContents.mdwn new file mode 100644 index 00000000..e7b4255f --- /dev/null +++ b/HelpContents.mdwn @@ -0,0 +1,23 @@ + + +## Help Contents + +Here is a tour of the most important help pages: + +* [[HelpForBeginners|HelpForBeginners]] - if you are new to wikis +* [[HelpOnNavigation|HelpOnNavigation]] - explains the navigational elements on a page +* [[HelpOnPageCreation|HelpOnPageCreation]] - how to create a new page, and how to use page templates +* [[HelpOnUserPreferences|HelpOnUserPreferences]] - how to make yourself known to the wiki, and adapt default behaviour to your taste +* [[HelpOnEditing|HelpOnEditing]] - how to edit a page +* [[HelpOnActions|HelpOnActions]] - tools that work on pages or the whole site +* [[HelpMiscellaneous|HelpMiscellaneous]] - more details, and a FAQ section +These pages contain information only important to wiki administrators and developers: + +* [[HelpOnAdministration|HelpOnAdministration]] - how to maintain a [[MoinMoin|MoinMoin]] wiki +* [[HelpOnInstalling|HelpOnInstalling]] - how to install a [[MoinMoin|MoinMoin]] wiki +* [[HelpForDevelopers|HelpForDevelopers]] - how to add your own features by changing the [[MoinMoin|MoinMoin]] code +An automatically generated index of all help pages is on [[HelpIndex|HelpIndex]]. See also [[HelpMiscellaneous/FrequentlyAskedQuestions|HelpMiscellaneous/FrequentlyAskedQuestions]] for answers to frequently asked questions. + +If you find any errors on the help pages, describe them on [[!MoinMoin HelpErrata desc="HelpErrata"]]. + +_[Please do not add redundant information on these pages (which has to be maintained at two places then), and follow the established structure of help pages. Also note that the master set of help pages is not public, that this very page you read and all other help pages may be overwritten when the wiki software is updated. So if you have major contributions that should not get lost, send an extra notification notice to the [[MoinMoin|MoinMoin]] user mailing list.]_ diff --git a/HelpForBeginners.mdwn b/HelpForBeginners.mdwn new file mode 100644 index 00000000..02cf53c3 --- /dev/null +++ b/HelpForBeginners.mdwn @@ -0,0 +1,34 @@ + + +## WikiWikiWeb + +A [[WikiWikiWeb|WikiWikiWeb]] is a collaborative hypertext environment, with an emphasis on easy access to and modification of information. + +You can edit any page by pressing the link at the bottom of the page. Capitalized words joined together form a [[WikiName|WikiName]], which hyperlinks to another page. The highlighted title searches for all pages that link to the current page. Pages which do not yet exist are linked with a question mark (or a different rendering in bold red): just follow the link and you can add a definition. That is also the way to create a new page: add a new [[WikiName|WikiName]] to an existing page, save your modification, click on your new link and create the page (more details on [[HelpOnPageCreation|HelpOnPageCreation]]). + +You are encouraged to edit the [[WikiSandBox|WikiSandBox]] whichever way you like. Please restrain yourself from editing other pages until you feel at home with the ways a wiki works. + +To learn more about what a [[!c2 WikiWikiWeb desc="WikiWikiWeb"]] is, read about [[!c2 WhyWikiWorks desc="WhyWikiWorks"]] and the [[!c2 WikiNature desc="WikiNature"]]. Also, consult the [[!c2 WikiWikiWebFaq desc="WikiWikiWebFaq"]] and [[!c2 OneMinuteWiki desc="OneMinuteWiki"]]. This wiki is also part of the [[InterWiki|InterWiki]] space, which means you can easily refer to a wealth of information available through other public wiki sites. + +Good starting points to explore a wiki are + +* [[RecentChanges|RecentChanges]]: see where people are currently working +* [[FindPage|FindPage]]: search or browse the database in various ways +* [[TitleIndex|TitleIndex]]: a list of all pages in the wiki +* [[WordIndex|WordIndex]]: a list of all words that are part of page title (thus, a list of the concepts in a wiki) +* [[SiteNavigation|SiteNavigation]]: a page leading to the different indexing schemes of the wiki +* [[WikiSandBox|WikiSandBox]]: feel free to change this page and experiment with editing +For more help, see the [[HelpContents|HelpContents]] and the [[HelpIndex|HelpIndex]] pages. + + +## Wiki Names + +A [[WikiName|WikiName]] is a word that uses capitalized words. [[WikiName|WikiName]]****s automagically become hyperlinks to the [[WikiName|WikiName]]'s page. What exactly is an uppercase or lowercase letter is determined by the configuration, the default configuration works for Latin-1 (ISO-8859-1) characters. See below for how to handle Asian, Hebrew and other non-western character encodings. + +When you click on the highlighted page title (i.e. HelpForBeginners on this page), you will see a list of all pages that link to the current page. This even works on pages that are not defined yet. + +A question mark before a link, or a different rendering in bold red, means that the page is not yet defined: you can click the question mark to offer a definition (e.g., [[NoSuchPageForReal|NoSuchPageForReal]]). If you click on such a link, you'll see a default page that you can edit; only after you save the page will it be created for real. A list of all pages that are not yet created but referred on another page is on [[WantedPages|WantedPages]]. + +To _escape_ a [[WikiName|WikiName]], i.e. if you want to write the word Wiki****Name without linking it, use an "empty" bold sequence (a sequence of six single quotes) like this: `Wiki''''''Name`. Alternatively, you can use the shorter sequence "````" (two backticks), i.e. `Wiki``Name`. + +To learn more about wiki markup, see [[HelpOnEditing|HelpOnEditing]]. diff --git a/HelpForDevelopers.mdwn b/HelpForDevelopers.mdwn new file mode 100644 index 00000000..6b50f73c --- /dev/null +++ b/HelpForDevelopers.mdwn @@ -0,0 +1,24 @@ + +**Contents** [[!toc ]] + + +## Helping with MoinMoin development + +[[MoinMoin|MoinMoin]] would miss quite some features were it not for the help of some of its users. What you can do to improve [[MoinMoin|MoinMoin]], also for your own benefit: + +* develop new extensions (macros, actions, processors, parsers) +* run the development version and help testing the new features +* test [[MoinMoin|MoinMoin]] on a certain platform, or with certain Python versions +* help with the translation efforts, especially adding new languages +* help developping new themes, CSS and icons +* ... +In any case, you should subscribe to the [[MoinMoin Developer List|http://lists.sourceforge.net/lists/listinfo/moin-devel]]. More information on [[MoinMoin|MoinMoin]] source code and other developer issues can be found in the [[MoinMoin|MoinMoin]] main wiki, on [[!MoinMoin MoinDev desc="MoinDev"]] and its subpages. + + +## Contributions + +The distribution contains a "contributions" directory for 3rd party extensions that are not made part of the official distribution. This directory contains extensions contributed by [[MoinMoin|MoinMoin]] users and that are considered either too exotic or need too much work to be integrated into the core sources. Another reason of not adding them is that modules in the core have to be maintained when structural changes happen, which is a constant burden. + +Thus, these sources are here for you to try them out and take advantage of a feature someone found useful enough to write code for, but you cannot expect that they always work with the current distribution. Contributors are encouraged to send updates... + +Other sources of user contributions are linked from [[!MoinMoin MoinMoinExtensions desc="MoinMoinExtensions"]]. diff --git a/HelpIndex.mdwn b/HelpIndex.mdwn new file mode 100644 index 00000000..e82f6d6f --- /dev/null +++ b/HelpIndex.mdwn @@ -0,0 +1,2 @@ + +The following is a plain list of all help pages. See [[HelpContents|HelpContents]] for a _guided tour_. [[!map pages="Help.*"]] diff --git a/HelpMiscellaneous.mdwn b/HelpMiscellaneous.mdwn new file mode 100644 index 00000000..588a0fcb --- /dev/null +++ b/HelpMiscellaneous.mdwn @@ -0,0 +1,127 @@ + + +## Other MoinMoin help topics + +**Subtopics** + +* [[/FrequentlyAskedQuestions|HelpMiscellaneous/FrequentlyAskedQuestions]] +* [[/ExperimentalFeatures|HelpMiscellaneous/ExperimentalFeatures]] +**Contents** [[!toc ]] + + +### Adding an icon to your wiki setup + +You maybe want to add some icon to your wiki site, commonly known as `favicon.ico`. To get those little icons besides bookmarks and with tabbed browsing, add this to your `moin_config.py`: +[[!format txt """ +html_head = ''' +<link rel="icon" href="/images/icon.png" type="image/png"> +<!-- ... more header stuff ... --> +''' +"""]] +The image size _must_ be 16x16 and simply putting it as `/favicon.ico` (into your Document``Root) does _not_ work with all browsers (e.g. does not work with Mozilla versions 1.0 - 1.3). + + +### Enabling a publically editable intermap + +If you want your users to easily add new [[InterWiki|InterWiki]] monikers, change your `moin_config.py` to contain an entry like this: +[[!format txt """ +shared_intermap = ['/usr/local/moin/mywiki/data/text/intermap_2etxt'] +"""]] +Then create a page named `intermap.txt` (see [[!LinuxWiki intermap desc="intermap"]].txt for an example) with the following content: +[[!format txt """ +#format text/plain +## Keep the first line and add text only after two hash marks (##) +## +## This is a publically editable extension of standard InterWiki +## definitions. Any addition here is immediately reflected in +## the wiki. +## +## To enable this in your own wiki, either add the page file of +## this page to config.shared_intermap (can be a list of files +## since version 1.1), or add an appropriate symbolic link. +## +## The format of an entry is interwiki moniker followed by the URL +## $PAGE can be used to embed the URI following the moniker in +## the resultant URL + +MyNewMoniker http://example.com/somewiki/$PAGE.html +"""]] +Then check whether your new monikers appear on the [[InterWiki|InterWiki]] list. + + +### Apache tricks + + +#### Securing access to a wiki via Apache means + +See [[!MoinMoin PasswordProtectedEditing desc="PasswordProtectedEditing"]] + + +#### Serving the wiki from a domain root + +`httpd.conf` modification for [[MoinMoin|MoinMoin]] installation at "/": +[[!format txt """ +# global section: +LoadModule rewrite_module /usr/lib/apache/1.3/mod_rewrite.so +# virtualhost section: +RewriteEngine on +RewriteRule ^/wiki/ - [last] +RewriteRule ^/robots.txt - [last] +RewriteRule ^/favicon.ico - [last] +RewriteRule ^/?(.*) /pathto/cgi-bin/moin.cgi/$1 [last,type=application/x-httpd-cgi] +"""]] +This way you can use short and clean URLs like [[http://LinuxWiki.de/FrontPage|http://LinuxWiki.de/FrontPage]]. + + +### Special features for wiki farms and intranets + +The following shows how certain features can help you to optimize your configuration when you run several wikis on one host, or when you use [[MoinMoin|MoinMoin]] in intranet environments. + + +#### Centralized settings + +* farm_config.py +* shared intermap.txt +* shared code base and icons + +#### Remapping URLs + +The configuration variable "`url_mappings`" can be used to remap absolute URLs to relative ones, or change certain URL prefixes to totally different ones. This is especially useful in intranets, when whole trees of documents hosted outside of the wiki move around. + +"`url_mappings`" is a lookup table in the form of a dict, the key is the prefix to be replaced, the value is the replacement. A typical example is `url_mappings = {'http://my.server.net/': '/'}`, which removes the scheme from local URLs, and thus makes links to your own server work for both `http` _and_ `https`. + + +### TODO + +[!] TODO: explain the following things in detail, and add more detail to the above sections + +Needing more explanation: + +* event logging +* Page trails (user option) +* [[UserPreferences|UserPreferences]]: checkboxes for double-click edit, page trail, fancy links, emoticons, jump to last page visited, and some other yes/no options +* "Remove trailing whitespace from each line" option in the editor +* Page templates (create a new page using a template page) +* Only "normal" URLs (outside of brackets) are converted to inline images ==> document exact rules +* Highlighting of search results, and of bad words when spellchecking +* Support for "[[file:"|file:"]] URLS +* email notification features +* "RSS" icon displayed by [[RecentChanges|RecentChanges]] macro +* commentary field of editor, recent changes and page info +* Page caching, for now limited to XSLT processing (where it's absolutely needed); new code & API to add the "Refresh``Cache" link +* inline search fields (at the bottom of each page) +* the interwiki name "Self" now always points to the own wiki +* page info action +Admin stuff: + +* describe "moin.cgi?test" tool in more detail +* Wiki``Farm support: + * <datadir>/plugin/macro and <datadir>/plugin/action can be used to store macros and actions local to a specific wiki instance + * config.shared_intermap can contain a pathname to a shared "intermap.txt" file (i.e. one stored outside the datadir) +* $PAGE placeholder in interwiki map +Command-line tools: + +* "moin-dump" command line tool to create a static copy of the wiki content +Compatibility: + +* RSS features require a recent PyXML (CVS or 0.7) due to bugs in the namespace handling of xml.sax.saxutils in earlier versions. This is (hopefully) automatically detected on every installation.
\ No newline at end of file diff --git a/HelpOnAccessControlLists.mdwn b/HelpOnAccessControlLists.mdwn new file mode 100644 index 00000000..7c13429a --- /dev/null +++ b/HelpOnAccessControlLists.mdwn @@ -0,0 +1,229 @@ + + +# Access Control Lists + +When Access Control Lists, or ACLs for short, are turned on, you will be able to control who may do what on or with a wiki page. + + +## Contents + +[[!toc ]] + + +## Basics + +Using ACLs in moin is as easy as including a control line at the top of the page you want to control, like the following one: +[[!format txt """ +#acl SomeUser:read,write All:read +"""]] +This will allow `SomeUser` to read and write on that page, while every other user will be able to read but not edit it (unless you've done some special setup in the site configuration). + + +## Syntax + +The syntax for each line is as follows: +[[!format txt """ +#acl [+-]User[,SomeGroup,...]:[right[,right,...]] [[+-]OtherUser:...] [[+-]Trusted:...] [[+-]Known:...] [[+-]All:...] [Default] +"""]] +Where: + +* **User** is a user name and triggers only if the user matches. +* **Some``Group** is a page name matching `page_group_regex` (see [[#Configuration|HelpOnAccessControlLists]]) with some lines in the form " * Member" (see [[#Groups|HelpOnAccessControlLists]]). +* **Trusted** is a special group containig all authenticated users (like when using password login). +* **Known** is a special group containing all valid users (like when using the cookie). +* **All** is a special group containing all users (known and anonymous users). +* **Default** is a special entry which inserts at the given place the entries from `acl_rights_default` (see [[#Default|HelpOnAccessControlLists]]). +* **right** may be an arbitrary word like read, write, delete, revert, admin. Only words in `acl_rights_valid` are accepted, others are ignored. It is allowed to specify no rights, which means that no rights are given. + +## Available rights + +These are the available rights you can use in an ACL entry: +read +: Given users will be able to read text of this page. + +write +: Given users will be able to write (edit) text of this page. + +delete +: Given users will be able to delete this page and its attachments. + +revert +: Given users will be able to revert this page to an older version. + +admin +: Given users will have admin rights for this page. It means users will be able to change ACL settings, including granting "admin" to others and revoking "admin" from others. + + + +## Processing logic + +When some user is trying to access some ACL-protected resource, the ACLs will be processed in the order they're found. The **first matching ACL** will tell if the user has access to that resource or not. + +(!) Due to that _first match_ algorithm, you should sort your ACLs: first single usernames, then special groups, then more general groups, then `Known` and at last `All`. + +For example, the following ACL tells that `SomeUser` is able to read and write the resources protected by that ACL, while any member of `SomeGroup` (besides `SomeUser`, if part of that group) may also admin that, and every other user is able to read it. +[[!format txt """ +#acl SomeUser:read,write SomeGroup:read,write,admin All:read +"""]] +To make the system more flexible, there are also two modifiers: the prefixes '+' and '-'. When they are used, the given ACL entry will **only** match if the user **is requesting** the **given** rights. As an example, the above ACL could also be written as: +[[!format txt """ +#acl -SomeUser:admin SomeGroup:read,write,admin All:read +"""]] +Or even: +[[!format txt """ +#acl +All:read -SomeUser:admin SomeGroup:read,write,admin +"""]] +Notice that you probably won't want to use the second and third examples in ACL entries of some page. They're very useful on the site configuration entries though. + +<a name="Default"></a> +## Inheriting from defaults + +Sometimes it might be useful to give rights to someone without affecting too much the default rights. For example, let's suppose you have the following entries in your configuration: +[[!format txt """ +acl_rights_default = "TrustedGroup:read,write,delete,revert All:read" +acl_rights_before = "AdminGroup:admin,read,write,delete,revert +TrustedGroup:admin" +"""]] +Now, you have some page where you want to give the "write" permission for `SomeUser`, but also want to keep the default behavior about All and `TrustedGroup`. You can easily do that using the **Default** entry: +[[!format txt """ +#acl SomeUser:read,write Default +"""]] +This will insert the entries from `acl_rights_default` in the exact place where the Default word is placed. In other words, the entry above, with the given configuration, is equivalent to the following entry: +[[!format txt """ +#acl SomeUser:read,write TrustedGroup:read,write,delete,revert All:read +"""]] +While they represent the same thing, inheriting from the defaults has the advantage of automatically following any further change introduced in the defaults. + +<a name="Configuration"></a> +## Configuration + +These are the configuration items used to setup ACLs on a moin site. +[[!table header="no" class="mointable" data=""" +**Entry** | **Default** | **Description** +acl_enabled | `0` | If true will enable ACL support. +acl_rights_before | `""` | applied **before** page or default ACLs +acl_rights_after | `""` | applied **after** page or default ACLs +acl_rights_default | `"Trusted:read,write,delete,revert Known:read,write,delete,revert All:read,write"` | **only** used when **no other** ACLs are given on the page being accessed +acl_rights_valid | `["read", "write", "delete", "revert", "admin"]` | These are the acceptable (known) rights (and the place to extend, if necessary). +"""]] + +So you know now what it _does_, but what does it _mean_? + +* "before" means **forcing stuff** (this is because of first match algorithm) +* "after" means **not forgetting stuff** accidently (like maybe giving read rights to all) +* "default" means **what is done if no ACLs are used on the page**. It is equivalent to writing exactly these ACLs onto a page. +<a name="Groups"></a> +## Groups + +User groups make it easier to specify rights for bigger groups. + +Only `SomeUser`'s friends can read and edit this page: +[[!format txt """ +#acl SomeUser:read,write SomeUser/FriendsGroup:read,write +"""]] +`SomeUser/FriendsGroup` would be a page with each top-level list item representing a wiki username in that group: +[[!format txt """ +#acl SomeUser:read,write,admin,delete,revert + * JoeSmith + * JoeDoe + * JoeMiller +"""]] +A page named `AdminGroup` (matching config.page_group_regex) could define a group of that name and could be also protected by ACLs: +[[!format txt """ +#acl AdminGroup:admin,read,write All:read + * SomeUser + * OtherUser + * This is currently ignored. +Any other text not in first level list will be ignored. +"""]] +You can configure which page names are considered as group definition pages (e.g. for non-english wikis): +[[!format txt """ +page_group_regex = '.*Group$' # this is the default +"""]] + +## Usage cases + + +### Public community Wiki on the Internet + +The most important point here is to use ACLs only in cases where really needed. Wikis depend on openness of information and free editing. They use soft security to clean up bad stuff. So there is no general need for ACLs. If you use them too much, you might destroy the way wiki works. + +This is why either ACLs should not be used at all (default) or, if used, the moin_config.py should look similar to that: +[[!format txt """ +acl_rights_before = 'WikiEditorName:read,write,admin,delete,revert +AdminGroup:admin BadGuy:' +"""]] +The default `acl_rights_default` option should be ok for you: +[[!format txt """ +acl_default = 'Known:read,write,delete,revert All:read,write' +"""]] +A good advice is to have only a few and very trusted admins in `AdminGroup` (they should be very aware of how a wiki works or they would maybe accidently destroy the way the wiki works: by its openness, not by being closed and locked!). + +If using `AdminGroup`, you should make a page called `AdminGroup` and use it to define some people who get admin rights. + +Specifing `BadGuy` like shown above basically locks him out - he can't read or edit anything with that account. That makes only sense if done temporarily, otherwise you also could just delete that account. Of course, this `BadGuy` can also work anonymously, so this is no real protection (this is where soft security will apply). + + +### Wiki as a simple CMS + +If you want to use a wiki to easily create web content, but if you don't want edits by the public (but only by some webmasters), you maybe want to use that in your moin_config.py: +[[!format txt """ +acl_rights_default = 'All:read' +acl_rights_before = 'WebMaster,OtherWebMaster:read,write,admin,delete,revert' +"""]] +So everyone can read, but only the Webmasters can do anything else. As long as they still work on a new page, they can put +[[!format txt """ +#acl All: +"""]] +on it, so nobody else will be able to see the unready page. When being finished with it, don't forget to remove that line again, so that `acl_rights_default` will be used. + +Some page(s) could also allow public comments (like one being called `PublicComments`), so you give more rights on that page: +[[!format txt """ +#acl All:read,write +"""]] + +### Wiki on Intranet + +If you want to use a wiki on your intranet and you trust your users (not doing hostile stuff like locking others out or hijacking pages) to use the admin functionality in a senseful way, you maybe want to use that: +[[!format txt """ +acl_rights_default = 'Known:admin,read,write,delete,revert All:read,write' +acl_rights_before = 'WikiAdmin,BigBoss:read,write,admin,delete,revert' +"""]] +So everyone can read, write and change ACL rights, `WikiAdmin` and `BigBoss` are enforced to be able to do anything, known users get admin rights by acl_rights_default (so they get it as long as no other ACL is in force for a page). + +Consequences: + +* on a new page, the page creator can put any ACLs he wants +* on existing pages, not having ACLs yet, any known user can set up any ACLs he wants +* all people (except `WikiAdmin` and `BigBoss`) can be locked out by anybody ("known") else on pages without ACLs + +### Wiki as a public company page + +If you want to use a wiki as the company page, and don't want every user being able to change the company page content, you may want to use something like this: +[[!format txt """ +acl_rights_default = "TrustedGroup:admin,read,write,delete,revert All:read" +acl_rights_before = "AdminGroup:admin,read,write,delete,revert +TrustedGroup:admin" +"""]] +This means that: + +* by default known and anonymous users are only allowed to read pages +* on a new page, users in `TrustedGroup` can put any ACLs they want +* on existing pages, not having ACLs yet, any user in `TrustedGroup` user can set up any ACLs he wants +* all people, except people in `AdminGroup`, can be locked out by other admins or trusted users +* people in `TrustedGroup` get use their admins rights on any page they're able to write, even if there are specific ACLs + +### Comments on read-only page + +You can easily add a comments section to a read-only page by using a writable subpage, and allowing users to write on it. For example, you can define `SomePage` like this: +[[!format txt """ +#acl SomeUser:read,write All:read +'''Some read-only content''' + +... + +''' User comments ''' +[[Include(SomePage/Comments)]] +"""]] +And `SomePage/Comments` like this: +[[!format txt """ +#acl All:read,write +Add your comments about SomePage here. +"""]]
\ No newline at end of file diff --git a/HelpOnActions.mdwn b/HelpOnActions.mdwn new file mode 100644 index 00000000..a927a45b --- /dev/null +++ b/HelpOnActions.mdwn @@ -0,0 +1,44 @@ + + +## Actions + +Actions are tools that work on a page or the whole wiki, but unlike macros do not add _to_ the page content when viewing a page, but work _on_ that page content. They either produce some output based on page contents (navigational actions like searching) or implement functions that are not related to viewing a page (like deleting or renaming a page). + +There is a set of system-defined actions, which includes page editing; you can extend the set of known actions by your own ones. See [[HelpForDevelopers|HelpForDevelopers]] for more on that. + +The following actions are added to the list of user-defined extension actions at the bottom of each page. This happens to any mixed-case extension, for other actions (all lower-case) see the list further down this page. Some of these action might not be available for your wiki site. + +* `AttachFile`: attach files to a page, see [[/AttachFile|HelpOnActions/AttachFile]] for more details. +* `DeletePage`: Delete a page, after you confirmed it; deletion means a final backup copy is created and only then the page is deleted, i.e. you can _revive_ the page later on (as long as the backups are not physically deleted). +* `RenamePage`: Rename a page, after you confirmed it. +* `LikePages`: list pages whose title starts or ends with the same [[!MeatBall WikiWord desc="WikiWord"]] as the current page title. +* `LocalSiteMap`: show nearby links of the current page, i.e. list all referred-to pages, and in turn their references, to a certain limited depth. +* `SpellCheck`: call the spell checker for the current page; see [[HelpOnSpellCheck|HelpOnSpellCheck]] for more. +The following is a list of _internal_ actions that are used to implement the various icons and links at the top and bottom of pages, or supplement certain macros. + +* titleindex: Implements the listing of all page names as text or ([[?action=titleindex|?action=titleindex]]) or XML ([[?action=titleindex&mimetype=text/xml);|?action=titleindex&mimetype=text/xml);]] the main use of this action is to enable [[!MeatBall MetaWiki desc="MetaWiki"]]. +* fullsearch: this action is triggered by clicking on the "Go" button of the `FullSearch` macro ([[?action=fullsearch&value=HelpOnActions|?action=fullsearch&value=HelpOnActions]]). +* titlesearch: this action is triggered by clicking on the "Go" button of the `TitleSearch` macro ([[?action=titlesearch&value=HelpOnActions|?action=titlesearch&value=HelpOnActions]]). +* inlinesearch: this implements the inline search for the form fields at the bottom of each page (note that this uses POST requests, so you won't normally see this action in URLs). +* highlight: highlight the search word when you click on a link in a search result list. +* diff: display differences between page revisions. +* info: show meta-data on a page. +* recall: display an older revision of a page. +* show: display a page (the default action). +* refresh: refresh the cached version of a page (currently only used on XSLT-formatted pages). +* print: show the print-view of a page, which omits the navigational items from the display view. +* edit: edit this page. +* savepage: save this page (do not ever use this manually). +* subscribe: subscribe to a page. +* userform: save user preferences. +* bookmark: set bookmark for [[RecentChanges|RecentChanges]]. +* raw: send the raw wiki markup as text/plain (e.g. for backup purposes via wget); [[SystemInfo?action=raw|SystemInfo?action=raw]] shows the markup of [[SystemInfo|SystemInfo]]. +* format: emit specially formatted views of a page. +* rss_rc: generate a RSS feed of [[RecentChanges|RecentChanges]]. +* chart: display charts. +* export: export the wiki content. _[experimental]_ +* content: for transclusion into static web pages, this action emits the pure page content, without any <html>, <head>, or <body> tags. +* links: generates a list of all pages and the links on them, just like [[!MeatBall LinkDatabase desc="LinkDatabase"]]. +* xmlrpc: Wiki XML-RPC interface, see [[!MeatBall XmlRpcToWiki desc="XmlRpcToWiki"]]. +* revert: revert to an older version of the page. +* macro: execute a helper action in an external macro.
\ No newline at end of file diff --git a/HelpOnAdministration.mdwn b/HelpOnAdministration.mdwn new file mode 100644 index 00000000..5e938cbd --- /dev/null +++ b/HelpOnAdministration.mdwn @@ -0,0 +1,18 @@ + +[[HelpContents|HelpContents]] > HelpOnAdministration + + +## Maintaining a MoinMoin wiki + +The following pages contain information on various subtopics important to [[MoinMoin|MoinMoin]] admins. + +Regular tasks: + +* [[HelpOnPageDeletion|HelpOnPageDeletion]] - how to delete pages +Installing and upgrading: + +* [[HelpOnInstalling|HelpOnInstalling]] - how to install the software and supporting files +* [[HelpOnConfiguration|HelpOnConfiguration]] - how to configure your system +* [[HelpOnUpdating|HelpOnUpdating]] - how to update an existing [[MoinMoin|MoinMoin]] installation +* [[HelpOnSpellCheck|HelpOnSpellCheck]] - how to configure and maintain the spell checking option +* [[HelpOnThemes|HelpOnThemes]] - how to change the appearance of your wiki
\ No newline at end of file diff --git a/HelpOnEditLocks.mdwn b/HelpOnEditLocks.mdwn new file mode 100644 index 00000000..90d06b22 --- /dev/null +++ b/HelpOnEditLocks.mdwn @@ -0,0 +1,52 @@ + + +## Locking against concurrent editing + +If two people try and edit the same wiki page at once some nasty conflicts can occur. Without any kind of warning system one of the editors can save the page, which leaves the other editor with a message warning them about the conflict. An easy way around this is to display warnings for editors that try to start editing wiki pages that are already being edited. i.e. the wiki keeps track of pages being edited. + +This can be done in Moin using the _editlock_ system. There are three levels of locking: to _warn_, to _lock_ and _None_ (turned off). + +If you configure Moin to **warn**, when someone tries to edit a page that is already being edited, they will be presented with a warning message asking them to consider waiting until the current editor has finished. + +Moin can also be configured to **lock** an edited page, only during editing. Here, if some tries to edit a page that is being edited they will receive a message saying that the page is locked and will not be able to edit it until the editor has finished. + +A complication of this feature is that an editing session might be started and might not be finished. e.g.: + +* Someone presses edit and then clicks on a link to exit the page without cancelling. +* The browser window is closed without cancelling. +* The back button is pressed. +* Someone starts editing a page and forgets and leaves it open overnight. +This would result in a page having permanent warnings or being permanently locked. Therefore, both _warn_ and _lock_ have a **timeout** feature. After a specified number of minutes the feature expires. Note that the timer restarts when you hit preview. If you are actively editing a page and hit preview it is assumed you are still busy and the timer starts again. If you leave the page, or exit it for more time than the timer allows the edit locking runs out and other people are free to edit the page. + + +### Configuration + +The `edit_locking` config variable controls the behaviour of the locking system. This can have the following values: + +* `None`, i.e. there is no edit locking. The feature is turned off and nobody is warned or stopped from doing simultaneous edits of a page. +* "`warn <timeout>`" tells Moin to warn anyone trying to concurrently editing a page, with a specified timeout, e.g. "`warn 10`" will warn for 10 minutes after an edit is started. +* "`lock <timeout>`" tells Moin to lock a page for the specified amount of time after an edit started. e.g. "`lock 5`" locks a page for 5 minutes. + +### Aborting an edit + +For the reasons explained in the timeout description above, you should **always use Cancel** to cancel an edit if you have enabled edit locking! + + +## Example + +Sample interaction of John``Miller and Jane``Doe... +no locking (None) +: +John``Miller starts editing a page and Jane``Doe thinks she'll edit the same page. She has no idea that someone else is editing the page so they both edit away and hit save. It doesn't matter who started first and did the most editing, whoever hits _save changes_ first will have their changes committed and the unfortunate 2nd editor will have to try and merge their changes in or lose them. + + +edit warnings (warn) +: +John``Miller starts editing a page and Jane``Doe thinks she'll edit the same page. When she hits edit she'll see a warning telling her that someone else got there first. If she is polite she'll leave the page, but she can still save before John and he may lose his changes. + + +edit locking (lock) +: +John``Miller starts editing a page and Jane``Doe thinks she'll edit the same page. When she hits edit she'll see a warning telling her that someone else got there first and the page is locked. She will have to wait for the page to become available. + + diff --git a/HelpOnEditing.mdwn b/HelpOnEditing.mdwn new file mode 100644 index 00000000..1058aa4b --- /dev/null +++ b/HelpOnEditing.mdwn @@ -0,0 +1,23 @@ + + +## Page Editing + +Names of pages have to [[LookLikeThis|LookLikeThis]]. It's called a [[WikiName|WikiName]]. If you write a word that [[LookLikeThis|LookLikeThis]], it will be automatically turned into a link. More details about this you find on [[HelpForBeginners|HelpForBeginners]]. + +The following pages describe the elements (wiki markup) you can use to get special formatting effects: + +* [[HelpOnFormatting|HelpOnFormatting]] - general text formatting rules +* [[HelpOnLinking|HelpOnLinking]] - external hyperlinks and inline images +* [[HelpOnHeadlines|HelpOnHeadlines]] - section headings +* [[HelpOnRules|HelpOnRules]] - horizontal rules +* [[HelpOnLists|HelpOnLists]] - lists and indented sections +* [[HelpOnTables|HelpOnTables]] - tables +* [[HelpOnPageCreation#variablesubstitution|HelpOnPageCreation]] - which variables are substituted (like @****SIG@, @****MAILTO@ ...) +* [[HelpOnSmileys|HelpOnSmileys]] - how to insert a :) +* [[HelpOnMacros|HelpOnMacros]] - system macros +* [[HelpOnProcessors|HelpOnProcessors]] - data processing scripts +* [[HelpOnProcessingInstructions|HelpOnProcessingInstructions]] - how to influence page formatting +* [[HelpOnXmlPages|HelpOnXmlPages]] - how to store pages with XML content and process them via XSLT +* [[HelpOnEditLocks|HelpOnEditLocks]] - how to behave correctly when edit locking is activated +* [[/SubPages|HelpOnEditing/SubPages]] - how to group together related information +To experiment with wiki markup, go to the [[WikiSandBox|WikiSandBox]] and then click on "Edit****Text" at the bottom of the page. Use your browser's "open a new window with this link" feature on the word "[[WikiSandBox|WikiSandBox]]", so you can keep the help pages open side-by-side to the editing window. diff --git a/HelpOnEditing/SubPages.mdwn b/HelpOnEditing/SubPages.mdwn new file mode 100644 index 00000000..ba1e4985 --- /dev/null +++ b/HelpOnEditing/SubPages.mdwn @@ -0,0 +1,39 @@ + +[[HelpContents|HelpContents]] > [[HelpOnEditing|HelpOnEditing]] + + +## Creating Subpages + +Subpages are groups of pages that share a common prefix, which itself is another page. While this is also possible with "classic" wiki, by using names like `SomeTopicSubTopic`, the use of `SomeTopic/SubTopic` allows better navigational support, and you can omit the common prefix when linking from the parent page to the child page. + +Thus, by using "/" to concatenate several [[WikiName|WikiName]]****s, you can create arbitrarily deep hierarchies (within limits, especially the length of filenames on your system). In reality, subpages are normal pages that contain a "/" in their name, and thus they are stored besides all other pages in the file system. Subpages are a configurable feature, but they're on by default and it's recommended that you keep it that way, since the help pages themselves use this feature. + +Links to sibling pages start with "`../`", for example ../SubPages (a link to this page). + + +### Example + + +[[!format txt """ + * HelpOnEditing/SubPages + * [wiki:HelpOnEditing/SubPages This very page] + * [wiki:Self:HelpOnEditing/SubPages This very page] + * /ThirdLevel + * [wiki:/ThirdLevel A page below this one] + * ../SubPages + * ["../"] (anonymous parent link) + * [:../:free parent link] +"""]] + + + +### Display + +* HelpOnEditing/SubPages +* [[This very page|HelpOnEditing/SubPages]] +* [[This very page|HelpOnEditing/SubPages]] +* [[/ThirdLevel|HelpOnEditing/SubPages/ThirdLevel]] +* [[A page below this one|HelpOnEditing/SubPages/ThirdLevel]] +* ../SubPages +* [[../|HelpOnEditing]] (anonymous parent link) +* [[free parent link|HelpOnEditing]] /!\ Please do all of us a favour and don't create the [[/ThirdLevel|HelpOnEditing/SubPages/ThirdLevel]] pages, it's just an example!
\ No newline at end of file diff --git a/HelpOnFormatting.moin b/HelpOnFormatting.moin new file mode 100644 index 00000000..a798d2f3 --- /dev/null +++ b/HelpOnFormatting.moin @@ -0,0 +1,66 @@ +##language:en
+== Text Formatting Rules ==
+
+Leave blank lines between paragraphs. Use {{{[[BR]]}}} to insert linebreaks into paragraphs.
+
+You can render text in ''italics'' or '''bold'''.
+To write italics, enclose the text in double single quotes.
+To write bold, enclose the text in triple single quotes.
+__Underlined text__ needs a double underscore on each side.
+You get ^superscripted text^ by enclosing it into caret characters,
+and ,,subscripts,, have to be embedded into double commas.
+
+To insert program source without reformatting in a {{{monospace font}}}, use three curly braces:
+{{{
+10 PRINT "Hello, world!"
+20 GOTO 10
+}}}
+
+Note that within code sections, both inline and display ones, any wiki markup is ignored. An alternative and shorter syntax for `inlined code` is to use backtick characters (note that this can be disabled by the site's configuration, but is enabled by default).
+
+For more information on the possible markup, see HelpOnEditing.
+
+=== Example ===
+{{{
+__Mixing__ ''italics'' and '''bold''':
+ * '''''Mix''' at the beginning''
+ * '''''Mix'' at the beginning'''
+ * '''Mix at the ''end'''''
+ * ''Mix at the '''end'''''
+
+You might recall ''a''^2^ `+` ''b''^2^ `=` ''c''^2^ from your math lessons, unless you head is filled with H,,2,,O.
+
+An { { {inline code sequence} } } has the start and end markers on the same line. Or you use `backticks`.
+
+A code display has them on different lines: { { {
+'''No''' markup here!
+} } }
+}}}
+/!\ In the above example, we "escaped" the markers for source code sequences by inserting spaces between the curly braces.
+
+=== Display ===
+__Mixing__ ''italics'' and '''bold''':
+ * '''''Mix''' at the beginning''
+ * '''''Mix'' at the beginning'''
+ * '''Mix at the ''end'''''
+ * ''Mix at the '''end'''''
+
+You might recall ''a''^2^ `+` ''b''^2^ `=` ''c''^2^ from your math lessons, unless you head is filled with H,,2,,O.
+
+An {{{inline code sequence}}} has the start and end markers on the same line. Or you use `backticks`.
+
+A code display has them on different lines: {{{
+'''No''' markup here!
+}}}
+
+=== Colorized code displays ===
+There are several ways to get colorized formatting of Python code<<FootNote(There is currently no support for languages other than Python.)>>:
+ 1. start a code display with a line only containing "#!python"
+ 1. embed a file attachment bearing a ".py" extension via "inline:"
+ 1. start a page with a Python format processing instruction ("#format python")
+
+Example: {{{
+#!python
+from colors import palette
+palette.colorize('python')
+}}}
diff --git a/HelpOnHeadlines.mdwn b/HelpOnHeadlines.mdwn new file mode 100644 index 00000000..7ace7ed9 --- /dev/null +++ b/HelpOnHeadlines.mdwn @@ -0,0 +1,28 @@ + + +## Section Headings + +You can create headings by starting and ending a line with up to five equal signs. The heading text is between those markers, separated by a single space. + +Headings can be automatically numbered, you can enable or disable this for each page (see `#pragma section-numbers` on [[HelpOnProcessingInstructions|HelpOnProcessingInstructions]]) and for the whole site (see `show_section_numbers` on [[HelpOnConfiguration|HelpOnConfiguration]]). + +For more information on the possible markup, see [[HelpOnEditing|HelpOnEditing]]. + + +### Example + + +[[!format txt """ + = Heading = + == Subheading == + === Level 3 === + ==== Level 4 ==== + ===== Level 5 ===== +"""]] + + + +### Display + +* = Heading = == Subheading == === Level 3 === ==== Level 4 ==== ===== Level 5 ===== +Note that proper section numbering requires you to order sections according to a valid structure, i.e. correctly nested. Our sample doesn't do this, so you get a different numbering scheme than you might expect. diff --git a/HelpOnInstalling.mdwn b/HelpOnInstalling.mdwn new file mode 100644 index 00000000..06f9ad84 --- /dev/null +++ b/HelpOnInstalling.mdwn @@ -0,0 +1,39 @@ + +[[HelpContents|HelpContents]] > [[HelpOnAdministration|HelpOnAdministration]] > HelpOnInstalling + +[[!toc ]] + + +## How to install your own MoinMoin Wiki + +This page describes the installation procedure applying to [[MoinMoin|MoinMoin]] version 1.1 and up. In the next section, there is a list of real-world [[Installation Scenarios|HelpOnInstalling]] that help you to understand how to apply the instructions in different environments. If you already have a wiki running and want to upgrade, see [[HelpOnUpdating|HelpOnUpdating]]. + +[[/BasicInstallation|HelpOnInstalling/BasicInstallation]] explains the "`setup.py`" step of the installation in more detail. This applies equally to all scenarios, and you should read it before trying a live installation. + +[[/TroubleShooting|HelpOnInstalling/TroubleShooting]] helps with fixing any general problems you might encounter, which apply to any installation platform. + +After a successful installation, you might want to read more about configuration and other options that you, as the wiki administrator, can set up. [[HelpOnAdministration|HelpOnAdministration]] contains links to pages that cover these topics. Especially, the [[HelpOnConfiguration|HelpOnConfiguration]] and [[HelpOnUpdating|HelpOnUpdating]] pages provide additional information regarding wiki setup and maintenance. [[!MoinMoin MoinMoinWinCvs desc="MoinMoinWinCvs"]] and [[!MoinMoin MoinMoinUnixCvs desc="MoinMoinUnixCvs"]] describe how to run your wiki using the current development version from the [[!MoinMoin SourceForge desc="SourceForge"]] CVS repository. +[[!table header="no" class="mointable" data=""" + Please **make sure** that you do **not** accidently put your wiki's **`data/`** directory under a directory directly accessible by your web server (like below document root). Or at least forbid your web server serving anything below `data/` to a user - this is neither needed nor wanted! Your web server needs to serve moin.cgi and the stuff below htdocs **only**. +"""]] + +<a name="installscenarios"></a> +### Sample Installation Scenarios + +The following subpages will show you concrete examples of installation sessions, showing the commands used and explaining what they do. It is highly recommended that you _first_ read the general information on installing (especially the next section of this page) before choosing an installation scenario that best fits your intended use of [[MoinMoin|MoinMoin]]. + +UNIX: + +* [[/ApacheOnUnix|HelpOnInstalling/ApacheOnUnix]] +Windows: + +* [[/ApacheOnWin32|HelpOnInstalling/ApacheOnWin32]] +* [[/InternetInformationServer|HelpOnInstalling/InternetInformationServer]] +Macintosh: + +* [[/ApacheOnMacOsx|HelpOnInstalling/ApacheOnMacOsx]] +Long-Running-Process Setup: + +* [[/ApacheWithFastCgi|HelpOnInstalling/ApacheWithFastCgi]] +* [[/ApacheWithModPython|HelpOnInstalling/ApacheWithModPython]] +* [[/TwistedWeb|HelpOnInstalling/TwistedWeb]]
\ No newline at end of file diff --git a/HelpOnLinking.mdwn b/HelpOnLinking.mdwn new file mode 100644 index 00000000..d762ee24 --- /dev/null +++ b/HelpOnLinking.mdwn @@ -0,0 +1,75 @@ + + +## Arbitrary Page Names + +If you enclose a sequence of characters in square brackets and double quotes `["like this"]`, that makes it a page name. That can be used for specific uses of [[MoinMoin|MoinMoin]] (like organizing a list of items, e.g. your CD collection, by their "natural" name), or if you want to create a wiki with a non-western character encoding. + +/!\ **This is a configurable feature enabled by `allow_extended_names`, so it might not work!** + + +## URLs and Inline Images + +There are several way to insert external references[^1] into the text: + +* direct URL insertion; if the URL ends in an image extension ("`.gif`", "`.jpg`" or "`.png`"), the URL is converted to an image tag. +* bracketed URLs. +* [[InterWiki|InterWiki]] links. +* email addresses. +If you enter URLs into normal text, there is the problem of detecting what belongs to the URL and what not. There are four ways to force the ending of an URL: + +* put a space after the URL. +* use the [[!c2 SixSingleQuotes desc="SixSingleQuotes"]] escaping. +* put the URL into double quotes. +* use the bracketed URL syntax. +The supported URL schemes are: `http`, `https`, `ftp`, `nntp`, `news`, `mailto`, `telnet`, and `file`. The administrator of your wiki can extend the supported schemes by using the `config.url_schemas` variable (see [[HelpOnConfiguration|HelpOnConfiguration]]). + +In addition to the standard schemes, there are [[MoinMoin|MoinMoin]]-specific ones: `wiki`, `attachment`, `inline`, and `drawing`. "`wiki`" indicates an [[InterWiki|InterWiki]] link, so `MoinMoin:FrontPage` and `wiki:MoinMoin:FrontPage` are equivalent; you will normally prefer the shorter form, the "`wiki`" scheme becomes important when you use bracketed links, since there you always need a scheme. The other three schemes are related to file attachments and are explained on [[HelpOnActions/AttachFile|HelpOnActions/AttachFile]]. + +When the configuration option `bang_meta` is set to true, you can surpress [[WikiName|WikiName]] linking by putting an exclamation mark (_bang_) before the [[WikiName|WikiName]], i.e. `!WikiName`. This is deactivated by default. + +For more information on the possible markup, see [[HelpOnEditing|HelpOnEditing]]. For details on how to link to subpages, see [[HelpOnEditing/SubPages|HelpOnEditing/SubPages]]. + +[^2] + + +### Example + + +[[!format txt """ + * http://moin.sourceforge.net/ + * [http://moin.sourceforge.net/] + * [http://moin.sourceforge.net/ MoinMoin Sourceforge Homepage] + * http://moin.sourceforge.net/moinmoin.gif + * [http://moin.sourceforge.net/moinmoin.gif] + * [http://moin.sourceforge.net/moinmoin.gif moinmoin.gif] + * InterWiki + * Self:InterWiki + * MeatBall:InterWiki + * wiki:MeatBall/InterWiki + * [wiki:MeatBall/InterWiki] + * [wiki:MeatBall/InterWiki InterWiki page on MeatBall] + * jh@web.de + * [#anchorname Anchor Link] +"""]] + + + +### Display + +* [[http://moin.sourceforge.net/|http://moin.sourceforge.net/]] +* [[http://moin.sourceforge.net/|http://moin.sourceforge.net/]] +* [[MoinMoin Sourceforge Homepage|http://moin.sourceforge.net/]] +* [[!img http://moin.sourceforge.net/moinmoin.gif] +* [[http://moin.sourceforge.net/moinmoin.gif|http://moin.sourceforge.net/moinmoin.gif]] +* [[moinmoin.gif|http://moin.sourceforge.net/moinmoin.gif]] +* [[InterWiki|InterWiki]] + * [[InterWiki|InterWiki]] + * [[!MeatBall InterWiki desc="InterWiki"]] + * [[!MeatBall InterWiki desc="InterWiki"]] + * [[!MeatBall InterWiki desc="InterWiki"]] + * [[!MeatBall InterWiki desc="InterWiki page on MeatBall"]] +* [[jh@web.de|mailto:jh@web.de]] +* [[Anchor Link|HelpOnLinking]] + +[^1] The opposite of external references are the internal, automatic WikiName links. +[^2] None diff --git a/HelpOnLists.mdwn b/HelpOnLists.mdwn new file mode 100644 index 00000000..3ba5d0c1 --- /dev/null +++ b/HelpOnLists.mdwn @@ -0,0 +1,102 @@ + + +## Lists and Indenting + +You can create bulleted and numbered lists in a quite natural way. All you do is inserting the line containing the list item. To get bulleted items, start the item with an asterisk "`*`"; to get numbered items, start it with a number template "`1.`", "`a.`", "`A.`", "`i.`" or "`I.`". Anything else will just indent the line. To start a numbered list with a certain initial value, append "`#`_value_" to the number template. + +To nest lists of different levels, you use different depths of indenting. All items on the same indent level belong to the same (sub-)list. That also means that you cannot change the style of a list after you started it. + +Definition lists can be created by items of the form `<whitespace>term:: definition`; note that the _term_ cannot currently contain any wiki markup. + +For more information on the possible markup, see [[HelpOnEditing|HelpOnEditing]]. + + +### Example + + +[[!format txt """ +If you indent text + like this, then it is indented in the output + you can have multiple levels of indent + +And if you put asterisks at the start of the line + * you get a + * bulleted + * list + * which can also be indented + * to several levels + +A numbered list, mixed with bullets: + 1. one + 1. two + 1. one + * bullet 1 + * bullet 2 + 1. two + 1. three + * bullet + 1. one + +Variations of numbered lists: + * Lowercase roman + i. one + i. two + * Uppercase roman (with start offset 42) + I.#42 forty-two + I. forty-three + * Lowercase alpha + a. one + a. two + * Uppercase alpha + A. one + A. two + + term:: definition + another term:: and its definition +"""]] + + + +### Display + +If you indent text + + * like this, then it is indented in the output + * you can have multiple levels of indent +And if you put asterisks at the start of the line + + * you get a + * bulleted + * list + * which can also be indented + * to several levels +A numbered list, mixed with bullets: + + 1. one + 1. two + 1. one + * bullet 1 + * bullet 2 + 1. two + 1. three + * bullet + 1. one +Variations of numbered lists: + + * Lowercase roman + 1. one + 1. two + * Uppercase roman (with start offset 42) + 1. forty-two + 1. forty-three + * Lowercase alpha + 1. one + 1. two + * Uppercase alpha + 1. one + 1. two term +: definition + +another term +: and its definition + diff --git a/HelpOnMacros.moin b/HelpOnMacros.moin new file mode 100644 index 00000000..63dd5cf1 --- /dev/null +++ b/HelpOnMacros.moin @@ -0,0 +1,64 @@ +##language:en
+##||{{{[[ ]]}}} || || ||
+<<Navigation(children)>>
+<<TableOfContents>>
+
+== Macros ==
+Macros allow the insertion of system features into normal wiki pages; the only thing that makes those pages special is that they contain macros. If you edit pages like RecentChanges or SystemInfo, you'll see what that means.
+
+For more information on the possible markup, see HelpOnEditing.
+
+=== Search macros ===
+||'''Macro'''||'''Description'''||'''Example'''||
+||{{{[[TitleSearch]]}}} || search the page titles || See the FindPage ||
+||{{{[[FullSearch]]}}} || search the page contents || See the FindPage ||
+||{{{[[FullSearch()]]}}} || search for the current title in all pages (like clicking on the page title) || See the CategoryCategory page ||
+||{{{[[FullSearch('text')]]}}} || search for "text" in all pages || Search for {{{FullSearch}}}:<<FullSearch('FullSearch')>> ||
+||{{{[[GoTo]]}}} || directly go to the page you enter || See the FindPage ||
+||{{{[[PageList(regex)]]}}} || list of pages whose title matches the regex || See the HelpIndex ||
+
+=== Navigation ===
+||'''Macro'''||'''Description'''||'''Example'''||
+||{{{[[RecentChanges]]}}} || a list of recently edited pages || See RecentChanges ||
+||{{{[[TitleIndex]]}}} || an index of all page titles || See TitleIndex ||
+||{{{[[WordIndex]]}}} || an index of all words in page titles || See WordIndex ||
+||{{{[[WantedPages]]}}} || list links to non-existent pages || See WantedPages ||
+||{{{[[OrphanedPages]]}}} || list pages no other page links to || See OrphanedPages ||
+||{{{[[AbandonedPages]]}}} || list pages that were not edited for the longest time || See AbandonedPages ||
+||{{{[[RandomPage]]}}} || a link to a random page || <<RandomPage>> ||
+||{{{[[RandomPage(#)]]}}} || links to a number of random pages || Two random pages:<<RandomPage(2)>> ||
+||{{{[[TableOfContents([maxdepth])]]}}} || display a local table of contents, possibly limited to a maximal depth || See above ||
+||{{{[[Anchor(anchorname)]]}}} || macro to insert anchors into a page || <<Anchor(here)>>[[#here]] ||
+||{{{[[Navigation(children[,maxdepth])]]}}} || macro to list all of a pages' children || See start of this page ||
+||{{{[[Navigation(siblings[,maxdepth])]]}}} || quick navigation to siblings of a page || See /MailTo ||
+||{{{[[Navigation(slideshow)]]}}} || creates a link to toggle between slide show and wiki mode, and a link to start the slide show || See HelpOnSlideShows ||
+||{{{[[Navigation(slides)]]}}} || displays first/prev/next/last links || See HelpOnSlideShows ||
+
+=== System information ===
+||'''Macro'''||'''Description'''||'''Example'''||
+||{{{[[InterWiki]]}}} || a list of all known InterWiki names || InterWiki ||
+||{{{[[SystemInfo]]}}} || info on the wiki, the python interpreter and the host system || SystemInfo ||
+||{{{[[PageCount]]}}} || current page count || <<PageCount>> pages ||
+||{{{[[PageSize]]}}} || list the sizes of all pages || See PageSize ||
+||{{{[[StatsChart(type)]]}}} || shows statistical charts (currently defined types: hitcounts, pagesize, useragents) || See EventStats and subpages ||
+||{{{[[SystemAdmin]]}}} || Web interface to wiki administration (not completed yet as of version 1.0) || See SystemInfo ||
+
+=== Others ===
+||'''Macro'''||'''Description'''||'''Example'''||
+||{{{[[Icon(image)]]}}} || display system icons || See HelpOnNavigation ||
+||{{{[[UserPreferences]]}}} || display a user preferences dialog || See UserPreferences ||
+||{{{[[BR]]}}} || insert a line break || 1st line<<BR>>2nd line ||
+||{{{[[RandomQuote(pagename)]]}}} || Select a random quote from the given page, or from `FortuneCookies` if ommitted || <<RandomQuote>> ||
+||{{{[[Include(HelloWorld[,"heading"[,level]])]]}}} || include contents of another page || for details see [[/Include]] ||
+||{{{[[FootNote(text)]]}}} || Add a footnote (the text cannot contain any wiki markup), or explicitely display collected footnotes when no args are given || See HelpOnPageCreation for an example ||
+||{{{[[Date(timestamp)]]}}} || display a timestamp according to system settings || <<Date>> ||
+||{{{[[DateTime(timestamp)]]}}} || display a timestamp<<FootNote("timestamp" can be empty (current time), a number of seconds since 1970 (unix timestamp), or a W3C time specification ("2002-01-23T12:34:56").)>> according to user settings || <<DateTime>> ||
+||{{{[[GetText(text)]]}}} || loads I18N texts (mainly intended for use on Help pages) || "Edit``Text" is translated to "<<GetText(EditText)>>" ||
+||{{{[[TeudView]]}}} || useful for intranet developer wikis, a means to view pydoc documentation, formatted via a XSLT stylesheet, for details see EfnetPythonWiki:TeudProject || See EfnetPythonWiki:TeudViewer?module=MoinMoin.macro.TeudView ||
+||{{{[[MailTo(email)]]}}} || protect your email address from spam bots || for details see /MailTo ||
+
+<<FootNote>>
+
+== Example Display ==
+We don't show examples for all macros here, because that would make this page quite long. Here is is the replacement text for the {{{[[SystemInfo]]}}} macro:
+ <<SystemInfo>>
diff --git a/HelpOnNavigation.mdwn b/HelpOnNavigation.mdwn new file mode 100644 index 00000000..1b9b2ded --- /dev/null +++ b/HelpOnNavigation.mdwn @@ -0,0 +1,20 @@ + + +## Navigation + +The header on each page allows you to go to the [[FrontPage|FrontPage]] (home), [[RecentChanges|RecentChanges]] (recent modifications), [[TitleIndex|TitleIndex]] (index of all the page titles), [[WordIndex|WordIndex]] (index of all the words in the page titles), [[SiteNavigation|SiteNavigation]] (list of navigation tools), and [[HelpContents|HelpContents]] (main help page). + +On the upper right you find icons for the most often used functions: + + * jumps to the parent page, and is only shown if you are on a subpage (see [[HelpOnEditing/SubPages|HelpOnEditing/SubPages]]) + * refreshes the current page + * shows a printable version of the page without the header or footer + * creates a XML version of the page (currently still experimental, creates [[!MoinMoin StyleBook desc="StyleBook"]], a [[!MoinMoin DocBook desc="DocBook"]] variant) + * / allows to subscribe to email notifications for the current page, the brighter version means you have already subscribed to a page + * allows you to say something, i.e. edit the page + * shows meta information about the page, especially the full version history + * shows changes between the current version and the previous version of the page + * shows the search page. + * shows the help page + * links to a user's homepage, if the user is logged in and a page with his login name exists +Clicking on the Page Title link located in the header above will show every page that references this page. A sample use of this back-referencing, inverted-links feature is the categorization of pages, i.e. [[CategoryHomepage|CategoryHomepage]]. On the bottom of each page, you find the "traditional" edit and search links known from the original wiki, and in addition fields for quick-searching titles and the page texts, plus links to call any custom actions you have installed. diff --git a/HelpOnPageCreation.mdwn b/HelpOnPageCreation.mdwn new file mode 100644 index 00000000..cbb3edf0 --- /dev/null +++ b/HelpOnPageCreation.mdwn @@ -0,0 +1,44 @@ + + +## Creating a New Page + +To create a page, add its [[WikiName|WikiName]] to an existing page and save it. After that, you can click on it on the revised page, since it automatically becomes a hyperlink. + +You will then be presented with your new page, which you can edit in the normal way. After you _first_ saved it, it will be automatically created. Pages normally[^1] cannot be deleted, so be sure to spell new [[WikiName|WikiName]]****s correctly. + +On details on how to create and link to subpages, see [[HelpOnEditing/SubPages|HelpOnEditing/SubPages]]. + + +## Creating and Using Template Pages + +To create a template, follow the above description and create a page with a name ending in "**Template**"[^2]. This page will then be added to the list of template pages displayed when you try to show a non-existant page. For example, [[NonExistantHelpPage|NonExistantHelpPage]] has a link to [[HelpTemplate|HelpTemplate]] that loads the content of [[HelpTemplate|HelpTemplate]] into the editor box, when you click on that link. + + +## Variable Substitution when Saving a Page + +<a name="variablesubstitution"></a> The following variables are substituted when a page is _finally_ saved. Note that they'll appear unreplaced in the preview! +[[!table header="no" class="mointable" data=""" + @****PAGE@ | Name of the page (useful for template pages) + @****DATE@ | Current date in the system's format + @****TIME@ | Current date and time in the user's format + @****USERNAME@ | Just the user's name (or his domain/IP) + @****USER@ | Signature "-- loginname" + @****SIG@ | Dated Signature "-- loginname date time" + @****MAILTO@ | A fancy mailto: link with the user's data +"""]] + +Note that saving template or form definition pages and using preview does _not_ expand variables. Other than that, variable expansion is very global and happens anywhere on the page, including code displays, comments, processing instructions and other "special" areas of a page you might think are excluded. + + +# Editor backup + +If the user has a homepage[^3] indicated by the icon, a backup of save/preview text is saved either as subpage `Home``Page``Name/Moin``Editor``Backup` (if subpages are allowed) or as page `Home``Page``Name``Moin``Editor``Backup` (if subpages are not allowed). + +So if you preview often, you will keep your changes, even if your browser crashes. + +Remark: this used to be an attachment to the homepage named `moin-editor-backup.txt`, but that was changed with introduction of Access``Control``Lists (see [[HelpOnAccessControlLists|HelpOnAccessControlLists]]) due to security problems. + + +[^1] Deleting pages can be activated by the wiki administrator (which you'll normally do in intranet sites only). +[^2] If the wiki administrator changed the default settings, rules for what names are template pages might be different. +[^3] Having a homepage means you're logged in under a name that is also the name of an existing wiki page. diff --git a/HelpOnProcessingInstructions.mdwn b/HelpOnProcessingInstructions.mdwn new file mode 100644 index 00000000..be7c8bef --- /dev/null +++ b/HelpOnProcessingInstructions.mdwn @@ -0,0 +1,22 @@ + + +## Processing Instructions + +[[MoinMoin|MoinMoin]] processing instructions have the same semantics as in XML: they control the paths taken when processing a page. Processing instructions are lines that start with a "`#`" character followed by a keyword and optionally some arguments; the keyword is always handled case-insensitive. Two consecutive hash marks at the start of a line are a comment that won't appear in the processed page. + +Processing instructions this wiki knows of: + +* `##` _any-text_: comment +* `#FORMAT` _format-specifier_: defines the input format for this page, known formats are: + * **Wiki**: default [[MoinMoin|MoinMoin]] wiki markup + * **Plain**: normal plain text + * **Python**: colorized Python source + * **[[StructuredText|StructuredText]]** ( [!] not implemented) +* `#REDIRECT` _pagename_: redirect to a different page (see [[!MeatBall PageRedirect desc="PageRedirect"]]****) +* `#REFRESH` _delay_ _[pagename_or_URL]_: redirect to a different page (or an external URL or just refresh the same page, if left out - use `config.refresh` to enable) +* `#PRAGMA` _mode_ _args_: sets processing modes for this page; mode names are not case-sensitive, currently known modes are: + * `#pragma section-numbers off` (or "0") switches off automatic numbering of section headers and "on" or "1" enables numbering (the default mode is set by the `show_section_numbers` config option). `#pragma section-numbers 2` only displays section numbers for headings of level 2 and up (similarly for 3 to 6). +* `#DEPRECATED`: Mark this page as deprecated, i.e. further changes to the page will create no backup versions and displaying it will show the current contents (usually the reason why this page is deprecated) plus the last backup. This effectively freezes the last version of the page, makes it unavailable for searches (no hits on stale content), but keeps that content available for viewing. +All PIs must appear at the very start of a page. An exception are comment PIs, those may appear anywhere within a page using "wiki" format (but not in pages using other formats). + +For more information on the possible markup, see [[HelpOnEditing|HelpOnEditing]]. diff --git a/HelpOnProcessors.moin b/HelpOnProcessors.moin new file mode 100644 index 00000000..bb3f7b4b --- /dev/null +++ b/HelpOnProcessors.moin @@ -0,0 +1,44 @@ +##language:en
+<<TableOfContents>>
+
+== Processors ==
+
+Processors work on the data in a code display. You specify which processor to call by using a ''bang path''-like construct in the first line. A bang path is a concept known from Unix command line scripts, where they serve the exact same purpose: the first line tells the shell what program to start to process the remaining lines of the script.
+
+For more information on the possible markup, see HelpOnEditing.
+
+=== Colorize ===
+
+The `Colorize` processor currently knows of Python sources, and can syntax-hilight them. Besides the canonical way to call that processor, MoinMoin also recognizes a traditional bang path on the first line of the script, as long as it contains "`python`".
+
+Example:
+{{{
+#!python
+if lines[0].contains("python"):
+ print "colors!"
+}}}
+
+<<Anchor(csvprocessor)>>
+=== CSV ===
+
+The CSV processor works on so-called ''comma separated values'', though the comma is now usually a semicolon.
+The first line is considered to contain column titles that are rendered in '''bold''', so when you don't want table headers, leave the first line empty.
+
+The bang path can contain "`-`''index''" arguments, to hide certain columns from the output; column indices are counted starting from 1.
+
+ /!\ The current code contains a ''very'' simple CSV parser.
+
+MoinMoin Version History: {{{#!CSV -3
+Version;Date;HIDDEN!
+0.11;2002-03-11;Revision 1.151
+0.10;2001-10-28;Revision 1.134
+0.9;2001-05-07;
+0.8;2001-01-23;
+0.7;2000-12-06;
+0.6;2000-12-04;
+0.5;2000-11-17;
+0.4;2000-11-01;
+0.3;2000-10-25;
+0.2;2000-08-26;
+0.1;2000-07-29;
+}}}
diff --git a/HelpOnRules.mdwn b/HelpOnRules.mdwn new file mode 100644 index 00000000..7a5b625f --- /dev/null +++ b/HelpOnRules.mdwn @@ -0,0 +1,61 @@ + + +## Horizontal Rules + +You can insert a horizontal rule across the page by typing four or more dashes. The number of dashes in a horizontal rule markup determines how thick it is, up to a limit of 10. + +For more information on the possible markup, see [[HelpOnEditing|HelpOnEditing]]. + + +### Example + + +[[!format txt """ +--- (not a rule) +---- +----- +------ +------- +-------- +--------- +---------- +-------------------------------------------- (not thicker than 10) +"""]] + + + +### Display + +--- (not a rule) + +--- + + + +--- + + + +--- + + + +--- + + + +--- + + + +--- + + + +--- + + + +--- + + (not thicker than 10) diff --git a/HelpOnSmileys.moin b/HelpOnSmileys.moin new file mode 100644 index 00000000..cb5b268e --- /dev/null +++ b/HelpOnSmileys.moin @@ -0,0 +1,8 @@ +##language:en
+== Graphical Smileys ==
+To insert a smiley, just type in your favourite from the table below. They're only converted to an icon though if they are ''surrounded by whitespace''.
+
+<<ShowSmileys>>
+
+For more information on the possible markup, see HelpOnEditing.
+
diff --git a/HelpOnTables.moin b/HelpOnTables.moin new file mode 100644 index 00000000..b236d897 --- /dev/null +++ b/HelpOnTables.moin @@ -0,0 +1,67 @@ +##language:en
+== Table Markup ==
+To create a table, you start and end a line using the table marker "{{{||}}}". Between those start and end markers, you can create any number of cells by separating them with "{{{||}}}". To get a centered cell that spans several columns, you start that cell with more than one cell marker. Adjacent lines of the same indent level containing table markup are combined into one table.
+
+For more information on the possible markup, see HelpOnEditing.
+
+=== Table Attributes ===
+
+Apart from the option to repeat cell markers to get columns spanning several other columns, you can directly set many HTML table attributes. Any attributes have to be placed between angle brackets {{{<...>}}} directly after the cell marker.
+
+The wiki-like markup has the following options:
+ * {{{<50%>}}}: cell width
+ * {{{<-2>}}}: colspan
+ * {{{<|2>}}}: rowspan
+ * {{{<(>}}}: left aligned
+ * {{{<:>}}}: centered
+ * {{{<)>}}}: right aligned
+ * {{{<^>}}}: aligned to top
+ * {{{<v>}}}: aligned to bottom
+ * {{{<#XXXXXX>}}}: background color
+
+If you use several conflicting options like {{{<(:)>}}}, the last option wins. There is no explicit option for vertical centering (''middle''), since that is always the default.
+
+In addition to these, you can add some of the traditional, more long-winded HTML attributes (note that only certain HTML attributes are allowed). By specifying attributes this way, it is also possible to set properties of the table rows and of the table itself, especially you can set the table width using {{{||<tablewidth="100%">...||}}} in the very first row of your table, and the color of a full row by {{{||<rowbgcolor="#FFFFE0">...||}}} in the first cell of a row. As you can see, you have to prefix the name of the HTML attribute with {{{table}}} or {{{row}}}.
+
+=== Example ===
+{{{
+ General table layout and HTML like options::
+ ||||||<tablewidth="80%">'''Heading'''||
+ ||cell 1||cell2||cell 3||
+ ||<rowspan=2> spanning rows||||<bgcolor='#E0E0FF'> spanning 2 columns||
+ ||<rowbgcolor="#FFFFE0">cell2||cell 3||
+ Cell width::
+ || narrow ||<:99%> wide ||
+ Spanning rows and columns::
+ ||<|2> 2 rows || row 1 ||
+ || row 2 ||
+ ||<-2> row 3 over 2 columns ||
+ Alignment::
+ ||<(> left ||<^|3> top ||<v|3> bottom ||
+ ||<:> centered ||
+ ||<)> right ||
+ Colors::
+ ||<#FF8080> red ||<#80FF80> green ||<#8080FF> blue ||
+}}}
+
+=== Display ===
+ General table layout and HTML like options::
+ ||||||<tablewidth="80%">'''Heading'''||
+ ||cell 1||cell2||cell 3||
+ ||<rowspan=2> spanning rows||||<bgcolor='#E0E0FF'> spanning 2 columns||
+ ||<rowbgcolor="#FFFFE0">cell2||cell 3||
+ Cell width::
+ || narrow ||<:99%> wide ||
+ Spanning rows and columns::
+ ||<|2> 2 rows || row 1 ||
+ || row 2 ||
+ ||<-2> row 3 over 2 columns ||
+ Alignment::
+ ||<(> left ||<^|3> top ||<v|3> bottom ||
+ ||<:> centered ||
+ ||<)> right ||
+ Colors::
+ ||<#FF8080> red ||<#80FF80> green ||<#8080FF> blue ||
+
+=== Insert Table Data from other sources ===
+ * comma separated values: see [[HelpOnProcessors#csvprocessor]]
diff --git a/HelpOnUserPreferences.mdwn b/HelpOnUserPreferences.mdwn new file mode 100644 index 00000000..6f2b842e --- /dev/null +++ b/HelpOnUserPreferences.mdwn @@ -0,0 +1,36 @@ + + +## Setting your UserPreferences + +You may self-register and establish your preferences by clicking on the [[UserPreferences|UserPreferences]] link at the top right corner of every page. If you have registered and are logged in, your name will be displayed instead of "User``Preferences". + +The various fields in User``Preferences are described below: + +* **Name**: Either your real name or an alias. Best is to use [[WikiName|WikiName]] format. + * If ACLs are enabled, it is **required** to be a unique [[WikiName|WikiName]]. +* **Password**: Something you can remember but is very hard for friends and family to guess. +* **Password repeat**: if you initially set or later change your password, repeat it here to avoid typos. +* **Email**: Your email address, this is required if you wish to subscribe to wiki pages or wish to have a forgotten login data mailed to you. + * If ACLs are enabled, the email address is required to be unique and valid. +* **Preferred theme**: choose a theme to change colours, icons and layout of the wiki +* **User CSS URL**: If you want to override some of the wiki system's css, put your own CSS here. +* **Editor size**: [!] This controls the size of the text area when you edit a page. Adjust this to suit the size of your monitor and your personal preferences. +* **Time zone**: ... + * **Your time is**: If the correct time is not displayed, use the drop down box and select the correct time. + * **Server time is**: Displays the server time. +* **Date format**: The default of year-month-day is least confusing for international use. +* **Preferred language**: The default is taken from your browser setting. It is advisable to set this to a specific language anyway, since then you get notification mails in your native tongue, too. +* **General options**: ... + * **Add spaces to displayed wiki names**: If checked, makes **Wiki``Names** look like **Wiki Names**. + * **Open editor on double click**: Handy if you edit a lot of pages. + * **Remember last page visited**: When you point your browser at the wiki's base URL (i.e. the one not mentioning a specific page), you will see the last page visited. This can be useful if you are frequently reading or editing a single page. + * **Remember login information forever**: When you set this, the cookie won't expire at midnight. + * **Show emoticons**: A fun thing, see /!\ and ;-) instead of `/!\` and `;-)`. + * **Show fancy diffs**: Makes diffs more readable. + * **Show fancy links**: Show the little icons that indicate the type of link, for WWW, for FTP, and so on. + * **Show icon toolbar**: Provides a row of icon links in the upper right corner. + * **Show question mark for non-existing pagelinks**: Display a highlighted **?** in front of a non-existant page instead of a color-coded page name. + * **Show page trail**: Lists the last five pages visited at the top of the page, so you can jump back several pages easily. + * **Show top/bottom links in headings**: If checked, every title bar will have an up and down arrow to navigate to top or bottom of page. +* **Quick links**: Overrides the standard choices in the gray navigation bar at the top of the page. Enter one Wiki page name per line. You may also add free-form links, i.e. entries of the form `[url linktext]` just like in wiki pages. +* **Subscribed wiki pages (one regex per line)**: Enter **`.*`** to receive an email when any page in this Wiki changes (_not recommended_ for busy wikis), or enter the names of any individual pages, one per line. If you are familiar with **regular expressions**, you may enter a regex expression to match the pages names of interest (.* matches all page names). With the **Show icon toolbar** option checked, subscription to individual pages is made easy by clicking the envelope icon when viewing a page of interest. /!\ This is an optional feature that only works when email support has enabled for this wiki, see [[HelpOnConfiguration/EmailSupport|HelpOnConfiguration/EmailSupport]] for details.
\ No newline at end of file diff --git a/HelpOnXmlPages.mdwn b/HelpOnXmlPages.mdwn new file mode 100644 index 00000000..f7f6750a --- /dev/null +++ b/HelpOnXmlPages.mdwn @@ -0,0 +1,36 @@ + + +## XML Pages & XSLT Processing + +If you have [[Python4Suite|http://4suite.org/]] installed in your system, it is possible to save XML documents as pages. It's important to start those pages with an XML declaration "`<?xml ...>`" in the very first line. Also, you have to specify the stylesheet that is to be used to process the XML document to HTML. This is done using a [[standard "xml-stylesheet" processing instruction|http://www.w3.org/TR/xml-stylesheet/]], with the name of a page containing the stylesheet as the "`href`" parameter. + +See the following example for details, which can also be found on the [[XsltVersion|XsltVersion]] page. + + +### Example + + +[[!format txt """ +<?xml version="1.0" encoding="ISO-8859-1"?> + +<?xml-stylesheet href="XsltVersion" type="text/xml"?> + +<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> + + <xsl:output method="html" omit-xml-declaration="yes" indent="no"/> + + <xsl:template match="/"> + This Wiki is running an XSLT engine by + <xsl:value-of select="system-property('xsl:vendor')"/> + (<a href="{system-property('xsl:vendor-url')}"><xsl:value-of select="system-property('xsl:vendor-url')"/></a>) + implementing XSLT v<xsl:value-of select="system-property('xsl:version')"/> + </xsl:template> + +</xsl:stylesheet> +"""]] + + + +### Display + +[[!inline pages="XsltVersion" quick="yes" raw="yes"]] diff --git a/HelpTemplate.mdwn b/HelpTemplate.mdwn new file mode 100644 index 00000000..d0f18010 --- /dev/null +++ b/HelpTemplate.mdwn @@ -0,0 +1,19 @@ + + +## Template for Help Pages + +Text. + + +### Example + + +[[!format txt """ +xxx +"""]] + + + +### Display + +xxx diff --git a/InputEventProcessing.mdwn b/InputEventProcessing.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/InputEventProcessing.mdwn diff --git a/Intel28Branch.mdwn b/Intel28Branch.mdwn new file mode 100644 index 00000000..e37a0994 --- /dev/null +++ b/Intel28Branch.mdwn @@ -0,0 +1,42 @@ + + +## Proposed patches + +Since xf86-video-intel 2.8.1 has been released, nominations here will be considered for future 2.8.x bugfix releases, if we do any. + +Below here, please list patches to nominate them for merging into the [[2.8 branch|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/?h=2.8]]. The commits must already exist in the [[master branch|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/]], and have received review and testing there. + +Proposed for 2.8.x (once these are merged, move them down to the next list) + + * +--- + + + +* [[7c48c21b22bf5862c5a35bda1635753cc5a7197c|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=7c48c21b22bf5862c5a35bda1635753cc5a7197c]] set correct value for indirect access check bound +* [[376397c21eb9a7e4ea79d349af41da81c1af861f|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=376397c21eb9a7e4ea79d349af41da81c1af861f]] Fix VGA plane disabling +* [[62494407e529cfa68529b7267155a12d75418f21|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=62494407e529cfa68529b7267155a12d75418f21]] Fix typo in bios_reader for invalid pointer cast +* [[6955fc7a74edf6034a292c31a304577c35e925e6|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6955fc7a74edf6034a292c31a304577c35e925e6]] Don't use fb offset when using shadow buffer +* [[2786a66719a6dbb735eb7c551c412475c30ffa51|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=2786a66719a6dbb735eb7c551c412475c30ffa51]] KMS: allocate one bo per crtc for cursor +* [[5fa8d04d9c86f343802c05bd3e11c6e733f01b63|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=5fa8d04d9c86f343802c05bd3e11c6e733f01b63]] Reload cursors as needed when setting new modes. +Released in 2.8.1 + + * +--- + + + +* [[6f3fc6b20f3daedab02e31f49678d4d2ff0fa7a3|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6f3fc6b20f3daedab02e31f49678d4d2ff0fa7a3]] drmmode_output_get_modes: Replace existing EDID property blob with new one +* [[6b7728491c3b771bcba2c7ffd75330c0a0b37f44|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6b7728491c3b771bcba2c7ffd75330c0a0b37f44]] Only align DRI2 tiled pixmaps to the DRI2 tiled pixmap alignment requirement +* [[af45482a52999b52bf41468c458808e30c100e35|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=af45482a52999b52bf41468c458808e30c100e35]] Calculate the DVO relative offset in LVDS data entry to get the DVO timing (fixes #22787 and Debian #538148) +* [[79b6851148574419389ac8055b0c31b8bdac3ab3|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=79b6851148574419389ac8055b0c31b8bdac3ab3]] Fix sampler indexes on i965 planar video. +* [[465a4ab416b2e5ad53b96702720331a44fffa2fe|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=465a4ab416b2e5ad53b96702720331a44fffa2fe]] Align the height of untiled pixmaps to 2 lines as well. +Released in 2.8.0.901 + + * +--- + + + + * [[8084f76d86f048ca5b82da089fffa9665dbbcdd5|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=8084f76d86f048ca5b82da089fffa9665dbbcdd5]] Allow DRM mode setting to include transformations + * [[222b52ef16895823fbf3a0fc0be4eb23b930ed1b|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=222b52ef16895823fbf3a0fc0be4eb23b930ed1b]] Align tiled pixmap height so we don't address beyond the end of our buffers (also include [[e8f0763d405a8152c74c28792c52fe12c1d41dd5|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=e8f0763d405a8152c74c28792c52fe12c1d41dd5]] Fix math in the tiling alignment fix)
\ No newline at end of file diff --git a/Intel29Branch.mdwn b/Intel29Branch.mdwn new file mode 100644 index 00000000..dc90de8e --- /dev/null +++ b/Intel29Branch.mdwn @@ -0,0 +1,36 @@ + + +## Proposed patches + +Since xf86-video-intel 2.9.1 has been released, nominations here will be considered for future 2.9.x bugfix releases, if we do any. + +Below here, please list patches to nominate them for merging into the [[2.9 branch|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/?h=2.9]]. The commits must already exist in the [[master branch|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/]], and have received review and testing there. + +For each fix, please provide a short description of the bug being fixed in terms that make sense to the user, (which I will put in the release notes). The commit message is rarely the right thing here, (since it will often refer to internals). Often the title of a bug report is exactly what's wanted, so if your commit message already includes a bugzilla URL then that's likely sufficient. + +As an example of what I'd like for the descriptions: + +What I don't want: Fix uninitialized pScrnPtr value. What I do want: Fix crash on X server start with multiple outputs. + +Proposed for 2.9.x (once these are merged, move them down to the next list) + +--- + + + +Merged for 2.9.x + +--- + + + +Released in 2.9.1 + +--- + + + +* [[8a77877f9c2c6a8a1308bc1a3be9e7ad88bc7f49|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=8a77877f9c2c6a8a1308bc1a3be9e7ad88bc7f49]] drmmode: with 1.7 server, set mode major doesn't get gamma setup. (Fixes orruption and artifacts due to wrong colors in the colormap with X server 1.7.) +* [[7e8f32d0a7279dce1976f87612833d9092554cfe|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=7e8f32d0a7279dce1976f87612833d9092554cfe]] uxa: Free the [[ScratchPixmapHeader|ScratchPixmapHeader]] after its associated Picture (Fixes incorrect rendering, such as missing scrollbar arrows in some themes: [[http://bugs.freedesktop.org/show_bug.cgi?id=24459|http://bugs.freedesktop.org/show_bug.cgi?id=24459]]) +* [[fcc2ee48b866b81c79315ff10189b56fc201539d|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=fcc2ee48b866b81c79315ff10189b56fc201539d]] Drop frontbuffer from crtc in [[I830CloseScreen|I830CloseScreen]] (Fixes black screen when X server is reset: [[https://bugs.freedesktop.org/show_bug.cgi?id=24383|https://bugs.freedesktop.org/show_bug.cgi?id=24383]]) +* Revert [[02fe9be695f7e209944bd0f7b67950f93619feee|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=02fe9be695f7e209944bd0f7b67950f93619feee]] Check whether the DVI-I/D is connected or disconnected based on EDID (Fixes regressions detecting DVI monitors: [[http://bugs.freedesktop.org/show_bug.cgi?id=24458|http://bugs.freedesktop.org/show_bug.cgi?id=24458]] [[http://bugs.freedesktop.org/show_bug.cgi?id=24458|http://bugs.freedesktop.org/show_bug.cgi?id=24458]] [[http://bugs.freedesktop.org/show_bug.cgi?id=24458|http://bugs.freedesktop.org/show_bug.cgi?id=24458]])
\ No newline at end of file diff --git a/IntelVideoDriver.mdwn b/IntelVideoDriver.mdwn new file mode 100644 index 00000000..938e01d4 --- /dev/null +++ b/IntelVideoDriver.mdwn @@ -0,0 +1,7 @@ + +For more information on the X drivers for Intel graphics, (including full documentation for several devices), please see [[http://intellinuxgraphics.org/|http://intellinuxgraphics.org/]] + +Proposals for addition to stable releases: + + * [[Proposals for the 2.9 branch|Intel29Branch]] + * [[Proposals for the 2.8 branch|Intel28Branch]]
\ No newline at end of file diff --git a/InterWiki.moin b/InterWiki.moin new file mode 100644 index 00000000..36b8b9d4 --- /dev/null +++ b/InterWiki.moin @@ -0,0 +1,14 @@ +##language:en
+InterWiki links are a quick way to refer to information in other wikis, without having to remember
+cryptic URLs. To write an InterWiki link, just use the InterWiki moniker of the foreign wiki,
+followed by a page name on that wiki.
+Of course, InterWiki links are not rendered differently when the remote page does not exist, and
+MoinMoin cannot check whether you followed the rules for WikiName``s of the other wiki.
+So double-check what you type.
+See the MeatBall:InterWiki page on MeatBall:MeatballWiki for further details.
+
+List of valid InterWiki names this wiki knows of:<<BR>>
+(the list is maintained at InterWikiMap)
+<<InterWiki>>
+
+MoinMoin marks the InterWiki links in a way that works for the MeatBall:ColourBlind and also is MeatBall:LynxFriendly by using a little icon with an ALT attribute. If you hover above the icon in a graphical browser, you'll see to which Wiki it refers. If the icon has a border, that indicates that you used an illegal or unknown BadBadBad:InterWiki name (see the list above for valid ones). BTW, the reasoning behind the icon used is based on the idea that a Wiki:WikiWikiWeb is created by a team effort of several people.
diff --git a/JeremyHuddleston.mdwn b/JeremyHuddleston.mdwn new file mode 100644 index 00000000..597d84bd --- /dev/null +++ b/JeremyHuddleston.mdwn @@ -0,0 +1,13 @@ + + +## Jeremy Huddleston + +Email: jeremyhu AT SPAMFREE freedesktop DOT org + +[[http://xquartz.macosforge.org|http://xquartz.macosforge.org]] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/JhBuildInstructions.mdwn b/JhBuildInstructions.mdwn new file mode 100644 index 00000000..a43fb227 --- /dev/null +++ b/JhBuildInstructions.mdwn @@ -0,0 +1,118 @@ + + +# Building modular X.org with ''jhbuild'' + + +## Introduction + +This page provides brief instructions on using _[[jhbuild|http://live.gnome.org/Jhbuild]]_, a Python-based build tool, to build modular X.Org. jhbuild was written to build GNOME from source, but has been adapted to many other projects. + + +## Prerequisites + +* Ubuntu 9.10: + * jhbuild: `sudo apt-get install git-core gnome-common libglib2.0-dev docbook-xsl subversion automake1.4 automake1.7 automake1.9 automake1.10 guile-1.8 waf` + * Xorg: `sudo apt-get install groff zlib1g-dev libfreetype6-dev libxml2-dev docbook gperf flex bison libssl-dev` +* Debian 5.0 (lenny): + * jhbuild: `sudo apt-get install git-core gnome-common gnome-doc-utils make automake1.4 automake1.7 automake1.9 docbook-xsl cvs subversion guile-1.8` + * Xorg: `sudo apt-get install groff zlib1g-devlib freetype6-dev g++ bison flex` ... +* Fedora 12: + * jhbuild: `sudo yum install @gnome-devel @development-tools gnome-common glib2-devel gnome-doc-utils docbook-style-xsl waf` + * Xorg: `sudo yum install zlib-devel freetype-devel libxml2-devel expat-devel gperf libgcrypt-devel` +* Cygwin: + * jhbuild: Devel/git, GNOME/gnome-common, Devel/subversion + * Xorg: X11/libfreetype-devel, Devel/gperf ... +* FreeBSD 8.0: + * jhbuild: ports `devel/git`, `devel/gnome-common`, `devel/autoconf262`, `devel/automake14`, `devel/automake17`, `devel/automake18`, `devel/automake19`, `devel/automake110`, `devel/glib20`, `devel/subversion` (don't use Apache 2.0 APR!), `textproc/gnome-doc-utils` (select all options for docbook-1.4!), `textproc/intltool`, `lang/guile` + * Xorg: ports `print/freetype2` ... + +## Building jhbuild + + +[[!format txt """ +git clone git://git.gnome.org/jhbuild +cd jhbuild +./autogen.sh +make +make install +cp sample.jhbuildrc ~/.jhbuildrc +"""]] +(On FreeBSD, do `gmake && gmake install` .) + +* Note: You may get an error message `msgfmt isn't installed` - it's in the GNU gettext package +* Note: You may get a message saying you need to run `make -f Makefile.plain install` - All this omits is building the documentation, which is also at [[http://library.gnome.org/devel/jhbuild/|http://library.gnome.org/devel/jhbuild/]] +The `jhbuild` executable is installed to ~/.local/bin/jhbuild. You will need to either symlink to it, use the full path or add it to your `$PATH`. + + +## Module Set and jhbuild Config File + +The [[moduleset|http://cgit.freedesktop.org/xorg/util/modular/tree/xorg.modules]] for jhbuilding xorg and [[an example jhbuildrc|http://cgit.freedesktop.org/xorg/util/modular/tree/jhbuildrc]] are stored in git in the xorg/util/modular repository. + + +## Building the Server, and Everything It Depends On + +To build everything, you can do: + + +[[!format txt """ +mkdir -p $HOME/xorg/util +git clone git://anongit.freedesktop.org/git/xorg/util/modular/ $HOME/xorg/util/modular +jhbuild -f $HOME/xorg/util/modular/jhbuildrc +"""]] +But often you would just want to build the X server and key drivers to enable support of your latest shiny hardware, without replacing all of your X libraries and utilities. In this case, you can build specific targets rather than everything. + +You will need a minimal number of drivers as well as the server; rather than executing separate jhbuild commands, you can issue a single one listing all the targets you want to build. The input drivers for PS/2 keyboards and mice are: _xf86-input-keyboard _and_ xf86-input-mouse_. + +To build the server and dependencies, along with these drivers, you would type: + + +[[!format txt """ +jhbuild -f $HOME/xorg/util/modular/jhbuildrc build xserver xf86-video-intel xf86-input-keyboard xf86-input-mouse +"""]] +Other interesting targets include _xorg-drivers_ which builds all maintained X.org drivers. + +Note: rather than building the target xorg-fonts, which will build you an entire additional set of fonts, you may want to make a link in your _$prefix_ area to link to your existing fonts. Unless you have built your X server with `--enable-builtin-fonts `it will need to access some fonts to start, even though few applications need legacy bitmap fonts anymore. + + +[[!format txt """ +cd $prefix/lib/X11; ln -s /usr/share/fonts/X11 fonts +"""]] +Other drivers you may need include the synaptics driver and/or wacom drivers, currently maintained elsewhere (fixme...). + + +## DRM and Kernel Modules + +The X server is finally using a device driver on many systems (e.g. Linux, BSD); this is called DRM. It consists of two parts, the generic DRM module and a driver specific to your hardware. Currently, the kernel modules are not built automatically by jhbuild; you can find them in _drm/linux-core_ or _drm/bsd-core_. To build the drm driver, +[[!format txt """ +make -C linux-core +"""]] +You may want to install these where you will be able to use them from your _/etc/modules_ file. + + +## Building Other Modules + +Other buildable modules include the applications (e.g. `xbiff`) and the libraries (e.g. `libXfixes`), plus there a couple of meta modules; `xorg-libs` will build all libs and `xorg-apps` will build all apps. + + +## Running The Results + +Now that your development environment is set up, you can try running it (as root). +[[!format txt """ +rmmod i915 # assuming you're using Intel +rmmod drm +insmod <path_to_drm_tree_above>/linux-core/drm.ko +insmod <path_to_drm_tree_above>/linux-core/i915.ko +export LD_LIBRARY_PATH=$prefix/lib +startx -- $prefix/bin/Xorg -verbose # make sure you have a ~/.xinitrc with what you want to run +"""]] +And there you have it, a fresh stack ready for tracking & doing upstream development. Enjoy! + +This page and the modules file for the build were originally written by Kristian Høgsberg, and modified by [[EricAnholt|EricAnholt]]. Wikified by [[JimGettys|JimGettys]]. + + +## Hiccups + +* libGL runs "make" straight after the git pull ([[bug 26337|https://bugs.freedesktop.org/show_bug.cgi?id=26337]]). Workaround: shell out, run <del>`./autogen.sh --prefix=$HOME/xorg-build`</del> , exit shell and try again. +* Some drivers don't or shouldn't build (_e.g._ [[geode on 64-bit|https://bugs.freedesktop.org/show_bug.cgi?id=26341]], [[impact not on MIPS|https://bugs.freedesktop.org/show_bug.cgi?id=26342]], [[sunbw2|https://bugs.freedesktop.org/show_bug.cgi?id=26343]]). Abandon module, file bug if you can work out what's wrong. + * There's no facility in jhbuild to mark these modules as only appropriate to some targets, so to permanently avoid building these modules, add the module to the **skip** configuration variable in your jhbuildrc configuration file. e.g. skip = [ 'xf86-video-impact', 'xf86-video-sunbw2' ] +* nouveau won't build unless you already have libdrm_nouveau built. One way to do so is setting temporarily autogenargs = '--enable-nouveau-experimental-api' in jhbuildrc, and use the `buildone libdrm` jhbuild command.
\ No newline at end of file diff --git a/JoeKrahn.mdwn b/JoeKrahn.mdwn new file mode 100644 index 00000000..f8ed397b --- /dev/null +++ b/JoeKrahn.mdwn @@ -0,0 +1,13 @@ + + +## Joe Krahn + +Email: Joseph.Krahn AT SPAMFREE gmail DOT com + +Nothing here but an email link for now. + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/KnowledgeBase.mdwn b/KnowledgeBase.mdwn new file mode 100644 index 00000000..f518e3e3 --- /dev/null +++ b/KnowledgeBase.mdwn @@ -0,0 +1,6 @@ + + +# Video Drivers + + * [[Projects/Drivers|Projects/Drivers]] lists the currently supported video drivers and provides useful links +-- Main.[[EgbertEich|EgbertEich]] - 15 Apr 2004 diff --git a/KristianHoegsberg.mdwn b/KristianHoegsberg.mdwn new file mode 100644 index 00000000..3d662866 --- /dev/null +++ b/KristianHoegsberg.mdwn @@ -0,0 +1,15 @@ + + +## Kristian Høgsberg + +In the future we'll have wikis that allow UTF-8 in page names. + +Email: [[krh@bitplanet.net|mailto:krh@bitplanet.net]] + +... + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/LinuxTag2005Infos.mdwn b/LinuxTag2005Infos.mdwn new file mode 100644 index 00000000..8250f694 --- /dev/null +++ b/LinuxTag2005Infos.mdwn @@ -0,0 +1,32 @@ + + +# Useful Information for our LinuxTag meeting + + +## Travel: + + * Travel information [[in German|http://www.linuxtag.org/typo3site/travel.html?&L=0]] [[in English|http://www.linuxtag.org/typo3site/travel.html?&L=1]] + +## Karlsruhe City Map + +* [[City Map|http://geodaten.karlsruhe.de/stadtplan/]] + [[Map|http://hydra.linuxtag.uni-kl.de/~joey/ka-shopping/]] of the area around the LinuxTag location with useful infos on shopping and eating places. + [[Area Map|http://www.infodrom.org/Debian/events/LinuxTag2002/lageplan.html]] and [[version for printing|http://hydra.hq.linuxtag.net/~joey/LT2005/akk.ps]]. + +## Karlsruhe City Info + + * City Information [[in German|http://www.linuxtag.org/typo3site/cityinfo.html?&L=0]] [[in English|http://www.linuxtag.org/typo3site/cityinfo.html?&L=1]] + +## Information on Public Transportation + + * [[local transportation|http://www.efa-bw.de/nvbw/en_index.htm]] + * [[Railroad|http://reiseauskunft.bahn.de/bin/query.exe/en?to=76137/Karlsruhe,%20Kongresszentrum]] + * Infos on flights etc. [[in German|http://www.linuxtag.org/typo3site/travel.html?&L=0]] [[in English|http://www.linuxtag.org/typo3site/travel.html?&L=1]] + +## Accommodations + + * The Karlsruhe LUG is providing limited free space at AKK to stay over night. Please visit [[their web page|http://www.akk.org/]] for further information. This space is only available during the show, not for the X developers meeting. However there are other inexpensive alternatives: + * [[youth hostel|http://www.jugendherberge-karlsruhe.de/]] (booked out for the show) + * very inexpensive: [[ETAP hotel Karlsruhe-Ost.|http://www.etaphotel.com/etaphotel/fichehotel/gb/etp/3179/fiche_hotel.shtml]] (Booked out for the show.) + * Official [[LinuxTag|LinuxTag]] hotel is the Novotel Dorint Karlsruhe Kongress Reservations can be made either thru the LinuxTag reservation page [[in German|http://www.linuxtag.org/typo3site/hotels.html?&L=0]] [[in English|http://www.linuxtag.org/typo3site/hotels.html?&L=1]] or [[directly|http://www.accorhotels.com/accorhotels/fichehotel/de/nov/5400/fiche_hotel.shtml]]. The weekend are usually lower however one will have to expect to pay special rates during the show. + * The Tourist Information has a [[web site|http://www.karlsruhe.de/Tourismus/ukv/]] for online search/registration
\ No newline at end of file diff --git a/LinuxTagMeeting2005.mdwn b/LinuxTagMeeting2005.mdwn new file mode 100644 index 00000000..9c85c0b8 --- /dev/null +++ b/LinuxTagMeeting2005.mdwn @@ -0,0 +1,102 @@ + + +# The European X.Org Developers Meeting + +* Time: Sunday June 19th and Monday June 20th 2005 +* Place: **[[LinuxTag|http://linuxtag.org]]** in Karlsruhe, Germany. +The X.Org Foundation is planning its first European Developers Meeting right before **[[LinuxTag|http://linuxtag.org]]** in Karlsruhe, Germany ** on Sunday June 19th and Monday June 20th**. + +The **purpose** of the conference is to bootstrap a European developers community. + +We expect to have 5-6 **talks** a day, 3 in the morning and 3 in the afternoon. This gives plenty of time to add additional presentations and discussions as well as extensive hacking. + +The **conference language** is English. + + +## Call For Papers + +There are still slots open for presentations so if you are interested in giving a talk please send us the title and a brief abstract to our [[contact address|LinuxTagMeeting2005]]. + +Presentations will be accepted until the first day of the conference, however we encourage you to contact us early as interest is great. + + +## Schedule + +Please check our preliminary [[LinuxTagMeeting2005Schedule|LinuxTagMeeting2005Schedule]]. + + +## Fees + +The conference will have **free entrance**, participants will have to pay travel and accommodation. + +Some **funding** is available to X.Org to sponsor travel and accommodation for people who are unable to take care of these expenses themselves. People applying for this should be prepared to give a talk. When submitting your abstract please indicate if you require funding. + +We are still working on getting free admission to the LinuxTag show for all those who participate in the conference - at least those who give a presentation. + +We've got a number of tickets that we will distribute among those participants who don't have other ways of getting into the show (for example as exhibitors) if they have [[registered|LinuxTagMeeting2005]] with us and indicated their need for a ticket. As the number of ticktets is limited please only get one if you really plan to go to the show. + +X.Org will organize a social event for all those who participate in the meeting. (Don't confuse this with the [[LinuxTag social event|http://www.linuxtag.org/typo3site/socialevent.0.html?L=1]]!) Admission is free for those who are giving a presentation on the meeting. Please see [[below|LinuxTagMeeting2005]] for further information. + + +## Location + +The meeting will take palce in room **S1** in the **upper level** of the **Konzerthaus**. Please check the [[area map|http://www.infodrom.org/Debian/events/LinuxTag2002/lageplan.html]] for the exact location. You can find links to further maps and information in our [[LinuxTag2005Infos|LinuxTag2005Infos]]. + + +_Please NOTE:_ The location of the room may still change, therefore make sure to check this page for updated information. + There is a [[list of participants|LinuxTagMeeting2005Participants]]. + + +# X.Org on LinuxTag + +X.Org is also going to have booth on [[LinuxTag|http://linuxtag.org]] from Wednesday, June 22, to Saturday, June 25. + +This booth is ment to be a gathering place where developers can meet and talk. At the same time people will be available on the booth to give demonstrations and to talk to the public. + + +## Presentations + +We are still looking for people who would like to give an X Window System related presentation on the show. Please indicate if you are willing to do so and what you would like to present. + +Tuesday, June 21 is planned for booth setup for all those who would like to give a presentation. + We expect that not all presentations can run simultaneously so once we get a rough idea of what you have planned to demo we will make up a schedule. + You should be prepared to bring your own equipment for your demo (ie. Laptop etc.), monitors or flat screens should be available on the booth, also there will be connectivity on the booth. If you need other special equipment that you won't be able to bring along we will do our best to provide it. Please indicate with your registration if you have special needs. + +If you have a **logo and/or a poster** in your demo please send us a PostScript file. We will try to print it and put it on display on the booth. + + +## Social Event + +<a name="social_event"></a> Everybody deserves a break! + +There will be a social event (not to be confused with the [[LinuxTag social event|http://www.linuxtag.org/typo3site/socialevent.0.html?L=1]]) for the people attending our meeting or participating in the booth activities to get together, eat, drink and talk. It will take place during LinuxTag right after the show. + +We don't know the exact location and date, yet. This information will be given when available + +The **costs** will be around EUR 20, for all those who give a presentation on our meeting or on the booth, or otherwise help with our booth activities admission will be free. If you are interested in coming - please let us know! + + +## Booth Helpers + +We are looking for volunteers to help out with booth duty. If you are interested please let us know. You will receive a free X.Org LinuxTag T-shirt as a little thank you. + + +## Further Information + +Please check the [[LinuxTag2005Infos|LinuxTag2005Infos]] for useful information concerning travel and accomodiations. + + +## Documentation + +Please send us your ideas and notes from the conference. As for pictures - please upload them to you website and send us its address. Thankyou! + + +## Organizers + +* The X.Org Foundation +* Leon Shiman +* Egbert Eich + +## Contacts + +<a name="contact"></a> Please feel free to contact the organizers at [[linuxtag-org_AT_lists_x_DOT_org|mailto://<linuxtag-org_AT_lists_x_DOT_org>]] if you have further questions. diff --git a/LinuxTagMeeting2005Participants.mdwn b/LinuxTagMeeting2005Participants.mdwn new file mode 100644 index 00000000..114032e6 --- /dev/null +++ b/LinuxTagMeeting2005Participants.mdwn @@ -0,0 +1,25 @@ + + +# List of Participants + +Gian Filippo Pinzari + Matthias Hopf + David Reveman + Gunnar Schmidt + Luc Verhaegen + Zack Rusin + Kai-Uwe Behrmann + Alan Hourihane + Keith Packard + Leon Shiman + Daniel Stone + Egbert Eich + Harald Koenig + Dirk Mueller + Marc Lehmann + Amir Bukhari + Lars Knoll + Matthieu Herrb + Waldo Bastian + Nicolai Hähnle + Roland Mainz diff --git a/LinuxTagMeeting2005Schedule.mdwn b/LinuxTagMeeting2005Schedule.mdwn new file mode 100644 index 00000000..eac1a63d --- /dev/null +++ b/LinuxTagMeeting2005Schedule.mdwn @@ -0,0 +1,39 @@ + + +# Meeting Schedule + + +## Sunday (June 19, 2005) + +15:00 + + * Leon Shiman: The X.Org Foundation - an Overview + Luc Verhaegen: [[What needs to happen in the DDX?|LinuxTagMeeting2005Luc]] + Egbert Eich: Migrating to a new driver model. [[slides|LinuxTagMeeting2005EgbertEich.pdf]] + Alan Hourihane: ACPI, how it works and what we need to do. + Leon Shiman: Managing media with X + +18:00 + + +## Monday (June 20, 2005) + +9:30 + + * Gunnar Schmidt: [[Magnification with X.Org 6.8|LinuxTagMeeting2005Gunnar]]. + Daniel Stone: [[The Modularisation Project|LinuxTagMeeting2005Daniel]] [[Slides (HTML)|http://people.freedesktop.org/~daniels/exdctalk]]. + Kai Uwe Behrmann: [[X and colour management|LinuxTagMeeting2005KaiUwe]]. + +12:30 + + * Lunch +14:00 + + * Keith Packard: What's new about Cairo?. + Zack Rusin: [[A redesign of the acceleration architecture|LinuxTagMeeting2005Zack]]. + Lars Knoll: [[Improving and extending Render|LinuxTagMeeting2005Lars]]. + David Reveman: [[Xgl|LinuxTagMeeting2005DavidR]]. + Matthias Hopf: [[Xvideo auf Xgl|LinuxTagMeeting2005Matthias]]. + Gian Filippo Pinzari: [[NoMachine NX|LinuxTagMeeting2005GianFilippo]]. + +19:00 diff --git a/LinuxTagMeeting2005Schedule/LinuxTagMeeting2005EgbertEich.pdf b/LinuxTagMeeting2005Schedule/LinuxTagMeeting2005EgbertEich.pdf Binary files differnew file mode 100644 index 00000000..dffd8d69 --- /dev/null +++ b/LinuxTagMeeting2005Schedule/LinuxTagMeeting2005EgbertEich.pdf diff --git a/LookingGlassIntegration.mdwn b/LookingGlassIntegration.mdwn new file mode 100644 index 00000000..7dacf732 --- /dev/null +++ b/LookingGlassIntegration.mdwn @@ -0,0 +1,19 @@ + + +# LookingGlass Integration + +This page describes the effort to migrate the some changes for Looking Glass into the Xserver for a future X.Org release. Note: This is not an effort to migrate all of the Looking Glass technology into the X.Org source tree - only those infrastructural pieces needed by the Xserver to operate with the other Looking Glass components. + + +## What is Project Looking Glass? + +Project Looking Glass is a Java-based 3D desktop. You can learn more about the overall technology by reading the [[Overview|http://www.freedesktop.org/~pma/doc/J1-TS1586-final.pdf]]. + + +## More information + +Additional information about Looking Glass and the proposed changes to the X.Org tree are available at the links below: + + * [[The Looking Glass Event Pipeline|http://www.freedesktop.org/~pma/doc/lg_event_trip.pdf]] + * [[Proposed Modifications|http://www.freedesktop.org/~pma/doc/lg_xorg_mods.pdf]] + * [[Looking Glass Extension Protocol Specification|http://www.freedesktop.org/~pma/doc/lge_protocol.pdf]]
\ No newline at end of file diff --git a/MakingReleases.mdwn b/MakingReleases.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/MakingReleases.mdwn diff --git a/MartinPeres.mdwn b/MartinPeres.mdwn new file mode 100644 index 00000000..fe906f86 --- /dev/null +++ b/MartinPeres.mdwn @@ -0,0 +1,23 @@ + + +## Martin Peres + +Email: martin.peres AT SPAMFREE ensi-bourges DOT fr Nickname: mupuf + +Martin Peres is PhD student at LaBRI. His thesis topic is on Power consumption and security in wireless networks. Martin was an engineering student at the 'ENSI de Bourges' where he studied and researched on computer security. + +Martin has been interested in programmation since the age of 12. He as first work on several game projects but moved to more low-level stuffs. He is the creator of PPassKeeper([[http://ppasskeeper.mupuf.org|http://ppasskeeper.mupuf.org]]), a library meant to abstract password storing. + +His interest upon X.org because of the lack of support of my ATI XPress 200M card. He then followed the development of the radeon driver and have been an happy tester on the xpress 200M and, more recently, on my AMD HD4770. He also happen to have caught interest in the nouveau project when he was given a laptop with an nvidia graphic card by his school. His involvement in X.org has got stronger when he was proposed to help in nouveau's development. + +At the moment, Martin is working on power management for nouveau. + +His real homepage with CV & portfolio: [[http://mupuf.org/contact/mupuf|http://mupuf.org/contact/mupuf]] + +His research page is located at : [[http://phd.mupuf.org|http://phd.mupuf.org]] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/MattDew.mdwn b/MattDew.mdwn new file mode 100644 index 00000000..1a24f0cd --- /dev/null +++ b/MattDew.mdwn @@ -0,0 +1,64 @@ +[[!table header="no" class="mointable" data=""" +**TODO**|| +Item | Status +Enable crosslinking | done +Enable profiling | no-profiling for now. +Adding crosslinks in documents | done +Master databases for website target | done +Pretty up xorg.css | done +Pretty up xorg.xsl | done +Hyphenation warning during build | Figured out. Uses jarfile but need to look more into .jar file licensing +Conversion of .gif to .svg | ? +New Index page | 20% +Initial Docbook conversion | done +Linking to doxygen | not started +Set colwidth in tables to .0 (floating point)' | 80% +Either change fonts in xorg.xsl or figure out which fonts are needed. | not started +Table warnings on <literallayout> during build | not started +epub generation (with dbtoepub) | not started +Catch up with [[http://tronche.com/gui/x/|http://tronche.com/gui/x/]] in regards to niceness of webpages. | not started +change <literallayout class='monospaced'> to <informaltable> with tgroups | not started +change <function>...</function> to <emphasis role='bold'>...</emphasis> for bolding | not started +use <simplelist type='vert' columns='N'><member> where appropriate (see x11proto/sect1-9.xml for example) | not started +Key Action's table in xkbproto, bulleted items offset. (~pg 24) | not started +gifs in xkbproto, scaled wrong | not started +"""]] + +Link collection: + + * [[http://www.youtube.com/watch?NR=1&v=j4REAaY2_-c|http://www.youtube.com/watch?NR=1&v=j4REAaY2_-c]] [[http://en.wikibooks.org/wiki/Guide_to_X11|http://en.wikibooks.org/wiki/Guide_to_X11]] +--- Not so frequently asked questions: + +1) How to play a sound on xterm event (using xkbevd): + + * A) [[http://ubuntuforums.org/showthread.php?t=1632133|http://ubuntuforums.org/showthread.php?t=1632133]] +2) Prevent pointer from going outside screens in a multiscreen environment. + + * A) [[https://bugs.freedesktop.org/show_bug.cgi?id=32731|https://bugs.freedesktop.org/show_bug.cgi?id=32731]] +3) XEvIE = Event Interception Extension, EVI = Extended Visual Information EVIE != EVI + +'ssh -X' vs 'ssh -Y' [12:46] <marcoz> general question. any real different between ssh -X and ssh -Y, '-Y' is for trusted connections but what does that actually mean? [12:47] <drago01> -X limits what you can do [12:47] <drago01> for security reason [12:47] <drago01> (to block key loggers etc) [12:47] <pharris> marcoz: -X uses the XSECURITY extension to create an "untrusted" magic cookie. Clients that connect via -X can't do certain things (eg. [[GetImage|GetImage]] from the root window) [12:47] == gustavold [gustavold@nat/ibm/x-bdcunkwjseyyztxg] has quit [Ping timeout: 245 seconds] [12:47] <drago01> while -Y is pretty much like a local connection [12:49] == jg_ [~[[jg@135.245.8.6|mailto:jg@135.245.8.6]]] has quit [Read error: Connection reset by peer] [12:49] <marcoz> ok, so default should be -X and not -Y then. [12:50] <marcoz> do you regularly use them? just curious if in practice you normally have trouble with -X where -Y works or vice versay [12:51] <ajax> -X breaks many things if you're running a server that actually supports the security extension. [12:51] <pharris> -X is a good default, but there are a few corner cases where -X doesn't work. eg. running an Xephyr with no other clients, SSH connects, creates a new magic cookie, disconnects, the server resets and forgets the cookie, the x client connects and the server rejects it. [12:51] <ajax> gtk mostly gets it right but i don't think xaw or motif do [12:52] <ajax> also the additional "security" created by -X is pretty much illusory anyway [12:52] <pharris> Also, the obvious things that -X intentionally prevents. It prevents screen captures, so you can't (usefully) run a screen capture over it. [12:52] <ajax> the attack it prevents is people being able to override file MAC on the remote machine, but if your attacker can do _that_ they can just replace the binary you think you're running. [12:53] <ajax> so any interaction you're having with the forwarded app is already suspect [13:30] <jturney> -X also breaks things if you don't have the security extension now, as since OpenSSH 5.6 it enforces [[ForwardX11Timeout|ForwardX11Timeout]] even when falling back to a trusted connection... + +EVoC/GSoC email to students to drum up interest: Work in progress. + +--- + + + + * My name is Matt Dew and I work on the X.org project. X.org[1] is the X windowing system for Linux, BSD, UNIX. If you run a GUI on linux or one of the BSDs or UNIXs then you most likely are using X.org. + * Google Summer of Code[2] is approaching and X.org is looking for bright, capable students who are interested in working on the Linux graphics stack. Google hasn't officially announced GSoC for 2012, but now is the time to start looking around to see if you're interested. For those who aren't aware, GSoC is a program where google pays students to work on open source projects. X.org has a complementary program called Endless Vacation of Code[3] (EVoC) for students whose schedules don't fit with GSoC. We have work in OpenGL/Mesa, graphics shaders, graphics drivers, state trackers, code refactoring, multi-touch and gestures work, automated testing, documentation, color management, etc.[4] You'll get to work with developers at AMD, Intel, NVidia, [[RedHat|RedHat]], Canonical, as well as others. I won't kid you. The work is challenging, not everyone's application is accepted and you will have to work hard to pass. But the people on the project are very smart and willing to help people who are genuinely interested in learning and wanting to participate and contribute. +Any and all interested students, please contact either me or hop on the irc channel at: irc.freenode.net #xorg or #xorg-devel + +Sincerely, Matt Dew Endless Vacation of Code Coordinator, X.org + +[1] [[http://www.x.org/wiki|http://www.x.org/wiki]] [2] [[http://code.google.com/soc/|http://code.google.com/soc/]] [3] [[http://www.x.org/wiki/XorgEVoC|http://www.x.org/wiki/XorgEVoC]] [4] [[http://www.x.org/wiki/SummerOfCodeIdeas|http://www.x.org/wiki/SummerOfCodeIdeas]] + +--- + + + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/MatthiasHopf.mdwn b/MatthiasHopf.mdwn new file mode 100644 index 00000000..30863651 --- /dev/null +++ b/MatthiasHopf.mdwn @@ -0,0 +1,13 @@ + + +## Matthias Hopf + +Email: [[mat@mshopf.de|mailto:mat@mshopf.de]], [[matthias.hopf@ohm-hochschule.de|mailto:matthias.hopf@ohm-hochschule.de]] + +Homepage: [[www.mshopf.de|http://www.mshopf.de/]] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/MatthieuHerrb.mdwn b/MatthieuHerrb.mdwn new file mode 100644 index 00000000..9fd87d0d --- /dev/null +++ b/MatthieuHerrb.mdwn @@ -0,0 +1,13 @@ + + +## Matthieu Herrb + +Email: matthieu.herrb AT SPAMFREE laas DOT fr + +See [[my real home page|http://www.laas.fr/~matthieu]]. + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/Membership.mdwn b/Membership.mdwn new file mode 100644 index 00000000..a990e978 --- /dev/null +++ b/Membership.mdwn @@ -0,0 +1,18 @@ + + +# Membership + +If you are a contributor to the X Window System technology as shipped by X.Org (developer, documentation writer etc) you may apply for membership in the [[X.Org Foundation|XorgFoundation]]. Membership entitles you to + +* Vote in [[elections|BoardOfDirectors/Elections]] for the [[X.Org Foundation Board|BoardOfDirectors]]. +* Vote on changes to the [[By-Laws|BylawReview]] and the Membership Agreement. +* Vote on other topics as required by the By-Laws or Membership Agreement. +* Chair X.Org Foundation Committees. +* Host X.Org related events. +Furthermore Membership may be required to access certain copyrighted material which the X.Org Foundation is not allowed to distribute publicly. + +The Foundation Bylaws state that "In order to qualify as a Member, a person must, at the time of their application and during the tenure of their membership: (i) be actively involved in the activities relating to the technologies of X.Org, as set forth in the Membership Agreement, and, who, in the consideration of the Board, supports the objects, purposes, aims and objectives of X.Org; and (ii) maintain current and accurate contact information as may be needed for delivery of Notices." + +Membership is aimed at people with a more than casual involvement in X.Org's work. It is not required in order to participate in X.Org's ongoing activities, to access our source code repositories or to subscribe to our mailing lists. Neither does membership provide you with additional information about X.Org's activities and ways you may want to get involved. If you are new to X.Org you probably just want to find out how you can participate. Visit [[XorgMailingLists|XorgMailingLists]] and join one of the mailing lists, or go to [[XorgIRC|XorgIRC]] to find out about the available IRC channels, for more information. + +To apply for membership, or to update or edit your membership record, please visit [[http://members.x.org|http://members.x.org]] diff --git a/MichaelLarabel.mdwn b/MichaelLarabel.mdwn new file mode 100644 index 00000000..e947586b --- /dev/null +++ b/MichaelLarabel.mdwn @@ -0,0 +1,15 @@ + + +## Michael Larabel + +Email: michael AT SPAMFREE michaellarabel DOT com + +Webpage: [[http://www.michaellarabel.com/|http://www.michaellarabel.com/]] + +Twitter: [[http://twitter.com/michaellarabel|http://twitter.com/michaellarabel]] [I will be tweeting my locations when showing various XDC Chicago 2011 attendees around the days prior to the event, for those interested in meeting up.] + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/MichaelVerret.moin b/MichaelVerret.moin new file mode 100644 index 00000000..57ab3d1c --- /dev/null +++ b/MichaelVerret.moin @@ -0,0 +1,9 @@ +##language:en
+== Michael Verret ==
+
+||<rowspan=3>{{http://www.axxium.us/pics/michaelv.png}}||X11 Maintainer for Zenwalk GNU/Linux||
+||Administrator & Webmaster for Zenwalk GNU/Linux||
+||Email: michael DOT verret ~AT~ gmail DOT com||
+
+----
+CategoryHomepage
diff --git a/MichelDaenzer.mdwn b/MichelDaenzer.mdwn new file mode 100644 index 00000000..0a173548 --- /dev/null +++ b/MichelDaenzer.mdwn @@ -0,0 +1,13 @@ + + +## Michel Dänzer + +Email: michel AT SPAMFREE daenzer DOT net + +Working on Radeon drivers. + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/Mirrors.mdwn b/Mirrors.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/Mirrors.mdwn diff --git a/ModeSetting.mdwn b/ModeSetting.mdwn new file mode 100644 index 00000000..baf1f7d4 --- /dev/null +++ b/ModeSetting.mdwn @@ -0,0 +1,57 @@ + +_**Mode Setting Design Discussion**_ + +**Contents:** [[!toc ]] + + +## Introduction + +The current design of having the X server drivers/frame buffer drivers all doing mode setting in the system is starting to cause issues, especially around areas like suspend/resume and with the development of new types of rendering mechanisms for X (like Xgl). + +Mode setting in the kernel is possible for most cards, however a few cards require the use of VBE to set modes especially with external LVDS/TMDS and tv-out controller chips that are undocumented. Mode setting in userspace causes other issues such as at times like suspend/resume and interaction with kernel drivers. + +It looks like a userspace modesetting system with an in-kernel component driver is the best possible solution. Current and future drawing system can interface to this modesetting library and use it to all their modesetting leaving the rendering application (X or Xgl) free to just render. This will also need to tie in with an in-kernel memory management system possibly. + +This document will be in two sections, Modesetting API and some ideas for an implementation of it. + + +## Terminology + +**setter**: application using the modesetting library (not the human sitting at the machine) + +**screen**: a physically viewable object (monitor, TV, the Matrix) + +**device**: a piece of hardware or software that provides access to 0..n screens (0 screens means nothing plugged in at the moment) + + +## API + + +### Requirements + +1. Must be extensible and allow new types of display not handled by the core. + +2. Allow user to enumerate current devices, and screens attached to those devices. + +3. For each screen, allow the setter to enumerate the currently available modes and enable/disable output. + + +### Currently open questions + +1. Show screen surface setup go via the modesetting library? + +the EGL_MESA_screen_surface has the ideas of setting up screen surfaces on a particular screen, in my mind this is more to do with memory management than mode setting. A unified namespace between parties is definitely needed so we can tell what a modesetting device corresponds to. The memory manager would need to be told, that the setter needs an area of VRAM of a certain size and then the mode setter needs to be told to set the mode on the screen and point to the VRAM. + +Comment by [[MichelDaenzer|MichelDaenzer]]: EGL_MESA_screen_surface is intended to be the connection between memory management and mode setting. IMO, neither should the mode setting instance do any memory management, nor should the memory manager (have to) know anything about mode setting. + + +## Implementation + + +### Decisions made so far + +1. Initial implementation can be backended onto a fbdev driver, while an cut-down X server can be worked on to just modeset and not render. + +2. The DRI is necessary for this to work. You don't need a full DMA implementation for a card or anything just a stub driver doing memory management. + +-- [[DavidAirlie|DavidAirlie]] diff --git a/ModularDevelopersGuide.mdwn b/ModularDevelopersGuide.mdwn new file mode 100644 index 00000000..8452db23 --- /dev/null +++ b/ModularDevelopersGuide.mdwn @@ -0,0 +1,388 @@ + + +# The X.Org Modular Tree Developer's Guide + +[[!toc ]] + + +## Introduction + +This guide is for developers who wish to build the X Window System from source. If your area of interest is limited to a single package, like a driver or an application, check with your O/S first for development facilities. + +<a name="RequiredTools"></a> +## Required Tools + +The most common cause of build failures for first time builders is the lack of required tools. There are over 30 tools required to build all of X 200+ packages and half of them are not installed by default on most O/S or Linux distributions. Some tools are only needed by dependent projects: + +* [[Mesa|http://www.mesa3d.org/]] ` ` The Mesa 3D Graphics Library +* [[Pixman|http://cgit.freedesktop.org/pixmanpixman/]] ` ` Low Level Pixel Manipulation Library +* [[XKeyboardConfig|http://www.freedesktop.org/wiki/Software/XKeyboardConfig]] ` ` X Keyboard Configuration Database +It is strongly advised you install such packages from your O/S official packaging system. Check the [[RequiredPackages|RequiredPackages]] for your O/S. Some of the tools may not be required to build some areas of X. Some GNU utility, like make, have native O/S equivalent on non GNU systems. + + +### Source Code Version Control + +* [[git|http://git-scm.com/]] ` ` The fast version control system +<a name="GNUBuildSystem"></a> +### GNU Build System + +* [[autoconf (2.60)|http://www.gnu.org/software/autoconf/]] ` ` Produce shell scripts that automatically configure software source code packages +* [[automake (1.10)|http://www.gnu.org/software/automake/]] ` ` Create GNU standards-compliant Makefiles from template files +* [[gmake|http://www.gnu.org/software/make/]] ` ` The GNU version of the "make" utility to maintain groups of programs +* [[libtool (1.5)|http://www.gnu.org/software/libtool/]] ` ` Provide generic shared library support +* [[pkg-config (0.22)|http://pkg-config.freedesktop.org/wiki/]] ` ` Return metainformation about installed libraries + +### Development Tools + +* [[yacc|http://en.wikipedia.org/wiki/Yacc]] ` ` The original AT&T parser generator or an upward compatible version such as [[bison|http://www.gnu.org/software/bison/]] or [[byacc|http://invisible-island.net/byacc/]] whitout using its specific features +* [[lex|http://en.wikipedia.org/wiki/Lex_%28software%29]] ` ` The original AT&T lexical analyser generator or an upward compatible version such as [[flex|http://flex.sourceforge.net/]] whitout using its specific features +* [[gcc (2.95)|http://www.gnu.org/software/gcc/]] ` ` The GNU C compiler +* [[gettext|http://www.gnu.org/software/gettext/]] ` ` GNU Internationalization utilities +* [[gperf (3.0.1)|http://www.gnu.org/software/gperf/]] ` ` Perfect hash function generator +* [[m4 (1.4)|http://www.gnu.org/software/m4/]] ` ` A macro processing language +* [[ncurses (5)|http://www.gnu.org/software/ncurses/]] ` ` Basic terminal type definitions + +### Development Tools/Libraries + +* [[perl (5)|http://www.perl.org/]] ` ` Larry Wall's Practical Extraction and Report Language +* [[intltool (0.30)|http://freedesktop.org/wiki/Software/intltool]] ` ` Utility scripts for internationalizing XML +* [[libpng (1.2.44)|http://www.libpng.org/pub/png/]] ` ` Reading and writing PNG (Portable Network Graphics) format files +* [[llvm|http://www.llvm.org/]] ` ` The Low-Level Virtual Machine (LLVM) +* [[libtalloc|http://talloc.samba.org/talloc/doc/html/index.html]] ` ` A hierarchical pool based memory allocator with destructors +* [[zlib (1.2.5)|http://zlib.net/]] ` ` Software library used for data compression + +### Cryptography + +The X server requires one of the following cryptographic libraries. + +* [[libgcrypt|http://directory.fsf.org/project/libgcrypt/]] ` ` General purpose cryptographic library +* [[libcrypto|http://www.openssl.org/docs/crypto/crypto.html]] ` ` OpenSSL cryptographic library +* [[libsha1|https://github.com/dottedmag/libsha1]] ` ` Tiny SHA1 implementation for embedded devices +* [[libmd|http://martin.hinner.info/libmd/]] ` ` Cryptographic message digest library +* [[CommonCrypto|http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man3/Common%20Crypto.3cc.html]] ` ` libSystem digest library on MAC OS X + +### Fonts + +* [[fontconfig (2.2.3)|http://www.freedesktop.org/wiki/Software/fontconfig]] ` ` A library for configuring and customizing font access +* [[freetype (2.2)|http://freetype.sourceforge.net/index2.html]] ` ` A Free, High-Quality, and Portable Font Engine + +### Documentation/XML Tools + +These tools are optionals. If they are missing, the documentation will not be generated. + +* [[Asciidoc|http://www.methods.co.nz/asciidoc/index.html]] ` ` Highly configurable text format for writing documentation +* [[Doxygen (1.6.1)|http://www.stack.nl/~dimitri/doxygen/]] ` ` Documentation system for C, C++, Java, Python and other languages +* [[Xmlto (0.0.22)|https://fedorahosted.org/xmlto/]] ` ` XML-to-any converter +* [[Xsltproc (1.1.26)|http://xmlsoft.org/XSLT/xsltproc2.html]] ` ` XSLT command line processor + +## Selecting a Build Process + +We are assuming you have installed the [[required tools|ModularDevelopersGuide]] but nothing else. There are two maintained build processes you can use. One is based on a simple Bourne script and one is a customization of the Gnome JHBuild process. + + +### Build Process Based on a Script + +This build process simply runs a `build.sh` script that downloads the source code from the git repositories and builds each package in dependency order. + +The _source tree_ is where the source code is extracted from git. It would typically be something like $HOME/src. The _installation tree_ is where the build generated objects (binaries, scripts, etc...) are created, typically $HOME/build. + +The script is itself part of a package which needs to be obtained from a git repository. The following command will extract the source code from git: +[[!format txt """ +cd $HOME/src +git clone git://anongit.freedesktop.org/git/xorg/util/modular util/modular +"""]] +You are now ready to launch a full build by invoking the build script. <a name="FullBuild"></a> +[[!format txt """ +mkdir $HOME/build +cd $HOME/src +./util/modular/build.sh --clone $HOME/build +"""]] +There are a good number of environment variables to be set and directories to be created. The script does a good job of setting default values. The `--help` option will list those variables and what they are used for. A common one is PREFIX which you may set to the installation directory. There is no variable for the source tree, you invoke commands from the top of the tree. + +Take a look at the features available in that script. You will certainly appreciate the `--autoresume` when the build stops on error. If you do not need to build all the packages, you can customize a list using the `-L` and use it with the `--modfile` options. + + +#### Building from Archive Files + +Alternatively, the script can build the source from archive files. X.Org regularly publishes versions of the source code in the form of [[tarballs|http://www.x.org/releases/X11R7.6/src/]]. The example shown involves tarballs from the X11R7.6 release. The script can also build a mixture of tarballs and source from git. + +You must first download the tarballs before running the build script. An input file containing URLs to read can be provided. You do not need to extract the tarballs. A sample command: +[[!format txt """ +wget http://www.x.org/releases/X11R7.6/src/util/util-macros-1.11.0.tar.gz +"""]] +You are now ready to launch a full build by invoking the build script. You can leave the `--clone` option in, any missing source will be obtained from git, at the current development level. +[[!format txt """ +mkdir $HOME/build +cd $HOME/src +./util/modular/build.sh $HOME/build +"""]] + +### Build Process Based on JHBuild + +The second build process uses [[jhbuild|http://www.freedesktop.org/wiki/Software/jhbuild]], a program written by James Henstridge that can be used to automatically download module components from Git and then build them in the correct dependency order. Refrer to the [[JhBuildInstructions|JhBuildInstructions]]. + + +## Features of the Build Script + +The `build script` first sets up environment variables and creates missing directories. It then cycles through a list of packages in dependency order to download them and run the Autotools from the [[GNU Build System|ModularDevelopersGuide]]. Some of the features require a conceptual understanding of Autoconf and Automake. Use the `--help` for a complete list of options. + + +### Environment Variables + +You normally do not need to have any environment variable set to run a full build. The script assigns reasonable defaults. The `--help` option will list those variables and what they are used for. + + +### Downloading and Updating Source Code + +As seen when launching a [[full build|ModularDevelopersGuide]], the `--clone` option will download the source code from git if it is missing on disk. The `-p` option will issue a `git -pull --rebase` to obtain the latest code currently in git. + + +### Stop/Continue/Resume On Error + +All builds eventually stop due to errors, sooner rather than later. The `-n` option allows the build script to continue the build with the next module. When the script terminates, it reports which ones failed. The `--autoresume` option writes a list of modules and can restart where it left off after you fixed the build error. + + +### Specifying Modules to Build + +The build script contains a full list of all X.Org modules and its dependent projects. That's a lot, over 200. You will most likely not need all of them. The `-L` will write this list to a file which you can edit and feed back to script using `--modfile` option. Make sure you understand the dependencies so as not to remove critical modules. + + +### Making Tarballs + +The X.Org modules are published as tarballs on the web. To create such tarballs, one can simply specify the `-D` option, but preferably `-d` as it performs a number of tests while creating the tarballs. + + +### Debug Mode + +The Automake default CFLAGS are -g and -O2. Using the -g option will add -g3 -O0 for additional debugging. + +The Automake silent rules are enabled by default at version 1.11 and higher. You may need additional context to debug the error. The `--retry-v1` will cause a rebuild of the module with the silent rules disabled. + + +### Advanced Commands and Configuration + +The build script provides additional flexibility in letting you specify arbitrary commands. You need more internal knowledge of the script and good experience with configuring and building modules. There is no checking to ensure that what you are trying to do _makes sense_. + +The `-a` option will skip the Autoconf configuration. This speeds up the build when you know that all modules have already been configured and do not need their source to be updated. You can rely, up to a point, on the make build rules to reconfigure the module if it is out of date. + +The `--cmd` option allows you to invoke a custom make or git command. You may want to run `git status` on all modules to ensure there are no local code changes for example. + +The `--confflags` option allows you to supply any Autoconf `configure` option. One example that comes to mind is `--disable-docs` which will suppress the building of user documention. These may conflict will default values assigned to environment variables set by the script. + + +### Building Individual Modules Yourself + +The build script does not mind if you cd to an individual module and build it yourself. It will have no adverse affect on the build when you resume the use of the script. You just need some basic understanding of the Autotools. Beware that the build script sets environment variables for you which are not available when you type the commands yourself in the terminal. + +Let's set those variables the way the script does it for you: + + +[[!format txt """ +export PREFIX=$HOME/build +export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PREFIX/share/pkgconfig +export ACLOCAL="aclocal -I $PREFIX/share/aclocal" +export LD_LIBRARY_PATH=$PREFIX/lib +export PATH=$PREFIX/bin:$PATH +"""]] +Now that have exported those variables, the build script will use them in lieu of its internal defaults. You can now switch back and forth between the build script and the terminal and keep the same environment. + +The script also creates directories for you: +[[!format txt """ +mkdir -p $PREFIX/share/aclocal +mkdir -p $PREFIX/var/log +"""]] +Download the font/util module and its dependency util/macros from git. +[[!format txt """ +cd $HOME/src +git clone git://anongit.freedesktop.org/git/xorg/util/macros util/macros +git clone git://anongit.freedesktop.org/git/xorg/font/util font/util +"""]] +Run the `autogen.sh` script, which will create and run the Autoconf configuration, and invoke the make command. +[[!format txt """ +cd $HOME/src/util/macros +./autogen.sh --prefix $PREFIX && make install +cd $HOME/src/font/util +./autogen.sh --prefix $PREFIX && make install +"""]] +This is exactly what the script does for you, note the order and the importance of running the _install_ target. Without it, the font util module would not be able to use xorg-macros.m4 in $PREFIX/share/aclocal. For complete details on the packaging structure of a module read the INSTALL file in the root directory of the module. + +When building from tarballs, the configuration has already been created and only needs to be run. The commands would be: +[[!format txt """ +cd $HOME/src/util/macros +./configure --prefix $PREFIX && make install +cd $HOME/src/font/util +./configure --prefix $PREFIX && make install +"""]] +The autogen.sh script is not part of the GNU Build System architecture and is kept for historical reasons. Other projects have different name and content for it. It should not be included in the tarball. If you need to recreate the configuration, `autoreconf -vfi` will do and is only what autogen.sh calls. + + +## Using the modular tree + +This section describes how to use the newly compiled X libraries, applications and X server. + + +### X libraries + +The X libraries which are built will typically be in $PREFIX/lib. + +To use them you have to configure the linker to find them. On GNU/Linux systems you do: + + +[[!format txt """ +export LD_LIBRARY_PATH=$PREFIX/lib +"""]] +Alternately, you might edit the `/etc/ld.so.conf` file and run `ldconfig`. There may be other ways to configure the linker on other systems. + +Once this is done X applications should use the newly compiled libraries. + + +### X applications + +The X client programs which are built will be found in $PREFIX/bin. Generally, these programs can be run with the default user permissions. + + +### Running the X server + +Verify that the Xorg binary that will get executed is really the one you just build. If not, adjust $PATH. +[[!format txt """ +ls -l `which Xorg` +"""]] +The Xorg binary needs to be _suid root_ which requires root privilege. +[[!format txt """ +chown root Xorg +chmod 4711 Xorg +"""]] +Run the new X server using the most basic command. Your computer screen will blank out and your desktop will be replaced with a small X terminal window with no borders. To return to your desktop, you can type `exit` or you can press `Ctrl Alt F7` (on most platforms). + +**Please read the above paragraph carefully before issuing the following command.** +[[!format txt """ +Xorg :1 -terminate & sleep 2 ; DISPLAY=:1 xterm +"""]] + +## Working with git submodules + +Submodules allow foreign repositories to be embedded within a dedicated subdirectory of the source tree, always pointed at a particular commit. This section assumes you are comfortable with the similar tasks when performed without git submodules. You might be interested in the [[Kernel Git Submodule Tutorial|https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial]]. + + +### Cloning a module with submodules + +After cloning the module, the git submodule command will clone and initialize the submodules specified in the .gitmodules file. In this example, the submodule path is _m4_. Git keeps track of which submodule commit to checkout. Later versions of the _git clone_ command have a _--recursive_ option. +[[!format txt """ +git clone git://anongit.freedesktop.org/xcb/util +git submodule update --init +"""]] + +### Updating a module + +It may be that only the module has changed since the last update, or that both the module and the submodule have changed. +[[!format txt """ +git pull --rebase +git submodule update +"""]] + +### Rolling back a module + +It may happen you need to revert the state of a module and a submodule to a previous point in time. The module should then point to the matching commit of the submodule. The commit numbers are valid, you can run the commands. +[[!format txt """ +git reset --hard 02289ca +git submodule update +"""]] +You should see this output: +[[!format txt """ +HEAD is now at 02289ca Bump version to 0.3.8 +Submodule path 'm4': checked out '55e8069773efd794a91d5fb37bfceeebae2e378a' +"""]] +The log [[http://cgit.freedesktop.org/xcb/util/log/m4|http://cgit.freedesktop.org/xcb/util/log/m4]] will show the commit history for the submodule. + + +### Hooking up a submodule to a module + +A submodule has a git repository like any other module. It is only different in the way it gets used. Several modules can _include_ the submodule containing reusable code. +[[!format txt """ +git submodule add git://anongit.freedesktop.org/xcb/util-common-m4 m4 +git submodule update --init +"""]] +You should see this output from _git status_: +[[!format txt """ +# On branch master +# Changes to be committed: +# (use "git reset HEAD <file>..." to unstage) +# +# new file: .gitmodules +# new file: m4 +# +"""]] + +### Detaching a submodule from a module + +There is no git submodule remove command. Given our example where the submodule path is _m4_, +[[!format txt """ +git config --remove-section submodule.m4 +git config --file .gitmodules --remove-section submodule.m4 +git rm --cached m4 +rm -fr m4 +"""]] +Create a commit for the changes incurred by the module and you are done. Note that the submodule still exists at fdo.org, you have only detached and deleted your module copy. + + +### Applying changes to a submodule + + +#### Working from within a submodule + +To directly modify sources referenced by a submodule, just change to the directory of the submodule and work with it like with a normal repository. Note however, that the state of a submodule is controlled by the supermodule and that under certain conditions it might even be possible to loose unpublished work. For more, see the Gotchas section of the [[Kernel Git Submodule Tutorial|https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial#Gotchas]]. + + +#### Using a local clone of a submodule + +It is also possible to separately clone the repository and redirect the upstream URL of the submodule to the local version. For example, the configuration of a submodule m4 in ` m4/.git/config ` could look like: + + +[[!format txt """ +[remote "origin"] + fetch = +refs/heads/*:refs/remotes/origin/* + url = git://anongit.freedesktop.org/xcb/util-common-m4.git +"""]] +Simply set the value of `url` to the path of the local repository. + + +[[!format txt """ +[remote "origin"] + fetch = +refs/heads/*:refs/remotes/origin/* + url = /path/to/util-common-m4.git +"""]] +Note, that we are changing the configuration of the submodule at ` m4/.git/config ` and not the configuration of the supermodule at `.git/config`. + + To use a different location from the start, it is also possible to change the submodule configuration in the supermodule before updating the submodule for the first time. The file `.gitmodules` specifies the official location of the submodule and changes to it are being tracked. But that file does not need to be changed for our purpose. The following command copies the contents of `.gitmodules` to the configuration of the supermodule at `.git/config`: + + +[[!format txt """ +git submodule init +"""]] +The submodule has not been checked out yet, and so it is possible to select a different location. For example, the configuration in `.git/config` could look like: + + +[[!format txt """ +[submodule "m4"] + url = git://anongit.freedesktop.org/xcb/util-common-m4.git +"""]] +Insert the preferred location like above and then update the submodule with: + + +[[!format txt """ +git submodule update +"""]] + +### Creating a submodule + +A git submodule is created just like any other git module. The reasons for using a module as a submodule is beyond the scope of this section. In the XCB example, the goal was code reuse. + + +## Crosscompiling + +There is a separate page dedicated to issues around [[CrossCompilingXorg|CrossCompilingXorg]]. + + +## New Modules + +When adding modules to the tree, you may want to read the [[NewModuleGuidelines|NewModuleGuidelines]]. diff --git a/ModularDevelopersGuide/git_xorg b/ModularDevelopersGuide/git_xorg new file mode 100644 index 00000000..6153a5c1 --- /dev/null +++ b/ModularDevelopersGuide/git_xorg @@ -0,0 +1,136 @@ +#! /bin/sh +# +# Copyright (c) 2006 Matthieu Herrb +# +# Permission to use, copy, modify, and distribute this software for any +# purpose with or without fee is hereby granted, provided that the above +# copyright notice and this permission notice appear in all copies. +# +# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +# +# Some updates by Brian Paul + + +gitbase="git://anongit.freedesktop.org/git/xorg" + +app="appres bdftopcf beforelight bitmap compiz constype editres fonttosfnt\ + fslsfonts fstobdf glxcompmgr iceauth ico lbxproxy listres luit\ + makepsres mkcfm mkfontdir mkfontscale oclock pclcomp proxymngr\ + rendercheck rgb rstart scripts sessreg setxkbmap showfont smproxy\ + twm viewres x11perf xauth xbiff xcalc xclipboard xclock xcmsdb\ + xcompmgr xconsole xcursorgen xdbedizzy xditview xdm xdpyinfo\ + xdriinfo xedit xev xeyes xf86dga xfd xfindproxy xfontsel xfs\ + xfsinfo xfwp xgamma xgc xhost xinit xkbcomp xkbevd xkbprint\ + xkbutils xkill xload xlogo xlsatoms xlsclients xlsfonts xmag\ + xman xmessage xmh xmodmap xmore xphelloworld xplsprinters xpr\ + xprehashprinterlist xprop xrandr xrdb xrefresh xrestop xrx xset\ + xsetmode xsetpointer xsetroot xshowdamage xsm xstdcmap xtrap \ + xvidtune xvinfo xwd xwininfo xwud" + +data="bitmaps cursors" + +doc="xorg-docs xorg-sgml-doctools" + +driver="xf86-input-acecad xf86-input-aiptek xf86-input-calcomp\ + xf86-input-citron xf86-input-digitaledge xf86-input-dmc\ + xf86-input-dynapro xf86-input-elo2300 xf86-input-elographics\ + xf86-input-evdev xf86-input-fpit xf86-input-hyperpen\ + xf86-input-jamstudio xf86-input-joystick xf86-input-keyboard\ + xf86-input-magellan xf86-input-magictouch xf86-input-microtouch\ + xf86-input-mouse xf86-input-mutouch xf86-input-palmax\ + xf86-input-penmount xf86-input-sample xf86-input-spaceorb\ + xf86-input-summa xf86-input-tek4957 xf86-input-ur98\ + xf86-input-vmmouse xf86-input-void xf86-video-apm\ + xf86-video-ark xf86-video-ast xf86-video-ati\ + xf86-video-chips xf86-video-cirrus xf86-video-cyrix\ + xf86-video-dummy xf86-video-fbdev xf86-video-glide\ + xf86-video-glint xf86-video-i128 xf86-video-i740\ + xf86-video-impact xf86-video-imstt xf86-video-intel\ + xf86-video-mga xf86-video-neomagic xf86-video-newport\ + xf86-video-nsc xf86-video-nv xf86-video-rendition\ + xf86-video-s3 xf86-video-s3virge xf86-video-savage\ + xf86-video-siliconmotion xf86-video-sis xf86-video-sisusb\ + xf86-video-sunbw2 xf86-video-suncg14 xf86-video-suncg3\ + xf86-video-suncg6 xf86-video-sunffb xf86-video-sunleo\ + xf86-video-suntcx xf86-video-tdfx xf86-video-tga\ + xf86-video-trident xf86-video-tseng xf86-video-v4l\ + xf86-video-vesa xf86-video-vga xf86-video-via\ + xf86-video-vmware xf86-video-voodoo xf86-video-wsfb" + +font="adobe-100dpi adobe-75dpi adobe-utopia-100dpi adobe-utopia-75dpi\ + adobe-utopia-type1 alias arabic-misc bh-100dpi bh-75dpi\ + bh-lucidatypewriter-100dpi bh-lucidatypewriter-75dpi\ + bh-ttf bh-type1 bitstream-100dpi bitstream-75dpi\ + bitstream-speedo bitstream-type1 cronyx-cyrillic\ + cursor-misc daewoo-misc dec-misc encodings ibm-type1\ + isas-misc jis-misc micro-misc misc-cyrillic misc-ethiopic\ + misc-meltho misc-misc mutt-misc schumacher-misc \ + screen-cyrillic sony-misc sun-misc util winitzki-cyrillic\ + xfree86-type1" + +lib="libAppleWM libFS libICE libSM libWindowsWM libX11 libXRes\ + libXScrnSaver libXTrap libXau libXaw libXcomposite libXcursor\ + libXdamage libXdmcp libXevie libXext libXfixes libXfont\ + libXfontcache libXft libXi libXinerama libXmu libXp\ + libXpm libXprintAppUtil libXprintUtil libXrandr libXrender\ + libXt libXtst libXv libXvMC libXxf86dga libXxf86misc\ + libXxf86rush libXxf86vm libdmx libfontenc liblbxutil\ + liboldX libpciaccess libxkbfile libxkbui libxtrans" + +proto="applewmproto bigreqsproto compositeproto damageproto\ + dmxproto evieproto fixesproto fontcacheproto\ + fontsproto glproto inputproto kbproto panoramixproto\ + pmproto printproto randrproto recordproto renderproto\ + resourceproto scrnsaverproto trapproto videoproto \ + windowswmproto x11proto xcmiscproto xextproto\ + xf86bigfontproto xf86dgaproto xf86driproto xf86miscproto\ + xf86rushproto xf86vidmodeproto xineramaproto" + +util="cf gccmakedep imake install-check lndir macros makedepend\ + modular xmkmf" + + +do_dir () { + dir=$1 + if [ ! -d ${dir} ]; then + echo "creating ${dir}" + mkdir ${dir} + fi + for d in $2; do + if [ -d "${dir}/$d" ]; then + echo "${dir}/$d exists, pulling" + (cd "${dir}/$d" ; git pull) + else + echo "cloning ${dir}/${d}" + if [ ${dir} == '.' ] ; then + src="${gitbase}/$d" + else + src="${gitbase}/${dir}/$d" + fi + (cd "${dir}" ; git clone ${src}) + fi + done +} + +do_dir app "${app}" +do_dir data "${data}" +do_dir doc "${doc}" +do_dir driver "${driver}" +do_dir lib "${lib}" +do_dir proto "${proto}" +do_dir util "${util}" +do_dir . xserver + +# DRM doesn't fit into above +if [ -d drm ] ; then + (cd drm ; git pull ) +else + git clone git://anongit.freedesktop.org/git/mesa/drm +fi + diff --git a/ModularDevelopersGuide/git_xorg.sh b/ModularDevelopersGuide/git_xorg.sh new file mode 100644 index 00000000..28413c51 --- /dev/null +++ b/ModularDevelopersGuide/git_xorg.sh @@ -0,0 +1,144 @@ +#! /bin/sh +# +# Copyright (c) 2006 Matthieu Herrb +# +# Permission to use, copy, modify, and distribute this software for any +# purpose with or without fee is hereby granted, provided that the above +# copyright notice and this permission notice appear in all copies. +# +# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +# +# Some updates by Brian Paul +# XCB update and some cleanup by Peter Hutterer + + +gitbase="git://anongit.freedesktop.org/git" + +app="appres bdftopcf beforelight bitmap compiz constype editres fonttosfnt\ + fslsfonts fstobdf glxcompmgr iceauth ico lbxproxy listres luit\ + makepsres mkcfm mkfontdir mkfontscale oclock pclcomp proxymngr\ + rendercheck rgb rstart scripts sessreg setxkbmap showfont smproxy\ + twm viewres x11perf xauth xbiff xcalc xclipboard xclock xcmsdb\ + xcompmgr xconsole xcursorgen xdbedizzy xditview xdm xdpyinfo\ + xdriinfo xedit xev xeyes xf86dga xfd xfindproxy xfontsel xfs\ + xfsinfo xfwp xgamma xgc xhost xinit xinput xkbcomp xkbevd xkbprint\ + xkbutils xkill xload xlogo xlsatoms xlsclients xlsfonts xmag\ + xman xmessage xmh xmodmap xmore xphelloworld xplsprinters xpr\ + xprehashprinterlist xprop xrandr xrdb xrefresh xrestop xrx xset\ + xsetmode xsetpointer xsetroot xshowdamage xsm xstdcmap xtrap \ + xvidtune xvinfo xwd xwininfo xwud" + +data="bitmaps cursors" + +doc="xorg-docs xorg-sgml-doctools" + +driver="xf86-input-acecad xf86-input-aiptek xf86-input-calcomp\ + xf86-input-citron xf86-input-digitaledge xf86-input-dmc\ + xf86-input-dynapro xf86-input-elo2300 xf86-input-elographics\ + xf86-input-evdev xf86-input-fpit xf86-input-hyperpen\ + xf86-input-jamstudio xf86-input-joystick xf86-input-keyboard\ + xf86-input-magellan xf86-input-magictouch xf86-input-microtouch\ + xf86-input-mouse xf86-input-mutouch xf86-input-palmax\ + xf86-input-penmount xf86-input-sample xf86-input-spaceorb\ + xf86-input-summa xf86-input-tek4957 xf86-input-ur98\ + xf86-input-vmmouse xf86-input-void xf86-video-apm\ + xf86-video-ark xf86-video-ast xf86-video-ati\ + xf86-video-chips xf86-video-cirrus xf86-video-cyrix\ + xf86-video-dummy xf86-video-fbdev xf86-video-glide\ + xf86-video-glint xf86-video-i128 xf86-video-i740\ + xf86-video-impact xf86-video-imstt xf86-video-intel\ + xf86-video-mga xf86-video-neomagic xf86-video-newport\ + xf86-video-nsc xf86-video-nv xf86-video-rendition\ + xf86-video-s3 xf86-video-s3virge xf86-video-savage\ + xf86-video-siliconmotion xf86-video-sis xf86-video-sisusb\ + xf86-video-sunbw2 xf86-video-suncg14 xf86-video-suncg3\ + xf86-video-suncg6 xf86-video-sunffb xf86-video-sunleo\ + xf86-video-suntcx xf86-video-tdfx xf86-video-tga\ + xf86-video-trident xf86-video-tseng xf86-video-v4l\ + xf86-video-vesa xf86-video-vga xf86-video-via\ + xf86-video-vmware xf86-video-voodoo xf86-video-wsfb" + +font="adobe-100dpi adobe-75dpi adobe-utopia-100dpi adobe-utopia-75dpi\ + adobe-utopia-type1 alias arabic-misc bh-100dpi bh-75dpi\ + bh-lucidatypewriter-100dpi bh-lucidatypewriter-75dpi\ + bh-ttf bh-type1 bitstream-100dpi bitstream-75dpi\ + bitstream-speedo bitstream-type1 cronyx-cyrillic\ + cursor-misc daewoo-misc dec-misc encodings ibm-type1\ + isas-misc jis-misc micro-misc misc-cyrillic misc-ethiopic\ + misc-meltho misc-misc mutt-misc schumacher-misc \ + screen-cyrillic sony-misc sun-misc util winitzki-cyrillic\ + xfree86-type1" + +lib="libAppleWM libFS libICE libSM libWindowsWM libX11 libXRes\ + libXScrnSaver libXTrap libXau libXaw libXcomposite libXcursor\ + libXdamage libXdmcp libXevie libXext libXfixes libXfont\ + libXfontcache libXft libXi libXinerama libXmu libXp\ + libXpm libXprintAppUtil libXprintUtil libXrandr libXrender\ + libXt libXtst libXv libXvMC libXxf86dga libXxf86misc\ + libXxf86rush libXxf86vm libdmx libfontenc liblbxutil\ + liboldX libpciaccess libxkbfile libxkbui libxtrans" + +proto="applewmproto bigreqsproto compositeproto damageproto\ + dmxproto evieproto fixesproto fontcacheproto\ + fontsproto glproto inputproto kbproto panoramixproto\ + pmproto printproto randrproto recordproto renderproto\ + resourceproto scrnsaverproto trapproto videoproto \ + windowswmproto x11proto xcmiscproto xextproto\ + xf86bigfontproto xf86dgaproto xf86driproto xf86miscproto\ + xf86rushproto xf86vidmodeproto xineramaproto" + +util="cf gccmakedep imake install-check lndir macros makedepend\ + modular xmkmf" + +xcb="proto libxcb pthread-stubs" + +# $1 is the main project path in the git repository (e.g. xorg). +# $2 is the module's directory (e.g. lib) +# $3 is the module name (e.g. libXi) +# $1 and $2 can be '.', in which case they are ignored. +# The path for git clone will be $gitbase/$1/$2/$3 +do_dir () { + dir=$2 + if [ ! -d ${dir} ]; then + echo "creating ${dir}" + mkdir -p ${dir} + fi + for d in $3; do + if [ -d "${dir}/$d" ]; then + echo "${dir}/$d exists, pulling" + (cd "${dir}/$d" ; git pull) + else + echo "cloning ${dir}/${d}" + if [ $1 = '.' ] ; then + src="${gitbase}" + else + src="${gitbase}/$1" + fi + + if [ ${dir} = '.' ] ; then + src="${src}/$d" + else + src="${src}/${dir}/$d" + fi + (cd "${dir}" ; git clone ${src}) + fi + done +} + +do_dir xorg app "${app}" +do_dir xorg data "${data}" +do_dir xorg doc "${doc}" +do_dir xorg driver "${driver}" +do_dir xorg lib "${lib}" +do_dir xorg proto "${proto}" +do_dir xorg util "${util}" +do_dir . . pixman +do_dir xorg . xserver +do_dir mesa . drm +do_dir . xcb "${xcb}" diff --git a/ModularizationDevelPlan.mdwn b/ModularizationDevelPlan.mdwn new file mode 100644 index 00000000..a36c53da --- /dev/null +++ b/ModularizationDevelPlan.mdwn @@ -0,0 +1,112 @@ + + +# Modularization Development Plan + +Kevin E. Martin + +[[!toc ]] + + +## Platform support + +We need to find out who will be working on modularization so that we can get an idea of the platform coverage. For the 6.8 release, I created a wiki page for the platforms that we wanted to test, and I would like to do the same for modularization. Below is the list of those platforms that people signed up to test from the previous release and the current one: + + * AIX (no arch listed) + * Cygwin (IA-32) + * Dragon``Fly/BSD + * FreeBSD (Alpha, AMD64, IA-32, IA-64) + * HP-UX (PA-RISC) + * IRIX (MIPS) + * Linux (Alpha, AMD64, ARM, IA-32, IA-64, M68k, MIPS, PPC, PPC64, PA-RISC, S/390, Sparc) + * MacOS (PPC) + * MacOS/Darwin (IA-32, PPC) + * NetBSD (IA-32) + * OpenBSD (AMD64, IA-32) + * SCO (no arch listed) + * Solaris (AMD64, IA-32, Sparc) + * Unix``Ware (no arch listed) +Other platforms that were listed, but didn't have anyone signed up to test were: + + * LynxOS + * OS/2 +Ideally, we would like to see at least one person and preferably more signed up to work on each of these platforms; however, it is more likely that we will get fairly good coverage on a subset of them. I expect good coverage on Linux, but we need much more than that. So, if you are interested in working on a platform and have the hardware available, please speak up now so that we can get an idea of where we stand. + + +## Development steps + +The Architecture Working group has given their approval, and we are now in the process of working out the development plan described here. Once we answer the remaining questions (see below) and agree to the plan outlined here, we can begin work. + +There are two parts to this project: dividing the tree into separate modules, and then autotooling those modules. These are described in the next two sections below. + + +### Module creation + +Here are the steps that for creating the modules: + + 1. Determine where each piece of code from the monolithic tree will go in the modular tree. + * See [[ModuleComponentList|ModuleComponentList]] for the current list. + * Nearly complete + 1. Create the top level modules (i.e., app, lib, proto, xserver, driver, font, doc and util) as peers to xc. + 1. Create the directory hierarchy for the modularization within each module based on the breakdown determined in step #1. + 1. Write a script that creates a symlink tree on the developer's local system from a checked out monolithic CVS tree. +Steps #2 and #3 should fall directly out of #1. The directory hierarchy can be filled in as modules are created in the dependency order (see below). Another developer has already started working on #4. + + +### Autotooling the modules + +We have a few people that have worked on previous autotooling efforts and many more that have not. Based on feedback from those previous efforts, much of the work will become routine once everyone understands exactly what needs to be done and how to do it. The question is how to fill this knowledge gap so that everyone can be productive initially (i.e., how do we bootstrap ourselves). + +My initial thought is that we should learn from the past efforts by having those involved explain the autotooling process that they used. We can then discuss it here on the list, make suggestions and come to consensus on how we want to proceed for our project. By discussing it openly, I think that many more developers will be able to become involved at an earlier stage since they will understand what is involved and how to make it happen. Also, this discussion will form the basis for part of the guide described in the proposal (see documents section below for more info). + +What I have in mind here is a simple brain dump of the process used to autotool in the xapps, xlibs, xserver and Debrix projects. I'd also like to see us discuss any common conventions that everyone should follow so that we have a consistent build system and config options name space. + +I expect as more people become involved in the modularization effort, the information here will be written and included in the developer's guide. + + +## Dependencies + +Note that while there are some dependencies that we need to follow for certain modules to work (lib, xserver, driver), others can be developed independently by using the monolithic tree for bootstrapping (app, font, doc, util). Here's the dependencies: + + * proto: no dependencies + * lib: depends on proto + * xserver: depends on proto and lib, but the lib dependency can be bootstrapped from the monolithic tree + * driver: depends on the xserver module headers + * app: depends on lib, but can be bootstrapped + * font: depends on app, which will contain the tools that build fonts, but can be bootstrapped + * doc: depends on (external?) tools to build docs + * util: no dependencies? +In order for bootstrapping to work, we need to have the capability to install and use missing pieces from a monolithic build. However, many libraries in the monolithic tree do not have pkg-config metadata files, which will make this difficult. Therefore, we recommend creating the modules in the dependency order listed above. + + +## Documents + +In the Modularization Proposal, we committed to create the following documents: + + * [[X.Org Modular Tree Developer's Guide|ModularDevelopersGuide]]: + * Required tools (Partially complete) + * Building and using the new modular tree (TBD) + * Standardized configuration options (TBD) + * Guidelines for module components (mostly complete) + * Converting code from Imake to Autotools (TBD) + * Component dependencies (included within component -- see developer's guide) + * Licenses (documented within component in COPYING -- see developer's guide) +Note that in the proposal, this guide was called the "Transition Guide", but it should have been called the a "Developer's Guide" instead since that is a better description of the doc. Using "transition" implies that the guide is only useful during the transition period, which does not reflect the life of this document. This doc is the place where new developers go to find out how to use and develop within the modular tree and will be kept up to date with the latest information. + +The initial outline for the developer's guide has been written. During development, we can fill in any new or missing information. To enable it to be easily updated, the developer's guide was placed in the wiki (see link above). + + +## Success Criteria + +Ideally, we should be able to build the exact same binaries and install them in the exact same place from either the monolithic and modular trees on the same system, but in reality the compiler options will probably differ and produce slightly different code. + +The next best solution would be to run through the same set of tests on both installed trees. The testing procedure used in for the 6.8 release is a good starting point for the set of tests used for the combined 6.9/7.0 release. These test should be updated to use the latest X Test Suite available (see the [[Test Working Group's wiki page|TestGroup]] for more info). Here's a link describing the procedure: + + * [[http://wiki.x.org/wiki/XorgTesting|http://wiki.x.org/wiki/XorgTesting]] +In addition, we should make sure that the installed trees look very similar and provide reasons for any discrepancies. + +Other success criteria would be the coverage we get on the platforms we support in the initial release. As noted above, Linux will most likely be the best supported, but we need others to make this a successful project. I agree with ajax that we should support at least Linux, Solaris, one of the BSDs, Darwin and Cygwin initially since we have active participation by people working on these platforms. However, my hope is that we will have several others supported as well. + + +## Open Questions + +None at this time. diff --git a/ModularizationProposal.mdwn b/ModularizationProposal.mdwn new file mode 100644 index 00000000..bfe84b33 --- /dev/null +++ b/ModularizationProposal.mdwn @@ -0,0 +1,217 @@ + + +# Modularization Proposal + +Paul Anderson, Alan Coopersmith, Egbert Eich, Adam Jackson, Kevin E. Martin and Keith Packard + +[[!toc ]] + + +<a name="intro"></a> +## Introduction + +Traditionally, the X Window System source code has been comprised of many different components that are brought together into a single monolithic source tree. We propose to split the tree into logical modules that can be developed, built and maintained separately, but still fit together coherently into the larger source code base as they have in the monolithic tree. + +This proposal provides rationale for modularization, attempts to address the known concerns people have raised, provides background on other modularization efforts, explains what the modularized source tree would look like, outlines the steps required to take this idea from concept to release, and suggests how future modular releases can be handled. + + +<a name="proscons"></a> +## The pros and cons of modularization + + +### The pros + + * There are many open source developers that are intimidated by the large X code base. Working on smaller self-contained modules with well defined ABIs, is much less intimidating. + * Most other open source projects use autotools, so it's something that many people know. Imake is known in our community but it's a barrier to entry for most others. + * Lowering the barriers to entry will both attract new developers and help them to become productive members of the community more quickly. More developers means progress speeds up, and bugs are found and fixed quicker. + * You no longer have to build and install the entire tree just to work on one small part of it. + * Creating releases from modules is automated with the autotools, along with the ability to automatically verify that the release is correct. + * Bug fixes in one part of the tree can be made available to vendors in a more timely fashion. For example, a bug fix in the Radeon driver module could be checked in on a stable development branch and released as an update for vendors. + * Finer grained access control to the source code; each module should have its own maintainer and access controls. Global developers will still have universal access. + * It should be easier to use technology that's not under the X license. Right now, we have the `xc/extras` directory, because the code there is either not under the X license or maintained externally. These _extras_ are often out of date and conflict with the installed versions on vendors' installations. + +### The cons + + * The autotools are a new build technology, which throws away existing knowledge of the current imake build system. People that are not already familiar with the autotools will need to learn a new build system. That could slow some developers down for a while. + * To address this issue, we need people who understand both imake and autotools well to write a transition guide for the benefit of all. + * Some platforms may not "come along" if there are no maintainers. + * This should be treated as an opportunity for us to contact the old maintainers and see if they are interested joining the community, or for us to encourage to new maintainers to step forward to support platforms if the old maintainer is no longer interested or available. + * Some platforms may not "come along" if the current build maintainers don't have time to learn the new build system during the initial release. + * The X.Org Foundation has been very good about having regular releases of our software and we are aggressively working to ensure that this continues. This regular release policy gives maintainers that don't have the time at present to complete the transition confidence that they will have opportunities in the near future to add their platforms to the new modular tree. + * Autodetection can add dependencies that you didn't intend. For example, a developer may have a library on their build system that isn't available on the target system. + * Dependencies will be explicitly listed and documented. Configure options will be used to control which dependencies are enabled or disabled. These configure options will be standardized and documented in the transition guide. + * Autotools are very version-dependent, and some OSes might not have the most up-to-date versions available. For example, some OSes might use an OS-specific libtool, which might need to be updated to includes the latest patches to properly handle "so" versions (see below). + * For developers who do not have the required autotools versions installed and don't want to overwrite their vendor-supported versions, it is possible to install them in out-of-the-way locations (e.g., not in $PATH) and still easily script the build process. + * Autotools are not very easy to understand (e.g., libtool). + * Imake is also not very easy to understand for new developers. The autotools have the advantage that there are many sources for good information. The transition guide will also help. Many of the more complex tools (e.g., libtool) can be ignored almost all of the time as other tools (e.g., automake, in the case of libtool) manage the whole interaction. + * The various servers have different (and possibly incompatible) build options, which means that they may not be able to share the same build of the code. For example, one server might build DIX with XINPUT support, while another one might require that XINPUT be disabled. + * This problem also affects the monolithic tree, and it is not easily solvable in either case without rebuilding the affected parts. This rebuilding task is simple with autotools. + * The configure scripts take a long time to complete; you have to run multiple "configures" from scratch, and it will take a while. + * Configure caches can be used to speed up multiple configure runs, and jhbuild or scripts can be used to automate them. + * With the imake build system, you can build and test in place with the link directory inside the tree. Building self-contained user environments are more difficult with autotools. + * jhbuild solves this since it runs a self-contained environment. Other solutions using chroot, LD_LIBRARY_PATH, etc. are also in use today with autotools. + * Legacy imake-only applications will need to be converted. + * Imake is not going away and will still be needed for legacy applications maintained outside of our source tree. The transition guide that we use internally will be made available externally to help others become familiar with how the new autotool build system works so that they can convert their applications as time permits. + +<a name="background"></a> +## Background + +During the past two years, several research projects have explored how to modularized and autotool the source tree. We can learn a great deal from these projects. Below is a description of the projects from two of those directly involved. + + +### Keith Packard's experiences + +The modularization work that Keith did was to split the sources up so that no distribution would have to break one of his packages apart in order to build their distribution -- i.e., no modules would need to be split across package boundaries. Distributing the software is then a matter collecting the pieces, rather than cutting things apart. To do that, he cut it pretty finely. He split it into three main chunks: xapps, xlibs, xserver. They are logically separate from a functionality standpoint. Also, he could control access to these separately. + +In doing this, Keith found that the header files were done incorrectly for many extensions. He now has many small packages that only have the specification and the header for the extension. We can learn from the experience that Keith has had in this area for the libraries. The protocol headers are the foundation of the system. We have to get those working/structured properly for the rest to work. + +Keith had to get a change made to 'libtool' (v1.5) so that the correct "so" versions could be specified. This is an absolute requirement for our product, but the change was made long enough ago that most people have it. There is an issue where certain OSes use a different libtool that may not have this change. + +Keith did less work with the xapps, since he doesn't use many of them. Plus, autotooling an X application is simple; autotooling the libraries was a longer process. + +Keith hasn't split the Xserver into pieces, since he treated it as just an application. However, for our modularization project, he pointed out that shipping individual drivers as separate modules is a fundamental goal, so we will need to do additional work along the lines of what was done with Debrix. + + +### Adam Jackson's experiences with Debrix + +Debrix was started by Daniel Stone as a second attempt at autotooling the Xorg server. The previous attempt was named "Xizzle" and floundered due to the DDX build-time dependence on various DIX config options discussed elsewhere. Daniel did most of the initial bootstrapping design, I imported most of the driver and input modules, and Jakub Stachowski contributed several autotooled extension modules. + +The Debrix model split the server into four basic components: + + * server core (cvs module name 'debrix') + * video drivers ('debrix-driver-ati' etc.) + * input drivers ('debrix-input-mouse' etc.) + * dynamically loadable extensions ('debrix-extension-dbe' etc.) +Some of the design decisions made in Debrix: + + * The server component consisted of the xfree86 DDX, including the core dynamic modules like int10 and ddc. + * The video/input/extension modules were split off on the assumption that those would be the pieces users would be most likely to want to replace piecewise. + * To enable the non-server modules to build, the server component installed server API headers to $(PREFIX)/include/xorg. The "config.h" generated during the server build was installed as "debrix.h", so drivers could see the options used to build the server. +Some of the issues we encountered: + + * Debrix was used as a staging area for the dlloader work that eventually landed in Xorg. We considered using libtool's 'ltdl' library instead, since some platforms don't have libdl but have their own APIs for dynamically loading modules, but this was quickly rejected. ltdl places some strange constraints on module usage and would require major ABI changes in basically every driver to accommodate ltdl's rather absurd symbol naming requirements. The executive decision was that platforms that didn't have libdl could implement it in 50 lines of API wrappers for much less pain. + * GLX support was hard to factor out. The server's GLcore software rasterizer requires a copy of the Mesa source to build, as well as some server-specific code. Jakub did have this working but it required telling the build process where to find a Mesa source tree via a configure option. This is unwieldy and will need to be addressed for 7.0. + * int10 support was initially through vm86 only. The x86emu version was added later, but x86emu lives under extras and thus might present a special case for the modular tree structure. Debrix simply imported it whole, but this is clearly wrong. + * No other DDXes besides the xfree86 DDX were attempted. The xnest, xwin, and xgl DDXes have been autotooled in Keith's xserver project. The darwin, dmx, sun, sunlynx, vfb, and xprint DDXes have not (to my knowledge) ever been autotooled. sun and sunlynx can probably be dropped at this point, but any lurking issues in the remaining imake-only DDXes are therefore still lurking. + * Docs and fonts are also logically separate, and were not attempted in Debrix. + +<a name="modulartree"></a> +## The monolithic and modular source trees + +This section outlines a proposal for what the modular source tree could look like. It provides details on each module's contents, the public interfaces, the dependencies between modules, and rationale. This and the next two sections are the heart of this proposal, and the parts that need to be accepted by the community before begin the modularization work. + +It is important to note that the modular source tree is expected to contain the same code as the monolithic tree, but will be organized and built in a different way. For example, the code will be organized into logical modules. Autotools ([[http://sources.redhat.com/autobook/|http://sources.redhat.com/autobook/]]) will be used to build the modular sources individually, and with the help of jhbuild and other support tools, we will continue to be able to create completely self-contained builds. + +The monolithic source tree will continue to exist as a self-contained source tree that can be built with imake, but it is expected that people will transition to the modular tree for future development (see the next section). We propose that both trees should co-exist side-by-side in the xorg CVS project hosted on freedesktop.org (see Figure 1 below). + +[[!img http://www.freedesktop.org/~kem/modular/figure1.gif] + +From the Figure above, the monolithic source tree will continue in the `xc` hierarchy within the xorg project. Along side of it will be several separate modules: **app**, **lib**, **proto**, **xserver**, **driver**, **font**, **doc**, and **util**. Each of these modules will be detailed below. Not shown in Figure 1 are the _extras_, which will exist outside of the source tree and contain only those source tarballs required to build the tree, but for which xorg is not the canonical source repository. + +The applications module: **app** + + * Applications are relatively straight forward to autotool. + * Each app will be placed into a subdirectory of its own within the **app** module, and will not depend on any other apps being present within the checked-out module. + * Each app will have its own dependencies on specific libraries from the **lib** module being installed. +The libraries module: **lib** + + * The libraries are one of the more difficult parts of the tree to modularize since they depend on both the API headers as well as the protocol headers, and other modules require them to be built and installed. + * The API headers and protocol are the public interface to our system. + * The API headers will be included with their respective libraries in this module. + * The protocol headers are required by both the **lib** and **xserver** modules and will be split into a **proto** module (see below). + * After these dependencies were worked out, the libraries become relatively straightforward to autotool. + * As with the other modules, each library will be placed into a separate subdirectory within the **lib** module and will not have any build-time source dependencies on other libs being present within the checked-out module. + * Library revisions have 3 component revisions, x.y.z, where: + * x changes when the ABI is incompatible with the previous revision + * y changes when the ABI is changed, but remains compatible + * z changes when bugs are fixed that don't change the ABI + * Note that some platforms only have 1 or 2 component revisions for their libraries. On these systems, either the second component (y) could be bumped, or symbol versioning could be used by vendors who package the libraries. + * By default, all libraries are built as shared objects; however, with other build options, static, profiled and debug versions can be built. +The protocol module: **proto** + + * As noted above, this module contains the protocol headers that are required to build the **lib** and **xserver** modules. + * In addition, the protocol specifications will be included in this module. +The X server module: **xserver** + + * The X server is also one of the more difficult parts of the tree to modularize since it also has external dependencies, there is a strong desire among the vendors to separate the drivers into their own modules, and the different DDXs support different build options. + * The XFree86 drivers depend on the X server headers, and since we are splitting the drivers into a separate module, these headers will need to be installed before the **driver** module can built. These headers will installed in /usr/include/.../xserver as part of the normal install target. A special DDK install could also be added, if that proved useful. + * At some point we may want to investigate splitting each of the DDXs into separate modules, but not at this time. The current design does not preclude doing this research in the future. + * The **xserver** module depends on the **proto** module, and some of the DDXs depend on the **lib** module (e.g., Xnest, DMX). + * As noted above, some DDXs require different built options, which implies that not all DDXs will be able to use the same dix, os, mi, etc. compile. However, they can and should share the same source code. For example, the kdrive server does not support XINPUT whereas the Xorg server does, so dix (and other subdirs) will need to be built differently for each server. Note that these conflicts can be detected at configure time. + * The basic tree structure in the **xserver** module will look similar to the one used in the monolithic tree under `xc/programs/Xserver`. Notable exceptions include the drivers that will be moved to their own module (see below), and support programs that could be moved to the **app** module. +The XFree86 drivers module: **driver** + + * Vendors have expressed a strong desire to be able to ship updates to individual drivers as bugs are fixed, so they have been split out into their own module. + * The drivers consist of both input and output (i.e., video) drivers. + * Each driver will be completely self-contained and placed in a separate subdir within the module, with the subdir name reflecting the driver interface and the device that it supports (e.g., `xaa-mga`, `kaa-ati`, `xf86input-mouse`, etc.). + * The **driver** module depends on the headers from the **xserver** module being installed. + * Vendors can choose to distribute the entire **driver** module as a whole, or they can subdivide this module into finer components if desired. +The font module: **font** + + * This module contains the fonts traditionally distributed with the monolithic releases. + * Note that some fonts have more restrictive licenses and these should be fully documented in this module. + * The **font** module depends on the font tools that will be included in the **app** module be installed. +The documentation module: **doc** + + * This module contains the documentation traditionally distributed with the monolithic releases that has not been moved to another module. + * The majority of documentation in `xc/doc` will be relocated to the module that they document. For example, the protocol specifications will be moved to the **proto** module and the library docs will be moved to the **lib** module. +The build utilities module: **util** + + * This module contains the build tools and configuration files for legacy applications and libraries that have not been converted to use the autotools. + * Other utilities will also be placed here (e.g., makedepend, lndir and mkshadow). +The _extras_: + + * This is not a module, but rather a separate cache of known working tarballs required to build various modules (e.g., Mesa, freetype). + * It is expected that the vendors will include known working and supported versions of these extras in their OS releases. + * By default, the modules described above will build using the installed versions, but can be overridden when necessary. + * These tarballs are made available as a convenience to those doing development on OSes that don't have the latest known working versions. + +<a name="transition"></a> +## Transitioning from monolithic to modular + +Now that we've seen what the modular source tree could look like in the section above, we can explain how to transition from our current monolithic tree to the proposed modular one. The transition can begin once this proposal has been finalized and accepted. Figure 2 shows the outline of how this transition will happen. + +[[!img http://www.freedesktop.org/~kem/modular/figure2.gif] + +The modularization effort will begin by creating the top level modules. The order in which to create them is implicit in their dependencies (see previous section). During this development period, our goal is to share source files between both the monolithic and modular trees. + +Several options were investigated for how to share source files during this development period including copying the ,v files as each module is created, creating symlinks within the CVS repository, and modifying the pre- and/or post-checkin scripts. Each of these options had significant downsides. + +The solution we propose to share the source files is for developers working on modularization to use a script to populate their local modular trees with symlinks from a checked out version of the monolithic tree. During the initial development phase, the only files that will be checked directly into the modular tree -- and not in the monolithic tree -- are the ones related to the autotool build environment (e.g., configure.ac, Makefile.am). The symlink script will be updated as new modules are added or as files are moved around. If source file changes are required, then the developer working on modularization can make and test those changes in their local modular tree, and when the changes are ready to be checked in, they do so from the monolithic tree. + +While this initial modular development occurs, development will continue as normal in the monolithic HEAD. Once the modular tree reaches a suitably stable point in all of the modules, both trees will be frozen for new features (Devel Freeze in Figure 2). We expected that this freeze will be announced several weeks before it takes place. At that time, the first release candidate (RC1) will be tagged, and we will begin to stabilize both trees for release. + +During this stabilization phase, release testing will begin on both the modular and monolithic trees. The script that populates the modular tree with symlinks will continue to be used, and files will continue to be checked in from the monolithic tree. Additional release candidates will be tagged as bugs are fixed and the release stabilizes. + +When the modular and monolithic trees reach the point where they could be released, the ,v files that have been symlinked will be copied within the CVS repository and a release candidate will be tagged (RCn in Figure 2). Additional testing will occur and any bugs caused by the copying of the ,v files will be fixed. Only major show stopper bug fixes will be accepted at that time, and they will need to be checked into both the monolithic and modular source trees. + +When both releases are ready (Release Tag in Figure 2), the monolithic tree will be tagged with XORG-6_9_0 and the modular tree will be tagged with XORG-7_0_0. In addition, the 6.9 and 7.0 branches will created in their respective trees. + +This plan was designed to ensure that the actual content of both the X11``R6.9 and X11``R7 releases are the same, so that no new features currently under development in the monolithic tree HEAD are left behind. Also, it allows those vendors who are not ready to move to a modular tree to have access to all of the latest features in the X11``R6.9 release. + + +<a name="future"></a> +## Future modular releases + +Looking forward to the time after the initial release, modularization will change the way packages are added to the CVS tree and the release process. This section proposes how these tasks could be handled in the future. + +Future X.Org Foundation releases can be constructed from an official list of the packages in the modular tree (along with specific package versions). This official release list should be maintained by the [[Architecture Working Group|ArchitectureWorkingGroup]]. The initial modular release will contain only what is included in the corresponding monolithic release. + +After the initial release, we will open up the modules for new code and packages to be included. Each package will be placed in the most appropriate module. For example, applications can be added to the **app** module, libraries can be added to the **lib** module, etc. The maintainers will be responsible for freezing, stabilizing, and tagging for release their packages and can do so on their own schedules. This should help simply the official release process. + +As new code or packages are added to the modular tree, the maintainers will need to request that their packages be added to the official release list, if they want them included in an official release. By default, their packages will not be included. A formal process for package maintainers to follow in order to have their code included in future official X.Org Foundation releases needs to be defined. This process is not something that we can work out in this proposal as it should be handled within the [[Architecture Working Group|ArchitectureWorkingGroup]]. + +Official releases will be announced well in advance and with specific deadlines, so that both individual package maintainers whose packages are already included on the official release list can get their latest stable packages ready for inclusion, and package maintainers who want to have their packages included have the opportunity to discuss them with the [[Architecture Working Group|ArchitectureWorkingGroup]] before the feature freeze deadline. + +Once the feature freeze deadline is reached, the release wranglers can determine which packages are included by looking at the official release list for the current release. Only packages within a module that are on the release list will be included in the release. However, if code within a package already on release list is not ready to ship (e.g., a new extension in the **xserver** module), then what is included in the official release becomes more complicated. The solution we propose is to require that unfinished development code live only on a branch until it is ready to be released. This solution will allow the new code to be developed on its own schedule and not hold up official releases. It will also help us to minimize the possibility of having to back out code during the release process. + +During the stabilization phase of a release, inter-package testing and debugging can be done by installing the packages from the official package list. If problems are found during testing, bugs can be filed for the package maintainers to fix. Other details of how this process will happen should be worked out within the [[Release Wranglers|ReleaseWorkingGroup]]. + +Once the bugs have been resolved and the release wranglers feel the release is ready to ship, tarballs from the final packages on the official release list will be created and released. + + +<a name="updates"></a> +_Updated 2005-03-31 in preparation to present to Architecture Working Group_ +_Updated 2005-04-11 and 2005-04-22 to remove inaccurate statements_ +_Updated 2005-04-29 to add anchors for external reference_ +_Updated 2005-05-13 to fix typo_ diff --git a/ModularizationWorkingGroup.mdwn b/ModularizationWorkingGroup.mdwn new file mode 100644 index 00000000..d7fadd65 --- /dev/null +++ b/ModularizationWorkingGroup.mdwn @@ -0,0 +1,41 @@ + + +# X.Org Foundation Modularization Working Group + + +## Purpose + +The purpose of this working group is to create a detailed design plan for how to modularize the X.Org Foundation source tree and then implement the plan once it has been approved by the Architecture Working Group. Participation is open to all interested developers. Participants are expected to actively participate in the design discussions, write proposals and other documentation, etc. + +As chair of this working group, my purpose is to organize the discussions, participate in the design and generally facilitate the group's progress toward creating a design and an eventual release. + + +## Status + +A few weeks ago the Modularization Working Group was announced, and several people expressed interest in helping out. Many of them attended the recent X Developers Conference meeting in Boston and talked about how modularization might be accomplished. Since there had not been very much discussion on the mailing lists after the initial announcement, we decided to take advantage of our face to face time to lay the groundwork for creating a proposal. We have now worked through the issues that we discovered in an effort to create a strawman proposal that describes the rationale for modularization, attempts to address the known concerns people have raised, provides background on other modularization efforts, explains what the modularized source tree would look like, outlines the steps required to take this idea from concept to release, and suggests how future modular releases can be handled. + +Since then the Modularization Working Group has discussed the initial strawman proposal, made modifications, and reached consensus that it should be presented to the Architecture Working Group for approval. The proposal was presented to the ArchWG on 4 Apr 2005 and no objections were raised during the discussion period, so it was approved. We are currently discussing implementation plans and have now begun the development phase. If you are interested in joining in this discussion or participating in the development effort, please join us on the mailing list (below). + + +## Mailing list + +A mailing list has been created on our new mailing list system for those who are interested in discussing the strawman proposal and working on modularizing the source tree. To subscribe to this list, please visit: + + * [[http://lists.x.org/mailman/listinfo/xorg-modular|http://lists.x.org/mailman/listinfo/xorg-modular]] +Mail can be sent to this list at **[[xorg-modular@lists.x.org|mailto:xorg-modular@lists.x.org]]** + + +## Modularization resources + +* [[ModularizationProposal|ModularizationProposal]] -- Current modularization proposal. +* [[ModularizationDevelPlan|ModularizationDevelPlan]] -- Current modularization development plan. +* [[ModuleComponentList|ModuleComponentList]] -- List of the proposed module components. +* [[ModularDevelopersGuide|ModularDevelopersGuide]] -- Guide for developers that work in the modular source tree. +* [[X11R7and69TODO|X11R7and69TODO]] -- List of tasks to complete before release + +## Past modularization efforts + +* [[GoingModular|GoingModular]] -- How to get the X.org tree from here to there. +* [[X Libraries|http://www.freedesktop.org/Software/xlibs]] is a project containing modular, autotooled version of X Window System libraries. +* [[X Server|http://www.freedesktop.org/Software/xserver]] is a project containing a modular, autotooled X server implementation. +* [[xapps|http://www.freedesktop.org/Software/xapps]] is a project containing modular, autotooled X applications.
\ No newline at end of file diff --git a/ModuleComponentList.mdwn b/ModuleComponentList.mdwn new file mode 100644 index 00000000..b72eed41 --- /dev/null +++ b/ModuleComponentList.mdwn @@ -0,0 +1,329 @@ + + +# List of X.Org Module Components + +[[!toc ]] + + +## General guidelines + + * Components should be put into the module that best reflects the primary interface for the code. For example, many packages, like Xpm, build both applications and libraries, but the primary interface for Xpm is the library. The applications included, cxpm and sxpm, are ancillary tools. + * Documentation should be included with the primary component. For example, the Xt library man pages which previous existed in xc/doc/man/Xt will be moved to the Xt component in the lib module. + +## app + + * xc/programs/appres + * xc/programs/bdftopcf + * xc/programs/beforelight + * xc/programs/bitmap + * xc/programs/cxpm + * xc/programs/dpsexec + * xc/programs/dpsinfo + * xc/programs/editres + * xc/programs/fonttosfnt + * xc/programs/fslsfonts + * xc/programs/fstobdf + * xc/programs/iceauth + * xc/programs/ico + * xc/programs/lbxproxy + * xc/programs/listres + * xc/programs/luit + * xc/programs/makepsres + * xc/programs/mkcfm + * xc/programs/mkfontdir + * xc/programs/mkfontscale + * xc/programs/oclock + * xc/programs/pclcomp + * xc/programs/proxymngr + * xc/programs/rgb + * xc/programs/rstart + * xc/programs/scripts + * xc/programs/setxkbmap + * xc/programs/showfont + * xc/programs/smproxy + * xc/programs/sxpm + * xc/programs/texteroids + * xc/programs/twm + * xc/programs/viewres + * xc/programs/x11perf + * xc/programs/xauth + * xc/programs/xbiff + * xc/programs/xcalc + * xc/programs/xclipboard + * xc/programs/xclock + * xc/programs/xcmsdb + * xc/programs/xconsole + * xc/programs/xcursorgen + * xc/programs/xdbedizzy + * xc/programs/xditview + * xc/programs/xdm + * xc/programs/xdpyinfo + * xc/programs/xdriinfo + * xc/programs/xedit + * xc/programs/xev + * xc/programs/xeyes + * xc/programs/xf86dga + * xc/programs/xfd + * xc/programs/xfindproxy + * xc/programs/xfontsel + * xc/programs/xfs + * xc/programs/xfsinfo + * xc/programs/xfwp + * xc/programs/xgamma + * xc/programs/xgc + * xc/programs/xhost + * xc/programs/xinit + * xc/programs/xkbcomp + * xc/programs/xkbevd + * xc/programs/xkbprint + * xc/programs/xkbutils + * xc/programs/xkill + * xc/programs/xload + * xc/programs/xlogo + * xc/programs/xlsatoms + * xc/programs/xlsclients + * xc/programs/xlsfonts + * xc/programs/xmag + * xc/programs/xman + * xc/programs/xmessage + * xc/programs/xmh + * xc/programs/xmodmap + * xc/programs/xmore + * xc/programs/xphelloworld + * xc/programs/xplsprinters + * xc/programs/xpr + * xc/programs/xprehashprinterlist + * xc/programs/xprop + * xc/programs/xrandr + * xc/programs/xrdb + * xc/programs/xrefresh + * xc/programs/xrx + * xc/programs/xset + * xc/programs/xsetmode + * xc/programs/xsetpointer + * xc/programs/xsetroot + * xc/programs/xsm + * xc/programs/xstdcmap + * xc/programs/xtrap + * xc/programs/xvidtune + * xc/programs/xvinfo + * xc/programs/xwd + * xc/programs/xwininfo + * xc/programs/xwud + +## lib + + * xc/doc/man (_See note above about including documentation in corresponding library component_) + * xc/lib/FS + * xc/lib/GL + * xc/lib/GLU + * xc/lib/GLw + * Some of the GL libraries may be provided by Mesa instead. + * xc/lib/ICE + * xc/lib/Xaw7 + * xc/lib/SM + * xc/lib/X11 + * xc/include/bitmaps + * xc/nls + * xc/lib/XRes + * xc/lib/XTrap + * xc/lib/Xau + * xc/lib/Xaw + * xc/lib/Xaw6 + * xc/lib/Xbsd + * xc/lib/Xcomposite + * xc/lib/Xcursor + * xc/lib/Xdamage + * xc/lib/Xdmcp + * xc/lib/Xevie + * xc/lib/Xext + * xc/lib/Xfixes + * xc/lib/Xfontcache + * xc/lib/Xft + * xc/lib/Xft1 + * xc/lib/Xi + * xc/lib/Xinerama + * xc/lib/Xmu + * xc/lib/Xmuu + * xc/lib/Xp + * xc/lib/Xpm + * Moved here from xc/extras/Xpm since we are currently the upstream maintainer + * xc/lib/Xprint``App``Util + * xc/lib/Xprint``Util + * xc/lib/Xrandr + * xc/lib/Xrender + * xc/lib/Xss + * xc/lib/Xt + * xc/lib/Xtst + * xc/lib/Xv + * xc/lib/XvMC + * xc/lib/Xxf86dga + * xc/lib/Xxf86misc + * xc/lib/Xxf86rush + * xc/lib/Xxf86vm + * xc/lib/apple + * xc/lib/dmx + * xc/lib/dps + * xc/lib/dpstk + * xc/lib/font + * xc/lib/fontenc + * xc/lib/lbxutil + * xc/lib/misc + * xc/lib/oldX + * xc/lib/psres + * xc/lib/windows + * xc/lib/xkbfile + * xc/lib/xkbui + * xc/lib/xtrans + +## proto + +Note that some of the headers will be moved to the appropriate library component. Only the protocol headers should remain. + + * xc/include + * xc/include/DPS + * xc/include/GL + * xc/include/extensions + * xc/include/fonts + +## xserver + + * xc/programs/Xserver + +## driver + + * xc/programs/Xserver/hw/xfree86/drivers/apm + * xc/programs/Xserver/hw/xfree86/drivers/ark + * xc/programs/Xserver/hw/xfree86/drivers/ati + * xc/programs/Xserver/hw/xfree86/drivers/chips + * xc/programs/Xserver/hw/xfree86/drivers/cirrus + * xc/programs/Xserver/hw/xfree86/drivers/cyrix + * xc/programs/Xserver/hw/xfree86/drivers/dummy + * xc/programs/Xserver/hw/xfree86/drivers/fbdev + * xc/programs/Xserver/hw/xfree86/drivers/glide + * xc/programs/Xserver/hw/xfree86/drivers/glint + * xc/programs/Xserver/hw/xfree86/drivers/i128 + * xc/programs/Xserver/hw/xfree86/drivers/i740 + * xc/programs/Xserver/hw/xfree86/drivers/i810 + * xc/programs/Xserver/hw/xfree86/drivers/i2c + * xc/programs/Xserver/hw/xfree86/drivers/imstt + * xc/programs/Xserver/hw/xfree86/drivers/mga + * xc/programs/Xserver/hw/xfree86/drivers/neomagic + * xc/programs/Xserver/hw/xfree86/drivers/newport + * xc/programs/Xserver/hw/xfree86/drivers/nsc + * xc/programs/Xserver/hw/xfree86/drivers/nv + * xc/programs/Xserver/hw/xfree86/drivers/rendition + * xc/programs/Xserver/hw/xfree86/drivers/s3 + * xc/programs/Xserver/hw/xfree86/drivers/s3virge + * xc/programs/Xserver/hw/xfree86/drivers/savage + * xc/programs/Xserver/hw/xfree86/drivers/siliconmotion + * xc/programs/Xserver/hw/xfree86/drivers/sis + * xc/programs/Xserver/hw/xfree86/drivers/sunbw2 + * xc/programs/Xserver/hw/xfree86/drivers/suncg14 + * xc/programs/Xserver/hw/xfree86/drivers/suncg3 + * xc/programs/Xserver/hw/xfree86/drivers/suncg6 + * xc/programs/Xserver/hw/xfree86/drivers/sunffb + * xc/programs/Xserver/hw/xfree86/drivers/sunleo + * xc/programs/Xserver/hw/xfree86/drivers/suntcx + * xc/programs/Xserver/hw/xfree86/drivers/tdfx + * xc/programs/Xserver/hw/xfree86/drivers/tga + * xc/programs/Xserver/hw/xfree86/drivers/trident + * xc/programs/Xserver/hw/xfree86/drivers/tseng + * xc/programs/Xserver/hw/xfree86/drivers/v4l + * xc/programs/Xserver/hw/xfree86/drivers/vesa + * xc/programs/Xserver/hw/xfree86/drivers/vga + * xc/programs/Xserver/hw/xfree86/drivers/via + * xc/programs/Xserver/hw/xfree86/drivers/sisusb + * xc/programs/Xserver/hw/xfree86/drivers/vmware + * xc/programs/Xserver/hw/xfree86/drivers/voodoo + * xc/programs/Xserver/hw/xfree86/drivers/wsfb + * xc/programs/Xserver/hw/xfree86/input/acecad + * xc/programs/Xserver/hw/xfree86/input/aiptek + * xc/programs/Xserver/hw/xfree86/input/calcomp + * xc/programs/Xserver/hw/xfree86/input/citron + * xc/programs/Xserver/hw/xfree86/input/digitaledge + * xc/programs/Xserver/hw/xfree86/input/dmc + * xc/programs/Xserver/hw/xfree86/input/dynapro + * xc/programs/Xserver/hw/xfree86/input/elo2300 + * xc/programs/Xserver/hw/xfree86/input/elographics + * xc/programs/Xserver/hw/xfree86/input/fpit + * xc/programs/Xserver/hw/xfree86/input/hyperpen + * xc/programs/Xserver/hw/xfree86/input/jamstudio + * xc/programs/Xserver/hw/xfree86/input/joystick + * xc/programs/Xserver/hw/xfree86/input/keyboard + * xc/programs/Xserver/hw/xfree86/input/magellan + * xc/programs/Xserver/hw/xfree86/input/magictouch + * xc/programs/Xserver/hw/xfree86/input/microtouch + * xc/programs/Xserver/hw/xfree86/input/mouse + * xc/programs/Xserver/hw/xfree86/input/mutouch + * xc/programs/Xserver/hw/xfree86/input/palmax + * xc/programs/Xserver/hw/xfree86/input/penmount + * xc/programs/Xserver/hw/xfree86/input/sample + * xc/programs/Xserver/hw/xfree86/input/spaceorb + * xc/programs/Xserver/hw/xfree86/input/summa + * xc/programs/Xserver/hw/xfree86/input/evdev + * xc/programs/Xserver/hw/xfree86/input/tek4957 + * xc/programs/Xserver/hw/xfree86/input/ur98 + * xc/programs/Xserver/hw/xfree86/input/void + * xc/programs/Xserver/hw/xfree86/input/wacom + +## font + + * xc/fonts/bdf + * xc/fonts/bdf/100dpi + * xc/fonts/bdf/75dpi + * xc/fonts/bdf/cyrillic + * xc/fonts/bdf/misc + * xc/fonts/encodings + * xc/fonts/encodings/large + * xc/fonts/scaled + * xc/fonts/scaled/CID + * xc/fonts/scaled/TTF + * xc/fonts/scaled/Ethiopic + * xc/fonts/scaled/Meltho + * xc/fonts/scaled/Speedo + * xc/fonts/scaled/Type1 + * xc/fonts/util + +## doc + + * xc/doc/misc + * xc/doc/util + * xc/doc/hardcopy + * xc/doc/specs +Note that we plan to keep the specs and related docs that have not yet been converted to a modern format in the doc module temporarily. Then, as they are converted to a new format, we will move them to the appropriate component in the proto or lib modules. + + +## util + + * xc/config/cf + * xc/config/util + * xc/config/util/mkshadow + * xc/config/docbook + * xc/config/imake + * xc/config/makedepend + * xc/config/pswrap + * xc/util/memleak + * xc/util/misc + +## Tarballs + +This is not another module, but rather a list of software we depend on that is maintained outside of the X.Org project. In the monolithic tree, they were put into xc/extras. For the modular tree, we will make specific versions of this third-party software available on the website as a convenience for those who don't have the latest know working versions available from their OS vendor. + + * xc/extras/Mesa + * Includes xc/programs/glxgears and xc/programs/glxinfo + * xc/extras/drm + * xc/extras/expat + * xc/extras/fontconfig + * Includes xc/programs/fc-cache, xc/programs/fc-lang and xc/programs/fc-list + * xc/extras/fonts + * We will be the upstream for arabic24 and ClearlyU + * The Bitstream-Vera fonts can be found here: [[http://ftp.gnome.org/pub/GNOME/sources/ttf-bitstream-vera/1.10/|http://ftp.gnome.org/pub/GNOME/sources/ttf-bitstream-vera/1.10/]] + * xc/extras/freetype2 + * xc/extras/ogl-sample + * xc/extras/regex + * xc/extras/rman + * xc/extras/ttf2pt1 + * xc/extras/x86emu + * xc/extras/zlib + * xc/programs/xterm
\ No newline at end of file diff --git a/ModuleDescriptions.mdwn b/ModuleDescriptions.mdwn new file mode 100644 index 00000000..1a6efd45 --- /dev/null +++ b/ModuleDescriptions.mdwn @@ -0,0 +1,298 @@ + +The X11``R7.0 release broke the X Window System source tree into many different modules for each application, library, major protocol extensions, and so on. This page lists what all those modules are. + +The categories I've broken them into are: +Core X11 runtime +: Things every basic desktop system should have to run. You could run specialized/embedded environments with less, but a general purpose desktop should probably have them all. + +Core X11 build/development/install +: Things you don't need for running X, but need to build the Xorg modular tree, or to build/install additional X software or fonts. + +Extended X11 platform +: Additional useful utilities that many general purpose desktops will want to have installed, but not everyone will. + +Legacy X11 platform +: Utilities used in classic X desktops, but which desktops like GNOME and KDE generally provide their own versions of, so you may not need if you plan to exclusively use/support one of those desktops, but would want for users with existing desktop environments. Also, software you may need to build and/or run legacy third-party apps, like apps using Xt-based toolkits like Motif/Xaw or software built with Imakefiles. + +Experimental +: Stuff which will likely become part of the X Core in the future but isn't quite there yet. + +Obsolete/deprecated +: +Things we shipped in this release to complete the monolith -> modular transition, but don't recommend most people use and which will probably not be included in the future. Suggested replacements are shown for each of these. + + +Sample/demo/test apps +: Primarily useful to developers or people needing to test that various extensions are working properly. + + + + +--- + + + + +## Core X11 runtime: + +* app/iceauth - _ICE authority file utility_ +* app/rgb - _X colorname -> RGB mapping database_ +* app/sessreg - _Register X sessions in system utmp/utmpx databases_ +* app/setxkbmap - _set the keyboard using the X Keyboard Extension_ +* app/smproxy - _Session Manager Proxy_ +* app/xauth - _X authority file utility_ +* app/xdpyinfo - _display information utility for X_ +* app/xev - _print contents of X events_ +* app/xhost - _server access control program for X_ +* app/xinit - _X Window System initializer (includes startx)_ +* app/xkbcomp - _compile XKB keyboard description_ +* app/xkill - _kill a client by its X resource_ +* app/xlsatoms - _list interned atoms defined on server_ +* app/xlsclients - _list client applications running on a display_ +* app/xlsfonts - _list X fonts available on X server_ +* app/xmodmap - _utility for modifying keymaps and button mappings_ +* app/xprop - _property displayer for X_ +* app/xrandr - _primitive command line interface to RandR extension_ +* app/xrdb - _X server resource database utility_ +* app/xrefresh - _refresh all or part of an X screen_ +* app/xset - _user preference utility for X_ +* app/xsetmode - _set the mode for an X Input device_ +* app/xsetpointer - _set an X Input device as the main pointer_ +* app/xsm - _X Session Manager_ +* app/xvinfo - _Print out X-Video extension adaptor information_ +* app/xwininfo - _window information utility for X_ +* data/bitmaps - _standard set of X bitmaps_ +* data/cursors - _standard set of X cursors_ +* lib/FS - _X Font Service client library_ +* lib/ICE - _Inter-Client Exchange library_ +* lib/SM - _Session Management library_ +* lib/X11 - _X11 Client library_ +* lib/Xau - _X Authorization routines_ +* lib/Xdmcp - _X Display Manager Control Protocol routines_ +* lib/Xext - _common X Extensions library_ +* lib/Xfont - _X font handling library for server & utilities_ +* lib/Xfontcache - _X-[[TrueType|TrueType]] font cache extension client library_ +* lib/Xft - _Client side font rendering library_ +* lib/Xi - _X Input Extension library_ +* lib/Xinerama - _Xinerama protocol library_ +* lib/Xmu - _X miscellaneous utility routines_ +* lib/Xpm - _XPM format pixmap library_ +* lib/Xrandr - _Xrandr extension library_ +* lib/Xrender - _RENDER extension library_ +* lib/Xv - _Xvideo extension library_ +* lib/Xxf86misc - _XFree86-MISC extension library_ +* lib/Xxf86vm - _XFree86-[[VidMode|VidMode]] extension library_ +* lib/fontenc - _font encoding library_ +* lib/lbxutil - _LBX utility routines_ +* lib/xkbfile - _XKB file handling routines_ +* xserver/xorg - _X servers (including Xorg, Xprt, Xvfb, Xnest, & Xdmx)_ + +### Platform specific: + +* lib/AppleWM - _(MacOS)_ +* lib/WindowsWM - _(Win32)_ +* app/xdriinfo - _query configuration information of DRI drivers (DRI-supporting platforms)_ + + +--- + + + + +## Core X11 build/development/install: + +* app/bdftopcf - _convert X font from Bitmap Distribution Format to Portable Compiled Format_ +* app/mkcfm - _create summaries of CID font metric files_ +* app/mkfontdir - _create an index of X font files in a directory_ +* app/mkfontscale - _create an index of scalable font files for X_ +* app/xcursorgen - _create an X cursor file from PNG images_ +* doc/xorg-sgml-doctools - _document format conversion tools for SGML docs_ +* lib/xtrans - _X Network Transport layer shared code_ +* proto/BigReqs +* proto/Fontcache - _font cache header files_ +* proto/Fonts - _font library header files_ +* proto/GL - _GL/GLX (3D) header files_ +* proto/Input - _Xinput header files_ +* proto/KB - _XKB (keyboard) extension header files_ +* proto/PM - _X Proxy Management header files_ +* proto/Xinerama +* proto/Randr +* proto/Render +* proto/Resource +* proto/ScrnSaver - _X [[ScreenSaver|ScreenSaver]] extension header files_ +* proto/Video +* proto/X11 +* proto/XCMisc +* proto/XExt +* proto/XF86Misc +* proto/XF86VidMode +* util/macros - _autoconf macros used in X modular configure.ac files_ + +### Platform specific: + +* proto/AppleWM - _(MacOS)_ +* proto/WindowsWM - _(Win32)_ +* proto/XF86DRI - _(DRI-supporting platforms)_ + + +--- + + + + +## Extended X11 platform: + +* app/bitmap - _XBM format bitmap editor and converter utilities_ +* app/scripts (xauth_switch_to_sun-des-1) - _Secure RPC (SUN-DES-1) helper script_ +* app/xcmsdb - _Device Color Characterization utility for X Color Management System_ +* app/xfd - _display all the characters in an X font_ +* app/xfontsel - _point and click selection of X11 font names_ +* app/xgamma - _Alter a monitor's gamma correction through the X server_ +* app/xkbprint - _print an XKB keyboard description_ +* app/xload - _system load average display for X_ +* app/xmag - _magnify parts of the screen_ +* app/xman - _Unix manual page viewer_ +* app/xmore - _plain text display program for the X Window System_ +* app/xpr - _print an X window dump from xwd_ +* app/xrx - _"Broadway"_ +* app/xvidtune - _video mode tuner for Xorg_ +* app/xwd - _dump current contents of X window or screen to file_ +* app/xwud - _display an X window dump from xwd_ +* lib/XRes - _X Resource extension_ +* lib/XScrnSaver - _MIT-SCREEN-SAVER extension_ +* lib/XTrap - _X Trap extension_ +* lib/Xcursor +* lib/Xtst +* lib/XvMC +* lib/Xxf86dga +* lib/dmx +* lib/xkbui +* proto/DMX +* proto/Record +* proto/Trap +* proto/XF86BigFont +* proto/XF86DGA +* proto/XF86Rush + +### X Font Server & related tools: + +* app/fslsfonts - _list fonts served by X font server_ +* app/fstobdf - _generate BDF font from X font server_ +* app/showfont - _show information about X font from font server_ +* app/xfs - _X Font Server_ +* app/xfsinfo - _X font server information utility_ + +### Xprint & related software: + +* app/pclcomp - _Compress PCL printer image output files_ +* app/xplsprinters - _List Xprint printers_ +* app/xprehashprinterlist - _Rehash list of Xprint printers_ +* lib/Xp - _Xprint client library_ +* lib/XprintAppUtil - _Xprint application utility routines_ +* lib/XprintUtil - _Xprint application utility routines_ +* proto/Print - _Xprint Protocol_ + +### Platform specific: + +* app/constype - _print type of console_ (SPARC & Sun/3 platforms, plus Solaris x86) + + +--- + + + + +## Legacy X11 platform: + +* app/luit - _Convert terminal i/o from legacy encodings to UTF-8_ +* app/oclock - _round X clock_ +* app/twm - _simple window manager_ +* app/xbiff - _watch mailboxes for new message delivery_ +* app/xcalc - _scientific calculator for X_ +* app/xclipboard - _X clipboard manager_ +* app/xclock - _X clock_ +* app/xconsole - _monitor system console messages with X_ +* app/xditview - _display ditroff output_ +* app/xdm - _X Display Manager / XDMCP server_ +* app/xedit - _simple text editor for X_ +* app/xmessage - _display a message or query in a window_ +* app/xsetroot - _root window parameter setting utility for X_ +* app/xstdcmap - _X standard colormap utility_ +* lib/Xaw - _Athena Widgets toolkit_ + +### Xt Toolkit Intrinsics and related software: + +* app/appres - _list X application resource database_ +* app/editres - _dynamic resource editor for X Toolkit applications_ +* app/listres - _list resources in widgets_ +* app/viewres - _graphical class/resource browser for Xt_ +* lib/Xt - _X Toolkit Intrinsics library_ + +### X Network Proxies & Remote Start: + +(Preferred replacements: ssh and/or NX) + +* app/lbxproxy - _Low [[BandWidth|BandWidth]] X proxy_ +* app/proxymngr - _proxy manager service_ +* app/rstart - _Remote Start client_ +* app/xfindproxy - _locate proxy services_ +* app/xfwp - _X Firewall Proxy_ + +### Imake build system: + +* util/cf - _Imake config files_ +* util/imake - _Imake utility_ +* util/makedepend - _makefile dependency listing generator_ +* util/xmkmf - _Imake helper utility_ + + +--- + + + + +## Experimental: + +* app/fonttosfnt - _Wrap a bitmap font in a sfnt ([[TrueType|TrueType]]) wrapper_ +* lib/Xcomposite - _Composite extension_ +* lib/Xdamage - _Damage extension_ +* lib/Xevie - _XEvIE extension_ +* lib/Xfixes - _X-Fixes extension_ +* proto/Composite - _Composite extension_ +* proto/Damage - _Damage extension_ +* proto/EvIE - _XEvIE extension_ +* proto/Fixes - _X-Fixes extension_ + + +--- + + + + +## Obsolete/Deprecated: + +* app/scripts (xon) - _run X command on another system via rsh_ (Preferred replacement: ssh) +* app/xmh - _X interface to MH mail tools_ (Preferred replacement: exmh) +* data/xkbdata - _XKB keyboard configuration data_ (Preferred replacement: xkb-config) +* lib/oldX - _X version 10 backwards compatibility_ (Preferred replacement: X11!) + + +--- + + + + +## Sample/demo/test applications: + +* app/beforelight - _MIT-SCREEN-SAVER sample_ +* app/ico - _animate an icosahedron or other polyhedron_ +* app/x11perf - _simple X server performance benchmarker_ +* app/xdbedizzy - _DBE sample_ +* app/xeyes - _follow the mouse/SHAPE extension X demo_ +* app/xf86dga - _test program for the XFree86-DGA extension_ +* app/xgc - _X graphics demo_ +* app/xkbevd - _XKB event daemon demo_ +* app/xkbutils - _XKB utility demos_ +* app/xlogo - _Draw (old) X logo_ +* app/xphelloworld - _Xprint sample applications_ +* app/xtrap - _XTrap sample clients_
\ No newline at end of file diff --git a/MoinMoin.mdwn b/MoinMoin.mdwn new file mode 100644 index 00000000..eaedd187 --- /dev/null +++ b/MoinMoin.mdwn @@ -0,0 +1,39 @@ + +The following pages are about the development of MoinMoin: + +* [[!MoinMoin MoinMoinQuestions desc="MoinMoinQuestions"]] - Questions about MoinMoin (installing, etc.) +* [[!MoinMoin MoinMoinTips desc="MoinMoinTips"]] - Tips & tricks for MoinMoin +* [[!MoinMoin MoinMoinTranslation desc="MoinMoinTranslation"]] - discussion about translating MoinMoin +* [[!MoinMoin MoinMoinBugs desc="MoinMoinBugs"]] - bugs in the software (see also [[The Sourceforge Bug Tracker|http://sourceforge.net/tracker/?group_id=8482&atid=108482]]) +* [[!MoinMoin MoinMoinDiscussion desc="MoinMoinDiscussion"]] - discussion about new features +* [[!MoinMoin MoinMoinIdeas desc="MoinMoinIdeas"]] - you are encouraged to _add_ wishes and ideas to this page +* [[!MoinMoin MoinMoinMailingLists desc="MoinMoinMailingLists"]] - discussion about MoinMoin via email +* [[!MoinMoin MoinMoinWinCvs desc="MoinMoinWinCvs"]] - instructions on using WinCVS to obtain the latest source of MoinMoin +* [[HelpForDevelopers|HelpForDevelopers]] - the rules that govern MoinMoin development +These pages provide information about using and installing MoinMoin: + +* [[/TextFormatting|MoinMoin/TextFormatting]] - a page containing samples of all the markup options +* [[!MoinMoin MoinMoinSuccessStories desc="MoinMoinSuccessStories"]] - what do other people use MoinMoin for? +* [[HelpContents|HelpContents]] - The main page of the help system +* [[HelpMiscellaneous/FrequentlyAskedQuestions|HelpMiscellaneous/FrequentlyAskedQuestions]] - Frequently Asked Questions (ask your own on [[!MoinMoin MoinMoinQuestions desc="MoinMoinQuestions"]]) +* [[!MoinMoin MoinMoinMailingLists desc="MoinMoinMailingLists"]] - discussion about MoinMoin via email +* [[!MoinMoin MoinMoinWikis desc="MoinMoinWikis"]] - list of wiki sites using MoinMoin +* [[/InstallDocs|MoinMoin/InstallDocs]] - all the help pages about installation rolled into one +* [[/InstallationsAnleitung|MoinMoin/InstallationsAnleitung]] - installation docs in German +* [[!MoinMoin SecurityPolicy desc="SecurityPolicy"]] - explains how to restrict access to your wiki, or parts of it +* [[!MoinMoin MoinMoinSyndication desc="MoinMoinSyndication"]] - Support for RSS feeds and other collaboration features across systems +Other pages about MoinMoin: + +* [[!MoinMoin MoinMoinEtymology desc="MoinMoinEtymology"]] +External links: + +* [[SourceForge Project Info|http://sourceforge.net/projects/moin/]] +* [[Project Homepage|http://moin.sourceforge.net/]] +* [[FreshMeat Entry|http://freshmeat.net/projects/moin]] +* [[PythonNews article on wikis|http://www.oreillynet.com/pub/a/python/2000/11/29/pythonnews.html]] +Connect to [[!Foldoc IRC desc="IRC"]] for meeting the author and other MoinMoin users and developers: + +* channel `#moin` on [[!MoinMoin FreeNode desc="FreeNode"]] server `irc.freenode.net` +* see also [[freenode home page|http://freenode.net/]] and esp. [[freenode IRC servers|http://freenode.net/irc_servers.shtml]] for more information +[[!img http://www.opensource.org/trademarks/opensource/web/opensource-110x95.png] +[[Open Source|http://www.opensource.org/docs/definition.php]] diff --git a/MoinMoin/InstallDocs.mdwn b/MoinMoin/InstallDocs.mdwn new file mode 100644 index 00000000..562ae1f5 --- /dev/null +++ b/MoinMoin/InstallDocs.mdwn @@ -0,0 +1,104 @@ + +This HTML page contains the basic install docs that can be found on [[http://moinmaster.wikiwikiweb.de/MoinMoin/InstallDocs|http://moinmaster.wikiwikiweb.de/MoinMoin/InstallDocs]]. It contains all necessary information to get your wiki up and running, even without being online. If you have a permanent internet connection, you might want to browse the docs on the Help``On``Installing page, which might contain more up-to-date information. + +After following the procedures on this page, you should have a working wiki and can browse the rest of the online docs there. + + +## How to install your own MoinMoin Wiki + +This page describes the installation procedure applying to [[!MoinMaster MoinMoin desc="MoinMoin"]] version 1.1 and up. In the next section, there is a list of real-world [[Installation Scenarios|MoinMoin/InstallDocs]] that help you to understand how to apply the instructions in different environments. + +[[Basic Installation|MoinMoin/InstallDocs]] explains the "`setup.py`" step of the installation in more detail. This applies equally to all scenarios, and you should read it before trying a live installation. + +[[Trouble-shooting|MoinMoin/InstallDocs]] helps with fixing any general problems you might encounter, which apply to any installation platform. + +After a successful installation, you might want to read more about configuration and other options that you, as the wiki administrator, can set up. [[!MoinMaster HelpOnAdministration desc="HelpOnAdministration"]] contains links to pages that cover these topics. Especially, the [[!MoinMaster HelpOnConfiguration desc="HelpOnConfiguration"]] and [[!MoinMaster HelpOnUpdating desc="HelpOnUpdating"]] pages provide additional information regarding wiki setup and maintenance. [[!MoinMoin MoinMoinWinCvs desc="MoinMoinWinCvs"]] and [[!MoinMoin MoinMoinUnixCvs desc="MoinMoinUnixCvs"]] describe how to run your wiki using the current development version from the [[!MoinMoin SourceForge desc="SourceForge"]] CVS repository. +[[!table header="no" class="mointable" data=""" + Please **make sure** that you do **not** accidently put your wiki's **`data/`** directory under a directory directly accessible by your web server (like below document root). Or at least forbid your web server serving anything below `data/` to a user - this is neither needed nor wanted! Your web server needs to serve moin.cgi and the stuff below htdocs **only**. +"""]] + +<a name="installscenarios"></a> +### Sample Installation Scenarios + +The following links lead you to concrete examples of installation sessions, showing the commands used and explaining what they do. It is highly recommended that you _first_ read the general information on installing (especially the next section of this page) before choosing an installation scenario that best fits your intended use of [[!MoinMaster MoinMoin desc="MoinMoin"]]. + +UNIX: + +* [[UNIX Installation|MoinMoin/InstallDocs]] +Windows: + +* [[Windows Installation using Apache|MoinMoin/InstallDocs]] +* [[Windows Installation using IIS|MoinMoin/InstallDocs]] +Mac OS X: + +* [[Mac OS X Installation|MoinMoin/InstallDocs]] +Long-Running-Process Setup: + +* [[FastCGI Setup using Apache|MoinMoin/InstallDocs]] +* [[mod_python Setup using Apache|MoinMoin/InstallDocs]] +* [[Setup using twisted|MoinMoin/InstallDocs]] +<a name="basic-install"></a> [[!inline pages="HelpOnInstalling/BasicInstallation" quick="yes" raw="yes"]] + +--- + + <a name="trouble-shooting"></a> + +--- + + [[!inline pages="HelpOnInstalling/TroubleShooting" quick="yes" raw="yes"]] + +--- + + <a name="unix-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/ApacheOnUnix" quick="yes" raw="yes"]] + +--- + + <a name="win32apache-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/ApacheOnWin32" quick="yes" raw="yes"]] + +--- + + <a name="win32iis-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/InternetInformationServer" quick="yes" raw="yes"]] + +--- + + <a name="macosx-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/ApacheOnMacOsx" quick="yes" raw="yes"]] + +--- + + <a name="fastcgi-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/ApacheWithFastCgi" quick="yes" raw="yes"]] + +--- + + <a name="modpy-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/ApacheWithModPython" quick="yes" raw="yes"]] + +--- + + <a name="twisted-install"></a> + +--- + + [[!inline pages="HelpOnInstalling/TwistedWeb" quick="yes" raw="yes"]] diff --git a/MoinMoin/TextFormatting.moin b/MoinMoin/TextFormatting.moin new file mode 100644 index 00000000..b767722a --- /dev/null +++ b/MoinMoin/TextFormatting.moin @@ -0,0 +1,130 @@ +##language:en
+'''Content'''
+<<TableOfContents(1)>>
+
+= Sections =
+== Header 2 ==
+=== Header 3 ===
+==== Header 4 ====
+===== Header 5 =====
+
+This page tries to use each supported markup element at least once.
+
+Normal text, ''emphasized'', '''strong''', __underline__, ,,subscript,,, ^superscript^, `typewriter` and {{{typewriter}}}.
+
+:) ;) :D {1} {de} {OK} (./)
+
+= Links =
+
+MoinMoin
+MoinMoin/TextFormatting
+MoinMoin/InstallDocs
+../InstallDocs
+/SubPage
+[[#anchorname|Anchor Link]]
+
+http://moin.sourceforge.net/
+[[http://moin.sourceforge.net/]]
+[[http://moin.sourceforge.net/|MoinMoin Sourceforge Homepage]]
+[^http://moin.sourceforge.net/ MoinMoin Sourceforge Homepage - in new window]
+[[http://moin.sourceforge.net/moinmoin.gif]]
+[[http://moin.sourceforge.net/moinmoin.gif|moinmoin.gif]]
+InterWiki
+MeatBall:InterWiki
+MeatBall:InterWiki
+MeatBall:InterWiki
+[[MeatBall:InterWiki|InterWiki page on MeatBall]]
+jh@web.de
+
+{{http://moin.sourceforge.net/moinmoin.gif}}
+
+
+= Blocks =
+
+'''Blockquote'''
+ This is indented
+ Even more
+
+'''Bullet list'''
+ * item 1
+
+ * item 2, with gap
+ * item 3
+ * item 3.1
+
+'''Numbered list'''
+ 1. item 1
+ i. item 1
+ i. item 2
+ 1. item 2
+ a. item 1
+ a. item 2
+##
+ Term:: Decription
+ Label:: Definition
+
+'''Code display'''
+ {{{
+line 1
+ indented 4 characters
+}}}
+
+'''Tables'''
+ General table layout and HTML like options
+ ||||||<tablewidth="80%">'''Heading'''||
+ ||cell 1||cell2||cell 3||
+ ||<rowspan=2> spanning rows||||<bgcolor='#E0E0FF'> spanning 2 columns||
+ ||<rowbgcolor="#FFFFE0">cell2||cell 3||
+
+ Cell width
+ || narrow ||<:99%> wide ||
+
+ Spanning rows and columns
+ ||<|2> 2 rows || row 1 ||
+ || row 2 ||
+ ||<-2> row 3 over 2 columns ||
+
+ Alignment
+ ||<(> left ||<^|3> top ||<v|3> bottom ||
+ ||<:> centered ||
+ ||<)> right ||
+
+ Colors
+ ||<#FF8080> red ||<#80FF80> green ||<#8080FF> blue ||
+
+
+'''Rules'''
+
+--- (not a rule)
+----
+-----
+------
+-------
+--------
+---------
+----------
+-------------------------------------------- (not thicker than 10)
+
+
+
+= Macros =
+
+<<Anchor(anchorname)>>
+'''<<PageCount>>''' pages
+<<RandomPage>>
+
+= Processors =
+
+'''Syntax Hilighting'''
+ {{{
+#!python
+# python code
+print code.colorize("abc", 1 + 1)
+}}}
+
+'''CSV Tables'''
+ {{{#!CSV -2
+Col1;Col2;Col3;Col4
+1;2;3;4
+a;b;c;d
+}}}
diff --git a/NVIDIAProprietaryDriver.mdwn b/NVIDIAProprietaryDriver.mdwn new file mode 100644 index 00000000..75ae9157 --- /dev/null +++ b/NVIDIAProprietaryDriver.mdwn @@ -0,0 +1,47 @@ + + +# NVIDIA Proprietary Driver + +This page describes the closed-source, proprietary driver created by nVidia themselves. See the [[nv|nv]] page for a description of the open-source driver created by Mark Vojkovich and maintained now by Aaron Plattner. + +The new proprietary driver from Nvidia is easier to install than prior versions as Nvidia has shifted to a single file for installation. They have attempted to make the setup as simple as possible with the installation script attempting to determine which kernel version you need. This has helped a lot but there are still some common problems. The best place to look for information about the Nvidia driver is [[Nvidia's website|http://www.nvidia.com/]]. + + + +--- + + + +The following is a common problem: (excerpted from Nvidia's docs) + +Q: My X server fails to start, and my Xorg log file contains the error: `"(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!"` + +A: Nothing will work if the NVIDIA kernel module doesn't function properly. If you see anything in the X log file like "(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!" then there is most likely a problem with the NVIDIA kernel module. First, you should verify that if you installed from rpm that the rpm was built specifically for the kernel you are using. You should also check that the module is loaded ('/sbin/lsmod'); if it is not loaded try loading it explicitly with 'insmod' or 'modprobe' (be sure to exit the X server before installing a new kernel module). If you receive errors about unresolved symbols, then the kernel module has most likely been built using header files for a different kernel revision than what you are running. You can explicitly control what kernel header files are used when building the NVIDIA kernel module with the --kernel-include-dir option (see `sh NVIDIA-Linux-x86-1.0-4349.run --advanced-options` for details). + +Please note that the convention for the location of kernel header files changed approximately at the time of the 2.4.0 kernel release, as did the location of kernel modules. If the kernel module fails to load properly, modprobe/insmod may be trying to load an older kernel module (assuming you've upgraded). cd'ing into the directory with the new kernel module and doing 'insmod ./nvidia.o' may help. + +Another cause may be that the /dev/nvidia* device files may be missing. To recreate this files simply run this script (as root). It assumes your users who have GUI access are in group "video"): +[[!format txt """ +for i in 0 1 2 3 4 5 6 7; do + node="/dev/nvidia$i" + rm -f $node + mknod $node c 195 $i || echo "mknod \"$node\"" + chmod 0660 $node || echo "chmod \"$node\"" + chown :video $node || echo "chown \"$node\"" +done + +node="/dev/nvidiactl" +rm -f $node +mknod $node c 195 255 || echo "mknod \"$node\"" +chmod 0666 $node || echo "chmod \"$node\"" +chown :video $node || echo "chown \"$node\"" +"""]] +Finally, the NVIDIA kernel module may print error messages indicating a problem -- to view these messages please check /var/log/messages, or wherever syslog is directed to place kernel messages. These messages are prepended with "NVRM". + + +## Some links to additional information on this driver + +* [[Nvidia's ReadMe for version 8756|ftp://download.nvidia.com/XFree86/Linux-x86/1.0-8756/README/index.html]] +* [[Nvidia's ReadMe for version 4349|ftp://download.nvidia.com/XFree86/Linux-x86/1.0-4349/README.txt]] +* [[Download Nvidia drivers for Linux, FreeBSD, and Solaris|http://www.nvidia.com/object/unix.html]] +* [[A Forum for Nvidia users|http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=13]]
\ No newline at end of file diff --git a/NewModuleGuidelines.mdwn b/NewModuleGuidelines.mdwn new file mode 100644 index 00000000..cbcd5e9a --- /dev/null +++ b/NewModuleGuidelines.mdwn @@ -0,0 +1,368 @@ + + +## New Module Guidelines + +This text was written for developers converting to modular structure during the 7.0 bootstrap. It may still be useful to people adding new modules to the tree. + +[[!toc ]] + + +## Guidelines for module components + +It is impossible to pre-specify all possible structures for every module component, so guidelines are given and should be followed whenever possible. In the next section, general guidelines are given for what should be included in all module components, general style, etc. Following that section are guidelines for the basic structure of each module and their module components. + + +### General guidelines for all module components + +All module components should have the following files: + +* ChangeLog: list of changes automatically generated from git by Makefile.am +* COPYING: the correct license for the package +* INSTALL: standard instructions for the building and installing package, automatically generated +* README: a brief description and appropriate URLs +* autogen.sh: script that invokes Autotools to build and configure the package +* configure.ac: Autoconf input file +* Makefile.am: top level Automake input file (others will be added to each subdir within the component) +* .gitignore: tells Git to ignore files that are not tracked in the package repository + +### Configuration files content guidelines + +The GNU Build System is composed of user hand written _input_ files (e.g. configure.ac, Makefile.am) from which _output_ files (e.g. configure, Makefile.in, Makefile, etc...) are generated. The former are checked-in the source tree while the latter are not. For a complete list of generated files, refer to the defaults section in the .gitignore file. + +**NOTE:** All X.Org modules are currently being revisited to follow these guidelines. +#### configure.ac + +This is a fictitious configuration to illustrate the most common statements encountered in the configure.ac file. +[[!format txt """ +# Initialize Autoconf +AC_PREREQ([x.yy]) +AC_INIT([xsample], [1.0.1], + [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg], [xsample]) +AC_CONFIG_SRCDIR([Makefile.am]) +AC_CONFIG_MACRO_DIR([m4]) +AC_CONFIG_HEADERS([config.h]) + +# Initialize Automake +AM_INIT_AUTOMAKE([foreign dist-bzip2]) +AM_MAINTAINER_MODE + +# Initialize libtool +AC_PROG_LIBTOOL + +# Require xorg-macros minimum of 1.10 for DocBook/XML +m4_ifndef([XORG_MACROS_VERSION], + [m4_fatal([must install xorg-macros 1.10 or later before running autoconf/autogen])]) +XORG_MACROS_VERSION(1.10) +XORG_DEFAULT_OPTIONS + +# Checks for programs. +AC_PROG_LN_S + +# Obtain compiler/linker options for dependencies +PKG_CHECK_MODULES(XPM, xproto x11) + +AC_CONFIG_FILES([Makefile + src/Makefile]) +AC_OUTPUT +"""]] +An explanation of some of the statements: + +**AC_PREREQ([_x.yy_])** + +This will prevent a version older than _x.yy_ of Autoconf to create the package configuration. It is set to the minimum version at which all X.Org modules will configure correctly. This can be found in the [[ModularDevelopersGuide#GNUBuildSystem|ModularDevelopersGuide]] wiki. + +**AC_INIT (package, version, [bug-report], [tarname])** + +Parameters: + +1. The package short descriptive name or the tar name which is often the source subdirectory. +1. The package version number as advised by release management. See [[X.Org and XFree86 Version Numbering Schemes.|http://www.x.org/releases/X11R7.5/doc/Versions.html/]] +1. Exactly this URL: [[https://bugs.freedesktop.org/enter_bug.cgi?product=xorg|https://bugs.freedesktop.org/enter_bug.cgi?product=xorg]] +1. The name (lower case) of the tarball. If omitted, the default value is the first parameter, lower cased by Autoconf. +**AC_CONFIG_SRCDIR([Makefile.am])** + +This statement tells Autoconf where the configuration is and provides a safety check when using --srcdir in case the directory does not exist. The filename supplied should be the one you are exists. Given all modules have Makefile.am, this filename is preferred so all modules have the same code. + +**AC_CONFIG_MACRO_DIR([m4])** + +Libtool recommends this statement and will store its macros there. Other Autotools may use this statement to find macros. If the module has created its own macros, they should be stored in git under the m4 directory. A common one is _AX_DEFINE_DIR_ from the [[Autoconf Archive.|http://www.gnu.org/software/autoconf-archive/]] + +Do not add `"ACLOCAL_AMFLAGS = -I m4"` in Makefile.am unless the module has a macro checked-in git. Aside from being useless, running the configuration will fail on a freshly cloned module as the m4 directory does not yet exists. + +**AC_CONFIG_HEADERS ([config.h])** + +This macro generates a config.h header file containing C preprocessor #define statements. Macros like AC_CHECK_HEADERS and AC_CHECK_FUNCS causes these #define statements to be created. + +Do not use the deprecated and undocumented _AC_CONFIG_HEADER_ (singular) version. + +**AM_INIT_AUTOMAKE([foreign dist-bzip2])** + +The `foreign` Automake option defines the strictness level. Xorg is not a GNU project, so their rules will not be enforced. The `dist-bzip2` option causes Automake to generate both a GNU zip and bzip2 compressed archive. + +**AM_MAINTAINER_MODE** + +This disables the _maintainer build rules_ for files that are usually distributed and that users should normally not have to update. The autogen.sh script enables them through --enable-maintainer-mode. + +**AC_PROG_LIBTOOL** + +This statement is not a program check as its name implies, it initializes the libtool library-building support services. It is sometimes preceded by `AC_DISABLE_STATIC` to prevent the creation of a static version of the library. In version 2 of libtool, this statement is more appropriately named `LT_INIT`. + +**AC_PROG_`XXX`** + +A number of program checks are performed to insure the desired program is available on the platform and invoked with the appropriate options. Most of the common tools such as `grep` and `sed` have already been checked by the compiler or by the various macros contained in `XORG_DEFAULT_OPTIONS`. + +**XORG_DEFAULT_OPTIONS** + +This macro expands into several macros and provide several build functions. Refer to the module generated aclocal.m4 file as this is subject to change. + +* XORG_CWARNFLAGS: platform adjusted compiler warning flags +* XORG_STRICT_OPTION: additional warning flags +* XORG_RELEASE_VERSION: defines variables for major, minor and patch level +* XORG_CHANGELOG: contains a makefile rule which creates the ChangeLog file from Git +* XORG_INSTALL: contains a makefile rule which provides the INSTALL file in the module root directory +* XORG_MANPAGE_SECTIONS: platform adjusted man page section number +The above macros invoke the following Autoconf macros: + +* AC_PROG_INSTALL +* AC_PROG_CC_C99 +* AC_PROG_SED +* AC_CANONICAL_HOST + +#### Makefile.am + +This is the minimum top level Makefile.am input file. It must contain targets to generate the ChangeLog and INSTALL files. It invokes the Makefile.am from the src subdirectory. The macro `XORG_DEFAULT_OPTIONS` is required in configure.ac. + + +[[!format txt """ +SUBDIRS = src + +.PHONY: ChangeLog INSTALL +INSTALL: + $(INSTALL_CMD) +ChangeLog: + $(CHANGELOG_CMD) + +dist-hook: ChangeLog INSTALL +"""]] + +#### autogen.sh + +It's role is to initiate the build of the package without the knowledge of the Autotools commands and options. It enables the _maintainer build rules_ in the package that are otherwise turned off by default. + + +#### .gitignore + +The .gitignore is part of the Git source code repository. It's role is to tell Git which file patterns to ignore (e.g *.o). Xorg has created a template with a defaults section which covers all generated files by the Autotools, complier, linker, lex, yacc, etc... Those generated file names will be ignored in all the subdirectories as well. + +What is left for you to do is to add file names or name patterns at the bottom of the file that are specific to your modules. You can have a .gitignore in subdirectories as well. + + +#### README + +The README file should contain, at a minimum, the package short descriptive name, a brief description and the X.Org project URLs. + + +[[!format txt """ + X Sample Module + +This module provides a sample for the creation and maintenance of an X Window System module. + +All questions regarding this software should be directed at the +Xorg mailing list: + + http://lists.freedesktop.org/mailman/listinfo/xorg + +Please submit bug reports to the Xorg bugzilla: + + https://bugs.freedesktop.org/enter_bug.cgi?product=xorg + +The master development code repository can be found at: + + git://anongit.freedesktop.org/git/xorg/sample/module + + http://cgit.freedesktop.org/xorg/sample/module + +For patch submission instructions, see: + + http://www.x.org/wiki/Development/Documentation/SubmittingPatches + +For more information on the git code manager, see: + + http://wiki.x.org/wiki/GitPage + +"""]] + +#### A Warning About Autotools Warnings and Suggestions + +The version of the Autotools you are currently working with is most likely to be a lot more recent than the minimum version required by X.Org. This means your version contains features that are not available on earlier versions. Autoconf may issue warnings or make suggestions, but you should not implement them if they use features unavailable in the minimum version. + +One example is the silent rules feature from Automake 1.11 which is not available in 1.10. Because is was a popular feature, a backward compatibility workaround was introduced in util-macros which made this feature a noop on 1.10. + + +### Guidelines for proto + +The proto module's directory structure is as follows: + + +[[!format txt """ + proto/x11proto + proto/compositeproto + proto/damageproto + proto/dmxproto + proto/evieproto + proto/fixesproto + ... +"""]] +Core protocol headers and protocol docs are in the X11 component. Extension protocol headers and protocol docs are put into a component named the same as the extension. + +Please note that all changes to the protocol of one of the official X.Org Foundation components must be discussed with the [[Architecture Working Group|ArchitectureWorkingGroup]] before changes are checked into the trunk. + +The basic structure of each component is as follows: + +* _extensionname_proto.h: protocol headers +* _extensionname_proto.txt: description of protocol +* _extensionname_proto.pc.in: pkg-config metadata file for use with the autotools (note that the core protocol metadata file will be named xproto.pc.in to be more descriptive and not conflict with xlib's metadata file) +* specs: the protocol specifications when available in DocBook/XML format +* plus the files listed in the general guidelines above + +### Guidelines for lib + +The lib module's directory structure is as follows: + + +[[!format txt """ + lib/libX11 + lib/libXt + lib/libXcomposite + lib/libICE + lib/libSM + lib/libdmx + ... +"""]] +Some libraries will have corresponding protocol headers that are kept in the proto module, while others will be standalone libraries. + +The basic structure of each component should be: + +* doc: any library documentation (e.g., howto's, specs, books, etc.) +* include: the library's public headers, which are placed in a subdir corresponding to where they go in the system (e.g., the Xlib headers go in `include/X11`, and the Xv headers go in `include/X11/extensions`). +* man: man pages for library +* src: source code +* specs: specification documents +* doc: other documentation +* _library-name_.pc.in: pkg-config metadata file for use with the autotools +* plus the files listed in the general guidelines above +Note that some libraries do not have any documentation or man pages, so those subdirs should not be created until they are needed. + + +### Guidelines for server + +The server module's directory structure is as follows: + + +[[!format txt """ + xserver/dix + xserver/hw + xserver/mi + xserver/os + xserver/mi + xserver/Xext + ... +"""]] +Within the xserver module, the structure is the same as found in the monolithic tree in `xc/programs/Xserver` except that the drivers are not included in this module. Instead, the drivers have been moved to the driver module (see below). + + +### Guidelines for driver + +The driver module's directory structure is as follows: + + +[[!format txt """ + driver/xf86-video-ati + driver/xf86-video-mga + driver/xf86-video-i810 + driver/xf86-input-mouse + driver/xf86-input-keyboard + driver/xf86-input-spaceorb + ... +"""]] +The name of each component is created from the DDX, driver interface, and device(s) that it supports. Currently, there is one DDX (xf86) and two driver interfaces (video and input). As other driver interfaces are developed, they should be added to the list above. + +The basic structure of each component should be: + +* doc: any driver documentation (e.g., howto's, info files, etc.) +* man: man pages for the driver +* src: source code +* util: special utilities used by the driver developers and/or users +* plus the files listed in the general guidelines above +Note that some drivers do not have any docs, man pages or utilities, so those subdirs should not be created until they are needed. Also, other directories may be necessary that contain code for examples, config tools, etc. + + +### Guidelines for app + +The app module's directory structure is as follows: + + +[[!format txt """ + app/xdpyinfo + app/xwd + app/xwud + app/twm + ... +"""]] +The name of most components will be the application name, but when not, it should be descriptive of the component contents. + +Note that it is very difficult to specify a structure for all apps since they vary greatly in complexity and organization, but when no other structure is already available, the one below could be adopted: + +* doc: any application documentation (e.g., howto's, info files, etc.) +* man: man pages for the app +* src: source code for the app +* plus the files listed in the general guidelines above + +### Guidelines for font + +The font module's directory structure is as follows: + + +[[!format txt """ + font/util + font/adobe-100dpi + font/adobe-utopia-100dpi + font/bitstream-type1 + ... +"""]] +The fonts are modularized along foundry and type boundaries, where type is 100dpi, 75dpi, misc, cyrillic, type1, ttf, etc., and the font module components are named _foundary-type_. Note that some fonts have special licenses and should be put into separate components. These separate components should be listed by _foundary-family*-type_. For example, most of the adobe foundry fonts have the same license with the exception of the utopia family fonts, so for the 100dpi adobe fonts, the ones that share the same license are placed in the `adobe-100dpi` component and the utopia fonts are placed in the `adobe-utopia-100dpi` component. + +Note that the license for the fonts in each component should be reflected in the `COPYING` file. + + +### Guidelines for doc + +The doc module's directory structure is as follows: + + +[[!format txt """ + doc/xorg-docs + doc/xorg-sgml-doctools +"""]] +A special case is the documentation that has not yet been converted to a modern format, which will be kept in the doc module until they are converted. At present, these are contained within the xorg-docs component. + + +### Guidelines for util + +The util module's directory structure is as follows: + + +[[!format txt """ + util/macros + util/modular + util/cf + util/gccmakedep + util/imake + util/lndir + util/makedepend +"""]] +This module contains the build tools for the modular tree as well as the build tools and configuration files that were used in the monolithic tree. These are kept around for legacy applications that have not yet been converted to use autotools. + +The build tools for the modular tree are contained in the `modular` component, and the m4 macros used across the entire modular build are contained in the macros component. **Important:** note that when changes are made to the m4 macros, all of the packages in the modular tree that use the macros that you changed are affected, and those packages will need to be rebuilt, have their version numbers bumped and released during the next release cycle. + +Many of the common utilities that are used mainly with imake are contained in the imake component. Others that have uses outside of imake are in their own component directories (e.g., `gccmakedep`, `lndir` and `makedepend`). diff --git a/News.mdwn b/News.mdwn new file mode 100644 index 00000000..977e499d --- /dev/null +++ b/News.mdwn @@ -0,0 +1,25 @@ + +(Listing mode: latest news first) + +* 2010-12-20: [[X11R7.6 released|Other/Press/X11R76Released]] +* 2009-10-26: [[X11R7.5 released|Other/Press/X11R75Released]] +* 2009-02-01: [[Results of Google/X.Org Summer of Code 2008|SummerOfCodeResults2008]] +* 2008-09-23: [[X11R7.4 released|Releases/7.4]] +* 2008-03-20: [[X.Org takes part in in Google Summer of Code 2008|SummerOfCodeIdeas2008]] +* 2007-09-06: [[X11R7.3 released|Releases/7.3]] +* 2007-02-15: [[X11R7.2 released|Other/Press/X11R72Released]] +* 2006-05-22: [[X11R7.1 Released|Other/Press/X11R71Released]] +* 2006-03-20: [[xorg-server 1.0.2 Released|http://lists.freedesktop.org/archives/xorg/2006-March/013993.html]] +* 2006-03-20: [[X.Org Security Advisory: privilege escalation and DoS in X11R6.9, X11R7.0|http://lists.freedesktop.org/archives/xorg/2006-March/013992.html]] +* 2005-12-21: [[X11R6.9 and X11R7.0 Released|PressReleases/X11R6970Released]] +* 2005-02-11: [[X11R6.8.2 Released|PressReleases/X11r682Released]] +* 2004-11-17: [[X.Org Foundation Security Advisory For The X Window System|ftp://ftp.x.org/pub/X11R6.8.1/patches/README.xorg-681-CAN-2004-0914.patch]] +* 2004-09-17: [[X11R6.8.1 Released|http://x.org/XOrg_Foundation_X11R6.8.1.pdf]] +* 2004-09-09: [[X11R6.8.0 Released|News200409091135]] +* 2004-05-07: [[XDevConf 2004|News200405070808]] +* 2004-04-24: [[Ongoing development moved to HEAD|News200404240744]] +* 2004-04-08: [[X.Org Foundation releases X11R6.7.0|News200404080917]] +* 2004-02-25: [[Report on platform compatibility|News20040225]] +You can find a bit more X11 related news at [[freedesktop.org's News page|http://freedesktop.org/wiki/News]]. + +You can find more detailed info on the releases at [[XorgReleases|XorgReleases]]. diff --git a/News20040225.mdwn b/News20040225.mdwn new file mode 100644 index 00000000..2f37c28d --- /dev/null +++ b/News20040225.mdwn @@ -0,0 +1,11 @@ + +The -CURRENT tree of the CVS repository is known to build on the following platforms: + +* Linux (SUSE Linux 9.0) +* Solaris 9 +* Mac OS X 10.3 +* FreeBSD 5.1R +* AIX 5.2 +More platforms are coming soon + +-- Main.[[KalebKeithly|KalebKeithly]] - 25 Feb 2004 diff --git a/News200404080917.mdwn b/News200404080917.mdwn new file mode 100644 index 00000000..2121e934 --- /dev/null +++ b/News200404080917.mdwn @@ -0,0 +1,7 @@ + + +### News heading + +The X.Org Foundation releases X11R6.7.0. + +-- Main.[[KeithPackard|KeithPackard]] - 08 Apr 2004 diff --git a/News200404240744.mdwn b/News200404240744.mdwn new file mode 100644 index 00000000..415f9f8e --- /dev/null +++ b/News200404240744.mdwn @@ -0,0 +1,11 @@ + + +## Ongoing development moved to HEAD + +On April, 23rd 2004 the development branch XORG-CURRENT was moved to the trunk of the CVS repository. If you currently have XORG-CURRENT checked out you can move the HEAD by doing: +[[!format txt """ +cvs update -A -dP +"""]] +The XORG-CURRENT branch has been declared closed. Please don't commit to XORG-CURRENT any more. If you have a branch on XORG-CURRENT and have problems merging back to the development branch (or mreging in new versions of the development branch) please ask on the [[[mailto:xorg''@''freedesktop.org|[mailto:xorg''@''freedesktop.org]][!X.Org mailing list]]. + +-- Main.[[EgbertEich|EgbertEich]] - 24 Apr 2004 diff --git a/News200405070808.mdwn b/News200405070808.mdwn new file mode 100644 index 00000000..10900114 --- /dev/null +++ b/News200405070808.mdwn @@ -0,0 +1,4 @@ + +Federico Mena-Quintero has posted <a href="[[http://primates.ximian.com/~federico/news-2004-04.html#30">his|http://primates.ximian.com/~federico/news-2004-04.html#30">his]] notes</a> of XDevConf 2004 on his web site. There are virtually no tech reporters interested in X much less ones who understand it so we have to make the most of people who care about X and who enjoy writing about it on their own web sites. X has been undergoing a true renaissance of late and can play a unique role in the future as Linux & BSD supporters begin to understand the value and advantage of using X to broadcast content to ubiquitous interactive displays which are attached to wireless networks instead of PC's. + +-- Main.[[GeneMosher|GeneMosher]] - 07 May 2004 diff --git a/News200409091135.mdwn b/News200409091135.mdwn new file mode 100644 index 00000000..6a8f5e2b --- /dev/null +++ b/News200409091135.mdwn @@ -0,0 +1,4 @@ + +[[X11R6|X11R6]].8 Released! + +-- Main.[[JimGettys|JimGettys]] - 09 Sep 2004 diff --git a/OrphanedPages.mdwn b/OrphanedPages.mdwn new file mode 100644 index 00000000..9b60b737 --- /dev/null +++ b/OrphanedPages.mdwn @@ -0,0 +1,2 @@ + +A list of pages no other page links to: [[!orphans ]] diff --git a/Other/Press.mdwn b/Other/Press.mdwn new file mode 100644 index 00000000..ad7b3f1c --- /dev/null +++ b/Other/Press.mdwn @@ -0,0 +1,12 @@ + +This page lists press releases issued by the X.Org Foundation, regarding X.Org. + +* 9th August, 2012: [[X.Org Foundation joins Open Invention Network (OIN) patent non-aggression community|Other/Press/XorgOIN]] +* 2nd August, 2012: [[Call for Proposals 2012|Other/Press/CFP2012]], [[supplement|Other/Press/CFP2012_supplemental]] +* 20th July, 2012: [[X.Org Foundation achieves non-profit public charity status|Other/Press/501c3StatusDetermination]] +* 26th October, 2009: [[X11R7.5 released|Other/Press/X11R75Released]] +* 15th February, 2007: [[X11R7.2 released|Other/Press/X11R72Released]] +* 22nd May, 2006: [[X11R7.1 released|Other/Press/X11R71Released]] +* 21st December, 2005: [[X11R6.9 & X11R7.0 Released|Other/Press/X11R6970Released]] +* 18th April, 2005: [[X Window System Test Suite Released|Other/Press/XTSReleased]] +* 9th February, 2005: [[X11R6.8.2 Released|Other/Press/X11R682Released]]
\ No newline at end of file diff --git a/Other/Press/501c3StatusDetermination.mdwn b/Other/Press/501c3StatusDetermination.mdwn new file mode 100644 index 00000000..45edac8d --- /dev/null +++ b/Other/Press/501c3StatusDetermination.mdwn @@ -0,0 +1,18 @@ + +20 JULY 2012: The X.Org Foundation is pleased to announce that the U.S. Internal Revenue Service has determined that the [[X.Org Foundation|XorgFoundation]] qualifies as a public charity under section 501(c)(3) of the U.S. Internal Revenue Code. This allows for contributions to the Foundation to be considered tax deductible for U.S. taxpayers. + +The Foundation's Board offers our deep gratitude to our legal counsel at the [[Software Freedom Law Center (SFLC)|http://www.softwarefreedom.org/]], including Karen Sandler, Justin Colannino, and Aaron Williamson, for their hard work, guidance, and assistance throughout the multi-year process of applying for this status. + +Contributions to the X.Org Foundation are used to further our mission to support the development of the open source graphics stack based on the X Window System, and to educate students and developers about the technology in the stack. The X Window System is one of the oldest Open Source software projects in the world, since its creation at MIT in 1984, and has become the standard graphical interface across Linux & Unix workstations and servers, and has been included in a number of mobile phones and tablets as well. Foundation members and contributing developers continue to enhance and maintain the existing X software base, while also researching and developing next generation open source graphics technologies such as the [[Wayland project|http://wayland.freedesktop.org]]. + +The Foundation is currently funding stipends for several students to learn about open source development, developer community participation, and the various portions of the graphics stack via [[X.Org's “Endless Vacation of Code” program|XorgEVoC]], which allows students to spend breaks between semesters participating in open source development on the graphics stack. + +Funding from the Foundation will also be used to hold the [[2012 X.Org Developer Conference|Events/XDC2012]], hosted by SUSE Linux GmbH, in Nuremberg, Germany from September 19 through 21, including helping cover travel and lodging expenses for developers and students who could not otherwise afford to attend. This year's conference will include a celebration of the 25th anniversary of the release of X11, the current core standard upon which the window system is based. + +Since its founding, the Foundation has also supported "hackfests" to gather developers together for focused meetings to advance specific areas, held a book sprint to create documentation to better educate users & developers, helped members and students travel to other open source conferences such as FOSDEM to present their work to wider audiences, and obtained access to standards documentation and technical specifications for members to use. + +Membership in the Foundation is open to those who have contributed in some way to the X Window System. Members may vote in annual elections for the Board of Directors and other questions put to the Foundation membership. Further details are available at [[Membership|Membership]]. + +Significant funding for the Foundation has come from Intel, Google, and Oracle (previously Sun Microsystems), as well as from the previous X.Org industry group that was run by The Open Group. With the determination of charitable non-profit status, we will be looking for contributions from a wider range of donors. To contribute, or for any other questions about the Foundation, please contact the [[X.Org Board of Directors|BoardOfDirectors]] at [[board@foundation.x.org|mailto:board@foundation.x.org]]. + +Public information about the Foundation and its projects may be found on the web site [[http://www.x.org/|http://www.x.org/]] - public disclosure of such documents as required by the Internal Revenue Code is at [[http://www.x.org/foundation/|http://www.x.org/foundation/]]. diff --git a/Other/Press/CFP2012.mdwn b/Other/Press/CFP2012.mdwn new file mode 100644 index 00000000..2166c0de --- /dev/null +++ b/Other/Press/CFP2012.mdwn @@ -0,0 +1,15 @@ + +# Call For Proposals **2012 X.Org Developers Conference (XDC 2012)** **19-21 September 2012** **Nürnberg (Nuremberg), Germany** + +The [2012 X.Org Developers Conference] ([[http://www.x.org/wiki/Events/XDC2012|http://www.x.org/wiki/Events/XDC2012]]) is the annual technical meeting for [X Window System]([[http://x.org|http://x.org]]) and [Free Desktop]([[http://freedesktop.org|http://freedesktop.org]]) developers. The attendees will gather to discuss outstanding technical issues related to X and to plan the direction of the X Window System and its software ecosystem. The event is free of charge and open to the general public. + +The XDC 2012 Technical Program Committee (TPC) is requesting proposals for papers and presentations at XDC 2012. While any serious proposal will be gratefully considered, topics of interest to X.org and [[FreeDesktop|FreeDesktop]].org developers are encouraged. There are three particular types of proposal the TPC is seeking: + + 1. Technical talk abstracts: 250-1000 words describing a presentation to be made at XDC 2012. This can be anything: a work-in-progress talk, a proposal for change, analysis of trends, etc. + 1. Informal white papers: 1000+ words on something of interest or relevance to X.org developers, [[FreeDesktop|FreeDesktop]].org developers or the X community at large. These papers will appear in the online conference proceedings of XDC 2012, and are unrefereed (beyond basic checks for legitimacy and relevance). Papers can be refereed if requested in advance. + 1. Technical research papers: 2500+ words in a format and style suitable for refereed technical publication. Papers that are judged acceptable by the TPC and its referees will be published in the printed conference proceedings of XDC 2012, available on a print-on-demand basis online. +XDC 2012 technical presenters will be chosen from the authors of any of these submissions (as well as other presenters invited by the TPC). + +Normally, there is time for everyone who wants to present to do so, but one can never tell. As much as possible, presenters will be selected from those who submit before the deadline. We also may be able to offer financial assistance for travel for presenters who could not otherwise afford to attend and who submit before the deadline. Please do submit your proposal in a timely fashion. + +**Proposals due:** Wednesday 15 August 2012 17:00 UTC *Accepted formats: PDF and ASCII text. **Notification of acceptance:** Monday 3 September 2012 **E-mail:** board at foundation.x.org diff --git a/Other/Press/X11R682Released.mdwn b/Other/Press/X11R682Released.mdwn new file mode 100644 index 00000000..8e8e1274 --- /dev/null +++ b/Other/Press/X11R682Released.mdwn @@ -0,0 +1,66 @@ + + +# X11R6.8.2 Officially Released + + +### X.Org Foundation Releases Update + + +### For X Window System Release X11R6.8.0 + +_Brookline Massachusetts, February 9, 2005_ The X.Org Foundation today announced the fourth release of the X Window System since the formation of the Foundation in January of 2004. + +The new X.Org release, called X Window System Version 11, Release 6.8.2 ([[X11R6|X11R6]].8.2) builds on the work of X.org [[X11R6|X11R6]].8.0 and [[X11R6|X11R6]].8.1 released in 2004. [[X11R6|X11R6]].8.2 combines the latest developments from many people and companies working with the X Window System and an open X.Org Foundation Release Team. All Official X.Org Releases are available for download from [[ftp://www.x.org/pub|ftp://www.x.org/pub]] and at mirror-sites world-wide. + + +## About this Release: + +The [[X11R6|X11R6]].8.2 release is intended to be a stable bug fix release ("Maintenance update") for the [[X11R6|X11R6]].8.0 and [[X11R6|X11R6]].8.1 X11 releases of the Xorg Foundation, containing bug fixes, security updates and a small set of new features, which include the following: + +* ATI R100 video driver +* ATI "radeon" video driver +* ATI Rage128 video driver +* CYGWIN infrastructure update +* DMX Library updates +* Intel i810 video driver +* libXpm security update (CAN-2004-0914) +* Mesa (OpenGL) update to release 6.2 +* Fixes to the pseudocolor emulation layer (currently only used by the Neomagic driver.) +* "nv" (Nvidia) video driver +* Postscript print driver +* Xprint infrastructure update +Please refer to the [[X11R6|X11R6]].8.2 Release Notes at [[http://www.x.org/|http://www.x.org/]] for further details. The full list of changes between the initial [[X11R6|X11R6]].8.0 and this release can be found in the Changelog. + + +## About participation and membership in X.Org: + +Membership in the X.Org foundation is free and open to all participants. Active participants in the further development of the X Window System are invited to visit: [[http://www.x.org/XOrg_Foundation_Membership.html|http://www.x.org/XOrg_Foundation_Membership.html]] to complete a membership application. Participation in the Foundation's Sponsor Group is also available to those who wish to financially support the activities of the X.Org Foundation. Current Sponsors include Hewlett Packard, Sun Microsystems, Hummingbird, IBM, Starnet Communications, WRQ, and Integrated Computer Solutions (ICS). + + +## About the X.Org Foundation: + +X.Org Foundation L.L.C. is a Delaware company organized to operate as a scientific charity under IRS code 501(c)(3), chartered to develop and execute effective strategies that provide worldwide stewardship of the X Window System technology and standards. The group is currently managed by its Board of Directors that includes: Stuart Anderson (Free Standards Group), Egbert Eich (Novell), Jim Gettys (HP), Stuart Kreitman (SUN Microsystems), Kevin Martin (Red Hat), Jim [[McQuillan|McQuillan]] (Linux Terminal Server Project), Keith Packard (HP), and Leon Shiman (Shiman Associates). The website for the X.Org Foundation can be found at [[http://www.x.org/|http://www.x.org/]]. + + +## About Community Participation: + +This release was built on [[X11R6|X11R6]].8.0 by the direct contributions of 66 developers, with the support of X.Org's Release Wranglers. Names of all contributors can be found in the Release Notes. + + +## About The X Window System: + +The X Window System provides the only common networked windowing environment bridging the heterogeneous platforms in today's computing. The X Window System is one of the most successful open-source, collaborative technologies developed to date and is the standard graphical window system for the Linux® and UNIX® operating systems. The inherent independence of the X Window System from the operating system, the network and the hardware, as well as its successful interoperability, have made it widely available and deployed with more than 30 million users worldwide. All major hardware vendors support the X Window System and many third parties provide technologies for integrating X Window System applications into the networked computer or personal computer environments including Microsoft Windows®, UNIX, Linux and Mac OS® X. Further, thousands of software developers provide X Window System applications, and with the continued growth of Linux and the emergence of Mac OS X, the number of users is growing rapidly. + +_Notes to Editors:_ + +(1) Distributed Multihead X Project: [[http://dmx.sourceforge.net/|http://dmx.sourceforge.net/]] + +(2) The Mesa 3D Graphics Library: [[http://www.mesa3d.org|http://www.mesa3d.org]] + +(3) The Xprint Project: [[http://xprint.mozdev.org/|http://xprint.mozdev.org/]] + +UNIX is a registered trademark of The Open Group in the US and other countries. LINUX is a registered trademark of Linus Torvalds. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. Mac OS is a registered trademark of Apple Computer, Inc., registered in the U.S. and other countries. All other company names are trademarks of the registered owners. + +For questions, please contact: Leon Shiman, Secretary, X.Org Foundation, at: + +* Shiman Associates Inc (00)1.617.277.0087 [[leon@shiman.com|mailto:leon@shiman.com]]
\ No newline at end of file diff --git a/Other/Press/X11R6970Released.mdwn b/Other/Press/X11R6970Released.mdwn new file mode 100644 index 00000000..a340f060 --- /dev/null +++ b/Other/Press/X11R6970Released.mdwn @@ -0,0 +1,20 @@ + + +# X11R6.9 and X11R7.0 Officially Released + + +### Landmark version X11R7.0 released today with X11R6.9 by the X.Org Foundation + +_Brookline, Massachusetts, December 21 2005._ The first major version release of the X Window System in more than a decade, X11R7.0 is the first release of the complete modularized and autotooled source code base for the X Window System. X11R6.9, its companion release, contains identical features, and uses the exact same source code as X11R7.0, but with the traditional imake build system. + +These changes in source code management, giving openness and transparency to the source code base and employing current technology, invite a new generation of developers to contribute, building on the long tradition of the X Window System. The new modular format offers focused development, and rapid and independent updates and distribution of tested modular components as they are ready, freed from the biennial maintenance release timetable. + +X11R6.9 comprises many distinct components bonded in a single tree, based on imake. X11R7.0 splits that set of components into logically distinct modules, separately developed, built, and maintained by the community of X.Org developers. This simulaneous release gives a transition point for developers, builders, and vendors to adapt their practices to the new X.Org modular process. X11R7.0 supports Linux and Solaris at this time, with other support pending. X11R7.1, the first modular roll-up release, is scheduled mid-2006. While the monolithic tree will continue to be fully supported and released, new feature development is expected to be concentrated in the modular code base. + +The X11R7.0 and X11R6.9 releases are the work of more than fifty volunteer contributors worldwide, working under the release management team of Kevin Martin (Head), Alan Coopersmith, and Adam Jackson, with the support of Red Hat, Sun Microsystems, and the unsupported generous contribution of effort by Adam Jackson.* + +All X Window System Releases are available from [[http://ftp.X.Org|http://ftp.X.Org]] and mirror sites worldwide (see [[http://wiki.x.org/Mirrors|http://wiki.x.org/Mirrors]]). They are distributed under the MIT ("X") License by the X.Org Foundation LLC. Information concerning organization, activities, and mailing lists can be found at [[http://www.X.Org|http://www.X.Org]]. Membership is free and open to contributors. Sponsorship is encouraged to support the global activities of the X.Org Foundation. Current X.Org Sponsors include Sun Microsystems, HP, IBM, StarNet Communications, AttachmateWRQ, Hummingbird, and Integrated Computer Solutions Incorporated [ICS].* + +In continuous use for over 20 years, the X Window System provides the only standard platform-independent networked graphical window system bridging the heterogeneous platforms in today's enterprise: from network servers to desktops, thin clients, laptops, and hand-helds, independent of operating system and hardware. + +* LINUX is a registered trademark of Linus Torvalds. "Solaris" is a tradmark of Sun Microsystems. Company names are trademarks of their registered owners. diff --git a/Other/Press/X11R71Released.mdwn b/Other/Press/X11R71Released.mdwn new file mode 100644 index 00000000..6a84c9e2 --- /dev/null +++ b/Other/Press/X11R71Released.mdwn @@ -0,0 +1,24 @@ + + +# X.Org Foundation Releases X11R7.1 + + +### First Modular Source Code Roll-up Release of the X Window System + +_Brookline, Massachusetts, May 22 2006._ Five months after release of X11R7.0, the modularized and autotooled release of the MIT ("X") Licensed X Window System source code, the X.Org Foundation has issued its first modular roll-up release. + +X11R7.1 supports Linux, Solaris, and BSD systems. It includes important new server and driver features for embedded systems, 64 bit platforms, enhanced operating system support, and accelerated indirect GLX support. It most importantly demonstrates to developers and industry immediate benefits of modularization. + +The full source code is free and available from ftp.X.Org and [[Mirrors|Mirrors]] worldwide. For a complete list of features in the new release and the contributors, please visit: [[http://ftp.x.org/pub/X11R7.1/|http://ftp.x.org/pub/X11R7.1/]]. + +The X Window System is distributed under the MIT ("X") License by the X.Org Foundation LLC. All X Window System Releases are the work of volunteer contributors. + +All X11R7.0 derivative ("modularized") releases divide the source code into logically distinct modules, separately developed, built, and maintained by the community of X.Org developers. This concentrates and accelerates development time, supporting continuous modification, testing, and publication of each module.The new modular format offers focused development, and rapid and independent updates and distribution of tested modular components as they are ready, freed from the biennial maintenance release timetable. These changes in source code management, giving openness and transparency to the source code base and employing current technology, invite a new generation of developers to contribute, building on the long tradition of the X Window System. + +Twice yearly, roll-up releases collect and publish a new reference source code version. X11R7.1 is the first of these regular releases, demonstrating the success of the new development environment. The last monolithic tree released, X11R6.9.0, will continue to be be supported with security patches, as are all past X.Org Foundation releases, while new feature development is concentrated on the X11R7.* modular code base. + +Membership is free and open to contributors. Sponsorship is encouraged to support the global activities of the X.Org Foundation. Current X.Org Sponsors include Sun Microsystems, HP, IBM, StarNet Communications, AttachmateWRQ, Hummingbird, and Integrated Computer Solutions Incorporated [ICS].* Information concerning organization, activities, and mailing lists can be found at [[http://www.X.Org|http://www.X.Org]]. + +In continuous use for over 20 years, the X Window System provides the only standard platform-independent networked graphical window system bridging the heterogeneous platforms in today's enterprise: from network servers to desktops, thin clients, laptops, embedded systems, and hand-helds, independent of operating system and hardware. + +* LINUX is a registered trademark of Linus Torvalds. "Solaris" is a trademark of Sun Microsystems. Company names are trademarks of their registered owners. diff --git a/Other/Press/X11R72Released.mdwn b/Other/Press/X11R72Released.mdwn new file mode 100644 index 00000000..2ce70e5e --- /dev/null +++ b/Other/Press/X11R72Released.mdwn @@ -0,0 +1,13 @@ + + +# X.Org community releases X11R7.2 + +_February 15, 2007._ The X.Org community is proud to announce the release of X11R7.2, the third modular release of the X Window System. + +X11R7.2 supports Linux, BSD, Solaris, Microsoft Windows and GNU Hurd systems. It incorporates significant stability and correctness fixes, including improved autoconfiguration heuristics, enhanced support for GL-based compositing managers such as Compiz and Beryl, and improved support for PCI systems with multiple domains. It also incorporates the new, more extensible XACE security policy framework. + +The full source code is free to use, modify and redistribute and is available from [[http://ftp.x.org/pub/X11R7.2/|http://ftp.x.org/pub/X11R7.2/]] and mirrors worldwide. + +For more information on the X Window System, including how to get involved with development, please see [[http://wiki.x.org|http://wiki.x.org]]. + +* Linux is a registered trademark of Linus Torvalds. Solaris is a trademark of Sun Microsystems. Windows is a trademark of Microsoft Corporation. Company names are trademarks of their registered owners. diff --git a/Other/Press/X11R75Released.mdwn b/Other/Press/X11R75Released.mdwn new file mode 100644 index 00000000..401dc28f --- /dev/null +++ b/Other/Press/X11R75Released.mdwn @@ -0,0 +1,32 @@ + +**26 October 2009** -- The [[X.Org Foundation|XorgFoundation]] and the global community of X.Org developers announce the release of [[X11R7.5 - Release 7.5 of the X Window System, Version 11|Releases/7.5]]. This release is the sixth modular release of the X Window System. The next full release will be [[X11R7.6|Releases/7.6]] and is expected in 2010. + +X11``R7.5 supports Linux, BSD, Solaris, MacOS X, Microsoft Windows and GNU Hurd systems. It incorporates new features, and stability and correctness fixes, including improved autoconfiguration heuristics, enhanced support for input devices, and new options for reconfiguring the screen geometry while the system is running. + +The full source code is free to use, modify and redistribute, under open source licenses, and is available from [[http://www.x.org/releases/X11R7.5/|http://www.x.org/releases/X11R7.5/]] and mirrors worldwide. + +For more information on the X Window System, including how to get involved with development, please see [[http://www.x.org|http://www.x.org]]. + + * +--- + + + + +## Summary of new features in X11R7.5 + +This is a sampling of the new features in X11``R7.5. A more complete list of changes can be found in the Change``Log files that are part of the source of each X module and on the [[http://www.x.org/releases/X11R7.5/|http://www.x.org/releases/X11R7.5/]] website. + +More information on the contents of X11``R7.5 and changes from previous releases can also be found in the release notes posted at: + + * [[http://www.x.org/releases/X11R7.5/doc/RELNOTES.html|http://www.x.org/releases/X11R7.5/doc/RELNOTES.html]] + * **Multi-Pointer X (MPX)** provides the user with multiple independent mouse cursors and multiple independent keyboard foci. Each cursor is a true system cursor and different pointers can operate in multiple applications simultaneously. + * **Input device properties** allow you to attach properties to a device. These properties can be of arbitrary type and can be changed without the server having to know their details. + * The **X Input Extension version 2.0 (XI2)** is designed to replace both core input processing and prior versions of the X Input Extension. Besides MPX, it provides a number of other enhancements over version 1.5, including: + * explicit device hierarchy of master and slave devices. + * the ability for devices to change capabilities at runtime. + * raw device events + * **Resize, Rotate and Reflect Extension (RANDR) version 1.3** builds on the changes made with version 1.2 and adds some new capabilities without fundmentally changing the extension again. The following features are added in this version: + * _Projective Transforms_: The implementation work for general rotation support made it trivial to add full projective transformations. These can be used to scale the screen up/down as well as perform projector keystone correct or other effects. + * _Panning_: Panning was removed with RandR 1.2 because the old semantics didn't fit any longer. With RandR 1.3 panning can be specified per crtc. + * The **DRI2** extension is designed to associate and access auxillary rendering buffers with an X drawable. It is a essentially a helper extension to support implementation of direct rendering drivers/libraries/technologies. The first consumer of this extension is a direct rendering OpenGL driver, but the DRI2 extension is not designed to be OpenGL specific. Work is underway to utilize DRI2 for the Video Decode and Presentation API for Unix (VDPAU) as well. Direct rendering implementations of OpenVG, Xv, cairo and other graphics APIs should find the functionality exposed by this extension helpful and hopefully sufficient.
\ No newline at end of file diff --git a/Other/Press/X11R76Released.mdwn b/Other/Press/X11R76Released.mdwn new file mode 100644 index 00000000..3d664250 --- /dev/null +++ b/Other/Press/X11R76Released.mdwn @@ -0,0 +1,37 @@ + +**20 December 2010** -- The [[X.Org Foundation|XorgFoundation]] and the global community of X.Org developers announce the release of [[X11R7.6 - Release 7.6 of the X Window System, Version 11|Releases/7.6]]. This release is the seventh modular release of the X Window System. The next full release will be [[X11R7.7|Releases/7.7]] and is expected in 2011. + +X11``R7.6 supports Linux, BSD, Solaris, MacOS X, Microsoft Windows and GNU Hurd systems. It incorporates new features, and stability and correctness fixes, including improved autoconfiguration heuristics, enhanced support for input devices, better documentation, and takes the next step in migrating to the [[XCB client APIs|http://xcb.freedesktop.org]]. + +The full source code is free to use, modify and redistribute, under open source licenses, and is available from [[http://www.x.org/releases/X11R7.6/|http://www.x.org/releases/X11R7.6/]] and mirrors worldwide. + +For more information on the X Window System, including how to get involved with development, please see [[http://www.x.org|http://www.x.org]]. + + * +--- + + + + +## Summary of new features in X11R7.6 + +This is a sampling of the new features in X11``R7.6. A more complete list of changes can be found in the Change``Log files that are part of the source of each X module and on the [[http://www.x.org/releases/X11R7.6/|http://www.x.org/releases/X11R7.6/]] website. + +More information on the contents of X11``R7.6 and changes from previous releases can also be found in the release notes posted at: + + * [[http://www.x.org/releases/X11R7.6/doc/xorg-docs/ReleaseNotes.html|http://www.x.org/releases/X11R7.6/doc/xorg-docs/ReleaseNotes.html]] + * **Input``Class** sections in Xorg configuration files are used to apply configuration options to any input device matching specified rules, such as device path, type of device, device manufacturer, or other data provided by the input hotplug backend. Details can be found in the INPUTCLASS section of the xorg.conf(5) manual page. + * **Xorg configuration directories** are used to allow fragments of the X server configuration to be delivered in individual files. For instance, the input device driver matching rules previously provided in HAL `.fdi` files are now provided as [[InputClass|InputClass]] sections in .conf files in a `xorg.conf.d` directory. + * **udev** is now used by the X server on Linux systems for input device discovery and hot-plug notification. Other platforms continue to use the **HAL** framework for these tasks for now. + * **X protocol C-language Binding (XCB)** is now included in the katamari, and is required by several client-side modules, including libX11, xlsatoms, xlsclients and xwininfo. XCB is a replacement for Xlib featuring a small footprint, latency hiding, direct access to the protocol, improved threading support, and extensibility. More information can be found on the XCB website at [[http://xcb.freedesktop.org/|http://xcb.freedesktop.org/]]. + * Major progress has been made on the **[[X.Org Documentation modernization|Development/Documentation/WritingDocumentation]]** - most of the library and protocol specifications are now included in the modules for those libraries and protocols so they can be updated in sync with new versions, and many have been converted to Doc``Book XML from the variety of formats they were previously in. On most systems these documents will be installed under `/usr/share/doc/`. They are also posted on the X.Org website at [[http://www.x.org/releases/X11R7.6/doc/index.html|http://www.x.org/releases/X11R7.6/doc/index.html]] +<ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins><ins></ins> + + +## Dedication + +Two of the early leaders of the X Window System community were lost to cancer this year -- **Smokey Wallace**, who led the DEC WSL team which created the initial implementation of X11, and **Hideki Hiura** from Sun Microsystems, who helped design the X11``R6 internationalization framework. The X11``R7.6 release is dedicated to their memory. + +Jim Gettys [[remembers|http://gettys.wordpress.com/2010/11/16/so-they-dont-pass-unnoticed/]] that “_Without Smokey, it is not clear that X11 would have ever existed: he and I drafted a memo that proposed developing X11 in Digital’s WSL and making the result freely available, as X11 would require more resources than we had available at MIT. This was one of the seminal moments in free and open source software, though few know of it._” + +Alan Coopersmith, who worked with Hideki at Sun, noted that “_Hideki’s contributions to the X Window System and leadership in forums such as openi18n.org will leave a lasting legacy on the millions of users who are able to use their native languages to interact with computers and portable devices running the Unix and Linux families of operating system._” diff --git a/Other/Press/XTSReleased.mdwn b/Other/Press/XTSReleased.mdwn new file mode 100644 index 00000000..ba666d63 --- /dev/null +++ b/Other/Press/XTSReleased.mdwn @@ -0,0 +1,46 @@ + + +# X Window System Test Suite + + +# Contributed by ApTest and The Open Group to The X.Org Foundation + + +# Released under "X" Open Source License. + +_Brookline Massachusetts, 18 April 2005._ + +The X.Org Foundation, global steward of the X Window System* and Standards, announced today that [[ApTest|ApTest]] and The Open Group have together donated their VSW5 Test Suite to The X.Org Foundation, where it shall be released under their standard Open Source license as XTS 5.0.2. The X Window System is released by the X.Org Foundation under the MIT ("X") License. The VSW5 Test Suite is the industry best practice in testing the X Window System. + +All Official X.Org releases are free and available for download from [[ftp://www.x.org/pub|ftp://www.x.org/pub]] and at mirror-sites world-wide. + +"[[ApTest|ApTest]] is excited by the opportunity X.Org offers the X community. We are pleased to contribute our technology and look forward to participating in ensuring the ongoing quality of X releases" said Shane [[McCarron|McCarron]], Managing Director of [[ApTest|ApTest]] Minnesota + +"The Open Group congratulates the X.Org Foundation on making the free availability of the X Window System Test Suite (VSW5) under an open source license possible and establishing a test working group" said Andrew Josey, Director of Certification at The Open Group. "This initiative will further enhance the quality of the X Window System and we look forward to working with X.Org. As part of that cooperation we plan to contribute a number of patches to the code base." + +To support the development of this critical and unique testing technology in tandem with the X Window System itself, the X.Org Foundation also announces the formation of a Testing Workgroup, to be lead by Stuart Anderson, for maintenance and extension of the test suites. Information about this workgroup can be found at [[http://www.x.org/TestGroup|http://www.x.org/TestGroup]]. Membership in all X.Org work groups is open and free. + + +## About VSW5: + +The VSW5 Test Suite is the latest in an evolutionary series of test suites for the X Window System that began in the early 1990's. The VSW Test Suite is built on the The Open Group's Test Environment Toolkit (TET) framework ([[http://tetworks.opengroup.org/|http://tetworks.opengroup.org/]]). The VSW test suite is a part of the certification program for both the UNIX system and the Linux Standard Base (LSB). The software can be downloaded from [[http://www.x.org/pub/XTS5.0.2|http://www.x.org/pub/XTS5.0.2]]. + + +## About ApTest: + +Applied Testing and Technology has provided testing analysis, design, development, and execution services to its clients since 1993. [[ApTest|ApTest]] specializes in outsourced product testing and the development of automated test suites, test tools, and test technology. We also develop and market the [[ApTest|ApTest]] Manager test management system - a web-based product for managing QA testing across the enterprise. Further information on [[ApTest|ApTest]] can be found at [[http://www.aptest.com|http://www.aptest.com]] or from Andy Silverman at 408-399-1930. + + +## About The Open Group: + +The Open Group is a specialist in the development and operation of certification programs for software specifications endorsed by industry standards bodies. The Open Group has a fifteen-year history of the provision of high quality test suites and certification related services to the software industry, and has been the active maintainer of VSW5 and X Window System certification for a number of years. Further information on The Open Group can be found at [[http://www.opengroup.org|http://www.opengroup.org]]. + +==About the X.Org Foundation: == + +X.Org Foundation L.L.C. is a Delaware company organized to operate as a scientific charity under IRS code 501(c)(3), chartered to develop and execute effective strategies that provide worldwide stewardship of the X Window System technology and standards. The group is currently managed by its Board of Directors that includes: Stuart Anderson (Free Standards Group), Egbert Eich (Novell), Jim Gettys (HP), Stuart Kreitman (SUN Microsystems), Kevin Martin (Red Hat), Jim [[McQuillan|McQuillan]] (Linux Terminal Server Project), Keith Packard (HP), and Leon Shiman (Shiman Associates). The website for the X.Org Foundation can be found at [[http://www.x.org/|http://www.x.org/]]. + +_Notes to Editors:_ + +For questions, please contact: Leon Shiman, Secretary, X.Org Foundation, at: + +* Shiman Associates Inc (00)1.617.277.0087 [[leon@shiman.com|mailto:leon@shiman.com]]
\ No newline at end of file diff --git a/Other/Press/XorgOIN.mdwn b/Other/Press/XorgOIN.mdwn new file mode 100644 index 00000000..f0c5977a --- /dev/null +++ b/Other/Press/XorgOIN.mdwn @@ -0,0 +1,32 @@ + +9 AUGUST 2012: The [[X.Org Foundation|XorgFoundation]] has joined the [[Open Invention Network (OIN)|http://www.openinventionnetwork.com/]] patent non-aggression community in order to better protect the future of the X Window System. OIN has granted the Foundation a license to use all of the patents they control or which are covered by agreements with other [[OIN community members and licensees|http://www.openinventionnetwork.com/licensees.php]], in exchange for a pledge from the Foundation to license back any patents which the Foundation may come into possession of. (Currently the Foundation owns no patents, but if we ever do, they will be covered by this agreement.) + +This will help protect the Foundation's resources and donations made to it against patent claims, allowing the Foundation to devote those resources and donations to the improvement of the window system itself. The OIN definition of the "Linux System" for which patent claims are covered by the agreement has long included X Window System software packages, and thus the X.Org Foundation receives coverage for many of 1the software packages we release. + +Due to the reciprocal nature of the OIN agreement, the Foundation can only enter to this agreement on behalf of the Foundation, as we cannot pledge anyone else's patents to the OIN community. Any vendors, distributors, or contributing organizations which wish to obtain similar protection should contact OIN directly about joining the OIN non-aggression community on their own, as described on [[http://www.openinventionnetwork.com/pat_license.php|http://www.openinventionnetwork.com/pat_license.php]]. + +In order to more broadly protect the open source desktop software systems, the X.Org Foundation is also asking our members and contributors to participate in the defensive patent programs sponsored by OIN, the Software Freedom Law Center, and the Linux Foundation, under the Linux Defenders umbrella, including Defensive Publication to establish prior art citations for new techniques, and helping the X.Org Foundation locate and publish prior art references from our archives of computer graphics and window system research and development stretching back over 25 years, through the original X Consortium back to the project's founding at MIT. Those who wish to help can learn about Defensive Publications at [[http://www.defensivepublications.org/|http://www.defensivepublications.org/]] and can contact the X.Org Foundation Board at [[board@foundation.x.org|mailto:board@foundation.x.org]] to be included in discussions about how to best utilize the X development archives. + + + +--- + + + +The X.Org Foundation is a non-profit public charity dedicated to supporting and defending the ongoing development of open source graphics and window system software, centered around the X Window System, one of the oldest and most successful open source software projects in existence. The X Window System software has become the standard graphical interface across Linux & Unix workstations and servers, and has been included in a growing number of mobile phones and tablets in recent years. More information about the X.Org Foundation and X Window System may be found at [[http://www.x.org/|http://www.x.org/]]. + + + +--- + + + +Open Invention Network® is an intellectual property company that was formed to promote Linux by using patents to create a collaborative environment. It promotes a positive, fertile ecosystem for Linux, which in turns drives innovation and choice in the global marketplace. This helps ensure the continuation of innovation that has benefited software vendors, customers, emerging markets and investors. More information about OIN is available at [[http://www.openinventionnetwork.com/|http://www.openinventionnetwork.com/]]. + + + +--- + + + +Conceptualized by Open Invention Network and co-sponsored with the Software Freedom Law Center and The Linux Foundation, Linux Defenders is a first-of- its-kind program which combines free online intellectual property (IP) publication with defensive patent tools to provide the Linux and open source community an effective vehicle to reduce future patent concerns. Linux Defenders serves as a portal for the Linux and broader open source community and seamlessly links to the Peer to Patent and Post-Issue Peer to Patent platforms that New York Law School manages. The Linux Defenders web site is located at [[http://linuxdefenders.org/|http://linuxdefenders.org/]]. diff --git a/OtherFAQs.mdwn b/OtherFAQs.mdwn new file mode 100644 index 00000000..3de705d4 --- /dev/null +++ b/OtherFAQs.mdwn @@ -0,0 +1,10 @@ + + +# Other X-related FAQs on the Internet + + * [[Remote X Apps mini-HOWTO|http://www.xs4all.nl/~zweije/xauth.html]] + * [[Multiseat X Under X11R6.9/7.0 How-To|http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html]] + * [[How-To setup A 2nd Mouse|http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/XFree86-Second-Mouse]] + * [[Direct Color FAQ|http://www.dpmms.cam.ac.uk/~werdna/XFree86-Overlay-FAQ.txt]] written by Dr. Andrew C. Aitchison + * [[Lots O' X FAQs|http://www.rahul.net/kenton/xsites.html#FAQ]] :) courtesy of Kenton Lee's site + * [[Even More FAQs|http://tldp.org/HOWTO/HOWTO-INDEX/apps.html#GUI]]
\ No newline at end of file diff --git a/PageSize.moin b/PageSize.moin new file mode 100644 index 00000000..b697fc6e --- /dev/null +++ b/PageSize.moin @@ -0,0 +1,5 @@ +##language:en
+<<StatsChart(pagesize)>>
+
+List of all pages, sorted by their size:
+<<PageSize>>
diff --git a/PauloZanoni.mdwn b/PauloZanoni.mdwn new file mode 100644 index 00000000..3a099869 --- /dev/null +++ b/PauloZanoni.mdwn @@ -0,0 +1,29 @@ + + +## Paulo Ricardo Zanoni + +[[http://www.inf.ufpr.br/prz05|http://www.inf.ufpr.br/prz05]] + +Interested in multiseat X: + +* Multiseats with MPX +* Multiseats with multiple instances of X +[[GrabsProcessing|GrabsProcessing]] + +prz05#c3sl*ufpr*br + +C3SL - Centro de Computação Científica e Software Livre + +(Center for Scientific Computing and Free Software) + +[[http://www.c3sl.ufpr.br|http://www.c3sl.ufpr.br]] + +... + + + +--- + + + +* [[CategoryHomepage|CategoryHomepage]]
\ No newline at end of file diff --git a/PciReworkHowto.mdwn b/PciReworkHowto.mdwn new file mode 100644 index 00000000..301baf5d --- /dev/null +++ b/PciReworkHowto.mdwn @@ -0,0 +1,416 @@ + + +## PCI Rework HOWTO + +Here's a list of steps you need to take to convert a video driver to the new libpciaccess library. Please feel free to fix this page where you find it inaccurate or incomplete. The examples here are from the intel driver and assume that you want to continue allowing the driver to be built with older X servers by making all of the changes conditional on whether the server uses libpciaccess. + + +### configure.ac changes + +This patch adds a check to see if the X server is using libpciaccess (the server will have XSERVER_LIBPCIACCESS defined in xorg-server.h), then makes sure the pciaccess package is installed and available. + + +[[!format txt """ + save_CFLAGS="$CFLAGS" + CFLAGS="$XORG_CFLAGS" + AC_CHECK_HEADER(xf86Modes.h,[XMODES=yes],[XMODES=no],[#include "xorg-server.h"]) ++AC_CHECK_DECL(XSERVER_LIBPCIACCESS, ++ [XSERVER_LIBPCIACCESS=yes],[XSERVER_LIBPCIACCESS=no], ++ [#include "xorg-server.h"]) + CFLAGS="$save_CFLAGS" + ++if test x$XSERVER_LIBPCIACCESS = xyes; then ++ PKG_CHECK_MODULES([PCIACCESS], [pciaccess >= 0.8.0]) ++fi ++ ++AM_CONDITIONAL(XSERVER_LIBPCIACCESS, test "x$XSERVER_LIBPCIACCESS" = xyes) + AM_CONDITIONAL(XMODES, test "x$XMODES" = xno) + + if test "x$XSERVER_SOURCE" = x; then +"""]] + + +Note: I have always encountered the xorg header files in /usr/include/xorg/, so i corrected the include. If this is not the usual location, please revert it. + + +### pciVideoPtr → struct pci_device * + +In the [[ScrnInfoRec|ScrnInfoRec]] driver private structure, there is a pointer to the pciVideoPtr structure which contains identification information about the associated PCI device. libpciaccess has a parallel structure, struct pci_device which contains the same information using different names. Another change here is to compute (and store) the PCI base address register indices in this structure; mapping PCI space now requires using these register indices instead of just the physical address of the hardware. + + +[[!format txt """ +@ -61,6 +61,11 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + #include "xf86Crtc.h" + #include "xf86RandR12.h" + ++#include "xorg-server.h" ++#ifdef XSERVER_LIBPCIACCESS ++#include <pciaccess.h> ++#endif ++ + #ifdef XF86DRI + #include "xf86drm.h" + #include "sarea.h" +@@ -360,8 +365,15 @@ typedef struct _I830Rec { + unsigned long MMIOAddr; + IOADDRESS ioBase; + EntityInfoPtr pEnt; ++#if XSERVER_LIBPCIACCESS ++ struct pci_device *PciInfo; ++ int mmio_bar; ++ int fb_bar; ++ int gtt_bar; ++#else + pciVideoPtr PciInfo; + PCITAG PciTag; ++#endif + CARD8 variant; + + unsigned int BR[20]; +"""]] + +### Macros to fetch PCI device ids + +Instead of changing the code to have conditional use of these new structures everywhere, we create macros to fetch various PCI identification data from either the old or new structures. Now, everywhere the driver used to refer to one of the old fields, just replace that using one of these macros. Placing these macros in your header file keeps the driver building against older servers. + + +[[!format txt """ +#if XSERVER_LIBPCIACCESS ++#define I810_MEMBASE(p,n) (p)->regions[(n)].base_addr ++#define VENDOR_ID(p) (p)->vendor_id ++#define DEVICE_ID(p) (p)->device_id ++#define SUBVENDOR_ID(p) (p)->subvendor_id ++#define SUBSYS_ID(p) (p)->subdevice_id ++#define CHIP_REVISION(p) (p)->revision ++#else ++#define I810_MEMBASE(p,n) (p)->memBase[n] ++#define VENDOR_ID(p) (p)->vendor ++#define DEVICE_ID(p) (p)->chipType ++#define SUBVENDOR_ID(p) (p)->subsysVendor ++#define SUBSYS_ID(p) (p)->subsysCard ++#define CHIP_REVISION(p) (p)->chipRev ++#endif +"""]] + +### DRI interface changes + +This change is simple; DRI needs to know the PCI address of the video card in several places, as these values are now stored in a new structure, the code must change to reflect the new names. + + +[[!format txt """ + } else { + pDRIInfo->busIdString = xalloc(64); + sprintf(pDRIInfo->busIdString, "PCI:%d:%d:%d", ++#if XSERVER_LIBPCIACCESS ++ ((pI810->PciInfo->domain << 8) | pI810->PciInfo->bus), ++ pI810->PciInfo->dev, pI810->PciInfo->func ++#else + ((pciConfigPtr) pI810->PciInfo->thisCard)->busnum, + ((pciConfigPtr) pI810->PciInfo->thisCard)->devnum, +- ((pciConfigPtr) pI810->PciInfo->thisCard)->funcnum); ++ ((pciConfigPtr) pI810->PciInfo->thisCard)->funcnum ++#endif ++ ); + } + pDRIInfo->ddxDriverMajorVersion = I810_MAJOR_VERSION; + pDRIInfo->ddxDriverMinorVersion = I810_MINOR_VERSION; +@@ -972,12 +978,20 @@ I810DRIScreenInit(ScreenPtr pScreen) + + if (!pI810DRI->irq) { + pI810DRI->irq = drmGetInterruptFromBusID(pI810->drmSubFD, ++#if XSERVER_LIBPCIACCESS ++ ((pI810->PciInfo->domain << 8) | ++ pI810->PciInfo->bus), ++ pI810->PciInfo->dev, ++ pI810->PciInfo->func ++#else + ((pciConfigPtr) pI810-> + PciInfo->thisCard)->busnum, + ((pciConfigPtr) pI810-> + PciInfo->thisCard)->devnum, + ((pciConfigPtr) pI810-> +- PciInfo->thisCard)->funcnum); ++ PciInfo->thisCard)->funcnum ++#endif ++ ); + if ((drmCtlInstHandler(pI810->drmSubFD, pI810DRI->irq)) != 0) { + xf86DrvMsg(pScrn->scrnIndex, X_INFO, + "[drm] failure adding irq handler, there is a device " +@@ -991,7 +1005,7 @@ I810DRIScreenInit(ScreenPtr pScreen) + xf86DrvMsg(pScrn->scrnIndex, X_INFO, + "[drm] dma control initialized, using IRQ %d\n", pI810DRI->irq); + +- pI810DRI->deviceID = pI810->PciInfo->chipType; ++ pI810DRI->deviceID = DEVICE_ID(pI810->PciInfo); + pI810DRI->width = pScrn->virtualX; + pI810DRI->height = pScrn->virtualY; + pI810DRI->mem = pScrn->videoRam * 1024; +"""]] + +### Mechanical API conversions + +Where your driver code calls various pci access functions, you need to mechanically convert them to using functions from libpciaccess +[[!table header="no" class="mointable" data=""" +Mapping built-in PCI functions to libpciaccess functions||| + Built-in | libpciaccess + xf86ReadPciBIOS | pci_device_read_rom + pciReadByte | pci_device_cfg_read_u8 + pciReadWord | pci_device_cfg_read_u16 + pciReadLong | pci_device_cfg_read_u32 +"""]] + + +### Listing the supported devices + +The device probing function will now relies on the libpciaccess code to identify all devices automatically. The match works much like the kernel; you fill in a description of which devices your driver supports and the library finds the available devices on the system. + +Here's a list of all of the devices supported by the intel driver: + + +[[!format txt """ ++#if XSERVER_LIBPCIACCESS ++ ++#define INTEL_DEVICE_MATCH(d,i) \ ++ { 0x8086, (d), PCI_MATCH_ANY, PCI_MATCH_ANY, 0, 0, (i) } ++ ++static const struct pci_id_match intel_device_match[] = { ++#ifndef I830_ONLY ++ INTEL_DEVICE_MATCH (PCI_CHIP_I810, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I810_DC100, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I810_E, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I815, 0 ), ++#endif ++ INTEL_DEVICE_MATCH (PCI_CHIP_I830_M, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_845_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I855_GM, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I865_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I915_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_E7221_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I915_GM, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I945_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I945_GM, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I945_GME, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I965_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I965_G_1, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I965_Q, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I946_GZ, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I965_GM, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_I965_GME, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_G33_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_Q35_G, 0 ), ++ INTEL_DEVICE_MATCH (PCI_CHIP_Q33_G, 0 ), ++ { 0, 0, 0 }, ++}; ++ ++#endif /* XSERVER_LIBPCIACCESS */ +"""]] + +### DriverRec changes + +The exported [[DriverRec|DriverRec]] has some new fields that refer to the above list of devices and a new libpciaccess-compatible probe function. Note that the structure places NULL for the old Probe field while listing the new probe function in the new slot. + + +[[!format txt """ +_X_EXPORT DriverRec I810 = { + I810_VERSION, + I810_DRIVER_NAME, + I810Identify, ++#if XSERVER_LIBPCIACCESS ++ NULL, ++#else + I810Probe, ++#endif + I810AvailableOptions, + NULL, +- 0 ++ 0, ++ NULL, ++#if XSERVER_LIBPCIACCESS ++ intel_device_match, ++ intel_pci_probe ++#endif + }; +"""]] + +### Registering the driver with the system + +In your setup function, you'll be adding a driver to the system. To make the server know that your [[DriverRec|DriverRec]] contains the new fields for libpciaccess, you need to pass the [[HaveDriverFuncs|HaveDriverFuncs]] flag or the server will never call your new probe function: + + +[[!format txt """ +@@ -429,7 +483,13 @@ i810Setup(pointer module, pointer opts, int *errmaj, int *errmin) + */ + if (!setupDone) { + setupDone = 1; +- xf86AddDriver(&I810, module, 0); ++ xf86AddDriver(&I810, module, ++#if XSERVER_LIBPCIACCESS ++ HaveDriverFuncs ++#else ++ 0 ++#endif ++ ); +"""]] + +### The new probe function + +The hardest part of the conversion is building a new probe function. This will replace your existing probe function when the server uses libpciaccess as the two mechanisms are incompatible. + +Here's the new intel probe function + + +[[!format txt """ +/* ++ * intel_pci_probe -- ++ * ++ * Look through the PCI bus to find cards that are intel boards. ++ * Setup the dispatch table for the rest of the driver functions. ++ * ++ */ ++static Bool intel_pci_probe (DriverPtr driver, ++ int entity_num, ++ struct pci_device *device, ++ intptr_t match_data) ++{ ++ ScrnInfoPtr scrn = NULL; ++ EntityInfoPtr entity; ++ I830EntPtr i830_ent = NULL; ++ DevUnion *private; ++ ++ scrn = xf86ConfigPciEntity (scrn, 0, entity_num, I810PciChipsets, ++ NULL, ++ NULL, NULL, NULL, NULL); ++ if (scrn != NULL) ++ { ++ scrn->driverVersion = I810_VERSION; ++ scrn->driverName = I810_DRIVER_NAME; ++ scrn->name = I810_NAME; ++ scrn->Probe = NULL; ++ ++ entity = xf86GetEntityInfo (entity_num); ++ ++ switch (DEVICE_ID(device)) { ++#ifndef I830_ONLY ++ case PCI_CHIP_I810: ++ case PCI_CHIP_I810_DC100: ++ case PCI_CHIP_I810_E: ++ case PCI_CHIP_I815: ++ scrn->PreInit = I810PreInit; ++ scrn->ScreenInit = I810ScreenInit; ++ scrn->SwitchMode = I810SwitchMode; ++ scrn->AdjustFrame = I810AdjustFrame; ++ scrn->EnterVT = I810EnterVT; ++ scrn->LeaveVT = I810LeaveVT; ++ scrn->FreeScreen = I810FreeScreen; ++ scrn->ValidMode = I810ValidMode; ++ break; ++#endif ++ case PCI_CHIP_845_G: ++ case PCI_CHIP_I865_G: ++ /* ++ * These two chips have only one pipe, and ++ * cannot do dual-head ++ */ ++ I830InitpScrn(scrn); ++ break; ++ default: ++ /* ++ * Everything else is an i830-ish dual-pipe chip ++ */ ++ xf86SetEntitySharable(entity_num); ++ ++ /* Allocate an entity private if necessary */ ++ if (I830EntityIndex < 0) ++ I830EntityIndex = xf86AllocateEntityPrivateIndex(); ++ ++ private = xf86GetEntityPrivate(scrn->entityList[0], ++ I830EntityIndex); ++ i830_ent = private->ptr; ++ if (!i830_ent) ++ { ++ private->ptr = xnfcalloc(sizeof(I830EntRec), 1); ++ i830_ent = private->ptr; ++ i830_ent->lastInstance = -1; ++ } ++ ++ /* ++ * Set the entity instance for this instance of the driver. ++ * For dual head per card, instance 0 is the "master" ++ * instance, driving the primary head, and instance 1 is ++ * the "slave". ++ */ ++ i830_ent->lastInstance++; ++ xf86SetEntityInstanceForScreen(scrn, ++ scrn->entityList[0], ++ i830_ent->lastInstance); ++ I830InitpScrn(scrn); ++ break; ++ } ++ } ++ return scrn != NULL; ++} +"""]] + +### Mapping device regions + +The final changes here affect how the driver maps bus regions into the server address space. This is a fairly mechanical change, except that the driver must know which BAR refers to each portion of the card address space. + +Here's a sample patch that maps the intel MMIO region: + + +[[!format txt """ + { + int mmioFlags; + I810Ptr pI810 = I810PTR(pScrn); ++#if XSERVER_LIBPCIACCESS ++ struct pci_device *const device = pI810->PciInfo; ++ int err; ++#endif + + #if !defined(__alpha__) + mmioFlags = VIDMEM_MMIO | VIDMEM_READSIDEEFFECT; +@@ -1211,11 +1408,23 @@ I810MapMMIO(ScrnInfoPtr pScrn) + mmioFlags = VIDMEM_MMIO | VIDMEM_READSIDEEFFECT | VIDMEM_SPARSE; + #endif + ++#if XSERVER_LIBPCIACCESS ++ err = pci_device_map_region (device, pI810->mmio_bar, TRUE); ++ if (err) ++ { ++ xf86DrvMsg (pScrn->scrnIndex, X_ERROR, ++ "Unable to map mmio BAR. %s (%d)\n", ++ strerror (err), err); ++ return FALSE; ++ } ++ pI810->MMIOBase = device->regions[pI810->mmio_bar].memory; ++#else + pI810->MMIOBase = xf86MapPciMem(pScrn->scrnIndex, mmioFlags, + pI810->PciTag, + pI810->MMIOAddr, I810_REG_SIZE); + if (!pI810->MMIOBase) + return FALSE; ++#endif + return TRUE; + } +"""]] +Unmapping requires similar changes: + + +[[!format txt """ +@ -1246,8 +1472,12 @@ I810UnmapMMIO(ScrnInfoPtr pScrn) + { + I810Ptr pI810 = I810PTR(pScrn); + ++#if XSERVER_LIBPCIACCESS ++ pci_device_unmap_region (pI810->PciInfo, pI810->mmio_bar); ++#else + xf86UnMapVidMem(pScrn->scrnIndex, (pointer) pI810->MMIOBase, + I810_REG_SIZE); ++#endif + pI810->MMIOBase = NULL; + } +"""]] + +### That's it + +The steps above are all that I found necessary to convert the intel driver; of course there are lots of other changes than the short patch excerpts here, but they're all available by looking at the intel driver git log. diff --git a/PersonalTrees.mdwn b/PersonalTrees.mdwn new file mode 100644 index 00000000..9a7e6ee9 --- /dev/null +++ b/PersonalTrees.mdwn @@ -0,0 +1,117 @@ + +This is a list of X server maintainer repositories. If you want to hack on the server, pick the most appropriate repository and branch and follow it. See the development process description on the [[XServer|XServer]] wiki page for more detail. + + +[[!format txt """ +URL: git://people.freedesktop.org/~ajax/xserver.git +MAINTAINER: Adam Jackson +DESCRIPTION: EDID, loader, Fedora, shatter, misc, other +NOTE: Branches may be non-fast-forward +BRANCHES: + - edid: EDID/DisplayID/general mode setup fixes +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~alanc/xserver.git +CGIT: http://cgit.freedesktop.org/~alanc/xserver/ +MAINTAINER: Alan Coopersmith +DESCRIPTION: Solaris & OpenSolaris port & upstreaming, general build system & dix work +NOTE: Branches may be non-fast-forward +BRANCHES: + - master: branch to be merged into xserver git master +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~daniels/xserver +CGIT: http://cgit.freedesktop.org/~daniels/xserver +MAINTAINER: Daniel Stone [daniel@fooishbar.org] +DESCRIPTION: XKB and Xi development, general patches +NOTES: Branches generally do not fast-forward +BRANCHES: + - master: general patches (mostly from the list and Bugzilla), rebased against upstream master + - misc-next: various WIP patches, rebased against master + - ge: GeneralEvents extension v1.1, rebased against master (depends on the ge branch of ~daniels/xextproto) + - xkbcommon: Port of the X server to libxkbcommon, rebased against master (depends on master of libxkbcommon) + - multitouch: Xi 2.1 multitouch support , rebased against master(depends on the multitouch branch of ~daniels/inputproto) + - input-next: Amalgamation of various input branches +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~dottedmag/xserver +CGIT: http://cgit.freedesktop.org/~dottedmag/xserver +MAINTAINER: Mikhail Gusarov <dottedmag@dottedmag.net> +DESCRIPTION: janitorial work, optimizations +BRANCHES: + - for-keithp: branch to be merged into xserver git master + - fixes: WIP fixes, often rebased +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~herrb/xserver +CGIT: http://cgit.freedesktop.org/~herrb/xserver +MAINTAINER: Matthieu Herrb <matthieu.herrb@laas.fr> +DESCRIPTION: OpenBSD patches +BRANCHES: + - master: branch with patches to be merged into xserver git master + - obsd: branch with all OpenBSD local changes tracking master + - obsd-server-1.9-branch: id. tracking server-1.9-branch + - obsd-server-1.10-branch: id. tracking server-1.10-branch +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~jcristau/xserver +CGIT: http://cgit.freedesktop.org/~jcristau/xserver +MAINTAINER: Julien Cristau +DESCRIPTION: random stuff +BRANCHES: + - libudev: udev-based input-hotplug backend +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~jeremyhu/xserver.git +CGIT: http://cgit.freedesktop.org/~jeremyhu/xserver +MAINTAINER: Jeremy Huddleston +DESCRIPTION: XQuartz development +BRANCHES: + - master: branch to be merged into xserver git master + - xorg-server-1.7-apple: Stable release branch for XQuartz based on server-1.7-branch + - xorg-server-1.6-apple: Stable release branch for XQuartz based on server-1.6-branch + - xorg-server-1.5-apple: Stable release branch for XQuartz based on server-1.5-branch + - xorg-server-1.4-apple: Stable release branch for XQuartz based on server-1.4-branch +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~mattst88/xserver.git +MAINTAINER: Matt Turner +DESCRIPTION: DEC Alpha work +BRANCHES: + - master: branch to be merged into xserver git master +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~vignatti/xserver.git +MAINTAINER: Tiago Vignatti +DESCRIPTION: General work mostly driven for embedded devices +BRANCHES: + - for-keith: branch to be merged into xserver git master +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~whot/xserver.git +MAINTAINER: Peter Hutterer +DESCRIPTION: General input work +BRANCHES: + - for-keith: branch to be merged into xserver git master (may rebase if I screw up, but should be the exception) +"""]] + +[[!format txt """ +URL: git://people.freedesktop.org/~yselkowitz/xserver.git +MAINTAINER: Yaakov (Cygwin/X) +DESCRIPTION: Cygwin/X development +NOTE: Some branches may be non-fast-forward +BRANCHES: + - cygwin: Cygwin/X experimental release branch based on master + - cygwin-release-1.8: Cygwin/X stable release branch on server-1.8-branch + - master: branch to be merged into xserver git master + - server-1.8-branch: branch to be merged into xserver git server-1.8-branch +"""]]
\ No newline at end of file diff --git a/PressReleases/X11R6970Released.mdwn b/PressReleases/X11R6970Released.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/PressReleases/X11R6970Released.mdwn diff --git a/PressReleases/X11R71Released.mdwn b/PressReleases/X11R71Released.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/PressReleases/X11R71Released.mdwn diff --git a/PressReleases/X11R72Released.mdwn b/PressReleases/X11R72Released.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/PressReleases/X11R72Released.mdwn diff --git a/PressReleases/X11r682Released.mdwn b/PressReleases/X11r682Released.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/PressReleases/X11r682Released.mdwn diff --git a/PressReleases/XtsReleased.mdwn b/PressReleases/XtsReleased.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/PressReleases/XtsReleased.mdwn diff --git a/ProgrammingDocumentation.mdwn b/ProgrammingDocumentation.mdwn new file mode 100644 index 00000000..afaa83f7 --- /dev/null +++ b/ProgrammingDocumentation.mdwn @@ -0,0 +1,25 @@ + +Most programmers who write applications for X will use third party toolkits. + +If you are interested in writing an application that uses X primitives directly without the use of a toolkit, you can use the Xlib interface, painful though it is. + +The documentation for the Xlib interface can be found here: + +* [[html version|http://www.x.org/releases/X11R7.6/doc/libX11/specs/libX11/libX11.html]] +* [[pdf version|http://www.x.org/releases/X11R7.6/doc/libX11/specs/libX11/libX11.pdf]] +* [[text version|http://www.x.org/releases/X11R7.6/doc/libX11/specs/libX11/libX11.txt]] +O'Reilly & Associates have also made freely available online some of their classic X programming manuals. These are a bit older, dating from the [[X11R3|X11R3]], R4, or R5 eras, and the toolkit ones cover Xt-based toolkits which are no longer in widespread use for new applications, but much of the Xlib documentation still applies, it just doesn't cover all the new additions: + +Xlib: + +* [[X Series Volume 2: Xlib Reference Manual (1989, covers X11R3)|http://www.archive.org/details/xlibretmanver1102nyemiss]] +* [[X Series Volume 2: Xlib Reference Manual, 2nd Edition (1990, covers X11R4)|http://www.archive.org/details/xlibrefmanv115ed02nyemiss]] +Xt & Xt-based toolkits: + +* [[X Series Volume 4: X Toolkit Intrinsics Programming Manual, 1st Edition (1990, covers X11R3)|http://www.archive.org/details/xtoolkitintrsin20400nyemiss]] +* [[X Series Volume 4: X Toolkit Intrinsics Programming Manual, 2nd Edition (1990, covers X11R4)|http://www.archive.org/details/xtoolkitintrinsi04nyemiss]] +* [[X Series Volume 4: X Toolkit Intrinsics Programming Manual, Motif Edition (1990, covers X11R4/Motif 1.1)|http://www.archive.org/details/xtoolktintrmotif04nyemiss]] +* [[X Series Volume 4: X Toolkit Intrinsics Programming Manual, 3rd Edition (1993, covers X11R5)|http://www.archive.org/details/xtoolkitintrinsic04nyemiss]] +* [[X Series Volume 5: X Toolkit Intrinsics Reference Manual (1990, covers X11R4)|http://www.archive.org/details/xtoolkitintrinsi04nyemiss]] +* [[X Series Volumes 6A & 6B: Motif Programming & Reference Manuals|http://www.oreilly.com/openbook/motif/]] +* [[X Series Volumes 7A & 7B: XView Programming & Reference Manuals|http://www.oreilly.com/openbook/openlook/]]
\ No newline at end of file diff --git a/Projects/Drivers.mdwn b/Projects/Drivers.mdwn new file mode 100644 index 00000000..a1012aba --- /dev/null +++ b/Projects/Drivers.mdwn @@ -0,0 +1,66 @@ + +Look here to check if your graphics card / chipset is supported. The pages are named like the driver modules and sorted by manufacturer. Hint: see also `man <drivername>` and `/usr/share/doc/`. + +* 3Dfx + * [[tdfx|tdfx]] - Voodoo Banshee, Voodoo3,4,5 + * [[glide|glide]] - for 2D on Voodoo1 and Voodoo2 cards (uses glide) + * [[voodoo|voodoo]] - for 2D on Voodoo1 and voodoo2 cards (glide not required) +Maintainer: Alan Cox +* [[apm|apm]] - Alliance Promotion chipset (*not* Advanced Power Managment) +* ATI + * [[ati|ati]] - ATI driver wrapper + * [[atimisc|atimisc]] - Mach8/32/64 + * [[r128|r128]] - ATI Rage 128 + * [[radeon|radeon]] - ATI Radeon +_see also [[ATIProprietaryDriver|ATIProprietaryDriver]]_ + * [[radeonhd|radeonhd]] - ATI Radeon X1000, HD1000, HD2000 series +* [[chips|chips]] - Chips and Technologies (CT64200,CT64300,CT65520,CT65525,CT65530, CT65535, CT65540, CT65545, CT65546, CT65548, CT65550, CT65554, CT65555, CT69000, CT69030) +_Maintainer:_ [[Egbert Eich|mailto:eich_at__freedesktop.org]] +* [[cirrus|cirrus]] - Cirrus Logic +* [[cyrix|cyrix]] - Cyrix MediaGX (MediaGX, MediaGXi, MediaGXm) +* [[fbdev|fbdev]] - a Framebuffer device based X server +* [[geode|geode]] (formerly _amd_) - AMD Geode +* [[glint|glint]] - 3Dlabs (GLINT, Permedia) and TI (Permedia) chips - details see link. +* [[i128|i128]] - Number Nine I128 +Maintainer: Adam Jackson +* [[imstt|imstt]] - Integrated Micro Solutions Twin Turbo 128 +* Intel + * [[i740|i740]] - Intel 740 based cards + * [[intel|intel]] (formerly _i810_) - Intel 8xx/9xx motherboards (i810, i810-dc100, i810e, i815, i830, i845, i855, i865, i915, i945, i965) +Maintainer: Intel +* [[mga|mga]] - Matrox Millennium I/II,Mystique, G100,G200,G400,G450,G550,G550 Dual-DVI +* [[neomagic|neomagic]] - Neomagic chips: MagicGraph 128, 128V, 128ZV, 128ZV+, 128XD, 256AV, 256AV+, 256ZX, 256XL+ +_Maintainer:_ [[Egbert Eich|mailto:eich_at_freedesktop.org]] +* [[newport|newport]] - SGI Indy newport cards +* [[nsc|nsc]] - National Semiconductor +* [[nv|nv]] - Nvidia RIVA 128,TNT,TNT2, GeForce, QUADRO, DCC,4, nForce, nForce2 +_see also [[NVIDIAProprietaryDriver|NVIDIAProprietaryDriver]]_ and [[nouveau|http://nouveau.freedesktop.org/]] +* [[rendition|rendition]] - Rendition (Micron) Verité chip (V1000, V2x00) +* S3 + * [[s3|s3]] - Old S3 Chipsets + * [[s3virge|s3virge]] - S3 ViRGE series (ViRGE, ViRGE DX,GX,GX2,MX,MX+,VX and Trio3D,Trio3D/2x) + * [[savage|savage]] - S3 Savage series (Savage 3D,4,2000,/MX,/IX, ProSavage PM133,KM133, Twister, TwisterK +* [[siliconmotion|siliconmotion]] - Silicon Motion, Inc. (SMI) Lynx, Lynx E/3D/EM/EM+/3DM +* [[sis|sis]] - [[SiS|SiS]] 5597/5598, 6326, 530/620, 300/305, 540, 630/730, 315/E/H/PRO, 650/651/M650/740, 661FX/M661FX/M661MX/741, 330 (Xabre), 760; and XGI Volari V3XT, V5, and V8 +_Maintainer:_ [[Thomas Winischhofer|mailto:twini_at_xfree86.org]] +* SUN + * [[sunbw2|sunbw2]] + * [[suncg14|suncg14]] + * [[suncg3|suncg3]] + * [[suncg6|suncg6]] + * [[sunffb|sunffb]] + * [[sunleo|sunleo]] + * [[suntcx|suntcx]] +* [[tga|tga]] - DEC 21030 (TGA) +* [[trident|trident]] - Trident Blade, Image, ProVidia, TGUI, ISA/VL families (details see link) +* [[tseng|tseng]] - Tseng Labs ET4000, ET4000w32, ET6000/6100 +* [[v4l|v4l]] - video4linux driver for video overlay, e.g. bt848/bt878-based TV cards +* [[vesa|vesa]] - Generic VESA video driver +* [[vga|vga]] - Standard VGA +* VIA Integrated Graphics + * [[via|via]] - VIA CLE266/KM400/![[K8M400|K8M400]] video driver + * [[openchrome|http://www.openchrome.org/]] - currently the most complete community based driver for VIA's unichrome[pro] chipsets + * [[unichrome|http://unichrome.sf.net/]] - an apparently abandoned community based driver, used as the base to openchrome + * [[VIA's own ''via'' driver|http://linux.via.com.tw/]] - now also open source, but lacks 3D and TVout support +* [[vmware|vmware]] - for running X under VMware +Maintainer: VMware
\ No newline at end of file diff --git a/Projects/XRandR.mdwn b/Projects/XRandR.mdwn new file mode 100644 index 00000000..fa944caa --- /dev/null +++ b/Projects/XRandR.mdwn @@ -0,0 +1,16 @@ + + +# RandR Documentation + +In addition to the RandR X protocol, an official configuration utility (named `xrandr`) is maintained in the [[freedesktop git repository|http://cgit.freedesktop.org/xorg/app/xrandr/]]. + +* [[Protocol specification|http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt]] +* [[RandR 1.2 overview|http://wiki.debian.org/XStrikeForce/HowToRandR12]] from Debian +* [[X Configuration|https://wiki.ubuntu.com/X/Config]] from Ubuntu +* Documentation from Intel on setting up [[dual head|http://www.intellinuxgraphics.org/dualhead.html]] configuration with RandR 1.2 +* [[XrandR 1.2 HowTo|http://www.thinkwiki.org/wiki/Xorg_RandR_1.2]] from Think``Wiki +* [[A Newbie's Guide|http://www.phoronix.com/scan.php?page=article&item=927]] from Phoronix +* A short how-to on [[writing an X.Org driver|http://wiki.x.org/wiki/DriverDevelopment]], updated to include RandR 1.2. +For Historical (only?) value: + +* The usenix [[paper|http://static.usenix.org/publications/library/proceedings/usenix01/freenix01/gettys.html]] from 2001 describing RANDR 0.91 and it's motivations.
\ No newline at end of file diff --git a/RadeonFeature.mdwn b/RadeonFeature.mdwn new file mode 100644 index 00000000..68a8e052 --- /dev/null +++ b/RadeonFeature.mdwn @@ -0,0 +1,291 @@ + +[[!toc ]] + + +## Feature Matrix for Free Radeon Drivers + +**This page is only for free Radeon drivers using KMS. + [[radeon|radeon]] (xf86-video-ati) for 2D; radeon, r200 Mesa and r300, r600, radeonsi Gallium drivers only. + THIS PAGE IS NOT FOR [[FGLRX/CATALYST|ATIProprietaryDriver]] DRIVERS PROVIDED BY AMD/ATI.** + +**See [[RadeonFeatureUMS|RadeonFeatureUMS]] for radeon in UMS.** + +**See [[radeonhd:feature|radeonhd:feature]] for radeonhd.** + +Also check out the [[RadeonProgram|RadeonProgram]], [[GalliumStatus|GalliumStatus]], and [[ATIRadeon|http://dri.freedesktop.org/wiki/ATIRadeon]] at DRI wiki. + +* "**DONE**" means that it is implemented and relatively bug-free. +* "**MOSTLY**" means that it is implemented but has some known bugs. +* "**WIP**" means that someone has started on the initial implementation. +* "**BIOS**" means only if supported by your BIOS. No software support. Yet. +* "**N/A**" means that the feature is not supported by the hardware. +* "**N/N**" means that the feature will not be implemented, because a better alternative is or will be available. +* "**TODO**" means that someone needs to write the code. The required knowledge to write the code may or may not be known. Please ask on #radeon if you want to get your feet wet on this. +* "**UNKNOWN**" means that the current status of this item isn't known. You are free to update it if you know. [[!table header="no" class="mointable" data=""" +**2D features** || | **R100** | **R200** | **R300/R400** | **R500** | **R600/700** | **Evergreen** | **N.Islands** | **S.Islands**[^1] +Kernel Modesetting || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Max Supported Displays (Eyefinity)[^2] || | 1-2 | 2 | 2 | 2 | 2 | 2-6 | 4-6 | 6 +DRI2 || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Page Flipping || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +ShadowFB || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +2D Acceleration (EXA) || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | Gallium +2D Acceleration (glamor)[^3] || | N/A | N/A | DONE | DONE | DONE | DONE | DONE | DONE +Textured Xv || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | Gallium +Video Decode (XvMC/VDPAU/VA-API) + on the 3D engine || | TODO | TODO | WIP | WIP | WIP | WIP | WIP | WIP +Video Decode (XvMC/VDPAU/VA-API) + on UVD || | N/A | N/A | N/A | N/A | DONE[^4] | DONE | DONE | DONE +Hybrid Graphics/PowerXpress/Enduro[^5] || | N/A | N/A | N/A | N/A | MOSTLY | MOSTLY | MOSTLY | MOSTLY +**Mesa 3D features** || | **R100** | **R200** | **R300/R400** | **R500** | **R600/700** | **Evergreen** | **N.Islands** | **S.Islands**[^6] +3D Driver || | radeon | r200 | r300g | r300g | r600g | r600g | r600g | radeonsi +Primitives || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Stippled Primitives || | DONE | DONE | TODO | TODO | TODO | TODO | TODO | TODO +Smooth Primitives || | DONE | DONE | TODO | TODO | TODO | TODO | TODO | TODO +Textures || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Hardware TCL || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Vertex Shaders || | N/A | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Fragment (Pixel) Shaders || | N/A | DONE | DONE | DONE | DONE | DONE | DONE | DONE +GLSL || | N/A | N/A | DONE | DONE | DONE | DONE | DONE | DONE +Color Buffer Tiling || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE[^7] +Texture Tiling || | TODO | TODO | DONE | DONE | DONE | DONE | DONE | DONE[^8] +S3TC decompression +<small>(via env variable / drirc)</small> || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE[^9] +full S3TC +<small>(via libtxc_dxtn.so)</small> || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE[^10] +Tessellation Shader Stages || | N/A | N/A | N/A | N/A | N/A | TODO | TODO | TODO +Geometry Shaders || | N/A | N/A | N/A | N/A | TODO | TODO | TODO | TODO +Anti-Aliasing (MSAA) || | N/A | N/A | MOSTLY[^11] | DONE | DONE[^12] | DONE[^13] | DONE[^14] | TODO +Anti-Aliasing (MLAA) || | N/A | N/A | N/A | [[MOSTLY|http://candgsoc.host56.com/]] | [[DONE|http://candgsoc.host56.com/]] | [[DONE|http://candgsoc.host56.com/]] | [[not tested|http://candgsoc.host56.com/]] | [[not tested|http://candgsoc.host56.com/]] +Anisotropic Filtering || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Hyper-Z || | WIP | TODO | MOSTLY[^15] | DONE | DONE | DONE | DONE | TODO +OpenGL Compliance (Driver/Hardware) || | 1.3/1.3 | 1.3/1.4 | 2.1/2.1[^16] | 2.1/2.1[^17] | 3.1/3.3[^18] | 3.1/4.2[^19] | 3.1/4.2[^20] | 2.1/4.2 +**Output** || | **R100** | **R200** | **R300/R400** | **R500** | **R600/700** | **Evergreen** | **N.Islands** | **S.Islands**[^21] +Dual-link DVI || | N/A | DONE | DONE | DONE | DONE | DONE | DONE | DONE +XRandR 1.2 || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +TV Out || | DONE | DONE | DONE | DONE | DONE | DONE | N/A | N/A +[[DisplayPort|DisplayPort]] || | N/A | N/A | N/A | N/A | DONE | DONE | DONE | DONE +HDMI Audio[^22] || | N/A | N/A | N/A | N/A | DONE | DONE[^23] | DONE[^24] | TODO +**Power Saving** || | **R100** | **R200** | **R300/R400** | **R500** | **R600/700** | **Evergreen** | **N.Islands** | **S.Islands**[^25] +Engine reclocking || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Memory reclocking || | TODO | TODO | TODO | DONE | DONE | DONE | DONE | DONE +Voltage adjusting || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +Thermal sensors || | N/A | N/A | DONE[^26] | DONE[^27] | DONE[^28] | DONE[^29] | DONE[^30] | DONE[^31] +**Other** || | **R100** | **R200** | **R300/R400** | **R500** | **R600/700** | **Evergreen** | **N.Islands** | **S.Islands**[^32] +Suspend Support || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +[[CrossFire|CrossFire]] (multi-card) || | N/A | N/A | N/A | TODO | TODO | TODO | TODO | TODO +Compute (OpenCL)[^33] || | N/A | N/A | N/A | N/A | TODO | WIP | WIP | WIP +Asynchronous DMA || | N/A | N/A | N/A | N/A | DONE | DONE | DONE | DONE +"""]] + +[^34] + + +## VSYNC + +There are several mechanisms involved in tear-free rendering due to limitations in X. + + +### 3D driver environment variable + +* vblank_mode - selects whether or not the 3D application should synchronize to vblank. + +### DDX driver options + +* [[EnablePageFlip|EnablePageFlip]] - This option enables the use of pageflipping (switching the display controller's base address pointer) rather than blits for GL buffer swaps. It only applies to fullscreen GL apps. Pageflipping is always synced to vblank at the moment. +* [[SwapBuffersWait|SwapBuffersWait]] - This option prevents tearing for GL buffer swaps by waiting to update the front buffer until scanout has passed the area of the screen the GL buffer swap is going to blit to. +* EXAVSync - This option prevents tearing for EXA operations by waiting to update the front buffer until scanout has passed the area of the screen the EXA operation is going to render to. + +### Xv Attribute + +* XV_VSYNC - This option prevents tearing when playing back videos using Xv by waiting to update the video image until scanout has passed the area of the screen displaying the video. It only prevents tearing if Xv is rendering directly to the front buffer. If you are using a compositer, this does not prevent tearing because Xv is rendering to an offscreen buffer and the compositor copied it to the front buffer. + +## KMS Power Management Options + +Kernel 2.6.35 or newer is required. The pm code supports two basic methods: + +1. "dynpm" +1. "profile" +You can select the methods via sysfs. Echo "dynpm" or "profile" to /sys/class/drm/card0/device/power_method. + +Controlling the fan speed directly is not possible (and would be very dangerous), but it can be lowered by setting lower power profile. + +The "dynpm" method dynamically changes the clocks based on the number of pending fences, so performance is ramped up when running GPU intensive apps, and ramped down when the GPU is idle. The reclocking is attemped during vertical blanking periods, but due to the timing of the reclocking functions, doesn't not always complete in the blanking period, which can lead to flicker in the display. Due to this, dynpm only works when a single head is active. + +The "profile" method exposes five profiles that can be selected from: + +1. "default" +1. "auto" +1. "low" +1. "mid" +1. "high" +Select the profile by echoing the selected profile to /sys/class/drm/card0/device/power_profile. + +* "default" uses the default clocks and does not change the power state. This is the default behavior. +* "auto" selects between "mid" and "high" power states based on the whether the system is on battery power or not. The "low" power state are selected when the monitors are in the dpms off state. +* "low" forces the gpu to be in the low power state all the time. Note that "low" can cause display problems on some laptops; this is why auto does not use "low" when displays are active. +* "mid" forces the gpu to be in the "mid" power state all the time. The "low" power state is selected when the monitors are in the dpms off state. +* "high" forces the gpu to be in the "high" power state all the time. The "low" power state is selected when the monitors are in the dpms off state. +The "profile" method is not as agressive as "dynpm," but is currently much more stable and flicker free and works with multiple heads active. + +Power management is supported on all asics (r1xx-evergreen) that include the appropriate power state tables in the vbios; not all boards do (especially older desktop cards). + +Thermal sensors are implemented via external i2c chips or via the internal thermal sensor (rv6xx-evergreen only; supported in 2.6.36 or newer); not all OEMs implement a thermal sensor. To get the temperature on asics that use i2c chips, you need to load the appropriate hwmon driver for the sensor used on your board (lm63, lm64, etc.). The drm will attempt to load the appropriate hwmon driver. On boards that use the internal thermal sensor, the drm will set up the hwmon interface automatically. When the appropriate driver is loaded, the temperatures can be accessed via lm_sensors tools or via sysfs in /sys/class/hwmon. + + +## Linux kernel parameters + +Try _modinfo -p radeon_ to find up-to-date parameters. To check default values look at _drivers/gpu/drm/radeon/radeon_drv.c_ in Linux kernel source. To check current values look at _/sys/class/drm/card*/device/driver/module/holders/radeon/parameters/*_ +[[!table header="no" class="mointable" data=""" +Option | Values | Default value<sup>1</sup> | Explanation +radeon.agpmode | 1, 2, 4, 8, -1 | 0 | AGP mode, -1 for PCI/PCIe mode +radeon.audio | 0, 1 | 0 | Disable/enable HDMI audio +radeon.benchmark | | 0 | Run benchmark +radeon.connector_table | | 0 | Force connector table +radeon.disp_priority | 0, 1, 2 | 0 | Display Priority (0 = auto, 1 = normal, 2 = high) +radeon.dynclks | 0, 1, -1 | -1 | Disable/Enable dynamic clocks, -1 for auto +radeon.gartsize | 32, 64, etc. | 512 | Size of PCIe/IGP gart to setup in megabytes +radeon.hw_i2c | 0, 1 | 0 | Disable/enable hw i2c engine +radeon.modeset | 0, 1, -1 | -1 | Disable/enable modesetting, -1 for auto +radeon.msi | 0, 1, -1 | -1 | Disable/enable MSI support, -1 for auto +radeon.no_wb | 0, 1 | | Disable/enable AGP writeback for scratch registers +radeon.pcie_gen2 | 0, 1 | -1 | Disable/enable PCIe 2.0 support, -1 for auto +radeon.r4xx_atom | 0, 1 | 0 | Disable/enable ATOMBIOS modesetting for R4xx +radeon.test | | 0 | Run tests +radeon.tv | 0, 1 | 1 | Disable/enable TV +radeon.vramlimit | 32, 64, etc. | 0 | Restrict VRAM for testing +"""]] + +<sup>1</sup> For Linux kernel 3.6 + + +## Decoder ring for engineering vs marketing names +[[!table header="no" class="mointable" data=""" +Family | Engineering Names | Marketing Names +R100 | R100, RV100, RV200, RS100, RS200 | 7xxx, 320-345 +R200 | R200, RV250, RV280, RS300 | 8xxx - 9250 +R300 | R300, R350, RV350, RV380, RS400, RS480 | 9500 - 9800, X300 - X600, X1050 - X1150, 200M +R400 | R420, R423, RV410, RS600, RS690, RS740 | X700 - X850, X12xx, 2100 +R500 | RV515, R520, RV530, RV560, RV570, R580 | X1300 - X2300, HD2300 +R600 | R600, RV610, RV630, RV620, RV635, RV670, RS780, RS880 | HD2400 - HD4290 +R700 | RV770, RV730, RV710, RV740 | HD4330 - HD5165, HD5xxV +Evergreen | CEDAR, REDWOOD, JUNIPER, CYPRESS, PALM (Wrestler), SUMO, SUMO2 | HD5430 - HD5970, all HD6000 not listed under _Northern Islands_, HD7350 +Northern Islands | ARUBA, BARTS, TURKS, CAICOS, CAYMAN | HD6450, HD6570, HD6670, HD6790 - HD6990, HD64xxM, HD67xxM, HD69xxM, HD7450 - HD7670 +Southern Islands | CAPE VERDE, PITCAIRN, TAHITI, OLAND, HAINAN | HD7750 - HD7970 +Sea Islands | BONAIRE, KABINI, KAVERI | HD7790 +"""]] + + +## Radeon 3D Hardware +[[!table header="no" class="mointable" data=""" +3D Core | Engineering Names | Shader Model | DX | OpenGL | Max Texture Size | Max Renderbuffer Size +R1xx | R100, RV100, RV200, RS100, RS200 | NA | 7 | 1.3 | 2048 | 2048 +R2xx | R200, RV250, RV280, RS300 | 1 | 8 | 1.4 | 2048 | 2048 +R3xx | R300, R350, RV350, RV380, RS400, RS480 | 2 | 9 | 2.1 | 2048 | 2560 +R4xx | R420, R423, RV410, RS600, RS690, RS740 | 2 | 9 | 2.1 | 2048 | 4021 +R5xx | RV515, R520, RV530, RV560, RV570, R580 | 3 | 9 | 2.1 | 4096 | 4096 +R6xx | R600, RV610, RV630, RV620, RV635, RV670, RS780, RS880 | 4 | 10 | 3.3 | 8192 | 8192 +R7xx | RV770, RV730, RV710, RV740 | 4 | 10 | 3.3 | 8192 | 8192 +R8xx | CEDAR, REDWOOD, JUNIPER, CYPRESS, PALM (Wrestler), SUMO, SUMO2, BARTS, TURKS, CAICOS | 5 | 11 | 4.2 | 16384 | 16384 +R9xx | CAYMAN, ARUBA | 5 | 11 | 4.2 | 16384 | 16384 +RAxx | CAPE VERDE, PITCAIRN, TAHITI, OLAND, HAINAN | 5 | 11 | 4.2 | 16384 | 16384 +RBxx | BONAIRE, KABINI, KAVERI | 5 | 11 | 4.2 | 16384 | 16384 +"""]] + + +## Radeon Display Hardware +[[!table header="no" class="mointable" data=""" +Display Core | Engineering Names | Display Controllers | DACs | TV Encoder | DVO | Digital | Notes +Classic Radeon | Rage128, R1xx-R4xx | 1-2 | 1-2 | 0-1 | 1 | 2 (1 TMDS, 1 LVDS) | +DCE1/Avivo | R5xx | 2 | 2 | 1 | 1 | 2 (1 TMDS, 1 LVDS/TMDS) | +DCE2 | R600, RV610, RV630, RV670, RS600, RS690, RS740 | 2 | 2 (R600, RV610, RV630, RV670), 1 (RS600, RS690, RS740) | 1 | 1 | 2 (1 TMDS, 1 LVDS/TMDS) | Adds HDMI 1.2 Support +DCE3 | RV620, RV635, RS780, RS880 | 2 | 2 (RV620, RV635), 1 (RS780, RS880) | 1 | 1 | 3 (LVDS/TMDS/DP) | Adds support for [[DisplayPort|DisplayPort]], HDMI 1.3 Support +DCE3.1 | RV770 | 2 | 2 | 1 | 1 | 3 (LVDS/TMDS/DP) | +DCE3.2 | RV710, RV730, RV740 | 2 | 2 | 1 | 1 | 5 (LVDS/TMDS/DP) | Adds support for up to 5 digital outputs +DCE4 | CEDAR, REDWOOD, JUNIPER, CYPRESS | 4-6 | 2 | 1 | 1 | 6 (LVDS/TMDS/DP) | Adds support for up to 6 independant displays (max of 2 non-[[DisplayPort|DisplayPort]] displays) +DCE4.1 | PALM (Wrestler), SUMO, SUMO2 | 2 | 1 (PALM), 0 (SUMO, SUMO2) | 1 | 1 | 6 (LVDS/TMDS/DP) | VGA and LVDS are implemented via DP bridge chips +DCE5 | BARTS, TURKS, CAICOS, CAYMAN | 4-6 | 1 | 0 | 1 | 6 (LVDS/TMDS/DP) | Adds improved gamma correction, HDMI 1.4 support, [[DisplayPort|DisplayPort]] 1.2 support +DCE6 | CAPE VERDE, PITCAIRN, TAHITI | 6 | 1 | 0 | 1 | 6 (LVDS/TMDS/DP) | HDMI 4K modes +DCE6.1 | ARUBA | 4 | 0 | 0 | 1 | 6 (TMDS/DP) | VGA and LVDS are implemented via DP bridge chips +DCE6.4 | OLAND | 2 | 1 | 0 | 1 | 2 (TMDS/DP) | +DCE8.1 | KAVERI | 4 | 0 | 0 | 0 | 7 (TMDS/DP) | VGA and LVDS are implemented via DP bridge chips +DCE8.2 | BONAIRE | 6 | 1 | 0 | 1 | 6 (LVDS/TMDS/DP) | +DCE8.3 | KABINI | 2 | 1 | 0 | 0 | 2 (LVDS/TMDS/DP) | +"""]] + + +## Where to get the drivers + +* Xorg radeon DDX ([[xf86-video-ati|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/]]) +* Mesa 3D driver ([[radeon, r200, r300c/g, r600c/g|http://cgit.freedesktop.org/mesa/mesa/]]) +* KMS DRM ([[Linux Kernel|http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=summary]]) +* libdrm ([[libdrm_radeon|http://cgit.freedesktop.org/mesa/drm/]]) + +## Where to file defect reports + +[[http://bugs.freedesktop.org|http://bugs.freedesktop.org]] using the following values for Product : Component... + +* Xorg radeon DDX - xorg : Driver/Radeon +* Mesa 3D driver (1xx) - Mesa : Drivers/DRI/Radeon +* Mesa 3D driver (2xx) - Mesa : Drivers/DRI/r200 +* Mesa 3D driver (3xx-5xx) - Mesa : Drivers/Gallium/r300 +* Mesa 3D driver (6xx-NI) - Mesa : Drivers/Gallium/r600 +* Mesa 3D driver (SI) - Mesa : Drivers/Gallium/radeonsi +* KMS DRM aka Kernel graphics driver - DRI : DRM/Radeon + +## Documentation + +* [[A presentation about R600 for very beginners|R600_pres_carli2.pdf]] +* [[AMD R3xx 3D Register Reference|http://www.x.org/docs/AMD/R3xx_3D_Registers.pdf]] +* [[AMD R5xx Acceleration|http://www.x.org/docs/AMD/R5xx_Acceleration_v1.5.pdf]] +* [[AMD R6xx/R7xx 3D Register Reference|http://www.x.org/docs/AMD/R6xx_3D_Registers.pdf]] +* [[AMD R6xx+ Acceleration|http://www.x.org/docs/AMD/R6xx_R7xx_3D.pdf]] +* [[AMD rv630|http://www.x.org/docs/AMD/42589_rv630_rrg_1.01o.pdf]] +* [[AMD rs690|http://www.x.org/docs/AMD/43372_rs690_rrg_3.00o.pdf]] +* [[AMD M56|http://www.x.org/docs/AMD/RRG-216M56-03oOEM.pdf]] +* [[AMD m76|http://www.x.org/docs/AMD/42590_m76_rrg_1.01o.pdf]] +* [[AMD R6xx shader ISA|http://developer.amd.com/wordpress/media/2012/10/R600_Instruction_Set_Architecture.pdf]] +* [[AMD R7xx shader ISA|http://developer.amd.com/wordpress/media/2012/10/R700-Family_Instruction_Set_Architecture.pdf]] +* [[AMD Evergreen shader ISA|http://developer.amd.com/wordpress/media/2012/10/AMD_Evergreen-Family_Instruction_Set_Architecture.pdf]] +* [[AMD Cayman/Trinity shader ISA|http://developer.amd.com/wordpress/media/2012/10/AMD_HD_6900_Series_Instruction_Set_Architecture.pdf]] +* [[AMD OpenCL and Compute Resources|http://developer.amd.com/tools/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/documentation/]] +* [[AMD Developer Guides (RS780/RS880, SB7xx, etc.)|http://developer.amd.com/resources/documentation-articles/developer-guides-manuals/]] +* [[AMD Southern Islands Series ISA|http://developer.amd.com/wordpress/media/2012/12/AMD_Southern_Islands_Instruction_Set_Architecture.pdf]] + +## Links + +* [[Wikipedia AMD GPUs|http://en.wikipedia.org/wiki/Ati_gpu]] + +[^1] Kernel 3.4 required +[^2] Depends on the OEM board. Max of 2 non-Displayport displays. +[^3] Requires a 3D driver with shader support +[^4] DONE for R7xx, TODO for R6xx +[^5] There are two versions of hybrd graphics: MUXed and MUX-less. MUXed have a display MUX to switch the displays between the discrete and integrated cards. MUXed systems can be switched using vgaswitcheroo. MUX-less do not have a display MUX and the displays are only connected to the integrated card. On MUX-less systems, the discrete card is solely for rendering, not display. X Server 1.14 is required to support rendering and display from different cards. Most new laptops (2011+) are MUX-less. +[^6] Kernel 3.4 required +[^7] Kernel 3.10 required +[^8] Kernel 3.10 required +[^9] Kernel 3.10 required +[^10] Kernel 3.10 required +[^11] Needs piglit testing before enabling by default, see mesa commit 8ed6b1400 +[^12] Kernel 3.6 required +[^13] Kernel 3.6 required +[^14] Kernel 3.6 required +[^15] Needs piglit and Lightsmark testing before enabling by default, see mesa commit 12dcbd595 +[^16] Hardware doesn't support ARB NPOT textures fully. +[^17] Hardware doesn't support ARB NPOT textures fully. +[^18] Kernel 3.6 and xserver 1.13 required +[^19] Kernel 3.6 and xserver 1.13 required +[^20] Kernel 3.6 and xserver 1.13 required +[^21] Kernel 3.4 required +[^22] Requires loading radeon with the audio parameter set to 1 (e.g., add radeon.audio=1 on the kernel command line in grub). +[^23] Kernel 3.3 required +[^24] Kernel 3.5 required +[^25] Kernel 3.4 required +[^26] i2c chip +[^27] i2c chip +[^28] i2c chip or internal sensor +[^29] i2c chip or internal sensor +[^30] i2c chip or internal sensor +[^31] i2c chip or internal sensor +[^32] Kernel 3.4 required +[^33] See http://dri.freedesktop.org/wiki/GalliumCompute +[^34] None diff --git a/RadeonFeature/R600_pres_carli2.pdf b/RadeonFeature/R600_pres_carli2.pdf Binary files differnew file mode 100644 index 00000000..07da91c3 --- /dev/null +++ b/RadeonFeature/R600_pres_carli2.pdf diff --git a/RadeonFeatureUMS.mdwn b/RadeonFeatureUMS.mdwn new file mode 100644 index 00000000..c3400df2 --- /dev/null +++ b/RadeonFeatureUMS.mdwn @@ -0,0 +1,52 @@ + + +## Feature Matrix for Free Radeon Drivers + +**This page is only for free Radeon drivers. [[radeon|radeon]] (xf86-video-ati) for 2D; radeon, r200, r300, r600 Mesa and r300, r600 Gallium drivers only. THIS PAGE IS NOT FOR [[FGLRX/CATALYST|ATIProprietaryDriver]] DRIVERS PROVIDED BY AMD/ATI.** + +**See [[RadeonFeature|RadeonFeature]] For KMS** + +**See [[radeonhd:feature|radeonhd:feature]] for radeonhd.** + +Also check out the [[RadeonProgram|RadeonProgram]], [[GalliumStatus|GalliumStatus]], and [[ATIRadeon|http://dri.freedesktop.org/wiki/ATIRadeon]] at DRI wiki. + + * "**DONE**" means that it is implemented and relatively bug-free. + * "**MOSTLY**" means that it is implemented but has some known bugs. + * "**WIP**" means that someone has started on the initial implementation. + * "**BIOS**" means only if supported by your BIOS. No software support. Yet. + * "**N/A**" means that the feature is not supported by the hardware. + * "**N/N**" means that the feature will not be implemented, because a better alternative is or will be available. + * "**TODO**" means that someone needs to write the code. The required knowledge to write the code may or may not be known. Please ask on #radeon if you want to get your feet wet on this. + * "**UNKNOWN**" means that the current status of this item isn't known. You are free to update it if you know. [[!table header="no" class="mointable" data=""" + **2D features** || | **R100** | **R200** | **R300** | **R400** | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + DDX (X server) Modesetting || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | MOSTLY + Console restore || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | TODO + DRI || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | N/N + ShadowFB || | N/N | N/N | N/N | N/N | N/N | N/N | DONE | DONE | DONE + Old 2D Acceleration (XAA) || | DONE | DONE | DONE | DONE | DONE | DONE | N/N | N/N | N/N + 2D Acceleration (EXA) || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | N/N + Overlay Xv || | DONE | DONE | DONE | DONE | N/N | N/N | N/N | N/N | N/N + Textured Xv || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | N/N + Video Decode (XvMC/VDPAU/VA-API) using the 3D engine || | TODO | TODO | TODO | TODO | TODO | TODO | TODO | TODO | TODO + Video Decode (XvMC/VDPAU/VA-API) using UVD || | N/A | N/A | N/A | N/A | N/A | N/A | TODO | TODO | TODO + **Mesa 3D features** || | **R100** | **R200** | **R300** | **R400** | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + Primitives || | DONE | DONE | DONE | DONE | DONE | DONE | MOSTLY | MOSTLY | N/N + Textures || | DONE | DONE | DONE | DONE | DONE | DONE | MOSTLY | MOSTLY | N/N + Hardware TCL || | DONE | DONE | DONE | DONE | N/A | DONE | MOSTLY | MOSTLY | N/N + Vertex Shaders || | N/A | DONE | DONE | DONE | N/A | DONE | MOSTLY | MOSTLY | N/N + Fragment (Pixel) Shaders || | N/A | DONE | DONE | DONE | DONE | DONE | MOSTLY | MOSTLY | N/N + GLSL || | N/A | N/A | WIP | WIP | WIP | WIP | MOSTLY | MOSTLY | N/N + Antialiasing || | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN + OpenGL Compliance (Driver/Hardware) || | 1.3/1.3 | 1.3/1.4 | 1.5/2.0<sup>1</sup> | 1.5/2.0<sup>1</sup> | 1.5/2.0<sup>1</sup> | 1.5/2.0<sup>1</sup> | 2.0/3.3 | 2.0/3.3 | N/N/4.0 + **Output** || | **R100** | **R200** | **R300** | **R400** | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + Dual-link DVI || | N/A | BIOS | BIOS | DONE | DONE | DONE | DONE | DONE | DONE + XRandR 1.2 || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE + TV Out || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE + [[DisplayPort|DisplayPort]] || | N/A | N/A | N/A | N/A | N/A | N/A | DONE | DONE | DONE + HDMI Audio || | N/A | N/A | N/A | N/A | TODO | N/A | TODO | TODO | TODO + **Other** || | **R100** | **R200** | **R300** | **R400** | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + Power Saving (Powerplay) || | MOSTLY | MOSTLY | MOSTLY | MOSTLY | MOSTLY | MOSTLY | MOSTLY | MOSTLY | MOSTLY + Suspend Support || | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE | DONE +"""]] + +<sup>1</sup> Hardware doesn't support ARB NPOT textures fully. diff --git a/RadeonProgram.mdwn b/RadeonProgram.mdwn new file mode 100644 index 00000000..703bc321 --- /dev/null +++ b/RadeonProgram.mdwn @@ -0,0 +1,283 @@ + + +## Supported Program List for Free Radeon Drivers + +**This page is only for the open source Xorg Radeon drivers. [[radeon|radeon]] (xf86-video-ati) for 2D; radeon, r200 Mesa Classic drivers and r300, r600 Gallium drivers only. THIS PAGE IS NOT FOR THE CLOSED-SOURCE [[FGLRX/CATALYST|ATIProprietaryDriver]] DRIVER PROVIDED BY AMD/ATI.** + +Also check out the [[RadeonFeature|RadeonFeature]] page. + +This list works on the same principle as the Wine game list, but there are some important differences. + +The biggest difference is that we are tracking driver capabilities, not performance. It doesn't matter if your game runs at 1680x1050 with everything cranked up, what matters is whether or not it is rendering properly. + +The entries in the table are "**STATUS (N.M)**", where **N.M** is the latest version / stable branch of Mesa on which the application was tested, and **STATUS** is one of the following (you can copy color codes from here): +[[!table header="no" class="mointable" data=""" +PLATINUM (N.M) | it works without any graphical bugs or problems, with all features enabled (no footnote is needed) +G0LD (N.M) | it works well, but not every little eye-candy feature works. For some chipsets, this might be due to hardware limitations. Please add a footnote why it is not PLATINUM (preferably with a link to a reported bug at freedesktop.org) +SILVER (N.M) | it works, but has serious graphical errors. For some chipsets, this might be due to hardware limitations. Please add a footnote why it is not G0LD (preferably with a link to a reported bug at freedesktop.org) +GARBAGE (N.M) | it just doesn't work, due to driver problems. Please add a footnote why it is not SILVER (preferably with a link to a reported bug at freedesktop.org) +TOO OLD | it just doesn't work at all, due to known hardware limitations. +UNKNOWN | the current status of this item isn't known. Please update it if you know. +"""]] + +Note that the level of support for R300-R500 is roughly on the same level because those chips all use the same driver. This means that if the status is known for e.g. R300, then it is likely that the status for R500 is the same or at least similar, but please refrain from changing this in the table unless you really did test the application using that chip. A similar thing is true for R600-R700. + +Here are some guidelines for this page: + +* We do not distinguish between different versions of a stable branch of Mesa. So Mesa 7.n, 7.n.1, 7.n.2, etc. all count as 7.n. +* If this page claims that an application works in Mesa 7.n, and you tested it using stable Mesa release 7.(n+1) and it still works, please update the table accordingly. +* If this page claims that an application works in Mesa 7.n, but you experience problems in stable Mesa release 7.(n+1), please notify the developers before changing the table. If we do not fix the problem within a reasonable time frame, feel free to change the corresponding entry in the table. +* If this page claims that an application fails in Mesa 7.n, but you have tested it using stable Mesa release 7.(n+1) and it works fine, please update the table accordingly. +* If the page makes claim about how well an application works in Mesa 7.n and you disagree about it, please discuss it in the community (see information on the [[Radeon 3D portal page|http://dri.freedesktop.org/wiki/Radeon]]). +* _Note on bugs:_ please prefers opening a [[new bug on freedesktop bugzilla|https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa]] and link it here rather than reporting directly the bug here. +* When experiencing issues on Apple hardware, refer to [[mac-how.net|http://www.mac-how.net]] +* Mesa version numbers do not apply to **UNKNOWN** or **TOO OLD** +* _Development (git) versions:_ When running Mesa from a git checkout, use the following format for version numbering: **X.Y-dev**. You can obtain the version number by running **glxinfo | grep version** and examining the OpenGL version string; it will say something like "1.5 Mesa 7.7-devel". +* The classic DRI drivers have been obsoleted by the newer Gallium3D ones, r300g is the default for r300-r500 since 7.9 and r600g for r600- since 7.10. Add no more test results with the classic drivers for these chips, please. +* When adding a footnote, please qualify it with the time it was written, so that we may in the future more easily decide whether the footnote is out of date. +* _Comments and changelogs:_ When editing this page, **please add** an explanatory note to the Comment field! We need to know what changed and why with a quick glance, to keep up with the driver progress. +* an <sup>S3</sup> after the name of the program indicates that it won't work at all without S3TC support (libtxc_dxtn.so) [[!table header="no" class="mointable" data=""" +**Native** | **R100** | **R200** | **R300** | **R400** | **RS690** | **R500** | **R600** | **R700** | **Evergreen** | **Northern Islands** +[[0 A.D.|http://www.wildfiregames.com/0ad/]]<sup>S3</sup> | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.11<sup>G</sup>)<sup>1</sup> | G0LD (7.9)<sup>32</sup> | PLATINUM (8.0) | UNKNOWN | PLATINUM (7.11) +[[Alien Arena 2011|http://red.planetarena.org/index.html]] | UNKNOWN | UNKNOWN | G0LD (7.11-dev)<sup>76</sup> | G0LD (7.6) | UNKNOWN | G0LD (7.6) | PLATINUM (7.11-dev) | PLATINUM (7.11) | UNKNOWN | PLATINUM (7.11) +[[Amnesia: The Dark Descent|http://www.amnesiagame.com/#main]]<sup>S3</sup> | UNKNOWN | UNKNOWN | UNKNOWN | SILVER (7.9)<sup>66</sup> | UNKNOWN | SILVER (7.10) | PLATINUM (7.11-dev) | PLATINUM (7.12-dev)<sup>3</sup> | UNKNOWN | UNKNOWN +[[AndYetItMoves|http://www.andyetitmoves.net/]] | UNKNOWN | UNKNOWN | PLATINUM (8.0) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Aquaria|http://www.bit-blot.com/aquaria/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.8) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Assault Cube|http://assault.cubers.net/]] | UNKNOWN | G0LD (7.5)<sup>15</sup> | UNKNOWN | PLATINUM (7.6) | UNKNOWN | PLATINUM (7.6) | G0LD (8.04)<sup>44</sup> | G0LD (7.9)<sup>44</sup> | UNKNOWN | UNKNOWN +[[AstroMenace|http://www.viewizard.com/]] | UNKNOWN | G0LD (7.11-dev)<sup>75</sup> | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (8.04)<sup>63</sup> | G0LD (7.9)<sup>63</sup> | UNKNOWN | UNKNOWN +[[Battle of Wesnoth|http://wesnoth.org/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | UNKNOWN | UNKNOWN | UNKNOWN +[[Blender3d|http://www.blender.org/]] | UNKNOWN | UNKNOWN | G0LD (7.6)<sup>18</sup> | G0LD (7.6) | UNKNOWN | GARBAGE (7.6)<sup>23</sup> | SILVER (7.7)<sup>18</sup> | G0LD (7.10) | PLATINUM (7.12-dev) | UNKNOWN +[[Blocks that matter|http://www.swingswingsubmarine.com/games/blocks-that-matter/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | UNKNOWN | UNKNOWN | UNKNOWN +[[Braid|http://www.braid-game.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11-dev) | UNKNOWN | PLATINUM (7.12-dev) | PLATINUM (8.1-dev) +[[Caster|http://www.elecorn.com/caster3d/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | SILVER (7.7)<sup>51</sup> | PLATINUM (7.11-dev) | UNKNOWN | UNKNOWN | UNKNOWN +[[Celestia|http://www.shatters.net/celestia/]] | UNKNOWN | UNKNOWN | PLATINUM (7.11) | UNKNOWN | UNKNOWN | G0LD (7.6) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | PLATINUM (7.11) +[[Cogs|http://www.cogsgame.com/]] | UNKNOWN | UNKNOWN | G0LD (8.0)<sup>100</sup> | UNKNOWN | UNKNOWN | UNKNOWN | GARBAGE (8.04)<sup>102</sup> | UNKNOWN | PLATINUM (7.12-dev) | UNKNOWN +[[ColdWar|http://www.linuxgamepublishing.com/info.php?id=24]] | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | UNKNOWN | UNKNOWN | GARBAGE (8.04)<sup>89</sup> | UNKNOWN | UNKNOWN | UNKNOWN +[[Compiz Fusion|http://www.compiz-fusion.org/]] | UNKNOWN | G0LD (7.5) | PLATINUM (7.5) | PLATINUM (7.6) | PLATINUM (7.5) | PLATINUM (7.7) | PLATINUM (7.10) | PLATINUM (7.10) | UNKNOWN | PLATINUM (7.11) +[[CoreBreach|http://corebreach.corecode.at/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | GOLD (7.11)<sup>96</sup> | UNKNOWN | UNKNOWN | UNKNOWN +[[Darwinia|http://www.introversion.co.uk/darwinia]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | PLATINUM (7.11) | UNKNOWN | UNKNOWN +[[Doom 3|http://zerowing.idsoftware.com/linux/doom/]]<sup>78</sup> <sup>81</sup> | UNKNOWN | G0LD (7.5) | PLATINUM (7.11-dev) | GARBAGE (7.5) | UNKNOWN | UNKNOWN | PLATINUM (7.11-dev) | PLATINUM (7.11-dev) | UNKNOWN | PLATINUM (7.11) +[[Eduke32|http://eduke32.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.10) | UNKNOWN | UNKNOWN | UNKNOWN +[[Enemy Territory: Quake Wars|http://zerowing.idsoftware.com/linux/etqw/]]<sup>S3</sup> <sup>78</sup> <sup>85</sup> | TOO OLD | TOO OLD | PLATINUM (7.10) | GARBAGE (7.5) | UNKNOWN | UNKNOWN | G0LD (7.11-dev) | PLATINUM (8.0) | UNKNOWN | PLATINUM (7.11) +[[ePSXe|http://www.epsxe.com/]] | UNKNOWN | UNKNOWN | PLATINUM (7.5) | UNKNOWN | UNKNOWN | G0LD (7.5) | G0LD (7.9) | G0LD (7.9) | UNKNOWN | UNKNOWN +[[Eschalon: Book I|http://basiliskgames.com/downloads]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.8)<sup>48</sup> | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Family Farm|http://www.familyfarmgame.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (8.04)<sup>103</sup> | PLATINUM (7.11) | UNKNOWN | UNKNOWN +[[FlightGear v2.0.0|http://www.flightgear.org/]] | UNKNOWN | UNKNOWN | G0LD (7.10)<sup>84</sup> | UNKNOWN | UNKNOWN | UNKNOWN | SILVER (7.8-dev)<sup>37</sup> | G0LD (7.10) | UNKNOWN | PLATINUM (7.11) +[[FooBillard|http://foobillard.sourceforge.net/]] | UNKNOWN | UNKNOWN | PLATINUM (7.12-dev)<sup>77</sup> | PLATINUM (7.9) | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | PLATINUM (7.11) +[[Frets On Fire|http://fretsonfire.sourceforge.net/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9)<sup>62</sup> | PLATINUM (7.9)<sup>62</sup> | UNKNOWN | UNKNOWN +[[Google Earth|http://earth.google.com/]] | UNKNOWN | G0LD (7.5) | PLATINUM (7.10) | G0LD (7.5) | G0LD (7.5) | PLATINUM (7.11<sup>G</sup>) | G0LD (7.9)<sup>56</sup> | G0LD (7.9)<sup>56</sup> | PLATINUM<sup>56</sup> (7.12-dev) | PLATINUM (7.11) +[[Gish|http://www.chroniclogic.com/gish.htm]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.8) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Glest|http://www.glest.org]] | UNKNOWN | UNKNOWN | PLATINUM (7.11) | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.9)<sup>46</sup> | G0LD (7.9)<sup>46</sup> | UNKNOWN | UNKNOWN +[[Hedgewars|http://www.hedgewars.org/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Heroes of Newerth|http://www.heroesofnewerth.com/]] | TOO OLD | TOO OLD | G0LD (8.0)<sup>101</sup> | UNKNOWN | UNKNOWN | G0LD (7.10) | G0LD (7.10) | G0LD (7.10) | UNKNOWN | UNKNOWN +[[KWin|http://techbase.kde.org/Projects/KWin]] | UNKNOWN | PLATINUM (7.9-dev) <sup>28</sup> | PLATINUM (7.10) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9)<sup>59</sup> | PLATINUM (7.10) | UNKNOWN | PLATINUM (8.1-dev) +[[Lightsmark 2008|http://dee.cz/lightsmark/]] | UNKNOWN | UNKNOWN | SILVER (7.11-dev)<sup>79</sup> | UNKNOWN | UNKNOWN | SILVER (7.10) | PLATINUM (7.11-dev) | PLATINUM (7.11-dev) | UNKNOWN | PLATINUM (7.11) +[[Lightspark|http://launchpad.net/lightspark]] | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN +[[Lugaru HD|http://www.wolfire.com/lugaru]] | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | UNKNOWN | G0LD (7.8) | PLATINUM (7.11-dev) | PLATINUM (7.11-dev) | PLATINUM (7.12-dev) | UNKNOWN +[[MegaGlest|http://megaglest.org/]] | UNKNOWN | UNKNOWN | PLATINUM (7.11) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | UNKNOWN | UNKNOWN | UNKNOWN +[[Mupen64Plus|http://code.google.com/p/mupen64plus/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.9) | G0LD (7.9) | UNKNOWN | UNKNOWN +[[Neverball|http://neverball.org/]] | UNKNOWN | PLATINUM (7.5) | PLATINUM (7.5) | PLATINUM (7.5) | PLATINUM (7.5) | PLATINUM (7.7) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | PLATINUM (7.10) +[[Neverwinter Nights|http://icculus.org/~ravage/nwn/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | UNKNOWN | UNKNOWN | UNKNOWN +[[Nexuiz|http://www.alientrap.org/nexuiz/]] | PLATINUM (7.6) | PLATINUM (7.6) | G0LD (7.10)<sup>80</sup> | G0LD (7.5) | G0LD (7.5) | PLATINUM (7.7) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.10) | PLATINUM (7.10) +[[OilRush|http://www.oilrush-game.com/]] | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | UNKNOWN | UNKNOWN | G0LD (7.11-dev) | UNKNOWN | SILVER (8.0.3)<sup>99</sup> +[[OpenArena|http://www.openarena.ws/]] ([[ioquake3|http://ioquake3.org/]]) | PLATINUM (7.6) | PLATINUM (7.6) | PLATINUM (7.5) | PLATINUM (7.5) | SILVER (7.5) | PLATINUM (7.7) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.12-dev) | PLATINUM (7.10) +[[OpenBVE|http://openbve.trainsimcentral.co.uk/]] | UNKNOWN | PLATINUM (7.9-dev) | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Osmos|http://www.hemispheregames.com/osmos/]] | UNKNOWN | UNKNOWN | PLATINUM (8.0) | UNKNOWN | UNKNOWN | PLATINUM (7.8) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.11) | PLATINUM (8.03) +[[Penumbra Collection|http://www.penumbragame.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | UNKNOWN | G0LD (7.8)<sup>55</sup> | G0LD (7.11-dev) | PLATINUM (7.11-dev) | UNKNOWN | UNKNOWN +[[Piglit|http://people.freedesktop.org/~nh/piglit/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN +[[PlaneShift|http://www.planeshift.it/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.10) | UNKNOWN | UNKNOWN +[[Postal 2|http://www.postal2.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.9) | PLATINUM (7.11) | UNKNOWN | UNKNOWN +[[Prey|http://icculus.org/prey/]]<sup>S3</sup> <sup>78</sup> <sup>81</sup> | UNKNOWN | G0LD (7.5) | PLATINUM (7.11-dev) | UNKNOWN | UNKNOWN | PLATINUM (7.11<sup>G</sup>) | G0LD (7.8) | PLATINUM (7.11-dev) | UNKNOWN | PLATINUM (7.11) +[[Racer|http://www.racer.nl/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.9)<sup>47</sup> | G0LD (7.9)<sup>47</sup> | UNKNOWN | UNKNOWN +[[Quake Live|http://www.quakelive.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Quake 4|http://zerowing.idsoftware.com/linux/quake4/]]<sup>78</sup> <sup>81</sup> | UNKNOWN | G0LD (7.5) | PLATINUM (7.11-dev) | GARBAGE (7.5) | UNKNOWN | GARBAGE (7.7) | PLATINUM (7.11-dev) | PLATINUM (7.11-dev) | PLATINUM (7.11-dev) | PLATINUM (7.11) +[[Regnum Online|http://www.regnumonlinegame.com/index.php?l=0&sec=6]]<sup>S3</sup> | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.12)<sup>98</sup> | G0LD (7.12)<sup>98</sup> | G0LD (7.12)<sup>98</sup> | G0LD (7.12)<sup>98</sup> | UNKNOWN | UNKNOWN +[[Return To Castle Wolfenstein|http://zerowing.idsoftware.com/linux/wolf/]] | UNKNOWN | PLATINUM (7.6) | UNKNOWN | PLATINUM (7.6) | UNKNOWN | PLATINUM (7.6) | PLATINUM (8.04) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[rRootage|http://rrootage.sourceforge.net/]] | UNKNOWN | PLATINUM (7.11-dev) | PLATINUM (7.5) | PLATINUM (7.5) | UNKNOWN | PLATINUM (7.5) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Ryzom|http://www.ryzom.com/en/index.html]] | UNKNOWN | UNKNOWN | SILVER (7.9)<sup>65</sup> | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.9)<sup>65</sup> | UNKNOWN | UNKNOWN +[[Savage: The Battle For Newerth|http://www.s2games.com/savage/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | SILVER (8.0.4)<sup>107</sup> | G0LD (7.10) | UNKNOWN | UNKNOWN +[[Savage 2: A Tortured Soul|http://www.savage2.com/]] | TOO OLD | TOO OLD | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | GARBAGE (8.04)<sup>108</sup> | G0LD (7.10) | UNKNOWN | PLATINUM (7.11-dev) +[[Sauerbraten|http://sauerbraten.org/]] | UNKNOWN | G0LD (7.5) | PLATINUM (7.10) | G0LD (7.5) | G0LD (7.5) | PLATINUM (7.11<sup>G</sup>) | G0LD (7.9)<sup>49</sup> | PLATINUM (7.11-dev)<sup>49</sup> | UNKNOWN | PLATINUM (7.11) +[[Scorched 3D|http://www.scorched3d.co.uk/]] | UNKNOWN | UNKNOWN | PLATINUM (7.6.1) | UNKNOWN | UNKNOWN | PLATINUM (7.10) | G0LD (7.11)<sup>57</sup> | G0LD (7.10) | UNKNOWN | G0LD (8.03) +[[Second Life|http://www.secondlife.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.5) | SILVER (7.7) | UNKNOWN | UNKNOWN | UNKNOWN +[[Secret Maryo Chronicles|http://www.secretmaryo.org/]] | UNKNOWN | PLATINUM (7.5) | SILVER (7.5) | PLATINUM (7.6) | UNKNOWN | PLATINUM (7.7) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Shadowgrounds|http://shadowgroundsgame.com/]]<sup>S3</sup> | UNKNOWN | UNKNOWN | PLATINUM (7.12-dev)<sup>92</sup> | UNKNOWN | UNKNOWN | UNKNOWN | GARBAGE (8.04)<sup>105</sup> | PLATINUM (7.11-dev) | G0LD<sup>91</sup> (7.12-dev) | UNKNOWN +[[Shadowgrounds: Survivor|http://shadowgroundsgame.com/survivor/]]<sup>S3</sup> | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | GARBAGE (8.04)<sup>105</sup> | PLATINUM (7.11-dev) | G0LD<sup>91</sup> (7.12-dev) | UNKNOWN +[[Shank|http://www.shankgame.com/]]<sup>S3</sup> | TOO OLD | TOO OLD | TOO OLD | TOO OLD | UNKNOWN | UNKNOWN | GARBAGE (8.04)<sup>106</sup> | PLATINUM (8.0-rc2) | UNKNOWN | UNKNOWN +[[Shogo: Mobile Armor Division|http://www.hyperion-entertainment.com/index.php?option=com_content&view=article&id=51&Itemid=57]] | PLATINUM (7.6) | PLATINUM (7.6) | PLATINUM (7.6) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Smokin' Guns|http://www.smokin-guns.net/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (8.04)<sup>104</sup> | G0LD (7.10) | UNKNOWN | UNKNOWN +[[Soldier of Fortune|http://www.lokigames.com/products/sof/]] | UNKNOWN | PLATINUM (7.6) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.6) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Spring RTS|http://springrts.com/]] [[(mod: CA)|http://springrts.com/wiki/Complete_Annihilation]] | UNKNOWN | UNKNOWN | SILVER (7.5) | UNKNOWN | UNKNOWN | SILVER (7.7) | SILVER (7.9)<sup>58</sup> | SILVER (7.9)<sup>58</sup> | UNKNOWN | UNKNOWN +[[Stellarium|http://www.stellarium.org/]] | UNKNOWN | G0LD (7.10) | G0LD (7.5) | UNKNOWN | G0LD (7.5) | PLATINUM (7.5) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.10) | UNKNOWN +[[Steel Storm: Burning Retribution|http://one.steel-storm.com/]] | UNKNOWN | UNKNOWN | PLATINUM (8.0) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | PLATINUM (7.11) | UNKNOWN | UNKNOWN +[[SuperTuxKart|http://supertuxkart.sourceforge.net/]] | PLATINUM (7.6) | PLATINUM (7.6) | PLATINUM (7.5) | UNKNOWN | UNKNOWN | PLATINUM (7.7) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.12-dev) | UNKNOWN +Team Fortress 2 Beta | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (9.0) +[[Teeworlds|http://www.teeworlds.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11<sup>G</sup>) | GARBAGE (7.12-dev) | UNKNOWN +[[Tiny & Big in: Grandpa's Leftovers|http://tinyandbig.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11-dev) | UNKNOWN | UNKNOWN | UNKNOWN +[[TORCS|http://torcs.sourceforge.net/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11<sup>G</sup>) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Transfusion|http://www.transfusion-game.com/]] | UNKNOWN | PLATINUM (7.6) | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Tremulous|http://tremulous.net/]] | UNKNOWN | UNKNOWN | PLATINUM (7.6) | UNKNOWN | G0LD (7.5) | PLATINUM (7.6) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.12-dev) | UNKNOWN +[[Trine|http://trine-thegame.com/site//]]<sup>S3</sup> | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | GARBAGE (8.04) | PLATINUM (7.11-dev) | PLATINUM (7.12-dev) | UNKNOWN +[[Trine 2|http://trine2.com/site/]]<sup>S3</sup> | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | UNKNOWN | PLATINUM (7.11) | UNKNOWN | UNKNOWN +[[True Combat: Elite|http://www.truecombatelite.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[UFO:AI|http://ufoai.ninex.info/wiki/index.php/News]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | G0LD (7.9) | UNKNOWN | UNKNOWN +[[Unigine: Sanctuary 2.3|http://www.unigine.com/products/sanctuary/]] | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | SILVER (7.9-dev)<sup>50</sup> | SILVER (7.11-dev) | SILVER (7.10) | UNKNOWN | PLATINUM (8.1-dev) +[[Unigine: Tropics 1.3|http://unigine.com/products/tropics/]] | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | UNKNOWN | SILVER (7.11-dev) | SILVER (7.11-dev) | UNKNOWN | PLATINUM (7.11) +[[Unigine: Heaven 2.5|http://unigine.com/products/heaven/]] | TOO OLD | TOO OLD | TOO OLD | TOO OLD | TOO OLD | UNKNOWN | GARBAGE (7.9)<sup>64</sup> | GOLD (7.12-dev)<sup>35</sup> | UNKNOWN | G0LD (7.11)<sup>95</sup> +[[Unknown Horizons|http://www.unknown-horizons.org/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11) | PLATINUM (7.11<sup>G</sup>) | UNKNOWN | UNKNOWN +[[Unreal Tournament 2004|http://www.unrealtournament2003.com/ut2004/]]<sup>82</sup> | G0LD (7.6) | G0LD (7.6) | PLATINUM (7.10) | G0LD (7.5) | UNKNOWN | G0LD (7.6) | PLATINUM (7.9)<sup>31</sup> | PLATINUM (7.9)<sup>31</sup> | PLATINUM (7.10) | PLATINUM (7.11) +[[Urban Terror|http://www.urbanterror.net]] | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.10) | UNKNOWN | PLATINUM (7.6) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.12-dev) | UNKNOWN +[[Warsow|http://www.warsow.net/]] | UNKNOWN | UNKNOWN | PLATINUM (7.10) | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | PLATINUM (7.11-dev) | PLATINUM (7.10) | UNKNOWN +[[Warzone 2100|http://wz2100.net/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (8.04) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[Wolfenstein:Enemy Territory|http://www.planetwolfenstein.com/enemyterritory/]] | PLATINUM (7.5) | PLATINUM (7.5) | PLATINUM (7.5) | PLATINUM (7.5) | UNKNOWN | PLATINUM (7.5) | PLATINUM (8.04) | PLATINUM (7.9)<sup>61</sup> | PLATINUM (7.9) | UNKNOWN +[[World of Goo|http://2dboy.com/games.php]] | UNKNOWN | PLATINUM (7.5) | PLATINUM (7.5) | UNKNOWN | PLATINUM (7.5) | PLATINUM (7.8) | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.11) | UNKNOWN +[[World of Padman|http://www.worldofpadman.com]] | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.10) | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | UNKNOWN +[[XBMC|http://www.xbmc.org]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.9) | PLATINUM (7.9) | PLATINUM (7.10) | PLATINUM (7.11) +[[Yo Frankie!|http://www.yofrankie.org/]] | UNKNOWN | UNKNOWN | G0LD (7.10)<sup>83</sup> | UNKNOWN | UNKNOWN | PLATINUM (7.6) | PLATINUM (7.9) | PLATINUM (7.9) | UNKNOWN | PLATINUM (7.11) +[[Vendetta Online|http://www.vendetta-online.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.9-dev) | UNKNOWN | PLATINUM (7.10) | UNKNOWN | UNKNOWN +"""]] + +Please verify that the application/game is marked as Platinum in [[Wine AppDB|http://appdb.winehq.org/]] before adding it here. +[[!table header="no" class="mointable" data=""" +**Wine** | **R100** | **R200** | **R300** | **R400** | **RS690** | **R500** | **R600** | **R700** | **Evergreen** | **Northern Islands** +[[Crysis 2|www.ea.com/pl/crysis2]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | SILVER (7.12-dev)<sup>90</sup> | UNKNOWN | UNKNOWN +[[EVE Online:Incursion|http://www.eve-online.com]]<sup>S3</sup> | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.11-dev)<sup>87</sup> | UNKNOWN | UNKNOWN +[[Max and the Magic Marker|http://http://maxandthemagicmarker.com//]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11-dev) | UNKNOWN | UNKNOWN | UNKNOWN +[[Max Payne|http://http://www.maxpayne.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11) | UNKNOWN | UNKNOWN +[[Multi Theft Auto|http://www.mtasa.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11-dev) | UNKNOWN | UNKNOWN +[[Perpetuum|http://www.perpetuum-online.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.11-dev)<sup>86</sup> | UNKNOWN | UNKNOWN +[[Portal 2|http://www.thinkwithportals.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.12-dev)<sup>93</sup> | UNKNOWN | UNKNOWN +[[Team Fortress 2|http://www.teamfortress.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.10) | UNKNOWN | UNKNOWN +[[World of Warcraft:Cataclysm|http://us.battle.net/wow]]<sup>S3</sup> | UNKNOWN | UNKNOWN | SILVER (7.9)<sup>29</sup> | UNKNOWN | GARBAGE (7.5) | SILVER (7.5) | PLATINUM (7.12)² | SILVER (7.10) | UNKNOWN | UNKNOWN +[[Victoria 2|http://www.victoria2.com/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | PLATINUM (7.11) +[[CivCity: Rome|http://www.2kgames.com/civcityrome/]] | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | G0LD (7.11)<sup>97</sup> +"""]] + + +### Game notes + +<sup>1</sup> Game minimap is corrupted ([[bug #36762|https://bugs.freedesktop.org/show_bug.cgi?id=36762]]). + +² S3TC support is needed. + +<sup>3</sup> (19 September 2011) All graphics features work except antialiasing, to enable advanced post process shaders like SSAO you have to compile mesa with --enable-texture-float. + +<sup>15</sup> Rendering is good on rV280; water reflection need to be turned off due performance reason (just like as in other Cube engine games) + +<sup>18</sup> (Blender) 2.49 requires low impact fallbacks to draw all interface symbols (looped stipple lines for lamp types, etc), but that affects speed. 2.50 requiries changing triple buffer mode to something else, or unusable (app problem, it seems to happen with other brands and operating systems too). + +<sup>23</sup> (26 Oct 2009) [mesa-git] Crashes on many operations and does not update it's interface correctly. + +<sup>28</sup> (14 Set 2010) Works perfectly [ATI Radeon 9000 AGP], just a bit slow due to hardware limitations. + +<sup>31</sup> (13 Dec 2009) Turn off s3tc in driconf, runs smooth in 1280x960 on a Radeon HD 4670. OpenGL renderer string: Mesa DRI R600 (RV730 9490) 20090101 x86/MMX+/3DNow!+/SSE2 TCL DRI2. Turn off s3tc in driconf, runs smooth in 1920x1200 on a 4670, all s3tc textures broken (white terrain, half the units), turn off advanced unit shading to fix menu and smoke corruption, water shader works and looks awesome. (tested with GPLed Complete Annihilation.) + +<sup>32</sup> (19 November 2010) It needs S3TC to show textures properly by default but it can be disabled. + +<sup>34</sup> (22 Jan 2010) Minor clipping issues, but totally playable. + +<sup>35</sup> (19 September 2011) Graphics look great but performance isn't so good, antialiasing doesn't work, the benchmark requires --enable-texture-float to be enabled in mesa compilation. [[Video/description|http://www.youtube.com/watch?v=Z9oLZwmO0L8]]. + +<sup>37</sup> (14 Mar 2010) Slow (4 Fps), if "Material shaders" and "3D Clouds" are enabled; if eye-candy is disabled fps of ~15-20 on a RV 635 Mobility (KMS enabled) + +<sup>43</sup> (09 May 2010) Works fine in 1440x900 with detail : high; blood : on (low detail); Blur Effects : disabled; Decals : disabled. + +<sup>44</sup> (09 May 2010) Anti-Aliasing not supported. + +<sup>46</sup> (09 May 2010) With Shadow Mapping the game is too slow to be playable, though it should works as there is GL_ARB_shadow_ambient support. + +<sup>47</sup> (28 November 2010) Racer runs fine, but i couldn't change the graphics settings since it crashes everytime i click it in options, so i could not say if it is platinum material. + +<sup>48</sup> (19 May 2010) The game is too slow to be playable and scaling is not correctly supported with a 1440*900 native screen and the game in 800*600. + +<sup>49</sup> (19 September 2011) Everything works except antialiasing. [[Video/description|http://www.youtube.com/watch?v=l6cyPrSXDNc]]. + +<sup>50</sup> (26 June 2010) Lots of warnings in terminal about incomplete attachements, and some problems with the interface, but it runs + +<sup>51</sup> (30 June 2010) Motion Blur and Glow are too slow. Water Reflection leads to graphical glitches. With these three effects disabled, there is still some graphical glitches. + +<sup>55</sup> (14 October 2010) Medium shaders cause lighting to flash. High shaders seem to leave awesome fresnel shadows. + +<sup>56</sup> (18 November 2010) Works fine except texture compression and antialiasing. + +* (6 August 2011) (Evergreen, 7.12-dev) Works fine except for antialiasing. Haven't visually confirmed anisotropic filtering works. Texture compression works with libtxc_dxtn. +<sup>57</sup> (18 November 2010) Runs fine but if you turn on all details and/or up your resolution a bit it is slow/unplayable on my HD3870 GDDR4. Shouldn't happen. + +* (30 October 2011) Runs slow on HD3450 with Normal settings. +<sup>58</sup> (18 November 2010) It seems to work fine, the major problem is the lack of S3TC compression support, i suppose when this support is implemented this would be a G0LD or PLATINUM. + +<sup>61</sup> (19 November 2010) It is ok, if only a little slow. Needs S3TC by default but this can be disabled. + +<sup>62</sup> (19 November 2010) It runs really good. In its settings Antialiasing x4 is selected by default, although it doesn't work yet. Doesn't affect anything. + +<sup>63</sup> (19 November 2010) It runs fine and relatively fast. Cannot enable all quality settings, most notably antialiazing and for some reason shading language, although it should be supported. + +<sup>64</sup> (19 November 2010) It crushes because: required extension GL_ARB_map_buffer_range is not supported. This benchmark needs OpenGL 3.x support. + +<sup>65</sup> (06 December 2010) The interface to create the avatar works well, but game need unsupported texture (probably S3TC) if graphics are set too high : Works well with "Normal" setting on R700, work correctly with "Low" settings on R300 (too slow to play if set better). + +<sup>66</sup> (07 January 2011 ) Tested on Fedora 14 i686 with r300g, mesa-7.9 20101219 snapshot. Game is a little bit slow with native resolution (1280x800), but works ok with 800x600. Still have some weird artifacts on some levels, other than that game is playable. + +<sup>75</sup> (23 April 2011) Works nicely, except that it's a bit slow even at low settings. + +<sup>76</sup> (23 April 2011) Normal maps, dynamic lights and some other effects result in blackness (also on windows) + +<sup>77</sup> (23 April 2011) Line stipple of the crosshairs is not supported by Mesa, but it's no big deal + +<sup>78</sup> (23 April 2011) If it refuses to start, because libGL.so cannot be opened, try removing libgcc_s.so and libstdc++.so.5 from the game's directory + +<sup>79</sup> (7 May 2011) Some fragment programs run out of hw temporaries (results in complete blackness), but most of the test seem OK, might be HW limitation (TOO OLD?) + +<sup>80</sup> (23 April 2011) Offset mapping is full black (Too many texture indirections) (How can it be PLATINUM on r100-r200???) + +<sup>81</sup> (23 April 2011) It seems to set very low texture size limits on unknown GPUs, have to edit its config manually (set image_*Limit to 1024, image_downSize* to 0) + +<sup>82</sup> (23 April 2011) Setting UseVBO=True in ut2004.ini adds substantial performance increase on Mesa, but it misrenders the sky, the foliage and some lightmaps. It is False by default, because it is a known bug of the game. + +<sup>83</sup> (24 April 2011) None of the shaders compile (Ran out of hardware temporaries, Too many ALU instructions), with disabled shaders it runs fine, but looks horrible + +<sup>84</sup> (24 April 2011) Material shaders cannot be enabled (tons of these on stderr: r300: ERROR: FS input generic 17 unassigned, not enough hardware slots. r300: ERROR: FS input FACE unassigned.), otherwise playable + +<sup>85</sup> (27 April 2011) Make sure that r_useIndexBuffers is set to 1 in .etqwctl/base/etqwconfig.cfg, or it will crash (sometimes the game resets it to 0) + +<sup>86</sup> (5 May 2011) GLSL must be disabled or big graphics corruption you will get when your outside of station. After the game is started, vsync must be disabler or enabled to stop the flickering. + +<sup>87</sup> (5 May 2011) Lower setting recommended, Highest setting work with shadow/hdr off but it become slower and slower after time pass. With everything in minimum, the fps stay constant over time. + +<sup>89</sup> (28 Feb 2013) It runs very slow. After Level loads you see onyl hud and black screen. No level is loaded. + +<sup>90</sup> (19 September 2011) The game freezes when loading some missions (e.g. 2nd mission), The game freezes when shooting enemies. Graphically looks ok It runs with about 20 fps. May require s3tc and texture-float to work. Tested with wine 1.3.28. [[Video/description|http://www.youtube.com/watch?v=XZ_T_xepfW8]]. + +<sup>91</sup> (6 August 2011) Some shadow glitches (foliage shadows flickers square) and decal flickers. As usual, no antialiasing, not sure about anisotropic filtering (doesn't look like it). + +<sup>92</sup> (6 August 2011) Tried only medium and high detail; if it crashes with 'Got signal 11 at (nil) from (nil)', remove all files from the lib directory and add back only the ones it misses + +<sup>93</sup> (6 August 2011) It's playable, missing dynamic shadows. + +<sup>95</sup> (2 December 2011) tesselation is not yet supported by Mesa + +<sup>96</sup> (2 December 2011) some rendering errors, see [[https://bugs.freedesktop.org/show_bug.cgi?id=43520|https://bugs.freedesktop.org/show_bug.cgi?id=43520]] + +<sup>97</sup> The game does not have any artifacts, but it is significantly slower than under then the old geforce cards. + +<sup>98</sup> (17 February 2012) The game needs S3TC to run. It can be playable perfectly on "safe mode". with mesa 8.1 dev it can be playable on fixed as per bug resolution[[https://bugs.freedesktop.org/show_bug.cgi?id=44701|https://bugs.freedesktop.org/show_bug.cgi?id=44701]]. Developers are working in order to improve the shader compatibility. [[https://bugs.freedesktop.org/show_bug.cgi?id=41152|https://bugs.freedesktop.org/show_bug.cgi?id=41152]] + +<sup>99</sup> (01 July 2012) Version 1.11, needs S3TC, anti aliasing needs to be disabled in the launcher or it shows disorted coloured boxes rather than the game and menu, works on low (<20 fps), mid (<15 fps) and high (<10 fps) settings 1920x1080 full screen on AMD6970M + +<sup>100</sup> (09 October 2012) Refuses to start when MSAA enabled in game. + +<sup>101</sup> (09 October 2012) Cannot set shader effect quality to highest settings or you will get graphical glitches in the water, cannot run MSAA. + +<sup>102</sup> (28 Feb 2013) Crash because missing GLX functions -> Your OpenGL drivers lack S3TC support + +<sup>103</sup> (28 Feb 2013) AA not supported so the fonts look ugly + +<sup>104</sup> (28 Feb 2013) AA not supported also no Antostrophic filtering. + +<sup>105</sup> (28 Feb 2013) Got signal 11 at (nil) from 0xf5ffddfb. Also some lookup error in /usr/lib/libXrandr.so.2: undefined symbol: _XGetRequest + +<sup>106</sup> (28 Feb 2013) ERROR: Missing required OpenGL extensions:GL_ARB_vertex_buffer_object GL_EXT_framebuffer_blit GL_ARB_shader_objects GL_ARB_vertex_shader GL_ARB_fragment_shader GL_ARB_shading_language_100 + +<sup>107</sup> (1 Mar 2013) No textures are drawn on the objects in-game. It's all white, cursor and menu not properly drawn. Many glitches. + +<sup>108</sup> (1 Mar 2013) openGl 2.0 not available but my card is able to do it...... Game does not start. diff --git a/RadeonTVbuildHowto.mdwn b/RadeonTVbuildHowto.mdwn new file mode 100644 index 00000000..f405507f --- /dev/null +++ b/RadeonTVbuildHowto.mdwn @@ -0,0 +1,20 @@ + +According to a [[post by Alex Deucher|http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2007-August/039867.html]], the canonical way to build the ATI driver with TV Out support that he maintains is: + +1. First make sure you back up the existing radeon (**radeon_drv.so**) and ati (**ati_drv.so**) drivers. +1. install the **xorg-dev**, **mesa-dev**, **libdrm-dev** and **xserver-dev** packages for your distro. The usual build tools are needed too (**autoconf**, **automake**, **libtool**, **gcc** and others) +1. **git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati** +1. **cd xf86-video-ati** +1. **./autogen.sh --prefix=/usr** +1. **make** +1. **sudo make install** or **make install** as root +If you get this error after running **autogen.sh**, you forgot to install **libtool**: + + +[[!format txt """ +configure.ac:38: error: possibly undefined macro: AC_DISABLE_STATIC + If this token and others are legitimate, please use m4_pattern_allow. + See the Autoconf documentation. +configure.ac:39: error: possibly undefined macro: AC_PROG_LIBTOOL +autoreconf: /usr/bin/autoconf failed with exit status: 1 +"""]]
\ No newline at end of file diff --git a/RandomPage.mdwn b/RandomPage.mdwn new file mode 100644 index 00000000..ff80db49 --- /dev/null +++ b/RandomPage.mdwn @@ -0,0 +1,2 @@ + +A list of 25 random pages (out of [[!pagecount ]] total): diff --git a/RelatedProjects.mdwn b/RelatedProjects.mdwn new file mode 100644 index 00000000..0b9522c4 --- /dev/null +++ b/RelatedProjects.mdwn @@ -0,0 +1,16 @@ + +The X.Org project exists as part of a family of related projects that contribute to the development of the X Window System. + +* [[freedesktop.org|http://www.freedesktop.org]] +* [[DRI Wiki|http://dri.freedesktop.org/wiki/]] useful information about using Direct Rendering with Xorg +* [[Cairo|http://cairographics.org/]] +* [[The XFree86 Project, Inc.|http://www.xfree86.org]] +* [[Gnome|http://www.gnome.org/]] +* [[The K Desktop Environment|http://www.kde.org/]] +* [[Enlightenment|http://enlightenment.org/]] +* [[Linux Terminal Server Project|http://www.ltsp.org/]] +* [[Cygwin/X|http://x.cygwin.com/]] +* [[Compiz|http://compiz.org/]] +* [[Croquet Project|http://www.opencroquet.org]] +* [[Project Looking Glass|https://lg3d-core.dev.java.net/]] +* [[The freedesktop.org info page|http://www.freedesktop.org/wiki/Info]] has links to many worthwhile projects.
\ No newline at end of file diff --git a/ReleaseWorkingGroup.mdwn b/ReleaseWorkingGroup.mdwn new file mode 100644 index 00000000..a6250f54 --- /dev/null +++ b/ReleaseWorkingGroup.mdwn @@ -0,0 +1,44 @@ + + +## History and Motivation + +Starting with Xorg 6.7, we used a fairly heavyweight release process, in which the entire source tree was frozen for stabilisation during a one to three month process. This led to excessively long release cycles, and frustrated developers who had to wait until the cycle was complete before commiting new code. With the move to modular X, the release process has become more decentralized and asynchronous. Maintainers for individual modules are able to release their subsystems as needed, rather than waiting up to a year or more for a monolithic release. + +There is still value in providing accumulated releases on a periodic basis. Much like releases in the Gnome project, these releases indicate that the indicated versions of each module have been tested and are known to work well together. Release management in the modular world is therefore mostly a matter of reviewing the various modules and selecting the appropriate branch to badge as released. + + +## Status + +Adam Jackson is currently lead RM, but ideally this will become merely a ceremonial title. + +7.1 has been released. This seems to have gone reasonably well for a first effort, but there have been some notable issues. + +* The katamari process was almost entirely manual. This needs to be made point-and-shoot. Some inconsistencies in the archive were found afterwards, which is a bit embarassing. ajax is working on scripting this process and placing the scripts and data in CVS so it's all public and easy-access. +* Still poor communication regarding how releases are to be composed by downstream. How do you know which modules to include? How do you know what modules have been deprecated? etc. + +## Schedule and work in progress + +See the [[proposed schedule|http://lists.freedesktop.org/archives/xorg/2006-May/015476.html]]. + + +## Future issues + +Current open questions regarding the release management process. + + +### Release-wrangler calls + +We did this in 6.x, and tried it during the start of the 6.9/7.0 effort, but it was impossible to schedule and the calls burned a lot of time. If 7.1 is anything to go by, they don't seem to be needed. + +There is some issue of process transparency during the RC cycle; again, automation should help with this next time around. + + +### Is the six month cycle too aggressive, or not aggressive enough + +No one's complained yet, so the working assumption is that it's Just Right. + + +### Where in the world is Carmen Sandiego + + +### What defines X11R8 diff --git a/Releases.mdwn b/Releases.mdwn new file mode 100644 index 00000000..8124df57 --- /dev/null +++ b/Releases.mdwn @@ -0,0 +1,32 @@ + + +## Current release + +**The latest release of X.Org was [[X11R7.7|Releases/7.7]]**, on June 6, 2012. Of note, this release added multitouch input support, Fence synchronization primitives, and pointer barriers. Read more in the [[Release Notes|http://www.x.org/releases/X11R7.7/doc/xorg-docs/ReleaseNotes.html]]. + + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.7/]]. + +## General + +* List of [[module versions in various roll-up releases|Releases/ModuleVersions]]. +* Individual releases of Xorg modules are [[here|http://www.x.org/releases/individual]]. +* [[6.8.0 post-partum|X11R68PostPartumNotes]]: lessons learned. +* For module maintainers: [[HOWTO Make a release|Development/Documentation/ReleaseHOWTO]]. + +## Old releases + +* [[X11R7.6|Releases/7.6]] (Released: 2010-12-20) [[Release Notes|http://www.x.org/releases/X11R7.6/doc/xorg-docs/ReleaseNotes.html]]. Of note, this release added xorg.conf.d directories, Input``Class configuration sections, udev support on Linux, improved documentation, and integrated xcb. + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.6/]]. +* [[X11R7.5|Releases/7.5]] (Released: 2009-10-26) [[Release Notes|http://www.x.org/archive/X11R7.5/doc/RELNOTES.txt]]. Of note, this release added [[Multi-Pointer X (MPX)|http://wearables.unisa.edu.au/mpx/]], RandR 1.3, E-EDID support and DRI2. + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.5/]]. +* [[X11R7.4|Releases/7.4]] (Released: 2008-09-23) [[Release Notes|http://www.x.org/archive/X11R7.4/doc/RELNOTES.txt]] + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.4/]]. +* [[X11R7.3|Releases/7.3]] (Released: 2007-09-06) [[Release Notes|http://www.x.org/archive/X11R7.3/doc/RELNOTES.txt]] Of note, this release added [[RandR 1.2|Projects/XRandR]] and [[input hotplug|XInputHotplug]] support. + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.3/]]. +* [[X11R7.2|Releases/7.2]] (Released: 2007-02-15) Of note, this release added autoconfiguration support, and enhanced support for GL-based compositing managers, such as Compiz and Beryl. + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.2/]]. +* [[X11R7.1|Releases/7.1]] (Released: 2006-05-22) [[Release Notes|http://www.x.org/archive/X11R7.1/doc/RELNOTES.html]] + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.1/]]. +* [[X11R7.0|Releases/7.0]] (Released: 2005-12-21) + * Download: [[mirrors|Releases/Download]], [[master site|http://www.x.org/releases/X11R7.0/]]. +For more complete information, including a release history, please see the [[historical releases|Releases/History]] page. diff --git a/Releases/7.2.mdwn b/Releases/7.2.mdwn new file mode 100644 index 00000000..b1a35bc2 --- /dev/null +++ b/Releases/7.2.mdwn @@ -0,0 +1,21 @@ + +The X.Org Foundation released 7.2.0 (aka X11R7.2) on February 15th, 2007. + + +## Features + +* Autoconfiguration: The X server can now start without an xorg.conf file in most cases. +* GL compositing managers: A number of improvements were merged that better enable the use of GL-based compositing managers such as Compiz and Beryl. +* i965: Intel i965 chipsets (aka X3000) are supported in this release. +* [[XACE|Projects/XACE]]: The XACE security framework has been merged, allowing the development of new, extensible, security models. +* [[XCB|http://xcb.freedesktop.org]]: XCB is part of the 7.2 release, including libX11 based on XCB for its transport. +* xdm: Among other improvements, xdm now supports PAM, for better authentication. + +## Download + +You can download 7.2.0 from either a [[mirror|Releases/Mirrors]], or the [[master site|http://xorg.freedesktop.org/releases/X11R7.2/]]. + + +## Documentation + +Due to bugs in the documentation toolchain, documentation for this release is not available online at the moment. The [[press release|PressReleases/X11R72Released]] is available. diff --git a/Releases/7.5.mdwn b/Releases/7.5.mdwn new file mode 100644 index 00000000..15381c34 --- /dev/null +++ b/Releases/7.5.mdwn @@ -0,0 +1,228 @@ + +[[X11R7.5 was released on October 26, 2009|Other/Press/X11R75Released]]. + +Release notes, changelogs, downloads, etc. are available at [[http://www.x.org/releases/X11R7.5/|http://www.x.org/releases/X11R7.5/]] + + +## Features Added/Enhanced + +* [[Xserver build no longer needs to symlink to Mesa sources|http://lists.freedesktop.org/archives/xorg/2008-May/035274.html]] +* [[MPX: Multi-Pointer X|http://wearables.unisa.edu.au/mpx/]] ([[PeterHutterer|PeterHutterer]]) +* E-EDID support ([[AdamJackson|AdamJackson]]) +* [[Input device properties|http://who-t.blogspot.com/2008/07/input-device-properties.html]] ([[PeterHutterer|PeterHutterer]]) +* [[predictable pointer acceleration|Development/Documentation/PointerAcceleration]] ([[SimonThum|SimonThum]]) +* xorg-server [[1.7.0|Server17Branch]] +* Add SELinux security module which uses XACE ([[EamonWalsh|EamonWalsh]]). +* RandR 1.3 ([[KeithPackard|KeithPackard]]) + +## Features Removed + +* X server libraries: [[cfb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0dab6fa3582b70ccd0f01459902415c28dbc81ff]], [[afb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=20ea99c655140e101f2d20cfab78fb22765fec62]], [[mfb/xf1bpp|http://cgit.freedesktop.org/xorg/xserver/commit/?id=eabcfce0a68d504d11be9479f09e66f574dd2f21]] +* X server support for obsolete/unused/broken/unmaintained extensions: [[AppGroup|http://cgit.freedesktop.org/xorg/xserver/commit/?id=eafaf40fb3368ca7e4cf48336fdb7a6c9f536bfa]], [[EVI|http://cgit.freedesktop.org/xorg/xserver/commit/?id=13adef8a17d8815f4db2aaac30ae04438e125343]], [[MIT-SUNDRY-NONSTANDARD|http://cgit.freedesktop.org/xorg/xserver/commit/?id=25827fde68d3bb02a2b7e05fae53a1d97edf1f76]], [[TOG-CUP|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a7503615a6893749d512f75d37646273f31b9dbf]], [[XTrap|http://cgit.freedesktop.org/xorg/xserver/commit/?id=cbc20d92de92aad5ca240310a9156ccf97c24a01]], [[XFree86-Misc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=22e64108ec63ba77779891f8df237913ef9ca731]], [[XEvIE|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f4036f6ace5f770f0fe6a6e3dc3749051a81325a]] +* X server command line flags: [[-co|http://cgit.freedesktop.org/xorg/xserver/commit/?id=41b68e0dea9305d66bca2fc4ad96db01f5342c6d]], [[-bestrefresh|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1f416fba994ed7a7e072a9f0a86b515855ea3bac]], [[-showunresolved|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5a72c45d42abc7227c6cf3d14fd7043ea7527c54]] +* X server bundled utilties: [[xorgconfig|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d34430414ac0e77eec61ab0ac9ef427b236eb639]], [[xorgcfg|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5c1e254cc85e9ad409b0217780545c29f62d5feb]], [[ioport|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b74927c3844bc2650d95f604fe782d95ade067f1]], [[kbd_mode|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8c0518379089d230060e9ff672ba5eba34198325]] +* Unmaintained X server variants: [[Xgl|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d15b3790307053587df8daed1936ff6923881b63]], [[Xprt|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1c8bd318fbaf65890ef16fe26c76dd5e6f14dfde]] (moved to [[separate xprint git repo|http://cgit.freedesktop.org/xorg/xprint/]]) + +## Modules included + +[[Module List|http://cgit.freedesktop.org/xorg/util/modular/tree/module-list.txt?id=XORG-7_5]] + + +## New/updated modules + +_These are just listed for easy reference here, the above link is the canonical list. Only the release announcement for the version included in X11``R7.5 is listed here. Some modules had multiple releases since X11``R7.4 - see each module's [[ChangeLog|ChangeLog]] or git repository for a full list of changes. _ + + +## New/Updated Modules + + +### xserver + + * [[xorg-server-1.7.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001183.html]] + +### app + + * [[bdftopcf-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001046.html]] + * [[iceauth-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001132.html]] + * [[luit-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001080.html]] + * [[mkfontdir-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001135.html]] + * [[mkfontscale-1.0.7|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001134.html]] + * [[sessreg-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001139.html]] + * [[setxkbmap-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000896.html]] + * [[smproxy-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001160.html]] + * [[x11perf-1.5.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001161.html]] + * [[xauth-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001047.html]] + * [[xbacklight-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001064.html]] + * [[xcmsdb-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001156.html]] + * [[xcursorgen-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001162.html]] + * [[xdpyinfo-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001158.html]] + * [[xdriinfo-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001159.html]] + * [[xev-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001143.html]] + * [[xgamma-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001151.html]] + * [[xhost-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001152.html]] + * [[xinput-1.5.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001148.html]] + * [[xkbcomp-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001095.html]] + * [[xkbevd-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001163.html]] + * [[xkbutils-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001164.html]] + * [[xkill-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001144.html]] + * [[xlsatoms-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001145.html]] + * [[xlsclients-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001165.html]] + * [[xmodmap-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001100.html]] + * [[xpr-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001170.html]] + * [[xprop-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001140.html]] + * [[xrandr-1.3.2|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001027.html]] + * [[xrdb-1.0.6|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001141.html]] + * [[xrefresh-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001166.html]] + * [[xset-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001043.html]] + * [[xsetroot-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001167.html]] + * [[xvinfo-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001168.html]] + * [[xwd-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001169.html]] + * [[xwininfo-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001142.html]] + * [[xwud-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001146.html]] + +### data + + * [[xbitmaps-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001147.html]] + * [[xcursor-themes-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001063.html]] + +### doc + + * [[xorg-docs-1.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001185.html]] + * [[xorg-sgml-doctools-1.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001182.html]] + +### driver + + +#### input + + * [[xf86-input-acecad-1.4.0|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001029.html]] + * [[xf86-input-aiptek-1.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001030.html]] + * [[xf86-input-evdev-2.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001176.html]] + * xf86-input-joystick-1.4.99.2 + * [[xf86-input-keyboard-1.4.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001109.html]] + * [[xf86-input-mouse-1.5.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001104.html]] + * [[xf86-input-synaptics-1.2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001116.html]] + * [[xf86-input-vmmouse-12.6.5|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000956.html]] + * [[xf86-input-void-1.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001028.html]] + +#### video + + * [[xf86-video-apm-1.2.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000923.html]] + * [[xf86-video-ark-0.7.2|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001014.html]] + * [[xf86-video-ast-0.89.9|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000924.html]] + * [[xf86-video-ati-6.12.4|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001033.html]] (see also [[radeon|radeon]]) + * [[xf86-video-chips-1.2.2|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000962.html]] + * [[xf86-video-cirrus-1.3.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000925.html]] + * [[xf86-video-dummy-0.3.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000872.html]] + * [[xf86-video-fbdev-0.4.1|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000926.html]] + * [[xf86-video-geode-2.11.6|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001066.html]] + * [[xf86-video-glide-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000987.html]] + * [[xf86-video-glint-1.2.4|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000927.html]] + * [[xf86-video-i128-1.3.3|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000928.html]] + * [[xf86-video-i740-1.3.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000929.html]] + * [[xf86-video-intel-2.9.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001186.html]] + * [[xf86-video-mach64-6.8.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000930.html]] + * [[xf86-video-mga-1.4.11|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000931.html]] + * [[xf86-video-neomagic-1.2.4|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000932.html]] + * [[xf86-video-newport-0.2.3|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001017.html]] + * [[xf86-video-nv-2.1.15|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001031.html]] + * [[xf86-video-r128-6.8.1|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000933.html]] + * [[xf86-video-rendition-4.2.3|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001013.html]] + * [[xf86-video-s3-0.6.3|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000936.html]] + * [[xf86-video-s3virge-1.10.4|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000934.html]] + * [[xf86-video-savage-2.3.1|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000935.html]] + * [[xf86-video-siliconmotion-1.7.3|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000952.html]] + * [[xf86-video-sis-0.10.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000939.html]] + * [[xf86-video-sisusb-0.9.3|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000938.html]] + * [[xf86-video-suncg14-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-May/000836.html]] + * [[xf86-video-suncg3-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-May/000837.html]] + * [[xf86-video-suncg6-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-May/000838.html]] + * [[xf86-video-sunffb-1.2.1|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001018.html]] + * [[xf86-video-suntcx-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-May/000839.html]] + * [[xf86-video-tdfx-1.4.3|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000937.html]] + * [[xf86-video-tga-1.2.1|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001015.html]] + * [[xf86-video-trident-1.3.3|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000951.html]] + * [[xf86-video-tseng-1.2.3|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001016.html]] + * [[xf86-video-vesa-2.2.1|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000940.html]] + * [[xf86-video-vmware-10.16.8|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001022.html]] + * [[xf86-video-voodoo-1.2.3|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000941.html]] + * [[xf86-video-wsfb-0.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001034.html]] + * [[xf86-video-xgi-1.5.1|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001012.html]] + * [[xf86-video-xgixp-1.7.99.4|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001019.html]] + +### font + + * [[font-util-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001138.html]] + * [[All font modules|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001131.html]] + +### lib + + * [[libAppleWM-1.4.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000988.html]] + * [[libFS-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000893.html]] + * [[libICE-1.0.6|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000995.html]] + * [[libSM-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000958.html]] + * [[libWindowsWM-1.0.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001112.html]] + * [[libX11-1.3.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001184.html]] + * [[libXScrnSaver-1.2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000972.html]] + * [[libXau-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000996.html]] + * [[libXaw-1.0.7|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001172.html]] + * [[libXcomposite-0.4.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001113.html]] + * [[libXcursor-1.1.10|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000997.html]] + * [[libXdamage-1.1.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001105.html]] + * [[libXdmcp-1.0.3|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001057.html]] + * [[libXext-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001181.html]] + * [[libXfixes-4.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001114.html]] + * [[libXfont-1.4.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001129.html]] + * [[libXft-2.1.14|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001127.html]] + * [[libXi-1.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001082.html]] + * [[libXinerama-1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001085.html]] + * [[libXmu-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001060.html]] + * [[libXpm-3.5.8|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001122.html]] + * [[libXrandr-1.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-March/000800.html]] + * [[libXrender-0.9.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001086.html]] + * [[libXres-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001121.html]] + * [[libXt-1.0.7|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001126.html]] + * [[libXtst-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001097.html]] + * [[libXv-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001094.html]] + * [[libXvMC-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001107.html]] + * [[libXxf86dga-1.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001103.html]] + * [[libXxf86vm-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001099.html]] + * [[libdmx-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001098.html]] + * [[libfontenc-1.0.5|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000994.html]] + * [[libpciaccess-0.10.9|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001065.html]] + * [[libxkbfile-1.0.6|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001108.html]] + * [[xtrans-1.2.5|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001171.html]] + +### proto + + * [[applewmproto-1.4.1|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000982.html]] + * [[bigreqsproto-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000975.html]] + * [[compositeproto-0.4.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001089.html]] + * [[damageproto-1.2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000984.html]] + * [[dmxproto-2.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001073.html]] + * [[dri2proto-2.1|http://lists.freedesktop.org/archives/xorg-announce/2009-June/000861.html]] + * [[fixesproto-4.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001101.html]] + * [[fontsproto-2.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000986.html]] + * [[glproto-1.4.10|http://lists.freedesktop.org/archives/xorg-announce/2009-May/000853.html]] + * [[inputproto-2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001081.html]] + * [[kbproto-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001149.html]] + * [[randrproto-1.3.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001102.html]] + * [[recordproto-1.14|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001076.html]] + * [[renderproto-0.11|http://lists.freedesktop.org/archives/xorg-announce/2009-July/000904.html]] + * [[resourceproto-1.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000970.html]] + * [[scrnsaverproto-1.2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000971.html]] + * [[videoproto-2.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000983.html]] + * [[windowswmproto-1.0.4|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001092.html]] + * [[xcmiscproto-1.2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000977.html]] + * [[xextproto-7.1.1|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000969.html]] + * [[xf86bigfontproto-1.2.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000978.html]] + * [[xf86dgaproto-2.1|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001074.html]] + * [[xf86driproto-2.1.0|http://lists.freedesktop.org/archives/xorg-announce/2009-August/000979.html]] + * [[xf86vidmodeproto-2.3|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001075.html]] + * [[xineramaproto-1.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001077.html]] + * [[xproto-7.0.16|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001058.html]] + +### util + + * [[makedepend-1.0.2|http://lists.freedesktop.org/archives/xorg-announce/2009-October/001133.html]] + * [[util-macros-1.3.0|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001024.html]]
\ No newline at end of file diff --git a/Releases/7.6.mdwn b/Releases/7.6.mdwn new file mode 100644 index 00000000..52511f2f --- /dev/null +++ b/Releases/7.6.mdwn @@ -0,0 +1,23 @@ + +[[X11R7.6|http://www.x.org/releases/X11R7.6/]] development is complete: [[the final release|http://www.x.org/releases/X11R7.6/]] has been posted. (See [[the announcement|Other/Press/X11R76Released]] for further details.) + + +## Features Added/Enhanced + +* [[XCB|http://xcb.freedesktop.org/]] included in the katamari, required by libX11 1.4 and some clients. +* [[Xorg server 1.8 changes|Server18Branch]], including [[new input hotplugging and configuration framework|http://who-t.blogspot.com/2010/01/new-configuration-world-order.html]] +* [[Xorg server 1.9 changes|Server19Branch]] +* [[Documentation|Development/Documentation/WritingDocumentation]]: Most protocol & API docs moved from xorg-docs into individual proto/library modules, converted from legacy formats to DocBook/XML where possible. +* Massive amounts of configure.ac/Makefile.am cleanup & improvement. Lots of previously duplicated bits moved to xorg-macros (requiring recent xorg-macros versions when we build the tarballs, but unless you autoreconf that shouldn't affect people building from tarballs). +* Most of the COPYING file stubs have been replaced with actual copies of the copyright & license notices for easier packaging by distributors who provide such notices in their packages. + +## Features Removed + +* [[Xsdl|http://cgit.freedesktop.org/xorg/xserver/commit/?id=52bc6d944946e66ea2cc685feaeea40bb496ea83]] - experimental kdrive server using SDL that was never finished +* [[Frame buffer support in XF86DGA|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0b7c6c728c2e2d8433a188315cc591308a89cd85]] +* [[Multibuffer extension in X servers|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0ba82562eeba8bf3bcd00b6e3ff28ce5b2c8df3c]] - deprecated since the 90's + +## Schedule + +* RC1: 11 November 2010 +* Final Release: 20 December 2010
\ No newline at end of file diff --git a/Releases/7.7.mdwn b/Releases/7.7.mdwn new file mode 100644 index 00000000..6e18b846 --- /dev/null +++ b/Releases/7.7.mdwn @@ -0,0 +1,18 @@ + +X11``R7.7 development is development is complete: the final release has been posted at [[http://www.x.org/releases/X11R7.7/|http://www.x.org/releases/X11R7.7/]] + + +## Features Added/Enhanced + +See also: [[Summary of new features in X11R7.7|http://www.x.org/releases/X11R7.7/doc/xorg-docs/ReleaseNotes.html#Summary_of_new_features_in_X11R7.7]], [[Combined ChangeLog for all X11R7.7 components (1.5 Mb)|http://www.x.org/releases/X11R7.7/changelog.html]] + +* [[Xorg server 1.10 changes|Server110Branch]], [[Xorg server 1.11 changes|Server11Branch]], [[Xorg server 1.12 changes|Server112Branch]] +* [[Documentation|Development/Documentation/WritingDocumentation]]: Finish conversions to DocBook/XML, improve integration across doc sets. +* Sync extension 3.1 - adds Fence object support +* Xi 2.2 multitouch support +* XFixes 5.0: Pointer Barriers + +## Schedule + +* RC 1: April 15, 2012 +* Final Release: June 6, 2012
\ No newline at end of file diff --git a/Releases/Download.mdwn b/Releases/Download.mdwn new file mode 100644 index 00000000..120821bb --- /dev/null +++ b/Releases/Download.mdwn @@ -0,0 +1,87 @@ + +All releases of X.Org since 7.0 can be downloaded from one of the primary download sites, or from a mirror close to you. Development releases are usually only available on the primary sites. + + +## Primary sites + +* freedesktop.org, Oregon, USA: [[HTTP|http://xorg.freedesktop.org/releases/]] and [[FTP|ftp://ftp.freedesktop.org/pub/xorg]]. +* x.org, Massachusetts, USA: [[HTTP|http://www.x.org/pub/]] and [[FTP|ftp://ftp.x.org/pub]]. + +## Mirrors + + +### North America + +* [[ftp://mirror.csclub.uwaterloo.ca/x.org/|ftp://mirror.csclub.uwaterloo.ca/x.org/]] +* [[ftp://xorg.mirrors.pair.com/|ftp://xorg.mirrors.pair.com/]] +* [[http://mirror.csclub.uwaterloo.ca/x.org/|http://mirror.csclub.uwaterloo.ca/x.org/]] +* [[http://xorg.mirrors.pair.com/|http://xorg.mirrors.pair.com/]] +* [[http://mirror.us.leaseweb.net/xorg/|http://mirror.us.leaseweb.net/xorg/]] + +### Europe + +* [[ftp://artfiles.org/x.org/|ftp://artfiles.org/x.org/]] +* [[ftp://ftp.chg.ru/pub/X11/x.org/|ftp://ftp.chg.ru/pub/X11/x.org/]] +* [[ftp://ftp.fu-berlin.de/unix/X11/FTP.X.ORG/|ftp://ftp.fu-berlin.de/unix/X11/FTP.X.ORG/]] +* [[ftp://ftp.gwdg.de/pub/x11/x.org/|ftp://ftp.gwdg.de/pub/x11/x.org/]] +* [[ftp://ftp.mirrorservice.org/sites/ftp.x.org/|ftp://ftp.mirrorservice.org/sites/ftp.x.org/]] +* [[ftp://ftp.ntua.gr/pub/X11/|ftp://ftp.ntua.gr/pub/X11/]] +* [[ftp://ftp.piotrkosoft.net/pub/mirrors/ftp.x.org/|ftp://ftp.piotrkosoft.net/pub/mirrors/ftp.x.org/]] +* [[ftp://ftp.portal-to-web.de/pub/mirrors/x.org/|ftp://ftp.portal-to-web.de/pub/mirrors/x.org/]] +* [[ftp://ftp.solnet.ch/mirror/x.org/|ftp://ftp.solnet.ch/mirror/x.org/]] +* [[ftp://ftp.sunet.se/pub/X11/|ftp://ftp.sunet.se/pub/X11/]] +* [[ftp://gd.tuwien.ac.at/X11/|ftp://gd.tuwien.ac.at/X11/]] +* [[ftp://mi.mirror.garr.it/mirrors/x.org/|ftp://mi.mirror.garr.it/mirrors/x.org/]] +* [[ftp://mirror.cict.fr/x.org/|ftp://mirror.cict.fr/x.org/]] +* [[ftp://mirror.switch.ch/mirror/X11/|ftp://mirror.switch.ch/mirror/X11/]] +* [[ftp://mirrors.ircam.fr/pub/x.org/|ftp://mirrors.ircam.fr/pub/x.org/]] +* [[ftp://x.mirrors.skynet.be/pub/ftp.x.org/|ftp://x.mirrors.skynet.be/pub/ftp.x.org/]] +* [[http://artfiles.org/x.org/|http://artfiles.org/x.org/]] +* [[http://ftp.chg.ru/pub/X11/x.org/|http://ftp.chg.ru/pub/X11/x.org/]] +* [[http://ftp.gwdg.de/pub/x11/x.org/|http://ftp.gwdg.de/pub/x11/x.org/]] +* [[http://gd.tuwien.ac.at/X11/|http://gd.tuwien.ac.at/X11/]] +* [[http://mi.mirror.garr.it/mirrors/x.org|http://mi.mirror.garr.it/mirrors/x.org]] +* [[http://mirror.cict.fr/x.org/|http://mirror.cict.fr/x.org/]] +* [[http://mirror.switch.ch/ftp/mirror/X11/|http://mirror.switch.ch/ftp/mirror/X11/]] +* [[http://mirrors.ircam.fr/pub/x.org/|http://mirrors.ircam.fr/pub/x.org/]] +* [[http://piotrkosoft.net/pub/mirrors/ftp.x.org/|http://piotrkosoft.net/pub/mirrors/ftp.x.org/]] +* [[http://www.mirrorservice.org/sites/ftp.x.org/|http://www.mirrorservice.org/sites/ftp.x.org/]] +* [[http://www.portal-to-web.de/pub/mirrors/x.org/|http://www.portal-to-web.de/pub/mirrors/x.org/]] +* [[http://x.cybermirror.org/|http://x.cybermirror.org/]] +* [[http://x.europnews.de/|http://x.europnews.de/]] +* [[http://x.mirrors.skynet.be/pub/ftp.x.org/|http://x.mirrors.skynet.be/pub/ftp.x.org/]] +* [[http://xorg.mirror.solnet.ch/|http://xorg.mirror.solnet.ch/]] +* [[https://yehkri.com/mirror/xorg/|https://yehkri.com/mirror/xorg/]] +* [[http://mirror.nl.leaseweb.net/xorg/|http://mirror.nl.leaseweb.net/xorg/]] +* [[http://mirror.de.leaseweb.net/xorg/|http://mirror.de.leaseweb.net/xorg/]] +* rsync://ftp.solnet.ch::X.org/ +* rsync://gd.tuwien.ac.at/X11/ +* rsync://mirrors.ircam.fr/pub/x.org/ +* rsync://piotrkosoft.net/mirrors/ftp.x.org/ +* rsync://rsync.mirrorservice.org/ftp.x.org/ + +### East Asia + +* [[ftp://ftp.cs.cuhk.edu.hk/pub/X11|ftp://ftp.cs.cuhk.edu.hk/pub/X11]] +* [[ftp://ftp.u-aizu.ac.jp/pub/x11/x.org/|ftp://ftp.u-aizu.ac.jp/pub/x11/x.org/]] +* [[ftp://ftp.yz.yamagata-u.ac.jp/pub/X11/x.org/|ftp://ftp.yz.yamagata-u.ac.jp/pub/X11/x.org/]] +* [[ftp://ftp.kaist.ac.kr/x.org/|ftp://ftp.kaist.ac.kr/x.org/]] +* [[ftp://mirrors.go-part.com/xorg/|ftp://mirrors.go-part.com/xorg/]] +* [[http://mirrors.go-part.com/xorg/|http://mirrors.go-part.com/xorg/]] +* [[http://ftp.yz.yamagata-u.ac.jp/pub/X11/x.org/|http://ftp.yz.yamagata-u.ac.jp/pub/X11/x.org/]] +* [[http://ftp.kaist.ac.kr/x.org/|http://ftp.kaist.ac.kr/x.org/]] +* [[http://x.cs.pu.edu.tw|http://x.cs.pu.edu.tw]] +* rsync://ftp.kaist.ac.kr/x.org/ +* rsync://mirrors.go-part.com/xorg/ + +### South Africa + +* [[ftp://ftp.is.co.za/pub/x.org|ftp://ftp.is.co.za/pub/x.org]] + +### South America + +* no known active mirror. + +### Australia + +* no known active mirror.
\ No newline at end of file diff --git a/Releases/History.mdwn b/Releases/History.mdwn new file mode 100644 index 00000000..aa81c82a --- /dev/null +++ b/Releases/History.mdwn @@ -0,0 +1,66 @@ + +This page lists old releases of X. For more current information, please see the [[releases|Releases]] page. + +The [[Wikipedia page on X|http://en.wikipedia.org/wiki/X_Window_System#Release_history]] has some more detailed information on older releases. + + +## X.Org Foundation monolithic releases + +* [[X.Org 6.9|Releases/6.9]] (Released: 2005-12-21) + * [[Master download site|http://xorg.freedesktop.org/releases/X11R6.9.0/]] +* [[X.Org 6.8.2|Releases/6.8.2]] (Released: 2005-02-09) + * [[Master download site|http://xorg.freedesktop.org/releases/X11R6.8.2/]] +* [[X.Org 6.8.1|Releases/6.8.1]] (Released: 2004-09-17, patch release) + * [[Master download site|http://xorg.freedesktop.org/releases/X11R6.8.1/]] +* [[X.Org 6.8.0|Releases/6.8]] (Released: 2004-09-09) + * [[Master download site|http://xorg.freedesktop.org/releases/X11R6.8.0/]] +* [[X.Org 6.7|Releases/6.7]] (Released: about 2004-04-06, based on X.Org X11R6.6 and XFree86 4.4.0 RC2) + * [[Master download site|http://xorg.freedesktop.org/releases/X11R6.7.0/]] + +## XFree86 releases + +Former X11 releases, done by [[XFree86|http://www.xfree86.org]]: + +* XFree86 4.5.0 (Release: 2005-03-16) +* XFree86 4.4.99.18 (snapshot): (Release: 2004-11-27) +* XFree86 4.4.99.9 (develsnap): (Release: 2004-07-12) +* XFree86 4.4.0 (Release: 2004-02-23) +* XFree86 4.4.0 RC2 (Release: ?) +* XFree86 4.3.0 (Release: 2003-02-26) +* XFree86 4.2.1 (Release: 2002-09-03) +* XFree86 4.2.0 (Release: 2002-01-16) +* XFree86 4.1.0 (Release: 2001-06-02) +* XFree86 4.0.3 (Release: 2001-03-02) +* XFree86 4.0.2 (Release: 2000-12-15) +* XFree86 4.0.1 (Release: 2000-06-30) +* XFree86 4.0.0 (Release: 2000-02-26) +* XFree86 3.3.6 (Release: 1999-12-31) +* XFree86 3.3.5 (Release: ?) +* XFree86 2.1.1 (Release: 1994-05-04) +* XFree86 2.1 (Release: 1994-03-11) +* XFree86 2.0 +(This listing might be incomplete. The provided release dates can be slightly deviating from the true release dates.) + +You can find the related packages on misc [[mirrors|http://xfree86.org/mirrors/]]. + + +## X.Org and X Consortium + +Former X11 releases, done by X.Org and the [[X Consortium|XConsortium]]: + +* X.Org X11R6.6 (Released: 2001-04-03) +* X.Org X11R6.5.1 (Released: 2000-08-25) +* X.Org X11R6.4 (Release: 1998-03-31) +* X.Org X11R6.3 (Release: 1997-07-15) +* X.Org X11R6.1 (Release: 1996-03-12) +* X.Org X11R6 (Release: 1995-03-02) +* X.Org X11R5 (Release: 1994-05-18) +* X.Org X11R4 (Release: 1989-01-29) +* X.Org X11R3 (Release: ca. 1988-10-27) +* X.Org X11R2 (Release: ca. 1988-03-24) +* X.Org X11R1 (Release: ca. 1987-09-18) +* X.Org X10R4 (Release: ca. 1986-12-25) +* X.Org X10R3 (Release: ca. 1986-06-07) +(This listing might be incomplete. The provided release dates can be slightly deviating from the true release dates.) + +You can find these older versions on one of the long term of the X.Org site. diff --git a/Releases/ModuleVersions.mdwn b/Releases/ModuleVersions.mdwn new file mode 100644 index 00000000..804d32d5 --- /dev/null +++ b/Releases/ModuleVersions.mdwn @@ -0,0 +1,317 @@ + +This table lists which module versions were included in each X.Org rollup release. + +For descriptions of what each module is, see the [[module descriptions|ModuleDescriptions]] page. +[[!table header="no" class="mointable" data=""" +**Module** | **Directory** | **[[7.0|Releases/7.0]]** | **[[7.1|Releases/7.1]]** | **[[7.2|Releases/7.2]]** | **[[7.3|Releases/7.3]]** | **[[7.4|Releases/7.4]]** | **[[7.5|Releases/7.5]]** | **[[7.6|Releases/7.6]]** | **[[7.7|Releases/7.7]]** +[[applewmproto|http://cgit.freedesktop.org/xorg/proto/applewmproto/]] | proto | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.0.3.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.4.1.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.4.1.tar.bz2]] | [[1.4.2|http://xorg.freedesktop.org/releases/individual/proto/applewmproto-1.4.2.tar.bz2]] +[[appres|http://cgit.freedesktop.org/xorg/app/appres/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/appres-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/appres-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/appres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/appres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/appres-1.0.1.tar.bz2]] | _none_||| +[[bdftopcf|http://cgit.freedesktop.org/xorg/app/bdftopcf/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.1.tar.bz2]] | _none_ | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/bdftopcf-1.0.3.tar.bz2]] +[[beforelight|http://cgit.freedesktop.org/xorg/app/beforelight/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/beforelight-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/beforelight-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/beforelight-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/beforelight-1.0.2.tar.bz2]] | _none_|||| +[[bigreqsproto|http://cgit.freedesktop.org/xorg/proto/bigreqsproto/]] | proto | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/bigreqsproto-1.1.2.tar.bz2]] +[[bitmap|http://cgit.freedesktop.org/xorg/app/bitmap/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/bitmap-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/bitmap-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/bitmap-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/bitmap-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/bitmap-1.0.3.tar.bz2]] | _none_||| +[[compositeproto|http://cgit.freedesktop.org/xorg/proto/compositeproto/]] | proto | [[0.2.2|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.2.2.tar.bz2]] | [[0.3.1|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.3.1.tar.bz2]] | [[0.3.1|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.3.1.tar.bz2]] | [[0.4|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.4.tar.bz2]] | [[0.4|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.4.tar.bz2]] | [[0.4.1|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.4.1.tar.bz2]] | [[0.4.2|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.4.2.tar.bz2]] | [[0.4.2|http://xorg.freedesktop.org/releases/individual/proto/compositeproto-0.4.2.tar.bz2]] +[[damageproto|http://cgit.freedesktop.org/xorg/proto/damageproto/]] | proto | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/damageproto-1.2.1.tar.bz2]] +[[dmxproto|http://cgit.freedesktop.org/xorg/proto/dmxproto/]] | proto | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.2.2.tar.bz2]] | [[2.3|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.3.tar.bz2]] | [[2.3|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.3.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/proto/dmxproto-2.3.1.tar.bz2]] +[[dri2proto|http://cgit.freedesktop.org/xorg/proto/dri2proto/]] | proto | _none_||||| | [[2.1|http://xorg.freedesktop.org/releases/individual/proto/dri2proto-2.1.tar.bz2]] | [[2.3|http://xorg.freedesktop.org/releases/individual/proto/dri2proto-2.3.tar.bz2]] | [[2.6|http://xorg.freedesktop.org/releases/individual/proto/dri2proto-2.6.tar.bz2]] +[[editres|http://cgit.freedesktop.org/xorg/app/editres/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/editres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/editres-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/editres-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/editres-1.0.3.tar.bz2]] | _none_|||| +[[encodings|http://cgit.freedesktop.org/xorg/font/encodings/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.0.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/encodings-1.0.4.tar.bz2]] +[[evieext|http://cgit.freedesktop.org/xorg/proto/evieext/]] | proto | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/evieext-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/evieext-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/evieext-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/evieext-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/evieext-1.0.2.tar.bz2]] | _none_||| +[[fixesproto|http://cgit.freedesktop.org/xorg/proto/fixesproto/]] | proto | [[3.0.2|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-3.0.2.tar.bz2]] | [[4.0|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-4.0.tar.bz2]] | [[4.0|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-4.0.tar.bz2]] | [[4.0|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-4.0.tar.bz2]] | [[4.0|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-4.0.tar.bz2]] | [[4.1.1|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-4.1.1.tar.bz2]] | [[4.1.2|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-4.1.2.tar.bz2]] | [[5.0|http://xorg.freedesktop.org/releases/individual/proto/fixesproto-5.0.tar.bz2]] +[[font-adobe-100dpi|http://cgit.freedesktop.org/xorg/font/font-adobe-100dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-adobe-100dpi-1.0.3.tar.bz2]] +[[font-adobe-75dpi|http://cgit.freedesktop.org/xorg/font/font-adobe-75dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-adobe-75dpi-1.0.3.tar.bz2]] +[[font-adobe-utopia-100dpi|http://cgit.freedesktop.org/xorg/font/font-adobe-utopia-100dpi/]] | font | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-100dpi-1.0.4.tar.bz2]] +[[font-adobe-utopia-75dpi|http://cgit.freedesktop.org/xorg/font/font-adobe-utopia-75dpi/]] | font | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-75dpi-1.0.4.tar.bz2]] +[[font-adobe-utopia-type1|http://cgit.freedesktop.org/xorg/font/font-adobe-utopia-type1/]] | font | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-adobe-utopia-type1-1.0.4.tar.bz2]] +[[font-alias|http://cgit.freedesktop.org/xorg/font/font-alias/]] | font | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-alias-1.0.3.tar.bz2]] +[[font-arabic-misc|http://cgit.freedesktop.org/xorg/font/font-arabic-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-arabic-misc-1.0.3.tar.bz2]] +[[font-bh-100dpi|http://cgit.freedesktop.org/xorg/font/font-bh-100dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-100dpi-1.0.3.tar.bz2]] +[[font-bh-75dpi|http://cgit.freedesktop.org/xorg/font/font-bh-75dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-75dpi-1.0.3.tar.bz2]] +[[font-bh-lucidatypewriter-100dpi|http://cgit.freedesktop.org/xorg/font/font-bh-lucidatypewriter-100dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-100dpi-1.0.3.tar.bz2]] +[[font-bh-lucidatypewriter-75dpi|http://cgit.freedesktop.org/xorg/font/font-bh-lucidatypewriter-75dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-lucidatypewriter-75dpi-1.0.3.tar.bz2]] +[[font-bh-ttf|http://cgit.freedesktop.org/xorg/font/font-bh-ttf/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-ttf-1.0.3.tar.bz2]] +[[font-bh-type1|http://cgit.freedesktop.org/xorg/font/font-bh-type1/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bh-type1-1.0.3.tar.bz2]] +[[font-bitstream-100dpi|http://cgit.freedesktop.org/xorg/font/font-bitstream-100dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-100dpi-1.0.3.tar.bz2]] +[[font-bitstream-75dpi|http://cgit.freedesktop.org/xorg/font/font-bitstream-75dpi/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-75dpi-1.0.3.tar.bz2]] +[[font-bitstream-speedo|http://cgit.freedesktop.org/xorg/font/font-bitstream-speedo/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-speedo-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-speedo-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-speedo-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-speedo-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-speedo-1.0.0.tar.bz2]] | _none_||| +[[font-bitstream-type1|http://cgit.freedesktop.org/xorg/font/font-bitstream-type1/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-bitstream-type1-1.0.3.tar.bz2]] +[[font-cronyx-cyrillic|http://cgit.freedesktop.org/xorg/font/font-cronyx-cyrillic/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-cronyx-cyrillic-1.0.3.tar.bz2]] +[[font-cursor-misc|http://cgit.freedesktop.org/xorg/font/font-cursor-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-cursor-misc-1.0.3.tar.bz2]] +[[font-daewoo-misc|http://cgit.freedesktop.org/xorg/font/font-daewoo-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-daewoo-misc-1.0.3.tar.bz2]] +[[font-dec-misc|http://cgit.freedesktop.org/xorg/font/font-dec-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-dec-misc-1.0.3.tar.bz2]] +[[font-ibm-type1|http://cgit.freedesktop.org/xorg/font/font-ibm-type1/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-ibm-type1-1.0.3.tar.bz2]] +[[font-isas-misc|http://cgit.freedesktop.org/xorg/font/font-isas-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-isas-misc-1.0.3.tar.bz2]] +[[font-jis-misc|http://cgit.freedesktop.org/xorg/font/font-jis-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-jis-misc-1.0.3.tar.bz2]] +[[font-micro-misc|http://cgit.freedesktop.org/xorg/font/font-micro-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-micro-misc-1.0.3.tar.bz2]] +[[font-misc-cyrillic|http://cgit.freedesktop.org/xorg/font/font-misc-cyrillic/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-misc-cyrillic-1.0.3.tar.bz2]] +[[font-misc-ethiopic|http://cgit.freedesktop.org/xorg/font/font-misc-ethiopic/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-misc-ethiopic-1.0.3.tar.bz2]] +[[font-misc-meltho|http://cgit.freedesktop.org/xorg/font/font-misc-meltho/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-misc-meltho-1.0.3.tar.bz2]] +[[font-misc-misc|http://cgit.freedesktop.org/xorg/font/font-misc-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.0.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.1.0.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/font/font-misc-misc-1.1.2.tar.bz2]] +[[font-mutt-misc|http://cgit.freedesktop.org/xorg/font/font-mutt-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-mutt-misc-1.0.3.tar.bz2]] +[[font-schumacher-misc|http://cgit.freedesktop.org/xorg/font/font-schumacher-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.0.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.1.0.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/font/font-schumacher-misc-1.1.2.tar.bz2]] +[[font-screen-cyrillic|http://cgit.freedesktop.org/xorg/font/font-screen-cyrillic/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-screen-cyrillic-1.0.4.tar.bz2]] +[[font-sony-misc|http://cgit.freedesktop.org/xorg/font/font-sony-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-sony-misc-1.0.3.tar.bz2]] +[[font-sun-misc|http://cgit.freedesktop.org/xorg/font/font-sun-misc/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-sun-misc-1.0.3.tar.bz2]] +[[font-util|http://cgit.freedesktop.org/xorg/font/font-util/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-util-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-util-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-util-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-util-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-util-1.0.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/font/font-util-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/font/font-util-1.2.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/font/font-util-1.3.0.tar.bz2]] +[[font-winitzki-cyrillic|http://cgit.freedesktop.org/xorg/font/font-winitzki-cyrillic/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/font/font-winitzki-cyrillic-1.0.3.tar.bz2]] +[[font-xfree86-type1|http://cgit.freedesktop.org/xorg/font/font-xfree86-type1/]] | font | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/font/font-xfree86-type1-1.0.4.tar.bz2]] +[[fontcacheproto|http://cgit.freedesktop.org/xorg/proto/fontcacheproto/]] | proto | [[0.1.2|http://xorg.freedesktop.org/releases/individual/proto/fontcacheproto-0.1.2.tar.bz2]] | [[0.1.2|http://xorg.freedesktop.org/releases/individual/proto/fontcacheproto-0.1.2.tar.bz2]] | [[0.1.2|http://xorg.freedesktop.org/releases/individual/proto/fontcacheproto-0.1.2.tar.bz2]] | [[0.1.2|http://xorg.freedesktop.org/releases/individual/proto/fontcacheproto-0.1.2.tar.bz2]] | [[0.1.2|http://xorg.freedesktop.org/releases/individual/proto/fontcacheproto-0.1.2.tar.bz2]] | _none_||| +[[fontsproto|http://cgit.freedesktop.org/xorg/proto/fontsproto/]] | proto | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.0.2.tar.bz2]] | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.0.2.tar.bz2]] | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.0.2.tar.bz2]] | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.0.2.tar.bz2]] | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.0.2.tar.bz2]] | [[2.1.0|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.1.0.tar.bz2]] | [[2.1.1|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.1.1.tar.bz2]] | [[2.1.2|http://xorg.freedesktop.org/releases/individual/proto/fontsproto-2.1.2.tar.bz2]] +[[fonttosfnt|http://cgit.freedesktop.org/xorg/app/fonttosfnt/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fonttosfnt-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fonttosfnt-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/fonttosfnt-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/fonttosfnt-1.0.3.tar.bz2]] | _none_|||| +[[fslsfonts|http://cgit.freedesktop.org/xorg/app/fslsfonts/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fslsfonts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fslsfonts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fslsfonts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fslsfonts-1.0.1.tar.bz2]] | _none_|||| +[[fstobdf|http://cgit.freedesktop.org/xorg/app/fstobdf/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/fstobdf-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/fstobdf-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/fstobdf-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/fstobdf-1.0.2.tar.bz2]] | _none_|||| +[[gccmakedep|http://cgit.freedesktop.org/xorg/util/gccmakedep/]] | util | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/gccmakedep-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/gccmakedep-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/gccmakedep-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/gccmakedep-1.0.2.tar.bz2]] | _none_|||| +[[glproto|http://cgit.freedesktop.org/xorg/proto/glproto/]] | proto | [[1.4.3|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.3.tar.bz2]] | [[1.4.7|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.7.tar.bz2]] | [[1.4.8|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.8.tar.bz2]] | [[1.4.8|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.8.tar.bz2]] | [[1.4.9|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.9.tar.bz2]] | [[1.4.10|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.10.tar.bz2]] | [[1.4.12|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.12.tar.bz2]] | [[1.4.15|http://xorg.freedesktop.org/releases/individual/proto/glproto-1.4.15.tar.bz2]] +[[iceauth|http://cgit.freedesktop.org/xorg/app/iceauth/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/iceauth-1.0.5.tar.bz2]] +[[ico|http://cgit.freedesktop.org/xorg/app/ico/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/ico-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/ico-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/ico-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/ico-1.0.2.tar.bz2]] | _none_|||| +[[imake|http://cgit.freedesktop.org/xorg/util/imake/]] | util | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/imake-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/imake-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/imake-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/imake-1.0.2.tar.bz2]] | _none_|||| +[[inputproto|http://cgit.freedesktop.org/xorg/proto/inputproto/]] | proto | [[1.3.2|http://xorg.freedesktop.org/releases/individual/proto/inputproto-1.3.2.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/proto/inputproto-1.3.2.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/proto/inputproto-1.3.2.tar.bz2]] | [[1.4.2.1|http://xorg.freedesktop.org/releases/individual/proto/inputproto-1.4.2.1.tar.bz2]] | [[1.4.4|http://xorg.freedesktop.org/releases/individual/proto/inputproto-1.4.4.tar.bz2]] | [[2.0|http://xorg.freedesktop.org/releases/individual/proto/inputproto-2.0.tar.bz2]] | [[2.0.1|http://xorg.freedesktop.org/releases/individual/proto/inputproto-2.0.1.tar.bz2]] | [[2.2|http://xorg.freedesktop.org/releases/individual/proto/inputproto-2.2.tar.bz2]] +[[kbproto|http://cgit.freedesktop.org/xorg/proto/kbproto/]] | proto | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/proto/kbproto-1.0.6.tar.bz2]] +[[lbxproxy|http://cgit.freedesktop.org/xorg/app/lbxproxy/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/lbxproxy-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/lbxproxy-1.0.1.tar.bz2]] | _none_|||||| +[[libAppleWM|http://cgit.freedesktop.org/xorg/lib/libAppleWM/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.0.0.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.4.0.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.4.0.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/lib/libAppleWM-1.4.1.tar.bz2]] +[[libFS|http://cgit.freedesktop.org/xorg/lib/libFS/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libFS-1.0.4.tar.bz2]] +[[libICE|http://cgit.freedesktop.org/xorg/lib/libICE/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.4.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.7.tar.bz2]] | [[1.0.8|http://xorg.freedesktop.org/releases/individual/lib/libICE-1.0.8.tar.bz2]] +[[libSM|http://cgit.freedesktop.org/xorg/lib/libSM/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/lib/libSM-1.2.1.tar.bz2]] +[[libWindowsWM|http://cgit.freedesktop.org/xorg/lib/libWindowsWM/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libWindowsWM-1.0.1.tar.bz2]] +[[libX11|http://cgit.freedesktop.org/xorg/lib/libX11/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.0.1.tar.bz2]] | [[1.1|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.1.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.1.3.tar.bz2]] | [[1.1.5|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.1.5.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.3.2.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.4.0.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/lib/libX11-1.5.0.tar.bz2]] +[[libXScrnSaver|http://cgit.freedesktop.org/xorg/lib/libXScrnSaver/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.0.1.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.1.0.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.1.2.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.1.3.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.2.1.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/lib/libXScrnSaver-1.2.2.tar.bz2]] +[[libXTrap|http://cgit.freedesktop.org/xorg/lib/libXTrap/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXTrap-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXTrap-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXTrap-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXTrap-1.0.0.tar.bz2]] | _none_|||| +[[libXau|http://cgit.freedesktop.org/xorg/lib/libXau/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libXau-1.0.7.tar.bz2]] +[[libXaw|http://cgit.freedesktop.org/xorg/lib/libXaw/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.4.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.7.tar.bz2]] | [[1.0.8|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.8.tar.bz2]] | [[1.0.11|http://xorg.freedesktop.org/releases/individual/lib/libXaw-1.0.11.tar.bz2]] +[[libXcomposite|http://cgit.freedesktop.org/xorg/lib/libXcomposite/]] | lib | [[0.2.2.2|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.2.2.2.tar.bz2]] | [[0.3|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.3.tar.bz2]] | [[0.3|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.3.tar.bz2]] | [[0.4.0|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.4.0.tar.bz2]] | [[0.4.0|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.4.0.tar.bz2]] | [[0.4.1|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.4.1.tar.bz2]] | [[0.4.3|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.4.3.tar.bz2]] | [[0.4.3|http://xorg.freedesktop.org/releases/individual/lib/libXcomposite-0.4.3.tar.bz2]] +[[libXcursor|http://cgit.freedesktop.org/xorg/lib/libXcursor/]] | lib | [[1.1.5.2|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.5.2.tar.bz2]] | [[1.1.6|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.6.tar.bz2]] | [[1.1.8|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.8.tar.bz2]] | [[1.1.9|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.9.tar.bz2]] | [[1.1.9|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.9.tar.bz2]] | [[1.1.10|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.10.tar.bz2]] | [[1.1.11|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.11.tar.bz2]] | [[1.1.13|http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.13.tar.bz2]] +[[libXdamage|http://cgit.freedesktop.org/xorg/lib/libXdamage/]] | lib | [[1.0.2.2|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.0.2.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.0.3.tar.bz2]] | [[1.1|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.1.2.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.1.3.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXdamage-1.1.3.tar.bz2]] +[[libXdmcp|http://cgit.freedesktop.org/xorg/lib/libXdmcp/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXdmcp-1.1.1.tar.bz2]] +[[libXevie|http://cgit.freedesktop.org/xorg/lib/libXevie/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXevie-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXevie-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXevie-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXevie-1.0.2.tar.bz2]] | _none_|||| +[[libXext|http://cgit.freedesktop.org/xorg/lib/libXext/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.0.4.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.2.0.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/lib/libXext-1.3.1.tar.bz2]] +[[libXfixes|http://cgit.freedesktop.org/xorg/lib/libXfixes/]] | lib | [[3.0.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-3.0.1.2.tar.bz2]] | [[4.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-4.0.1.tar.bz2]] | [[4.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-4.0.1.tar.bz2]] | [[4.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-4.0.1.tar.bz2]] | [[4.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-4.0.3.tar.bz2]] | [[4.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-4.0.4.tar.bz2]] | [[4.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-4.0.5.tar.bz2]] | [[5.0|http://xorg.freedesktop.org/releases/individual/lib/libXfixes-5.0.tar.bz2]] +[[libXfont|http://cgit.freedesktop.org/xorg/lib/libXfont/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.0.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.1.0.tar.bz2]] | [[1.2.7|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.2.7.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.3.1.tar.bz2]] | [[1.3.3|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.3.3.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.4.1.tar.bz2]] | [[1.4.3|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.4.3.tar.bz2]] | [[1.4.5|http://xorg.freedesktop.org/releases/individual/lib/libXfont-1.4.5.tar.bz2]] +[[libXfontcache|http://cgit.freedesktop.org/xorg/lib/libXfontcache/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXfontcache-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXfontcache-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXfontcache-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXfontcache-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXfontcache-1.0.4.tar.bz2]] | _none_||| +[[libXft|http://cgit.freedesktop.org/xorg/lib/libXft/]] | lib | [[2.1.8.2|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.1.8.2.tar.bz2]] | [[2.1.8.2|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.1.8.2.tar.bz2]] | [[2.1.12|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.1.12.tar.bz2]] | [[2.1.12|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.1.12.tar.bz2]] | [[2.1.13|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.1.13.tar.bz2]] | [[2.1.14|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.1.14.tar.bz2]] | [[2.2.0|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.2.0.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/lib/libXft-2.3.1.tar.bz2]] +[[libXi|http://cgit.freedesktop.org/xorg/lib/libXi/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.0.2.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.1.3.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.1.3.tar.bz2]] | [[1.3|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.3.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.4.0.tar.bz2]] | [[1.6.1|http://xorg.freedesktop.org/releases/individual/lib/libXi-1.6.1.tar.bz2]] +[[libXinerama|http://cgit.freedesktop.org/xorg/lib/libXinerama/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.0.3.tar.bz2]] | [[1.1|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXinerama-1.1.2.tar.bz2]] +[[libXmu|http://cgit.freedesktop.org/xorg/lib/libXmu/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXmu-1.1.1.tar.bz2]] +[[libXp|http://cgit.freedesktop.org/xorg/lib/libXp/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXp-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXp-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXp-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXp-1.0.0.tar.bz2]] | _none_|||| +[[libXpm|http://cgit.freedesktop.org/xorg/lib/libXpm/]] | lib | [[3.5.4.2|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.4.2.tar.bz2]] | [[3.5.5|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.5.tar.bz2]] | [[3.5.6|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.6.tar.bz2]] | [[3.5.7|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.7.tar.bz2]] | [[3.5.7|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.7.tar.bz2]] | [[3.5.8|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.8.tar.bz2]] | [[3.5.9|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.9.tar.bz2]] | [[3.5.10|http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.10.tar.bz2]] +[[libXprintAppUtil|http://cgit.freedesktop.org/xorg/lib/libXprintAppUtil/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintAppUtil-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintAppUtil-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintAppUtil-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintAppUtil-1.0.1.tar.bz2]] | _none_|||| +[[libXprintUtil|http://cgit.freedesktop.org/xorg/lib/libXprintUtil/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintUtil-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintUtil-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintUtil-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXprintUtil-1.0.1.tar.bz2]] | _none_|||| +[[libXrandr|http://cgit.freedesktop.org/xorg/lib/libXrandr/]] | lib | [[1.1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.1.0.2.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.1.2.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.2.2.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.2.3.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.3.0.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.3.1.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.3.2.tar.bz2]] +[[libXrender|http://cgit.freedesktop.org/xorg/lib/libXrender/]] | lib | [[0.9.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.0.2.tar.bz2]] | [[0.9.1|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.1.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.2.tar.bz2]] | [[0.9.4|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.4.tar.bz2]] | [[0.9.4|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.4.tar.bz2]] | [[0.9.5|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.5.tar.bz2]] | [[0.9.6|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.6.tar.bz2]] | [[0.9.7|http://xorg.freedesktop.org/releases/individual/lib/libXrender-0.9.7.tar.bz2]] +[[libXres|http://cgit.freedesktop.org/xorg/lib/libXres/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/lib/libXres-1.0.6.tar.bz2]] +[[libXt|http://cgit.freedesktop.org/xorg/lib/libXt/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.0.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.2.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.5.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.5.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.5.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.7.tar.bz2]] | [[1.0.9|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.0.9.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXt-1.1.3.tar.bz2]] +[[libXtst|http://cgit.freedesktop.org/xorg/lib/libXtst/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/lib/libXtst-1.2.1.tar.bz2]] +[[libXv|http://cgit.freedesktop.org/xorg/lib/libXv/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libXv-1.0.7.tar.bz2]] +[[libXvMC|http://cgit.freedesktop.org/xorg/lib/libXvMC/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libXvMC-1.0.7.tar.bz2]] +[[libXxf86dga|http://cgit.freedesktop.org/xorg/lib/libXxf86dga/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.0.2.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.1.2.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/lib/libXxf86dga-1.1.3.tar.bz2]] +[[libXxf86misc|http://cgit.freedesktop.org/xorg/lib/libXxf86misc/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXxf86misc-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86misc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86misc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86misc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86misc-1.0.1.tar.bz2]] | _none_||| +[[libXxf86vm|http://cgit.freedesktop.org/xorg/lib/libXxf86vm/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libXxf86vm-1.1.2.tar.bz2]] +[[libdmx|http://cgit.freedesktop.org/xorg/lib/libdmx/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/lib/libdmx-1.1.2.tar.bz2]] +[[libfontenc|http://cgit.freedesktop.org/xorg/lib/libfontenc/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/lib/libfontenc-1.1.1.tar.bz2]] +[[liblbxutil|http://cgit.freedesktop.org/xorg/lib/liblbxutil/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/liblbxutil-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/liblbxutil-1.0.1.tar.bz2]] | _none_|||||| +[[liboldX|http://cgit.freedesktop.org/xorg/lib/liboldX/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/liboldX-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/liboldX-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/liboldX-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/liboldX-1.0.1.tar.bz2]] | _none_|||| +[[libpciaccess|http://cgit.freedesktop.org/xorg/lib/libpciaccess/]] | lib | _none_|||| | [[0.10.3|http://xorg.freedesktop.org/releases/individual/lib/libpciaccess-0.10.3.tar.bz2]] | [[0.10.9|http://xorg.freedesktop.org/releases/individual/lib/libpciaccess-0.10.9.tar.bz2]] | [[0.12.0|http://xorg.freedesktop.org/releases/individual/lib/libpciaccess-0.12.0.tar.bz2]] | [[0.13.1|http://xorg.freedesktop.org/releases/individual/lib/libpciaccess-0.13.1.tar.bz2]] +[[libpthread-stubs|http://cgit.freedesktop.org/xorg/lib/libpthread-stubs/]] | lib | _none_|| | [[0.1|http://xorg.freedesktop.org/releases/individual/lib/libpthread-stubs-0.1.tar.bz2]] | [[0.1|http://xorg.freedesktop.org/releases/individual/lib/libpthread-stubs-0.1.tar.bz2]] | _none_|| | [[0.3|http://xorg.freedesktop.org/releases/individual/lib/libpthread-stubs-0.3.tar.bz2]] | [[0.3|http://xorg.freedesktop.org/releases/individual/lib/libpthread-stubs-0.3.tar.bz2]] +[[libxcb|http://cgit.freedesktop.org/xcb/libxcb/]] | xcb | _none_|||||| | [[1.7|http://xorg.freedesktop.org/releases/individual/xcb/libxcb-1.7.tar.bz2]] | [[1.8.1|http://xorg.freedesktop.org/releases/individual/xcb/libxcb-1.8.1.tar.bz2]] +[[libxkbfile|http://cgit.freedesktop.org/xorg/lib/libxkbfile/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.7.tar.bz2]] | [[1.0.8|http://xorg.freedesktop.org/releases/individual/lib/libxkbfile-1.0.8.tar.bz2]] +[[libxkbui|http://cgit.freedesktop.org/xorg/lib/libxkbui/]] | lib | [[1.0.1|http://xorg.freedesktop.org/releases/individual/lib/libxkbui-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libxkbui-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libxkbui-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/lib/libxkbui-1.0.2.tar.bz2]] | _none_|||| +[[listres|http://cgit.freedesktop.org/xorg/app/listres/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/listres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/listres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/listres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/listres-1.0.1.tar.bz2]] | _none_|||| +[[lndir|http://cgit.freedesktop.org/xorg/util/lndir/]] | util | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/lndir-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/lndir-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/lndir-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/lndir-1.0.1.tar.bz2]] | _none_|||| +[[luit|http://cgit.freedesktop.org/xorg/app/luit/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/luit-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/luit-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/luit-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/luit-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/luit-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/luit-1.0.4.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/luit-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/luit-1.1.1.tar.bz2]] +[[makedepend|http://cgit.freedesktop.org/xorg/util/makedepend/]] | util | [[1.0.0|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.4.tar.bz2]] +[[mkcfm|http://cgit.freedesktop.org/xorg/app/mkcfm/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/mkcfm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/mkcfm-1.0.1.tar.bz2]] | _none_|||||| +[[mkcomposecache|http://cgit.freedesktop.org/xorg/app/mkcomposecache/]] | app | _none_|| | [[1.2|http://xorg.freedesktop.org/releases/individual/app/mkcomposecache-1.2.tar.bz2]] | [[1.2|http://xorg.freedesktop.org/releases/individual/app/mkcomposecache-1.2.tar.bz2]] | _none_|||| +[[mkfontdir|http://cgit.freedesktop.org/xorg/app/mkfontdir/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/app/mkfontdir-1.0.7.tar.bz2]] +[[mkfontscale|http://cgit.freedesktop.org/xorg/app/mkfontscale/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.3.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.5.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.7.tar.bz2]] | [[1.0.8|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.0.8.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/mkfontscale-1.1.0.tar.bz2]] +[[oclock|http://cgit.freedesktop.org/xorg/app/oclock/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/oclock-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/oclock-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/oclock-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/oclock-1.0.1.tar.bz2]] | _none_|||| +[[printproto|http://cgit.freedesktop.org/xorg/proto/printproto/]] | proto | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/printproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/printproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/printproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/printproto-1.0.3.tar.bz2]] | _none_|||| +[[proxymngr|http://cgit.freedesktop.org/xorg/app/proxymngr/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/proxymngr-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/proxymngr-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/proxymngr-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/proxymngr-1.0.1.tar.bz2]] | _none_|||| +[[randrproto|http://cgit.freedesktop.org/xorg/proto/randrproto/]] | proto | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.1.2.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.2.1.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.3.1.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.3.2.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.3.2.tar.bz2]] +[[recordproto|http://cgit.freedesktop.org/xorg/proto/recordproto/]] | proto | [[1.13.2|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.13.2.tar.bz2]] | [[1.13.2|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.13.2.tar.bz2]] | [[1.13.2|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.13.2.tar.bz2]] | [[1.13.2|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.13.2.tar.bz2]] | [[1.13.2|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.13.2.tar.bz2]] | [[1.14|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.14.tar.bz2]] | [[1.14.1|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.14.1.tar.bz2]] | [[1.14.2|http://xorg.freedesktop.org/releases/individual/proto/recordproto-1.14.2.tar.bz2]] +[[renderproto|http://cgit.freedesktop.org/xorg/proto/renderproto/]] | proto | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.9.2.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.9.2.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.9.2.tar.bz2]] | [[0.9.3|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.9.3.tar.bz2]] | [[0.9.3|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.9.3.tar.bz2]] | [[0.11|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.11.tar.bz2]] | [[0.11.1|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.11.1.tar.bz2]] | [[0.11.1|http://xorg.freedesktop.org/releases/individual/proto/renderproto-0.11.1.tar.bz2]] +[[resourceproto|http://cgit.freedesktop.org/xorg/proto/resourceproto/]] | proto | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/resourceproto-1.2.0.tar.bz2]] +[[rgb|http://cgit.freedesktop.org/xorg/app/rgb/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/rgb-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/rgb-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/rgb-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/rgb-1.0.1.tar.bz2]] | _none_|||| +[[rstart|http://cgit.freedesktop.org/xorg/app/rstart/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/rstart-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/rstart-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/rstart-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/rstart-1.0.2.tar.bz2]] | _none_|||| +[[scripts|http://cgit.freedesktop.org/xorg/app/scripts/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/scripts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/scripts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/scripts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/scripts-1.0.1.tar.bz2]] | _none_|||| +[[scrnsaverproto|http://cgit.freedesktop.org/xorg/proto/scrnsaverproto/]] | proto | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.2.1.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-1.2.2.tar.bz2]] +[[sessreg|http://cgit.freedesktop.org/xorg/app/sessreg/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.0.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/app/sessreg-1.0.7.tar.bz2]] +[[setxkbmap|http://cgit.freedesktop.org/xorg/app/setxkbmap/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.0.4.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.2.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/app/setxkbmap-1.3.0.tar.bz2]] +[[showfont|http://cgit.freedesktop.org/xorg/app/showfont/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/showfont-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/showfont-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/showfont-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/showfont-1.0.1.tar.bz2]] | _none_|||| +[[smproxy|http://cgit.freedesktop.org/xorg/app/smproxy/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/smproxy-1.0.5.tar.bz2]] +[[trapproto|http://cgit.freedesktop.org/xorg/proto/trapproto/]] | proto | [[3.4.3|http://xorg.freedesktop.org/releases/individual/proto/trapproto-3.4.3.tar.bz2]] | [[3.4.3|http://xorg.freedesktop.org/releases/individual/proto/trapproto-3.4.3.tar.bz2]] | [[3.4.3|http://xorg.freedesktop.org/releases/individual/proto/trapproto-3.4.3.tar.bz2]] | [[3.4.3|http://xorg.freedesktop.org/releases/individual/proto/trapproto-3.4.3.tar.bz2]] | [[3.4.3|http://xorg.freedesktop.org/releases/individual/proto/trapproto-3.4.3.tar.bz2]] | _none_||| +[[twm|http://cgit.freedesktop.org/xorg/app/twm/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/twm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/twm-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/twm-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/twm-1.0.3.tar.bz2]] | _none_|||| +[[util-macros|http://cgit.freedesktop.org/xorg/util/macros/]] | util | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.0.2.tar.bz2]] | [[1.1.5|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.1.5.tar.bz2]] | [[1.1.5|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.1.5.tar.bz2]] | [[1.1.6|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.1.6.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.3.0.tar.bz2]] | [[1.11.0|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.11.0.tar.bz2]] | [[1.17|http://xorg.freedesktop.org/releases/individual/util/util-macros-1.17.tar.bz2]] +[[videoproto|http://cgit.freedesktop.org/xorg/proto/videoproto/]] | proto | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.2.2.tar.bz2]] | [[2.3.0|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.3.0.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.3.1.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/proto/videoproto-2.3.1.tar.bz2]] +[[viewres|http://cgit.freedesktop.org/xorg/app/viewres/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/viewres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/viewres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/viewres-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/viewres-1.0.1.tar.bz2]] | _none_|||| +[[windowswmproto|http://cgit.freedesktop.org/xorg/proto/windowswmproto/]] | proto | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/proto/windowswmproto-1.0.4.tar.bz2]] +[[x11perf|http://cgit.freedesktop.org/xorg/app/x11perf/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.0.1.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.4.1.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.4.1.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.4.1.tar.bz2]] | [[1.5|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.5.tar.bz2]] | [[1.5.1|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.5.1.tar.bz2]] | [[1.5.2|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.5.2.tar.bz2]] | [[1.5.4|http://xorg.freedesktop.org/releases/individual/app/x11perf-1.5.4.tar.bz2]] +[[xauth|http://cgit.freedesktop.org/xorg/app/xauth/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.5.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/app/xauth-1.0.7.tar.bz2]] +[[xbacklight|http://cgit.freedesktop.org/xorg/data/xbacklight/]] | data | _none_||| | [[1.1|http://xorg.freedesktop.org/releases/individual/data/xbacklight-1.1.tar.bz2]] | [[1.1|http://xorg.freedesktop.org/releases/individual/data/xbacklight-1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/data/xbacklight-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/data/xbacklight-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/data/xbacklight-1.1.2.tar.bz2]] +[[xbiff|http://cgit.freedesktop.org/xorg/app/xbiff/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xbiff-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xbiff-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xbiff-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xbiff-1.0.1.tar.bz2]] | _none_|||| +[[xbitmaps|http://cgit.freedesktop.org/xorg/data/xbitmaps/]] | data | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.0.1.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/data/xbitmaps-1.1.1.tar.bz2]] +[[xcalc|http://cgit.freedesktop.org/xorg/app/xcalc/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcalc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcalc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcalc-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xcalc-1.0.2.tar.bz2]] | _none_|||| +[[xcb-proto|http://cgit.freedesktop.org/xcb/proto/]] | xcb | _none_|||||| | [[1.6|http://xorg.freedesktop.org/releases/individual/xcb/xcb-proto-1.6.tar.bz2]] | [[1.7.1|http://xorg.freedesktop.org/releases/individual/xcb/xcb-proto-1.7.1.tar.bz2]] +[[xclipboard|http://cgit.freedesktop.org/xorg/app/xclipboard/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xclipboard-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xclipboard-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xclipboard-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xclipboard-1.0.1.tar.bz2]] | _none_|||| +[[xclock|http://cgit.freedesktop.org/xorg/app/xclock/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xclock-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xclock-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xclock-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xclock-1.0.3.tar.bz2]] | _none_|||| +[[xcmiscproto|http://cgit.freedesktop.org/xorg/proto/xcmiscproto/]] | proto | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.1.2.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.2.1.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/proto/xcmiscproto-1.2.2.tar.bz2]] +[[xcmsdb|http://cgit.freedesktop.org/xorg/app/xcmsdb/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xcmsdb-1.0.4.tar.bz2]] +[[xconsole|http://cgit.freedesktop.org/xorg/app/xconsole/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xconsole-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xconsole-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xconsole-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xconsole-1.0.3.tar.bz2]] | _none_|||| +[[xcursor-themes|http://cgit.freedesktop.org/xorg/data/xcursor-themes/]] | data | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/data/xcursor-themes-1.0.3.tar.bz2]] +[[xcursorgen|http://cgit.freedesktop.org/xorg/app/xcursorgen/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xcursorgen-1.0.5.tar.bz2]] +[[xdbedizzy|http://cgit.freedesktop.org/xorg/app/xdbedizzy/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdbedizzy-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdbedizzy-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xdbedizzy-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xdbedizzy-1.0.2.tar.bz2]] | _none_|||| +[[xditview|http://cgit.freedesktop.org/xorg/app/xditview/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xditview-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xditview-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xditview-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xditview-1.0.1.tar.bz2]] | _none_|||| +[[xdm|http://cgit.freedesktop.org/xorg/app/xdm/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdm-1.0.1.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xdm-1.0.4.tar.bz2]] | [[1.1.4|http://xorg.freedesktop.org/releases/individual/app/xdm-1.1.4.tar.bz2]] | [[1.1.6|http://xorg.freedesktop.org/releases/individual/app/xdm-1.1.6.tar.bz2]] | _none_|||| +[[xdpyinfo|http://cgit.freedesktop.org/xorg/app/xdpyinfo/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.2.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.3.0.tar.bz2]] +[[xdriinfo|http://cgit.freedesktop.org/xorg/app/xdriinfo/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xdriinfo-1.0.4.tar.bz2]] +[[xedit|http://cgit.freedesktop.org/xorg/app/xedit/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xedit-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xedit-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xedit-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xedit-1.0.2.tar.bz2]] | _none_|||| +[[xev|http://cgit.freedesktop.org/xorg/app/xev/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xev-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xev-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xev-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xev-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xev-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xev-1.0.4.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xev-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/app/xev-1.2.0.tar.bz2]] +[[xextproto|http://cgit.freedesktop.org/xorg/proto/xextproto/]] | proto | [[7.0.2|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.2.tar.bz2]] | [[7.0.2|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.2.tar.bz2]] | [[7.0.2|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.2.tar.bz2]] | [[7.0.2|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.2.tar.bz2]] | [[7.0.3|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.0.3.tar.bz2]] | [[7.1.1|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.1.1.tar.bz2]] | [[7.1.2|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.1.2.tar.bz2]] | [[7.2.1|http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.2.1.tar.bz2]] +[[xeyes|http://cgit.freedesktop.org/xorg/app/xeyes/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xeyes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xeyes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xeyes-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xeyes-1.0.1.tar.bz2]] | _none_|||| +[[xf86-input-acecad|http://cgit.freedesktop.org/xorg/driver/xf86-input-acecad/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.2.0.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.2.2.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.4.0.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-acecad-1.4.0.tar.bz2]] | _none_ +[[xf86-input-aiptek|http://cgit.freedesktop.org/xorg/driver/xf86-input-aiptek/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.0.0.5.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.0.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.1.1.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.3.0.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-aiptek-1.3.1.tar.bz2]] | _none_ +[[xf86-input-calcomp|http://cgit.freedesktop.org/xorg/driver/xf86-input-calcomp/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-calcomp-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-calcomp-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-calcomp-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-calcomp-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-citron|http://cgit.freedesktop.org/xorg/driver/xf86-input-citron/]] | driver | [[2.1.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-citron-2.1.1.5.tar.bz2]] | [[2.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-citron-2.2.0.tar.bz2]] | [[2.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-citron-2.2.0.tar.bz2]] | [[2.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-citron-2.2.0.tar.bz2]] | _none_|||| +[[xf86-input-digitaledge|http://cgit.freedesktop.org/xorg/driver/xf86-input-digitaledge/]] | driver | [[1.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-digitaledge-1.0.1.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-digitaledge-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-digitaledge-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-digitaledge-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-dmc|http://cgit.freedesktop.org/xorg/driver/xf86-input-dmc/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dmc-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dmc-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dmc-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dmc-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-dynapro|http://cgit.freedesktop.org/xorg/driver/xf86-input-dynapro/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dynapro-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dynapro-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dynapro-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-dynapro-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-elo2300|http://cgit.freedesktop.org/xorg/driver/xf86-input-elo2300/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elo2300-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elo2300-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elo2300-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elo2300-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-elographics|http://cgit.freedesktop.org/xorg/driver/xf86-input-elographics/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elographics-1.0.0.5.tar.bz2]] | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elographics-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elographics-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-elographics-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-evdev|http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-1.0.0.5.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-1.1.2.tar.bz2]] | [[1.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-1.1.5.tar.bz2]] | [[1.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-1.1.5.tar.bz2]] | [[2.0.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-2.0.4.tar.bz2]] | [[2.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-2.3.0.tar.bz2]] | [[2.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-2.5.0.tar.bz2]] | [[2.7.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-evdev-2.7.0.tar.bz2]] +[[xf86-input-fpit|http://cgit.freedesktop.org/xorg/driver/xf86-input-fpit/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-fpit-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-fpit-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-fpit-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-fpit-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-hyperpen|http://cgit.freedesktop.org/xorg/driver/xf86-input-hyperpen/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-hyperpen-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-hyperpen-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-hyperpen-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-hyperpen-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-jamstudio|http://cgit.freedesktop.org/xorg/driver/xf86-input-jamstudio/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-jamstudio-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-jamstudio-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-jamstudio-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-jamstudio-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-joystick|http://cgit.freedesktop.org/xorg/driver/xf86-input-joystick/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.1.0.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.2.3.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.3.2.tar.bz2]] | [[1.4.99.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.4.99.2.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.5.0.tar.bz2]] | [[1.6.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-joystick-1.6.1.tar.bz2]] +[[xf86-input-keyboard|http://cgit.freedesktop.org/xorg/driver/xf86-input-keyboard/]] | driver | [[1.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.0.1.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.1.1.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.2.2.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.3.1.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.4.0.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.5.0.tar.bz2]] | [[1.6.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-keyboard-1.6.1.tar.bz2]] +[[xf86-input-magellan|http://cgit.freedesktop.org/xorg/driver/xf86-input-magellan/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magellan-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magellan-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magellan-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magellan-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-magictouch|http://cgit.freedesktop.org/xorg/driver/xf86-input-magictouch/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magictouch-1.0.0.5.tar.bz2]] | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magictouch-1.0.0.5.tar.bz2]] | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magictouch-1.0.0.5.tar.bz2]] | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-magictouch-1.0.0.5.tar.bz2]] | _none_|||| +[[xf86-input-microtouch|http://cgit.freedesktop.org/xorg/driver/xf86-input-microtouch/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-microtouch-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-microtouch-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-microtouch-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-microtouch-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-mouse|http://cgit.freedesktop.org/xorg/driver/xf86-input-mouse/]] | driver | [[1.0.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.0.3.1.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.1.0.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.1.2.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.2.2.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.3.0.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.5.0.tar.bz2]] | [[1.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.6.0.tar.bz2]] | [[1.7.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mouse-1.7.2.tar.bz2]] +[[xf86-input-mutouch|http://cgit.freedesktop.org/xorg/driver/xf86-input-mutouch/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mutouch-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mutouch-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mutouch-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-mutouch-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-palmax|http://cgit.freedesktop.org/xorg/driver/xf86-input-palmax/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-palmax-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-palmax-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-palmax-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-palmax-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-penmount|http://cgit.freedesktop.org/xorg/driver/xf86-input-penmount/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-penmount-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-penmount-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-penmount-1.2.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-penmount-1.2.0.tar.bz2]] | _none_|||| +[[xf86-input-spaceorb|http://cgit.freedesktop.org/xorg/driver/xf86-input-spaceorb/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-spaceorb-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-spaceorb-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-spaceorb-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-spaceorb-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-summa|http://cgit.freedesktop.org/xorg/driver/xf86-input-summa/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-summa-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-summa-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-summa-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-summa-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-synaptics|http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/]] | driver | _none_|||| | [[0.15.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-synaptics-0.15.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-synaptics-1.2.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-synaptics-1.3.0.tar.bz2]] | [[1.6.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-synaptics-1.6.1.tar.bz2]] +[[xf86-input-tek4957|http://cgit.freedesktop.org/xorg/driver/xf86-input-tek4957/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-tek4957-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-tek4957-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-tek4957-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-tek4957-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-ur98|http://cgit.freedesktop.org/xorg/driver/xf86-input-ur98/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-ur98-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-ur98-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-ur98-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-ur98-1.1.0.tar.bz2]] | _none_|||| +[[xf86-input-vmmouse|http://cgit.freedesktop.org/xorg/driver/xf86-input-vmmouse/]] | driver | _none_ | [[12.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.4.0.tar.bz2]] | [[12.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.4.0.tar.bz2]] | [[12.4.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.4.1.tar.bz2]] | [[12.5.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.5.1.tar.bz2]] | [[12.6.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.6.5.tar.bz2]] | [[12.6.10|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.6.10.tar.bz2]] | [[12.8.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-vmmouse-12.8.0.tar.bz2]] +[[xf86-input-void|http://cgit.freedesktop.org/xorg/driver/xf86-input-void/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.1.1.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.3.0.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.3.1.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-input-void-1.4.0.tar.bz2]] +[[xf86-video-apm|http://cgit.freedesktop.org/xorg/driver/xf86-video-apm/]] | driver | [[1.0.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.0.1.5.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.2.0.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.2.2.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-apm-1.2.3.tar.bz2]] | _none_ +[[xf86-video-ark|http://cgit.freedesktop.org/xorg/driver/xf86-video-ark/]] | driver | [[0.5.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.5.0.5.tar.bz2]] | [[0.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.6.0.tar.bz2]] | [[0.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.6.0.tar.bz2]] | [[0.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.6.0.tar.bz2]] | [[0.7.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.7.0.tar.bz2]] | [[0.7.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.7.2.tar.bz2]] | [[0.7.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.7.3.tar.bz2]] | [[0.7.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ark-0.7.4.tar.bz2]] +[[xf86-video-ast|http://cgit.freedesktop.org/xorg/driver/xf86-video-ast/]] | driver | _none_ | [[0.81.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.81.0.tar.bz2]] | [[0.81.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.81.0.tar.bz2]] | [[0.81.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.81.0.tar.bz2]] | [[0.85.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.85.0.tar.bz2]] | [[0.89.9|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.89.9.tar.bz2]] | [[0.91.10|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.91.10.tar.bz2]] | [[0.93.10|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-0.93.10.tar.bz2]] +[[xf86-video-ati|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/]] | driver | [[6.5.7.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.5.7.3.tar.bz2]] | [[6.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.6.0.tar.bz2]] | [[6.6.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.6.3.tar.bz2]] | [[6.6.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.6.3.tar.bz2]] | [[6.9.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.9.0.tar.bz2]] | [[6.12.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.12.4.tar.bz2]] | [[6.13.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.13.2.tar.bz2]] | [[6.14.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.14.4.tar.bz2]] +[[xf86-video-chips|http://cgit.freedesktop.org/xorg/driver/xf86-video-chips/]] | driver | [[1.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.0.1.3.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.2.0.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.2.2.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-chips-1.2.3.tar.bz2]] | _none_ +[[xf86-video-cirrus|http://cgit.freedesktop.org/xorg/driver/xf86-video-cirrus/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.1.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.2.1.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.3.2.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.3.2.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cirrus-1.4.0.tar.bz2]] +[[xf86-video-cyrix|http://cgit.freedesktop.org/xorg/driver/xf86-video-cyrix/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cyrix-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cyrix-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cyrix-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-cyrix-1.1.0.tar.bz2]] | _none_|||| +[[xf86-video-dummy|http://cgit.freedesktop.org/xorg/driver/xf86-video-dummy/]] | driver | [[0.1.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.1.0.5.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.2.0.tar.bz2]] | [[0.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.3.0.tar.bz2]] | [[0.3.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.3.2.tar.bz2]] | [[0.3.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.3.4.tar.bz2]] | [[0.3.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-dummy-0.3.5.tar.bz2]] +[[xf86-video-fbdev|http://cgit.freedesktop.org/xorg/driver/xf86-video-fbdev/]] | driver | [[0.1.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.1.0.5.tar.bz2]] | [[0.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.3.0.tar.bz2]] | [[0.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.3.1.tar.bz2]] | [[0.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.3.1.tar.bz2]] | [[0.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.4.0.tar.bz2]] | [[0.4.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.4.1.tar.bz2]] | [[0.4.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.4.2.tar.bz2]] | [[0.4.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-fbdev-0.4.2.tar.bz2]] +[[xf86-video-geode|http://cgit.freedesktop.org/xorg/driver/xf86-video-geode/]] | driver | _none_|||| | [[2.10.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-geode-2.10.1.tar.bz2]] | [[2.11.6|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-geode-2.11.6.tar.bz2]] | [[2.11.10|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-geode-2.11.10.tar.bz2]] | [[2.11.13|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-geode-2.11.13.tar.bz2]] +[[xf86-video-glide|http://cgit.freedesktop.org/xorg/driver/xf86-video-glide/]] | driver | _none_||| | [[1.0.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glide-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glide-1.0.1.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glide-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glide-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glide-1.2.0.tar.bz2]] +[[xf86-video-glint|http://cgit.freedesktop.org/xorg/driver/xf86-video-glint/]] | driver | [[1.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.0.1.3.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.1.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.2.1.tar.bz2]] | [[1.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.2.4.tar.bz2]] | [[1.2.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.2.5.tar.bz2]] | [[1.2.7|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-glint-1.2.7.tar.bz2]] +[[xf86-video-i128|http://cgit.freedesktop.org/xorg/driver/xf86-video-i128/]] | driver | [[1.1.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.1.0.5.tar.bz2]] | [[1.1.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.1.0.5.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.2.1.tar.bz2]] | [[1.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.3.1.tar.bz2]] | [[1.3.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.3.3.tar.bz2]] | [[1.3.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.3.4.tar.bz2]] | [[1.3.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i128-1.3.5.tar.bz2]] +[[xf86-video-i740|http://cgit.freedesktop.org/xorg/driver/xf86-video-i740/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.2.0.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.3.2.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i740-1.3.2.tar.bz2]] | _none_ +[[xf86-video-i810|http://cgit.freedesktop.org/xorg/driver/xf86-video-i810/]] | driver | [[1.4.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i810-1.4.1.3.tar.bz2]] | [[1.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i810-1.6.0.tar.bz2]] | [[1.7.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i810-1.7.4.tar.bz2]] | [[1.7.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i810-1.7.4.tar.bz2]] | _none_|||| +[[xf86-video-impact|http://cgit.freedesktop.org/xorg/driver/xf86-video-impact/]] | driver | _none_|| | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-impact-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-impact-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-impact-0.2.0.tar.bz2]] | _none_||| +[[xf86-video-imstt|http://cgit.freedesktop.org/xorg/driver/xf86-video-imstt/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-imstt-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-imstt-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-imstt-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-imstt-1.1.0.tar.bz2]] | _none_|||| +[[xf86-video-intel|http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/]] | driver | _none_||| | [[2.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel-2.1.1.tar.bz2]] | [[2.4.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel-2.4.2.tar.bz2]] | [[2.9.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel-2.9.1.tar.bz2]] | [[2.13.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel-2.13.0.tar.bz2]] | [[2.19.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel-2.19.0.tar.bz2]] +[[xf86-video-mach64|http://cgit.freedesktop.org/xorg/driver/xf86-video-mach64/]] | driver | _none_|||| | [[6.8.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mach64-6.8.0.tar.bz2]] | [[6.8.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mach64-6.8.2.tar.bz2]] | [[6.8.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mach64-6.8.2.tar.bz2]] | [[6.9.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mach64-6.9.1.tar.bz2]] +[[xf86-video-mga|http://cgit.freedesktop.org/xorg/driver/xf86-video-mga/]] | driver | [[1.2.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.2.1.3.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.4.1.tar.bz2]] | [[1.4.6|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.4.6.tar.bz2]] | [[1.4.6|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.4.6.tar.bz2]] | [[1.4.9|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.4.9.tar.bz2]] | [[1.4.11|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.4.11.tar.bz2]] | [[1.4.13|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.4.13.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-mga-1.5.0.tar.bz2]] +[[xf86-video-neomagic|http://cgit.freedesktop.org/xorg/driver/xf86-video-neomagic/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.0.0.5.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.1.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.2.1.tar.bz2]] | [[1.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.2.4.tar.bz2]] | [[1.2.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.2.5.tar.bz2]] | [[1.2.6|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-neomagic-1.2.6.tar.bz2]] +[[xf86-video-newport|http://cgit.freedesktop.org/xorg/driver/xf86-video-newport/]] | driver | [[0.1.4.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.1.4.1.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.0.tar.bz2]] | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.1.tar.bz2]] | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.1.tar.bz2]] | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.1.tar.bz2]] | [[0.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.3.tar.bz2]] | [[0.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.3.tar.bz2]] | [[0.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-newport-0.2.4.tar.bz2]] +[[xf86-video-nsc|http://cgit.freedesktop.org/xorg/driver/xf86-video-nsc/]] | driver | [[2.7.6.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nsc-2.7.6.5.tar.bz2]] | [[2.8.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nsc-2.8.1.tar.bz2]] | [[2.8.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nsc-2.8.2.tar.bz2]] | [[2.8.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nsc-2.8.3.tar.bz2]] | _none_|||| +[[xf86-video-nv|http://cgit.freedesktop.org/xorg/driver/xf86-video-nv/]] | driver | [[1.0.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-1.0.1.5.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-1.1.1.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-1.2.2.tar.bz2]] | [[2.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-2.1.3.tar.bz2]] | [[2.1.12|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-2.1.12.tar.bz2]] | [[2.1.15|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-2.1.15.tar.bz2]] | [[2.1.18|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-2.1.18.tar.bz2]] | [[2.1.18|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-nv-2.1.18.tar.bz2]] +[[xf86-video-openchrome|http://cgit.freedesktop.org/openchrome/xf86-video-openchrome/]] | driver | _none_|||| | [[0.2.903|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-openchrome-0.2.903.tar.bz2]] | [[0.2.904|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-openchrome-0.2.904.tar.bz2]] | [[0.2.904|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-openchrome-0.2.904.tar.bz2]] | [[0.2.906|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-openchrome-0.2.906.tar.bz2]] +[[xf86-video-r128|http://cgit.freedesktop.org/xorg/driver/xf86-video-r128/]] | driver | _none_|||| | [[6.8.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-r128-6.8.0.tar.bz2]] | [[6.8.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-r128-6.8.1.tar.bz2]] | [[6.8.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-r128-6.8.1.tar.bz2]] | [[6.8.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-r128-6.8.2.tar.bz2]] +[[xf86-video-rendition|http://cgit.freedesktop.org/xorg/driver/xf86-video-rendition/]] | driver | [[4.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.0.1.3.tar.bz2]] | [[4.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.1.0.tar.bz2]] | [[4.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.1.3.tar.bz2]] | [[4.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.1.3.tar.bz2]] | [[4.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.2.0.tar.bz2]] | [[4.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.2.3.tar.bz2]] | [[4.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-rendition-4.2.4.tar.bz2]] | _none_ +[[xf86-video-s3|http://cgit.freedesktop.org/xorg/driver/xf86-video-s3/]] | driver | [[0.3.5.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.3.5.5.tar.bz2]] | [[0.4.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.4.1.tar.bz2]] | [[0.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.5.0.tar.bz2]] | [[0.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.5.0.tar.bz2]] | [[0.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.6.0.tar.bz2]] | [[0.6.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.6.3.tar.bz2]] | [[0.6.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3-0.6.3.tar.bz2]] | _none_ +[[xf86-video-s3virge|http://cgit.freedesktop.org/xorg/driver/xf86-video-s3virge/]] | driver | [[1.8.6.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.8.6.5.tar.bz2]] | [[1.9.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.9.1.tar.bz2]] | [[1.9.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.9.1.tar.bz2]] | [[1.9.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.9.1.tar.bz2]] | [[1.10.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.10.1.tar.bz2]] | [[1.10.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.10.4.tar.bz2]] | [[1.10.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-s3virge-1.10.4.tar.bz2]] | _none_ +[[xf86-video-savage|http://cgit.freedesktop.org/xorg/driver/xf86-video-savage/]] | driver | [[2.0.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.0.2.3.tar.bz2]] | [[2.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.1.1.tar.bz2]] | [[2.1.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.1.2.tar.bz2]] | [[2.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.1.3.tar.bz2]] | [[2.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.2.1.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.3.1.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.3.1.tar.bz2]] | [[2.3.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-savage-2.3.4.tar.bz2]] +[[xf86-video-siliconmotion|http://cgit.freedesktop.org/xorg/driver/xf86-video-siliconmotion/]] | driver | [[1.3.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.3.1.5.tar.bz2]] | [[1.4.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.4.1.tar.bz2]] | [[1.4.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.4.2.tar.bz2]] | [[1.4.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.4.2.tar.bz2]] | [[1.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.6.0.tar.bz2]] | [[1.7.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.7.3.tar.bz2]] | [[1.7.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.7.4.tar.bz2]] | [[1.7.6|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-siliconmotion-1.7.6.tar.bz2]] +[[xf86-video-sis|http://cgit.freedesktop.org/xorg/driver/xf86-video-sis/]] | driver | [[0.8.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.8.1.3.tar.bz2]] | [[0.9.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.9.1.tar.bz2]] | [[0.9.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.9.3.tar.bz2]] | [[0.9.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.9.3.tar.bz2]] | [[0.10.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.10.0.tar.bz2]] | [[0.10.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.10.2.tar.bz2]] | [[0.10.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.10.3.tar.bz2]] | [[0.10.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sis-0.10.4.tar.bz2]] +[[xf86-video-sisusb|http://cgit.freedesktop.org/xorg/driver/xf86-video-sisusb/]] | driver | [[0.7.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.7.1.3.tar.bz2]] | [[0.8.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.8.1.tar.bz2]] | [[0.8.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.8.1.tar.bz2]] | [[0.8.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.8.1.tar.bz2]] | [[0.9.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.9.0.tar.bz2]] | [[0.9.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.9.3.tar.bz2]] | [[0.9.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sisusb-0.9.4.tar.bz2]] | _none_ +[[xf86-video-sunbw2|http://cgit.freedesktop.org/xorg/driver/xf86-video-sunbw2/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunbw2-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunbw2-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunbw2-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunbw2-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunbw2-1.1.0.tar.bz2]] | _none_||| +[[xf86-video-suncg14|http://cgit.freedesktop.org/xorg/driver/xf86-video-suncg14/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg14-1.1.1.tar.bz2]] | _none_ +[[xf86-video-suncg3|http://cgit.freedesktop.org/xorg/driver/xf86-video-suncg3/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg3-1.1.1.tar.bz2]] | _none_ +[[xf86-video-suncg6|http://cgit.freedesktop.org/xorg/driver/xf86-video-suncg6/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suncg6-1.1.1.tar.bz2]] +[[xf86-video-sunffb|http://cgit.freedesktop.org/xorg/driver/xf86-video-sunffb/]] | driver | [[1.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.0.1.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunffb-1.2.1.tar.bz2]] +[[xf86-video-sunleo|http://cgit.freedesktop.org/xorg/driver/xf86-video-sunleo/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.2.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.2.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-sunleo-1.2.0.tar.bz2]] | _none_ +[[xf86-video-suntcx|http://cgit.freedesktop.org/xorg/driver/xf86-video-suntcx/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-suntcx-1.1.1.tar.bz2]] | _none_ +[[xf86-video-tdfx|http://cgit.freedesktop.org/xorg/driver/xf86-video-tdfx/]] | driver | [[1.1.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.1.1.3.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.2.1.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.3.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.3.0.tar.bz2]] | [[1.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.4.0.tar.bz2]] | [[1.4.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.4.3.tar.bz2]] | [[1.4.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.4.3.tar.bz2]] | [[1.4.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tdfx-1.4.4.tar.bz2]] +[[xf86-video-tga|http://cgit.freedesktop.org/xorg/driver/xf86-video-tga/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.2.1.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tga-1.2.1.tar.bz2]] +[[xf86-video-trident|http://cgit.freedesktop.org/xorg/driver/xf86-video-trident/]] | driver | [[1.0.1.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.0.1.2.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.2.1.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.2.3.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.2.3.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.3.0.tar.bz2]] | [[1.3.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.3.3.tar.bz2]] | [[1.3.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.3.4.tar.bz2]] | [[1.3.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-trident-1.3.5.tar.bz2]] +[[xf86-video-tseng|http://cgit.freedesktop.org/xorg/driver/xf86-video-tseng/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.2.0.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.2.3.tar.bz2]] | [[1.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-tseng-1.2.4.tar.bz2]] | _none_ +[[xf86-video-v4l|http://cgit.freedesktop.org/xorg/driver/xf86-video-v4l/]] | driver | [[0.0.1.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.0.1.5.tar.bz2]] | [[0.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.1.1.tar.bz2]] | [[0.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.1.1.tar.bz2]] | [[0.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.1.1.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.2.0.tar.bz2]] | [[0.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-v4l-0.2.0.tar.bz2]] +[[xf86-video-vermilion|http://cgit.freedesktop.org/xorg/driver/xf86-video-vermilion/]] | driver | _none_||| | [[1.0.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vermilion-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vermilion-1.0.1.tar.bz2]] | _none_||| +[[xf86-video-vesa|http://cgit.freedesktop.org/xorg/driver/xf86-video-vesa/]] | driver | [[1.0.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-1.0.1.3.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-1.2.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-1.3.0.tar.bz2]] | [[1.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-1.3.0.tar.bz2]] | [[2.0.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-2.0.0.tar.bz2]] | [[2.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-2.2.1.tar.bz2]] | [[2.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-2.3.0.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-2.3.1.tar.bz2]] +[[xf86-video-vga|http://cgit.freedesktop.org/xorg/driver/xf86-video-vga/]] | driver | [[4.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vga-4.0.0.5.tar.bz2]] | [[4.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vga-4.1.0.tar.bz2]] | [[4.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vga-4.1.0.tar.bz2]] | [[4.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vga-4.1.0.tar.bz2]] | _none_|||| +[[xf86-video-via|http://cgit.freedesktop.org/xorg/driver/xf86-video-via/]] | driver | [[0.1.33.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-via-0.1.33.2.tar.bz2]] | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-via-0.2.1.tar.bz2]] | [[0.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-via-0.2.2.tar.bz2]] | [[0.2.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-via-0.2.2.tar.bz2]] | _none_|||| +[[xf86-video-vmware|http://cgit.freedesktop.org/xorg/driver/xf86-video-vmware/]] | driver | [[10.11.1.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-10.11.1.3.tar.bz2]] | [[10.13.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-10.13.0.tar.bz2]] | [[10.14.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-10.14.1.tar.bz2]] | [[10.14.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-10.14.1.tar.bz2]] | [[10.16.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-10.16.5.tar.bz2]] | [[10.16.8|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-10.16.8.tar.bz2]] | [[11.0.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-11.0.3.tar.bz2]] | [[12.0.2|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vmware-12.0.2.tar.bz2]] +[[xf86-video-voodoo|http://cgit.freedesktop.org/xorg/driver/xf86-video-voodoo/]] | driver | [[1.0.0.5|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.0.0.5.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.2.0.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.2.3.tar.bz2]] | [[1.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.2.4.tar.bz2]] | [[1.2.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-voodoo-1.2.4.tar.bz2]] +[[xf86-video-wsfb|http://cgit.freedesktop.org/xorg/driver/xf86-video-wsfb/]] | driver | _none_|| | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-wsfb-0.2.1.tar.bz2]] | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-wsfb-0.2.1.tar.bz2]] | [[0.2.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-wsfb-0.2.1.tar.bz2]] | [[0.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-wsfb-0.3.0.tar.bz2]] | [[0.3.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-wsfb-0.3.0.tar.bz2]] | [[0.4.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-wsfb-0.4.0.tar.bz2]] +[[xf86-video-xgi|http://cgit.freedesktop.org/xorg/driver/xf86-video-xgi/]] | driver | _none_|||| | [[1.5.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-xgi-1.5.0.tar.bz2]] | [[1.5.1|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-xgi-1.5.1.tar.bz2]] | [[1.6.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-xgi-1.6.0.tar.bz2]] | _none_ +[[xf86-video-xgixp|http://cgit.freedesktop.org/xorg/driver/xf86-video-xgixp/]] | driver | _none_|||| | [[1.7.99.3|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-xgixp-1.7.99.3.tar.bz2]] | [[1.7.99.4|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-xgixp-1.7.99.4.tar.bz2]] | [[1.8.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-xgixp-1.8.0.tar.bz2]] | _none_ +[[xf86bigfontproto|http://cgit.freedesktop.org/xorg/proto/xf86bigfontproto/]] | proto | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.1.2.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.2.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.2.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/proto/xf86bigfontproto-1.2.0.tar.bz2]] +[[xf86dga|http://cgit.freedesktop.org/xorg/app/xf86dga/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xf86dga-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xf86dga-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xf86dga-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xf86dga-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xf86dga-1.0.2.tar.bz2]] | _none_||| +[[xf86dgaproto|http://cgit.freedesktop.org/xorg/proto/xf86dgaproto/]] | proto | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.0.2.tar.bz2]] | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.0.2.tar.bz2]] | [[2.0.2|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.0.2.tar.bz2]] | [[2.0.3|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.0.3.tar.bz2]] | [[2.0.3|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.0.3.tar.bz2]] | [[2.1|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.1.tar.bz2]] | [[2.1|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.1.tar.bz2]] | [[2.1|http://xorg.freedesktop.org/releases/individual/proto/xf86dgaproto-2.1.tar.bz2]] +[[xf86driproto|http://cgit.freedesktop.org/xorg/proto/xf86driproto/]] | proto | [[2.0.3|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.0.3.tar.bz2]] | [[2.0.3|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.0.3.tar.bz2]] | [[2.0.3|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.0.3.tar.bz2]] | [[2.0.3|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.0.3.tar.bz2]] | [[2.0.4|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.0.4.tar.bz2]] | [[2.1.0|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.1.0.tar.bz2]] | [[2.1.0|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.1.0.tar.bz2]] | [[2.1.1|http://xorg.freedesktop.org/releases/individual/proto/xf86driproto-2.1.1.tar.bz2]] +[[xf86miscproto|http://cgit.freedesktop.org/xorg/proto/xf86miscproto/]] | proto | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/xf86miscproto-0.9.2.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/xf86miscproto-0.9.2.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/xf86miscproto-0.9.2.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/xf86miscproto-0.9.2.tar.bz2]] | [[0.9.2|http://xorg.freedesktop.org/releases/individual/proto/xf86miscproto-0.9.2.tar.bz2]] | _none_||| +[[xf86rushproto|http://cgit.freedesktop.org/xorg/proto/xf86rushproto/]] | proto | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86rushproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86rushproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86rushproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xf86rushproto-1.1.2.tar.bz2]] | _none_|||| +[[xf86vidmodeproto|http://cgit.freedesktop.org/xorg/proto/xf86vidmodeproto/]] | proto | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.2.2.tar.bz2]] | [[2.2.2|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.2.2.tar.bz2]] | [[2.3|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.3.tar.bz2]] | [[2.3|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.3.tar.bz2]] | [[2.3.1|http://xorg.freedesktop.org/releases/individual/proto/xf86vidmodeproto-2.3.1.tar.bz2]] +[[xfd|http://cgit.freedesktop.org/xorg/app/xfd/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfd-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfd-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfd-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfd-1.0.1.tar.bz2]] | _none_|||| +[[xfindproxy|http://cgit.freedesktop.org/xorg/app/xfindproxy/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfindproxy-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfindproxy-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfindproxy-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfindproxy-1.0.1.tar.bz2]] | _none_|||| +[[xfontsel|http://cgit.freedesktop.org/xorg/app/xfontsel/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfontsel-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfontsel-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xfontsel-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xfontsel-1.0.2.tar.bz2]] | _none_|||| +[[xfs|http://cgit.freedesktop.org/xorg/app/xfs/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfs-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xfs-1.0.2.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xfs-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xfs-1.0.4.tar.bz2]] | _none_|||| +[[xfsinfo|http://cgit.freedesktop.org/xorg/app/xfsinfo/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfsinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfsinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfsinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfsinfo-1.0.1.tar.bz2]] | _none_|||| +[[xfwp|http://cgit.freedesktop.org/xorg/app/xfwp/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfwp-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfwp-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfwp-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xfwp-1.0.1.tar.bz2]] | _none_|||| +[[xgamma|http://cgit.freedesktop.org/xorg/app/xgamma/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xgamma-1.0.5.tar.bz2]] +[[xgc|http://cgit.freedesktop.org/xorg/app/xgc/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgc-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xgc-1.0.1.tar.bz2]] | _none_|||| +[[xhost|http://cgit.freedesktop.org/xorg/app/xhost/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.5.tar.bz2]] +[[xineramaproto|http://cgit.freedesktop.org/xorg/proto/xineramaproto/]] | proto | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.1.2.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.1.2.tar.bz2]] | [[1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.2.tar.bz2]] | [[1.2|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.2.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/proto/xineramaproto-1.2.1.tar.bz2]] +[[xinit|http://cgit.freedesktop.org/xorg/app/xinit/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xinit-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xinit-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xinit-1.0.3.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xinit-1.0.5.tar.bz2]] | _none_|||| +[[xinput|http://cgit.freedesktop.org/xorg/app/xinput/]] | app | _none_|||| | [[1.3.0|http://xorg.freedesktop.org/releases/individual/app/xinput-1.3.0.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/app/xinput-1.5.0.tar.bz2]] | [[1.5.3|http://xorg.freedesktop.org/releases/individual/app/xinput-1.5.3.tar.bz2]] | [[1.6.0|http://xorg.freedesktop.org/releases/individual/app/xinput-1.6.0.tar.bz2]] +[[xkbcomp|http://cgit.freedesktop.org/xorg/app/xkbcomp/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.3.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.0.5.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.1.1.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.2.0.tar.bz2]] | [[1.2.4|http://xorg.freedesktop.org/releases/individual/app/xkbcomp-1.2.4.tar.bz2]] +[[xkbdata|http://cgit.freedesktop.org/xorg/data/xkbdata/]] | data | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xkbdata-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xkbdata-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xkbdata-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/data/xkbdata-1.0.1.tar.bz2]] | _none_|||| +[[xkbevd|http://cgit.freedesktop.org/xorg/app/xkbevd/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.1.0.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.1.2.tar.bz2]] | [[1.1.3|http://xorg.freedesktop.org/releases/individual/app/xkbevd-1.1.3.tar.bz2]] +[[xkbprint|http://cgit.freedesktop.org/xorg/app/xkbprint/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbprint-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbprint-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbprint-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbprint-1.0.1.tar.bz2]] | _none_|||| +[[xkbutils|http://cgit.freedesktop.org/xorg/app/xkbutils/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xkbutils-1.0.3.tar.bz2]] +[[xkeyboard-config|http://cgit.freedesktop.org/xkeyboard-config/]] | data | _none_||||||| | [[2.6|http://xorg.freedesktop.org/releases/individual/data/xkeyboard-config//xkeyboard-config-2.6.tar.bz2]] +[[xkill|http://cgit.freedesktop.org/xorg/app/xkill/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xkill-1.0.3.tar.bz2]] +[[xload|http://cgit.freedesktop.org/xorg/app/xload/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xload-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xload-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xload-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xload-1.0.2.tar.bz2]] | _none_|||| +[[xlogo|http://cgit.freedesktop.org/xorg/app/xlogo/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlogo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlogo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlogo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlogo-1.0.1.tar.bz2]] | _none_|||| +[[xlsatoms|http://cgit.freedesktop.org/xorg/app/xlsatoms/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/xlsatoms-1.1.1.tar.bz2]] +[[xlsclients|http://cgit.freedesktop.org/xorg/app/xlsclients/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.0.2.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/app/xlsclients-1.1.2.tar.bz2]] +[[xlsfonts|http://cgit.freedesktop.org/xorg/app/xlsfonts/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsfonts-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xlsfonts-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xlsfonts-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xlsfonts-1.0.2.tar.bz2]] | _none_|||| +[[xmag|http://cgit.freedesktop.org/xorg/app/xmag/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmag-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmag-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmag-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xmag-1.0.2.tar.bz2]] | _none_|||| +[[xman|http://cgit.freedesktop.org/xorg/app/xman/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xman-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xman-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xman-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xman-1.0.3.tar.bz2]] | _none_|||| +[[xmessage|http://cgit.freedesktop.org/xorg/app/xmessage/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmessage-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmessage-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmessage-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xmessage-1.0.2.tar.bz2]] | _none_|||| +[[xmh|http://cgit.freedesktop.org/xorg/app/xmh/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmh-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmh-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmh-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmh-1.0.1.tar.bz2]] | _none_|||| +[[xmodmap|http://cgit.freedesktop.org/xorg/app/xmodmap/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.5.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/app/xmodmap-1.0.7.tar.bz2]] +[[xmore|http://cgit.freedesktop.org/xorg/app/xmore/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmore-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmore-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmore-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xmore-1.0.1.tar.bz2]] | _none_|||| +[[xorg-cf-files|http://cgit.freedesktop.org/xorg/util/xorg-cf-files/]] | util | [[1.0.1|http://xorg.freedesktop.org/releases/individual/util/xorg-cf-files-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/xorg-cf-files-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/xorg-cf-files-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/util/xorg-cf-files-1.0.2.tar.bz2]] | _none_|||| +[[xorg-docs|http://cgit.freedesktop.org/xorg/doc/xorg-docs/]] | doc | [[1.0.1|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.0.1.tar.bz2]] | [[1.2|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.2.tar.bz2]] | [[1.3|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.3.tar.bz2]] | [[1.4|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.4.tar.bz2]] | [[1.4|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.4.tar.bz2]] | [[1.5|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.5.tar.bz2]] | [[1.6|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.6.tar.bz2]] | [[1.7|http://xorg.freedesktop.org/releases/individual/doc/xorg-docs-1.7.tar.bz2]] +[[xorg-server|http://cgit.freedesktop.org/xorg/xserver/]] | xserver | [[1.0.1|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.0.1.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.2.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.2.0.tar.bz2]] | [[1.5.0|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.5.0.tar.bz2]] | [[1.7.1|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.7.1.tar.bz2]] | [[1.9.3|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.9.3.tar.bz2]] | [[1.12.2|http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.12.2.tar.bz2]] +[[xorg-sgml-doctools|http://cgit.freedesktop.org/xorg/doc/xorg-sgml-doctools/]] | doc | [[1.0.1|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.0.1.tar.bz2]] | [[1.1|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.1.tar.bz2]] | [[1.1|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.1.tar.bz2]] | [[1.2|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.2.tar.bz2]] | [[1.2|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.2.tar.bz2]] | [[1.3|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.3.tar.bz2]] | [[1.6|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.6.tar.bz2]] | [[1.11|http://xorg.freedesktop.org/releases/individual/doc/xorg-sgml-doctools-1.11.tar.bz2]] +[[xphelloworld|http://cgit.freedesktop.org/xorg/app/xphelloworld/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xphelloworld-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xphelloworld-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xphelloworld-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xphelloworld-1.0.1.tar.bz2]] | _none_|||| +[[xplsprinters|http://cgit.freedesktop.org/xorg/app/xplsprinters/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xplsprinters-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xplsprinters-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xplsprinters-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xplsprinters-1.0.1.tar.bz2]] | _none_|||| +[[xpr|http://cgit.freedesktop.org/xorg/app/xpr/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.3.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xpr-1.0.4.tar.bz2]] +[[xprehashprinterlist|http://cgit.freedesktop.org/xorg/app/xprehashprinterlist/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xprehashprinterlist-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xprehashprinterlist-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xprehashprinterlist-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xprehashprinterlist-1.0.1.tar.bz2]] | _none_|||| +[[xprop|http://cgit.freedesktop.org/xorg/app/xprop/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xprop-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xprop-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xprop-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xprop-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xprop-1.0.4.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xprop-1.1.0.tar.bz2]] | [[1.2.0|http://xorg.freedesktop.org/releases/individual/app/xprop-1.2.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/app/xprop-1.2.1.tar.bz2]] +[[xproto|http://cgit.freedesktop.org/xorg/proto/x11proto/]] | proto | [[7.0.4|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.4.tar.bz2]] | [[7.0.5|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.5.tar.bz2]] | [[7.0.10|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.10.tar.bz2]] | [[7.0.10|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.10.tar.bz2]] | [[7.0.13|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.13.tar.bz2]] | [[7.0.16|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.16.tar.bz2]] | [[7.0.20|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.20.tar.bz2]] | [[7.0.23|http://xorg.freedesktop.org/releases/individual/proto/xproto-7.0.23.tar.bz2]] +[[xproxymanagementprotocol|http://cgit.freedesktop.org/xorg/proto/pmproto/]] | proto | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/xproxymanagementprotocol-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/xproxymanagementprotocol-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/xproxymanagementprotocol-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/proto/xproxymanagementprotocol-1.0.2.tar.bz2]] | _none_|||| +[[xrandr|http://cgit.freedesktop.org/xorg/app/xrandr/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.0.2.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.2.2.tar.bz2]] | [[1.2.3|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.2.3.tar.bz2]] | [[1.3.2|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.3.2.tar.bz2]] | [[1.3.4|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.3.4.tar.bz2]] | [[1.3.5|http://xorg.freedesktop.org/releases/individual/app/xrandr-1.3.5.tar.bz2]] +[[xrdb|http://cgit.freedesktop.org/xorg/app/xrdb/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.5.tar.bz2]] | [[1.0.6|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.6.tar.bz2]] | [[1.0.7|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.7.tar.bz2]] | [[1.0.9|http://xorg.freedesktop.org/releases/individual/app/xrdb-1.0.9.tar.bz2]] +[[xrefresh|http://cgit.freedesktop.org/xorg/app/xrefresh/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.4.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xrefresh-1.0.4.tar.bz2]] +[[xrx|http://cgit.freedesktop.org/xorg/app/xrx/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrx-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrx-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrx-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xrx-1.0.1.tar.bz2]] | _none_|||| +[[xset|http://cgit.freedesktop.org/xorg/app/xset/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xset-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xset-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xset-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xset-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xset-1.0.4.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xset-1.1.0.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/app/xset-1.2.1.tar.bz2]] | [[1.2.2|http://xorg.freedesktop.org/releases/individual/app/xset-1.2.2.tar.bz2]] +[[xsetmode|http://cgit.freedesktop.org/xorg/app/xsetmode/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetmode-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetmode-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetmode-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetmode-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetmode-1.0.0.tar.bz2]] | _none_||| +[[xsetpointer|http://cgit.freedesktop.org/xorg/app/xsetpointer/]] | app | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetpointer-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/app/xsetpointer-1.0.0.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsetpointer-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsetpointer-1.0.1.tar.bz2]] | _none_|||| +[[xsetroot|http://cgit.freedesktop.org/xorg/app/xsetroot/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.0.3.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.1.0.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xsetroot-1.1.0.tar.bz2]] +[[xsm|http://cgit.freedesktop.org/xorg/app/xsm/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsm-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xsm-1.0.1.tar.bz2]] | _none_|||| +[[xstdcmap|http://cgit.freedesktop.org/xorg/app/xstdcmap/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xstdcmap-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xstdcmap-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xstdcmap-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xstdcmap-1.0.1.tar.bz2]] | _none_|||| +[[xtrans|http://cgit.freedesktop.org/xorg/lib/xtrans/]] | lib | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.0.0.tar.bz2]] | [[1.0.0|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.0.0.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.0.4.tar.bz2]] | [[1.2.1|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.2.1.tar.bz2]] | [[1.2.5|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.2.5.tar.bz2]] | [[1.2.6|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.2.6.tar.bz2]] | [[1.2.7|http://xorg.freedesktop.org/releases/individual/lib/xtrans-1.2.7.tar.bz2]] +[[xtrap|http://cgit.freedesktop.org/xorg/app/xtrap/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xtrap-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xtrap-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xtrap-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xtrap-1.0.2.tar.bz2]] | _none_|||| +[[xvidtune|http://cgit.freedesktop.org/xorg/app/xvidtune/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvidtune-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvidtune-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvidtune-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvidtune-1.0.1.tar.bz2]] | _none_|||| +[[xvinfo|http://cgit.freedesktop.org/xorg/app/xvinfo/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.0.2.tar.bz2]] | [[1.1.0|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.1.0.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.1.1.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/xvinfo-1.1.1.tar.bz2]] +[[xwd|http://cgit.freedesktop.org/xorg/app/xwd/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xwd-1.0.5.tar.bz2]] +[[xwininfo|http://cgit.freedesktop.org/xorg/app/xwininfo/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.0.2.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.0.4.tar.bz2]] | [[1.0.5|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.0.5.tar.bz2]] | [[1.1.1|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.1.1.tar.bz2]] | [[1.1.2|http://xorg.freedesktop.org/releases/individual/app/xwininfo-1.1.2.tar.bz2]] +[[xwud|http://cgit.freedesktop.org/xorg/app/xwud/]] | app | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.1.tar.bz2]] | [[1.0.1|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.1.tar.bz2]] | [[1.0.2|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.2.tar.bz2]] | [[1.0.3|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.3.tar.bz2]] | [[1.0.4|http://xorg.freedesktop.org/releases/individual/app/xwud-1.0.4.tar.bz2]] +"""]] diff --git a/RepoPolicy.mdwn b/RepoPolicy.mdwn new file mode 100644 index 00000000..18442b66 --- /dev/null +++ b/RepoPolicy.mdwn @@ -0,0 +1,39 @@ + +X.Org currently keeps the source for its stuff in a [[GIT|http://www.freedesktop.org/wiki/Infrastructure/git]] repository. This page is one of several documents describing that repository. **Note: The xserver module follows a slightly different development model than outlined below. Some information below may not apply. Please read the [[XServer|XServer]] page for more detail.** + + +## Who can access the repository? + +* Anyone. See the users' GIT [[page|http://www.freedesktop.org/wiki/Infrastructure/git/Users]] for instructions about how to access the repository anonymously. + +## Who can get repository commit privileges? + +* Anyone can apply for commit privileges to the master repository. You should give a description of what you plan to do, or even better provide an initial set of patches you plan to apply. A sponsor from the current X.Org team is required before commit privileges can be granted. This sponsor needs to have some idea of your background and experience. You may be asked for a sample of code to judge the quality of your coding. Only people with serious projects and long term commitment get commit privileges. One-time-fix submissions should be done to the [[xorg-devel mailing list|http://lists.x.org/mailman/listinfo/xorg-devel]], or to the freedesktop.org [[Bugzilla|https://bugs.freedesktop.org/]], against the xorg product. + +## Is there something in between? + +* Thanks to GIT, yes, there is. GIT makes it quite straightforward for you to maintain your own repository of changes that tracks our master repository. You might host this repository on your own website, on a hosting site such as gitorious, or you might request an account at people.freedesktop.org. This makes it easy for folks with commit access to the master repository to incorporate your changes, and gives you a chance to establish a track record as a developer in a "safe" environment. We highly recommend that you initially do development this way. + +## ChangeLog + +* X.Org no longer uses manually maintained Change``Log files, but instead uses dist-hook entries in the top-level Makefile to generate Change``Log from git log output when tarballs are being generated. + +## Master Repository Commit Rules + +* Before being given commit priviliges on the master repository, you need to read and agree to the commit rules described in this section. + +### Who may commit what? + +* Committers are allowed to commit to master (where ongoing development takes place) only after review. Exceptions are obvious bug and typo fixes. Write access to other branches is controlled by the branch owner. The release manager is the owner of the release branch. + +### Use proper discretion + +* The general rule is (especially when committing to HEAD): only commit stuff you are certain about. If you don't understand a particular area and you think you need to commit a patch: *ASK*! There may be someone who can help you. In general, it's nice to post to the appropriate list describing the changes you've just made or would like to make. That increases the visibility of the change (potentially saving others lots of time) and gives others a chance to comment on and/or improve upon your modifications. Don't worry if you don't get any comments: it may be that your patch is perfect, so go ahead and check it in. If there's something wrong with it, you'll find out soon enough. Again, please note the different rules for [[the X server|XServer]]. + +### What should you do after the commit? + +* Committers are responsible for their own commits. They should be prepared to fix without delay problems their commit may create, or revert their changes. Ideally a committer would watch the [[tinderbox|http://tinderbox.freedesktop.org/]] to see if their changes caused any build breakages afterwards, though we currently need more machines in the tinderbox for it to be useful. + +### What if you screw up the repo? + +* Please email [[sitewranglers@freedesktop.org|mailto:sitewranglers@freedesktop.org]] *promptly* if you feel you may have corrupted the master GIT repository. This is not something you are likely to be able to fix yourself, and we'll need to tackle it *as soon as possible*. (The good news is that with GIT this is very difficult to do.) If you are unhappy with a patch sequence, and think the repo needs a rollback or rebase, please contact someone as soon as possible. These things are much easier the sooner they're tackled. In general, we will not disturb commits to the repository without a *very* good reason, so please be careful out there. People's commit privileges shall be revoked if they repeatedly violate these rules.
\ No newline at end of file diff --git a/RequiredPackages.mdwn b/RequiredPackages.mdwn new file mode 100644 index 00000000..66385a2e --- /dev/null +++ b/RequiredPackages.mdwn @@ -0,0 +1,199 @@ + +List of required packages to build the X server from git. [[!toc ]] + +(Please add your distribution if it is missing) + + +## Ubuntu + + +### Natty Narwhal 11.04 + +Swipe the following command to install all required packages. About 900MB of additional storage is required. +[[!format txt """ +sudo apt-get install asciidoc autoconf automake autotools-dev bison docbook-utils doxygen flex fop git-core gperf intltool jadetex libfontconfig1-dev libfreetype6-dev libglib2.0-dev libncurses5-dev libpng12-dev libssl-dev libtool llvm m4 netpbm psutils w3m xmlto zlib1g-dev +"""]] + +[[!format txt """ +asciidoc 8.6.3 +autoconf 2.67 +automake 1.11 +autotools-dev 20100122 +bison 2.4.1 +docbook-utils 0.6.14 +doxygen 1.7.3 +flex 2.5.35 +fontconfig 2.8.0 pre-installed +fop 0.95 +gcc 4.5.2 pre-installed +gettext 0.18.1 pre-installed +gettext-base 0.18.1 pre-installed +ghostscript 9.01 pre-installed +git-core 1.7.4 +gperf 3.0.3 +intltool 0.41.1 +jadetex 3.13 +libfontconfig1-dev 2.8.0 +libfreetype6 2.4.4 pre-installed +libfreetype6-dev 2.4.4 +libglib2.0-dev 2.28.6 +libncurses5-dev 5.7 +libpng12-0 1.2.44 pre-installed +libpng12-dev 1.2.44 +libssl-dev 0.9.8o +libtool 2.2.6b +llvm 2.8 +m4 1.4.14 +netpbm 10.0 +openssl 0.9.8o pre-installed +perl 5.10.1 pre-installed +pkg-config 0.25 pre-installed +psutils 1.17 +w3m 0.5.3 +xmlto 0.0.23 +zlib1g 1.2.3.4 pre-installed +zlib1g-dev 1.2.3.3 +"""]] + +### Oneiric Ocelot 11.10 + +Swipe the following command to install all required packages. About 900MB of additional storage is required. +[[!format txt """ +sudo apt-get install asciidoc autoconf automake autotools-dev bison docbook-utils doxygen flex fop git-core gperf intltool jadetex libdrm-dev libfontconfig1-dev libfreetype6-dev libglib2.0-dev libncurses5-dev libpng12-dev libssl-dev libtool libudev-dev llvm m4 netpbm psutils systemtap-sdt-dev w3m xmlto zlib1g-dev +"""]] + +[[!format txt """ +asciidoc 8.6.4 +autoconf 2.68 +automake 1.11.1 +autotools-dev 20110511 +bison 2.4.1 +docbook-utils 0.6.14 +doxygen 1.7.4 +flex 2.5.35 +fontconfig 2.8.0 pre-installed +fop 0.95 +gcc 4.6.1 pre-installed +gettext 0.18.1 pre-installed +gettext-base 0.18.1 pre-installed +ghostscript 9.04 pre-installed +git-core 1.7.5.4 +gperf 3.0.3 +intltool 0.41.1 +jadetex 3.13 +libfontconfig1-dev 2.8.0 +libfreetype6 2.4.4 pre-installed +libfreetype6-dev 2.4.4 +libglib2.0-dev 2.30.0 +libncurses5-dev 5.9 +libpng12-0 1.2.46 pre-installed +libpng12-dev 1.2.46 +libssl-dev 1.0.0e +libtool 2.4 +libudev-dev +llvm 2.8 +m4 1.4.16 +netpbm 10.0 +openssl 1.0.0e pre-installed +perl 5.12.4 pre-installed +pkg-config 0.26 pre-installed +psutils 1.17 +systemtap-sdt-dev 1.4 +w3m 0.5.3 +xmlto 0.0.23 +zlib1g 1.2.3.4 pre-installed +zlib1g-dev 1.2.3.4 +"""]] + +## Gentoo + + +### stage3-amd64-20100514.tar.bz2 + +Had to install: +[[!format txt """ +docbook-xml-dtd 4.1.2 +docbook-xml-dtd 4.3 +docbook-xml-dtd 4.4 +doxygen +gd (USE: jpeg png) +git +gperf +freetype +intltool +libxlst +lynx (or w3m) +pkgconfig +xmlto +"""]] + +## OpenSolaris + + +### 2009.06 + + +[[!format txt """ +There are multiple versions for aclocal, automake, and python. You need to create links to the latest version in $prefix/bin. +SUNWaconf 2.61 +SUNWgnu-automake-110 1.10 +SUNWbison 2.3 +SUNWgnome-xml 0.6.3 +SUNWdoxygen 1.5.7.1 +SUNWflexlex 2.5.33 +SUNWfontconfig 2.5.0 pre-installed +SUNWgcc 3.4.3 +gcc-dev 3.4.3 +SUNWgmake 3.81 +SUNWgnome-common-devel 0.5.11 +SUNWgnu-gettext 0.16.1 +SUNWgit 1.5.6.5 +SUNWgperf 3.0.3 +SUNWgroff 1.19.2 +SUNWncurses 0.5.11 +SUNWpng 0.5.11 +SUNWopenssl 0.9.8 pre-installed +SUNWlibtool 1.5.22 +SUNWgm4 1.4.2 +SUNWperl* 5.8.4 +SUNWPython26 2.6.1 +SUNWpython-lxml 2.1.2 +SUNWzlib 1.2.3 +"""]] + +## OpenBSD + +pkg_add the following packages +[[!format txt """ +automake-1.9 +autoconf-2.62 +libtool +metaauto +"""]] +_Packages needed to reformat docs need to be sorted out_... + +Set environment variables to point to the autotools version you're using + + +[[!format txt """ +PKG_CONFIG_LIBDIR=/usr/X11R6/lib/pkgconfig +AUTOMAKE_VERSION=1.9 +AUTOCONF_VERSION=2.62 +ACLOCAL="aclocal -I /usr/X11R6/share/aclocal" +"""]] + +## openSUSE + + +### 11.3 + +The `libtalloc-devel` package for openSUSE 11.3 is missing the required `talloc.pc` file to allow the _mesa_ build to complete successfully. There are two ways this can be fixed: + +1. defining environment variables which work with `pkg-config`: [[!format txt """ + $> export TALLOC_LIBS=-ltalloc + $> export TALLOC_CFLAGS="-I/usr/include" + $> build.sh -o mesa/mesa $PREFIX + +"""]] +1. installing a fixed, updated `libtalloc-devel` package. See [[https://bugzilla.novell.com/show_bug.cgi?id=632770|https://bugzilla.novell.com/show_bug.cgi?id=632770]] for details. +NOTE: openSUSE 11.2 also seems to have this problem diff --git a/SecurityPage.mdwn b/SecurityPage.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/SecurityPage.mdwn diff --git a/SecurityTalkAgenda.mdwn b/SecurityTalkAgenda.mdwn new file mode 100644 index 00000000..d740990c --- /dev/null +++ b/SecurityTalkAgenda.mdwn @@ -0,0 +1,35 @@ + + +# Xorg Developer's Conference - Security Talk + +Rough outline of talk/discussion follows: + + +## Security Advisories/Response + +* Not covered + +## X Authentication/Transport + +* Loadable module support for authentication methods. Could be done: provide registration function, call callback list passing connection setup information plus file descriptor; callback performs authentication entirely before returning decision to server. +* Xtrans improvements. XCB doesn't use it. Could make it an actual library. Is a filehandle a sufficient abstraction? +* XC-QUERY-SECURITY rework. + +## Fine-Grained Access Control + +* Have a research paper; will post link. +* Improved resource lookup functions: still thinking about the prototype for dixLookupResource. Not sure if the Dix``Read``Access/Dix``Write``Access flags are useful or necessary. +* Use the resource system to store your module's objects. +* Don't multiplex different operations through the same protocol request. + +## Other Security Work of Note + +* Security error handling. Right now, the Security extension "hides" denials from the user by returning false information. I would like to see the server begin returning actual errors, preferably Bad``Access. +* devPrivates rework. Currently have separate functions for each supported structure. Could standardize this into one set of functions. +* Need to add devPrivates to additional structures: Property``Rec. +* Window labeling: currently exporting properties to window manager. Feature request: need secure area for showing labels. +* Secure handling of input events. Secure attention key support. + +## Applications + +* Shared Display Wall
\ No newline at end of file diff --git a/Server110Branch.mdwn b/Server110Branch.mdwn new file mode 100644 index 00000000..2277e4d6 --- /dev/null +++ b/Server110Branch.mdwn @@ -0,0 +1,58 @@ + +Release manager: [[KeithPackard|KeithPackard]] + +Stable branch maintainer: [[JeremyHuddleston|JeremyHuddleston]] + +**The 1.10 branch is no longer actively maintained** + + +## Schedule + +See the [[X.Org Calendar|http://www.google.com/calendar/embed?src=nl1n1fmvu091eqh35ldqspar80%40group.calendar.google.com&ctz=Australia/Brisbane]]. + + +## Merge Windows + +The stable release cycle will typically be 6 weeks between dot releases. This is subject to change as needed if big issues arise forcing earlier releases or regressions arise pushing back a release. + + +#### 3 weeks before RC1 + +During the first three weeks of the release cycle, the branch is open for general nominations. As a rule of thumb, if a change does not alter ABI, change dependencies, or introduce new features, it can probably be considered for the stable branch. The focus of patches merged into the stable branch during this period should be + + * Crash fixes + * General bug fixes + * New architecture support + +#### 2 weeks before RC2 + +During the next two weeks of the cycle, the branch gets slightly tighter. The branch is still open for general nominations, but the criteria for acceptance is a bit stricter. Larger change sets which do not fix crashes or regressions will likely be deferred to the next release cycle (and picked up prior to RC1). The focus of patches merged into stable during this period should be + + * Crash fixes + * Regressions (from any previous release) + * Fixes for bugs listed in the [[1.10 tracker|https://bugs.freedesktop.org/show_bug.cgi?id=xserver-1.10]] + +#### 1 week before final release + +During the last week before the release, the branch gets much tighter. Any other changes should be held for nomination in the next cycle. The focus of patches merged into stable during this period should be + + * Crash fixes with minimal code churn + * Regressions from the previous stable release + +## Proposing patches for 1.10.x + +Server 1.10.0 has been [[released|http://lists.freedesktop.org/archives/xorg-announce/2011-February/001612.html]]. Patches may be nominated for future 1.10.x releases using the process outlined below. + + * **Do not push to server-1.10-branch.** + * Patches for 1.10 must be in master first. Please follow the guidelines outlined on the [[XServer|XServer]] page to get a patch into master. Exceptions are patches where the master code has changed in a way that git master is not affected by a particular bug. + * For single patches: Once a patch is in master, let the stable branch maintainer know that this patch is to be cherry-picked to 1.10. Reply to the original patch email, placing the branch maintainer in TO and CC-ing the list. Make sure that the subject line contains `[PATCH 1.10]`. + * For multiple patches: Create a local branch and cherry-pick the patches required (Always use cherry-pick -x). Push this branch to your people.freedesktop.org repository and send a pull request to the stable branch maintainer, CC-ing the list. Make sure the subject line contains `[PULL 1.10]`. + * Only fixes for regressions introduced since the previous stable release will be accepted between the final rc and the release. + +### Critical Bugs / Halting Release + +If you have found a bug that you believe should delay the release of the next stable release, make sure you do each of the following to get attention: + + * Create a bug, and make sure the branch maintainer is CC'd. Include a link to the commit that caused the issue if you were able to determine that. + * Email the branch maintainer and xorg-devel about the issue. Make sure the subject line contains either `[1.10 REGRESSION]` or `[1.10 DNR]` or similar. +Make sure you get confirmation, and follow up. If the branch maintainer agrees, the bug will be added to the [[1.10 tracker|https://bugs.freedesktop.org/show_bug.cgi?id=xserver-1.10]]. diff --git a/Server112Branch.mdwn b/Server112Branch.mdwn new file mode 100644 index 00000000..f16a33d4 --- /dev/null +++ b/Server112Branch.mdwn @@ -0,0 +1,54 @@ + +Stable branch release manager: [[JeremyHuddleston|JeremyHuddleston]] + + +## Schedule + +See the [[X.Org Calendar|http://www.google.com/calendar/embed?src=nl1n1fmvu091eqh35ldqspar80%40group.calendar.google.com&ctz=Australia/Brisbane]]. + + +## Merge Windows + +The stable release cycle will typically be 6 weeks between dot releases. This is subject to change as needed if big issues arise forcing earlier releases or regressions arise pushing back a release. + + +#### 3 weeks before RC1 + +During the first three weeks of the release cycle, the branch is open for general nominations. As a rule of thumb, if a change does not alter ABI, change dependencies, or introduce new features, it can probably be considered for the stable branch. The focus of patches merged into the stable branch during this period should be + + * Crash fixes + * General bug fixes + * New architecture support + +#### 2 weeks before RC2 + +During the next two weeks of the cycle, the branch gets slightly tighter. The branch is still open for general nominations, but the criteria for acceptance is a bit stricter. Larger change sets which do not fix crashes or regressions will likely be deferred to the next release cycle (and picked up prior to RC1). The focus of patches merged into stable during this period should be + + * Crash fixes + * Regressions (from any previous release) + * Fixes for bugs listed in the [[1.12 tracker|https://bugs.freedesktop.org/show_bug.cgi?id=xserver-1.12]] + +#### 1 week before final release + +During the last week before the release, the branch gets much tighter. Any other changes should be held for nomination in the next cycle. The focus of patches merged into stable during this period should be + + * Crash fixes with minimal code churn + * Regressions from the previous stable release + +## Proposing patches + +Server 1.12.0 has been [[released|http://lists.freedesktop.org/archives/xorg-announce/2012-March/001846.html]]. Patches may be nominated for future 1.12.x releases using the process outlined below. + + * **Do not push to server-1.12-branch.** + * Patches for 1.12 must be in master first. Please follow the guidelines outlined on the [[XServer|XServer]] page to get a patch into master. Exceptions are patches where the master code has changed in a way that git master is not affected by a particular bug. + * For single patches: Once a patch is in master, let the stable branch maintainer know that this patch is to be cherry-picked to 1.12. Reply to the original patch email, placing the branch maintainer in TO and CC-ing the list. Make sure that the subject line contains `[PATCH 1.11]`. + * For multiple patches: Create a local branch and cherry-pick the patches required (Always use cherry-pick -x). Push this branch to your people.freedesktop.org repository and send a pull request to the stable branch maintainer, CC-ing the list. Make sure the subject line contains `[PULL 1.12]`. + * Only fixes for regressions introduced since the previous stable release will be accepted between the final rc and the release. + +### Critical Bugs / Halting Release + +If you have found a bug that you believe should delay the release of the next stable release, make sure you do each of the following to get attention: + + * Create a bug, and make sure the branch maintainer is CC'd. Include a link to the commit that caused the issue if you were able to determine that. + * Email the branch maintainer and xorg-devel about the issue. Make sure the subject line contains either `[1.12 REGRESSION]` or `[1.12 DNR]` or similar. +Make sure you get confirmation, and follow up. If the branch maintainer agrees, the bug will be added to the [[1.11 tracker|https://bugs.freedesktop.org/show_bug.cgi?id=xserver-1.11]]. diff --git a/Server113Branch.mdwn b/Server113Branch.mdwn new file mode 100644 index 00000000..b29c1de9 --- /dev/null +++ b/Server113Branch.mdwn @@ -0,0 +1,56 @@ + +Release manager: [[KeithPackard|KeithPackard]] + +Stable branch maintainer: [[MattDew|MattDew]] + + +## Schedule + +See the [[X.Org Calendar|http://www.google.com/calendar/embed?src=nl1n1fmvu091eqh35ldqspar80%40group.calendar.google.com&ctz=Australia/Brisbane]]. + + +## Merge Windows + +The stable release cycle will typically be 6 weeks between dot releases. This is subject to change as needed if big issues arise forcing earlier releases or regressions arise pushing back a release. + + +#### 3 weeks before RC1 + +During the first three weeks of the release cycle, the branch is open for general nominations. As a rule of thumb, if a change does not alter ABI, change dependencies, or introduce new features, it can probably be considered for the stable branch. The focus of patches merged into the stable branch during this period should be + + * Crash fixes + * General bug fixes + * New architecture support + +#### 2 weeks before RC2 + +During the next two weeks of the cycle, the branch gets slightly tighter. The branch is still open for general nominations, but the criteria for acceptance is a bit stricter. Larger change sets which do not fix crashes or regressions will likely be deferred to the next release cycle (and picked up prior to RC1). The focus of patches merged into stable during this period should be + + * Crash fixes + * Regressions (from any previous release) + * Fixes for bugs listed in the [[1.13 tracker|https://bugs.freedesktop.org/show_bug.cgi?id=xserver-1.13]] + +#### 1 week before final release + +During the last week before the release, the branch gets much tighter. Any other changes should be held for nomination in the next cycle. The focus of patches merged into stable during this period should be + + * Crash fixes with minimal code churn + * Regressions from the previous stable release + +## Proposing patches for 1.13.x + +Server 1.13.0 has been [[released|http://lists.x.org/archives/xorg-announce/2012-September/002068.html]]. Patches may be nominated for future 1.13.x releases using the process outlined below. + + * **Do not push to server-1.13-branch.** + * Patches for 1.13 must be in master first. Please follow the guidelines outlined on the [[XServer|XServer]] page to get a patch into master. Exceptions are patches where the master code has changed in a way that git master is not affected by a particular bug. + * For single patches: Once a patch is in master, let the stable branch maintainer know that this patch is to be cherry-picked to 1.13. Reply to the original patch email, placing the branch maintainer in TO and CC-ing the list. Make sure that the subject line contains `[PATCH 1.13]`. + * For multiple patches: Create a local branch and cherry-pick the patches required (Always use cherry-pick -x). Push this branch to your people.freedesktop.org repository and send a pull request to the stable branch maintainer, CC-ing the list. Make sure the subject line contains `[PULL 1.13]`. + * Only fixes for regressions introduced since the previous stable release will be accepted between the final rc and the release. + +### Critical Bugs / Halting Release + +If you have found a bug that you believe should delay the release of the next stable release, make sure you do each of the following to get attention: + + * Create a bug, and make sure the branch maintainer is CC'd. Include a link to the commit that caused the issue if you were able to determine that. + * Email the branch maintainer and xorg-devel about the issue. Make sure the subject line contains either `[1.13 REGRESSION]` or `[1.13 DNR]` or similar. +Make sure you get confirmation, and follow up. If the branch maintainer agrees, the bug will be added to the [[1.13 tracker|https://bugs.freedesktop.org/show_bug.cgi?id=xserver-1.13]]. diff --git a/Server12Branch.mdwn b/Server12Branch.mdwn new file mode 100644 index 00000000..6752cf04 --- /dev/null +++ b/Server12Branch.mdwn @@ -0,0 +1,4 @@ + +This page lists revisions nominated for the server-1.2-branch, after sufficient testing. + +(None!) diff --git a/Server13Branch.mdwn b/Server13Branch.mdwn new file mode 100644 index 00000000..1f9de013 --- /dev/null +++ b/Server13Branch.mdwn @@ -0,0 +1,98 @@ + + +## X server version 1.3 release plans + +X server version 1.3 is API/ABI compatible with X server version 1.2. It includes the following new features: + +* RandR 1.2 +* EXA Damage track +Below here, please list patches nominated for merging into the 1.3.x branch from master, after sufficient testing has been done (no insta-merges, please). + +* f8482967ae8080f49dd1bbb0b79cc65020df679f: Add exa driver callback for pixmapIsOffscreen. +* c10df5b967d4da4e11786520317e2917de5541fa: Swap RRScreenChangeNotifyEvent dimensions when the screen has one crtc and it's rotated. +* 649e7f82d8d4333443493056b81eb20d6cf022bc: Consolidate portPriv->pDraw assignments into xf86XVEnlistPortInWindow. (Fixes crashes introduced by commit a232693c8c2a206aac47c07b133c071938204e0b below, see e.g. [[https://bugs.freedesktop.org/show_bug.cgi?id=11264|https://bugs.freedesktop.org/show_bug.cgi?id=11264]]) + + +--- + + + +Once those patches are merged, please move them below this line: + + + +--- + + RC1 contains these fixes: + +* 811675733e97416c990e6dc9c19271b43d96248d: os: fix client privates leak + * We accidentally leaked the os layer's private structures for every client. +* 0f6dd4aea6176507dbe1c90c950d332fecbcaacb: xephyr: fix screen private leak + * We accidentally leaked the screen private structure every regeneration. +* 5dcad9e9d7d9993d65f989219bee94a060bbf476: Fix bus error on startup in 64-bit Xephyr + * We were passing pointers to CARD32's to a function expecting pointers to unsigned longs. +* c4b7e9d1c16797c3e4b1200b40aceab5696a7fb8: Add an RDTSC implementation to the x86 emulator. + * Not a very good implementation, but it's better than nothing. +* edd5f1745461f995670969cb736d1569ca94643f: Add ast driver/device info to Xorg server & config utilities + * No reason not to let the server give this driver a try. +* 40f84793bca40dcc6883d51aefa1bda44bd1ac61: Propogate $LIBS for xtrans, clock_gettime, libm, etc for each server + * Make sure OS'es that need additional libraries get them added to the library list for all the servers +* f9f7d7f3be53c808abb5eaceb7a1abc55744a210: Make sparc #ifdefs compatible with Sun cc +* 5680efc0d2baf0a9451e82e490e3690fc23dda0f: Xorg should not be including <sys/immu.h> on Solaris + * Fixes builds on current Solaris development branch releases +RC2 contains these fixes: + +* d5aba03feff41722c72b4c6193f09d141cbf1678: Xprint: shorten font filename to fit in tar length limit + * Follow-up for commit aeabf2a1f873f884b8a8c33b1517c3f3cab4c7f5, bring filenames within tar limits. Revert 73904d953f2f9cbe941a215ba240b46bc7a61357 before applying. + + +--- + + RC3 contains these fixes: + +fbdevhw fixes: + +* f6815cb68b0f6698497348fc6e4214dacef33b95: fbdevhw: Consolidate modeset ioctl calling, report failure if it modifies mode. +* c385bcf0bde38dd869f7065f859dd4b4126f5690: fbdevhw: Fix some issues with the previous commit. +* d077c0da470ab7291e8d838eaace57b066477d6f: fbdevhw: Use displayWidth for fbdev virtual width when appropriate. +* dc5eb4523298f966bd5fd9ae6672160034b5e82c: fbdevhw: Override RGB offsets and masks after setting initial mode. +* 27a01e100bff21ac0b70c6d72071d7226fc91264: fbdevhw: Consider mode set equal to mode requested if virtual width is larger. +* 14d6a9b327381a6bb2dac59c62728e5fd0f0bcfb: fbdevhw: Only deal with RGB weight if default visual is True- or [[DirectColor|DirectColor]]. +Allow colour-keyed Xv overlay adaptors to work a little better with compositing managers (only implemented in radeon driver on master branch so far): + +* a232693c8c2a206aac47c07b133c071938204e0b: Add per-drawable Xv colour key helper function. +* 788cfce911793a26aed16f38f30678ecee82c873: Bump video driver ABI version to 1.2. + + +--- + + + +RC4 didn't contain these fixes, so they're in RC5 instead. + +* 8c7f56d92d8471ee059c14d322af5f7f555dd5c6: Fix timer reschedule. +* 645d87cf8ef724d4591614f9994cdc4d7549a7a8: CVE-2007-1003 + + +--- + + Patches which cause chaos when cherry-picked. These have been rejected for 1.3; suitable 1.3-specific patches are welcome as substitutes; please publish as a branch from a 1.3 tag or attach a patch to this message. + +* 68d39d8571d8717d26cedc84015d537549520a14: kdrive/ephyr: fix keysym type confusion once and for all + * Keysyms were getting mangled in the keymap load, because of 32-bit vs. 64-bit type confusion. +* 68c64ad7b1eea79c786b5a7f3459076780163a47: Xext: Update device's lastx/lasty when sending a motion event with XTest. + + +--- + + Patches which appear to change the ABI/API compatibility with server version 1.2. + +DRI enhancements: + +Allow page flipping with unredirected fullscreen windows while running compiz: + +* eedf148e5a1273ebbf4dc8dcac9c435712fc00ea: Track number of visible DRI windows separately for transitions. +Allow independent page flipping on each CRTC and excluding the DRI window contents when synchronizing 2D rendering between pages (only implemented in the intel driver so far): + +* 3c7a27dc77595ad018bb7c4f7cef6bc178268cb6: DRI: New [[ClipNotify|ClipNotify]] driver hook. +* 3344a4eda704edc7dc30037f095de277a60a70bb: DRI: Make sure number of DRI windows is accurate in driver [[ClipNotify|ClipNotify]] hook.
\ No newline at end of file diff --git a/Server14Branch.mdwn b/Server14Branch.mdwn new file mode 100644 index 00000000..3393b888 --- /dev/null +++ b/Server14Branch.mdwn @@ -0,0 +1,92 @@ + + +## X server version 1.4 release plans + + +### 1.4.1 + +1.4.1 will be released on November 11th, 2007. It is scheduled to contain some random minor fixups, as well as a load of input fixes for extended events. Please nominate your patches on this page, as usual. + +[[DanielStone|DanielStone]] is responsible for this release. The blocker bug for this release is [[xorg-server-1.4.1|https://bugs.freedesktop.org/show_bug.cgi?id=xorg-server-1.4.1]]. + + +### 1.4.0 + +X server version 1.4.0 includes the following new features: + +* [[Input hotplug|Projects/Input]]: Input hotplug allows hotplugging of input devices, and also adds enhanced support for touchscreens and tablets, through either HAL or D-Bus. +* KDrive: Numerous enhancements have been made to the KDrive codebase, including better support for multiple input devices. +* [[DTrace|http://people.freedesktop.org/~alanc/dtrace/]]: When running on [[OpenSolaris|OpenSolaris]], DTrace support is available in the X server, allowing detailed accounting of operations inside the server. +* EXA: A great deal of work has been done on the EXA framework to make it more usable. + +## ABI + +The input & video driver API/ABI's are **not** compatible with X server version 1.3. All other module type API/ABI's are compatible with X server version 1.3. +[[!table header="no" class="mointable" data=""" + | **1.4** | **1.3 ** + ABI_ANSIC_VERSION | 0.3 | 0.3 + ABI_VIDEODRV_VERSION | 2.0 | 1.2 + ABI_XINPUT_VERSION | 2.0 | 0.7 + ABI_EXTENSION_VERSION | 0.3 | 0.3 + ABI_FONT_VERSION | 0.5 | 0.5 +"""]] + + +## Proposed patches + +Below here, please list patches nominated for merging into the [[server-1.4-branch|http://cgit.freedesktop.org/xorg/xserver/log/?h=server-1.4-branch]] from [[master|http://cgit.freedesktop.org/xorg/xserver/log/]], after sufficient testing has been done (no insta-merges, please). + +* [[095850596114178119a8cc854716ce0cc6e05121|http://cgit.freedesktop.org/xorg/xserver/commit/?id=095850596114178119a8cc854716ce0cc6e05121]] ``_``_glXDRIbindTexImage: Fail if no texture bound to pixmap's texture target. +* [[d502521c3669f3f22b94c39a64ab63bfd92c6a97|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d502521c3669f3f22b94c39a64ab63bfd92c6a97]] - EXA: Fix off-by-one in polyline drawing. +* [[feac0759522cbdc3e61ccfa373df735903c5cb27|http://cgit.freedesktop.org/xorg/xserver/commit/?id=feac0759522cbdc3e61ccfa373df735903c5cb27]] - Make config file preferred mode override monitor preferred mode. +* [[29e0e180729a4f0cc020985a4de4c8bc4b9c7f5f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=29e0e180729a4f0cc020985a4de4c8bc4b9c7f5f]] - Leave hardware-specified preferred modes alone when user preference exists. +* [[ce50bfd3369686cfecee5a138bd84ef1107a249d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ce50bfd3369686cfecee5a138bd84ef1107a249d]] - EXA: Skip empty glyphs. ([[bug 13407|https://bugs.freedesktop.org/show_bug.cgi?id=13407]]) +* [[12e532403210c15a25200ef448bfe9701735ab20|http://cgit.freedesktop.org/xorg/xserver/commit/?id=12e532403210c15a25200ef448bfe9701735ab20]] - dix: Always add valuator information if present [[discussion here|http://lists.freedesktop.org/archives/xorg/2007-December/031195.html]] + + +--- + + + +* Once those patches are merged, please move them below this line: + + +--- + + + +* [[70c0592a97c7dc9db0576d32b3bdbe4766520509|http://cgit.freedesktop.org/xorg/xserver/commit/?id=70c0592a97c7dc9db0576d32b3bdbe4766520509]] - Resize composite overlay window when the root window changes. +* [[a48cc88ea2674c28b69b8d738b168cbafcf4001f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a48cc88ea2674c28b69b8d738b168cbafcf4001f]] - Fix rotation for multi-monitor situation. +* [[c7d6d1f589d729fa689d22d82fe30afbc6e1cacb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c7d6d1f589d729fa689d22d82fe30afbc6e1cacb]] - EXA: Punt on fallback case not handled correctly in exaFillRegionTiled. (Backport to 1.4 branch attached to [[bug 12520|https://bugs.freedesktop.org/show_bug.cgi?id=12520]]) +* [[006f6525057970a74382132237b2131286ad147c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=006f6525057970a74382132237b2131286ad147c]] - EXA: Make sure tile offsets passed to drivers are never negative. (Backport to 1.4 branch attached to [[bug 12606|https://bugs.freedesktop.org/show_bug.cgi?id=12606]]) +* [[5d74416740de883b7ef0994afea4bbd4d3901be0|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5d74416740de883b7ef0994afea4bbd4d3901be0]] - EXA: Don't attempt to move in pixmaps that can't be accelerated. (Backport to 1.4 branch attached to [[bug 12815|https://bugs.freedesktop.org/show_bug.cgi?id=12815]]) +* [[23fbd5292d356067e85e1eec4eb4f743532b0503|http://cgit.freedesktop.org/xorg/xserver/commit/?id=23fbd5292d356067e85e1eec4eb4f743532b0503]] Actually build Secure RPC authentication support +* [[265a633cf1fcbf497d6916d9e22403dffdde2e07|http://cgit.freedesktop.org/xorg/xserver/commit/?id=265a633cf1fcbf497d6916d9e22403dffdde2e07]] Screen size changing should leave FB alone when X is inactive. +* [[48ca5961caee62f2980017a6bdc96a1b4c747727|http://cgit.freedesktop.org/xorg/xserver/commit/?id=48ca5961caee62f2980017a6bdc96a1b4c747727]] - Prefer configured [[DisplaySize|DisplaySize]] to probed DDC data, if available. +* [[3a965fdadccea7beff09a28c9c0ef4b4975eae38|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3a965fdadccea7beff09a28c9c0ef4b4975eae38]] - Don't segfault on shutdown if we never managed to connect to dbus. +* [[50fa8722d35c12e5f0322cebe25faf99c39d4f50|http://cgit.freedesktop.org/xorg/xserver/commit/?id=50fa8722d35c12e5f0322cebe25faf99c39d4f50]] - Set noCompositeExtension to TRUE when failing to initialize the extension (e.g. when Xinerama is enabled). +* 0fcde83d94507eadd9f99d4e6a63584b221c989c and 3f42af8c0ef1e5379bc836f589e0cbee43c02ac5. Tested with add & remove command, both valid and invalid forms, on a compile of the server-1.4. branch. +* d0dc9698ae4324d44ed4c0482d6858d0b73bff33 Add _X_EXPORT to exported functions in hw/xfree86/modes/* +* 32666d77227fcd2c066de16bf3c07366f92b0457 Bug #12015: Use the right offsets in the dst arguments of pixman_blt. +* 6a32a96d8df184c3ace4847beb48fdcb846d2286 stride is in [[FbBits|FbBits]]-sized chunks, but xoff is not. +* 53c04351c462d2ae307684e50d5960debe1ee557 move intel crtc xv clipping helper to the xserver +* 1f6ddae003ec65d6bc567831bf32bf75dfefdd6c add xf86_crtc_clip_video_helper to xf86sym.c +* 7dc8531548cc9573e28bb04363dcbb3af5864c9a Ref count cursors used in hw/xfree86/modes code. +* 12d27cf33c6d963eae77795c0d247175907162a5 fix for bug [[#3113|https://bugs.freedesktop.org/show_bug.cgi?id=3113]] (also get a66c0f1dca2958835ff65a5b50579e3304ed316a please.) +* 0dc2bb6101704d0fd25f36e2c3df79687f119f5b [RANDR] Compare only milliseconds of config time. (Bug #6502) +* 1afdf8b0a92437dffe84fa98b6083b3d8fd55e27 [RANDR] Don't mark Xinerama as active if no crtcs are enabled. (bug #11504). +* f98dfec79dadb70fa7bba84e7335f92b3a73dc02 [COMPOSITE] Composite used for pixmap population on redirect. (Bug #7447) + + +--- + + + +* Patches not approved for 1.4.0: + + +--- + + + +* [[c839859d1bc35451923a2cbd5dfac4f3ca5eb3f9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c839859d1bc35451923a2cbd5dfac4f3ca5eb3f9]] Move module defaults from the header to the source file.
\ No newline at end of file diff --git a/Server15Branch.mdwn b/Server15Branch.mdwn new file mode 100644 index 00000000..76a4c9ed --- /dev/null +++ b/Server15Branch.mdwn @@ -0,0 +1,139 @@ + + +## Proposed patches + +Below here, please list patches nominated for merging into the [[server-1.5-branch|http://cgit.freedesktop.org/xorg/xserver/log/?h=server-1.5-branch]] from [[master|http://cgit.freedesktop.org/xorg/xserver/log/?h=master]], after sufficient testing has been done (no insta-merges, please). + +Since xserver 1.5.3 has been released, nominations here will be considered for future 1.5.x bugfix releases, if we do any. + +[[08cd361234ed0410f67342f46ae01120c4fe3331|http://cgit.freedesktop.org/xorg/xserver/commit/?id=08cd361234ed0410f67342f46ae01120c4fe3331]] exa: avoid doing prepare/done without intervening copies in exaFillRegionTiled + +[[0b56b44addc323a00eb7cd86240cb0dd4275bcf8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0b56b44addc323a00eb7cd86240cb0dd4275bcf8]] xfree86: [[AllowEmptyInput|AllowEmptyInput]] is true by default - update the xf86Info defaults. + +[[ace38fafb062372dcd3d56378b5b8f86525c6241|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ace38fafb062372dcd3d56378b5b8f86525c6241]] xfree86: without CONFIG_HAL, Auto{Add|Enable}Devices and AEI is false. + +[[a54153e669fd293a47f0077bf25505dd545ddce2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a54153e669fd293a47f0077bf25505dd545ddce2]] xfree86: don't reset Auto(Add|Enable)Devices, use defaults from xf86Globals + +[[8d4d0b47a07a298a20ffae9fefe96c8c7ca9dccc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8d4d0b47a07a298a20ffae9fefe96c8c7ca9dccc]] gl: include assert.h if we're compiling with DEBUG + +[[60bcdd687040db76490851d4b459284ce37020e0|http://cgit.freedesktop.org/xorg/xserver/commit/?id=60bcdd687040db76490851d4b459284ce37020e0]] x11-input.fdi: Add options needed to handle adding USB devices on Solaris + +[[d2cf562bbad553d7f09b70202134f5b6ada0114e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d2cf562bbad553d7f09b70202134f5b6ada0114e]] Make [[RgbPath|RgbPath]] keyword in xorg.conf a non-fatal error + +[[ca56d764d2be28c64fe15c9e37d534ef00117ad2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ca56d764d2be28c64fe15c9e37d534ef00117ad2]] xsync: Fix wakeup storm in idletime counter. + +[[Bug 21459|https://bugs.freedesktop.org/show_bug.cgi?id=21459]] bogus events sent out whe XKB is disables + +* Patch at [[Xi: don't send XKB mapping notifications when XKB is disabled|https://bugs.freedesktop.org/attachment.cgi?id=25226]] +[[Bug 21455|http://bugs.freedesktop.org/show_bug.cgi?id=21455]] Bad event list generated when adding fake [[KeyRelease|KeyRelease]] + +* Patch at [[dix: fix calculation of number of fake KeyRelease events|http://bugs.freedesktop.org/attachment.cgi?id=25218]] +[[Bug 20098|http://bugs.freedesktop.org/show_bug.cgi?id=20098]] Xserver 1.5: seg fault when initializing DMX screens + +* Patch at [[add dmx*PrivateKeyIndex static ints / dixRequestPrivate|http://bugs.freedesktop.org/attachment.cgi?id=22897]] + + +--- + + + +Once these have been merged, move them below this line: + + + +--- + + + +[[a9e20306fbe3262602f21b876a52a1ef38cdf20a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a9e20306fbe3262602f21b876a52a1ef38cdf20a]] int10: Do an mprotect(..,PROT_EXEC) on shmat()ed memory ranges. + +[[d3d6be4948fa19947fd3b03e6694247109cc0ffb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d3d6be4948fa19947fd3b03e6694247109cc0ffb]] mi: Fix infinite loop on regen when swrast_dri.so is missing + +[[991c88b7542164194be73573e7644164416ea90c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=991c88b7542164194be73573e7644164416ea90c]] xfree86: xf86SetDepthBpp needs to respect the driver's depth24flags + +[[59f9fb4b8c031df69b3592a26b77e744ff4a556e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=59f9fb4b8c031df69b3592a26b77e744ff4a556e]] XAA [[PixmapOps|PixmapOps]]: Sync before accessing unwrapped callbacks. + +[[c9051b684b524549eab6d5b88ee3e195a6f6fbe8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c9051b684b524549eab6d5b88ee3e195a6f6fbe8]] Use [[OsSignal|OsSignal]] in Popen/Pclose to avoid SysV signal() stupidity + +[[d63ea510138c8b6de66184c78cda39ed9981fc1f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d63ea510138c8b6de66184c78cda39ed9981fc1f]] Non-Linux OS'es should default to kbd driver, not now-dead keyboard driver + +[[8f8a9c19ad58768b07461a3f4bccea98f7c4f958|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8f8a9c19ad58768b07461a3f4bccea98f7c4f958]] EXA: avoid copy operations if no boxes in use + +[[c9c1c8ca18d57b65889ec69a93e249f549562732|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c9c1c8ca18d57b65889ec69a93e249f549562732]] dix: extra sanity-checks against potential NULL-dereferences. + + +### Xserver 1.5.3 + +[[8e368cf5b964f1d29fda0a463f9510457619b14d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8e368cf5b964f1d29fda0a463f9510457619b14d]] Xorg: add -modalias option + +[[ffaaa1a198a77eb6800c08d4613ee1cc0b068ba0|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ffaaa1a198a77eb6800c08d4613ee1cc0b068ba0]] xfree86: fix compiler warnings in [[DoModalias|DoModalias]]() + +[[5b336585a4cdf11d20831a9536ad581e959ea7f1|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5b336585a4cdf11d20831a9536ad581e959ea7f1]] dri: don't set the dixPrivate key to NULL, as this is a staticly set variable + + +### Xserver 1.5.2 + +[[8c46505d7d91e0644b19cccc4b342fceb6f86cab|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8c46505d7d91e0644b19cccc4b342fceb6f86cab]] xkb: fix use of uninitialized variable. + +[[ae986d1c73d2f720bd0309d8c33328d14e8eed25|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ae986d1c73d2f720bd0309d8c33328d14e8eed25]] xkb: fix core keyboard map generation. #14373 + +[[30c3c13f1030268aaa6a3598d538fafd0592d77a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=30c3c13f1030268aaa6a3598d538fafd0592d77a]] xkb: squash canonical types into explicit ones on core reconstruction + +[[94919480d8bb66e1807b4fe87b8f326ef6e012c6|http://cgit.freedesktop.org/xorg/xserver/commit/?id=94919480d8bb66e1807b4fe87b8f326ef6e012c6]] int10: Fix a nasty memory leak. (depends on int10 warning commits [[a65e36a873cd1ba9896cd0f9a3e94dd933666005|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a65e36a873cd1ba9896cd0f9a3e94dd933666005]] & [[a57b2f172c1291f22f7ba2780c1b2f55e353c3e9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a57b2f172c1291f22f7ba2780c1b2f55e353c3e9]] ) + +[[56c615368c5a8e7acb0398434c2c68578626aa38|http://cgit.freedesktop.org/xorg/xserver/commit/?id=56c615368c5a8e7acb0398434c2c68578626aa38]] Check nextEnabledOutput()'s return in bestModeForAspect() + +[[1feb69eb63e6739ff5db255ad529e84adf941a10|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1feb69eb63e6739ff5db255ad529e84adf941a10]] DGA: Fix ProcXF86DGASetViewPort for missing support in driver. + + +### Xserver 1.5.1 + +[[2b266eda6e23d16116f8a8e258192df353970279|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2b266eda6e23d16116f8a8e258192df353970279]] Fix panoramiX request and reply swapping + +[[b4762c0245ed2966606171cf27f40aa745fdc76e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b4762c0245ed2966606171cf27f40aa745fdc76e]] exa: disable shared pixmaps + + +### Xserver 1.5 + +[[d01c5ca7935a8340a3cd68c325da6dfec005c952|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d01c5ca7935a8340a3cd68c325da6dfec005c952]] Xserver.man: Typo (the the). + +[[229e60db8f95232afc8cdcb7cd0572d117c84b90|http://cgit.freedesktop.org/xorg/xserver/commit/?id=229e60db8f95232afc8cdcb7cd0572d117c84b90]] Xorg.man: Typo (the the). + +[[01264f17925005969c3b71ca945fc1014bcd8c8e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=01264f17925005969c3b71ca945fc1014bcd8c8e]] Add swapped dispatch for randr 1.2 requests. (alternatively, return 1.1 from RRQueryVersion if (client->swapped)) + +[[d3ae193f4ac87530f2745f8cb5e7b70dd516881e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d3ae193f4ac87530f2745f8cb5e7b70dd516881e]] Xevie: always initialize rep.length (bug#17394) + +[[b5cdcfa55c399e83d51242e93d4f25d8bc4fec1f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b5cdcfa55c399e83d51242e93d4f25d8bc4fec1f]] Xevie: swap replies as necessary + +[[eff25430b4a391409e39337962ff7697165d23c7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=eff25430b4a391409e39337962ff7697165d23c7]] Don't abort if swrast library is not present + +[[244a635fcdc9e0a7212d51b26d74f49d8e1b071f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=244a635fcdc9e0a7212d51b26d74f49d8e1b071f]] Fix the tile offset in miPaintWindow for [[ParentRelative|ParentRelative]] windows. + +[[49751fee3b82ebc4917bfb168ec78aad7874f1f1|http://cgit.freedesktop.org/xorg/xserver/commit/?id=49751fee3b82ebc4917bfb168ec78aad7874f1f1]] glx: copy msaa visual capabilities + +[[2d7ba09dc4b5eff5dba8d7867f285111574b1737|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2d7ba09dc4b5eff5dba8d7867f285111574b1737]] Make devPrivates lookup functions ABI instead of static inlines. + +[[95d4ede538fbb68049ba3efa0acb0e9712e5cb01|http://cgit.freedesktop.org/xorg/xserver/commit/?id=95d4ede538fbb68049ba3efa0acb0e9712e5cb01]] Fix types of modeIsPresent + +[[d5ae85b5b722821499d5796cf0973ecb6ec125f1|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d5ae85b5b722821499d5796cf0973ecb6ec125f1]] Fix embarrasing GLXPixmap leak. + +[[facb255fa9267e343cbc91f841f1b64e5dc99e98|http://cgit.freedesktop.org/xorg/xserver/commit/?id=facb255fa9267e343cbc91f841f1b64e5dc99e98]] Need to unref pixmaps backing pbuffers too. + +[[0b9ef835a0fe900c121b84e43989591e58ab1126|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0b9ef835a0fe900c121b84e43989591e58ab1126]] modes: fix initial xorg.conf mode selection. + +[[2eaed4a10fe5bf727579bca4ab8d4a47c8763a7d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2eaed4a10fe5bf727579bca4ab8d4a47c8763a7d]] xfree86: use xorg.conf input devices if there is no [[ServerLayout|ServerLayout]] (or revert c30f36c8c1dfd85deaf1c109823a1f15dd218ac7) + +[[b8dd07f855c555af56cbf0f69df799f424da2cca|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b8dd07f855c555af56cbf0f69df799f424da2cca]] HAL: Remove grotesque open-coded strcasestr + +[[35b14519b4a3158592a089170ec039bbc219603e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=35b14519b4a3158592a089170ec039bbc219603e]] config: add parsing for input.x11_options.[[XkbOptions|XkbOptions]]. #16874 + +[[92c51b183c2ff06361dad7f918daed6577ba4935|http://cgit.freedesktop.org/xorg/xserver/commit/?id=92c51b183c2ff06361dad7f918daed6577ba4935]] config: support type strlist for [[XkbOptions|XkbOptions]] property. + +[[3c6a9c531f673b7a0cb9ca01860b4dbe79686363|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3c6a9c531f673b7a0cb9ca01860b4dbe79686363]] config: protect against potential out-of-bounds indexing. + + +## Rejected + +These changes were nominated, but found not suitable for a 1.5.x release, though they will be in 1.6.0 and later: + +[[b6ab114212c0e4c3346ceb5b207f14c526ab81e7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b6ab114212c0e4c3346ceb5b207f14c526ab81e7]] Array-index based devPrivates implementation. (depends on [[ebea78cdba0ff14a397239ee1936bd254c181e1b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ebea78cdba0ff14a397239ee1936bd254c181e1b]]) -- **breaks ABI** diff --git a/Server16Branch.mdwn b/Server16Branch.mdwn new file mode 100644 index 00000000..7630ef3b --- /dev/null +++ b/Server16Branch.mdwn @@ -0,0 +1,351 @@ + + +## Features + +* RANDR 1.3 +* DRI2 +* Xinput 1.5 (including [[Input device properties|http://who-t.blogspot.com/2008/07/input-device-properties.html]]) ([[PeterHutterer|PeterHutterer]]) +* [[predictable pointer acceleration|Development/Documentation/PointerAcceleration]] ([[SimonThum|SimonThum]]) + +## Proposed patches + +Since xserver 1.6.0 has been released, nominations here will be considered for future 1.6.x bugfix releases, if we do any. + +Below here, please list patches nominated for merging into the [[server-1.6-branch|http://cgit.freedesktop.org/xorg/xserver/log/?h=server-1.6-branch]] from [[master|http://cgit.freedesktop.org/xorg/xserver/log/]], after sufficient testing has been done (no insta-merges, please). + +* [[3a690598cf18c4cdc6aadd10a1ecf0772cacd34b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3a690598cf18c4cdc6aadd10a1ecf0772cacd34b]] Remove unused [[HandleSpecialKeys|HandleSpecialKeys]] config option + * best to just merge the man page sections, the xf86Info might be ABI? + * +--- + + + +Once these have been merged, move them below this line: + + * +--- + + + +* [[2180174034ae007023f248964be315fccc3c32ee|http://cgit.freedesktop.org/~ewalsh/xserver/commit/?h=server-1.6-branch&id=2180174034ae007023f248964be315fccc3c32ee]] xace: Fake return values on denials in input polling requests. +* [[4a8cc895ccdb64945661747c75a118deea96b53a|http://cgit.freedesktop.org/~ewalsh/xserver/commit/?h=server-1.6-branch&id=4a8cc895ccdb64945661747c75a118deea96b53a]] xselinux: Stop special-casing [[QueryPointer|QueryPointer]] access checks. +* [[e81a665ef210845911d2b03bcca4f6a05cb367d0|http://cgit.freedesktop.org/~ewalsh/xserver/commit/?h=server-1.6-branch&id=e81a665ef210845911d2b03bcca4f6a05cb367d0]] xace: Relax permissions on [[XkbGetState|XkbGetState]] from Read to Getattr. +* [[e26957d0cd937a6433f980c7384f0290c0c579b3|http://cgit.freedesktop.org/~ewalsh/xserver/commit/?h=server-1.6-branch&id=e26957d0cd937a6433f980c7384f0290c0c579b3]] xselinux: switch from x_device to separate x_pointer and x_keyboard classes. +* [[b14bbce6b420a3891cab886d759175c6a16d54e5|http://cgit.freedesktop.org/~ewalsh/xserver/commit/?h=server-1.6-branch&id=b14bbce6b420a3891cab886d759175c6a16d54e5]] xselinux: Note something in the log if disabled by boolean. +* [[cfc09c3618ca194bca0b7ca0bf8334afe9327a36|http://cgit.freedesktop.org/~ewalsh/xserver/commit/?h=server-1.6-branch&id=cfc09c3618ca194bca0b7ca0bf8334afe9327a36]] xselinux: Allow [[SetWindowCreateContext|SetWindowCreateContext]] to be used for pixmaps as well. +* [[9625f6d328d6f516520930227b218979309938bc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9625f6d328d6f516520930227b218979309938bc]] Fix breakage on alpha caused by c7680befe5ae + +## xserver 1.6.5 + +* [[19be992d9dc542b61fa3f4fd32a09071c9e64880|http://cgit.freedesktop.org/xorg/xserver/commit/?id=19be992d9dc542b61fa3f4fd32a09071c9e64880]] ephyr: if -parent is given, check for a trailing -screen. (#24144) + +### xserver 1.6.4.901 (1.6.5 RC1) + +* [[db98b26ee145f70e732e2cf4a6ac3de77fdf4adc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=db98b26ee145f70e732e2cf4a6ac3de77fdf4adc]] Re-fix DGA removal. + +## xserver 1.6.4 + +* [[c1d901d723c3bee523736eacc15b44a7dff484fe|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1d901d723c3bee523736eacc15b44a7dff484fe]] Don't reset the lastDeviceEventTime when doing DPMS actions +* [[df597709d71f47b8516e27c6fb1bfffd59de5e48|http://cgit.freedesktop.org/xorg/xserver/commit/?id=df597709d71f47b8516e27c6fb1bfffd59de5e48]] dri2: Don't crash if pPriv is NULL. +* [[render: return the supported version rather than just passing the proto's version|http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=blob_plain;f=debian/patches/render-return-the-supported-version.patch;h=cdd84851c7f9b3243d39e7bf533ccd1743717c60;hb=0c5ab464dd5bee5644ac05164d1154006e338d04]] (1.6 doesn't support render 0.11, this patch makes it advertise 0.10 even when built against newer renderproto) +* [[f4350c66b493d63fa06be87caa958d7033232ea4|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f4350c66b493d63fa06be87caa958d7033232ea4]] fbdevhw: Test for graphics:fb%d as well as graphics/fb%d +* [[f56cbe1ef24415d0142b9a7d0ab0a031069ccb52|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f56cbe1ef24415d0142b9a7d0ab0a031069ccb52]] dix: append "built-ins" to the font path in [[SetDefaultFontPath|SetDefaultFontPath]] +* [[0b7c6c728c2e2d8433a188315cc591308a89cd85|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0b7c6c728c2e2d8433a188315cc591308a89cd85]] xfree86/modes: Remove all framebuffer support from DGA +* [[Bug 24100 (Attachment 29788)|https://bugs.freedesktop.org/attachment.cgi?id=29788]] Don't send core events for devices that have [[SendCoreEvents|SendCoreEvents]] off + +### xserver 1.6.3.901 (1.6.4 RC1) + +* [[db568f9eabf3450d8a023597ff007df355b13ea8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=db568f9eabf3450d8a023597ff007df355b13ea8]] Xext: fix up wrong conditions for negative sync transitions. +* [[49046088f10cceaea7da97401d742d3fb59371f5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=49046088f10cceaea7da97401d742d3fb59371f5]] config: don't shutdown the libhal ctx if it failed to initialize (#23213). +* [[c73cd3b265c301b8a54ffe484d6c696f2abefb46|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c73cd3b265c301b8a54ffe484d6c696f2abefb46]] xfree86: Link libselinux with Xorg system libraries. +* [[6c292d17053eb2a7e7054e51210f423dbc0cb7e8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6c292d17053eb2a7e7054e51210f423dbc0cb7e8]] dix: update the sprite trace for all masters && floating slaves (#23257) (does not apply cleanly) +* [[6b5978dcf1f7ac3ecc2f22df06f7000f360e2066|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6b5978dcf1f7ac3ecc2f22df06f7000f360e2066]] Do not reset lastDeviceEventTime when we do dixSaveScreens +* [[2075d4bf9e53b8baef0b919da6c44771220cd4a5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2075d4bf9e53b8baef0b919da6c44771220cd4a5]] glx: If a destroyed window is bound to the current context, make it not current +* [[3020b1d43e34fca08cd51f7c7c8ed51497d49ef3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3020b1d43e34fca08cd51f7c7c8ed51497d49ef3]] glx: Clean up more thoroughly if the drawable of a current context goes away +* [[4aab05e3b3231f1ec9795a66a075d17a722634a7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=4aab05e3b3231f1ec9795a66a075d17a722634a7]] xf86_reload_cursors: fix cursor position to eliminate jumping after mode set +* [[1740cda7a37abc7d0a169ab4555b446adaa62211|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1740cda7a37abc7d0a169ab4555b446adaa62211]] Perform rotation redisplay before calling driver block handler (which may flush rendering) +* [[e7dd1efef408effe52d0bd3d3aa0b5d4ee10ed90|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e7dd1efef408effe52d0bd3d3aa0b5d4ee10ed90]] Ensure that rotation updates happen frequently + +## xserver 1.6.3 + +* [[b1c3dc6ae226db178420e3b5f297b94afc87c94c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b1c3dc6ae226db178420e3b5f297b94afc87c94c]] config: add HAL error checks +* [[1e816065e5ec3b9394dc1fa5815457a664e15fd9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1e816065e5ec3b9394dc1fa5815457a664e15fd9]] Don't printf NULL pointers on HAL connection error +* [[048697ccfa31cf7f7a29afa90a2f702d43efb7d4|http://cgit.freedesktop.org/xorg/xserver/commit/?id=048697ccfa31cf7f7a29afa90a2f702d43efb7d4]] quirk: use first detailed timing as preferred for PEA prod 9003 (rh#492359) +* [[283a081572d8db787c77d09e5ba6bcadebf4f7fe|http://cgit.freedesktop.org/xorg/xserver/commit/?id=283a081572d8db787c77d09e5ba6bcadebf4f7fe]] selinux: Only activate if policy says to be an object manager +* [[442967c90dd9d8483a56bdc9237c49e33d619126|http://cgit.freedesktop.org/xorg/xserver/commit/?id=442967c90dd9d8483a56bdc9237c49e33d619126]] Remove hardcoded gcc -Wall option from configure.ac + +### xserver 1.6.2.901 + +* [[http://lists.freedesktop.org/archives/xorg-devel/2009-July/001338.html|http://lists.freedesktop.org/archives/xorg-devel/2009-July/001338.html]] Fix build of drivers with 1.6.2 when not using --install-libxf86config +* [[0eb19f9437b7d8c19592e49eedb028771d300d80|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0eb19f9437b7d8c19592e49eedb028771d300d80]] xdmcp: Don't crash on X -query with more than 255 IP addresses. (#20675) +* [[Bug 22885|https://bugs.freedesktop.org/show_bug.cgi?id=22885]] Fix key repeat problem. + * Patch at [[https://bugs.freedesktop.org/attachment.cgi?id=27898|https://bugs.freedesktop.org/attachment.cgi?id=27898]] +* [[35758544813f156eaac28844e693b2a28f6de316|http://cgit.freedesktop.org/xorg/xserver/commit/?id=35758544813f156eaac28844e693b2a28f6de316]] EXA: Only pass CT_YXBANDED to RECTS_TO_REGION() if that is really true. +* [[2c69deb92e11542f615df0f24fdc03e3b4415475|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2c69deb92e11542f615df0f24fdc03e3b4415475]] configure: libXinerama isn't needed anymore (reduce deps for embedded setups -- [[RemiCardona|RemiCardona]]) +* [[b3e3154cce47add97f5561088036ce3b9e7dc937|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b3e3154cce47add97f5561088036ce3b9e7dc937]] One = is more than adequate here. Make is sh safe. +* [[f8dd80d13bb5313a11b38b280f8ad3e22f0a6300|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f8dd80d13bb5313a11b38b280f8ad3e22f0a6300]] Replace dixLookupResource by dixLookupResourceBy{Type,Class} (Fixes xfs -- [[RemiCardona|RemiCardona]]) +* [[12e725d08b4cf7dbb7f09b9ec09fa1b621156ea9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=12e725d08b4cf7dbb7f09b9ec09fa1b621156ea9]] randr: fix server crash in RRGetScreenInfo +* [[cadf65a6e190a8952ad3cc216dc9ea55241de91a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=cadf65a6e190a8952ad3cc216dc9ea55241de91a]] randr: Nuke broken set_origin shortcut +* [[6f59a8160042ea145514fdcb410f17f33fd437c2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6f59a8160042ea145514fdcb410f17f33fd437c2]] hw/xf86/modes: Set crtc mode/rotation/transform before calling set_mode_major +* [[b2bf67b61c564a4b92a429ca9ad455403161f33a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b2bf67b61c564a4b92a429ca9ad455403161f33a]] randr: fix operation order so that rotation+transform works +* [[0de58c88aba7ddd69b04f24ab5b2967c359aa69e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0de58c88aba7ddd69b04f24ab5b2967c359aa69e]] xfree86: move didLock assignment down to where the function pointer is valid. + +## xserver 1.6.2 + +* [[b349a764e98f0d8f221190157ffa0904b91beca5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b349a764e98f0d8f221190157ffa0904b91beca5]] xinerama: Put the proto version in the code instead using proto headers. +* [[2a8b8077d8f6001eb57deba60e1009fc99c28668|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2a8b8077d8f6001eb57deba60e1009fc99c28668]] dri2: support glXWaitGL & glXWaitX by copying fake front to front and vice-versa. +* [[https://bugs.freedesktop.org/attachment.cgi?id=27363|https://bugs.freedesktop.org/attachment.cgi?id=27363]] build system: fix make install +* [[2e2c5b216cc1c7a9bc26bd2c68226aaed5fc52ca|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2e2c5b216cc1c7a9bc26bd2c68226aaed5fc52ca]] dri2: Preserve compatibility with 1.6 DRI2 API/ABI + +### xserver 1.6.1.902 + +* The following 10 patches that fix front-buffer rendering with DRI2: + * Have these been tested to work with clients without the corresponding fixes? Obviously front-buffer rendering would remain broken in that case. -[[MichelDaenzer|MichelDaenzer]] + * In theory, yes. In practice, no. Commit ff6c7764c2909e4126403b7211faa6c58556b341 changes the DRI2 interface between the driver and the extension. When xf86-driver-intel was updated to the new interface, we changed the way that clients request stencils buffers (using DRI2BufferDepthStencil vs. DRI2BufferDepth and DRI2BufferStencil). This affects one driver (intel), and it will be resolved by Intel's 2009Q2 in a couple weeks. In the mean time, users upgrading their xserver can use DRI1. I don't think this should block pulling these patches to 1.6. If anything, not having them in 1.6 soon potentiates the same sort of compatibility for other drivers that will be releasing DRI2 support soon. - [[IanRomanick|IanRomanick]] + * For the record, those patches require a new release of dri2proto - [[RemiCardona|RemiCardona]] + * Yes. [[KristianHoegsberg|KristianHoegsberg]] released dri2proto 2.1 on June 12th, 2009. - [[IanRomanick|IanRomanick]] + * [[03aebed519986c4dd03e02b3b3d4af1f64595ca7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=03aebed519986c4dd03e02b3b3d4af1f64595ca7]] Use a #define instead of a magic number + * [[f250eea2e90fc50bec5214c2f41132b95edc2c46|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f250eea2e90fc50bec5214c2f41132b95edc2c46]] DRI2: update DRI2 private drawable width & height according to X drawable + * [[0d9d3f3e361f769822caedccf4c2a58cc9930ecc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0d9d3f3e361f769822caedccf4c2a58cc9930ecc]] DRI2: Force allocation of real-front buffer for non-windows as well + * [[ff6c7764c2909e4126403b7211faa6c58556b341|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ff6c7764c2909e4126403b7211faa6c58556b341]] DRI2: Implement protocol for DRI2GetBuffersWithFormat + * [[28ddfc88d8d547941c7f4713db527a3c2f9ec35a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=28ddfc88d8d547941c7f4713db527a3c2f9ec35a]] DRI2: Add interface for drivers to query DRI2 extension version + * [[d1e916d29be8b470cbc8cadcf6e83991fdbc5a9f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d1e916d29be8b470cbc8cadcf6e83991fdbc5a9f]] DRI2: Add missing front-buffer flush callback. + * [[de1e43181bd670877b994db221ad8a04b5d63324|http://cgit.freedesktop.org/xorg/xserver/commit/?id=de1e43181bd670877b994db221ad8a04b5d63324]] DRI2: Don't leave empty entries in private->buffers + * [[567cf67959b30432ae30f4851ec17b3a375ab838|http://cgit.freedesktop.org/xorg/xserver/commit/?id=567cf67959b30432ae30f4851ec17b3a375ab838]] DRI2: Synchronize the contents of the real and fake front-buffers + * [[f1a995d1496d73741731e32f475097c44a8da972|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f1a995d1496d73741731e32f475097c44a8da972]] DRI2: Do not send the real front buffer of a window to the client + * [[aa2928325fe51d94a636dde9c090e8f54a311a12|http://cgit.freedesktop.org/xorg/xserver/commit/?id=aa2928325fe51d94a636dde9c090e8f54a311a12]] DRI2: Add fake front-buffer to request list for windows +* [[557dbadf3be273255e8fdb12d9321f4e88bf2b65|http://cgit.freedesktop.org/xorg/xserver/commit/?id=557dbadf3be273255e8fdb12d9321f4e88bf2b65]] [[XkbSetNamedIndicator|XkbSetNamedIndicator]] should ignore SD's without LED's +* [[b0ad9e1ced9619f37acf77764c395c57b86cf463|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b0ad9e1ced9619f37acf77764c395c57b86cf463]] Remove long-gone '-co' option from Xserver man page +* [[d0dd649035fc3698c5b436f9d9d248116aa106a3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d0dd649035fc3698c5b436f9d9d248116aa106a3]] Remove references to rgb.txt from files section of Xserver and Xorg man page +* [[7d0f7518c2235a9dc783029971259ddaada2db20|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7d0f7518c2235a9dc783029971259ddaada2db20]] Fix byte swapping of XF86VidMode{Get,Set}[[GammaRamp|GammaRamp]] +* [[faf7dfa099f5b42a703313fbd1bf8afdad07a179|http://cgit.freedesktop.org/xorg/xserver/commit/?id=faf7dfa099f5b42a703313fbd1bf8afdad07a179]] randr12: looking up these bits if randr isn't initialised is bad. +* [[0e0642ee9466d3268476d0084a83a9d93a4aa555|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0e0642ee9466d3268476d0084a83a9d93a4aa555]] os: don't malloc memory in LogVMessageVerb. +* [[8b583ca2b21155359c6255f406c96599b277c762|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8b583ca2b21155359c6255f406c96599b277c762]] Xi: fix copy/paste error causing sizeof against wrong struct. +* [[50cc8adafca4ba3838d468278d6eb8a4692d2488|http://cgit.freedesktop.org/xorg/xserver/commit/?id=50cc8adafca4ba3838d468278d6eb8a4692d2488]] Xi: don't double-swap the XListDeviceProperties reply. +* [[1c101d75d4855b2698e3fc8d2dd662f20585812f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1c101d75d4855b2698e3fc8d2dd662f20585812f]] Don't leak canonical module name and patterns if module is built-in +* [[66539cc05d0b017b9feb4a038499907810140623|http://cgit.freedesktop.org/xorg/xserver/commit/?id=66539cc05d0b017b9feb4a038499907810140623]] Don't leak default font path when appending built-ins +* [[91b697efdefba125348dbcaf584ee51a7f8c9bf6|http://cgit.freedesktop.org/xorg/xserver/commit/?id=91b697efdefba125348dbcaf584ee51a7f8c9bf6]] Support setTexBuffer2 in AIGLX. (Needs mesa 7.5 or #ifdef protection code to work with mesa 7.4 -- [[RemiCardona|RemiCardona]]) +* [[525aa17f804d37d1cfcbbf6b8e6cddb45e999b20|http://cgit.freedesktop.org/xorg/xserver/commit/?id=525aa17f804d37d1cfcbbf6b8e6cddb45e999b20]] Bug #6428, #16458, #21464: Fix crash due to uninitialized VModMap fields. +* [[850675d4de4373e5df95507dbf2cd9affaaf54bc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=850675d4de4373e5df95507dbf2cd9affaaf54bc]] EXA: Take GC client clip type into account for migration. +* [[7c8327f0a75087a85864256a9cea80dd4b86def5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7c8327f0a75087a85864256a9cea80dd4b86def5]] EXA: Always damage glyph cache pixmap manually after uploading a glyph. +* [[737b49199a05299486064e6e762cf2a2f6f95be6|http://cgit.freedesktop.org/xorg/xserver/commit/?id=737b49199a05299486064e6e762cf2a2f6f95be6]] xfree86: restore default off for [[DontZap|DontZap]] +* [[04c9e80f083659e63cffec8969fb3a0cfc551a97|http://cgit.freedesktop.org/xorg/xserver/commit/?id=04c9e80f083659e63cffec8969fb3a0cfc551a97]] off by one fixes from alanc, rebased for the 1.6 branch +* [[b746a00cffca5c553b607a8e9c1074294a23b443|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b746a00cffca5c553b607a8e9c1074294a23b443]] Resync COPYING file with notices in code base as of xorg-server-1.6.1 +* [[Turn off ExaOptimizeMigration by default|http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=blob_plain;f=debian/patches/Change-default-for-ExaOptimizeMigration-to-false.diff;h=41930f9a255225ccf2fec6085975a6c4bb26b79c;hb=e026fa4df402a207f01b3bf99f70b355ca8719da]] as suggested by [[MichelDaenzer|MichelDaenzer]] in [[http://lists.x.org/pipermail/xorg-devel/2009-February/000187.html|http://lists.x.org/pipermail/xorg-devel/2009-February/000187.html]] +* [[6f9e22049862ee9ac7f604411d005d8bb1b2dd1c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6f9e22049862ee9ac7f604411d005d8bb1b2dd1c]] dix: ensure Activate/DeactivateGrab has a valid value. +* [[b1b5ec45c1cb650ccb8c659218f9481379c777d9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b1b5ec45c1cb650ccb8c659218f9481379c777d9]] kdrive: set Activate/Deactivate grab for input devices (#21591) +* [[e244a5991e2cc55f5aa2f6e5255f1dabf56f0235|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e244a5991e2cc55f5aa2f6e5255f1dabf56f0235]] dix/randr: Add missing fields to SRR*[[NotifyEvent|NotifyEvent]]() (#21987) +* [[69a9545d1f8110841538410818df19fd960412c5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=69a9545d1f8110841538410818df19fd960412c5]] Make RANDR 'set' timestamps follow client specified time. Bug 21987. +* [[Fedora:xserver-1.6.0-xinerama-cursors.patch|http://cvs.fedoraproject.org/viewvc/rpms/xorg-x11-server/F-11/xserver-1.6.0-xinerama-cursors.patch?revision=1.1]] - backport to 1.6 of [[66089e9129a821cfb1983d3d35f41b975a52de5e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=66089e9129a821cfb1983d3d35f41b975a52de5e]] xfree86: fix SWCursor check in xf86CursorSetCursor. + +### xserver 1.6.1.901 + +* [[44227ef1b77467c76147b9bf79bdd0e6305a522a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=44227ef1b77467c76147b9bf79bdd0e6305a522a]] DRI2: Send the version the code actually supports +* [[4cfb36f6ad2df01215028fec48d99239a0e4496b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=4cfb36f6ad2df01215028fec48d99239a0e4496b]] EXA: Handle separate alpha maps properly in Composite fallback, take two. +* [[3948b523893d3d44b6a088340c4252e969613769|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3948b523893d3d44b6a088340c4252e969613769]] EXA: Guard empty pending region warning by DEBUG_MIGRATE. +* [[Bug 20557|http://bugs.freedesktop.org/show_bug.cgi?id=20557]] Xinerama causes segfault on keypress on xserver-1.6.0 + * Patch at [[dix: ignore non-pointer events in XineramaCheckMotion (#20557)|http://bugs.freedesktop.org/attachment.cgi?id=24224]] +* [[efa31092d6703397121a0ada4f7205a8ecad3d3d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=efa31092d6703397121a0ada4f7205a8ecad3d3d]] xfree86: Remove device from inputInfo.devices if [[ActivateDevice|ActivateDevice]] failed. +* [[063833f3a6d9f8f657e3de309c8d6d5c3d606513|http://cgit.freedesktop.org/xorg/xserver/commit/?id=063833f3a6d9f8f657e3de309c8d6d5c3d606513]] Add XI 1.5 event and requests to protocol.txt +* [[4f86ee61a4abf7a29e565d095aa08abd0ca9dc66|http://cgit.freedesktop.org/xorg/xserver/commit/?id=4f86ee61a4abf7a29e565d095aa08abd0ca9dc66]] Add RandR 1.3 requests to protocol.txt +* [[b1dab580bdfb4acfe3feddeda6e760098ec4922a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b1dab580bdfb4acfe3feddeda6e760098ec4922a]] xfree86: edid quirk for Philips LCD LP154W01-TLAJ +* [[0dfb97f15f591f85e079f5829c77d0c328d00464|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0dfb97f15f591f85e079f5829c77d0c328d00464]] Bug#21324: Add quirk for Iiyama Vision Master 450 +* [[94648bb797d94b025746c60679c584e5be2fae28|http://cgit.freedesktop.org/xorg/xserver/commit/?id=94648bb797d94b025746c60679c584e5be2fae28]] Bug #21077: flicker when setting modes with KMS +* [[Bug 21459|https://bugs.freedesktop.org/show_bug.cgi?id=21459]] bogus events sent out whe XKB is disables + * Patch at [[Xi: don't send XKB mapping notifications when XKB is disabled|https://bugs.freedesktop.org/attachment.cgi?id=25226]] +* [[Bug 21455|http://bugs.freedesktop.org/show_bug.cgi?id=21455]] Bad event list generated when adding fake [[KeyRelease|KeyRelease]] + * Patch at [[dix: fix calculation of number of fake KeyRelease events|http://bugs.freedesktop.org/attachment.cgi?id=25218]] + +## xserver 1.6.1 + +* [[7b6400a1b8d2f228fcbedf17c30a7e3924e4dd2a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7b6400a1b8d2f228fcbedf17c30a7e3924e4dd2a]] glx: Fix drawable private leak on destroy +* [[603db34337a61754e0c5f71525011d10eab78411|http://cgit.freedesktop.org/xorg/xserver/commit/?id=603db34337a61754e0c5f71525011d10eab78411]] Xext: set POINTER_SCREEN flag in XTestFakeInput if necessary. (RH #490984) +* [[8a6ed44a8b2fc5f14729dc54fec17607ced03859|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8a6ed44a8b2fc5f14729dc54fec17607ced03859]] randr: Fix thinko in xf86TargetPreferred + * patch for bug causing only one mode available in randr +* [[669f6810af9a89187d6149841925fe765f3988ff|http://cgit.freedesktop.org/xorg/xserver/commit/?id=669f6810af9a89187d6149841925fe765f3988ff]] Xi: add XIPropToInt() auxiliary function. + * this patch is required for simple merging of the XATOM_FLOAT one. +* [[a48c81dcdf569a3f634ac23e08d2491354de6a36|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a48c81dcdf569a3f634ac23e08d2491354de6a36]] Xi: add XATOM_FLOAT to server-defined properties. +* [[0d9a42dc0380d1583889b6b6521bd5a2451735d4|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0d9a42dc0380d1583889b6b6521bd5a2451735d4]] Xi: don't crash on a NULL property name, just return None. +* [[f5bf1fdaf36163d5c2f1b9b51df96326ebbb0e9c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f5bf1fdaf36163d5c2f1b9b51df96326ebbb0e9c]] xkb: Fix wrong colour reference in XKB geometry copying. #20081 + +## xserver 1.6.0 + +* [[ab61033700b5383a7a15370dd054eaa80e72e811|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ab61033700b5383a7a15370dd054eaa80e72e811]] Add Extensions section to xorg.conf man page +* [[4901b8147e593d26d7a31a9b73a201254b948916|http://cgit.freedesktop.org/xorg/xserver/commit/?id=4901b8147e593d26d7a31a9b73a201254b948916]] XQuartz: Fix caps-lock +* [[ef320bdd5ec3419abba77041d3a4d96a3ff87563|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ef320bdd5ec3419abba77041d3a4d96a3ff87563]] DRI1: Make DRICreateDrawable return TRUE for pixmaps. (Fixes regression from a26c77ff432d2e85a2665fc36fca25143460c476 below) +* [[24c562f04b41d219c34f5fa3f963564accf329f2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=24c562f04b41d219c34f5fa3f963564accf329f2]] Update See Also lists in Xorg & xorg.conf man pages +* [[5f3f14179edf48aad518f6f707bfdc37c27267c6|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5f3f14179edf48aad518f6f707bfdc37c27267c6]] Xorg server core dump in xf86RandRModeRefresh(NULL) +* [[6a1850b8c677e2a2993f6f6b731ee3d35aa55d09|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6a1850b8c677e2a2993f6f6b731ee3d35aa55d09]] Correct warning for unknown [[GlxVisuals|GlxVisuals]] option in conf file +* [[8c560422b44e012053612754430d2b87dc44ed59|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8c560422b44e012053612754430d2b87dc44ed59]] More man page updates for 1.6 release for Xorg, xorg.conf & exa man pages +* [[b0d371ab0a6efd4956c3677faa20b2ac15c33765|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b0d371ab0a6efd4956c3677faa20b2ac15c33765]] randr: Don't send output property events on server exit +* [[c1db925d10fd37077bed90612ed95c3fd20cd2e2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1db925d10fd37077bed90612ed95c3fd20cd2e2]] Add atKeynames.h to libdmxinput_a_SOURCES so it's included in tarballs +* [[15bb6abd59fdefe7037237faaea1a39711a972ed|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=15bb6abd59fdefe7037237faaea1a39711a972ed]] XQuartz 39: XQuartz GLX Updates for 1.6 +* [[a665ed16f736cf1901b89448dc5d37f4d16dfaf4|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=a665ed16f736cf1901b89448dc5d37f4d16dfaf4]] XQuartz 40: XQuartz GLX Updates for 1.6 +* [[d514152195452ae11ec7769c76489651620ad380|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=d514152195452ae11ec7769c76489651620ad380]] XQuartz 41: XQuartz GLX Updates for 1.6 +* [[6461729647ff4441d80811e73f0c0d2f108f2700|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=6461729647ff4441d80811e73f0c0d2f108f2700]] XQuartz 42: Only call [[DarwinUpdateModKeys|DarwinUpdateModKeys]] when needed +* [[9cf264e67744262b9f45079e6cd752eb3e3b0e08|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=9cf264e67744262b9f45079e6cd752eb3e3b0e08]] XQuartz 43: XQuartz xpr DRI Updates for GLX +* [[f020900641b44a1142e5c2198e9678de2744454e|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=f020900641b44a1142e5c2198e9678de2744454e]] XQuartz 44: Fix builddir != srcdir issues and undef _XSERVER64 where appropriate on fat binary compilation +* [[94e417ac87a98cd5c6bf2d7c495d702748398931|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=94e417ac87a98cd5c6bf2d7c495d702748398931]] XQuartz 45: mieq: Wait for the server to finish initializing before letting other threads mieqEnqueue +* [[b57cb05c69acbedb00a97234099ea104309aa2cb|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=b57cb05c69acbedb00a97234099ea104309aa2cb]] XQuartz 46: [[SnowLeopard|SnowLeopard]] Help Book Name +* [[143224405ba74929c702a95de52b56df140b0d1b|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=143224405ba74929c702a95de52b56df140b0d1b]] XQuartz 47: [[SnowLeopard|SnowLeopard]] OpenGL.framework compat fix +* [[639f289dcdbe00a516820f573c01a8339e120ed4|http://cgit.freedesktop.org/xorg/xserver/commit/?id=639f289dcdbe00a516820f573c01a8339e120ed4]] EXA: Declare glyph cache picture as component-alpha when necessary. (#19233) +* [[5f3188228eb988bd8f08b62c84f98a8ff66ee283|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5f3188228eb988bd8f08b62c84f98a8ff66ee283]] Avoid a potential endless loop. (#19343) +* [[77c7a64e8885696665556c9fbcb3cffb552e367a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=77c7a64e8885696665556c9fbcb3cffb552e367a]] RandR rotations and reflections offset by one pixel + +#### 2008-12-9 + +* [[1dfed222e93f4684c2a450944a9a0ea9e085c43f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1dfed222e93f4684c2a450944a9a0ea9e085c43f]] Xext: fix [[MultiBuffer|MultiBuffer]] compilation error with [[TryClientEvents|TryClientEvents]]. (#18835) +* Revert [[8da8a0fec4b1b9d9208635dedb2f449dc99e0004|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8da8a0fec4b1b9d9208635dedb2f449dc99e0004]] dmx: claim we support XI 2. +* [[fd2d40b7ec5d685dac55453eb1f2da672dc83126|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fd2d40b7ec5d685dac55453eb1f2da672dc83126]] Xi: change XIUnRegisterPropertyHandler to XIUnregisterPropertyHandler +* [[110a71d11ab7a1a55a6a24d792457fdef0b0746d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=110a71d11ab7a1a55a6a24d792457fdef0b0746d]] Test for DRI2 extension in dri_internal.h and only enable AIGLX DRI2 if found. +* [[0b5ecabfb803cd820338fb0364521fe39b05578b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0b5ecabfb803cd820338fb0364521fe39b05578b]] randr: add swapped dispatch for RR[GS]etCrtcTransform +* [[dd128ddcdcbe254a9cdd973590f6a979a7f0427e|http://cgit.freedesktop.org/xorg/xserver/patch/?id=dd128ddcdcbe254a9cdd973590f6a979a7f0427e]] If AEI is on, disable 'vmmouse' in addition to 'kbd' and 'mouse'. +* [[ffb484f7ef84099019b196ef97bfb2355eb6d52a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ffb484f7ef84099019b196ef97bfb2355eb6d52a]] randr: Avoid needlessly creating a shadow framebuffer. +* [[39db182b637041255ed6dac739ff77c8e4e07c30|http://cgit.freedesktop.org/xorg/xserver/commit/?id=39db182b637041255ed6dac739ff77c8e4e07c30]] xfree86: init EQ before trying to initialise the devices (#18890) +* [[78a62d7713c708d067d8824ec41b0a0225c1997f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=78a62d7713c708d067d8824ec41b0a0225c1997f]] Xi: XIGetDevice needs to ignore the MORE_EVENTS flag. +* [[ee1a6c28418a6dad6c89f79a994f27bfbaa77368|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ee1a6c28418a6dad6c89f79a994f27bfbaa77368]] dix: fix calculation of valuator events. +* [[d507f60689f4e14383b0d24e63afc8cf836360d5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d507f60689f4e14383b0d24e63afc8cf836360d5]] xfree86: don't [[FatalError|FatalError]] on "too many input devices". +* [[bbf811514d3cdf84790bad5b852942a4e636902b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=bbf811514d3cdf84790bad5b852942a4e636902b]] ddxCtrls.c: XkbDDXUsesSoftRepeat always returns 1 now +* [[58a27d2932164e43c0db42b1286ec2f95250b420|http://cgit.freedesktop.org/xorg/xserver/commit/?id=58a27d2932164e43c0db42b1286ec2f95250b420]] Default to x86emu even on i386 linux + +#### 2008-12-16 + +* [[0bdfdaa7df8105c7ffc3248a4fdd5f64da67103c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0bdfdaa7df8105c7ffc3248a4fdd5f64da67103c]] randr: Add [GS]etOutputPrimary +* [[2ef02833d614c42693e019a444560e84f501b5dc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2ef02833d614c42693e019a444560e84f501b5dc]] randr: Mangle compat Xinerama reply based on primary output +* [[f0234a9eb88ed103bca7db73a833c472ab95b48f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f0234a9eb88ed103bca7db73a833c472ab95b48f]] randr: Mangle [[GetScreenResources|GetScreenResources]] sort order based on primary output +* [[2bc53ce66828b6c177e3298fa2f326c77c93e136|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2bc53ce66828b6c177e3298fa2f326c77c93e136]] randr: use primary output for RRFirstOutput() +* [[a82f10c5dd9fa74ff18759ab288bbd9c8b7ac4de|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a82f10c5dd9fa74ff18759ab288bbd9c8b7ac4de]] randr: clear primaryOutput when the output is deleted +* [[ca56d764d2be28c64fe15c9e37d534ef00117ad2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ca56d764d2be28c64fe15c9e37d534ef00117ad2]] xsync: Fix wakeup storm in idletime counter. +* [[7be6520d94df874c6bbd46d06a1830a12d0967f2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7be6520d94df874c6bbd46d06a1830a12d0967f2]] dolt: allow older versions of bash to compile the xserver (#19031). +* [[Xi: don't update VCP's valuators from DeviceValuator events #18882|http://lists.freedesktop.org/archives/xorg/2008-December/041231.html]] +* [[463e02e7de5da3e582a3a049110a476713c7210e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=463e02e7de5da3e582a3a049110a476713c7210e]] xkb: Allow NULL as rulesFile in [[XkbSetRulesDflts|XkbSetRulesDflts]]. +* [[bb072019fa8dd292a50ef433d05caeefd1304a73|http://cgit.freedesktop.org/xorg/xserver/commit/?id=bb072019fa8dd292a50ef433d05caeefd1304a73]] xfree86: don't render SW cursors for devices attached to VCP (#16805) +* [[8e3279134987a45f2a89c963ef2d33bc3d3c8179|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8e3279134987a45f2a89c963ef2d33bc3d3c8179]] xfree86: fix compiler warning (use of uninitialized variable) +* [[fb2a8d0e59a3d187255538f6add22ec67551507a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fb2a8d0e59a3d187255538f6add22ec67551507a]] Xi: silence compiler warning +* [[cbb9ee57f8f29d2a1c39946381471fcd3b8e495e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=cbb9ee57f8f29d2a1c39946381471fcd3b8e495e]] XQuartz 01: pbproxy: Simplify linking +* [[451050b1e2dc0f2f6356d74ddb6f52183a794e8f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=451050b1e2dc0f2f6356d74ddb6f52183a794e8f]] XQuartz 02: Removed unused option from configure.ac for launchd +* [[9ac2e68d86ed1eb6e3f6c900c60908813eca140e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9ac2e68d86ed1eb6e3f6c900c60908813eca140e]] XQuartz 03: Corrected name/command labels in the customization widget +* [[70930f6d31cc2ca16b40c17e101b106506a8337a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=70930f6d31cc2ca16b40c17e101b106506a8337a]] XQuartz 04: darwinPointer reports the actual pixel position now rather than a relative position +* [[8065953ea8c3b7d10c775f6b7fec629bb5a2c83c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8065953ea8c3b7d10c775f6b7fec629bb5a2c83c]] XQuartz 05: Removed some debug spew +* [[99b2cbf061a9d074e66e6220dc08f8b4624ea6bb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=99b2cbf061a9d074e66e6220dc08f8b4624ea6bb]] XQuartz 06: unsetenv(DISPLAY) if we're not org.x.X11 +* [[9cbed0a325175e7ddb751db54fe6c0f5a5cedd16|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9cbed0a325175e7ddb751db54fe6c0f5a5cedd16]] XQuartz 07: unset DISPLAY if we didn't get a launchd socket handoff +* [[fdf64256127b2661bd6aa81ac694350028d36c43|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fdf64256127b2661bd6aa81ac694350028d36c43]] XQuartz 08: Avoid using login /bin/sh blech. Just use a bash script to start the app, so it will inherit the right environment +* [[13eff12902be1b25d0ccc2089e08305f88949f32|http://cgit.freedesktop.org/xorg/xserver/commit/?id=13eff12902be1b25d0ccc2089e08305f88949f32]] XQuartz 09: fixed make dist +* [[5926b213b39a90601c73f026dc0699723f5ed10d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5926b213b39a90601c73f026dc0699723f5ed10d]] XQuartz 10: Fix path to executable +* [[fd31984e0c0f9a37087cd1cffaa3ba116b12c2e5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fd31984e0c0f9a37087cd1cffaa3ba116b12c2e5]] XQuartz 11: Tiger fix, don't call Xplugin code in the Appkit thread if Xplugin isn't threadsafe +* [[73987010b2ef9c67b6614e226c6fae65d834d8f3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=73987010b2ef9c67b6614e226c6fae65d834d8f3]] XQuartz 12: Updated menu item ordering for better HIG compliance +* [[2a61397d17339113b9e37995b06ca543589814ce|http://cgit.freedesktop.org/xorg/xserver/commit/?id=2a61397d17339113b9e37995b06ca543589814ce]] Fix typo in xf86PickCrtcs() +* [[f1c9b5ab230cbb4124d8d476ae4886d05022adcb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f1c9b5ab230cbb4124d8d476ae4886d05022adcb]] GLX: Changes resulting from changes to Mesa generator scripts / data +* [[7aa29b9d66c3cd0f8af4fafbe92efd0c0556d225|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7aa29b9d66c3cd0f8af4fafbe92efd0c0556d225]] Support -sharevts on FreeBSD. + +#### 2009-1-12 + +* [[0c6987df3b9b3a37d201d740d8248c326449835e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0c6987df3b9b3a37d201d740d8248c326449835e]] XAA: Disable offscreen pixmaps by default. +* [[6d8ea5104cf97dbf64612f58fc06f94f869ed5ec|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6d8ea5104cf97dbf64612f58fc06f94f869ed5ec]] Fix compilation with -Werror=format-security (and a small memleak) +* [[d61e902aab92c262e6c8ee9cd70aec4493cf6cae|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d61e902aab92c262e6c8ee9cd70aec4493cf6cae]] Don't log audit messages when -audit 0 specified +* [[d281866b74f7067f2704c278fe9720eafc0ee5ef|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d281866b74f7067f2704c278fe9720eafc0ee5ef]] mi 1: Clean up [[CopyGetMasterEvent|CopyGetMasterEvent]], re-use the memory. (NB: it seems [[0b4fef6337d88ae8ef05b8b73941350a9007565c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0b4fef6337d88ae8ef05b8b73941350a9007565c]] is needed for this to work - coling) +* [[a939368ab8140d48c1da4ba0bb229d13b221189c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a939368ab8140d48c1da4ba0bb229d13b221189c]] mi 2: Reuse memory in mieqProcessInputEvents rather than making excessive calls to calloc() +* [[aedd2f566df585db7a1614f302cc8d3feda54275|http://cgit.freedesktop.org/xorg/xserver/commit/?id=aedd2f566df585db7a1614f302cc8d3feda54275]] randr/xfree86: Fix a one off error in the panning calculations. +* [[102abeda37d6b62971a9952efa0453e38504ae0b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=102abeda37d6b62971a9952efa0453e38504ae0b]] XQuartz 13: Name the startup shell script X11 for better compatability +* [[fd6fb6a2771df152b57f9dfb159fa42a3b1d37cd|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=fd6fb6a2771df152b57f9dfb159fa42a3b1d37cd]] XQuartz 14: Get rid of white rectangle bug +* [[c3812aec973b7341a600e5d2d07d5a7f15abd609|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=c3812aec973b7341a600e5d2d07d5a7f15abd609]] XQuartz 15: Changed X11.sh to allow use of a ~/.x11run as requested by users of alternate shells +* [[ecc3a7b6090552c309fe8e264d527ddd666a5761|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=ecc3a7b6090552c309fe8e264d527ddd666a5761]] XQuartz 16: update quoting in case X11.app is moved to a directory with a space. +* [[4c256c0e9c4fe61990343c8bcf2e352c83d76e69|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=4c256c0e9c4fe61990343c8bcf2e352c83d76e69]] XQuartz 17: pbproxy: Release display notification lock when not needed to avoid a deadlock +* [[7dc0dafef1d241d396f215c506ec2d4f7d8e3a24|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=7dc0dafef1d241d396f215c506ec2d4f7d8e3a24]] XQuartz 18: Run applications via '/bin/sh -c ...' to support users who expect shell parsing +* [[7e7758e1780326ad867be74dbd583a154bad017b|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=7e7758e1780326ad867be74dbd583a154bad017b]] XQuartz 19: Update our "screens" when we toggle rootless rather than when we toggle fullscreen (makes our root window consistent and avoids a crash due to our root window being smaller than our screen) +* [[84f0c03418bf74188596635dcac128fc05f204ad|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=84f0c03418bf74188596635dcac128fc05f204ad]] XQuartz 20: Don't use keycode 0 to determine !swallow since our most common key to swallow is actually keycode=0 +* [[85347902d97f2d4937f63ae1fac62ee46a61c82f|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=85347902d97f2d4937f63ae1fac62ee46a61c82f]] XQuartz 22: Re-enable rlAccel +* [[61ae56f97326c57dda05632ca9f4873238ee18e1|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=61ae56f97326c57dda05632ca9f4873238ee18e1]] XQuartz 23: Reposition windows when we enter fullscreen to ensure our root window +* [[338f096861136fb6c4f604e93ff21277252676b7|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=338f096861136fb6c4f604e93ff21277252676b7]] XQuartz 24: Try harder to get the user's login environment +* [[8c6e8fa811c782c85e7fefbe75fe5480098739ae|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=8c6e8fa811c782c85e7fefbe75fe5480098739ae]] XQuartz 25: pbproxy: We explicitly need libX11 for pbproxy +* [[d790c9dd041a2c8e3513d14a556333219d0f8d5e|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=d790c9dd041a2c8e3513d14a556333219d0f8d5e]] XQuartz 26: Updated man page fullscreen_hotkeys fullscreen_menu +* [[c67a3e2972c75c02f1aeed94bc0a3c5272422267|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=c67a3e2972c75c02f1aeed94bc0a3c5272422267]] XQuartz 27: Workaround OSX VNC server bug for modifier key state +* [[4be8d7346b9fdc014b72dd6c404ceecc0ef0d245|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=4be8d7346b9fdc014b72dd6c404ceecc0ef0d245]] XQuartz 28: Better avoid stuck keys on context switches +* [[9faf3de7e5610af340b92acb1b86bf03b6f2241a|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=9faf3de7e5610af340b92acb1b86bf03b6f2241a]] XQuartz 29: Honor system key repeat rate +* [[0d2621b6d4684ec62e67156a5a9dbdd3297f9cb0|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=0d2621b6d4684ec62e67156a5a9dbdd3297f9cb0]] XQuartz 30: Make sure to reset the saved key state when deactivating X11.app +* [[0676a580fcc05d54049269028a34358935a4101c|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=0676a580fcc05d54049269028a34358935a4101c]] XQuartz 31: Don't use NX_SECONDARYFNMASK, NX_NUMERICPADMASK, NX_HELPMASK +* [[adbfd49da2453b58a9e13b09c62e0611ea1c3f77|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=adbfd49da2453b58a9e13b09c62e0611ea1c3f77]] XQuartz 32: pbproxy: Push dpy init and CFRunLoop hook setup into the pbproxy thread to avoid possible deadlock +* [[df6ca888b0c04fdf4ff2d7fb4a414275b983ed34|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=df6ca888b0c04fdf4ff2d7fb4a414275b983ed34]] XQuartz 33: copyright date updated for 2009 +* [[65ab2f44ea7fc4d87e021bed548eda81fc3cbae7|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=65ab2f44ea7fc4d87e021bed548eda81fc3cbae7]] XQuartz 34: use a more compatible header for availability macros +* [[cc677cb4f458f371a4012ce0dc1121a52a2cb699|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=cc677cb4f458f371a4012ce0dc1121a52a2cb699]] XQuartz 35: cpp magic for 32/64 fat binary builds on OSX +* [[3534a5e5d9c5af85149c799f324257f89507fa23|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3534a5e5d9c5af85149c799f324257f89507fa23]] exa: Allow drivers to set non-NULL devPrivate.ptr for !offscreen pixmaps. +* [[027b440d4f9f0cdd46addff46fd2d5c44cd5c847|http://cgit.freedesktop.org/xorg/xserver/commit/?id=027b440d4f9f0cdd46addff46fd2d5c44cd5c847]] exa: preparing as source and finishing access as mask is a bad idea +* [[e1a3a1a0d85c9971aea65c2228b5fd4dbf3bf57a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e1a3a1a0d85c9971aea65c2228b5fd4dbf3bf57a]] xfree86: don't call [[CheckMotion|CheckMotion]] if a device hasn't been enabled. #19176 +* [[27011254c4de4e573a0851bf46892fb488db6522|http://cgit.freedesktop.org/xorg/xserver/commit/?id=27011254c4de4e573a0851bf46892fb488db6522]] xfree86: If an input device failed to activate, return immediately. +* [[aea6f19f25e13768b1d09fac4991d6a5e6c2cdac|http://cgit.freedesktop.org/xorg/xserver/commit/?id=aea6f19f25e13768b1d09fac4991d6a5e6c2cdac]] xfree86: don't restore the TTY mode if we didn't initialize it ourselves +* [[9c5dd7337fa93fb1650cc017e523b939dcbf482a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9c5dd7337fa93fb1650cc017e523b939dcbf482a]] Let the DDX decide on the [[XkbRulesDefaults|XkbRulesDefaults]]. +* [[13de7511b17b57a28668e1a60b196ccfe61dbcbe|http://cgit.freedesktop.org/xorg/xserver/commit/?id=13de7511b17b57a28668e1a60b196ccfe61dbcbe]] xfree86: Only use the evdev ruleset on linux +* [[1962af7ee3bdf54cfa674187dea67b9ad36cd5a1|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=1962af7ee3bdf54cfa674187dea67b9ad36cd5a1]] XQuartz 20.5: Added some debugging code that causes this next patch to fail if not merged first +* [[932ed6e949757926a17f7efe6b0255e38efa1152|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=932ed6e949757926a17f7efe6b0255e38efa1152]] XQuartz 21: Use depth=24 instead of [[FatalError|FatalError]] if we can't figure out our depth +* [[a1d35cee5907a76977ee43c49cb55c8f411c9794|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=a1d35cee5907a76977ee43c49cb55c8f411c9794]] XQuartz 36: Force DRI2 off on OSX +* [[c137f681680e1d04b1513a8be68aeda4d1c56fd5|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=c137f681680e1d04b1513a8be68aeda4d1c56fd5]] XQuartz 37: Misc 1.5->1.6 DDX changes for XQuartz +* [[7a8d2266861e74176b5310b83652a9c10a170494|http://cgit.freedesktop.org/xorg/xserver/commit/?h=xorg-server-1.6-apple&id=7a8d2266861e74176b5310b83652a9c10a170494]] XQuartz 38: mieq locking for thread safety in XQuartz +* [[56efbc0986e782da45addb05ece9f456d41d7a90|http://cgit.freedesktop.org/xorg/xserver/commit/?id=56efbc0986e782da45addb05ece9f456d41d7a90]] dix: drop x/y back into last.valuators before updating the history (#19285) +* [[488d45295105daf10ccd17ca93ae6a6f4d0104f1|http://cgit.freedesktop.org/xorg/xserver/commit/?id=488d45295105daf10ccd17ca93ae6a6f4d0104f1]] dix: [[EnqueueEvent|EnqueueEvent]] and [[PlayReleasedEvent|PlayReleasedEvent]] need to handle [[DeviceMotionNotifies|DeviceMotionNotifies]] +* [[d36adf52a2b2711d22b11105f7bd907d4493fb9b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d36adf52a2b2711d22b11105f7bd907d4493fb9b]] dix: fix [[WarpPointer|WarpPointer]] calls for devices with custom valuator ranges (#19297) +* [[a85f0d6b98237d8a196de624207acf1983a1859a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a85f0d6b98237d8a196de624207acf1983a1859a]] Xi: fix use of button->down - bitflags instead of int arrays. +* [[515ce3e4ba42605a1ee9979e8bb5acd3cf6470a3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=515ce3e4ba42605a1ee9979e8bb5acd3cf6470a3]] xkb: fix typo - missing negation when checking button state. +* [[b2756a71a432f7cf7c870a48676c98625512558d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b2756a71a432f7cf7c870a48676c98625512558d]] Xext: Send out correct events in ProcXTestFakeInput +* [[3d549438c29004d78032ecc50ab45ca0e3f49623|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3d549438c29004d78032ecc50ab45ca0e3f49623]] Don't alter device button maps in [[DoSetPointerMapping|DoSetPointerMapping]] +* [[d645721170b1196e5064b397cfbffd1da8c79bb1|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d645721170b1196e5064b397cfbffd1da8c79bb1]] mi: ensure chained button mappings from SD -> MD (#19282) +* [[f7f85f696570541e2dd43462675de9e6ee46f545|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f7f85f696570541e2dd43462675de9e6ee46f545]] Count the number of logically down buttons in buttonsDown +* [[717a961528ec69a6e630d536e15568670e0b398a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=717a961528ec69a6e630d536e15568670e0b398a]] Don't release grabs unless all buttons are up +* [[332d65ec7a6e94d75efe95d53742f137835274de|http://cgit.freedesktop.org/xorg/xserver/commit?id=332d65ec7a6e94d75efe95d53742f137835274de]] randr: Consider panned crtc's when calculating xinerama screen sizes. Question -- what about RRGetCrtcInfo? Resolved -- same as Xinerama + +#### 2009-2-17 + +* [[123093996507c4d3b6dc457240ce00f8ac42f410|http://cgit.freedesktop.org/xorg/xserver/commit/?id=76f18b94bd2719a8199334742d021c4d0806187d]] Add [[XkbDir|XkbDir]] to Files config file section +* [[123093996507c4d3b6dc457240ce00f8ac42f410|http://cgit.freedesktop.org/xorg/xserver/commit/?id=123093996507c4d3b6dc457240ce00f8ac42f410]] RANDR: Fail softly on [[GetPanning|GetPanning]] if the screen can't do it. +* [[49b93df8a3002db7196aa3fc1fd8dca1c12a55d6|http://cgit.freedesktop.org/xorg/xserver/commit/?id=49b93df8a3002db7196aa3fc1fd8dca1c12a55d6]] Default to use standard bitmap fonts, with builtins as fallback + * See [[http://lists.freedesktop.org/archives/xorg/2009-January/042632.html|http://lists.freedesktop.org/archives/xorg/2009-January/042632.html]] + * I've tested it in Xquartz, but I can't vouch for the hw/xfree86/* changes ... either way, something needs to be done to handle this - JH + * Tested with Xorg - DN +* [[a26c77ff432d2e85a2665fc36fca25143460c476|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a26c77ff432d2e85a2665fc36fca25143460c476]] glx: fix retval checks when failures occur for drawable creation. +* [[ea309e47457156b60aadbf113f04e5b6851029c8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ea309e47457156b60aadbf113f04e5b6851029c8]] Make crtc_notify wrap/unwrap code do nothing unless mode code is inuse +* [[b1d29784410b3b93037e5636f336ba608d8ad6e3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b1d29784410b3b93037e5636f336ba608d8ad6e3]] XQuartz 48: Remove extrenuous Activate/EnableDevice +* [[fd08be749e0b3c5de02a6ae8b3d21f92c5986157|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fd08be749e0b3c5de02a6ae8b3d21f92c5986157]] XQuartz 49: Conditionalize indirect.c for Tiger's OpenGL.framework +* [[0dbc356795bbab3889b5f1684f55bd193757d0c9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0dbc356795bbab3889b5f1684f55bd193757d0c9]] XQuartz 50: Fixes the condition in the previous patch to not exclude Leopard +* [[60bcdd687040db76490851d4b459284ce37020e0|http://cgit.freedesktop.org/xorg/xserver/commit/?id=60bcdd687040db76490851d4b459284ce37020e0]] x11-input.fdi: Add options needed to handle adding USB devices on Solaris +* [[5100d829a4d71ce4a9fbc2b81694a1fb90066ccf|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5100d829a4d71ce4a9fbc2b81694a1fb90066ccf]] glx: Don't match fbconfigs to visuals with mismatched channel masks. +* [[Bug 19754|http://bugs.freedesktop.org/show_bug.cgi?id=19574]] Pressing a multimedia key will cause the X Server to crash +* [[9fe9b6e4ef669b192ee349e3290db5d2aeea273c|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9fe9b6e4ef669b192ee349e3290db5d2aeea273c]] mi: don't call [[UpdateSpriteForScreen|UpdateSpriteForScreen]] if we have Xinerama enabled. #18668 +* [[panning-for-server-1.6|http://cgit.freedesktop.org/xorg/xserver/log/?h=panning-for-server-1.6]] branch (5 commits) +* [[16b11cd03d8c5def07f0e598f237f71a37883a46|http://cgit.freedesktop.org/xorg/xserver/commit/?id=16b11cd03d8c5def07f0e598f237f71a37883a46]] Correct the display of resouce length in pci probe line. +* [[b33905234025f005819c7e2acd653a3a0ecfeb82|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b33905234025f005819c7e2acd653a3a0ecfeb82]] xfree86: always force RAW mode under linux. +* [[ac470dfb4fadaa0b28b6f8b57f4f13a20842b897|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ac470dfb4fadaa0b28b6f8b57f4f13a20842b897]] Check for and report errors writing xorg.conf.new from Xorg -configure +* [[bd713794ceaa1b2890522554562103c0a2d50f04|http://cgit.freedesktop.org/xorg/xserver/commit/?id=bd713794ceaa1b2890522554562103c0a2d50f04]] Correct error message if specified config file is not found + +### Xserver 1.6 + +* [[066b17028a35956a089815716e38571f305469c5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=066b17028a35956a089815716e38571f305469c5]] XQuartz: [[BuildFailure|BuildFailure]] fix from 516f8e2cad1311a09764e2633644188d1e3c31bb +* [[43967514cd57ad836d7fb85c8c9e58ada07e0232|http://cgit.freedesktop.org/xorg/xserver/commit/?id=43967514cd57ad836d7fb85c8c9e58ada07e0232]] XQuartz: Support version strings like W.X.Y.Z-XXXXX +* [[4039603413f9f46d7f725463a70b4a51838e0049|http://cgit.freedesktop.org/xorg/xserver/commit/?id=4039603413f9f46d7f725463a70b4a51838e0049]] glx: Inialize best_score before calculating visual scores +* [[d2cf562bbad553d7f09b70202134f5b6ada0114e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d2cf562bbad553d7f09b70202134f5b6ada0114e]] Make [[RgbPath|RgbPath]] keyword in xorg.conf a non-fatal error +* [[5cc67ae94c066dcac78072ad8a819c3b602d8bab|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5cc67ae94c066dcac78072ad8a819c3b602d8bab]] exa: kill of exaImageGlyphBlt + +### Rejected + +These changes were nominated, but found not suitable for a 1.6.x release, though they will be in 1.7.0 and later: + +* [[09df7cc5ad7b72d8a23c3e22fc718aad8c16f4d3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=09df7cc5ad7b72d8a23c3e22fc718aad8c16f4d3]] Avoid dereferencing NULL pScreen in xf86CrtcSetModeTransform(). +* [[58c4116c47543b5e30c2232e7bee8efc0b9be176|http://cgit.freedesktop.org/xorg/xserver/commit/?id=58c4116c47543b5e30c2232e7bee8efc0b9be176]] XQuartz 51: DRI - Fix code for pixmaps +* [[630518766b01022c49fe3a9e7d501808f71b06e2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=630518766b01022c49fe3a9e7d501808f71b06e2]] XQuartz 52: More GLXPixmap work for OSX +* [[e46f02fa2de79261221b42ab73f9daa2ce8ac650|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e46f02fa2de79261221b42ab73f9daa2ce8ac650]] Xext: allocate a separate event list for XTest events (#23100) (does not apply as-is cleanly) (unnecessary as 1.6 doesn't use the DIX event queue from SIGIO) +* [[bfb219f532f3c78ba905424365ee7c5f7b5f21a2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=bfb219f532f3c78ba905424365ee7c5f7b5f21a2]] input: allow for detectable autorepeat. (#22515) + * too invasive, imo. this patch has indentation stuff + XI2-dependent stuff that doesn't work on 1.6, so it requires extra time and testing to apply. [whot] +* [[34eddbbb73bb16395dba0818247909c1b4bee4c2|http://cgit.freedesktop.org/xorg/xserver/commit/?id=34eddbbb73bb16395dba0818247909c1b4bee4c2]] Fix undefined symbols on alpha + * Not needed on 1.6 as these symbols were already _X_EXPORT'd + + +--- + + + + +## Features Removed + +* X server libraries: [[cfb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0dab6fa3582b70ccd0f01459902415c28dbc81ff]], [[afb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=20ea99c655140e101f2d20cfab78fb22765fec62]], [[mfb/xf1bpp|http://cgit.freedesktop.org/xorg/xserver/commit/?id=eabcfce0a68d504d11be9479f09e66f574dd2f21]] +* X server support for obsolete/unused/broken/unmaintained extensions: [[AppGroup|http://cgit.freedesktop.org/xorg/xserver/commit/?id=eafaf40fb3368ca7e4cf48336fdb7a6c9f536bfa]], [[EVI|http://cgit.freedesktop.org/xorg/xserver/commit/?id=13adef8a17d8815f4db2aaac30ae04438e125343]], [[MIT-SUNDRY-NONSTANDARD|http://cgit.freedesktop.org/xorg/xserver/commit/?id=25827fde68d3bb02a2b7e05fae53a1d97edf1f76]], [[TOG-CUP|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a7503615a6893749d512f75d37646273f31b9dbf]], [[XTrap|http://cgit.freedesktop.org/xorg/xserver/commit/?id=cbc20d92de92aad5ca240310a9156ccf97c24a01]], [[XFree86-Misc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=22e64108ec63ba77779891f8df237913ef9ca731]], [[XEvIE|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f4036f6ace5f770f0fe6a6e3dc3749051a81325a]] +* X server command line flags: [[-co|http://cgit.freedesktop.org/xorg/xserver/commit/?id=41b68e0dea9305d66bca2fc4ad96db01f5342c6d]], [[-bestrefresh|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1f416fba994ed7a7e072a9f0a86b515855ea3bac]], [[-showunresolved|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5a72c45d42abc7227c6cf3d14fd7043ea7527c54]] +* X server bundled utilties: [[xorgconfig|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d34430414ac0e77eec61ab0ac9ef427b236eb639]], [[xorgcfg|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5c1e254cc85e9ad409b0217780545c29f62d5feb]], [[ioport|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b74927c3844bc2650d95f604fe782d95ade067f1]], [[kbd_mode|http://cgit.freedesktop.org/xorg/xserver/commit/?id=8c0518379089d230060e9ff672ba5eba34198325]] +* Unmaintained X server variants: [[Xgl|http://cgit.freedesktop.org/xorg/xserver/commit/?id=d15b3790307053587df8daed1936ff6923881b63]], [[Xprt|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1c8bd318fbaf65890ef16fe26c76dd5e6f14dfde]] (moved to [[separate xprint git repo|http://cgit.freedesktop.org/xorg/xprint/]])
\ No newline at end of file diff --git a/Server17Branch.mdwn b/Server17Branch.mdwn new file mode 100644 index 00000000..aea08045 --- /dev/null +++ b/Server17Branch.mdwn @@ -0,0 +1,92 @@ + + +## Schedule + +* 1.7.0: Released 2009-10-01 +* 1.7.1: Released 2009-10-22 +* 1.7.2: Scheduled 2009-11-26 + +## Features + +* X Input 2.0 +* Mandatory XKB +* Support for symbol visibility +* EXA mixed pixmaps +* VGA arbitration + +## Proposing patches for 1.7.x + +The 1.7 branch has reached the [[end|http://lists.x.org/archives/xorg-devel/2010-June/009460.html]] of its active development lifecycle. Patches may be committed directly to the [[server-1.7-branch|http://cgit.freedesktop.org/xorg/xserver/log/?h=server-1.7-branch]]. If you feel the need to make an additional maintenance release from this branch, please discuss it on the [[xorg-devel|http://lists.x.org/mailman/listinfo/xorg-devel]] mailing list after making sure it [[doesn't perform worse|http://lists.x.org/archives/xorg-devel/2010-June/009484.html]] than the previous release. + + +## Patches merged between RC2 and 1.7.0 + + +#### 2009-09-25 + +* [[824a09d856a5f750694e11d2fd2faaa3de705eaa|http://cgit.freedesktop.org/xorg/xserver/commit/?id=824a09d856a5f750694e11d2fd2faaa3de705eaa]] dix: move bounds check before access +* [[096f21bb7a1217443d8a03529b1a2938518eb24f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=096f21bb7a1217443d8a03529b1a2938518eb24f]] EXA: Fix some issues pointed out by clang. +* [[ce1fe8ddb4a4dbe6cfd909e5b1b73b459d742bec|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ce1fe8ddb4a4dbe6cfd909e5b1b73b459d742bec]] render: Don't add b8g8r8x8 format for depth 24. +* [[5402f18d9c3f7ba19cc05b3a814e3a9e94c8d551|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5402f18d9c3f7ba19cc05b3a814e3a9e94c8d551]] dix: report XI1 axis values correctly if first_valuator != 0 +* [[3b5bbb149d4c932d9624336f5cbe9fe71c87bea3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3b5bbb149d4c932d9624336f5cbe9fe71c87bea3]] configure: fix up tslib check once again + +#### 2009-09-26 + +* [[9fa73be9fa543a686ea35c861084f5af37d44caa|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9fa73be9fa543a686ea35c861084f5af37d44caa]] Require libXext >= 1.0.99.4 +* [[a9c274df5c37cb4ece6449e934342d8ff8e61705|http://cgit.freedesktop.org/xorg/xserver/commit/?id=a9c274df5c37cb4ece6449e934342d8ff8e61705]] kdrive: plug two memory leaks when freeing the KdKeyboard/Pointer. +* [[fd913136732ff14a0484ca28f60ac1fbf49be81d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fd913136732ff14a0484ca28f60ac1fbf49be81d]] dix: plug memory leak in [[DeviceEnterLeaveEvents|DeviceEnterLeaveEvents]]. +* [[e23bffc41b007f1bc2b8f5cd4ac54213062c95cc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e23bffc41b007f1bc2b8f5cd4ac54213062c95cc]] Fix build of unit tests when dtrace probes are enabled +* [[1818cbd70fc1f2e1487b4c678e67e28f1265c0ef|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1818cbd70fc1f2e1487b4c678e67e28f1265c0ef]] EXA: Extend mixed pixmaps scheme to allow driver [[PrepareAccess|PrepareAccess]] hook to fail. + +#### 2009-09-27 + +* [[e7c2598f565e8252dd66ee3e6212b310856476cb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e7c2598f565e8252dd66ee3e6212b310856476cb]] dmx: core events are always in screen coordinates when passed to GPE. +* [[43a2eb794f19a2ba56d653f465fc5f6b2ff0d3d3|http://cgit.freedesktop.org/xorg/xserver/commit/?id=43a2eb794f19a2ba56d653f465fc5f6b2ff0d3d3]] configure: Unify all library defines that require a specific version. +* [[9bd08c690fc687c4d69bb70536f3079a9184476d|http://cgit.freedesktop.org/xorg/xserver/commit/?id=9bd08c690fc687c4d69bb70536f3079a9184476d]] Xi: update axisVals with the right subpixel data. +* [[c9ec2bab2f258798fd6e6676698c732f09571a60|http://cgit.freedesktop.org/xorg/xserver/commit/?id=c9ec2bab2f258798fd6e6676698c732f09571a60]] dmx: undefine MITSHM, move undefs to miinitext.c. +* [[fc9d733bab3ff0e4e51b19c73b66196dca563a70|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fc9d733bab3ff0e4e51b19c73b66196dca563a70]] dmx: reshuffle linker order to avoid errors when MITSHM is undefined. +* [[73ae547d5e687ef10dea45801fc627e10ac4b659|http://cgit.freedesktop.org/xorg/xserver/commit/?id=73ae547d5e687ef10dea45801fc627e10ac4b659]] EXA: Fix mixed pixmaps crash with missing / failing [[UploadToScreen|UploadToScreen]] hook. ([[http://bugs.freedesktop.org/show_bug.cgi?id=24167|http://bugs.freedesktop.org/show_bug.cgi?id=24167]]) + +#### 2009-09-28 + +* merge [[xorg-server-1.7-apple (77099b933a0362d40a28f9afea46c5cc97c29e13)|http://cgit.freedesktop.org/xorg/xserver/log/?h=77099b933a0362d40a28f9afea46c5cc97c29e13]]: + * [[1a0dfde2d102d845f1ceda66ad7a078aa1b42ef9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=1a0dfde2d102d845f1ceda66ad7a078aa1b42ef9]] XQuartz: GLX capabilities: Allow 16bit accumulation buffers + * [[e0e2eaf1f30ebce4c0ff28416259d8e976fdf0d7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=e0e2eaf1f30ebce4c0ff28416259d8e976fdf0d7]] XQuartz: Use internal xshm header for new xextproto + * [[6e4fc5d066d9c1ea4fca444cfee1e73147c5fefb|http://cgit.freedesktop.org/xorg/xserver/commit/?id=6e4fc5d066d9c1ea4fca444cfee1e73147c5fefb]] Xi: [[CopyKeyClass|CopyKeyClass]] is not static for XQuartz + * [[fd1adc21a931e2dd1ff2e52b60a77c2153a30fe0|http://cgit.freedesktop.org/xorg/xserver/commit/?id=fd1adc21a931e2dd1ff2e52b60a77c2153a30fe0]] XQuartz: Nuke duplicate locks that make painful headaches + * [[29b2d9cdf5095399b79d9ff2a2f12f5a9c49cf1f|http://cgit.freedesktop.org/xorg/xserver/commit/?id=29b2d9cdf5095399b79d9ff2a2f12f5a9c49cf1f]] XQuartz: Fix a brain-o array indexing problem + * [[7958f6b75b3c6b8a827188af2e684f181bdd7688|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7958f6b75b3c6b8a827188af2e684f181bdd7688]] XQuartz: Add pressure/tilt property labels + * [[77099b933a0362d40a28f9afea46c5cc97c29e13|http://cgit.freedesktop.org/xorg/xserver/commit/?id=77099b933a0362d40a28f9afea46c5cc97c29e13]] XQuartz: Stop checking version numbers of the bundle because CFBundleGetVersionNumber is gimpish +* [[78ad6ca9a97440b74019c00a28144ea7d1e03431|http://cgit.freedesktop.org/xorg/xserver/commit/?id=78ad6ca9a97440b74019c00a28144ea7d1e03431]] xfree86: Hurd fix +* [[3db28f92b0c810b452506abbed299a204c90ba0b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3db28f92b0c810b452506abbed299a204c90ba0b]] configure: make XNEST default to auto. +* merge [[xorg-server-1.7-apple (b49dba33f94b51ba9a14803f0d81ccde2cb778f8)|http://cgit.freedesktop.org/xorg/xserver/log/?h=b49dba33f94b51ba9a14803f0d81ccde2cb778f8]]: + * [[a3dbde2de87ee4f577748a8c447501a3ea462559|http://cgit.freedesktop.org/xorg/xserver/commit/?id= a3dbde2de87ee4f577748a8c447501a3ea462559]] XQuartz: Transition from xEvent based mieq to [[InternalEvent|InternalEvent]] + * [[ceaa5c779ceed3de5ea53727649613be3133b24e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=ceaa5c779ceed3de5ea53727649613be3133b24e]] XQuartz: Force a keymap resync on the first keypress to workaround XKB mucking with our keymap + * [[de6cee11e1c335a0e5f708e7641e81d3cfe52529|http://cgit.freedesktop.org/xorg/xserver/commit/?id=de6cee11e1c335a0e5f708e7641e81d3cfe52529]] XQuartz: Fix inverse map from mode_switch to alt + * [[29cb904e4de2411a9b6dbe68694954788f0525f7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=29cb904e4de2411a9b6dbe68694954788f0525f7]] XQuartz: Nuke TSM + * [[54000bdcbca52a2de31f7c1a1147de6d8e9dbbb8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=54000bdcbca52a2de31f7c1a1147de6d8e9dbbb8]] XQuartz: Fix a bunch of compilation warnings about style + * [[dadab5a2279a19dcf709402d7f22f0cd48670db0|http://cgit.freedesktop.org/xorg/xserver/commit/?id=dadab5a2279a19dcf709402d7f22f0cd48670db0]] XQuartz: Fix [[QuartzSetCursor|QuartzSetCursor]] to match the expected prototype. + * [[cf2e3312cff3f341e9edba8c321a4ca7ffd8748e|http://cgit.freedesktop.org/xorg/xserver/commit/?id=cf2e3312cff3f341e9edba8c321a4ca7ffd8748e]] Rootless: Correct border rendering on parent-relative windows + * This one I'm not so sure about... it fixes the problem, but it's ugly. I'm hoping there's a better way. -JH + * [[b49dba33f94b51ba9a14803f0d81ccde2cb778f8|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b49dba33f94b51ba9a14803f0d81ccde2cb778f8]] Add (ok, fix) support for DTrace under OS X + +#### 2009-09-30 + +* [[f772014c435f56db56520ca13ffa39431684f122|http://cgit.freedesktop.org/xorg/xserver/commit/?id=f772014c435f56db56520ca13ffa39431684f122]] render: Plug a memory leak in [[AddGlyph|AddGlyph]]. (#23286) +* [[83023ffd09a84ff48e6b99f57ebad101a00478db|http://cgit.freedesktop.org/xorg/xserver/commit/?id=83023ffd09a84ff48e6b99f57ebad101a00478db]] xfree86: use the DDC size if either width or height of [[DisplaySize|DisplaySize]] is bogus. +* [[0c2731596f27f2cdf5000ba41de37e7eb86ad6f9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=0c2731596f27f2cdf5000ba41de37e7eb86ad6f9]] Put tests for zero-sized strings in quotes (#24060) +* [[19be992d9dc542b61fa3f4fd32a09071c9e64880|http://cgit.freedesktop.org/xorg/xserver/commit/?id=19be992d9dc542b61fa3f4fd32a09071c9e64880]] ephyr: if -parent is given, check for a trailing -screen. (#24144) + +#### 2009-10-01 + +* [[db98b26ee145f70e732e2cf4a6ac3de77fdf4adc|http://cgit.freedesktop.org/xorg/xserver/commit/?id=db98b26ee145f70e732e2cf4a6ac3de77fdf4adc]] Re-fix DGA removal. +* [[b5fcc5553eb784c9f4826936e839079c0cdee55a|http://cgit.freedesktop.org/xorg/xserver/commit/?id=b5fcc5553eb784c9f4826936e839079c0cdee55a]] exa: avoid infinite loops if UTS sw fallbacks. +* [[758ab55d2defc78d0169fd61a7036eb9f889e9e7|http://cgit.freedesktop.org/xorg/xserver/commit/?id=758ab55d2defc78d0169fd61a7036eb9f889e9e7]] render: set the glyph picture to NULL by default. + * needed for 622fc98fd08aba98369e6933c3ab8c9ff85385d5 +* [[622fc98fd08aba98369e6933c3ab8c9ff85385d5|http://cgit.freedesktop.org/xorg/xserver/commit/?id=622fc98fd08aba98369e6933c3ab8c9ff85385d5]] render: Fix crash in [[RenderAddGlyphs|RenderAddGlyphs]] (#23645) + +#### 2009-10-02 + +* [[3ebb82d61c2b56e8f7145443a552a4e913bbfc80|http://cgit.freedesktop.org/xorg/xserver/commit/?id=3ebb82d61c2b56e8f7145443a552a4e913bbfc80]] rotate: drop unwrapping inside block handler. +* [[64fe5784b49347e1fd27b0c463be5c16557594c9|http://cgit.freedesktop.org/xorg/xserver/commit/?id=64fe5784b49347e1fd27b0c463be5c16557594c9]] configure: if xnest was requested but modules weren't found, fail. +* [[45f447dafded5adfe11b7df3325c2d8f6ae0639b|http://cgit.freedesktop.org/xorg/xserver/commit/?id=45f447dafded5adfe11b7df3325c2d8f6ae0639b]] dix: force a minimum of 0 for screen coordinates.
\ No newline at end of file diff --git a/Server18Branch.mdwn b/Server18Branch.mdwn new file mode 100644 index 00000000..30c9fcb1 --- /dev/null +++ b/Server18Branch.mdwn @@ -0,0 +1,21 @@ + +Release manager: [[KeithPackard|KeithPackard]] + +Stable branch maintainer: [[PeterHutterer|PeterHutterer]] + + +## Schedule + +* End of feature merge window: 2009-12-31 +* End of bugfix window: 2010-2-28 +* Release of 1.8.0: 2010-3-31 + +## Features + +* [[New input hotplug and configuration system|http://who-t.blogspot.com/2010/01/new-configuration-world-order.html]], including: + * [[HAL Replacement|XorgHAL]] - udev support for Linux integrated, other OS'es TBD + * [[xorg.conf.d|http://lists.freedesktop.org/archives/xorg-devel/2009-November/003710.html]] + +## Proposing patches for 1.8.x + +The 1.8 branch has reached the [[end|http://lists.x.org/archives/xorg-devel/2010-June/009460.html]] of its active development lifecycle. Patches may be committed directly to the [[server-1.8-branch|http://cgit.freedesktop.org/xorg/xserver/log/?h=server-1.8-branch]]. If you feel the need to make an additional maintenance release from this branch, please discuss it on the [[xorg-devel|http://lists.x.org/mailman/listinfo/xorg-devel]] mailing list after making sure it [[doesn't perform worse|http://lists.x.org/archives/xorg-devel/2010-June/009484.html]] than the previous release. diff --git a/Server19Branch.mdwn b/Server19Branch.mdwn new file mode 100644 index 00000000..3afa7abc --- /dev/null +++ b/Server19Branch.mdwn @@ -0,0 +1,44 @@ + +Release manager: [[KeithPackard|KeithPackard]] + +Stable branch maintainer: [[JeremyHuddleston|JeremyHuddleston]] + + +## Schedule + +* End of feature merge window: 2010-06-01 +* End of bugfix window: 2010-08-01 +* Release of 1.9.0: 2010-08-20 +See also the [[X.Org Calendar|http://www.google.com/calendar/embed?src=nl1n1fmvu091eqh35ldqspar80%40group.calendar.google.com&ctz=Australia/Brisbane]]. + + +## Features + +* dix devPrivates rework (changed by a memory-wise version) +* DRI2: + * [[new authentication mechanism|http://cgit.freedesktop.org/xorg/xserver/commit/?id=cdcb575664d3d60b662c542e782de83a047165c9]] allowing build the server without libdrm + * [[buffers invalidation|http://cgit.freedesktop.org/xorg/xserver/commit/?id=421606a8ef447d10c2ee0986f20e752056a47675]] to reduce unnecessary round trips to the X server + * lot of fixes. +* configuration: smart set up using xorg.conf.d (FIXME [[DanNicholson|DanNicholson]], [[PeterHutterer|PeterHutterer]]), start up of the server [[without output devices connected|http://cgit.freedesktop.org/xorg/xserver/commit/?id=5939e39a641773a36c22104e1184143678dca7a2]] +* xinput: [[invisible cursor sprite not damaging screen anymore|http://cgit.freedesktop.org/xorg/xserver/commit/?id=7c085aebfedeb621a6fbeb3f09f4fcc640452044]] (performance improvements) +* code clean-up: + * MAXSCREENS (almost) removal + * allocation function wrapping removal + * bus PCI related + * replacement of all X allocation functions (*alloc) with their C89 counterparts (performance improvement) + * removal of bzero + * region implementation from mi to dix + * mandatory RENDER +* documentation: conversion of [[LinuxDoc|LinuxDoc]] documents to DocBook/XML +* deprecation: mibank support, Multibuffer extension (MBE). +* besides lot of bug fixing as usual ([[sw cursor on multiple screens|http://cgit.freedesktop.org/xorg/xserver/commit/?id=518f3b189b6c8aa28b62837d14309fd06163ccbb]]) and big number of changes (339 commits since X server 1.8.0 - 9th Jun) + +## Proposing patches for 1.9.x + +Server 1.9.0 has been [[released|http://lists.freedesktop.org/archives/xorg-announce/2010-August/001390.html]]. Patches may be nominated for future 1.9.x releases using the process outlined below. + + * **Do not push to server-1.9-branch.** + * Patches for 1.9 must be in master first. Please follow the guidelines outlined on the [[XServer|XServer]] page to get a patch into master. Exceptions are patches where the master code has changed in a way that git master is not affected by a particular bug. + * For single patches: Once a patch is in master, let the stable branch maintainer know that this patch is to be cherry-picked to 1.9. Reply to the original patch email, placing the branch maintainer in TO and CC-ing the list. Make sure that the subject line contains `[PATCH 1.9]`. + * For multiple patches: Create a local branch and cherry-pick the patches required (Always use cherry-pick -x). Push this branch to your people.freedesktop.org repository and send a pull request to the stable branch maintainer, CC-ing the list. Make sure the subject line contains `[PULL 1.9]`. + * Only regressions over the previous stable will be accepted between the final rc and the release.
\ No newline at end of file diff --git a/SiteNavigation.mdwn b/SiteNavigation.mdwn new file mode 100644 index 00000000..d64c0419 --- /dev/null +++ b/SiteNavigation.mdwn @@ -0,0 +1,16 @@ + +SiteNavigation is the central place to explore this wiki. [[MoinMoin|MoinMoin]] supports these [[!MeatBall IndexingScheme desc="IndexingScheme"]]****s: + +* [[RecentChanges|RecentChanges]] +* [[TitleIndex|TitleIndex]] +* [[WordIndex|WordIndex]] +* [[FindPage|FindPage]] +* [[WantedPages|WantedPages]] +* [[OrphanedPages|OrphanedPages]] +* [[RandomPage|RandomPage]] +* [[PageSize|PageSize]] +At the bottom of each page, there are actions that allow to navigate to other pages related to the current page: + +* Like****Pages +* Local****Site****Map +Additionally, there are the `[[PageList]]`, `[[FullSearch('text')]]` and `[[TableOfContents]]` macros, which allow you to automatically generate indices for cohesive parts of a wiki. diff --git a/SponsorshipPage.mdwn b/SponsorshipPage.mdwn new file mode 100644 index 00000000..e0b82889 --- /dev/null +++ b/SponsorshipPage.mdwn @@ -0,0 +1,10 @@ + +# Information for Sponsors + +X.Org is trying to do an extremely big, important job with limited resources. Sponsorship and contributions of money, equipment, etc are extremely valuable to us in promoting and supporting X development. + +X.Org Foundation is a non-profit Delaware corporation and has applied for tax-exempt 501(c)(3) status, but has not yet received a tax exemption ruling from the IRS. Donations will not be tax deductible until this status is obtained from the IRS. However, upon recognition of tax exemption, all donations will be tax-deductible retroactive to the date of donation. + +Please contact our Treasurer, currently Stuart Kreitman <[[Stuart.Kreitman@oracle.com|mailto:Stuart.Kreitman@oracle.com]]>, for Tax ID information and any other financial information you need to facilitate your sponsorship. Please contact our Secretary, currently Bart Massey <[[bart@cs.pdx.edu|mailto:bart@cs.pdx.edu]]>, if you have general questions about sponsorship or contribution. + +Thank you for your support. diff --git a/StructuredText.mdwn b/StructuredText.mdwn new file mode 100644 index 00000000..5847234b --- /dev/null +++ b/StructuredText.mdwn @@ -0,0 +1,48 @@ + +Structured text is text that uses indentation and simple symbology to indicate the structure of a document. For the next generation of structured text, see [[!MoinMoin ReStructuredText desc="ReStructuredText"]] and [[here|http://dev.zope.org/Members/jim/StructuredTextWiki/StructuredTextNG]]. + +A structured string consists of a sequence of paragraphs separated by one or more blank lines. Each paragraph has a level which is defined as the minimum indentation of the paragraph. A paragraph is a sub-paragraph of another paragraph if the other paragraph is the last preceding paragraph that has a lower level. + +Special symbology is used to indicate special constructs: + +* A single-line paragraph whose immediately succeeding paragraphs are lower level is treated as a header. +* A paragraph that begins with a '-', '*', or 'o' is treated as an unordered list (bullet) element. +* A paragraph that begins with a sequence of digits followed by a white-space character is treated as an ordered list element. +* A paragraph that begins with a sequence of sequences, where each sequence is a sequence of digits or a sequence of letters followed by a period, is treated as an ordered list element. +* A paragraph with a first line that contains some text, followed by some white-space and '--' is treated as a descriptive list element. The leading text is treated as the element title. +* Sub-paragraphs of a paragraph that ends in the word 'example' or the word 'examples', or '::' is treated as example code and is output as is. +* Text enclosed single quotes (with white-space to the left of the first quote and whitespace or puctuation to the right of the second quote) is treated as example code. +* Text surrounded by '*' characters (with white-space to the left of the first '*' and whitespace or puctuation to the right of the second '*') is emphasized. +* Text surrounded by '**' characters (with white-space to the left of the first '**' and whitespace or puctuation to the right of the second '**') is made strong. +* Text surrounded by '_' underscore characters (with whitespace to the left and whitespace or punctuation to the right) is made underlined. +* Text encloded by double quotes followed by a colon, a URL, and concluded by punctuation plus white space, *or* just white space, is treated as a hyper link. For example: + * "Zope":[[http://www.zope.org/|http://www.zope.org/]] is ... +Is interpreted as '<a href="[[http://www.zope.org/">Zope</a>|http://www.zope.org/">Zope</a>]] is ....' + +**Note:** This works for relative as well as absolute URLs. + +* Text enclosed by double quotes followed by a comma, one or more spaces, an absolute URL and concluded by punctuation plus white space, or just white space, is treated as a hyper link. For example: + * "mail me", [[mailto:amos@digicool.com|mailto:amos@digicool.com]]. +Is interpreted as '<a href="[[mailto:amos@digicool.com">mail|mailto:amos@digicool.com">mail]] me</a>.' + +* Text enclosed in brackets which consists only of letters, digits, underscores and dashes is treated as hyper links within the document. For example: + * As demonstrated by Smith [12] this technique is quite effective. +Is interpreted as '... by Smith <a href="#12">[12]</a> this ...'. Together with the next rule this allows easy coding of references or end notes. + +* Text enclosed in brackets which is preceded by the start of a line, two periods and a space is treated as a named link. For example: + * . [12] "Effective Techniques" Smith, Joe ... +Is interpreted as '<a name="12">[12]</a> "Effective Techniques" ...'. Together with the previous rule this allows easy coding of references or end notes. + +* A paragraph that has blocks of text enclosed in '||' is treated as a table. The text blocks correspond to table cells and table rows are denoted by newlines. By default the cells are center aligned. A cell can span more than one column by preceding a block of text with an equivalent number of cell separators '||'. Newlines and '|' cannot be a part of the cell text. For example: + * [[!format txt """ +|||| **Ingredients** || +|| *Name* || *Amount* || +||Spam||10|| +||Eggs||3|| +"""]]renders like this: + * [[!table header="no" class="mointable" data=""" + **Ingredients** || + *Name* | *Amount* +Spam | 10 +Eggs | 3 +"""]] diff --git a/StuartKreitman.mdwn b/StuartKreitman.mdwn new file mode 100644 index 00000000..ec71426f --- /dev/null +++ b/StuartKreitman.mdwn @@ -0,0 +1,13 @@ + + +## Stuart Kreitman + +Email: stuart.kreitman AT SPAMFREE sun DOT com + +Helping move Solaris from Xsun to Xorg for Sparc and Sunray, configuration, multihead, laptop issues. + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/SummerOfCodeIdeas.mdwn b/SummerOfCodeIdeas.mdwn new file mode 100644 index 00000000..1c241568 --- /dev/null +++ b/SummerOfCodeIdeas.mdwn @@ -0,0 +1,178 @@ + + +# Project Ideas for Google Summer of Code / X.Org Endless Vacation of Code programs + + +## Goal + +The X.org board treats GSoC as an opportunity to teach new developers rather than a chance to get a pile of free code. With this perspective, if, in two months, the student actually has learned how to contribute to X Window System, that's a huge step forward. Creating a project which guides this process with a maximal chance of success is the only tricky part. + +When writing a proposal, please remember to make it detailed. Include at least the information called for in "[[What should a student application look like?|http://code.google.com/support/bin/answer.py?answer=60306&topic=10727]]", but including milestones and a project schedule is even better. See [[GSoCApplication|GSoCApplication]] for guidelines. + +X.Org is a large and comprehensive project with a huge number of possible opportunities for interesting Google / X.Org Summer of Code projects. This list contains a few of those opportunities that are particularly interesting to X.Org developers and potential mentors. Please note that these are just suggestions; if you have an idea for something else please ask. + +If you have questions, feel free to contact us on the [[X.Org mailing list|http://lists.freedesktop.org/mailman/listinfo/xorg]] or the [[X.Org IRC channel|irc://irc.freenode.net/#xorg-devel]]. + + +## 2013 Ideas + + +### Glamor + + +##### Glamor Performance Tuning + +* _Difficulty:_ Medium +* _Skills Required:_C, OpenGL +* _Helpful, but optional skills:_ GLSL, GPU driver development +* _Where to ask questions:_ [[glamor@lists.freedesktop.org|mailto:glamor@lists.freedesktop.org]], #dri-devel on irc.freenode.org +* _Description:_ +* Glamor is a helper library that uses OpenGL to accelerate X rendering. The goal of this task would be to improve the the performance of Glamor by profiling problematic areas and improving the. Some possible ideas: + 1. Implement a delayed flushing mechanism to avoid tiny drawing operation for each [[DrawElements/DrawArrays|DrawElements/DrawArrays]] call. + 1. Implement an atlas for small pixmap. + 1. Optimize trapezoid shader to reduce the overhead for those non-edge pixels. + 1. Optimize trapezoid/gradient shader to merge the mask/source creation and compositing into one shader. + +##### Glamor Xv support + +* _Difficulty:_ Easy +* _Skills Required:_C, OpenGL +* _Helpful, but optional skills:_ GLSL, GPU driver development +* _Where to ask questions:_ [[glamor@lists.freedesktop.org|mailto:glamor@lists.freedesktop.org]], #dri-devel on irc.freenode.org +* _Description:_ +* Glamor is a helper library that uses OpenGL to accelerate X rendering. The goal of this task would be to implement support for Xv (Xvideo) in glamor. Basic support would involve using OpenGL to implement colorspace conversion for various YUV formats. More advanced goals include: + 1. Improved scaling algorithms + 1. Support for brightness/contrast/saturation/hue adjustments + 1. Support for gamma adjustment + 1. Support for colorspace selection (ITU-R BT.601 vs. BT.709) + +### Mesa + + +#### GLSL Compiler + + +##### Find common patterns in real GLSL shaders + +* _Difficulty:_ Medium +* _Skills Required:_ C, C++ +* _Helpful, but optional skills:_ GLSL, compilers +* _Possible Mentor:_ [[IanRomanick|IanRomanick]] (idr on IRC) +* _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #dri-devel on irc.freenode.org +* _Description:_ +* Using Mesa's stand-along GLSL compiler as a basis, generate a database of IR from a large number of existing shaders (e.g., from shaderdb). Write a piece of software that will mine this database for "large" patterns that commonly occur in shaders. This information will be used by people working on the GLSL compiler to improve code generation for these sequences. + +##### Improved application of GLSL complier optimizations + +* _Difficulty:_ Easy +* _Skills Required:_ C, C++ +* _Helpful, but optional skills:_ GLSL, compilers +* _Possible Mentor:_ [[IanRomanick|IanRomanick]] (idr on IRC) +* _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #dri-devel on irc.freenode.org +* _Description:_ +* Mesa's GLSL compiler contains a large number of optimization passes. Each pass may change the code of a shader, and this may result in opportunities for other passes to make more changes. As a result, we run all of our optimization passes in a loop until the shader code stabilizes. This is expensive, and, though we have never observed this in the wild, it is possible that a shader may never stabilize. +* Find a static ordering, with possible repeats, of optimization passes that does not compromise the quality of the generated code. Measure the before and after speed of compiling a large set of real-world shaders. + +#### r600g + + +##### Add support for OpenCL local and private memory spaces + + * _Difficulty:_ Medium + * _Skills Required:_ C, C++ + * _Helpful, but optional skills:_ OpenCL, compilers, GPU driver development, LLVM + * _Possible Mentor:_ [[TomStellard|TomStellard]] (tstellar on IRC) + * _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #radeon or #dri-devel on irc.freenode.org + * _Description:_ + * This project would involve modifying the r600g driver and LLVM compiler backend to support reading and writing from local and private memory spaces as defined by the OpenCL specification. + +##### Improve VLIW5 scheduling in the LLVM backend + + * _Difficulty:_ Easy + * _Skills Required:_ C, C++ + * _Helpful, but optional skills:_ compilers, GPU driver development, LLVM + * _Possible Mentor:_ [[VincentLejeune|VincentLejeune]] (vlj on IRC) + * _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #radeon or #dri-devel on irc.freenode.org + * _Description:_ + * The idea is to improve hw utilization by improving instruction scheduling on VLIW5 hardware (r6xx-evergreen). This would require a way to represent trans slot compatibility for instructions and handle the additional constant read and literals limitations on this slot and updating the scheduler to take advantage of it. + +#### clover + + +##### Pick a popular OpenCL application and get it running with clover and at least one of the compute capable drivers (r600g or radeonsi) + +* _Difficulty:_ Depends on the application +* _Skills Required_ C, C++, OpenCL +* _Helpful, but optional skills:_ Compilers, LLVM +* _Possible Mentor:_ [[TomStellard|TomStellard]] (tstellar on IRC) +* _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #radeon or #dri-devel on irc.freenode.org +* _Description:_ +* This project is pretty straightforward: Pick an application and fix bugs or implement missing features in clover and/or the gallium drivers until it works. In order to come up with a good proposal for this project a student will need to first investigate their chosen application to determine what needs to be done to get it working. Some possible applications: + * Any bitcoin client (r600g = Medium / radeonsi = Hard) + * GEGL filters in GIMP (r600g = Easy / radeonsi = Hard) + * Luxmark (r600g = Hard / radeonsi = Very Hard) + +#### Intel + + +##### Implement GLSL 1.30 for older chipsets than SandyBridge + +* _Difficulty:_ Medium +* _Skills Required:_ C, C++ +* _Helpful, but optional skills:_ GLSL, compilers +* _Possible Mentor:_ [[PaulBerry|PaulBerry]] (stereotype441 on IRC) +* _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #dri-devel on irc.freenode.org +* _Description:_ +* Implement GLSL 1.30 support for pre-Sandybridge asics that support it. For additional details see: [[https://bugs.freedesktop.org/show_bug.cgi?id=59187|https://bugs.freedesktop.org/show_bug.cgi?id=59187]] + +### Piglit + + +#### GL/GLSL tests for GL 3.2, 3.3 + +* _Difficulty:_ Easy-Medium +* _Skills Required:_ C +* _Useful skills:_ OpenGL, GLSL programming +* _Hardware/Software required:_ driver supporting >= OpenGL 3.2 +* _Possible Mentor:_ [[JordanJusten|JordanJusten]] (jljusten on IRC) +* _Where to ask questions:_ [[mesa-dev@lists.freedesktop.org|mailto:mesa-dev@lists.freedesktop.org]], #dri-devel on irc.freedesktop.org +* _Description:_ +* Write tests for OpenGL 3.2 / GLSL 1.50 and newer. Proposal should identify: + * GL/GLSL version/features you plan to focus on + * Number of tests you estimate completing + * Hardware/driver you have access to + +### X Server + + +#### Shatter support for the X Server (Xinerama replacement) + + * _Difficulty:_ Hard + * _Skills Required:_ C + * _Helpful, but optional skills:_ GPU driver development + * _Possible Mentor:_ [[DaveAirlie|DaveAirlie]] (airlied on IRC) + * _Where to ask questions:_ [[xorg-devel@lists.x.org|mailto:xorg-devel@lists.x.org]] or #xorg-devel on irc.freenode.org + * _Description:_ + * This project would involve adding an impedance layer to the X Server to divide rendering between multiple GPUs each covering different areas of a larger desktop. For more details: [[http://mirror.linux.org.au/linux.conf.au/2013/ogv/Teaching_the_X_server_new_tricks.ogv|http://mirror.linux.org.au/linux.conf.au/2013/ogv/Teaching_the_X_server_new_tricks.ogv]] (shatter discussion starts at ~24:00). + +### Kernel + + +#### Implement working rendernode support + + * _Difficulty:_ Medium + * _Skills Required:_ C + * _Helpful, but optional skills:_ GPU driver development + * _Possible Mentors:_ [[DaveAirlie|DaveAirlie]] (airlied on IRC), [[DanielVetter|DanielVetter]] (danvet on IRC) + * _Where to ask questions:_ [[dri-devel@lists.freedesktop.org|mailto:dri-devel@lists.freedesktop.org]] or #dri-devel on irc.freenode.org + * _Description:_ + * This project would involve adding a new interface to the drm to allow rendering on drm nodes without being master. This could also be expanded to cover display resource allocation for things like multiseat. Further information: + 1. [[http://airlied.livejournal.com/72187.html|http://airlied.livejournal.com/72187.html]] + 1. [[http://lists.freedesktop.org/archives/dri-devel/2012-April/021326.html|http://lists.freedesktop.org/archives/dri-devel/2012-April/021326.html]] + 1. [[http://lists.freedesktop.org/archives/dri-devel/2012-September/028338.html|http://lists.freedesktop.org/archives/dri-devel/2012-September/028338.html]] + +### Xpra + +See this page for ideas: [[https://www.xpra.org/trac/wiki/ProjectIdeas|https://www.xpra.org/trac/wiki/ProjectIdeas]] + +See also: [[ToDo|ToDo]] diff --git a/SummerOfCodeIdeas2008.mdwn b/SummerOfCodeIdeas2008.mdwn new file mode 100644 index 00000000..26cee0c7 --- /dev/null +++ b/SummerOfCodeIdeas2008.mdwn @@ -0,0 +1,97 @@ + + +## Goal + +The X.org board treats GSoC as an opportunity to teach new developers rather than a chance to get a pile of free code. With this perspective, if, in two months, the student actually has learned how to contribute to X Window System, that's a huge step forward. Creating a project which guides this process with a maximal chance of success is the only tricky part. + + +## Ideas + +Ideas for projects for students looking to participate in Google's Summer of Code. Please note that these are just suggestions; if you have an idea for something else please ask. + +When writing a proposal, please remember to make it detailed. Include at least the information called for in "[[What should a student application look like?|http://code.google.com/support/bin/answer.py?answer=60306&topic=10727]]", but including milestones and a project schedule is even better. See [[X.Org-GSoC2008-Application|X.Org-GSoC2008-Application]] for guidelines. + + +### Xserver core + +* Move the dmx muxing code into the server to replace the existing xinerama mux code +* EXA support for surfaces larger than the hardware limits +* Infrastructure for direct-rendering GL windows larger than the hardware supports +* Investigate redoing miarc/miwideline/etc. for smaller size and better performance + +### Xinerama + +* Composite/Xinerama integration +* Hotplugging additional local and remote displays +* Auto enabling and disabling Xinerama screens. +* Make Xinerama handle more than just X screens + +### Xdmx + + * Integrate with the rootless code a la Xdarwin and Cygwin/X, for floating window migration + * Add support for Fixes/Damage/Composite + * Fix input + +### XCB + + * Auto-generate server-side protocol stubs from XCB's protocol descriptions + * Implement a new language binding for XCB + * Finishing the Haskell language binding would be really cool. + * Implement a more complete test suite for XCB + * Port Gdk and/or Qt to XCB + * Port the important X utilities (xdpyinfo, xhost, etc.) to XCB + * The [[XCB demos|http://gitweb.freedesktop.org/?p=xcb;a=tree;f=xcb-demo]] include partial ports of xdpyinfo and xrandr. + * You'd have to port a lot of applications to make this an interesting Summer of Code project. + * See [[XCBToDo|http://xcb.freedesktop.org/XCBToDo]] and Bugzilla(XCB) for more ideas, or contact [[jamey@minilop.net|mailto:jamey@minilop.net]] or [[xcb@lists.freedesktop.org|mailto:xcb@lists.freedesktop.org]]. + +### Xau/Xdmcp + + * Implement the XDM-AUTHORIZATION-2 authentification protocol for better IPv6/XDM support. (See [[Bug 277|https://bugs.freedesktop.org/show_bug.cgi?id=277]] and the never-adopted draft of the XDM-AUTHORIZATION-2 changes to the XDMCP protocol spec.) + * Replace the old/uncompiliable KERBEROS-5 authentication with GSS-API authentication. + +### Drivers + + * Add more support for EXA in the drivers; see [[ExaStatus|ExaStatus]] for a list. + * Add dualhead support to an unsupported chip (trident, mach64, s3virge, [[nv|https://bugs.freedesktop.org/show_bug.cgi?id=5190]], etc.) + * Add basic DRI support to an unsupported chip (trident, s3virge, glint, siliconmotion, etc.) + * Do some work on [[nouveau|http://nouveau.freedesktop.org/]] ; ideas include adding 3D support for more cards, better Xv/XvMC support through gallium, suspend/resume support, (see our [[TODO page|http://nouveau.freedesktop.org/wiki/ToDo]] for more ideas) + * More DRI-related ideas are visible on [[http://dri.freedesktop.org/wiki/GSoC_2008|http://dri.freedesktop.org/wiki/GSoC_2008]] + +### XQuartz (OSX) + +Some of these might require changes to libXplugin (proprietary Apple code), but Apple is more than willing to provide the needed hooks. Just join the [[xquartz-dev mailing list|http://trac.macosforge.org/projects/xquartz/wiki/MailingLists]] + + * New extension support + * RandR + * Composite + * Fix OpenGL support + * Switch to XF86DRI instead of AppleDRI + * Write a Mesa DRI driver that uses OpenGL.framework + * Top-Of-Tree syncing + * input model, keymapping needs to be reworked + * Copy/Paste proxying between OS-X and X11 + * Eliminate the need for AppleWM extension to allow other WMs to work better + * Handle exposé / spaces events inside the X server rather than quartz-wm (so other WMs can be used) + * Compositing window manager to replace quartz-wm (once Composite is enabled) + +### Misc + +* Add test cases for more extensions, especially newer ones like Render, Composite, etc. (possibly to XTS5; see [[TestGroup|TestGroup]] wiki) +* Introspection extension to support tools like xscope + * Would allow querying for request names and structures in generic fashion + * Look at xcb-proto descriptions +* Integrate NX in XCB or X protocol +* Create GUI or textual tool for assisted editing of XKB configuration database. +* Formally documenting XKB configuration syntax and configuration database structure. + +### DRI + + * GLX_EXT_texture_from_pixmap + * Update to latest spec + * More efficient implementation, ideally texturing directly from offscreen pixmaps + * Integrate properly with Composite, in particular, render to redirected windows correctly + * Port new memory manager changes to drivers other than i915 + * make the X server's Xsync extension use DRM vblank waits or signals (really a DRI/X cross project) + * rough patch is already available + * developer would get good exposure to server and DRM internals +See also: [[ToDo|ToDo]], [[Releases/7.4|Releases/7.4]], [[DRI ideas list|http://dri.freedesktop.org/wiki/SummerOfCode]]. diff --git a/SummerOfCodeResults2008.mdwn b/SummerOfCodeResults2008.mdwn new file mode 100644 index 00000000..5492804e --- /dev/null +++ b/SummerOfCodeResults2008.mdwn @@ -0,0 +1,12 @@ + +This page is a brief and highly belated report on the highly successful Google / X.Org Summer of Code 2008. Details, of course, are welcome. + +In 2008, Google / X.Org Summer of Code was able to accept five student applicants. As in previous years, each accepted student received a $4500 stipend (in two contingent payments at the midway point and at the end) to execute a proposed coding project useful to X.Org. + +Of the five students accepted, one dropped out early on. The remaining four completed their projects successfully. + + * Younes Manton, under the mentorship of Stephane Marchesin, completed the bulk of work on a full implementation of GPU-accelerated video decoding for X. + * Kristof Ralovich, under the mentorship of Bart Massey, worked on adding support for XCB-GLX to Mesa. In the end, this proved to be a debugging and architecture project that resulted in improvements to both codebases. + * Symeon Xenitellis, under the mentorship of Sergey Udaltsov, built a GUI tool for assisted editing of the XKB configuration database. + * Tiago Vignatti returned for a second year with Google / X.Org Summer of Code. Under the mentorship of Daniel Stone, he extended his 2008 Summer of Code project that moved X server pointer handling into a separate thread by moving remaining input code into this thread. +X.Org would like to thank the students for their great contributions to X, and also the mentors who volunteered their time to make these students a success. diff --git a/SupportMailingList.mdwn b/SupportMailingList.mdwn new file mode 100644 index 00000000..f147231a --- /dev/null +++ b/SupportMailingList.mdwn @@ -0,0 +1,66 @@ + + +## X.Org Mailing Lists + +So you have a question and you can't find the answer on the wiki or [[Google|http://www.google.com]]. + +Feel free to subscribe to the X.Org support mailing list. **Please** subscribe, don't just post your questions there. You will not receive all of the answers to your question unless you subscribe to the list. + + +### Please Hear Our Cry! + +**You can help us to help you!** + +**Before** you post your problem you should take a look at our **[[FAQ|FAQ]]** if you haven't done so already. Maybe somebody has had the same problem before and it is already answered. + +When you post a report please: + + * Please post in **English**. Even though people subscribed to the list may be able to speak some other languages English is the 'least common denominator' on this list. + * _Post your questions to the **X.Org** mailing list only. Do **NOT** crosspost!_ + * Also please post your Xorg log file. It can typically be found here: `/var/log/Xorg.0.log` + * A description of your problem would also be helpful, along with the steps you've taken in your attempts to solve it. **You have tried to fix it yourself haven't you?** At the very least you should **READ** your log file. There is a key which explains some of the symbols used in it at the top (of the log file.) + * Please **don't** use HTML in your email! You are much less likely to receive an answer. Some supporters filter out email containing HTML as SPAM. + * Please consider this outcry of an anonymous supporter: + +[[!format txt """ +May I ask all posters to refrain from using the subject lines: +(no subject) +Need help +Help +please help +Can someone help me +Problem +Big problem +X crash +Fatal server error +X server crash +crash +X windows problem +Fatal server error +Server crash +what is this +Error log + +and all other permutations on this theme. + +Some creative possibilities for subject lines are: +The error message you are receiving. +The manufacturer and name of your graphic card. +The Distro and version of X you are running. +Area where the problem is occurring. + i.e. if your mouse isn't working, "Mouse Troubles" + +Thanks for your support, + anonymous poster on a support mailing list. +"""]] + +## How to Subscribe + +Have you read our requests above? ;) + +OK, please go ahead and **[[subscribe|http://freedesktop.org/mailman/listinfo/xorg]]** to the support mailing list. + + +## Other lists + +* [[ati/radeon driver|http://lists.freedesktop.org/mailman/listinfo/xorg-driver-ati]] specific list
\ No newline at end of file diff --git a/SystemInfo.moin b/SystemInfo.moin new file mode 100644 index 00000000..78e1bf39 --- /dev/null +++ b/SystemInfo.moin @@ -0,0 +1,2 @@ +##language:en
+<<SystemInfo>>
diff --git a/TestGroup.mdwn b/TestGroup.mdwn new file mode 100644 index 00000000..90d09cee --- /dev/null +++ b/TestGroup.mdwn @@ -0,0 +1,69 @@ + + +# X.Org Foundation(XOF) Testing WorkGroup + + +## Purpose + +The Testing Group's purpose is to maintain and extend the test suites associated with the X Window System technology and to develop and maintain an infrastructure for regression testing releases. The following goals have been established for the Testing Group: + +* Support and Maintain the existing X Test Suite +* Extend the existing X Test Suite to cover additional interfaces which have become X.Org standards +* Support the XOF Release process, and the XOF Release Manager by providing test suites, scripts and tool that can be used for regression and verification testing of each new release +* Provide input on the testability of new features during the design and development process of those features +* define and maintain procedures for testing portions of the product not covered by the X Test Suite. + +## Organization + +The Test Group will communicate primarily via IRC and email. Occasional conference calls may be held as needed. IRC meetings shall default to being held weekly at a time that is suitable to the majority of the active participants of the group. + +* IRC on #xorg-test on [[FreeNode|http://freenode.net/]] with channel logging archive available via the web. +* email list [[xorg-test@lists.x.org|mailto:xorg-test@lists.x.org]] ([[http://lists.x.org/mailman/listinfo/xorg-test/|http://lists.x.org/mailman/listinfo/xorg-test/]]) +* CVS is at [[http://cvs.freedesktop.org/xtest/|http://cvs.freedesktop.org/xtest/]] +Participation is open to everyone. Membership in X.Org is not required, but is encouraged. + + +## Deliverables + +We need to take a look at the exisiting APIs to create a list of tests which are missing (results documented here). Examples include the RENDER extension, RandR, DAMAGE and COMPOSITE. + +Unless there is good reason, new tests shall be in the [[TET|http://tetworks.opengroup.org]] framework to facilitate integration into the existing test suite. An additional task to investigate is to provide additional documentation that helps people to understand the TET framework more easily. + +Other frameworks could also be investigated, but we should be cautious to not get bogged down in endless religious debate over testing frameworks. + + +## Policies + +* [[TestGroup/CodeManagement|TestGroup/CodeManagement]] +* [[TestGroup/HowTo|TestGroup/HowTo]] + +## Build the X Test Suite + +Building the X Test Suite requires a few steps, but none of them are terribly difficult. Instructions can be found at [[BuildingXtest|BuildingXtest]]. + +Prebuilt tests can be found [[http://xorg.freedesktop.org/tests/|http://xorg.freedesktop.org/tests/]] + + +## CurrentWork + +* [[TestGroup/EviExt|TestGroup/EviExt]] - 3 interfaces +* [[TestGroup/DpmsExt|TestGroup/DpmsExt]] - 9 interfaces +* Xau +* Xmu(u) +* Xdbe +* XShm +* XSync +* XShape +* XMITMisc +* XSecurity +* Xcomposite +* Xcursor +* Xdamage +* Xevie +* Xft +* Xi +* Xinerama +* Xpm +* Xrender +* Xss +* Xv
\ No newline at end of file diff --git a/TestGroup/CodeManagement.mdwn b/TestGroup/CodeManagement.mdwn new file mode 100644 index 00000000..42ec235d --- /dev/null +++ b/TestGroup/CodeManagement.mdwn @@ -0,0 +1,26 @@ + + +# Test Suite Code Management + +More formal rules should be used for managing the source code of formal tests. This document defined the rules that should be followed. + + +## Change Reviews + +Code changes should be sent to the [[mailing list|http://lists.freedesktop.org/mailman/listinfo/xorg-test]] for approval. 2 days should be allowed for comments, after which time, the change may be committed if there were not issues raised. Code changes that alter the method used to implement a test should be given heavier consideration and evaluated against the definition of the assertion and test cases involved. + + +## Functional Changes + +Functional changes to existing code should be considered carefully. Functional changes should not change the intended result of a test. + + +## New Features + +New features should be developed following the formal process of test suite development as summarized here + +* The specification of the feature being tested shall be identified. The specification should be largely complete, with some maturity, but need not be formally approved as a Standard yet. +* For each entity (ie function) in the Specification, a list of assertions shall be created and reviewed. +* For each assertion, a list of test cases shall be created and reviewed. +* For each test case, write code to implement the test. +New features shall be clearly marked as "in-progress" until they are complete, and approved by the Testing Group for use as a part of the formal test suite. diff --git a/TestGroup/DpmsExt.mdwn b/TestGroup/DpmsExt.mdwn new file mode 100644 index 00000000..3b7227de --- /dev/null +++ b/TestGroup/DpmsExt.mdwn @@ -0,0 +1,25 @@ + + +# Display Power Managment Signaling Test Suite + +This is an addition to the test suite for the DPMS extension. + + +## The Specification + +The specification for this extension can be found [[here|http://xorg.freedesktop.org/docs/Xext/DPMSLib.pdf]]. + + +## The Test Code + +Until we get our own CVS repository organized, this work is being done in the Linux Standard Base (LSB) project repository, [[http://cvs.gforge.freestandards.org/cgi-bin/cvsweb.cgi/tests/lsb-vsw4/xtest/tset/DPMS/?cvsroot=lsb|http://cvs.gforge.freestandards.org/cgi-bin/cvsweb.cgi/tests/lsb-vsw4/xtest/tset/DPMS/?cvsroot=lsb]] + + +## Owner + +Gordon [[McFadden|McFadden]] + + +## Current Status + +Assertions ready for Review diff --git a/TestGroup/EviExt.mdwn b/TestGroup/EviExt.mdwn new file mode 100644 index 00000000..c72adc92 --- /dev/null +++ b/TestGroup/EviExt.mdwn @@ -0,0 +1,27 @@ + + +# Extended Visual Information Test Suite + +This is an addition to the test suite for the EVI extension. This extension has only 3 APIs so it a good small example of how to add tests for an extension. + + +## The Specification + +The specification for this extension can be found [[here|http://xorg.freedesktop.org/docs/Xext/evi.pdf]]. + + +## The Test Code + +Until we get our own CVS repository organized, this work is being done in the Linux Standard Base (LSB) project repository, [[http://cvs.gforge.freestandards.org/cgi-bin/cvsweb.cgi/tests/lsb-vsw4/xtest/tset/EVI/?cvsroot=lsb#dirlist|http://cvs.gforge.freestandards.org/cgi-bin/cvsweb.cgi/tests/lsb-vsw4/xtest/tset/EVI/?cvsroot=lsb#dirlist]] + + +## Owner + +Gordon [[McFadden|McFadden]] [[gordon.mcfadde@intel.com|mailto:gordon.mcfadde@intel.com]] + + +## Current Status + +Assertions ready for Review + +Strategy sections have been added diff --git a/TestGroup/HowTo.mdwn b/TestGroup/HowTo.mdwn new file mode 100644 index 00000000..2d9250d5 --- /dev/null +++ b/TestGroup/HowTo.mdwn @@ -0,0 +1,11 @@ + +The existing X Test Suite was developed using a methodology that will be described here. + + +## Create Assertion List + + +## Develop Test Strategy + + +## Implement Test Cases diff --git a/TiagoVignatti.mdwn b/TiagoVignatti.mdwn new file mode 100644 index 00000000..d3be06ca --- /dev/null +++ b/TiagoVignatti.mdwn @@ -0,0 +1,13 @@ + + +## Tiago Vignatti + +[[http://web.inf.ufpr.br/vignatti|http://web.inf.ufpr.br/vignatti]] + +Email: vignatti AT c3sl DOT ufpr DOT br + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/Tinderbox.mdwn b/Tinderbox.mdwn new file mode 100644 index 00000000..bbbfed33 --- /dev/null +++ b/Tinderbox.mdwn @@ -0,0 +1,54 @@ +## Tinderbox status + +[[tinderbox|http://tinderbox.x.org/]] + +## Adding a new machine + +The steps for setting up a new machine are: + +* Read [[http://tinderbox.x.org/participate|http://tinderbox.x.org/participate]], get a username/pass +* Set up jhbuild; see [[http://wiki.x.org/wiki/JhBuildInstructions|http://wiki.x.org/wiki/JhBuildInstructions]] +* "jhbuild build"; check that the build completes and you have the appropriate dependencies +* Once you're ready to add the machine to the tinderbox front page, set up a crontab entry such as: + +`0 */2 * * * bin/jhbuild autobuild -a -c --report-url="http://USER:PASS@tinderbox.x.org/builds/rpc"` + +(instructions from [[this email|http://lists.freedesktop.org/archives/xorg/2008-December/041211.html]]) + +## Using ccache and an autoconf cache file + +Since many of these clean/configure/build runs will be identical, it's a big win to use [[ccache|http://ccache.samba.org/]] and an [[autoconf cache file|http://www.gnu.org/software/hello/manual/autoconf/Cache-Files.html]], e.g. add to jhbuildrc + + os.environ['CC'] = 'ccache gcc' + os.environ['CXX'] = 'ccache g++' + autogenargs='--cache-file=os.path.join(os.environ['HOME'], 'configure-cache') + +## Changing the moduleset + +Locally modifying the jhbuild moduleset to add or remove modules isn't a good idea as this means that you don't automatically pick up changes to it. + +To avoid building modules (e.g. which aren't appropriate to your target), you can use the skip configuration variable in the jhbuildrc file, e.g. + + skip = [ 'xdriinfo', 'libdrm', 'libpciaccess' ] + +To add additional modules, you can use the technique of creating of local moduleset which includes the standard moduleset and your additions, e.g. + + moduleset = os.path.join(os.environ['HOME'], 'myxorg.modules') + +where the contents of myxorg.modules is something like + + <?xml version="1.0" standalone="no"?> <!--*- mode: nxml -*--> + <!DOCTYPE moduleset SYSTEM "moduleset.dtd"> + <?xml-stylesheet type="text/xsl" href="moduleset.xsl"?> + + <moduleset> + <include href="http://cgit.freedesktop.org/xorg/util/modular/plain/xorg.modules" /> + + <metamodule id="xquartz"> + <dependencies> + <dep package="libAppleWM"/> + <dep package="xorg"/> + </dependencies> + </metamodule> + + </moduleset> diff --git a/TitleIndex.moin b/TitleIndex.moin new file mode 100644 index 00000000..d32ace36 --- /dev/null +++ b/TitleIndex.moin @@ -0,0 +1,10 @@ +##language:en
+This is an index of all pages in the this Wiki.
+
+See also:
+ * WordIndex -- a permuted index of all words occuring in titles
+ * SiteNavigation -- other indexing schemes
+
+----
+
+<<TitleIndex>>
diff --git a/ToDo.mdwn b/ToDo.mdwn new file mode 100644 index 00000000..50c40bae --- /dev/null +++ b/ToDo.mdwn @@ -0,0 +1,77 @@ + +[[!toc ]] + +Xorg always needs more work and more contributors. Several tasks anyone can help with are listed below. Don't feel limited to these suggestions, and feel free to add your own suggestions to the list. + + +## Server + + +### Janitorial things + +These are largely mechanical things, suitable for someone who's just getting started and needs a way to get familiar with the server. + +* The diagnostic messages printed in the log file are confusing. They range from uninformative, to misleading, to flat out wrong. The message severity levels are frequently wrong as well. [[Bug 3116|https://bugs.freedesktop.org/show_bug.cgi?id=3116]] +* Driver option names are inconsistent. +* Many drivers are underdocumented. +* The X codebase is quite crufty and could use a lot of cleaning up. +* Still far too much K&R C that should be ANSI. +* Triage [[open bugs in bugzilla|https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&product=xorg]]. +* Review and test [[patches in bugzilla|https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&product=xorg&keywords=patch]] and from [[the xorg mailing list|http://lists.freedesktop.org/archives/xorg/]]. +* Remove CVS tags inside of files. +See more possible work in the [[Janitor|Development/Janitor]] page. + + +### Minor development + +These are relatively self-contained problems, suitable for someone who knows how to program but doesn't necessarily understand the whole server. + +* X server backtraces could potentially be more useful. glibc's backtrace() isn't great. Maybe fork() gdb? Maybe link against libelf and walk the the symbols ourselves? +* XAA is lacking. See [[ExaStatus|ExaStatus]] for status on the replacement. +* Input properties are a lovely hammer, but they need some standardization for things like pointer acceleration. +* X server protocol dispatch is still handwritten. We should generate it from xcb-proto instead. +* Extend shadow to be something you can have per-drawable instead of per-screen. +* Loader: Remove the abstraction from the loader (hw/xfree86/loader) so it's just a simple libdl wrapper with the same API, and punt it up to the DIX, so all DDXes can use it. +* Remove statics: Make [[MAXSCREENS|https://bugs.freedesktop.org/show_bug.cgi?id=3876]] and [[MAXFORMATS|https://bugs.freedesktop.org/show_bug.cgi?id=3876]] run-time configurable, ditto MAXCLIENTS. ajax started a patch for MAXFORMATS, bother him about it. +* Code removal: Remove anything that's unused and/or bad. +* Port the int10 code to libx86. mjg59 and vignatti had started on this (from opposite ends). +* Build the "X server awesome scheduler": + * What we want is simple: a preemptive scheduler with priorities (real-time scheduler) to deal with multiple clients and with a special care for input events. One interesting thing to considerer is that the issue of long-lived requests is mostly a thing of the past. [[PolyLines|PolyLines]] are not that common, fonts are mostly client side, and OpenGL is usually client-side as well due to DRI. Moreover, clients can block each other. Just try to execute a `x11perf -getimagexy500` plus play a video to see. x11perf eats all the X process. Isn't wiser to give a tiny quantum here for each client? The funny thing is that -dumbSched gives a better result than with the _smart_ scheduler :) So simultaneous client requests aren't dealt by smart scheduler at all. This is quite interesting for those who is trying to start in the X world because it doesn't touch much of the graphics oddities :) + +### Major development + +These are big cross-cutting things. Much of this is just ajax's wishlist. + +* Rewrite the bottom of the rendering layer. The old Get/Set/Fill``Spans API was appropriate when your memory aperture was all of 16 bytes, but this is really not the case anymore. Should move to Get``Image/Put``Image/Poly``Fill``Rect/Copy``Area. +* Redo Pictures. Right now they're like a GC and a Drawable in one, which makes things really awkward. +* More generally, detach rendering from the ScreenRec. Wrapping is a useful technique, but most useful if the thing with the wrap chain is something you can create temporaries of, which ScreenRec is not. +* Extend Xdmx to act as a drop-in replacement for Xnest, and delete the latter. +* Extend Xdmx to use the XI2 model of input devices. +* Port to any new platforms we need support for. +* Make one set of Xinerama protocol routines for use by Xinerama and Xinerama-emulating code such as randr-1.2 and driver MergedFB code. +* Make one set of logical screen to graphics device splitting code out of the Xinerama & Xdmx code bases. +* Enable more input devices, in particular speech recognition, by allowing events to specify keysyms. It can be very difficult to convert dictation to keystrokes; it is much easier to transmit unicode directly to the application. + +### Driver projects + +* evdev: the evdev driver currently ignores joysticks altogether. It could be extended to work against such devices and auto-setup itself accordingly. +* evdev: evdev touchscreen support is still subpar to evtouch. One missing feature is a right-click emulation on long presses. This would be a quite trivial project. +* synaptics: coasting is a on/off state toggle. should be momentum-based instead + +## Utilities + +* xrandr is still a bit touchy. The failure modes are not obvious, CRTCs are magical, etc. +* Input device utilities (xmodmap, setxkbmap, xkbutils etc.) need to deal with multiple devices (MPX/Xi2). +* xev needs to learn how to display events added in recent extensions, such as Xi2, RandR +* Should xprop work with input device (Xi2) and output device (randr) properties too? +* xdpyinfo could probably use some updates to the -ext support for newer extensions. +* Port utilities (one at a time) from libX11 to [[xcb|http://xcb.freedesktop.org/]] + +## Testing + +* For general information on helping with Xorg testing, see the [[TestGroup|TestGroup]] page. +* Specific information about release testing can be found on the [[XorgTesting|XorgTesting]] page. + +## Related Projects + +* xcb: See [[XCBToDo|http://xcb.freedesktop.org/XCBToDo/]]
\ No newline at end of file diff --git a/UserDocumentation.mdwn b/UserDocumentation.mdwn new file mode 100644 index 00000000..a1eb5fc5 --- /dev/null +++ b/UserDocumentation.mdwn @@ -0,0 +1,17 @@ + +The user documentation for the different versions can be found here: + +* [[6.9.0|http://ftp.x.org/pub/X11R6.9.0/doc/html]] +* [[7.0|http://ftp.x.org/pub/X11R7.0/doc/html]] +* [[7.5|http://www.x.org/releases/X11R7.5/doc/]] +* [[7.6|http://www.x.org/releases/X11R7.6/doc/]] +* [[7.7|http://www.x.org/releases/X11R7.7/doc/]] +A brief getting started guide and tutorial for end-users and non-programmers is [[here|UserDocumentation/GettingStarted]]. + +O'Reilly & Associates have also made freely available online some of their classic X Window System manuals. These are a bit older, dating from the [[X11R3|X11R3]], R4, or R5 eras, and applying to the commercial Unix versions of the time, but may still have some useful information in: + +* [[X Series Volume 3: X Window System User's Guide, 3rd Edition (1990, covers X11R3 & R4)|http://www.archive.org/details/xwindowsystem03quermiss]] +* [[X Series Volume 3: X Window System User's Guide, OSF/Motif Edition (1990, covers X11R4 & Motif 1.1)|http://www.archive.org/details/xwindowsytemosf03querarch]] +* [[X Series Volume 3: X Window System User's Guide, OpenLook Edition (never published)|http://www.oreilly.com/openbook/openlook/]] +* [[X Series Volume 8: X Window System Administrator's Guide, 1st edition (1993, covers X11R5)|http://www.archive.org/details/xwindowsystemadm08muimiss]] +O'Reilly has published a much more recent and up-to-date user guide [[X Power Tools|http://books.google.com/books?id=V1ZBeNJIx7UC]], but only a small preview of it is available for free online at this point. diff --git a/UserDocumentation/GettingStarted.mdwn b/UserDocumentation/GettingStarted.mdwn new file mode 100644 index 00000000..cf0a3c66 --- /dev/null +++ b/UserDocumentation/GettingStarted.mdwn @@ -0,0 +1,217 @@ + +This wiki page will be used to briefly document getting started with X.org tools and technologies. This wiki page is a quick tutorial for end-users and non-programmers. (Please add wiki content to quickly introduce and get up to speed with tools and technologies, but keep it brief -- link to manual page or other wiki pages for full details. See copyright license note at bottom.) + + +# Tools and applications + +The following are some of the commonly installed applications and tools included with X.org. This is not a complete list. This just briefly introduces, shares examples of common usage, and links to further details. + +TODO: maybe better organize this by just most common applications first or just remove rarely used applications. + + +### appres + +List "application resources". For example, "appres XTerm" will list the xterm resources. These X resources are a type of configuration syntax. Default X resource configuration files can be seen under /etc/X11/app-defaults/, /usr/local/lib/X11/app-defaults/, or other location. + + +### beforelight + +Simple screensaver using MIT-SCREEN-SAVER. TODO link to details about MIT-SCREEN-SAVER. TODO: And show example usage. + + +### bitmap + + +### atobm + + +### bmtoa + + +### editres + + +### iceauth + + +### ico + + +### listres + + +### luit + + +### setxkbmap + + +### twm + +"twm (Tom's Window Manager or Tab Window Manager) is the standard window manager for the X Window System, version [[X11R4|X11R4]] onwards. twm was created by Tom [[LaStrange|LaStrange]]. It is a re-parenting window manager that provides title bars, shaped windows and icon management, and is extensively configurable. + +twm was a breakthrough achievement in its time, but has been largely superseded by other window managers and is no longer maintained. " [[http//en.wikipedia.org/wiki/Tom's_Window_Manager|http//en.wikipedia.org/wiki/Tom's_Window_Manager]] +### x11perf + + +### x11perfcomp + + +### xauth + + +### xbacklight + + +### xbiff + + +### xcalc + +xcalc is a scientific calculator desktop accessory that can emulate a TI-30 or an HP-10C. (from the xcalc man page) +### xclock + +The xclock program displays the time in analog or digital form. The time is continuously updated at a frequency which may be specified by the user. (from the xclock man page) +### xconsole + + +### xdm + + +### xdmshell + + +### xdpyinfo + +Xdpyinfo is a utility for displaying information about an X server. It is used to examine the capabilities of a server, the predefined values for various parameters used in communicating between clients and the server, and the different types of screens and visuals that are available. [...] (from the xdpyinfo man page) +### xev + +This opens a small "Event Tester" window. This is normally used for studying X events, such as pointer motion, entering windows, etc. + +For a normal user it may be useful to identify special keys. For example, running xev and pressing the "right Windows menu" key on a system may show "keycode 117 (keysym 0xff67, Menu)" (and other details). + + +### xeyes + +"xeyes is a graphical computer program showing two googly eyes which follow the cursor movements on the screen as if they were watching it." [[http://en.wikipedia.org/wiki/Xeyes|http://en.wikipedia.org/wiki/Xeyes]] + + +### xfontsel + + +### xgamma + + +### xhost + + +### xinit + + +### startx + + +### xkill + + +### xload + + +### xlogo + + +### xlsclients + +Xlsclients is a utility for listing information about the client applications running on a display. It may be used to generate scripts representing a snapshot of the user's current session. (from the xlsclients man page) +### xmag + + +### xman + + +### xmessage + + +### xmodmap + + +### xmore + + +### xplsprinters + + +### xprehashprinterlist + + +### xprop + + +### xrandr + + +### xrdb + + +### xrefresh + + +### xset + + +### xsetmode + + +### xsetpointer + + +### xsetroot + + +### xsm + + +### koi8rxterm + + +### resize + + +### uxterm + + +### xterm + +"xterm is the standard terminal emulator for the X Window System. A user can have many different invocations of xterm running at once on the same display, each of which provides independent input/output for the process running in it (normally the process is a Unix shell)." [[http://en.wikipedia.org/wiki/Xterm|http://en.wikipedia.org/wiki/Xterm]] + + +### xvinfo + + +### xwd + +Useful and easy way to take screenshots. Saves in the XWD X Window Dump image data format. The image can be displayed with xwud or The GIMP, [[ImageMagick|ImageMagick]] display or other popular image viewers. + +Here's an example of taking screenshot of entire display: + + * xwd -root -out screenshot.xwd +Here's an example of taking a screenshot of just a selected window after three seconds: + + * sleep 3 && xwd -out window.xwd +(It will show a special mouse pointer for you to click in the window to capture.) + + +### xwininfo + + +### xwud + +Can be used to display images in the XWD X Window Dump image format (see xwd above). Note that common utilities like The GIMP and [[ImageMagick|ImageMagick]] display(1) can also work with these images. + + + +--- + + + +Copyright / License. I have no idea what the copyright and licensing is for this entire wiki website. For this webpage, let's just consider this content is under the standard X.org license. (I'd link to it but don't see official statement on the license to be used for new code.) diff --git a/UserPreferences.moin b/UserPreferences.moin new file mode 100644 index 00000000..62314e3d --- /dev/null +++ b/UserPreferences.moin @@ -0,0 +1,22 @@ +#acl AdminGroup:read,write,revert,admin All:read
+##language:en
+<<UserPreferences>>
+
+= First time =
+Please fill out '''<<GetText(Name)>>''', '''<<GetText(Password)>>''', '''<<GetText(Password repeat)>>''' and '''<<GetText(Email)>>'''.
+
+(!) It is best to choose a WikiName (like Firstname``Lastname) as username to get your changes and signatures link back to your Wiki``Homepage. Your email is needed for you to be able to get notifications on page changes and to recover lost login data.
+
+If you click on '''<<GetText(Create Profile)>>''', a user profile will be created for you and you will be logged in immediately.
+
+= Logging in =
+If want to re-login, just use '''<<GetText(Name)>>''' and '''<<GetText(Password)>>''' and click on '''<<GetText(Login)>>'''. If you forgot your password, provide your email address and click on '''<<GetText(Mail me my account data)>>'''.
+
+= Changing settings =
+'''<<GetText(Save)>>''' updates your profile (stored on the wiki server).
+
+= Logging out =
+'''<<GetText(Logout)>>''' clears the cookie created at login.
+
+= The Cookie =
+/!\ The "ID", shown in the response page, gets saved as a cookie in your browser for the system to temporarily recognize you. It will expire next midnight - except if you choose '''<<GetText(Remember login information forever)>>''' (after being logged in), then the cookie won't expire.
diff --git a/VgaArbiter.mdwn b/VgaArbiter.mdwn new file mode 100644 index 00000000..2223f7a2 --- /dev/null +++ b/VgaArbiter.mdwn @@ -0,0 +1,117 @@ + + +# VGA arbiter + + +## Background + +When multiple video cards are uncoordinatedly using the legacy VGA interface, one card might decode messages that were not sent to it. To solve this problem, it is needed an entity that controls all the accesses made using the legacy VGA interface. In Xorg this happens when multiple instances are running. It is important to note that some GPUs can skip completely if they are able to disable their VGA decoding resources (unfortunately this seems not so usual). + +A good explanation of this problem is presented here: [[http://people.freedesktop.org/~dodji/arbitration-log.txt|http://people.freedesktop.org/~dodji/arbitration-log.txt]] + + +## Required Functionality + +Devices that decode legacy VGA IO and/or MEM need to be identified. In addition, their IO/MEM enable/disable bits need to be toggled (along with the VGA forwarding enables on any bridges on the path to the devices). This is needed to prevent multiple devices from decoding legacy access. Drivers need to disable legacy decoding completely on their hardware, which most modern cards can do. The driver must be able to inform the arbiter of that fact to take out the card from the picture. This must be done carefully since bad things will happen if the card generates an interrupt when the arbiter has disabled MEM decoding on the card. The arbiter needs to either forbid cards to use interrupts if they are set to decode legacy space (and thus can be disabled at any time) or have a driver callback for disabling IRQ emission on a given card when it's being disabled by the arbiter. IO and MEM can't be treated separately since there is only one VGA forward bit on PCI-to-PCI bridges. + + +## Project Status + +The implementation provided is just a proof-of-concept, and it shows that the VGA Arbiter **works**. Now we need to decide the definitive interfaces and start writing the definitive code. There is an interesting [[blog post|http://vignatti.wordpress.com/2008/02/21/benchmarking-it-all/]] regarding the performance of this proof-of-concept. + +The current implementation is split into 3 pieces. + + +### Kernel Module + +The VGA Arbiter, a Linux Kernel module, provides a device node that has to be used by applications that decode the legacy VGA interface. This can be easily ported to others platforms. + +Currently, it is just a Kernel module because modules are way much easier to compile and test than built-in Kernel code. Ideally, this module will be integrated into the Kernel so that Kernel code will also be able to use the module without using its device node interface. + +Also, the device node interface could also be changed to something else, to improve performance. + + +### User Space Library + +There is a little user space library that communicates with the arbiter using the device node interface. It was made so that the code inside the applications would be much easier to write. Also, when something on the device node interface changes, we wouldn't need to change all the applications, only the library (considering that its interface doesn't change). + + +### X Server Code + +There is a modified version of the X server that uses the VGA Arbiter instead of RAC when it can. The current implementation works exactly like the RAC implementation: it's a wrapper on the video drivers. Ideally, only the code that accesses the VGA Arbiter should be moved to inside the video drivers, because this would allow a much better performance. So, the video driver wrapper could be just removed. + + +## Current Implementation + +[[http://people.freedesktop.org/~vignatti/VGA.Notes|http://people.freedesktop.org/~vignatti/VGA.Notes]] + + +## Source code + +The current repository address is just **temporary**, so when it stops working, be sure to visit this page again to get the updated link. + +* Kernel module: git-clone [[http://git.c3sl.ufpr.br/pub/scm/multiseat/vga-module.git|http://git.c3sl.ufpr.br/pub/scm/multiseat/vga-module.git]] +* User space library: git-clone [[http://git.c3sl.ufpr.br/pub/scm/multiseat/libvgaaccess.git|http://git.c3sl.ufpr.br/pub/scm/multiseat/libvgaaccess.git]] +* X implementation: git-clone [[http://git.c3sl.ufpr.br/pub/scm/multiseat/xserver.git|http://git.c3sl.ufpr.br/pub/scm/multiseat/xserver.git]] (Note that the code is under server-1.4-branch branch) +You can also use [[gitweb|http://git.c3sl.ufpr.br/gitweb]] to navigate through the code. + + +## Building and installing + +Beyond these repositories above, to bring up an Xorg server with the VGA arbiter, we'll need to clone the input devices and the video driver repository from fd.o. After cloned all these repositories, the first step is building the kernel module. We'll need this environment variable set: +[[!format txt """ + export PKG_CONFIG_PATH=/opt/master/lib/pkgconfig +"""]] +then, + + +[[!format txt """ + cd vga-module + make +"""]] +After we need to build the vgaaccess library: +[[!format txt """ + cd libvgaaccess + ./autogen.sh --prefix=/opt/master + make + sudo make install +"""]] +Now we can build the X server: +[[!format txt """ + cd xserver + git-checkout -b server-1.4-branch origin/server-1.4-branch # to checkout the server-1.4-branch where the arbiter implementation resides + ./autogen.sh --prefix=/opt/master -disable-xnest -disable-kdrive -disable-xprint -disable-xvfb + make + sudo make install +"""]] +So now it's time to run it all. Lets do it using two servers: +[[!format txt """ + cd vga-module + insmod vgaarb.ko + cd .. + cd xserver + ./hw/xfree86/Xorg -ac -fp /usr/share/fonts/X11/misc -noreset -sharevts -VGAarbiter vt7 :1 & + ./hw/xfree86/Xorg -ac -fp /usr/share/fonts/X11/misc -noreset -sharevts -VGAarbiter vt7 :2 & +"""]] + +## TODO + +Kernel Module: + +* make it a built-in Kernel Code. +* decide if the device node interface will be the definitive interface. +* make other parts Kernel code that use the VGA Interface use the module functions +* need to be DRI (interruptions) aware. +X server code: + +* call the arbiter functions inside the video drivers, not using the current video driver wrapper (like in RAC). (this sentence means: start the X server code all over again, but now doing it the right way). + +## FAQ + +Q: Why? + +A: To start several instances of Xorg at same time using different graphical devices (e.g. to deploy a [[multiseat|http://wiki.c3sl.ufpr.br/multiseat/]]) + +Q: Who is working here? + +A: [[TiagoVignatti|TiagoVignatti]], [[PauloZanoni|PauloZanoni]] and Benjamin Herrenschmidt diff --git a/VideoDriverFAQ.mdwn b/VideoDriverFAQ.mdwn new file mode 100644 index 00000000..04027e1a --- /dev/null +++ b/VideoDriverFAQ.mdwn @@ -0,0 +1,43 @@ + + +# Video driver FAQ + +[[!toc ]] + +Information about the individual video drivers can be found on the [[VideoDrivers|VideoDrivers]] page. This page is there to provide information that doesn't quite fit into a single driver. + + +## I have an S3 graphics card, which driver should I use ? + +There are three drivers for S3 graphics chipsets: + + * The _S3_ driver, which supports some of the _Trio64_ and older chipsets (use: `Driver "s3"`, for details check [[s3|s3]]), + * the _S3 Virge_ driver which supports the _S3 Virge_ and _S3 Trio3D_ chipsets (use: `Driver "s3virge"`, for details check [[s3virge|s3virge]]), + * the _Savage_ driver which supports most of the _S3 Savage_ chipsets (use: `Driver "savage"`, for details check [[savage|savage]]). +Please *NOTE*. The S3 driver in XFree86 3.x supports a lot more of the old S3 chips. Only support for a few of them has been ported to X.Org R6.7. Currently noone is working on porting further chipsets. We are still looking for someone to help porting more S3 chips. + + +## I have a CirrusLogic chipset, which driver should I use ? + +There is one 'wrapper' module which will automatically detect the type of hardware and load the correct sub module. We support both flavors of Cirrus Logic chipsets, the _ 'Laguna' _ and the _ 'Alpine' _ chipsets. (use: `Driver "cirrus"`, for details check [[cirrus|cirrus]]) + +Please *NOTE*: X.Org 6.7 doesn't support some of the old ISA Cirrus chips XFree86 3.x used to support. + + +## I have an ATI graphics card, which driver should I use ? + +The [[GATOS|http://sourceforge.net/projects/gatos]] project create enhanced (fast) drivers for the ATI chipsets, which also include TV in/out support for most ATI cards that have this feature. While the main target of these drivers is still XFree86, they are still compatible with the X.org server. The GATOS project does not yet redistribute X.org compatible binaries, but compiling against the X.org source tree will work. The GATOS TV-in code has been incorporated into XOrg, but its TV-out code is still only available in the GATOS drivers. + +For r200 cards on down, the open source ati drivers will provide excellent 3d acceleration. for r300 and up, the only fully functioning option is ATI's proprietary fglrx drivers in [[X11R6|X11R6]].8 and below. In [[X11R6|X11R6]].9 and [[X11R7|X11R7]].0, DRI will work on r300 and up. + + +## I have an XGI card, which driver should I use? + +The XGI XP5 laptop chip and Volari V3 card are based on a Trident core. However, they are not yet supported in the [[trident|trident]] driver, so you will have to use [[vesa|vesa]] for now. + +All other XGI chips (Volari V3XT, V5, and V8) are supported by the [[sis|sis]] driver in Xorg 6.9 and later. + + +## I have a Matrox card, which driver should I use? + +X.Org ships with the [[mga|mga]] driver which supports the Matrox G-series cards (G550 and below). Alternatively, Matrox offers X.org-compatible Linux drivers on their [[driver download page|http://www.matrox.com/mga/support/drivers/latest/home.cfm]], for both the G-series and P-series cards. diff --git a/VideoDrivers.mdwn b/VideoDrivers.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/VideoDrivers.mdwn diff --git a/WantedPages.moin b/WantedPages.moin new file mode 100644 index 00000000..24ae2d21 --- /dev/null +++ b/WantedPages.moin @@ -0,0 +1,3 @@ +##language:en
+A list of non-existing pages including a list of the pages where they are referred to:
+<<WantedPages>>
diff --git a/WikiHomePage.mdwn b/WikiHomePage.mdwn new file mode 100644 index 00000000..adec7b77 --- /dev/null +++ b/WikiHomePage.mdwn @@ -0,0 +1,10 @@ + +A WikiHomePage is your personal page on a [[WikiWikiWeb|WikiWikiWeb]], where you could put information how to contact you, your interests and skills, etc. It is regarded as to be owned by the person that created it, so be careful when editing it. + +When you create one, put the the word [[CategoryHomepage|CategoryHomepage]] on it, like can be seen on this page. + + + +--- + + [[CategoryHomepage|CategoryHomepage]] diff --git a/WikiName.mdwn b/WikiName.mdwn new file mode 100644 index 00000000..0b6481e3 --- /dev/null +++ b/WikiName.mdwn @@ -0,0 +1,2 @@ + +A WikiName is a word that uses capitalized words. WikiName****s automagically become hyperlinks to the WikiName's page. See also [[HelpForBeginners|HelpForBeginners]], "Arbitrary Page Names". diff --git a/WikiSandBox.moin b/WikiSandBox.moin new file mode 100644 index 00000000..04a2c3bb --- /dev/null +++ b/WikiSandBox.moin @@ -0,0 +1,93 @@ +##language:en
+Please feel free to experiment here, after the four dashes below... and please do '''NOT''' create new pages without any meaningful content just to try it out!
+
+'''Tip:''' Shift-click "HelpOnEditing" to open a second window with the help pages.
+----
+
+== Formatting ==
+
+''italic'' '''bold''' {{{typewriter}}}
+
+`backtick typewriter` (configurable)
+
+{{{
+preformatted
+}}}
+
+== Linking ==
+
+Dear Web Master,
+
+Cybernation Infotech, Inc. is a Philadelphia based company providing Medical Transcription Services. Our website has a good page rank, healthy traffic volumes and a good Alexa Rank which is constantly improving. We are keen to exchange links with your website because we believe it will boost Google Search Rank Position & also improve traffic volumes for both ours as well as your website thereby improving the respective Alexa Rank as well. Now ours medical transcription service website 1st in Top Ten Google Search Engine. U.S.A.
+
+Please add ours Link First....Your link will be here…at Google PR. Check the back links and tell me..
+
+www.cybernationinfotech.com PR.4
+www.dic2doc.com PR. 2
+www.xlntseo.com PR. 2 And it's back link...
+
+http://www.cybernationinfotech.com/Links/doctors/linkpartnersdoctors001.html PR. 1
+http://www.cybernationinfotech.com/Links/doctors/linkpartnersdoctors002.html PR. 1
+http://www.cybernationinfotech.com/Links/directory/linkpartnersdirectory001.html PR. 1
+http://www.cybernationinfotech.com/Links/health/linkpartnershealth004.html PR. 1
+http://www.cybernationinfotech.com/Links/insurance/linkpartnersinsurance001.html PR. 1
+http://www.cybernationinfotech.com/Links/hospital/linkpartnershospital002.html PR. 1
+http://www.cybernationinfotech.com/Links/hospital/linkpartnershospital003.html PR. 1
+http://www.cybernationinfotech.com/Links/medical/linkpartnersmedical001.html PR. 1
+http://www.cybernationinfotech.com/Links/medical/linkpartnersmedical003.html PR. 1
+http://www.cybernationinfotech.com/Links/outsourcing/linkpartnersoutsourcing001.html PR. 1
+http://www.dic2doc.com/links/computer/computer.html PR. 1
+http://www.dic2doc.com/links/homes/homes.html PR. 1
+http://www.dic2doc.com/links/others/others.html PR. 1
+http://www.dic2doc.com/links/shopping/shopping.html PR. 1
+http://www.xlntseo.com/Directory/seo.html
+
+Ours desired pages: Minimum Google Page Rank. web pages.
+
+Link code:
+
+1.Medical transcription Website:
+<a href="http://www.cybernationinfotech.com" target="_blank" class="style16"><strong>Medical Transcription Service </strong></a></span><span class="style20">Based in Philadelphia, and providing HIPAA compliant medical transcription services to hospital and clinic based physicians. Reports emailed next day morning, Sign up for a </span><span class="style22"><a href="http://www.cybernationinfotech.com/cybernation_signup.htm">15-Days Free Trial.</a></span><span class="style20"> Cybernation Infotech Inc.
+
+2.SEO Website:
+<a href="http://www.xlntseo.com" target="_blank" class="style13"><strong>Search Engine Optimization Service </strong></a><br> www.xlntseo.com is a Search Engine Optimization Service Provider who can improve the quality and quantity of traffic to your website. Once you provide us the targeted keyword(s) for your website, we will get your website to appear amongst the top search results on major search engines for those targeted keywords.</a>
+
+3.Dictation Recording Website:
+<a href="http://www.dic2doc.com" target="_blank" class="style13"><strong>dictation recording Service </strong></a><br> We provide the most popular, easy to use and technically advanced dictation and transcription service platform. Our infrastructure serves as the backbone of the entire transcription service industry. We invest in and maintain everything on your behalf, so you can simply focus on what you do best i.e. transcribe reports. So, whether you are a one person show, a mom and pop enterprise or a transcription service company, sign up for a free trial.</a>
+
+Please send exact back link path where you have added ours link….and send your link description
+
+Thank you,
+
+Cybernation Infotech Inc. – (Medical Transcription Service – U.S.A.)
+S.E.O. Manager: Email: links@cybernationinfotech.com
+For more information: Website: http://www.cybernationinfotech.com
+
+HelpOnEditing MoinMoin:InterWiki
+
+http://purl.net/wiki/moin/ [[http://www.python.org/|Python]]
+
+someone@the.inter.net
+
+
+=== Image Link ===
+{{http://c2.com/sig/wiki.gif}}
+
+== Lists ==
+
+=== Bullet ===
+ * first
+ 1. nested and numbered
+ 1. numbered lists are renumbered
+ * second
+
+ blockquote
+ deeper
+
+=== Glossary ===
+ Term:: Definition
+
+=== Drawing ===
+{{drawing:mytest}}
+
+Here is a '''new''' test
diff --git a/WikiSandBox/.._.._.._plugin_action_moinexec.py b/WikiSandBox/.._.._.._plugin_action_moinexec.py Binary files differnew file mode 100644 index 00000000..b8befca1 --- /dev/null +++ b/WikiSandBox/.._.._.._plugin_action_moinexec.py diff --git a/WikiSandBox/mytest.png b/WikiSandBox/mytest.png Binary files differnew file mode 100644 index 00000000..5e7c09c7 --- /dev/null +++ b/WikiSandBox/mytest.png diff --git a/WikiWikiWeb.mdwn b/WikiWikiWeb.mdwn new file mode 100644 index 00000000..15f5ecd3 --- /dev/null +++ b/WikiWikiWeb.mdwn @@ -0,0 +1,11 @@ + +The [[!c2 FrontPage desc="first ever wiki site"]] was founded in 1994 as an automated supplement to the [[!c2 PortlandPatternRepository desc="PortlandPatternRepository"]]. The site was immediately popular within the pattern community, largely due to the newness of the internet and a good slate of [[!c2 InvitedAuthors desc="InvitedAuthors"]]. The site was, and remains, dedicated to [[!c2 PeopleProjectsAndPatterns desc="PeopleProjectsAndPatterns"]]. + +[[!c2 WardCunningham desc="WardCunningham"]] created the site and the WikiWikiWeb machinery that operates it. He chose wiki-wiki as an alliterative substitute for quick and thereby avoided naming this stuff quick-web. An early page, [[!c2 WikiWikiHyperCard desc="WikiWikiHyperCard"]], traces wiki ideas back to a [[!c2 HyperCard desc="HyperCard"]] stack he wrote in the late 80's. + +See also one of these links: + +* [[http://www.c2.com/cgi/wiki|http://www.c2.com/cgi/wiki]] or [[!c2 FrontPage desc="FrontPage"]] +* get some answers on the [[!c2 WikiWikiWebFaq desc="WikiWikiWebFaq"]] +* get to know more about the [[!c2 WikiHistory desc="WikiHistory"]] +* [[Ward Cunningham Radio Interview|http://news.mpr.org/programs/futuretense/daily_rafiles/20011220.ram]]
\ No newline at end of file diff --git a/WordIndex.moin b/WordIndex.moin new file mode 100644 index 00000000..3a47fcec --- /dev/null +++ b/WordIndex.moin @@ -0,0 +1,9 @@ +##language:en
+This is an index of all words occuring in page titles.
+
+See also:
+ * TitleIndex -- a shorter index
+ * SiteNavigation -- other indexing schemes
+
+----
+<<WordIndex>>
diff --git a/X.Org-GSoC2008-Application.mdwn b/X.Org-GSoC2008-Application.mdwn new file mode 100644 index 00000000..dc8531bb --- /dev/null +++ b/X.Org-GSoC2008-Application.mdwn @@ -0,0 +1,41 @@ + + +## Project Proposal Guidelines + +We expect more project proposals than Google will be able to fund. Here is our list of suggestions about how to write a Summer of Code proposal that will stand a chance of rising to the top of the heap. + + +## Requirements + + * Applicants meet Google's requirements for participation in Summer of Code. + * Applicants are in regular and close contact with their X.Org mentors. + * Applicants know their target programming language. + +## Proposal Outline + + * Name and Contact Information + * Title + * Synopsis. A short summary. + * Benefits to the Community. What novel technologies or approaches will be demonstrated? + * Deliverables. Give a brief, clear work breakdown structure with milestones and deadlines. Make sure to label deliverables as optional or required. You may want plan to start by producing some kind of whitepaper, or planning the project in traditional software engineering style. Work should include + * investigation + * programming + * documentation + * dissemination + * Description. A list of project details (rough architecture, etc). + * Related Work. A list of other people's work. Could be as simple as a URL with one sentence description. Be sure to explain how the proposed work is different from similar related work. + * Biographical Information. + * Summarize your education, work, and open source experience. + * List your skills and give evidence of your qualifications. + * List published papers, successful open source projects, etc. + * Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments. + +## General Notes + +Your proposal should be around 1500-4000 words in plain text. There is a limit on the number of submitted proposals, if you have several ideas, please submit several proposals. Do include URLs pointing to information that would help convince us of your chances of success: preliminary project plans or progress, other projects you've been involved with that were successful, code samples, etc. + +It is better if your project is under-scoped and sure to complete; as opposed to a largeish project which may not get done. + +One of the features of Google/X.Org Summer of Code is that it is a organization to help with projects involving integrating free software and hardware from different sources. + +See [[SummerOfCodeIdeas|SummerOfCodeIdeas]] for project ideas. diff --git a/X11R68PostPartumNotes.mdwn b/X11R68PostPartumNotes.mdwn new file mode 100644 index 00000000..a6bdc9e8 --- /dev/null +++ b/X11R68PostPartumNotes.mdwn @@ -0,0 +1,215 @@ + + +# X.Org Foundation 6.8 release postpartum discussion notes + +[[!toc ]] + + +## Introduction + +These notes serve to document the tasks and issues that arose during the 6.8 release cycle and are intended to be a starting point for further discussion. They are arranged into the following general categories: scheduling, testing, and finalizing the release. + +While the discussion below mainly focuses on tasks that did not work well or need to be improved, it should be noted that the goal of the release team was not to perfect the release process but rather to improve it as much as possible. I (and, from the comment I received, many others) feel that the team was very successful and achieved its goal given the constraints of the release. + + +## Scheduling + +Discussion of this release started in late May 2004; however, due to the travel schedules of most X.Org Foundation BOD members, the schedule was not finalized until mid July 2004. The release was determined to be a time based release since it was driven by several companies (most notably Red Hat and SUSE) that needed to have a newer X Window System release for their upcoming products. Those companies needed to have the release ready at the beginning of September 2004, so the date for the release was initially set to 25 August 2004 in order to give a buffer for problems that might occur during the release cycle. + +The initial deadline for the release left us with a very tight schedule, which had several consequences. + + * The deadlines for the feature freeze and code freeze were severely compressed, which limited the features that could be added and limited the amount of testing that was possible. + * A few bugs that would have otherwise have held up the release had to be postponed until after the release. + * The number of new features added in this release was significant; however, most (if not all) had significant testing outside of the X.Org CVS tree before they were merged in. The majority of the remaining testing and bug fixing for these features were due to interactions they had with other new components. + * It was challenging to keep people working on the features and bugs in order to meet the deadlines. Gentle pressure was applied in most cases to help motivate people on the critical paths. This will likely always be an issue for the release manager. + * Because the release cycle was compressed, it was not difficult to keep people focused on the release. However, if the release cycle was longer, this will likely become a problem. +The schedule was broken down into three phases: adding new features, fixing bugs and updating documentation. The deadlines were set approximately two weeks apart for each phase in order for the release to be completed by the initial target date. + +During the first phase, the tree was open to adding new features, fixing bugs and updating documentation. The primary responsibility was setting up the initial wiki pages to describe the release plan and status, making sure that the community members were aware of the release schedule and coordinating with the authors of the new code to make sure that everything was checked in before the feature freeze deadline. This phase went smoothly with only a small amount of additional work being required to encourage a few of the committers to have their code checked in before the deadline. + +After the feature freeze, the work was limited to fixing bugs and updating documentation. The source tree remained open to all committers to allow for the most people to find and fix bugs. For the release manager, the amount of time and effort required was significantly higher in this phase. The main tasks included: + + * Managing the blocker bug list + * Holding regular release wranglers meetings (3 days/week) + * Keeping people focused on fixing bugs + * Reviewing and checking in fixes + * Resolving conflicts + * Encouraging testing (see testing section below) +Several suggestions were made by the release wranglers to help with fixing bugs. The most important of which was the release bug, which is a commonly practiced method of managing a release. Bugs that were considered serious enough to hold up (i.e., block) the release should be marked as blocking the release bug. Bugzilla allows the release manager to list the dependency tree of all bugs that block the release. While there were several attempts to explain how this worked, there was still some confusion. For future releases, it should probably be explicitly explained on the release and status pages. + +The release wranglers met several times per week -- usually Monday, Wednesday and Friday mornings -- to focus on the blocker bugs and any issues that had come up during the previous few days. During these meetings, the release manager asked for (and usually got) volunteers to work on certain bugs. The remaining bugs were left to the release manager to investigate and resolve. These meetings were invaluable to the release manager. + +Since multiple people were working on fixing bugs at this time, the source tree remained open, which not only allowed the release wranglers to check-in fixes, but also allowed other members of the community to work on and fix issues. The release manager monitored all of the check-ins to make sure that new features were not being added to the release. + +Other important contributions during this stage came from those testing the release. There were quite a few people who were just staring to compile the tree and do testing. They reported bugs and marked them as blockers where appropriate. Some pre-packaged binaries were also made to help those who didn't have the experience of building the source tree, but could help with testing. These packages should be encouraged and made more formal in future releases. The general idea behind the testing for this release was loosely defined, but the details had not yet been worked out at this point, so the majority of the testing during this phase was devoted to build and daily usage testing. + +Two other bugs were added during this phase: the "hold open but not block the release" bug and the release notes bug. The "hold open" bug turned out to be the less useful of the two since there was too much other work to do that these did not get attention. It is possible that this bug might be more useful in future releases if the schedule is not so compressed. The release notes bug was very useful and over the course of the release cycle it became the place where all documentation issues were placed. + +This bug fixing phase was extended by three days to allow several major bug fixes to be completed and checked in. It could have been extended further, but the general feeling what that if we were going to keep on track for a late August release, then we should go ahead and freeze the code. + +After the code freeze, the work was limited to fixing all major blocker bugs and updating the documentation. As noted above, the transition between the previous phase and this one was rather arbitrary to keep the release on schedule; however, it turned out that the main difference was that instead of everyone else checking in bug fixes, the release manager was the only person allowed to check in changes. Bug fixes were being proposed and attached to the release blocker bugs, and the release manager and/or the release wranglers would evaluate the change (where possible) and apply the patch if it was accepted. + +Looking back, having all bug fixes funneled through a single person slowed down the bug fixing too much. For future releases, we should consider having a small team of people with write permission to continue to check in bugs during the critical bug fixing phase. Also, this transition phase should probably happen before the code freeze goes into effect, which would allow the code freeze phase to concentrate solely on documentation changes and last minute critical bug fixes. + +It was during this code freeze phase that the testing was finally formalized. Once the formal testing procedures were documented, many more people started testing the release. The test matrix was updated as time permitted and as new test reports came in. Ideally, the testing should have been happening much earlier, but due to the compressed time schedule the test procedures were not formalized until late in the process. See the next section on testing for more details of the formal testing requirements for this release. + +One action helped initiate the testing: tagging the tree with the first release candidate. This action along with the formalizing of the test procedure appeared to catalyze the community around the release. There were four release candidates tagged during this phase. Perhaps making snapshot tags in the previous release process and defining the test procedure earlier would have helped focus attention on testing before the code freeze. + +As active formal testing began, more bugs were found and fixed in a relatively short period of time, but it soon became clear that the release would not be able to happen on the original schedule. The number of bugs were remaining relatively constant during this time. At this time, a list of the current blocker bugs was sent out each night to the mailing list to let people know the state of each blocker bug. + +Over time the number of blocker bugs slowly shrank, and the focus shifted from bug fixing to updating the release documentation. Initially, the source tree was open to others making documentation only changes, but as the release neared, the source tree was closed to all but the release manager. At that time, the release notes bug became even more valuable to keep track of the features and bugs that needed to be documented. + +The documentation needed to be updated in several places. First, the release number is currently present in the following files in the xc/docs directory: + + * xc/doc/man/general/Standards.man + * xc/doc/man/general/X.man + * xc/doc/man/general/XOrg``Foundation.man + * xc/doc/specs/BDF/bdf.ms + * xc/doc/specs/CTEXT/ctext.tbl.ms + * xc/doc/specs/FSProtocol/protocol.ms + * xc/doc/specs/ICCCM/icccm.ms + * xc/doc/specs/ICCCM/indexmacros.t + * xc/doc/specs/ICE/ICElib.ms + * xc/doc/specs/ICE/ice.ms + * xc/doc/specs/SM/SMlib.ms + * xc/doc/specs/SM/xsmp.ms + * xc/doc/specs/X11/CH01 + * xc/doc/specs/X11/abstract.t + * xc/doc/specs/X11/indexmacros.t + * xc/doc/specs/XDMCP/xdmcp.ms + * xc/doc/specs/XIM/xim.ms + * xc/doc/specs/XLFD/xlfd.tbl.ms + * xc/doc/specs/XProtocol/X11.protocol + * xc/doc/specs/XProtocol/indexmacros.t + * xc/doc/specs/Xaw/CH1 + * xc/doc/specs/Xaw/TPage_Credits + * xc/doc/specs/Xaw/widg.idxmac.t + * xc/doc/specs/Xext/DPMS.ms + * xc/doc/specs/Xext/DPMSLib.ms + * xc/doc/specs/Xext/bigreq.ms + * xc/doc/specs/Xext/evi.ms + * xc/doc/specs/Xext/record.ms + * xc/doc/specs/Xext/recordlib.ms + * xc/doc/specs/Xext/security.tex + * xc/doc/specs/Xext/shape.ms + * xc/doc/specs/Xext/shapelib.ms + * xc/doc/specs/Xext/sync.tex + * xc/doc/specs/Xext/synclib.tex + * xc/doc/specs/Xext/tog-cup.ms + * xc/doc/specs/Xext/xc-misc.ms + * xc/doc/specs/Xi/library.ms + * xc/doc/specs/Xi/porting.ms + * xc/doc/specs/Xi/protocol.ms + * xc/doc/specs/Xmu/Xmu.ms + * xc/doc/specs/Xt/strings.mit + * xc/doc/specs/i18n/Framework.ms + * xc/doc/specs/i18n/LocaleDB.ms + * xc/doc/specs/i18n/Trans.ms +Note that the documentation listed above is current as of the 6.8 release, and might change in the future. + +The documentation in the xc/programs/Xserver/hw/xfree86/doc directory also needed to be updated. This documentation was built from the sgml files in the sgml subdir. The README, BUILD and RELNOTES sgml files will probably need to be updated with every release. The other files should be updated by their respective maintainers as needed. One special file, defs.ent, contains the macro definitions for the current and previous releases, and it was updated. Next, the old XFree86 doctools were required to build the sgml documentation. A few patches were required to build the tools (thanks to Soeren). Egbert added a README.build-docs file that describes what is needed to build and update the docs in the source tree. + +Once the documentation was complete, the last steps to finish the development phase of the release were: + + * Set the final version number and release date in the config/cf/xorg.cf and config/cf/cygwin.cf files + * Tag the tree with the release tag, XORG-6_8_0 + * Create the release branch, XORG-6_8-branch +It was noted in an earlier release wranglers call that the branch could have been created much earlier in the release. Due to the compressed time schedule, it was decided to hold off creating the branch until very late to keep people focused on the release, instead of on new development. This should be reevaluated for future releases. + +Additional discussion points: + + * How should new releases be scheduled (i.e., if someone has a need for a new release, what should they do to get it scheduled)? + * Who/what determines the feature set for a new release? + * When should the stable release branch be created? What are the consequences of creating it earlier or later in the release cycle? + * Who should have write access to the source tree during the various stages of the release cycle? + * When should the tree be tagged for snapshots and release candidates? + * Should the documentation be updated to a more modern format? If so, should all docs be updated? + +## Testing + +For the release to be successful and accepted by the community, it was determined very early in the release cycle that testing the release would need to be a priority. The testing was broken down into two parts: what platforms were to be tested and what tests were to be run on those platforms. During OLS, Stuart Anderson and I discussed both of these issues and then presented it to the BOD. + +First, we determined that, given the scheduling constraints, it would not be possible to test all possible OS vendor, release, architecture, video card combinations, so a subset was proposed as sufficient. These included the operating system, the architecture, the distribution and release version number. Each combination would define a platform to be tested. + +Next, we proposed a set of tests to be run on those platforms. The list included build, install, conformance and run test categories, and we outlined what was required to pass each test category. The tests as well as the platforms were organized into a matrix and was added to the freedesktop wiki: + + * [[http://wiki.x.org/wiki/X11R68ReleaseStatus|http://wiki.x.org/wiki/X11R68ReleaseStatus]] +On that page, the test matrix was included and instructions were given for running each of the tests. Initially the instructions were quite sparse, but as more people ran the tests, they were expanded and improved. + +In the test matrix, the first three columns of each row defined one platform to be tested, and the last four columns displayed the state of the testing on that platform. Entries were labeled with the release candidate version that was tested and were given a green background if the test passed or a red background if the test failed (or had not yet been tested). + +Names responsible for testing (or gathering the test information) were put into the fourth column in an attempt to give people some ownership and responsibility for testing a particular platform. This was moderately successful; however, there were a few problems with this system: + + * The release schedule was incredibly tight and it was not possible to fully test all of the platforms listed. + * The amount of time to run through all of the tests was on the order or 8+ hours (on a 1GHz PC running Linux). Other platforms were significantly slower and some took days to complete the tests. + * Finding volunteers for testing (i.e., adding their name to the table) was not difficult as this was done early in the process, but it was not managed well enough. Clear responsibilities should have been outlined so that this process could have been self-starting and self-regulating. + * Updating the test matrix was cumbersome. Either giving this responsibility to those that volunteered to test a particular platform or automating it so that anyone can update the table would be better. The process for this release required that the release manager monitor the mailing list and update the release matrix as new reports came in. + * By the time the testing had begun, it quickly became clear that there were problems with the tests, which had to be addressed before any testing could truly begin. These problems were worked out within a few days, but the delay caused confusion and slowed down the testing process, and ultimately led to the release being delayed. + * There was also confusion about exactly which tests could be run on each platform. Certain tests could only be run on Linux systems, and comparable tests were not investigated for other platforms. + * The X test suite used was chosen for expediency and ease of use. It was not necessarily the best one available. +The initial goal for testing was to fill in the entire test matrix before the final release. However, it became clear to the release wranglers during the release cycle that the test matrix would not be completely filled, so the goal was changed to fill in as much of the matrix as possible before the release. + +As noted above, testing is a very time consuming process and certain tests lend themselves to automation. Many people do not have the extra test machines required to do run tests; however, for those that do, automating the test process would certainly make it more likely that testing would be done. One key tool that automated part of the testing procedure was tinderbox. It allowed us to quickly notice when recent check-ins broke the build process. During many of the release wranglers calls, tinderbox and related tools were discussed, and it was generally agreed that these tools should be explored further to help automate as many of the tests as possible. + +Additional discussion points: + + * What else should be done to improve the test instructions? + * How can the test matrix be better managed? + +## Finalizing the release + +Once the main development tasks were complete (as outlined above in the schedule section), the release was ready to be packaged and distributed to the community. This finalization stage included building the tarballs and documentation, uploading everything to the appropriate websites and handling the announcement/press release. + +Historically, the source code for each public release is made available through a set of tarballs. Egbert created a script to automate creating the set of tarballs from a checked out source tree. Here is an outline of the steps involved (to be run as root): + + 1. Create a new directory that will hold the release + * `mkdir /tmp/release` + 1. Export the tagged tree to this new dir + * `cd /tmp/release` + * `cvs export -r XORG-6_8_0 xc` + 1. Untar Egbert's build scripts and cd to that directory + 1. Create a directory to hold the tarballs and run the source script + * `mkdir final` + * `cd final` + * `../source /tmp/release` + 1. Rename the tarballs to the appropriate names for the current release + * `cd source/bindist` + * `mv Xsrc1.tgz X11R6.8.0-src1.tar.gz` + * _Repeat for each of the other src files_ +Currently, there are seven tarballs created. Their contents are described in the README file that is shipped with the release (and can be found in the documentation on the website -- see below). + +In addition to the multiple tarballs, it was later determined during the 6.8.1 update release that creating one large tarball containing all source code was desirable. From the web logs, more people downloaded the one large tarball than the set of smaller ones. + +The website on freedesktop includes not only the tarballs (above) but also the documentation for the release. The website is arranged as follows: +[[!format txt """ + X11R6.8.0/ + binaries/ + doc/ + patches/ + PDF/ + src/ + src-single/ +"""]] +The binaries directory contains the pre-compiled binaries for various operating system releases. At this time, no pre-compiled binaries are being made available. We should consider doing this for future releases. + +The doc directory contains the html formatted documentation for the full release. This documentation is taken from `ProjectRoot/lib/X11/doc/html` after doing both a "make install" and a "make install.man" from a full build of the release. These html files also reference the PDF docs, so the PDF sibling directory should contain the documentation from `ProjectRoot/lib/X11/doc/PDF`. + +The src directory contains the set of seven tarballs (described above) along with the md5sums file. The md5sums file can be created with the following command: "md5sum *.tar.* > md5sums". The src-single dir contains the single source tarballs and their own md5sums. For the 6.8.1 release, two single source tarballs were created: one in gzipped tar format and one in bzip2'd tar format. The bzip2 compressed tarball was added since it has become very popular and is smaller than the gzip compressed tarball. + +The patches directory is normally empty for full releases (i.e., releases that have a patch number of 0). For patch releases, this directory would contain the patches necessary to bring the release from the previous full or patch release up-to-date with the current patch release. See the 6.8.1 release for an example. + +The next task of the finalization process is creating the press release. This task took quite a while to get appropriate quotes from members of the community, companies, etc. so it is suggested for future releases that it be started well in advance of the preparation of the website documentation and tarballs. There are other steps required here, but since I was not involved with this task, I will leave it to others to describe the process. + +The goal was to complete the tasks described above and make the release available to the community on 9 September 2004. Unfortunately, several problems occurred and important lessons were learned about how to handle the release announcements: + +Many people were very excited about this release, and we hope that the excitement and enthusiasm carries over to future releases. However, there were some who snooped around the website and found the source tarballs before the official announcement had been made, and this got reported to slashdot. Since the X.Org website had not been updated and the press releases had not been finalized, this pre-announcement by slashdot caused confusion and "stole the thunder" from the official announcement. The lesson here is that the documentation and tarballs should be embargoed in a completely private place that no one other than those involved in the finalization stage have access to. + +The X.Org website and freedesktop website need to be made public at very nearly the same time. The official website should be X.Org with freedesktop as a mirror. However, since few people have access to the X.Org website, the freedesktop site was set up first and the X.Org site files were copied from there. This could have been handled better by embargoing the release. + +The press release needs to be prepared well ahead of time so that the official announcement sent to the press/mailing lists and the unveiling of the websites can be done simultaneously. + +Discussion points: + + * How much ahead of time does the press release need to be sent to the appropriate press outlets in order for it to be released at a specific time (i.e., the time that the embargo is lifted)? + * What other mirror sites are available? What should be done to coordinate with them to make the release available on their sites as soon as possible after the announcement? +-- [[KevinMartin|http://wiki.freedesktop.org/wiki/KevinMartin]] - 29 Sep 2004 (updated for [[MoinMoin|MoinMoin]] 02 Mar 2005) diff --git a/X11R7and69TODO.mdwn b/X11R7and69TODO.mdwn new file mode 100644 index 00000000..58b09090 --- /dev/null +++ b/X11R7and69TODO.mdwn @@ -0,0 +1,36 @@ + + +# X11R7 and X11R6.9 TODO Task List + +[[!toc ]] + +The plan is to use this page as a list of tasks and changes that need to be completed before the combined X11``R6.9/7.0 release. So, please feel free to add tasks that you are currently working on or will be eventually. People who are looking for ways that they can help can go through this list to pick out tasks to work on. + + +## General items + +The blocker bug for the combined release is here: [[https://bugs.freedesktop.org/show_bug.cgi?id=1690|https://bugs.freedesktop.org/show_bug.cgi?id=1690]] + +* Test the code in the tree and file bugs for problems found +* Go through all of the bugs listed in bugzilla and fix those that we can before the release +* Set up tinder clients for your system (see [[http://freedesktop.org/Software/TinderboxWiki|http://freedesktop.org/Software/TinderboxWiki]] for info on how to do this) + +## X11R6.9 + +Tasks for the 6.9 release: + +* Update to latest Mesa release -- note this is still being worked on by the Mesa developers. + +## X11R7.0 + +Tasks for the 7.0 release: + +* Many of the supporting files either have not been created or are currently empty. These include the protocol (for the proto module components), AUTHORS, Change``Log, COPYING, INSTALL, NEWS, README, and DEPEDENCIES files. +* Configure options corresponding to various monolithic tree cf options need to be supported. +* Server: create style guide for Makefile.ams, rewrite to fit. It's a mess right now. [[[DanielStone|DanielStone]]] +* Server: audit files currently being installed and determine if they match the exported SDK from 6.9, and if/how we need to update it. +* Server: port to more platforms (non-trivially difficult). +* Server: quartz, cygwin support +* Server: dmx, Xprint DDXes +* Server: add optional Exa support, expose selected AA via pkg-config. [[[DanielStone|DanielStone]]] +* lib/drivers: add XvMC client side libraries for via and i810
\ No newline at end of file diff --git a/XConsortium.mdwn b/XConsortium.mdwn new file mode 100644 index 00000000..d273a509 --- /dev/null +++ b/XConsortium.mdwn @@ -0,0 +1,170 @@ + + +## Name + +XConsortium - X Consortium information + + +## Synopsis + +Release 6.3 of X Version 11 was brought to you by X Consortium, Inc. + + +## Description + +The X Consortium was an independent, not-for-profit Delaware membership corporation. It was formed in 1993 as the successor to the MIT X Consortium. The purpose of the X Consortium was to foster the development, evolution, and maintenance of the X Window System, a comprehensive set of vendor-neutral, system-architecture neutral, network-transparent windowing and user interface standards. + +The X Window System was created in the mid-1980s at the Massachusetts Institute of Technology. In 1988, MIT formed a member-funded consortium to provide the technical and administrative leadership necessary to support further development of the X Window System. In 1992, MIT and the membership decided it was in their best interests to move the consortium out of MIT and create an independent, stand-alone organization. All rights to the X Window System were assigned by MIT to X Consortium, Inc. on January 1, 1994. X Consortium, Inc. closed its doors on December 31, 1996. All rights to the X Window System have been assigned to the Open Software Foundation. + +The X Consortium was financially self-supporting through membership fees. There are no license fees associated with the use of X Window System standards and code developed by the X Consortium. Membership in the X Consortium was open to any organization willing to execute a membership agreement. + +The X Consortium was a highly participative body. Members were encouraged to actively cooperate with the staff and other members in the design and review of proposed specifications, and in the design, coding and testing of sample implementations of those specifications. + +The X Consortium accomplished most of its work using electronic mail over the Internet, with individual mailing lists for working groups. Internet electronic mail connectivity was viewed as a requirement for useful participation in X Consortium activities. Meetings were held as necessary, often in conjunction with industry conferences and trade shows. + + +## Address + +To reach the X Consortium public Wide World Web server, use the URL: [[http://www.x.org|http://www.x.org]] + +To reach the X Consortium public ftp machine, use anonymous ftp to: [[ftp://ftp.x.org|ftp://ftp.x.org]] + + +## Roles + + +### Staff + +* President: + * Bob Scheifler +* Office Manager: + * Janet O'Halloran +* Director of Marketing: + * Paul Lavallee +* Director of Engineering: + * Jim Fournier +* Manager, X Window System: + * Matt Landau, emeritus +* Technical Director, X Window System: + * Ralph Swick +* Technical Staff, X Window System: + * Donna Converse, emeritus + * Stephen Gildea, emeritus + * Kaleb Keithley + * Arnaud Le Hors + * Ralph Mor, emeritus + * Ray Tice + * Dave Wiggins, emeritus +* Managers, CDE Development: + * Giora Guth + * Peter Bohnert, emeritus +* Manager, CDE Quality Engineering: + * David Brooks +* CDE Architects: + * Kevin Samborn + * Daniel Dardailler, emeritus +* Technical Staff, CDE Development: + * Art Barstow + * Pascale Dardailler + * David Kaelbling + * Mitch Greess + * Robert Seacord +* Technical Staff, CDE Quality Engineering: + * Chris Burleson + * Tom Cavin + * Sami Mohammed + * Mark Schuldenfrei +* Manager, Systems Administration: + * Kevin Ethier +* Technical Staff, Systems Administration: + * Mike Donati + * Amy Rich, emeritus + * Anne Salemme + +### Board of Directors + +The X Consortium's activities and affairs were managed under the direction and oversight of a Board of Directors, elected annually by the Members. The Board was responsible for reviewing the achievements of the Consortium, approving planned work, appointing a President and other officers of the Consortium, and setting membership dues. The last Directors were: + +* Robert W. Scheifler, President, X Consortium +* Dr. Forest Baskett, Senior VP of R&D, Silicon Graphics Computer Systems +* Harold D. Blair, Apogee International Corp. +* Roger S. Gourd, Gourd & Associates +* Dr. Robin Hillyard, Chairman and Chief Technical Officer, Novasoft Systems +* Don McGovern, General Operations Manager and Executive Dir., Hewlett Packard +* Peter J. Shaw, Senior VP, NetManage +* Michael Tobias, President, Tech-Source, Inc. + +### Full Members + +* Adobe Systems Inc. +* Cray Research, Inc. +* Digital Equipment Corp. +* Fujitsu Limited +* Hewlett-Packard Company +* Hitachi Ltd. +* IBM Corporation +* Megatek Corp. +* Motorola, Inc. +* NEC Corporation +* Novell, Inc. +* Oki Electric Industry Co., Ltd. +* OMRON Corporation +* SCO, Inc. +* Siemens Nixdorf Informationssysteme AG +* Silicon Graphics, Inc. +* Sony Corporation +* Sun Microsystems, Inc. +* Tektronix, Inc. + +### Associate Members + +* Boundless Technologies +* Hummingbird Communications Ltd. +* Insignia Solutions, Ltd. +* Mercury Interactive Corp. +* NetManage, Inc. +* Network Computing Devices +* VisiCom Laboratories, Inc. +* Walker Richer & Quinn, Inc. + +### End Users + +* Hughes Aircraft Company + +### Affiliate Members + +* ASTEC, Inc. +* BARCO Chromatics, Inc. +* CenterLine Software, Inc. +* CliniComp, Intl. +* Component Integration Laboratories, Inc. +* Draper Laboratory. +* Electronic Book Technologies, Inc. +* Gallium Software, Inc. +* Georgia Institiute of Technology +* Human Designed Systems, Inc. +* INRIA - Institut National de Recherche en Informatique et en Automatique +* Integrated Computer Solutions, Inc. +* Investment Management Services, Inc. +* Jupiter Systems +* KL Group Inc. +* Massachusetts Institute of Technology +* Metheus Corporation +* Metro Link, Inc. +* Object Management Group, Inc. +* Open Software Foundation +* Performance Awareness Corp. +* Peritek Corp. +* Petrotechnical Open Software Corp. +* Point Technologies, Inc. +* Shiman Associates, Inc. +* Smithsonian Astrophysical Observatory. +* Software Development Corp. +* SOUM Corporation +* Spectragraphics Corp. +* Tech-Source, Inc. +* TriTeal Corp. +* White Pine Software, Inc. +* World Wide Web Consortium. +* The XFree86 Project, Inc. +* X Inside, Inc.
\ No newline at end of file diff --git a/XDC2007Notes.mdwn b/XDC2007Notes.mdwn new file mode 100644 index 00000000..4af91ef3 --- /dev/null +++ b/XDC2007Notes.mdwn @@ -0,0 +1,300 @@ + +[[!toc ]] + +These are running notes from the X Developer's Conference in San Jose, February 7 through 9, 2007. Please add more content, and reformat to look prettier. + + +## Wednesday, February 7 + + +### (intro speech) + +What are we doing this year? By the end of the week, we should know and communicate this. + + +### Peter Hutterer: MPX + +Slides: [[PDF slides|XDC07_mpx_slides.pdf]] + +Basic problem: Only one focus for keyboard and mouse input + +All the existing multi-user toolkits don't work. You have to write to them, doesn't work for arbitrary apps. So, hey, let's give X multiple pointers! + +Basically all functionality works. Each pointer acts like a core pointer, like an XI pointer, can have different shapes, can be queried, can be warped, each keyboard can have different focus, and pointers and keyboards can be dynamically associated. + +So what changed? + +Event delivery is modified so that every device has its own sprite structure, instead of just one like we have now. Therefore, on event dequeue, we know _which_ device generated the event. + +Cursor rendering goes entirely through software now, since basically no hardware has more than one cursor in hardware. This had to be extended to handle the cases where the backing tiles for each cursor overlap. + +In standard X, you get one shape per window, and shapes can be inherited. In MPX, each device can have one shape per window, and the inheritance works the way you expect. + +[[QueryDevicePointer|QueryDevicePointer]] [[WarpDevicePointer|WarpDevicePointer]] [[DefineDeviceCursor|DefineDeviceCursor]] [[ChangePointerKeyboardPairing|ChangePointerKeyboardPairing]] Device{Enter,Leave}Notify [[PairingChangedNotify|PairingChangedNotify]] + +~30 calls in the core protocol no longer have a defined state. Possible solution: "[[SetPointerBehaviour|SetPointerBehaviour]]" for [[FollowSingle|FollowSingle]], [[DevicePointer|DevicePointer]], etc., which the window manager would enforce for naive apps. Lots of race conditions until this happens when multiple users are interacting with the same window or widget. + +Really need window manager support for this to work. There is a demo wm that works, blackbox kinda works, metacity completely doesn't. + +Also, applications need to become aware of this too. Pointers can pop in and out of existance now. + +Things to think of: + +* Floor control +* Relative device events +* Multi-user cut-and-paste +* Mouse cursor restacking +* Gesture events +It's not ready yet. + +Questions: + +* Composite and DMX integration? "Not yet, would be cool" +* Use cases? "Lots, needs more research" +* How to handle hotplug? "That's Daniel's problem." + +### (Intermission for lunch orders) + + +### Philip Langdale: Virtual Multihead in VMware + +Host support + +Single head: plain fullscreen + +Multihead: Old school manual window resizing + +Guest support, since this was pre-RANDR 1.2: yet another pseudo-xinerama. Additional call to the vmware extension to send a new xinerama config. + +Needs RANDR 1.2 integration. EWMH needs extending to cover maximization across multiple screens. + +(shiny demo) + + +### (another intermission) + + +### Keith Packard: RANDR 1.2 + +Things we had tried before: Xinerama, xf86vidmode, RandR Classic + +Core X does not support multiple screens well. Number of screens is fixed, size of each screen is fixed, monitors probed at startup. This info is passed over to Xlib at app startup, and is really hard to fix. The server also makes this fragile internally, but that's fixable. But many resources are per-screen, so it just doesn't work the way you want. + +Xinerama. Merges many monitors into one screen. Allows apps to move across screens, which is cool! Screen config was fixed at startup, so suitable for fixed multi-head environment. (Initial implementation also happened to be wildly inefficient.) + +Changing modes was xf86vidmode. Changes monitor mode on the fly, but not the screen size. Whee, pan and scan. Also exposes gamma correction. But screen size is still fixed at startup, and set of modes fixed at startup. + +Changing screen size was RandR. Runtime changes to screen size, but still fixed set of sizes and monitor modes, and mode expressed as size and refresh only. + +Randr 1.0 done for kdrive for rotation. When added to xfree86, was done without changing drivers, so no mode reprobing, no rotation... + +RandR 1.2 fully expresses hardware capabilities. All configuration can be changed. Unified config file structure, reduced driver-specific code, unifies the semantics of the above extensions. + +The three objects: Screen, CRTC, Output. (Pretty picture). One screen, N CRTCs, connected to M outputs. (Shiny demo) + +What else can it do? LUT for gamma adjustment. Arbitrary output properties. User defined modes. New driver-independent API. + +Minor driver problems. XAA is kind of gross, DRI is fixed. + +Protocol is finished, DIX implementation is finished, intel driver working, radeon and nouveau nearly working, gtk-based UI demo. Need to fix remaining drivers and finish rotation/reflection work. + + +### ajax: Xorg releases and future planning + +The current release is almost done, and is blocked on the documentation release. That's mostly a build system issue, and we should work on making the docs build something that is less of a disaster for future releases. + +However, the release process is far too heavyweight, and we have pieces of our process which are not adding value and burning out release managers. Prevailing opinion has been that this is probably a job for more than one person, but we might be able to get it down to something manageable by a single person sustainably. We've also been doing a better job of documenting our processes ([[MakingReleases|MakingReleases]]), so that the release process is transferable between people. + +Currently, the release manager is rolling releases for everything that has been touched but not released as part of releasing the katamari. This was not the initial plan for modularization, which involved getting individual maintainers per module. There are several solutions to this burden on the release wrangler + +* ajax: remove more modules from the katamari. We have a lot of dead weight that shouldn't be bothered with any more. +* get more individual maintainers to take care of modules +* remove the burden of doing new releases not critical to the katamari from the release manager's responsibility. +If we remove the responsibility of catching minor changes to unloved modules for release, then we should automate reminder messages to get those released after they've been sitting stable for some amount of time. + +The badged tarball idea needs to be abandoned. The badged tarballs don't match the unbadged versions, and don't even distcheck. Instead, our only badging process that's recorded outside of the release announcement would be a git tag for the katamari in each module (which is somewhat failure-prone, but can be remedied if mistakes are found). + +As far as abandoning modules, abandoning apps katamari entirely was discussed but thrown out. + +The X Server release should be decoupled from the katamari release. So the upcoming server release planned (~2 week timeframe) will be 1.3 instead of 1.2.1. + +We should do a better job of maintaining stable branches. This is the responsibility of OSVs and others maintaining stable releases. However, if we accomplish our goal of faster releases, it may be less interesting. + +The planned features for 1.3: + +* exa updates from master +* damage protocol update (already merged) +* randr 1.2 with xfree86 layer (randr 1.2 base already merged) +The planned features for 7.3 katamari (1.4+ xserver, ~May 2007) + +* XACE merged (almost done) +* Apple's OSX support (pended for 7.2 release to not disturb it) +* lobotomized generic DGA (will be done, straightforward) +* input hotplug (ready) +* GPU -> CRTC mapping property for randr. +* input transformation +* active module deprecation +* PCI rework +Desired goals for 7.4 katamari (1.5+ xserver, ~Nov 2007) + +* XAA death (large change, but mostly mechanical) +* DRI memory manager +* kernel modesetting support +* GLX 1.3 +* GL acceleration architecture +* MPX +* XCB server-side +* ABI rework +* FB rework +* DMX/Xinerama integration +ABI/API compatibility was discussed. One proposal was the kernel model, of just releasing the server when server people want to, and if that breaks things then people get to recover. keithp's proposal is maintaining API compatibility between last stable releases and master, but not ABI. This is being experimented with in the intel driver, and appears to be promising, allow more change, but still maintain what OSVs really want (recompiling lets you take new driver and run on old X Server, or take new X Server and run with old driver code) + +Eric Anholt is signed up for the 7.3 release management. Badged tarballs will not be done. Rolling releases for minor fixes will be up to people interested in seeing those fixes go out -- only the X Server and other criticial releases will be rolled by Eric. + + +### (keith doing nerdcore about randr1.2 api) + + +## Thursday, February 8 + + +### Board Q/A session + +Observations: lack of structured talk scheduling doesn't seem to reduce the amount of quality technical discussion. Flipside is that the small sessions need to be responsible for reporting their results. + +Do we need to go as far as professional facilitators? Maybe not. But hey, look, office supplies! (Pass stuff out.) Let's try to write stuff down. + +Do we want to try changing the format to a hothouse / retreat? Yeah, maybe. One thing lacking this year was that, last year, almost everyone was at the same hotel, which encouraged after-hours discussion and work. Suggestion for next year is to either reserve hotel earlier so we can get block allocation, or try the retreat format. + +It's been suggested that the board should facilitate small group meetings. So, yeah, if you have a proposal for this kind of thing, please send it to the board so they can get that started. All reasonable proposals will be entertained. Local groups, small interest stuff, etc. + +Question from a non-member: I'm not one, should I be? It lets you vote on the board, host events, represent the organization at conferences and trade shows, etc. It's free, there's really no downside, and it announces your participation in the X development community. Do it! + +Suggestion: Is it possible to do something like Summer of Code directly from X? Sure. Board hasn't finalized anything yet, but could be doable. The important thing about SoC is that it's not about producing code, it's about teaching students. + + +### Joe Miseli: Display technology, VESA, and EDID + +[[PDF slides|Xorg_2007-EDID-JMiseli.pdf]] + +EDID is the mechanism by which monitors describe themselves. It's now technically called E-EDID since it's been extended, but it's still the same thing. EDID is now at version 1.4. + +Review of various display technologies in use today: CRT, LCD, plasma, projector, etc. Most fixed-pixel array displays have scalers. Newer and higher resolution displays have no pure scalers, so EDID becomes critical for driving them correctly. + +Review of display interfaces: VGA, DVI-{D,I}, HDMI, [[DisplayPort|DisplayPort]], UDI... + +A display may have many timings, CRTs for example are basically infinitely adaptable within their sync range. Some may have a few timings, or even only one. All cases are handled by EDID. The purpose of EDID is to make sure that _something_ comes up at power on. + +Signalling: Video content, blanking, sync, I2C digital signals for communication. Connector may carry other pins too (USB, audio, etc). (Timing math.) Timing specs include DMT, GTF, CVT. DMT was pages of explicit timings, GTF and CVT are formulas. + +Sync. Three main times: separate, where H and V can be positive or negative on independent pins; composite, where they're combined into one phase- coherent signal (unsupported but sometimes works for DVI); and sync-on-green, which is a DC-bias added to the green signal. + +Version table: 1.1 in 1996, 1.2 in 1997, 1.3 in 2000, 1.4 in 2006. 1.3 was the first that could handle extension blocks. + +Timing priority order: Preferred timing, other detailed timings in the base block, other detailed timings in the VTB-EXT, 3-byte CVT codes in base or extended blocks, standard timings, established timings, base video mode. + +Related vesa standards: CVT, DMT, DPM, DDC/CI, DPVL, MCCS, MDDI. DDC is the carrier channel for EDID. Coordinated Video Timings and Detailed Monitor Timings are various timing specs. DPM (successor to DPMS) is for Display Power Management. Basically, missing pulses on either or both sync pins plus inactive video means low power mode. DPMS was more complicated where there were standby and suspend modes between On and Off, depending on sync pin wiggling. + +Extensions: CEA, VTB, DI, LS, DPVL. (consumer electronics conformance, video timing block, display information, localised strings, and digital packet video link.) CEA is the DTV profile for uncompressed high speed digital video. DDC/CI allows for control of displays, basically anything you could do from the front panel and more. MCCS is the standard command set for DDC/CI. DPVL allows for only updating the regions of the screen that have changed. + +Lots of changes in EDID 1.4. (Will acquire slides for the list.) + + +### Eamon Walsh: Security in X + +(See [[SecurityTalkAgenda|SecurityTalkAgenda]]) + +"The trick is to have a consistent set of lies." + + +### Bart Massey: Cut and Paste + +Something about elephants. + +Cut and paste suffers from weak guidelines, data type hell, and indifference. The problems really exist, are easy to find and demo. Need to figure out requirements, then the fixes, draft the spec, write the library to make it work, and fix the visible important apps. + +Amusingly enough, DND works more reliably than copy and paste. The problem space here is cut/copy/paste versus select/insert. Should work for text, pictures, and "other". + +How it works: highlighting a region makes it the PRIMARY selection. You can either middle-click to paste the PRIMARY, or hit ^C to copy it to the CLIPBOARD. ^V pastes from CLIPBOARD. That would be a nice theory, but it's not consistently implemented. + +Non-text selection is also completely broken. + +Anyway it's all busted and it needs to be fixed. Will be starting the CCP Strike Force to make this work. Join! Do stuff! + + +## Friday, February 9 + + +### David Reveman: Compiz + +What is compiz? Compositing window manager with flexible plugin architecture. + +Latest additions include multihead support and pluggable fragment shading. (shiny demo of stacked fragment plugins) + +Wants to switch to software cursors. Doing this properly requires modifying the Fixes extension's reporting of cursor changes to include the sprite dimensions and hotspot. + +Also wants to change the Xv interface to allow the compositing manager to do the colorspace conversion and scaling, which would be slightly more efficient in terms of copies, gets frame sync (potentially) right, etc. + +Drawing synchronization. Could be done entirely client-side, but could also have server-support. Most of the server support options are fairly brutal; needs more thought. Do client side first. + +Input transformation. Need it so you can interact (correctly) with transformed windows. Match the triangle primitives of the windows to an input mesh, and do the straightforward pick. Implementation is started, where Composite clients provide pairs of triangles that specify the mapping lfrom the composite window to the redirected subwindow. Minimal DIX changes to XYToWindow, [[WriteEventsToClient|WriteEventsToClient]], and [[TranslateCoords|TranslateCoords]]. + +Retained drawing interface. Currently have interfaces for decorations, video, thumbnails, blur-behind-window, etc. Want one common interface instead, with tree hierarchy of inheritance, extensible by current plugin architecture. + + +### Quinn Storm: Beryl + +Beryl is another GL-based compositing manager. Started as a fork of compiz, has many more visual effects, bit more experimental of a plugin interface, etc. + +(mostly demo) + + +### Brian Paul: Mesa + +Memory management update. Initial development done for unified memory architectures like i915, currently working on VRAM architectures. Accelerated readback for glReadPixels and glCopyPixels not quite sorted, but soon. Also working on sub-allocator for more efficient management. White paper coming soon! + +VBO changes. Will enable storing vertex data in GPU memory, avoids per-draw host-to-GPU memory transfer. All vertex-related drawing code done in one place now; glBegin/glEnd converted into VBOs, as are display lists. Simplifies life for driver writers too, including helper code for buffers larger than the hardware can handle. Todo: implement compiled vertex arrays in the same way, update the DRI drivers to use the new path. + +OpenGL shading language. Mesa has kind of had this support for a while, but had no hardware support, very slow, etc. Previously had support for the ATI and nVidia extensions, but GLSL wasn't integrated with this. Shaders are clearly the way forward, so we need to get Mesa fixed to handle this. + +(example shader program walkthrough.) + +(shader compiler diagram. ATI_fp and friends had one front-end, one middle-end for representation, and N backends for execution. GLSL had own front-end, but different middle- and backends. New model unifies this, and adds a stage for optimization and hinting. + +Kept the GLSL tokenizer/parser, but replaced the rest. Pretty much a straightforward compiler design. Need to extend the IR to handle new instructions (jump, branch) and addressing modes. Other changes needed to handle the different between ARB shader extensions and the GL 2.0 version. + +GL 2.0 API interface is complete, supports most of the language except: arrays, structs, multishader linking, and integer ops. Need to implement indirect addressing for arrays. Register allocation is fair but not great. No subroutining, everything is inlined. No hardware backends updated for this yet, but not a huge job to add. Backends need to be extneded to say what instructions are supported. Error detection is kinda poor. Possible extras: profiler, histogram, debugger, peephole optimizations, etc. + + +### Andy Ritger: Multi-GPU X Screens + +Why would you want to use multiple GPUs? Solve larger problems, throw more power at large problems. SLI is one technique for splitting the scene among multiple GPUs. Xinerama is another technique for big desktop. The two are not mutually exclusive. + +SLI allows multiple GPUs to render one X screen. Multiple modes: alternate frame rendering, scan line interleaving, and SLI + antialiasing. + +Xinerama means two things. One is the protocol, which defines the "screen" layout. The internal implementation is the code that splits the protocol requests among multiple hardware drivers. + +Unofficial terminology: the "physical" X screen is a video memory buffer in a single GPU, the "logical" X screen is the object as visible through the protocol to clients. + +Use cases: Powerwalls. Caves. Large desktop. Multiple logical X screens. + +What do we have today? TwinView/MergedFB, where two display devices are connected to one physical X screen (vram buffer). Multiple X screens per GPU, sort of the classic X "Zaphod" mode; allows you to advertise different capabilities per screen. Xinerama, where you have multiple physical X screens glued together into one logical X screen. RANDR 1.2 operates on a logical X screen, basically allows dynamic reconfig of MergedFB/TwinView. + +What's nice about the existing Xinerama? Transparent to X drivers, and mostly works today. What's bad? Lots of resource duplication, which causes performance issues. What does it mean to redirect windows with multi-GPU X screens? RANDR and Xinerama (implementation) are mutually exclusive. + +Ideas: Post RANDR 1.2, expose physical X screen in the RANDR protocol, which would allow the combination of the two. Apply DMX lessons and work to the Xinerama implementation for optimization. Expose ways for compmgrs to control what GPU receives the allocation for a redirected pixmap. + +Nothing solid yet. Think about how to address these issues. + + +### Bart Massey: XCB mini-status + +It lives! 1.0 released, included in [[X11R7|X11R7]].2. Supports most of the X protocol. Team of about 6 active contributors with occasional casuals. Used for the client-side protocol libraries, but not the server (yet). + +XCB is XML descriptions of the protocol, with XSLT to produce the C "top half". The C bottom-half contains the transport and multiplexing code. Xlib now built on the XCB bottom-half. Conceptualised in ~2000, originally done in m4 instead of XSLT. + +There is minimal magic here, it's just protocol. Latency hiding is free, threading just works, error handling fixed, protocol docs are handy for other tools like wireshark or language bindings. + +Lets you mix and match Xlib and XCB code, which allows the transition. Make the transition short, of course. It's slightly volatile and sometimes awkward to work with, the team bandwidth is slightly low, etc. But it's a good start. Still need client libraries, XSLT cleanups, get XCB into the toolkits, to use it on the server side, and to grow the team. + +Question: can I handle disconnect politely with XCB? Yes, but maybe not if you're using the Xlib frontend. diff --git a/XDC2007Notes/XDC07_mpx_slides.pdf b/XDC2007Notes/XDC07_mpx_slides.pdf Binary files differnew file mode 100644 index 00000000..62b05102 --- /dev/null +++ b/XDC2007Notes/XDC07_mpx_slides.pdf diff --git a/XDC2007Notes/Xorg_2007-EDID-JMiseli.pdf b/XDC2007Notes/Xorg_2007-EDID-JMiseli.pdf Binary files differnew file mode 100644 index 00000000..98907675 --- /dev/null +++ b/XDC2007Notes/Xorg_2007-EDID-JMiseli.pdf diff --git a/XDevConf.mdwn b/XDevConf.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/XDevConf.mdwn diff --git a/XHotplugProposal.mdwn b/XHotplugProposal.mdwn new file mode 100644 index 00000000..588f3e2d --- /dev/null +++ b/XHotplugProposal.mdwn @@ -0,0 +1,82 @@ + + +# X Hotplug Proposal + + +## Table of Contents + +[[!toc ]] + + +## Overview + +This is a proposal for converting the entire X server over to a hotplug-capable configuration mechanism. This effort expects to occur on similiar time scales as the modular code effort and the X on GL effort. The proposal is designed around a non-root X server not being possible in the near future. + + +## Phases + + +### Phase 1: Design + +[[EgbertEich|EgbertEich]] suggested using a different IPC method than the X protocol. This immediately solves the security problems. Possibilities include dbus or another named socket (/tmp/.X11-unix/X0.conf ?). + +The currently evolving plan is to have an external device daemon that informs the server of available devices. This external daemon can help with system level access control and negotiation among multiple servers. This daemon would handle all direct communications to the OS-dependent hotplug system. + +The list of input devices on the server is not simply be a list of all local devices. It should be possible to keep devices 'installed' in the X device list, even if that device gets unplugged. Newly discovered local devices should generally not be automatically installed into the X Device List. One approach is to have a Device Manager, somewhat like the Window Manager, which handles every addition or removal to the X device list. + + +#### Questions + +* Would the named socket cause problems with cygwin? (or other archs?) +* Is dbus an acceptable dependency? +* The configuration client would probably expose itself on dbus if we want DEs to be able to fiddle with policy. (This would be instead of the DEs writing their own configuration client, since with a root X server that's a security problem), so a dbus dependancy wouldn't be necessary in Xorg even if we want to control Xorg from across dbus. + +### Phase 2: XINPUT + +The protocol will expose only the device_presence_notify event. The AddDevice and RemoveDevice commands will be exposed on the new configuration IPC mechanism (chosen above). + +Backwards compatibility with newly broken code can be solved by exposing a single mouse and single keyboard to any client that doesn't request a new enough version of the XINPUT extension. These devices should be horrendously generic and barely reflect the hardware. + +Essentially, if we go the "virtual device" route, only these devices would be exposed to old clients (since they are never added or removed). + + +#### Questions + +* Compatibility will be lost for clients that want to use special features of input devices. (Are there any common cases other than drawing pads under the gimp? What else specifically uses extension devices?) I don't see an alternative: either we break code or we break features. I prefer to broken features to crashing code. (Are the problems with gtk crashing bugs?) +* [[XInputHotplug|XInputHotplug]] suggests remote input devices may be a problem. Is there any reason to natively support these rather than implement them as a driver? +* Should the core pointer and keyboard continue to exist? Should they be converted into "dummy" devices instead and have all new input devices SendCoreEvents by default? ([[XOrgInputDriverSpec|XOrgInputDriverSpec]] suggest the dummy pointer (or virtual pointer) method) +* Should multiple cursor support be native, or should things like the MERL projector table expose numerous devices and have the client monitor each one individually? Perhaps clients could request that multiple, specific devices become pointers (locked into that client's window, so as not to confuse other clients)? + +#### Further work + +There are a number of issues raised on the [[XInputHotplug|XInputHotplug]] page under the "XInput Protocol" and "Other Stuff" sections about driver ugliness and protocol problems. Also [[XOrgInputDriverSpec|XOrgInputDriverSpec]] and [[XInputSpec|XInputSpec]]. These changes to the protocol would probably go in along with the device event, so phase 2 depends on this work as well. + + +### Phase 3: General + +Move all configuration into the configuration client. The parser for /etc/X11/X![[OrgConfig|OrgConfig]] would be moved into its own client and out of the X server. The client can now control everything about the X server, including displays. + + +#### Questions + +* Presumably, opening sockets for regular clients to connect would be a command issued by the configuration client. Should we just error if the command is issued before the X server has a full configuration, or should we begin supporting a partial configuration? +* Are all the event notifications we need in order to support display-hotplug present? Would adding another head be any different than a "mode change" from 800x600 to 1600x600 to the client? Would any client even care if we suddenly start rendering to a projector as well as an lcd? (other than the configuration client) + +### Phase 4: Completion + +Presumably at the same time XOrg begins using OpenGL, mode changing will be freed up. This responsibility could be moved out of the X server and into the configuration client, and only framebuffer configuration would be sent to the X server. See questions belows. + +At this point, X![[OrgConfig|OrgConfig]] is just another configuration client. Any internal assumptions about configuration format can be changed without external compatibility problems (just change the client to send information in the new format). (except for binary drivers? If X on GL happens, would nvidia or ati even have a binary driver for xorg anymore?) + +After this phase, external configuration clients could be encouraged. Prior to this, maintaining backwards compatibility for external clients would mean we wouldn't gain anything by making the client do something because the server would still have to be able to do it, just in case. Therefore, we don't care about compatibility until this point. + + +#### Questions + +* The mode selection part is debatable. I think it would be better for it to seem to the configuration client that the X server still does mode selection, even if that is moved into a shared library outside of the X server (mesa?). -- [[TedKaminski|TedKaminski]] - 22 Jan 2005 + +## See Also + +* [[XInputHotplug|XInputHotplug]] +* [[XOrgInputDriverSpec|XOrgInputDriverSpec]] +* [[XInputSpec|XInputSpec]]
\ No newline at end of file diff --git a/XInputHotplug.mdwn b/XInputHotplug.mdwn new file mode 100644 index 00000000..060d303a --- /dev/null +++ b/XInputHotplug.mdwn @@ -0,0 +1,94 @@ + + +# XInput Hotplug +[[!table header="no" class="mointable" data=""" + /!\ The following description is quite out of date and left for historical reference only - the DBus API described below was later rev'ed to version 2, then deprecated in favor of [[HAL|XorgHAL]], which itself was deprecated in favor of udev on Linux. +"""]] + + +## Table of Contents + +[[!toc ]] + + +## Overview + +The X.org server supports hotplugging input devices since November 2006 [[http://lists.freedesktop.org/archives/xorg/2006-October/019007.html|http://lists.freedesktop.org/archives/xorg/2006-October/019007.html]] ([[X11R7|X11R7]].2 will NOT have hotplug support yet). + + +## Design + +The X.server uses DBus to get information about devices that are to be added or removed. From [[http://cgit.freedesktop.org/xorg/xserver/commit/config/dbus-api?id=ec35e7198debf938f1115f584e675ce5995743e3|http://cgit.freedesktop.org/xorg/xserver/commit/config/dbus-api?id=ec35e7198debf938f1115f584e675ce5995743e3]] + + +[[!format txt """ +D-BUS Configuration API v0.1 +---------------------------- + +The X server will register the bus name org.x.config.displayN, and the +object /org/x/config/N, where N is the display number. + + +Currently only hotplugging of input devices is supported. + +org.x.config.input: + org.x.config.input.add: + Takes an argument of key/value option pairs in arrays, e.g.: + [ss][ss][ss][ss] + is the signature for four options. These options will be passed + to the input driver as with any others. + Option names beginning with _ are not allowed; they are reserved + for internal use. + + Returns one int32, which is an X Status, as defined in X.h. If + everything is successful, Success will be returned. BadMatch will + be returned if the options given do not match any device. BadValue + is returned for a malformed message. + + Notably, BadAlloc is never returned: the server internally signals + to D-BUS that the attempt failed for lack of memory. + + The return does not notify the client of which devices were created + or modified as a result of this request: clients are encouraged to + listen for the XInput DevicePresenceNotify event to monitor changes + in the device list. + + org.x.config.input.remove: + Takes one int32 argument, which is the device ID to remove, i.e.: + i + is the signature. + Same return values as org.x.config.input.add. + +"""]] +The main idea behind keeping the discovery mechanism out of the server was that different systems can use different mechanisms. On GNOME or KDE desktops it would make good sense to use [[HAL|http://freedesktop.org/wiki/Software/hal]] for detection (which is a cross-platform device detection and enummeration system), but an embedded system may well want to use something more lean. + +Also, by moving the mechanism to an X client daemon, you can implement desktop specific policy in the daemon. For example, in the GNOME environment you could have a daemon that reads per user settings for input devices from GConf. + + +## XInput Protocol + +A event was added _devicePresenceNotify_ to notify a client about new devices. XI has been bumped to version 1.5 + + +## Code + + * Simple, experimental device manager in C: git://anongit.freedesktop.org/users/daniels/respeclaration + +## Other Stuff + + * The design of XOrg XINPUT drivers is undocumented, and inconsistent. The main driver Control() functions are not being used correctly, with PreInit() doing much of the work for DEVICE_INIT and DEVICE_ON. + * Main.[[JoeKrahn|JoeKrahn]] suggests: combining the various other driver export functions into additional deviceControl() operations to create as a single driver access point, rather than Probe(), PreInit(). This function could also be used to replace the numerous standard driver-name symbols like _DriverName_Options. This would require a change to the module ABI, but would be, IMHO, much simpler and cleaner, and allow for things like returning an altered option list, based on the hardware. + +## Issues + + * Security: allowing any client to ask the server to open a file as an input device is problematic. E.g. adding a mouse and specifying /etc/passwd as the device file. + * Backwards compatibility: GTK+ doesn't handle disappearing XInput devices well. One option is to keep a shadow list that doesn't change, and export that to clients that haven't asked for a recent enough version of XInput. + * Remote devices: how well does this integrate with remote input devices? + * DBus' behaviour to abort the process (using assert()) if an error in the library occurs. This behaviour was considered inappropriate by Daniel Stone, with announcements that it may cause DBus to be removed again [[http://lists.freedesktop.org/archives/dbus/2006-November/006390.html|http://lists.freedesktop.org/archives/dbus/2006-November/006390.html]]. + +# See Also + + * [[XInputSpec|XInputSpec]] - Related updates for the XInput extension. + * [[XOrgInputDriverSpec|XOrgInputDriverSpec]] - Input Driver module design. + * [[XHotplugProposal|XHotplugProposal]] - Initial proposal for the hotplug design. +-- Created by Main.[[KristianHogsberg|KristianHogsberg]] - 02 Jul 2004 diff --git a/XInputSpec.mdwn b/XInputSpec.mdwn new file mode 100644 index 00000000..bbb94c38 --- /dev/null +++ b/XInputSpec.mdwn @@ -0,0 +1,196 @@ + + +# XInput Extension Specifications (Developmental Proposal) + +**This page is out of date and its content is provided for historic reasons only. Some of the features below is superfluous, others have been implemented already. This is not a guide to the future of input development.** + + +## Table of Contents + +[[!toc ]] + + +## Overview + +This page is intended as a place to evolve the design specifications for the next version of the XINPUT for the X.org server. This includes a long needed update to the XINPUT specification to improve support for better device controls, hotplugging, and multiple core devices. This page focuses on the XInput protocol. The implementation in the XOrg server should be documented in [[XOrgInputDriverSpec|XOrgInputDriverSpec]]. + + +## Introduction + +First, an important question: Should the XInput improvements all be part of XInput 2.0? XInput includes several commands that resemble a general purpose interface to extension events. Furthermore, many of the needed improvements for managing and configuring input devices are applicable to output devices, including something as substantial as a hot-pluggable PCMCIA video card. + +So, in addition to the much-needed update to the XInput protocol, should there also be another extension called (perhaps) XDevice, that defines all of the runtime device configuration and management issues that are not part of the existing XInput? + +Or, should we just extend XInput, and not worry that it is really applicable to more than just input devices, despite the name? This is already true for XInput because Feedback events are a form of output. (In a way, a graphical display is just a very elaborate central Feedback device.) Besides, HID is similarly misnamed. + + +## HID Protocol Features + +The HID design is a verbose and inflexible, rather than a simple but extensible design. This does not really fit the overall X design concept very well, so it does not make sense to incorporate the actual HID spec into X. However, most modern input devices are designed around HID, so XInput should attempt to be HID compatible. In otherwords, XInput should be able to include device and control attributes that correspond to HID names, but these should all conveyed by name rather than using all of the HID enum values. + +One useful aspect of HID is Device and Control Usages. XInput has some support for Device Usage by including a type Atom in the X![[DeviceInfo|DeviceInfo]] structure, although it has not been adequately implemented. It is reasonable to define the standard type Atoms with the corresponding HID Usage names, which already include several common type names typically used in X, such as Pointer, Keyboard, Joystick. + +Individual controls do not have a similar type identifier, but one should be incorporated into the various control Info structures. Each info structure includes a length value. That means it is possible to extend these structures and keep backwards compatibility. The extended structures should also include additional details about each control. For example, buttons can be described as momentary or toggle switches. + +Rather than trying to define a few additional specific properties, it is probably best to support a variable number of parameter+value pairs for each device and each control. This allows for extensibility, and can work similar to Window properties. + + +## Security Considerations + +Device event handling has important security implications. Currently, security is handled with global Display access, and temporary Device Grabs. With the possibility of multiple input devices, multiple servers, and even [[multiple users on the same Display|http://www.freedesktop.org/wiki/MultiplePointers]], event access control needs to be more explicit. So, devices need security attributes, which probably need to be implemented in a similar way for explicit access to/from individual windows. + + +## Proposed Additional XInput Functions + + +### X[Get|Change|Delete]DeviceProperty(), X[List|Rotate]DeviceProperties() + +A straightforward method of implementing extensible and diverse device properties is to provide each device with a set of properties that is accessible in a manner similar to Window properties. This allows for a variety of data formats and sizes, and would use the existing Window Property infrastructure. Device Properties can relay all of the information about input usages, advanced pointer-acceleration curves, etc. + + +### XChangeDeviceControl(), XGetDeviceControl() + +This function is important, but drastically incomplete. The Device Property interface could probably work as a complete replacement for these functions, but it is useful to have separate interface for active commands that affect the hardware. However, note that the single defined device control, DEVICE_RESOLUTION, is more of a property than a hardware command. + +Rather than adding a new data structure for each new control type, it is better to use an approach similar to window properties, except that control data is interpreted rather than simply being saved in a database. + +Some undecided issues: + +1. Should XDeviceControl() simply be left as a 'legacy' function and use general Device Properties instead? If so, is it reasonable to have a property be acted on as an active command by a device (i.e. set property DEVICE_COMMAND = "reset")? +1. Is it useful to implement new, specific data structures for some common device controls, as intended in the original XInput design, or should all new controls be implemented using the generic mechanism? +1. Should the generic control value also support 16-bit and 32-bit data? Window Properties and Client Messages both support multiple data sizes, but it may be an unnecessary complication. Are there any good examples control parameters that would benefit from 16 or 32 bit data? Data for a force-feedback would be an example, except that it is better implemented as a Feedback, not a Control. +1. How will the control be implemented? One possibility is to send the control data as a new Device Control in the existing X![[ChangeDeviceControl|ChangeDeviceControl]](). Another possibility is to implement a new function that is designed around generic character data values. +This approach is completely compatible with the existing XInput protocol, but is not really using the control type argument as originally intended, and adds unnecessary complexity. + + +### X[Add|Remove][Keyboard|Pointer]Device() + +There should be a formal mechanism for multiple Pointer and Keyboard devices capable of sending core events. Question: how will these functions interoperate with X![[ChangePointerDevice|ChangePointerDevice]] and X![[ChangeKeyboardDevice|ChangeKeyboardDevice]]? Should X retain the concept of a single "primary" mouse and keyboard, and have the new functions enable/disable devices to emit core events in addition to the core devices? Or, should the old functions be considered obsolete and just have them always return BadDevice? Any other ideas? + + +### XSetDeviceMode() and Motion Event Types + +This function assumes that devices can only emit relative or absolute events for all clients listening to the device. This probably should not be true for any device. Therefore, it may be reasonable to always return BadMode, which is the proper response for devices not supporting X![[SetDeviceMode|SetDeviceMode]] requests. + +The problem is that no other mechanism is defined to select relative versus absolute events. Therefore, it would probably be necessary to add RelativeMotionNotify and AbsoluteMotionNotify event types. It may also be acceptable to use the existing MotionNotify to handle Absolute events, which are more common. On the other hand, a new Absolute event type would also add an opportunity to support fractional motion events. + +Absolute events should also be better defined. Most drivers are pointer oriented, and consider absolute motion events to mean screen coordinates, rather than device coordinates. Perhaps Absolute events should always be in device coordinates, and only be converted to screen coordinates for core pointer events. Note that MotionEvents also send x_root and y_root, so clients will always get pointer coordinates. + +There are also some problems with the definition of Absolute versus Relative events. Many input devices send control data that is intended to be used for relative motion, even though the device state is actually an absolute position. For example, a centering joystick is intended to direct relative motion, but a non-centering joystick is accurately represented by an absolute position. Consider how you would would want to use these two joystick types to direct pointer motion. Although the control state is absolute in both cases, the data for the centering joystick should (arguably) be defined as Relative data, partly because the derivative is fairly useless but integrating from Relative to Absolute could be useful. + + +### XListInputDrivers() + +A device driver can be automatically associated with a device, depending on the device type, or otherwise controlled at the OS level. However, it may be useful to allow some client control, especially if more than one driver can handle the same device. + +Get a list of available device drivers; information format not yet defined. It is probably useful to include information about supported hardware, but that can be quite complex. Perhaps just a list of driver names and versions is sufficient. + + +### XAddInputDriver(), XRemoveInputDriver() + +Just an idea for now: Should it be possible to add/remove drivers in a running server? If so, should it be managed by a formal X event, or should this be managed simply by adding or removing driver binaries from the module directory? + + +### XAddInputDevice(), XRemoveInputDevice() + +These functions add or remove a device instance from the server. These are similar to the internal dix functions AddInputDevice() and RemoveDevice(). + +In the current server design, a newly added device but uninitialized device is in the **`off_devices`** list, and not available in X![[ListInputDevices|ListInputDevices]](). Before the device is initialized and made available to clients, it needs to be configured, presumably by the client that sent the request to add the device. Here are possibilities for handling the initial configuration. + +1. X![[AddInputDevice|AddInputDevice]]() can include as an argument a complete array of configuration directives. +1. The initial state of the new device can be as Grabbed by the requesting client, which can release the Grab when it decides the device is ready for use. +The **`off_devices`** list may be considered an obsolete feature when proper hotplugging is implemented. However, there are a few cases where it may still be useful. First, if a device fails initialization, it remains in the **`off_devices`** list. The list could be used to give devices another opportunity to attempt initialization. Secondly, if a device is opened by a client, but the hardware becomes unavailable, it may be useful to keep the **`off_devices`** instance around until all clients have closed the device. + +How does one get a list of the "off devices"? X![[ListInputDevices|ListInputDevices]]() has no option flags, so the current design would best handle this by listing all devices, and defining an DeviceInfo.use=IsOffline type. + + +### XEnableDevice(), XDisableDevice() + +These functions move a device from/to the off_devices list, and succeed depending on the result from the drivers response to DEVICE_INIT and DEVICE_CLOSE. + + +## Proposed Additional XInput Data Structures + + +### Issues with Extended XEvents and Other Data Structures + +The XEvent structure was designed with a fixed size to simplify memory management. Events are passed to the client by passing an entire XEvent structure, rather than passing an event pointer. This limits possibilities for defining Event types with larger data sizes. + +One approach for handling large event types would be to include a data pointer in the XEvent structure. The extended data can be automatically freed by Xlib upon the next event retrieval. + +The [[ClassInfo|ClassInfo]] structures include a length element, which means that extending existing structures can be backwards compatible. The XDeviceInfo structure does not have a length field, so changes will be incompatible. However, a much more versatile approach to extended device properties is to support property attributes similar to window properties, and to leave much of the current data structures unchanged. + + +### XDeviceListChangeEvent + +A new event is added to XInput to notify clients that the device list has changed. + +The event structure could be similar to X![[ChangeDeviceNotifyEvent|ChangeDeviceNotifyEvent]], where the XID is identifies the lost or gained device. This would require an event for each lost or gained device, but could be useful for clients that only want to monitor the status of one device. + + +[[!format txt """ +typedef struct { + int type; + unsigned long serial; + Bool send_event; + Display *display; + Window window; /* Root Window, or unused ? */ + XID deviceid; /* ID of new or lost device */ + Time time; + int state; /* DeviceNew, DeviceLost. Maybe also: DeviceEnabled, DeviceDisabled? */ + } XDeviceListChangeEvent; +"""]] + +### XDeviceConfigureControl + +One possible solution for generalizing Device Controls. This uses existing XInput functions, with a generic, extensible control type: + + +[[!format txt """ +typedef struct { + XID control = DEVICE_CONFIGURE; + int length = sizeof(XDeviceConfigureControl); + Atom name; + int format; + unsigned char *value; + int length; +} XDeviceConfigureControl; +"""]] + +## Input Device Properties + + * This is a listing of generalized device properties to consider. These would be available via a DeviceControl function that returns a string given a parameter named by a string or associated Atom. === Device Description === + * UUID -- Unique ID for this device, which is valid outside of the current server context. What makes it unique is not defined here. It would be easy if all devices had a serial number. + * HardwareID -- Identifies the hardware connection (i.e. HAL/devfs name, network address:port, etc.) + * SerialNumber -- embedded device serial number, when available + * Name -- Some sort of short 'friendly' name unique on the server (Mouse0, Keyboard0) + * Description -- A verbose device description + * VendorName -- Vendor name + * ProductName -- Product name + * ProductRevision -- Product version + * UserName -- Identify who is using the device, if it is Grabbed. +It may be good to always include numeric product and vendor ID's, to avoid ambiguities for cases where names are unknown, or have changed. Should these be a separate field, or grouped with the text name? In addition to user name, devices should probably include support for security (authentication, access-control) features. + + * === Device Event Properties === + * Valuator properties (partly based on HID): + * Relative / Absolute + * Preferred State (Auto-Center valuators and Momentary buttons) + * Wrap (or Periodic) + * Volatile (Value is settable) + * Units + * Minimum Value + * Maximum Value + * Granularity (Precision) + * Null Position (says if an input can have an "invalid" state) -- This property was invented to handle Hat switches, which can be idle, or pointing a direction. It is probably best to represent these as an X,Y valuator pair, or as a directional valuator and a 'valid' or 'active' button. === Other HID Properties === The following HID properties are not so useful for XClients, but might be needed for devices calibration, which should probably be handled by the X Client Input Device Manager: + * Logical (raw input) range + * Current Physical (event data) range + * Default Physical range + * Saturation (assuming the actual max-val may not be exact) === Linearity Properties === Non-linear input should probably be converted to linear at the server level. Acceleration is probably best handled by the server, with all devices set for linear output, in order to provide uniform acceleration parameters for all devices. (Q: Are there cases where acceleration at the device level is really an advantage?) + * Linear + * Unit Exponent + * Acceleration parameters, or point data for general line/curve + * Null radius +* = See Also = +* [[XInputHotplug|XInputHotplug]] +* [[XOrgInputDriverSpec|XOrgInputDriverSpec]] +* [[XHotplugProposal|XHotplugProposal]]
\ No newline at end of file diff --git a/XKB.mdwn b/XKB.mdwn new file mode 100644 index 00000000..353526f3 --- /dev/null +++ b/XKB.mdwn @@ -0,0 +1,25 @@ + + +## XKB - X Keyboard Extension + +The XKB data files for the various keyboard models, layouts, and locales are now maintained by [[the X Keyboard Config project on freedesktop.org|http://www.freedesktop.org/wiki/Software/XKeyboardConfig]] + +some helpful links: + +* [[The XKB Configuration Guide|http://www.x.org/releases/current/doc/xorg-docs/input/XKB-Config.html]] +* [[How to further Enhance XKB Configuration|http://www.x.org/releases/current/doc/xorg-docs/input/XKB-Enhancing.html]] +* en: [[http://pascal.tsu.ru/en/xkb/|http://pascal.tsu.ru/en/xkb/]] +* ru: [[http://pascal.tsu.ru/other/xkb/|http://pascal.tsu.ru/other/xkb/]] +* Patch XKB to support more than 128 keys: [[http://planet.gentoo.org/developers/flameeyes/2005/06/15/and_the_keyboard_lose_the_match|http://planet.gentoo.org/developers/flameeyes/2005/06/15/and_the_keyboard_lose_the_match]] +* [[RMLVO keyboard configuration|http://who-t.blogspot.com/2008/09/rmlvo-keyboard-configuration.html]] (rules, models, layouts, variants and options) +* [[Creating custom keyboard layouts for X11 using XKB|http://hektor.umcs.lublin.pl/~mikosmul/computing/articles/custom-keyboard-layouts-xkb.html]] +* [[An Unreliable Guide to XKB Configuration|http://www.charvolant.org/~doug/xkb/html/index.html]] +* [[XKB Layout Creation Notes|XKBLayoutCreationNotes]] +The original XKB extension protocol and library specs are available in several formats: + +* [[Original XKB specifications in FrameMaker format, as previously found in the xorg-docs module in git|http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/specs/XKB?id=XORG-7_0]] +* [[Original XKB specifications from X11R6.4 in PostScript & PDF|http://www.x.org/docs/XKB/]] +* [[XKB libX11 API documentation in HTML, generated from current DocBook sources|http://www.x.org/releases/current/doc/libX11/XKB/xkblib.html]] +* [[XKB protocol specification in HTML, generated from current DocBook sources|http://www.x.org/releases/current/doc/kbproto/xkbproto.html]] +* [[XKB libX11 API documentation in PDF 1.4, generated from current DocBook sources|http://www.x.org/releases/current/doc/libX11/XKB/xkblib.pdf]] +* [[XKB protocol specification in PDF 1.4, generated from current DocBook sources|http://www.x.org/releases/current/doc/kbproto/xkbproto.pdf]]
\ No newline at end of file diff --git a/XOrgInputDriverSpec.mdwn b/XOrgInputDriverSpec.mdwn new file mode 100644 index 00000000..754e7a88 --- /dev/null +++ b/XOrgInputDriverSpec.mdwn @@ -0,0 +1,108 @@ + + +# XOrg Input Driver Specifications (Incomplete Proposal) + + +## Table of Contents + +[[!toc ]] + + +## Introduction + +This page is intended as a place to evolve the design specifications for XInput device drivers in the XOrg server. Most of this document is not based on the existing server code. Instead, this is mostly a proposal of a new and improved design that is more consistent with DIX. Therefore, comments and suggestions from other device driver programmers is important. + +The modular driver design introduced in XFree86 4.0 is documented and designed primarily for video display hardware. It is also used for input devices, but the functions needed for video and input devices are not always equivalent, and the design has been independently mis-translated in many input device drivers. As a result, the driver sources inherited from XFree86 are a very inconsistent. + +One important consideration left out of the XInput driver design (and the video driver design as well) is propoer sharing of devices with other servers or terminals on the same VT console. + +Another feature that has been neglected is the use of the deviceControl() functions intended to be the primary control point for XInput drivers, as documented in the Xi docs and implemented in DIX. It is a well defined, clean design, and should be used. In fact, the same design could be ported to the video drivers as well, to provide a uniform driver design that is (arguably) better than the current design. + + +## Virtual Core Devices + +Many issues arise from core devices being different from extension input devices. An excellent solution, implemented in the IRIX server, is to use virtual core devices. In this design, the core keyboard and mouse are virtual devices, and cannot be changed. + +Virtual core devices are always available, but produce no independent events. All events come from extension devices. This is an excellent fit to a server that supports multiple core devices and device hot-plugging. With the recent integration of MPX, multiple virtual core devices may exist. They are also referred to as master devices. + +The master devices are designed to provide core events in a range that matches the Display resolution. At the same time, they also generate events that are in the device-specific resolution (if applicable). Clients that register for XInput Extension events, will receive events in this native resolution. Clients that open physical devices ("slave devices") directly and register for events do not receive core events. A slave device cannot generate core events. + +The server starts up with two master devices, which are always present. This makes it possible for the external hotplug agent to assign all input devices, and provides a clean method for running a server with no input devices. It also provides a chance to clean up all of the core device code, and convert everything to a standard extension device driver. + +Any slave device may be "attached" to a master device. In this case, when the slave device generates an event, this event is processed both by the slave device and by the respective master device. This device dependency is referred to as Master-Slave Device Hierarchy, and all slave devices attached to a master device control the master's cursor/keyboard focus. If a slave device is not attached to master device, it is referred to as "floating". It cannot generate core events and clients have to explicitly open the device and register for events. This is discouraged except in special circumstances (i.e. mapping the whole device to the canvas in the GIMP). Internally, floating slave devices control their own cursor sprite but this sprite is not rendered to the screen. + + +## HID Protocol Features + +The HID design is a verbose and inflexible, rather than a simple but extensible design. This does not really fit the overall X design concept very well, so it does not make sense to incorporate the actual HID protocol into X. However, it does make sense to use HID within the input drivers. Any HID information sent to the server from drivers should be in the form of Atoms (or strings) rather than HID enums. + +One meaningful use for HID is the Device and Control Usage tables. XInput supports a type Atom for Devices, which should be defined to match HID Usage names where possible. These already match names typically used in X: + +HID Usage tables would also be useful to define a type Atom for each input control of a device, but the XInput spec needs to be updated in order to support Control types. + + +## Device initialization functions + +These come in two different kinds. The functions defined in the driver (the XF86ModuleData and the registered InputDriverRec structures) and the deviceControl(DeviceIntPtr pdev, int action) function. The latter not to be confused with X![[ChangeDeviceControl|ChangeDeviceControl]](), it is referred to as deviceProc() in the XInput documentation and is the primary control point to input devices in the sample server DIX code. + +The core server design has always included a central deviceControl() function for each input device. Aside from the fact that the currently evolved input driver design is completely mangled, Main.[[JoeKrahn|JoeKrahn]] thinks that the originally documented design is better, and in fact could easly be applied to video devices as well. + +Here are the current modular driver functions defined for input drivers: + + +### ModuleSetupProc() + +This is where a driver initializes itself and is part of the module loading process, thus it's per-driver, not per-device. Device instances are initialized later, so this function should never attempt to access any hardware. + +The xf86AddInputDriver() function must be called with the InputDriverRec for the driver as one argument to register the driver and making it available to create instances of. The return value must be non-NULL if the driver should successfully be initialized. + + +### PreInit() + +**Device side:** Allocates all the resources for the device the driver needs. Should not access the hardware yet. Must call xf86AllocateInput() to allocate the device-struct that is returned. This is a good place to check/verify parameters and initialize structures for the device. An option with the key "_source" will be in the provided option list if called as a result of a hot-plug request.** ** + +**Server side:** If function returns a pointer to an InputInfoRec but haven't set XI86_CONFIGURED, UnInit() is called if defined. If not, xf86DeleteInput() is called to make some kind of cleanup. For devices that should be hot pluggable the UnInit() function is required if there shouldn't be any resource leaks. + + +### DEVICE_INIT + +**Device side:** Additional initialization/resource allocation for the device. Should avoid to access the hardware, but if accessing the device is the only way of getting specific device parameters the device can be opened. The appropriate Init*ClassDeviceStruct() functions should be called here to initialize the input device structure. + +**Server side:** If the function return anything but _Success_ the device can not be used. DEVICE_ON will never be called. It will however be listed as an extension device in X, thus making it visible, but not available. + + +### DEVICE_ON + +**Device side:** Opens the underlying device and should restore the device to a known state, based on the config, or from the state saved at the lst DEVICE_OFF. Should call xf86AddEnabledDevice() to add the FD to the ones monitored by the event loop. It is called when adding an input device or switching to the VT. + +** Server side:** Only if the function return _Success_ the server will call DEVICE_OFF at a VT-switch. + + +### DEVICE_OFF + +**Device side:** Called when switching away from the VT. Drivers should save the device state, if applicable, and close the device port. Should call xf86RemoveEnabledDevice() first to stop the event loop from monitoring the FD. + +**Server side:** This function will only be called if the DEVICE_ON returned _Success_. + + +### DEVICE_CLOSE + +**Device side:** Deallocation of the resources allocated in DEVICE_INIT. This is sent when a device instance is to be removed from the server. Before this is called, any long-term storage of device state information, such as touch-screen calibration, should be retrieved by client code (i.e. a HotPlug agent) and not by the device driver. + +**Server side:** Will be called without prior call to DEVICE_OFF when a remove request is received. Not called if DEVICE_INIT returned anything but _Success_. + + +### UnInit() + +**Device side:** Deallocates all recources allocated in PreInit(). xf86DeleteInput() should be called to free the device-struct allocated in PreInit(). + +**Server side:** If the function is not defined, xf86DeleteInput() will be called instead. But that will most likely result in a memory leak as no device-private structures will be deallocated. + + +### ModuleTearDownProc() + +This function is called when the driver is about to be unloaded from memory and should free all resources allocated in ModuleSetupProc(). The argument to this function is the same as returned from ModuleSetupProc(). xf86DeleteInputDriver() must be called to remove the module from the list of available modules. + +-- Main.[[JoeKrahn|JoeKrahn]] - 10 Jul 2004 + +-- Main.[[MagnusVigerlof|MagnusVigerlof]] - 07 May 2007 diff --git a/XServer.mdwn b/XServer.mdwn new file mode 100644 index 00000000..fbbf66fd --- /dev/null +++ b/XServer.mdwn @@ -0,0 +1,154 @@ + + +# X Server Module + +Here's a list of other X server related wiki pages + +* [[XorgModuleABIVersions|XorgModuleABIVersions]] + +## X server branches + +* [[Server12Branch|Server12Branch]] +* [[Server13Branch|Server13Branch]] +* [[Server14Branch|Server14Branch]] +* [[Server15Branch|Server15Branch]] +* [[Server16Branch|Server16Branch]] +* [[Server17Branch|Server17Branch]] +* [[Server18Branch|Server18Branch]] +* [[Server19Branch|Server19Branch]] +* [[Server110Branch|Server110Branch]] +* [[Server113Branch|Server113Branch]] +A guideline for what stable branch maintainers need to do is [[here|Development/Documentation/XServerStableBranchManagement]] + + +## Development Process + +Beginning with [[Server 1.8|Server18Branch]], we have [[changed our development process.|http://lists.freedesktop.org/archives/xorg-devel/2009-September/002330.html]] Below are instructions on how to test and develop on the X server. For stable releases, please refer to the appropriate wiki site (e.g. [[Server113Branch|Server113Branch]]) + +The development process is split into three stages: + +* feature merge window: Starts after the release of the previous version. Features ready will be merged, the server may be unstable during this time. +* bugfix window: No new features may be merged, only bugfixes and stabilization work is permitted. +* release freeze: Only bug fixes to go into the pending release may be merged. +The relevant dates are noted on each server branch page and in the [[X.Org Calendar|http://www.google.com/calendar/embed?src=nl1n1fmvu091eqh35ldqspar80%40group.calendar.google.com&ctz=Australia/Brisbane]]. + + +### General information + +The development process is now more distributed than it used to be in the past. To explain the process, the following terms are important: + +* **remote**: a repository you cloned from. +* **master**: the master branch on git.freedesktop.org. This branch will eventually become the new X server. The master branch is in the hands of the release manager. If you are familiar with the kernel development style, think of master being Linus' tree. +* **personal tree**: a git tree a maintainer has on people.freedesktop.org. These trees are merged into master. A list of these trees are available at [[PersonalTrees|PersonalTrees]]. A personal tree may have multiple branches, only one of which will be merged back to master. See feature branch and devel branch. +* **feature branch**: a branch on a personal tree devoted to a particular new feature. These feature branches are in development until the feature is deemed ready. Once ready, it can be merged into master during the next feature merge window. +* **devel branch**: a branch on a personal tree devoted to live development. +* **rebasing**: rebasing means using git rebase to change the patch order. Rebasing changes the history and should not be used for any published branch. You are only allowed to rebase local patches not yet pushed or patches you applied with git am (e.g. from a mailing list). If you rebase a branch that has been published and possibly already pulled, you destroy all history and screw everyone downstream from you. +* **fast-forward/non-fast-forward**: once you clone a git repository, you have the same history as the remote repository. If the remote gets updated by adding commits and you pull from it, you have a fast-forward change. If the remote however rewrites its history (using git rebase), this is a so-called non-fast-forward change. The history has been rewritten and your local copy does not share the same history anymore. Non-fast-forwards are generally discouraged for any public branch. + +### Users and Testers + +Decide what you want to test. This depends on your personal git and development skills but also in what you expect to get from testing. + +If you just want to test the X server in general, the master branch is probably the best for you. The master branch has many temporary patches already pre-tested and thus provides the most stable solution. Master will always be a bit behind the personal trees. + +If you are interested in testing particular subsystems, find the maintainer of that subsystem by browsing the [[PersonalTrees|PersonalTrees]]. Now you have the choice of testing that tree's master branch (more stable, but not as up-to-date) or one of the tree-specific feature branches. + +Testing feature branches means you're at the forefront of development and you help us most by catching bugs early. You can test new, unreleased features, features that may not appear in a released server for another year or even longer. + +Testing a development branch means you can help out the developer by pointing out broken patches. Development branches require some involvement with the developers (otherwise how will you tell them a patch is broken?). If you catch a bug early enough, the developer will rewrite the patch and thus change the remote's history. Thus, development branches are are often non-fast-forward. + + +### Developers + +If you are a developer with no public trees, choose how you want to help out by selecting the appropriate branch to test. Note that it is easy to switch between multiple remotes and branches so you're not bound to a single one. + +Aside from this, the process for you hasn't changed a lot: commit the patch locally, test and send the patch (see [[SubmittingPatches|Development/Documentation/SubmittingPatches]] for some more information) to the xorg-devel list (and/or the maintainer). Keep rebasing regularly from your chosen remote (git pull --rebase). + +The [[MAINTAINERS|http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/MAINTAINERS]] file has a list of maintainers for a given subsystem. In addition, ajax volunteered to scoop up dangling patches. If your patch isn't picked up in a reasonable time, don't hesitate to ping the list or the maintainer. + + +### Maintainers + +You are a maintainer if you have a public branch on people.freedesktop. Such a branch is recommended over sending patches one-by-one to the release manager as you will have control over the patches at all times (until the pull request), the patches will see better testing and past experience indicates that pull requests are processed by Keith with a higher priority than patches. + +First, setup up the repository (we're assuming your freedesktop.org username is bond007). + + +[[!format txt """ +$> git clone git://anongit.freedesktop.org/git/xorg/xserver +$> cd xserver +$> ssh bond007@annarchy.freedesktop.org +annarchy $> mkdir xserver.git +annarchy $> cd xserver.git +annarchy $> GIT_DIR=. git init +annarchy $> touch git-daemon-export-ok +annarchy $> vim description +annarchy $> exit +$> git remote add bond007 git+ssh://bond007@people.freedesktop.org/~bond007/xserver.git +$> git push bond007 master +"""]] +Congratulations, you now have a public master branch in your home directory on freedesktop.org. Add it to the the [[PersonalTrees|PersonalTrees]] list so testers know when and why to pick your tree. For this part, we'll assume your master branch is the branch that's supposed to be merged to git master. + +Note that the "bond007" bit in the git remote command is an arbitrary identifier. You can name it "fdo" (for freedesktop.org), after your username, or after your favourite color. The important thing is that you remember what git push bond007 means when you run it (i.e. where you're pushing to). + + +#### Scooping up patches + +Scoop up patches from the list that apply to your area of work when you've reviewed them. Simply pipe the patch into "git am -s" should do in most cases. Let the developer know that you've scooped it up, it saves others from doing the same. If there are multiple ACKs or Reviewed-by on the list, please add them to the patch so we have a record of who looked at the patch. It doesn't have to be a perfect record, remember that once you pushed your tree you can't amend the patches anymore, even if a late Reviewed-by comes in. + +Once you have scooped up a patch, push it to the matching branch in your personal repository. A simple git push does in most cases but see below for more details. Hint: if you haven't synced with master for a while, it's better to rebase master before pushing. + + +#### Pushing to your personal tree + +Syncing with master often is encouraged. This way, testers of your personal tree also test recent patches in master. Also, it's one way to keep testers as they are less inclined to switch to other branches if they get fixes from others soon enough anyway. To sync your personal tree, either pull or rebase from master. **You can only ever rebase if the last state of your personal tree has been pulled into master already.** Rebasing destroys history, so you can only ever do it when the history being destroyed is not public (i.e. only on your local box). + +If bond007/master has been pulled by the RM: +[[!format txt """ +$> git pull --rebase +$> git am -s <patches from list> +# test +$> git rebase -i origin/master # if you need to reshuffle something +$> git push bond007 master +"""]] +If bond007/master has **not** been pulled (e.g. you are accumulating a few patches before sending the pull request): +[[!format txt """ +$> git pull origin # if you need to sync with master +$> git am -s <patches from list> +# test +$> git rebase -i <merge commit from pull> # if you need to reshuffle something +$> git push bond007 master +"""]] + +#### Your own patches + +Your own patches follow the same process as others, send it to the list for review, then merge them accordingly once the Reviewed-by comes in. We should demand the same level of review from each other as from casual contributors. + + +#### Getting Patches and Pulls merged into master + +Again, you are encouraged to have your own branch on freedesktop.org. Once a patch has a Reviewed-by tag, pull this patch into your branch and at the appropriate time, push the branch to freedesktop.org and request a pull from the release manager. The pull must have a [PULL] in the subject line and make sure you Cc: the release manager in your email. For 1.9, the release manager is [[keithp@keithp.com|mailto:keithp@keithp.com]]. + +If a patch should be merged to master directly instead of going through a personal tree and a pull request, make sure you state so in the patch email and the release manager is on the CC list. + +Patches will not automatically be accepted; make sure there has been sufficient review, and that the reviewers have added their Reviewed-by: line to the commit message. Of course, patches may also be rejected for almost any other reason; the release manager is known to be somewhat arbitrary and capricious at times. + +Use [[git-request-pull|http://www.au.kernel.org/software/scm/git/docs/git-request-pull.html]] to get the standard email for a pull request. + + +[[!format txt """ +$> git request-pull 12345deadbeef git://people.freedesktop.org/~bond007/xserver.git +"""]] +Where 12345deadbeef refers to the last commit from the master branch. Pull requests (and patches in general) may get lost. If no reason for not pulling/applying has been given, poke the release manager again. + +There is no minimum number of patches for pull requests, a pull request for a single patch is fine. All patches included in a pull request should have a Reviewed-by line. + + +#### Development branches + +Developing intermediate patches are best done on a separate branch. This branch may be non-fast-forward if needed (document this for users!). The situation to avoid is that a number of patches have accumulated in your tree that need to be merged into master but there's other in-development patches that prevent it from being pulled. Keep ongoing work separate from the trees to be pulled. + + +### Patchwork + +The [[xorg patchwork|http://patchwork.freedesktop.org/project/Xorg/list/]] installation keeps track of patches. Note that to change the state of a patch in patchwork requires manual interaction, it does not get updated automatically as patches are pulled into the tree. diff --git a/XorgDeprecatedMailingLists.mdwn b/XorgDeprecatedMailingLists.mdwn new file mode 100644 index 00000000..579b1319 --- /dev/null +++ b/XorgDeprecatedMailingLists.mdwn @@ -0,0 +1,28 @@ + + +# Archives of X.Org Mailing Lists no longer in Use + + +## Development Lists + + +### Discussion Lists + + * [[xorg-modular|http://lists.freedesktop.org/archives/xorg-modular]]: Mailing list to discuss details of the **modularization project**. + * [[xorg-arch|http://lists.freedesktop.org/archives/xorg-arch]]: Mailing of the **Architecture Working Group**. + * [[xevie|http://lists.freedesktop.org/archives/xevie]]: Mailing list to discuss details on SUN's **X Event Interception Extension**. + +### Logging Lists + + * [[xorg-commit-diffs|http://lists.freedesktop.org/archives/xorg-commit-diffs]]: This mailing list was used to send the full diffs from CVS. Today those are sent to xorg-commit anyway... + * [[xorg-bugzilla-noise|http://lists.freedesktop.org/archives/xorg-bugzilla-noise]]: This Mailing list collected all tickets and comments added to the freedesktop.org bugzilla for the Xorg product. + +## Special Event Mailing Lists + + * [[Xdevconf|http://lists.freedesktop.org/archives/xdevconf/]]: Mailing list covering the periodic [[developers conference|http://freedesktop.org/bin/view/Software/XDevConf]]. + * [[xorg-fosdem|http://lists.freedesktop.org/archives/xorg-fosdem/]]: Mailing list covering X@FOSDEM2006. + * [[xds2007|http://lists.x.org/archives/xds2007/]]: Mailing list covering XDS 2007 in Cambridge, UK. + +## Miscellaneous Mailing Lists + + * [[xorg-mentors|http://lists.freedesktop.org/archives/xorg-mentors]]: Mailing list of the Mentorship Working Group.
\ No newline at end of file diff --git a/XorgDeveloperDocumentation.mdwn b/XorgDeveloperDocumentation.mdwn new file mode 100644 index 00000000..032057c5 --- /dev/null +++ b/XorgDeveloperDocumentation.mdwn @@ -0,0 +1,31 @@ + + +## Documentation I Have Known And Loved + + +### Modern Texts + +More-or-less accurate descriptions of the way X works now. + +* The [[Cygwin/X developer site|http://x.cygwin.com/devel/]] has many useful bits. +* The [[DRI|http://dri.freedesktop.org/wiki/Documentation]] documentation. Mostly still applicable! +* XFree86 DDX documentation: + * [[DESIGN|http://www.x.org/releases/current/doc/xorg-server/ddxDesign.html]] doc. + * [[Multi-monitor Mode Setting APIs|http://cgit.freedesktop.org/xorg/xserver/tree/hw/xfree86/doc/README.modes]] + * Additional [[XFree86 DDX developer documents|http://cgit.freedesktop.org/xorg/xserver/tree/hw/xfree86/doc/]] +* The [[protocol & API specifications for the latest X11 katamari release|http://www.x.org/releases/current/doc/]], covering pretty much everything. + +### Ancient Scrolls + +A miscellaneous collection of documentation surrounding the technical side of X, in particular what it gets wrong and the way it's been implemented in the past. Those who do not learn from history are doomed to reinvent it. + +* _[[An LBX Postmortem|http://keithp.com/~keithp/talks/lbxpost/index.html]]_. Packard, 2001. +* _Component Design Specification for the MIT Multi-Threaded X Window Sample Server_. Haynes, et al., 1993. Available in three parts from the R6.0 source, mirrored [[here|http://people.freedesktop.org/~ajax/mtx/]]. Consider this a warning about how not to multithread an X server. +* _[[D11: a high-performance, protocol-optional, transport-optional window system with X11 compatibility and semantics|http://citeseer.ist.psu.edu/kilgard95highperformance.html]]_. Kilgard, 1995. +* _[[The Evolution of the X Server Architecture|http://keithp.com/~keithp/talks/Xarchitecture/Talk.htm]]_. Packard, 1999. +* _[[Why X Is Not Our Ideal Window System|http://www.std.org/~msm/common/protocol.pdf]]_. Gajewska, et al., 1990. +* _[[X Server Multi-rendering for OpenGL and PEX|http://citeseer.ist.psu.edu/kilgard94server.html]]_. Kilgard, et. al, 1994. Be glad you don't have to care about PEX anymore. + +## See Also + +* [[DevelopersPages|DevelopersPages]].
\ No newline at end of file diff --git a/XorgEVoC.mdwn b/XorgEVoC.mdwn new file mode 100644 index 00000000..cf4950ab --- /dev/null +++ b/XorgEVoC.mdwn @@ -0,0 +1,26 @@ + + +# The X.Org Endless Vacation of Code (EVoC) + +For the last several years, X.Org was a participating mentoring organization in Google's most excellent [[Summer of Code|http://code.google.com/soc]] (GSoC) program. This program provides approximately US$5000 to students to spend their summer developing code for an open source project. Each student proposes a project and is matched with an organization mentor who guides and evaluates the work. GSoC was great for X.Org; we saw more than a dozen students through it, and some of these students went on to be extremely active contributors to X.Org. + +However, for whatever reason some students with good project proposals who would like to participate in GSoC have been unable to do so. Typically, this was because Google funded fewer high-quality GSoC proposals than we had available in a given year, or because the rigid timing of GSoC was entirely incompatible with a student's calendar. In any case, it is now moot: X.Org is now no longer part of Google Summer of Code. + +Rather than lose out on getting students working on X, the X.Org Foundation Board voted in 2008 to initiate a program known as the X.Org Endless Vacation of Code (EVoC) program. The basic terms and conditions of this program are quite similar to Google's GSoC. The key differences are that (1) an EVoC mentorship can be initiated at any time during the calendar year, and (2) the Board can fund as many of these mentorships as it sees fit. We will also consider a broader range of proposals than GSoC: technical documentation is a specific area of interest for us. + +A proposal will typically be for a period of three to four months of contiguous nearly-full-time work, and will be funded at the US$5000-$6000 level, with an initial payment and further payments upon completion of project milestones. The proposal should include a detailed proposed scope of work and schedule; see the [[X.Org GSoC|http://www.x.org/wiki/X.Org-GSoC2008-Application]] page for more information about writing successful proposals. Proposals must acquire a lead mentor from the X.Org technical community in order to be accepted; if the student can help identify this person early, that will increase their chance of success. + +Non-students may also participate in EVoC. Application and participation for non-students is the same as for students, with one exception: non-students will not be paid. The X.Org Foundation believes that paying non-students to help develop X leads to a variety of problems, not least of which is complicating the non-profit status of the Foundation. For EVoC purposes, a student is someone who is a half-time or more college or university student during, immediately before or immediately after their EVoC period. Secondary school students 18 years of age or older are also eligible; sadly, it is legally complicated to pay younger students. + +Students are welcome to either come up with an idea on their own or work up a proposal for an idea suggested by someone else. Lists of ideas that existing developers have come up with can be found at [[Todo|http://www.x.org/wiki/ToDo]] and [[Ideas|http://www.x.org/wiki/SummerOfCodeIdeas]]. + +Hanging out on the irc channels (listed below) and talking with people there is an excellent way to flush out ideas and/or possible mentors. + +Students need to have at least a basic understanding of the following: + +* mailing lists +* irc (graphics developers use irc.freenode.net #xorg-devel,#xorg, #dri-devel, #nouveau and #wayland to name a few.) +* gcc +* git +* Be comfortable using a linux shell and command line +At the current time, X.Org Foundation member Matt Dew marcoz AT osource DOT org is the contact person for X.Org EVoC. All inquiries should be emailed to him, with a cc to board AT foundation DOT x DOT org. diff --git a/XorgFoundation.mdwn b/XorgFoundation.mdwn new file mode 100644 index 00000000..9565d339 --- /dev/null +++ b/XorgFoundation.mdwn @@ -0,0 +1,14 @@ + + +### About the X.Org Foundation. + +X.Org Foundation (or X.Org for short) is a company chartered to develop and execute effective strategies that provide worldwide stewardship and encouragement of the X Window System and related projects (Mesa, DRI, Wayland, etc.). The X.Org Foundation has an open membership, and a Board of Directors which is elected from the membership. Please check the [[BoardOfDirectors|BoardOfDirectors]] page for information about the Board. Information on how to join the X.Org Foundation can be found on the [[Membership|Membership]] page. + + +### Why X.Org Foundation? + +In a period between close to the end of 2003 and beginning of 2004, there were attempts from leading XFree86.org project members to apply a few restrictions on the existing 1.0 license of the upcoming XFree86 X4.4.0 release. Since not all (developers, distributors, hardware vendors) were able or willing to agree with and implement that new licensing policy in their code, their development process and their products, they consequently split up and rejoined in the form of the X.org Foundation. + +As a base for their future works, they took one of the last code snippets covered by the old license and joined that with the still existing and freely available codebase from X.org. Further taking responsibility for the contents in the x.org domain made them the de-facto successor of [[XConsortium|XConsortium]]. With their accumulated development power and their joint efforts, there were already two major releases and a patch-level release in 2004, a second patch-level release in early 2005, and major releases each year since. A current summary of the state of the foundation can be found in the most recent [[Annual Report|XorgFoundation/Reports/]]. + +Details on any major X Windows Release can be located through the [[Releases|XorgReleases]] page. The Foundation provides [[funding|XorgFunding]] for various kinds of activities that advance X.Org, most notably [[student development|XorgEVoC]] and [[workshops and meetings|XorgWorkshops]]. Traditional contracting for X Window System development is explicitly not funded by the Foundation, among whose purposes is to encourage development by volunteers. diff --git a/XorgFoundation/Reports.mdwn b/XorgFoundation/Reports.mdwn new file mode 100644 index 00000000..ec99b49b --- /dev/null +++ b/XorgFoundation/Reports.mdwn @@ -0,0 +1,6 @@ + + +### X.Org Foundation Annual Reports + +* [[2010|XorgFoundation/Reports/2010]] +* [[2013|XorgFoundation/Reports/2013]]
\ No newline at end of file diff --git a/XorgFoundation/Reports/2010.mdwn b/XorgFoundation/Reports/2010.mdwn new file mode 100644 index 00000000..7868b5ac --- /dev/null +++ b/XorgFoundation/Reports/2010.mdwn @@ -0,0 +1,76 @@ + +_Converted to wiki form from original report at [[http://foundation.x.org/pipermail/members/2010-February/000550.html|http://foundation.x.org/pipermail/members/2010-February/000550.html]] _ + + +# The State of The X.Org Foundation 2010 + +Bart Massey + +Secretary, [[X.Org Foundation|XorgFoundation]] + +February 20, 2010 + +_Abstract:_ 2009 has been a year of consolidation for X.Org. Software is now being released on a predictable schedule, with predictable improvement. + +_Note:_ The Bylaws of the X.Org Foundation require the Secretary to prepare and deliver a State of the Organization report within 60 days of the start of the calendar year. It is my pleasure to discharge that responsibility by preparing this report. While I have prepared this report in close consultation with the X.Org Foundation [[Board of Directors|BoardOfDirectors]], all views contained herein are ultimately my own. + + +## Introduction + +Six years ago, the X.Org Foundation was re-formed and its first officers elected. Since then, approximately one X Window System major release has occurred per year. The mission of the modern X.Org Foundation Board is to support this work through raising and allocation of funds, through recruitment and support of Foundation members, and through initiatives in community development, education, and support, and by providing a computing and communications infrastructure; in short "to develop and execute effective strategies that provide worldwide stewardship of the X Window System technology and standards." [ [[1|http://www.x.org/wiki/XorgFoundation]] ] + +In the next two sections of this report, I first review X.Org Foundation activities during 2009 and report on our successes and challenges; I then suggest something of the goals, needs, and plans for the future of the X.Org Foundation in 2010 and beyond. Finally, I draw some conclusions. + + +## X.Org Foundation 2009 + +In 2009 X.Org development proceeded at a steady and reasonable pace. The Foundation did not make major changes in operation in 2009. + + +### Development + +In keeping with the X.Org goal of about one release per year, [[Release 7.5 of the X Window System|Releases/7.5]] occurred on October 26, 2009. This release featured the first official version of Multi-Pointer X, "E-EDID support", improved pointer acceleration, an XACE-based SELinux security module, and RandR version 1.3. It also included the kernel modesetting support developed over the last several years, with the goal of moving parts of X better handled by the host operating system into it. + + +### Funded Activities + +Based on the limited ability to raise funds in the 2009 economic climate, and on the limited capacity of conference organizers, the decision was made in early 2009 to cut back from two conference events per year to just one. The Board felt that alternating between North America and elsewhere on alternate years would provide sufficient developer contact worldwide, while cutting costs even when extra travel subsidies were taken into account. This appears to have been a correct decision. + +The [[2009 X Developers Conference|Events/XDC2009]] was held in Portland, Oregon September 28-30, immediately following the Linux Plumbers Conference there. The conference emphasis was on smaller projects and preliminary work; there was no strong unifying topic. The [[2010 X.Org Developers Summit|Events/XDS2010]] is planned for 16-18 September in Toulouse, France. Discussion is proceeding on possibly holding the 2011 X.Org Developers Conference in conjunction with BOSSA in Brazil. + +The Google/X.Org Summer of Code 2009 was successful, with three of four accepted projects completing and contributing to X.Org development, as well as helping to bring new developers to X.Org [ [[2|http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/xorg]] ]. The [[X.Org Endless Vacation of Code|XorgEVoC]] was established in 2009 to provide opportunities similar to Summer of Code to selected students on an ad hoc calendar. Only a couple of students have shown interest to date, and the one student that submitted an accepted proposal later withdrew. This is probably due to the lack of promotion of the program. + +The X.Org Foundation funded a video hackfest held at the Collabora offices in Barcelona in November. The event was reportedly highly successful [ [[3|http://lists.freedesktop.org/archives/xorg/2009-November/048182.html]] ], and was held at a modest cost. It is hoped that other X.Org projects will take this example to heart and seek funding help when needed. + + +### Foundation Activities + +The Board had hoped to complete the legal transition of the X.Org Foundation from a US LLC to a US 501(c)3 Educational Non-Profit Foundation in the first few months of 2008. A large number of delays culminated in the completion of this transition in early 2009, when the State of Delaware granted us corporate status. However, it turns out that some IRS documents still need to be filed by the Treasurer. This work is underway. + +The 2009 Board election was once again delayed, and completed in mid-February 2010. This is unfortunate, and further work needs to be done to ensure that the 2010 and ongoing elections can be held in a timely and regular manner. This election was the first in quite a while in which the restriction in the X.Org Bylaws that only two people from a given organization can be on the Board simultaneously was an issue. The issue was resolved by Keith Packard stepping down from the Board, leaving only two Intel representatives. + +The attempt to improve coordination and throughput of the Board continued in 2010. The Board established a wiki that it experimented with as an internal communication mechanism, but it saw only modest use. The regular bi-weekly IRC meetings begun in 2008 continue to date, and e-mail continues to play a crucial role. + +Membership in the Foundation is currently at about 145 active members. Work continues on encouraging X.Org participants to join the Foundation. + +Communication between the Board and the Membership has continued to be an issue in 2009, culminating in a bit of drama during the 2010 Board election. As a result of this, I am stepping down as Secretary, in the hope that someone else on the Board can do a better job of facilitating this communication. + + +## 2010 And Beyond + +No substantial work was done in 2009 in finding recurring sponsors for X.Org as a whole, although conference sponsorships and other kinds of directed sponsorships were strong. Many on the Board still believe that this may be the future of funding for the organization, but funding options undoubtedly will be explored again in 2010. + +Good improvements have been made in the X.Org / Freedesktop.org shared infrastructure, in particular more sysadmin support. Emphasis for 2010 will be on cutting infrastructure costs, and on continuing to improve infrastructure reliability and responsiveness. There was some work done in 2009 on expanding build and tinderbox facilities; this work will likely continue in 2010. Traffic volume and spam problems on the xorg email list and on X.org wikis became an issue in 2009. The wiki spam problem is particularly bad on auxiliary X.Org wikis that do not have the same amount of regular attention from their maintainers as the main X.Org site. After careful consideration, the Board failed to come up with any ideal resolution to these problems. + +The heavily-hacked legacy members.x.org PHP codebase has been increasingly a thorn in the side of conducting membership business, and is due for replacement. The Board should consider how to proceed on this issue as early as possible in 2010, with the goal of having the replacement in place and verified in time for the next Board election. + +Attempts were made to straighten out X.Org banking issues in 2009, but as of this writing the banking situation is mostly unchanged. + +There is ongoing concern among the Board about the trademark situation of X.Org. It is not at all obvious what trademarks, if any, are currently registered. There is also a friendly lack of consensus among the Board members about what needs to be registered; the various costs and benefits make for a complex engineering tradeoff. In 2010, this issue needs to be resolved one way or the other. As an ancillary issue, the question of what, if anything, to do about changing out the old X.Org "halo" logo should once again be considered. + + +## Conclusion + +The state of the X.Org Foundation is strong. The X Window System continues to succeed. + +Each year that I have prepared this report I have confidently predicted that the following year will be the Year of the Linux Desktop. However, I do not believe that 2010 will be the Year of the Linux Desktop, due to decreasing interest in desktops and laptops. I am quite sure that 2010 will be the Year of Mobile Linux. diff --git a/XorgHAL.mdwn b/XorgHAL.mdwn new file mode 100644 index 00000000..9356e0e5 --- /dev/null +++ b/XorgHAL.mdwn @@ -0,0 +1,29 @@ + + +# Xorg server and HAL + + +## Versions that use HAL + +Xorg versions 1.4 through 1.7 (and optionally later versions) use [[HAL|http://www.freedesktop.org/wiki/Software/hal]] for several things related to input devices: + +1. Finding input devices at startup +1. Being notified of input device hotplugging (arrival & removal) +1. Mapping system input devices to Xorg input driver modules (via .fdi files provided with Xorg input drivers) +1. Setting input device options (via user-customized .fdi files) +HAL is not used by Xorg for output devices or any other devices, only input. + + +## Versions that do not use HAL + +Since the HAL project has stopped development and deprecated itself, X.Org is planning to move off HAL in the future. Support for udev instead of HAL is available in X Servers 1.8 and later and enabled by default, pending platform availability. As HAL was also used for input device configuration, a new feature has been added to X Server 1.8 to support configuration snippets in the xorg.conf.d directory. Instead of udev rules, users and distributions are encouraged to use the xorg.conf.d for configuration. Old-style xorg.conf configuration is still available. + +[[https://fedoraproject.org/wiki/Input_device_configuration|https://fedoraproject.org/wiki/Input_device_configuration]] has instructions on how the new system works. + + +## Future Versions + +The currently planned replacements for the above functionality pieces are: + +1. Direct calls to OS-dependent device enumeration libraries (libudev on Linux, libdevinfo on Solaris, etc. - basically whatever HAL called to do this) +Neither [[DeviceKit|http://www.freedesktop.org/wiki/Software/DeviceKit]], nor the [[udisks|http://www.freedesktop.org/wiki/Software/udisks]]/upower/etc. replacements provide any of this functionality for input devices, and the [[DeviceKit|DeviceKit]] authors have indicated that they do not plan to provide such functionality, suggesting direct use of the OS interfaces such as libudev instead. diff --git a/XorgIRC.mdwn b/XorgIRC.mdwn new file mode 100644 index 00000000..ce320277 --- /dev/null +++ b/XorgIRC.mdwn @@ -0,0 +1,12 @@ + +Xorg hosts two channels on the [[freenode|http://freenode.net/]] IRC network: #xorg and #xorg-devel. #xorg is for general discussion and user support questions, and #xorg-devel is for development discussion. We ask that you respect a few rules and guidelines when using them. + +1. Don't ask to ask, just ask. +1. Be patient. IRC is variable-latency, and you may not always get a response immediately. +1. That said, please don't repaste the same question continuously just because three new people joined the channel. +1. Be prepared to supply your configuration file (almost always `/etc/X11/xorg.conf`) and log file (almost always `/var/log/Xorg.0.log`) on a paste site so we can help you troubleshoot. Two such sites are [[pastebin|http://pastebin.com]] and [[rafb|http://rafb.net/]]. +1. Stay on topic. In particular, don't re-ask support questions in #xorg-devel just because no one answered in #xorg. +1. Proprietary video driver support questions are off-topic. We didn't write them, we don't have the source, and we can't fix them. Use #ati or #nvidia as appropriate, even if those channels appear to be dead too. +1. For end-user support on the open-source radeon driver there is #radeon . For the open-source intel driver, there is [[#intel-gfx|http://intellinuxgraphics.org/feedback.html]] . +1. Have a look at the [[User FAQ|FAQ]] before asking +etc. diff --git a/XorgMailingLists.mdwn b/XorgMailingLists.mdwn new file mode 100644 index 00000000..d816c0e8 --- /dev/null +++ b/XorgMailingLists.mdwn @@ -0,0 +1,44 @@ + + +# X.Org's Mailing Lists + + +## Announcements + + * **[[xorg-announce|http://lists.freedesktop.org/mailman/listinfo/xorg-announce]]** is for announcements about Xorg releases and releases of related Xorg components. It is not a place for discussion. + +## Discussion Lists + + * **[[xorg|http://lists.freedesktop.org/mailman/listinfo/xorg]]** is for **general purpose discussions** and support questions. + * **[[xorg-devel|http://lists.x.org/mailman/listinfo/xorg-devel]]** is for development discussions. Patch review and development discussion can go there. + * **[[xorg-driver-ati|http://lists.freedesktop.org/mailman/listinfo/xorg-driver-ati]]** is for discussions on **ati driver** related issues. + * **[[x-packagers|http://lists.freedesktop.org/mailman/listinfo/x-packagers]]**: Discussions among people who are interested in **packaging X binaries** (mostly distro maintainers) + * **[[xorg-test|http://lists.freedesktop.org/mailman/listinfo/xorg-test]]** is the general discussion list of the **XTEST Project**. + * **[[Xcb|http://lists.freedesktop.org/mailman/listinfo/Xcb]]** is the general developers discussion list of the **Xcb Project**. + * **[[Nouveau|http://lists.freedesktop.org/mailman/listinfo/Nouveau]]** discusses the NVIDIA reverse engineering project **Nouveau**. + +## Logging Lists (not for posting) + + * The [[xorg-commit|http://lists.freedesktop.org/mailman/listinfo/xorg-commit]] mailing list archives commits to the xorg repository. + * The [[xorg-test-commit|http://lists.x.org/mailman/listinfo/xorg-test-commit]] mailing list archives commits to the XTEST Project repository. + * The [[xorg-team|http://lists.x.org/mailman/listinfo/xorg-team]] mailing list is where bugzilla sends notices about bugs filed against the xorg tree. + +### Other X related developers lists not directly part of the X.Org Foundation. + + * The [[xdg|http://lists.freedesktop.org/mailman/listinfo/xdg]] freedesktop standards and specifications mailing list. + * The [[XKB-Config project|http://www.freedesktop.org/wiki/Software/XKeyboardConfig/Development]] hosts a mailing list for discussion of XKB keyboard layouts and usage. + +## Other Lists + + * The [[xorg-europe|http://lists.freedesktop.org/mailman/listinfo/xorg-europe]] mailing list is to announce and discuss events and meetings in Europe. + +## Archives + + +### Mailing List Archives (Unofficial) + + * [[archive.netbsd.se|http://archive.netbsd.se/?cn=XOrg]], browse, search, RSS-feeds. + +### Deprecated Lists Archives + + * The archives of [[deprecated X.Org mailing lists|XorgDeprecatedMailingLists]] can be found here.
\ No newline at end of file diff --git a/XorgModuleABIVersions.mdwn b/XorgModuleABIVersions.mdwn new file mode 100644 index 00000000..f02c4268 --- /dev/null +++ b/XorgModuleABIVersions.mdwn @@ -0,0 +1,23 @@ + +The Xorg server includes version numbers for various ABI's for interfaces used by loadable modules such as drivers and extensions. + +This major number of the ABI version (_**x**_.*) is incremented when there are incompatible changes in module API/ABI's, while the minor number (*._**x**_) is incremented for compatible additions. + +Modules reporting they require a incompatible version number will not be loaded unless the `-ignoreABI` option is used. (Modules can also check ABI versions themselves, and choose which function variant to call or structure variant to access, based on the reported versions - this is the option used by some closed source drivers for instance.) + +ABI numbers may increment multiple times during Xorg server development cycles, to track changes for those following the head of the development stream. X.Org tries to avoid changing ABI's incompatibly in stable release branches. +[[!table header="no" class="mointable" data=""" + **Xorg Version: ** | **[[1.3|Server13Branch]] ** | **[[1.4|Server14Branch]]** | **[[1.5|Server15Branch]]** | **[[1.6|Server16Branch]]** | **[[1.7|Server17Branch]]** | **1.8** | **1.9** | **1.10** | **1.11** + ABI_ANSIC_VERSION | 0.3 | 0.3 | 0.4 | 0.4 | 0.4 | 0.4 | 0.4 | 0.4 | 0.4 + ABI_VIDEODRV_VERSION | 1.2 | 2.0 | 4.1 | 5.0 | 6.0 | 7.0 | 8.0 | 10.0 | 11.0 + ABI_XINPUT_VERSION | 0.7 | 2.0 | 2.1 | 4.0 | 7.0 | 9.0 | 11.0 | 12.2 | 13.0 + ABI_EXTENSION_VERSION | 0.3 | 0.3 | 1.1 | 2.0 | 2.0 | 3.0 | 4.0 | 5.0 | 5.0 + ABI_FONT_VERSION | 0.5 | 0.5 | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 +"""]] + + +## Input ABI policy + +Note: this is a guideline more so than a strict rule. + +The input ABI is bumped whenever an incompatible change is introduced to the server. This may happen several times during a development cycle. The goal of the ABI management is to allow the master branch of the various input drivers to compile when bisecting the server. If multiple changes to the server's ABI are required, these changes are usually accumulated and pushed in one merge. diff --git a/XorgReleases.mdwn b/XorgReleases.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/XorgReleases.mdwn diff --git a/XorgTesting.mdwn b/XorgTesting.mdwn new file mode 100644 index 00000000..05897dbc --- /dev/null +++ b/XorgTesting.mdwn @@ -0,0 +1,118 @@ + + +# The X.Org Foundation Testing Plan + + +## Detailed test instructions + +This section outlines the test procedure to follow when testing a release candidate. When a test run has been completed, please e-mail the [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]] mailing list with the following information so that we can track what has and has not yet been tested. Note that we are interested in progress: please do not wait to complete all phases of testing to send in reports. + + 1. Your Name + 1. The date tested + 1. The platform you tested: + * The operating system tested (e.g., AIX, Cygwin, FreeBSD, HP-UX, Linux, etc.) + * The architecture tested (e.g., Alpha, AMD64, EM64T, IA-32, IA-64, Sparc, etc.) + * The distribution and release tested (e.g., Red Hat FC2, SUSE 9.1, Debian unstable, Solaris 9, etc.) + 1. The snapshot or release candidate tag tested (e.g., XORG-6_7_99_1, etc.) + 1. Build test status: passed or failed or untested + 1. Install test status: passed or failed or untested + 1. Conformance test status: passed or failed or untested + 1. Run test status: passed or failed or untested + * List the tests run +For any test(s) that failed, please include in your report the test(s) that failed, and file a bugzilla report if no one has already filed one against the failure(s) you found. + + +### Build tests + +Each of the following build tests can be performed by copying the _sample_ host.def file (or the _alternate_) to the xc/config/cf directory and the running `make World >& World.LOG` (or other such command as appropriate for your platform), and then checking the World.LOG file for any failures. + + 1. Build with empty host.def file ([[sample|http://www.freedesktop.org/~kem/build-tests/1/host.def]] [[alternate|http://www.freedesktop.org/~kem/build-tests/1a/host.def]]) + 1. Build with [[BuildServersOnly|BuildServersOnly]] defined as YES ([[sample|http://www.freedesktop.org/~kem/build-tests/2/host.def]] [[alternate|http://www.freedesktop.org/~kem/build-tests/2a/host.def]]) + 1. Build with [[DoLoadableServer|DoLoadableServer]] defined as NO ([[sample|http://www.freedesktop.org/~kem/build-tests/3/host.def]] [[alternate|http://www.freedesktop.org/~kem/build-tests/3a/host.def]]) +Note that some systems do not have a compatible version of Freetype2 installed on their system, so in addition to each build requirement above, defining [[HasFreetype2|HasFreetype2]] as NO is permitted. Each _alternate_ host.def file above have this define included. + + +### Install tests + +Each of the following install tests can be performed by building the release (as described above using the _sample_ or _alternate_ host.def file provided), running `make Install >& Install.LOG` (or other such command as appropriate for your platform), and checking the Install.LOG output for any failures. + + 1. Build and install with no host.def file ([[sample|http://www.freedesktop.org/~kem/install-tests/1/host.def]] [[alternate|http://www.freedesktop.org/~kem/install-tests/1a/host.def]]) + 1. Build and install with: Project``Root defined to be something other than the default, and Nothing``Outside``Project``Root defined as YES ([[sample|http://www.freedesktop.org/~kem/install-tests/2/host.def]] [[alternate|http://www.freedesktop.org/~kem/install-tests/2a/host.def]]) +Note that some systems do not have a compatible version of Freetype2 installed on their system, so in addition to each install requirement above, defining Has``Freetype2 as NO is permitted. Each _alternate_ host.def file above have this define included. + + +### Conformance tests + +After installing the full release, the conformance tests can be run using the X test suite, which can be downloaded [[here|http://www.freedesktop.org/~kem/testing/xtest.tar.gz]]. A helper script (called ``xreg``) is used to run the X test suite, which can be downloaded [[here|http://www.freedesktop.org/~kem/testing/xreg]]. See the next two sections below for more information on how to setup and use these tools. + + +#### Setting up the X test suite + +Here are some brief instructions on how to download and set up everything that you will need to run the X test suite: + + 1. Follow the directions at [[BuildingXtest|BuildingXtest]] + 1. `wget http://www.freedesktop.org/~kem/testing/xreg` +Now you should be ready to begin testing. + + +#### Examples of how to use the xreg script + +Here are some examples of how to use xreg to run the X test suite: + + 1. `xreg -xtest -xvfb` + * This runs xtest at all default depths using the Xvfb server. + * The default depths are 8, 15, 16, and 24+32. + * The "24+32" depth is one that uses a depth of 24 with a frame buffer bits per pixel of 32 (i.e., -depth 24 -fbbpp 32). + 1. `xreg -xtest -xorg -d 16` + * This runs xtest at depth 16 using the Xorg server. + 1. `xreg -xtest -xvfb -d 15 -test XCopyArea` + * This runs xtest at depth 15 using the Xvfb server, but it only runs the XCopy``Area test. + * Selecting individual tests is very useful to track down test failures. + 1. `xreg -xtest -xvfb -d 16 -xvfbwidth 1280 -xvfbheight 1024 -test XFillRectangles -n 3-5` + * This runs xtest at depth 16 using the Xvfb server running at 1280x1024, but only runs the third through the fifth tests of the XFill``Rectangles test. +Notes on using xreg: + + * The output from these test runs are stored in `pwd`/results by default. You can change the default output dir using the -O command line option. + * The material below assumes that you have done a full install of the system to /usr/X11``R6. However, if you are using a different Project``Root, you can use the following command line option to the xreg script to run from that alternate location: `-projroot` _path-to-your-project-root_ + * The files that are generated from an xreg run of xtest are: + 1. `X-setup..output` -- this file contains the output of the X server during the setup phase + 1. `xtest.DEPTH.DATE.TIME.errors` -- this file contains the list of errors found during the test run at depth _DEPTH_ made on date _DATE_ at time _TIME_. + 1. `xtest.DEPTH.DATE.TIME.report` -- this file contains the report of all tests run at depth _DEPTH_ made on date _DATE_ at time _TIME_. + 1. `xtest.DEPTH.DATE.TIME.summary` -- this file contains a summary of the errors found during the test run at depth _DEPTH_ made on date _DATE_ at time _TIME_. The summary file is only useful during full test runs (e.g., not when running individual tests). + 1. `xtest.DEPTH.DATE.TIME.results` -- this directory contains the journal from the tests run at depth _DEPTH_ made on date _DATE_ at time _TIME_ as well as any error images generated. + * After running xtest, you can check to see if everything passed by looking at the summary/errors/report file(s) to see if there are any failures. + * There are some known failures that the summary file attempts to take into account. The first part of the summary file is the list of failures, and at the end of the summary file is a diff between the known failures (e.g., XDraw``Arcs) and what the failures were for this run. + * The xreg script has only been tested on Linux systems. If there are problems with these scripts, please post patches to the [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]] mailing list. + * There are many other options to xreg (and it can be used to run other tests such as x11perf). Run `xreg -help` to see the usage message. + +#### Actually running the conformance tests + +For this section, one of the following should be used for testing: + + * For platforms based on a XFree86-style DDX, the ``dummy`` driver should be used. + * For example: `xreg -xtest -xorg` + * This will run xtest at all the default depths using the Xorg server. + * Check the output of each report or summary file to make sure that all tests that are expected to pass do actually pass. + * For all other platforms, ``Xvfb`` should be used. + * For example: `xreg -xtest -xvfb -d "15 16 24+32"` + * This will run xtest at depths 15, 16 and 24+32 using the Xvfb server. + * Check the output of each report or summary file to make sure that all tests that are expected to pass do actually pass. + * Note that Xvfb does not currently run at depth 8, so the example above limits the testing to depths 15, 16 and 24+32. Update, this problem has been fixed in CVS now and Xvfb at depth 8 works again. +Additional notes: + + * The ``Xvfb`` server is special X server that uses a virtual framebuffer. It is normally built and installed with the full release. See the `Xvfb(1)` for more information about this server. + * The ``dummy`` driver is a special driver available with the XFree86 DDX. To use the dummy driver, simply substitue it for your normal card driver in the `Device` section of your `xorg.conf` configuration file. For example, if you normally uses an ati driver, then you will have a `Device` section with `Driver "ati"` to let the X server know that you want it to load and use the ati driver; however, for these conformance tests, you would change that line to `Driver "dummy"` and remove any other ati specific options from the `Device` section. + +### Run tests + +After installing the full release, you can run the subset of tests listed below that applies to the platform being tested. Please run these tests on at least two different driver families (where applicable). For example, on an IA-32 system running Linux, you could run the tests using one card from the ATI driver family and another card from the NVIDIA driver family. + +Tests for each driver family: + + 1. X test suite (listed above) + 1. x11perf + 1. rendertest (found in the xapps CVS repository on freedesktop.org) + 1. Standard graphical environment + 1. GL tests: glxgears, gloss, [[quake3|http://www.freedesktop.org/~jg/quake3.tar.gz]] + 1. Switch to/from VTs (on Linux) +-- [[KevinMartin|KevinMartin]] - 18 Jan 2005 diff --git a/XorgTriage.mdwn b/XorgTriage.mdwn new file mode 100644 index 00000000..e4b78b4f --- /dev/null +++ b/XorgTriage.mdwn @@ -0,0 +1,16 @@ + +Basic rules about triaging bugs for X.org: + +* Bugs that are NEW and assigned to `xorg-team` are awaiting triage. +* ASSIGNED with owner set to `xorg-team` means that the bug is valid but not assigned to a specific developer yet +* ASSIGNED with owner changed to specific developer means that it's in that developer's queue +* Don't go closing bugs if they're assigned to someone else (including assigned to the team) +* Discuss a WONTFIX, NOTABUG, or NOTOURBUG with the developers first before closing any bug with these resolutions. +* General rules for the severity field: + * Blocker: server crashes, security problems, build problems with the default build, release issues. + * Critical: rendering errors, client-side crashes, (most) regressions. +* Use keywords intelligently: + * `want-backtrace` on bugs that need a useful backtrace before they can be debugged + * change `want-backtrace` to `have-backtrace` once you have one + * `regression` for functionality regressions relative to previous releases + * `janitor` for cleanup or style tasks a la [[kernel janitors|http://janitor.kernelnewbies.org/]]
\ No newline at end of file diff --git a/XorgWorkshops.mdwn b/XorgWorkshops.mdwn new file mode 100644 index 00000000..5ebd7886 --- /dev/null +++ b/XorgWorkshops.mdwn @@ -0,0 +1,7 @@ + + +# X.Org-related Workshop and Meeting Funding + +One of the explicit goals of the X.Org Foundation is to fund work that helps to advance the development of the X.Org project, and of X and related open source projects in general. As such, the X.Org Foundation Board explicitly invites proposals to fund such workshops. A good proposal will contain a target date, a reasonably accurate budget, and a description of the event that emphasizes why it will benefit X-related work. Note that the Board is more than willing to approve funding for events, such as the recent Video Hackfest, that are not directly about work on the core X.Org software base. + +To apply for funding for your workshop or meeting, please email your proposal to board AT foundation DOT x DOT org, or contact any Board member for feedback and help. diff --git a/XsltVersion.mdwn b/XsltVersion.mdwn new file mode 100644 index 00000000..ac0333e9 --- /dev/null +++ b/XsltVersion.mdwn @@ -0,0 +1,12 @@ + +<?xml version="1.0" encoding="ISO-8859-1"?> + +<?xml-stylesheet href="XsltVersion" type="text/xml"?> + +<xsl:stylesheet version="1.0" xmlns:xsl="[[http://www.w3.org/1999/XSL/Transform">|http://www.w3.org/1999/XSL/Transform">]] + + * <xsl:output method="html" omit-xml-declaration="yes" indent="no"/> <xsl:template match="/"> + * This Wiki is running an XSLT engine by <xsl:value-of select="system-property('xsl:vendor')"/> (<a href="{system-property('xsl:vendor-url')}"><xsl:value-of select="system-property('xsl:vendor-url')"/></a>) implementing XSLT v<xsl:value-of select="system-property('xsl:version')"/> +</xsl:template> + +</xsl:stylesheet> diff --git a/apm.mdwn b/apm.mdwn new file mode 100644 index 00000000..1265b274 --- /dev/null +++ b/apm.mdwn @@ -0,0 +1,14 @@ + + +# apm + +Driver for Alliance Promotion chipset based video chips. License: MIT + + +## Documentation and Support + + +## Known Issues + + +### Release 6.7.0 diff --git a/ati.mdwn b/ati.mdwn new file mode 100644 index 00000000..41342514 --- /dev/null +++ b/ati.mdwn @@ -0,0 +1,19 @@ + + +# ati + +Wrapper driver for ATI video chips + +License: MIT + + +## Documentation and Support + +The ati driver is a small wrapper that probes your card and then loads the appropriate driver, either radeon, r128, or atimisc. + +* Please check the [[radeon|radeon]], [[r128|r128]], or [[atimisc|atimisc]] manpages for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/atimisc.mdwn b/atimisc.mdwn new file mode 100644 index 00000000..ef1f42f0 --- /dev/null +++ b/atimisc.mdwn @@ -0,0 +1,15 @@ + + +# ati + +Driver for ATI Mach8/32/64 based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/ati.4.html]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/chips.mdwn b/chips.mdwn new file mode 100644 index 00000000..f73af866 --- /dev/null +++ b/chips.mdwn @@ -0,0 +1,16 @@ + + +# chips + +Driver for Chips&Technologies based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/chips.4.html]] for the current release for configuration options. + * There is also a [[README file|http://www.freedesktop.org/~xorg/current/doc/chips.4.html]] containing additional information about known problems and hints. + +## Known Issues + + +### Release 6.7.0 diff --git a/cirrus.mdwn b/cirrus.mdwn new file mode 100644 index 00000000..d7e88622 --- /dev/null +++ b/cirrus.mdwn @@ -0,0 +1,14 @@ + + +# cirrus + +Driver for Cirrus Logic based video chips. License: MIT + + +## Documentation and Support + + +## Known Issues + + +### Release 6.7.0 diff --git a/conversion.mdwn b/conversion.mdwn new file mode 100644 index 00000000..9868632f --- /dev/null +++ b/conversion.mdwn @@ -0,0 +1,10 @@ +# MoinMoin to Ikiwiki conversion + +If you have an account on Annarchy, you can help out with the conversion of this wiki. + +You can follow the [[page conversion|http://wiki.freedesktop.org/sitewranglers/wiki/moin2iki_page_selection/]] instructions using `PROJECT="xorg"`. + +Here is a list of broken links, which should be a starting place for what needs converting: + +[[!brokenlinks]] + diff --git a/cyrix.mdwn b/cyrix.mdwn new file mode 100644 index 00000000..76ea5f56 --- /dev/null +++ b/cyrix.mdwn @@ -0,0 +1,16 @@ + + +# cyrix + +Driver for Cyrix MediaGX based video chips. License: MIT + + +## Documentation and Support + + * There is also a [[README file|http://www.freedesktop.org/~xorg/current/doc/cyrix.4.html]] containing additional information about known problems and hints. + * The requested URL /~xorg/current/doc/cyrix.4.html was not found on this server. + +## Known Issues + + +### Release 6.7.0 diff --git a/fbdev.mdwn b/fbdev.mdwn new file mode 100644 index 00000000..8a76f86d --- /dev/null +++ b/fbdev.mdwn @@ -0,0 +1,15 @@ + + +# fbdev + +Driver for Linux framebuffer device based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.x.org/releases/current/doc/man/man4/fbdev.4.xhtml]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/fosdem2006.mdwn b/fosdem2006.mdwn new file mode 100644 index 00000000..0439db25 --- /dev/null +++ b/fosdem2006.mdwn @@ -0,0 +1,101 @@ + + +# X@FOSDEM2006 + +* Time: Friday, **24**th until Sunday, **26**th of **February 2006**. +* Place: At **[[FOSDEM 2006|http://www.fosdem.org/2006]]** in Brussels, Belgium. +X.org will this year have its first X@FOSDEM, meaning that X will have some events on or surrounding the FOSDEM event. An [[X Developers HotHouse|fosdem2006]] will be organised on **Friday the 24th**, the day before FOSDEM 2006 and during the weekend (**25th** and **26th**) X.org will have a [[DevRoom|fosdem2006]] at FOSDEM. + +The goal of X@FOSDEM is to have X developers meet, discuss and hack. This is why the idea of an [[X Developers HotHouse|fosdem2006]] has been revived. The event also allows those who were unable to make it to the [[X.org Developers Conference|XDevConf]] to catch up on what happened there. At the same time, X.org will have a very clear presence at [[one of the most highly regarded Free and Open Source community events|http://www.fosdem.org/]]. + +**We are still looking for [[speakers for the Devroom|fosdem2006]].** + + +## X@FOSDEM Schedule + + +### Friday, 24th of February 2006: + + * 9.30 - 18.00: [[X@FOSDEM Developers HotHouse|fosdem2006]]. +* 18.00+ : [[X@FOSDEM Social event|fosdem2006]]. + +### Saturday, 25th of February 2006: + + * 9.30 - 12.30: [[FOSDEM Opening talks|http://www.fosdem.org/2006]]. +* 14.00 - 18.00: [[X@FOSDEM Devroom|fosdem2006]]. + +### Sunday, 26th of February 2006: + + * 9.30 - 12.30: [[X@FOSDEM Devroom|fosdem2006]]. +* 13.30 - 18.00: [[X@FOSDEM Devroom|fosdem2006]]. + +## X@FOSDEM Developers HotHouse + +<a name="hothouse"></a> + +A **[[HotHouse|HotHouse]]** is a place where developers can meet informally, discuss and hack on code together. It is proven concept that's highly creative and very productive. + +The room is on the same campus where FOSDEM takes place the days after ([[map|http://www.freedesktop.org/~libv/HotHouse_location.png]]), and it is equipped with electricity and (at least local) networking. You should be able to find arrows that guide you to the hothouse (ACE room) when you walk down the Rue Paul Heger. + +Here is a list of [[HotHouse participants|Fosdem2006HotHouseParticipants]]. + + +## X@FOSDEM DevRoom + +<a name="devroom"></a> + +A **[[DevRoom|DevRoom]]** is a project/topic specific room on FOSDEM, holding anywhere from 50 to 150 people. It is public but doesn't tend to draw the crowds the main FOSDEM talks tend to get. In general, a [[DevRoom|DevRoom]] can be thought of as a more public [[HotHouse|HotHouse]], but one which has [[scheduled talks|fosdem2006]]. + +The [[DevRoom|DevRoom]] is free and open to everyone, there is no registration required. But if you're coming, you can always attach yourself to [[this list|Fosdem2006DevRoomAttendants]]. + + +### DevRoom Speaker Schedule + +<a name="schedule"></a> + +Saturday: + +* 14.00: [[Stuart Kreitman - Highlights from the Santa Clara XDevConf|fosdem2006Stuart]]. +* 15.00: [[Keith Packard - Coordinate transform redirection for composited window environments|fosdem2006Keith]]. +* 16.00: [[Matthias Hopf - Xgl, the current future of X|fosdem2006Matthias]]. +Sunday: + +* 09.30: [[Stuart Kreitman - Automated Display Configuration in the Xorg Window System|fosdem2006Stuart]]. +* 10.30: [[Luc Verhaegen - X and modesetting, atrophy illustrated|fosdem2006Luc]]. +* 11.30: [[Jay Hobson - Dtracing the Xorg Server|fosdem2006Jay]]. +* 12.30: Lunchtime. +* 13.30: [[Egbert Eich - Reworking the PCI subsystem on X|fosdem2006Egbert]]. +* 14.30: [[Stephane Marchesin - Towards open source 3D acceleration for nvidia cards|fosdem2006Stephane]]. +* 15.30: [[Daniel Stone - XKB|fosdem2006Daniel]] +* 16.30: Zack Rusin - Why XGL is **not** the answer +The "To Be Announced" talks are slots reserved for talks not appearing in the FOSDEM brochure. + + +### DevRoom Speakers + +<a name="speakers"></a> + +If you're interested in giving a talk at the X.org FOSDEM [[DevRoom|DevRoom]], then [[contact us|mailto:fosdem-org@lists.x.org]] right away. + +* We have time for about 11 talks. +* We will require a **titel or topic**, and a **brief description** ASAP. +* Papers are due on wednesday 22nd. +* FOSDEM provides a projector and networking. If you need anything further you can always [[ask us|mailto:fosdem-org@lists.x.org]], but be prepared to bring it along yourself. + +## X@FOSDEM Social Event + +<a name="social"></a> + +The "back room" of Cafe De L'Universite has been reserved for X.org. Cafe De L'Universite is a students cafe 500m east of the FOSDEM site (towards the cemetary) and they offer a good choice of belgian food at good prices, accompanied by a nice selection of belgian beers. Friday night is mussels night! + + +## Further FOSDEM information + +For more information about the FOSDEM event, there's always the [[FOSDEM website|http://www.fosdem.org/2006]]. It includes city maps, information about transportation and a list of hotels. + +If you would like a complete overview of FOSDEM, then maybe [[last years site|http://www.fosdem.org/2005]] will be of interest. + + +## Registration and further information + +<a name="contact"></a> If you want to register for the [[HotHouse|fosdem2006]] or are interested in [[speaking at the DevRoom|fosdem2006]], or just need more information, mail us at [[fosdem-org@lists.x.org|mailto:fosdem-org@lists.x.org]]. diff --git a/fosdem2006Daniel.mdwn b/fosdem2006Daniel.mdwn new file mode 100644 index 00000000..8c6df110 --- /dev/null +++ b/fosdem2006Daniel.mdwn @@ -0,0 +1,9 @@ + +Daniel Stone is apparently the XKB maintainer, but is not entirely sure how that happened. He fears the prospect of overhauling the input system, but feels powerless to stop it. He was previously the X maintainer for Ubuntu, and worked on Debian packaging of X also. + + +## XKB FTW + +XKB, the X Keyboard Extension is, at least in theory, a terrific extension that allows easy and sensible keyboard configuration. In practice, however, it offers many opportunities for improvement. This talk will outline my current plans for XKB, as well as some of the history of this rarely-understood extension. + +Slides: [[http://www.fooishbar.org/talks/fosdem-xkb.pdf|http://www.fooishbar.org/talks/fosdem-xkb.pdf]] diff --git a/fosdem2006Egbert.mdwn b/fosdem2006Egbert.mdwn new file mode 100644 index 00000000..dd19fb50 --- /dev/null +++ b/fosdem2006Egbert.mdwn @@ -0,0 +1,18 @@ + +Egbert Eich is a long time X developer, SuSE X maintainer, and X.org board member. He also managed the X.org 6.7.0 release. + + +## Reworking the PCI subsystem in X + +The PCI subsystem is one of the pieces of X that are in urgent need of renovation. The majority of its code was developed in the early days of PCI and when X mostly supported x86 systems. Since then numerous systems with additional requirements have been introduced and the support provided by the operating systems has been greatly enhanced. + +Therefore it is time to redesign this entire subsystem. Some ideas behind this redesign are presented here. + +The talk was renamed to: + + +## Renovating DDX + +The X.Org DDX has met its limits. A lot of functionality it provides is not required by most operating systems any more today. It imposes limits and restricitions of hardware of the mid-90's. Furthermore it doesn't provide a lot of infrastructure that is needed for modern hardware. Thus a lot of this is now implemented inside the drivers - and designed in an ad hoc fashion. + +The [[Slides|FOSDEM2006EgbertEich.pdf]] of the talk. diff --git a/fosdem2006Egbert/FOSDEM2006EgbertEich.pdf b/fosdem2006Egbert/FOSDEM2006EgbertEich.pdf Binary files differnew file mode 100644 index 00000000..7987a1b3 --- /dev/null +++ b/fosdem2006Egbert/FOSDEM2006EgbertEich.pdf diff --git a/fosdem2006Luc.mdwn b/fosdem2006Luc.mdwn new file mode 100644 index 00000000..c426a853 --- /dev/null +++ b/fosdem2006Luc.mdwn @@ -0,0 +1,11 @@ + +Luc Verhaegen is a bedroom hacker whose focus is almost solely on modesetting, he started [[http://unichrome.sf.net/|http://unichrome.sf.net/]] and spends most of his time bashing VIA. + + +## X and modesetting, atrophy illustrated + +X had a rich and diverse modesetting history, but with the advent of 3D acceleration and DRI, modesetting suddenly received a lot less attention. Some examples of the resulting cruft are shown and some shortcomings examined. Current developments are explained and possible future directions are explored. + +Paper: [[X_and_Modesetting_-_Atrophy_illustrated_(paper).pdf|http://people.freedesktop.org/~libv/X_and_Modesetting_-_Atrophy_illustrated_(paper).pdf]] + +Slides: [[X_and_Modesetting_-_Atrophy_illustrated_(slides).pdf|http://people.freedesktop.org/~libv/X_and_Modesetting_-_Atrophy_illustrated_(slides).pdf]] diff --git a/fosdem2006Matthias.mdwn b/fosdem2006Matthias.mdwn new file mode 100644 index 00000000..e782e757 --- /dev/null +++ b/fosdem2006Matthias.mdwn @@ -0,0 +1,9 @@ + +Matthias Hopf is X.org developer working for SUSE / Novell. As his main interests include using 3D graphics, working on Xgl is a natural thing for him. + + +## Xgl - The Current Future of X + +XAA has pretty much reached the end of its productive life. One promissing successor is OpenGL, an industry standard API that could help stabilize the internal rendering interface of the Xserver. This API has been used by David Reveman to create Xgl. It enables the use of modern features like pixel shaders, and it allows for accelerating Render and Composite independent of the graphics hardware. Additionally, Xgl is a technology enabler, allowing for these neat effects that compiz is now showing. + +Slides: [[fosdem_2006_xgl.pdf|http://people.freedesktop.org/~mhopf/fosdem_2006_xgl.pdf]] diff --git a/fosdem2006Stephane.mdwn b/fosdem2006Stephane.mdwn new file mode 100644 index 00000000..6b37a5e1 --- /dev/null +++ b/fosdem2006Stephane.mdwn @@ -0,0 +1,5 @@ + + +## Towards open source 3D acceleration for nvidia cards + +In this talk, steps towards an open source driver for 3D acceleration on nvidia graphics cards are detailed. Relevant hardware features found on nvidia cards are reviewed, and a quick overview of the DRI/DRM model for 3D acceleration is given. Reverse engineering techniques for these cards are shown, along with ongoing developments. Finally, future directions for this work are given. diff --git a/fosdem2007.mdwn b/fosdem2007.mdwn new file mode 100644 index 00000000..cc638967 --- /dev/null +++ b/fosdem2007.mdwn @@ -0,0 +1,25 @@ + + +# X@FOSDEM2007 + +* Time: Saturday, **24**th and Sunday, **25**th of **February 2007**. +* Place: At **[[FOSDEM|http://www.fosdem.org/]]** in Brussels, Belgium. +* Program: available **[[on the fosdem website|http://fosdem.org/2007/schedule/devroom/xorg]]** +There will be a second X@FOSDEM this year. We have secured a [[DevRoom|DevRoom]] for the FOSDEM event, where talks and open discussion around Xorg and related technologies will happen. Attending the [[DevRoom|DevRoom]] and FOSDEM is of course free. + +Notice that there will be no [[HotHouse|HotHouse]] this year, at least I (Stephane) cannot organize it, since I'm working on friday. + +The X@FOSDEM [[DevRoom|DevRoom]] will, like last year, be a place where talks can be held, amongst other things. More generally, it's a good occasion to meet other Xorg devs ! + +Only a call for attendants and community interest was made at this point, and the results were very positive. The following persons will already be attending: Michel Daenzer, Egbert Eich, Jim Gettys, Jerome Glisse, Matthieu Herrb, Matthias Hopf, Amaury Jacquot, Lars Knoll, Stephane Marchesin, Keith Packard, Rene Rebe, Zack Rusin, Jamey Sharp, Luc Verhaegen. + +If you are also interested in visiting this event, don't hesitate to mail [[me|http://wiki.x.org/wiki/StephaneMarchesin]] or pop up on irc (#xorg-europe on freenode.net). There is no obligation to do this, but it will help organisation. + + +# Videos of Talks + +FOSDEM recorded some of the X related talks in the Desktop Applications track including: + +* [[X.Org: Projects and People - Keith Packard|http://www.youtube.com/watch?v=C5HNy_Vxr78]] +* [[AIGLX: Accelerated Indirect GLX - Kristian Høgsberg|http://www.youtube.com/watch?v=9A3R4h88sEw]] +Ogg/Theora links are available on [[http://archive.fosdem.org/2007/media/video.html|http://archive.fosdem.org/2007/media/video.html]] diff --git a/fosdem2008.mdwn b/fosdem2008.mdwn new file mode 100644 index 00000000..c20a38ae --- /dev/null +++ b/fosdem2008.mdwn @@ -0,0 +1,90 @@ + + +# X@FOSDEM2008 + +* Time: Saturday, **23**rd and Sunday, **24**th of **February 2008**. +* Place: At **[[FOSDEM 2008|http://fosdem.org/2008]]** in Brussels, Belgium. +X.org will this year have its third X@FOSDEM, meaning that X will have some events on or surrounding the FOSDEM event. We have a FOSDEM [[DevRoom|fosdem2008]] on Saturday the 23rd and Sunday the 24th. Due to limited interest and high organizational overhead, no [[HotHouse|HotHouse]] will be organized. + +The goal of X@FOSDEM is to have X developers meet, discuss and hack and X.org will have a very clear presence at [[one of the most highly regarded Free and Open Source community events|http://www.fosdem.org/]]. So FOSDEM is the perfect place to get exposed to both the Xorg developer and the Xorg user community. + +**A call for [[speakers for the Devroom|fosdem2008]] has gone out.** + + +## X@FOSDEM Schedule + + +### Friday, 22nd of February 2008: + +* 18.00+ : Those already in Brussels could meet up and share supper, and maybe head on to [[FOSDEM beerevent|http://www.fosdem.org/2008/beerevent]] afterwards. + +### Saturday, 23rd of February 2008: + +* 9.30 - 12.30: [[FOSDEM Opening talks|http://www.fosdem.org/2008]]. +* 14.00 - 19.00: [[X@FOSDEM Devroom|fosdem2008]]. +* 19.00+ : Supper somewhere in Brussels (sponsors?). + +### Sunday, 24th of February 2008: + +* 9.30 - 18.00: [[X@FOSDEM Devroom|fosdem2008]]. +* 19.00+ : Might want to meet up for supper, but nothing will be organized as people will be leaving already. + +## X@FOSDEM DevRoom + +<a name="devroom"></a> + +A **[[DevRoom|DevRoom]]** is a project/topic specific room on FOSDEM, holding up to 100 people. It is public but doesn't tend to draw the crowds the main FOSDEM talks tend to get. In general, the FOSDEM public consists of developers and more advanced users and people interested in X.org and the topic in the [[talk scheduled|fosdem2008]] then will attend such talks. + +The [[DevRoom|DevRoom]] is free and open to everyone, there is no registration required. If the devroom is dangerously full, like during the 2006 Xgl talk, you will just be denied access :) + + +### DevRoom Speaker Schedule + +<a name="schedule"></a> + +Saturday: + +* 14.30: John Bridgman - Open sourcing ATI. +* 15.30: Egbert Eich - The RadeonHD Project. +* 16.30: Stephane Marchesin - Nouveau : Cooking an Open Source Nvidia driver. +* 17.30: To Be Announced. +Sunday: + +* 10.30: Helge Bahmann - XAudio. +* 11.00: Remi Cardona - Bringing Metisse and X.org together. +* 12.00: Daniel Stone - Fixing X input: the beer coaster roadmap to success. +* 13.00: Lunch +* 14.00: Michael Meeuwisse - Project VGA. +* 15.00: Keith Whitwell - Update on Gallium3D. +* 16.00: Jerome Glisse - Radeon, from DRM to Gallium. +* 17.00: Keith Packard - Roadmap to recovery - pain and redemption in X driver development. +The "To Be Announced" talks are slots reserved for talks not appearing in the FOSDEM brochure. Those just have not met the January 31st deadline. + + +### DevRoom Speakers + +<a name="speakers"></a> + +If you're interested in giving a talk at the X.org FOSDEM [[DevRoom|DevRoom]], then [[contact us|fosdem2008]] right away. + +* We have time for about 11 talks. +* We will require a **titel or topic**, and a **brief description** before january 31st. +* FOSDEM provides a projector and networking. If you need anything further you should probably bring this along yourself, but feel free to ask anyway :) + +## X@FOSDEM Social Event + +<a name="social"></a> + +We hope to be organizing at least 1 sponsored evening. But this is still in a highly preliminary state. + + +## Further FOSDEM information + +For more information about the FOSDEM event, there's always the [[FOSDEM website|http://www.fosdem.org/2008]]. It includes city maps, information about transportation and a list of hotels. + +If you would like a complete overview of FOSDEM, then maybe [[last years site|http://www.fosdem.org/2007]] will be of interest. + + +## Registration and further information + +<a name="contact"></a> I still need to check whether there is life still in the old mailing lists. But feel free to just mail me, lverhaegen at suse dot de, or the xorg mailinglist, or poke us on irc in #xorg-europe on freenode.net. diff --git a/fosdem2009.mdwn b/fosdem2009.mdwn new file mode 100644 index 00000000..719312e6 --- /dev/null +++ b/fosdem2009.mdwn @@ -0,0 +1,129 @@ + + +# X.org DevRoom at FOSDEM2009 + +* Time: Saturday, **7**th and Sunday, **8**th of **February 2009**. +* Place: At **[[FOSDEM 2009|http://fosdem.org/]]** in Brussels, Belgium. +X.org will this year have its fourth X.org [[DevRoom|fosdem2009]] at FOSDEM. The goal of X.org [[DevRoom|DevRoom]] at FOSDEM is to have X developers meet, discuss and hack and X.org will have a very clear presence at [[one of the most highly regarded Free and Open Source community events|http://www.fosdem.org/]]. So FOSDEM is the perfect place to get exposed to both the X.org developer and the X.org (advanced) user community. + + +## X.org at FOSDEM Schedule + + +### Saturday, 7th of February 2009: + +* 9.30 - 12.00: [[FOSDEM Opening talks|http://www.fosdem.org/]]. +* 13.00 - 19.00: [[X.org Devroom|fosdem2009]]. + +### Sunday, 8th of February 2009: + +* 10.00 - 17.00: [[X.org Devroom|fosdem2009]]. + +## X.org DevRoom + +<a name="devroom"></a> + +A **[[DevRoom|DevRoom]]** is a project/topic specific room on FOSDEM, holding up to 100 people. It is public but doesn't tend to draw the crowds the main FOSDEM talks tend to get. In general, the FOSDEM public consists of developers and more advanced users and people interested in X.org and the topic in the [[talk scheduled|fosdem2009]] then will attend such talks. + +The [[DevRoom|DevRoom]] is free and open to everyone, there is no registration required. If the devroom is dangerously full, like during the 2006 Xgl or the 2008 Gallium talk, you will just be denied access :) + +This year, we have room H.1309, which has a massive 150seat capacity, and the luxury of 3 breathing holes. It's the first [[DevRoom|DevRoom]] on the upper level in the main building, which was last years CentOS/Fedora [[DevRoom|DevRoom]]. + + +### DevRoom Talks Schedule + +<a name="schedule"></a> + +Saturday: + +* 13.00: +* 14.00: [[Matthias Hopf: RandR 1.3: New Features in a Nutshell.|fosdem2009]] +* 15.00: [[Keith Packard: The Rebuilt Linux Desktop.|fosdem2009]] +* 16.00: [[Stephane Marchesin: Nouveau Status Update.|fosdem2009]] +* 17.00: [[Eric Anholt: Intel's graphics projects for the coming year.|fosdem2009]] +Sunday: + +* 10.00: +* 11.00: [[Helge Bahmann: Multimedia processing extensions for the X Window System.|fosdem2009]] +* 12.00: [[Matthew Garrett: Aggressive power management in graphics hardware.|fosdem2009]] +* 13.00: +* 14.00: [[Matthias Hopf: r600_demo: Programming the New GPU Generations from AMD|fosdem2009]] +* 15.00: [[Stephane Marchesin: LLVM + Gallium 3D: Mixing a compiler with a graphics framework.|fosdem2009]] +* 16.00: [[Jerome Glisse: Shader Compiler Optimisation Strategies.|fosdem2009]] +The empty slots in this schedule will be filled up still. The [[fosdem website|http://www.fosdem.org/2009/schedule/rooms/h.1309]] also has a page with our schedule. + + +### DevRoom Talks + +<a name="hopf1"></a> +#### Matthias Hopf : RandR 1.3: New Features in a Nutshell. + +RandR 1.3 presents - amongst other things - transformations, panning, and standardized properties. This talk will show how to use these features and how they should influence tools and applications. + +<a name="packard"></a> +#### Keith Packard: The Rebuilt Linux Desktop. + +Graphics drivers under Linux have seen the most significant changes since X was first ported in the last year. The X server can now run as an unprivileged process; kernel panic messages can be displayed while graphics are active; graphics applications can use virtual memory to store GPU data. + +In the kernel, these changes include the new Graphics Execution Manager (GEM) and kernel-based video mode setting (KMS). Beyond the kernel, the second version of the Direct Rendering Interface X extension (DRI2) unifies the X and OpenGL image storage space. + +This talk will describe the kernel and user-space changes along with the other kernel changes necessary to support the new code. Finally, the audience will be encouraged to participate in a discussion about future plans in this area. + +<a name="marcheu1"></a> +#### Stephane Marchesin: Nouveau Status Update. + +Since last Fosdem, Nouveau has been making steady progress. This talk will detail some of the changes made since last year and present the newest features. Throughout this talk, I will also introduce a number of "did you know ?" slides about the project and Nvidia hardware's inner workings. + +<a name="helge"></a> +#### Helge Bahmann: Multimedia processing extensions for the X Window System. + +This talk reports on experiences gained with a set of experimental extensions for multimedia processing in the X Window System. They allow to transmit compressed images and audio through the X protocol, and provide playback synchronization capabilities within the X server. This for example to build network-transparent media players and bring multimedia to classical thin clients. + +<a name="anholt"></a> +#### Eric Anholt: Intel's graphics projects for the coming year. + +While significant progress has been made in fixing the Linux graphics architecture, there are still some sharp edges. This talk will cover Intel's plans for the coming year, including DRI2 vblank support, DRI2 page flipping, rebuilding Mesa's compiler infrastructure, pulling ideas from Gallium into core Mesa, and more. + +<a name="mjg"></a> +#### Matthew Garrett: Aggressive power management in graphics hardware. + +Computers spend a lot of time idle, and graphics cards spend a lot of time just displaying a static image. This talk presents various techniques for reducing the power consumption of graphics hardware without any significant impact on visual quality or performance. + +<a name="hopf2"></a> +#### Matthias Hopf: r600_demo: Programming the New GPU Generations from AMD + +By allowing the release of r600_demo AMD has carried out a first step of their promise to release enough information for open source DRI driver development. As the initial, to be released documentation will be very register centric there is hardly enough information about how the chips are actually working. This talk will give an overview over how the r6xx and r7xx chip families are to be programmed, and in which pit falls one might stumble. + +<a name="marcheu2"></a> +#### Stephane Marchesin: LLVM + Gallium 3D: Mixing a compiler with a graphics framework. + +With the increasing importance of shaders, it has become necessary to use advanced optimization strategies for shader compilers. This talks presents the ongoing work on integrating a compiling and optimizing framework (LLVM) with a 3D framework (Gallium 3D). We will discuss the main difficulties behind this work, the inner workings and the current developments. + +<a name="glisse"></a> +#### Jerome Glisse: Shader Compiler Optimisation Strategies. + +Different GPUs have different architectures and thus require different shader compiler optimisations for more optimal performance. This talk explains some of the differences between both AMD, Nvidia and Intel GPUs and will present some compiler algorithms to optimise shaders accordingly. + +<a name="speakers"></a> +### DevRoom Speakers + +There are still some talk slots open. If you're interested in giving a talk at our [[DevRoom|DevRoom]], then [[contact us|fosdem2009]] right away. FOSDEM provides a projector and networking. If you need anything further you should probably bring this along yourself, but feel free to ask anyway :) + + +## Social Event + +<a name="social"></a> + +We might end up at the excellent and affordable [[restaurant mirabelle|http://www2.resto.be/mirabelle/]] again. But it is too early days for that to be certain. + + +## Further FOSDEM information + +For more information about the FOSDEM event, there's always the [[FOSDEM website|http://www.fosdem.org/]]. It includes city maps, information about transportation and a list of hotels. + +If you would like a complete overview of FOSDEM, then maybe [[last years site|http://www.fosdem.org/2008]] will be of interest. + + +## Registration and further information + +<a name="contact"></a> Feel free to just mail me, lverhaegen at suse dot de, or the xorg mailinglist, or poke us on irc in #xorg-europe on freenode.net. diff --git a/fosdem2010.mdwn b/fosdem2010.mdwn new file mode 100644 index 00000000..00a9b50b --- /dev/null +++ b/fosdem2010.mdwn @@ -0,0 +1,93 @@ + + +# X.org DevRoom at FOSDEM2010 + +* Time: Sunday, **7**th of **February 2010**. +* Place: At **[[FOSDEM 2010|http://fosdem.org/]]** in Brussels, Belgium. +X.org will this year have its fifth X.org [[DevRoom|fosdem2010]] at FOSDEM. The goal of X.org [[DevRoom|DevRoom]] at FOSDEM is to have X developers meet, discuss and hack and X.org will have a very clear presence at [[one of the most highly regarded Free and Open Source community events|http://www.fosdem.org/]]. So FOSDEM is the perfect place to get exposed to both the X.org developer and (advanced) user community. + + +## X.org at FOSDEM Schedule + + +### Sunday, 7th of February 2010: + +* 12.00 - 17.00: [[X.org Devroom|fosdem2010]]. + +## X.org DevRoom + +<a name="devroom"></a> + +A **[[DevRoom|DevRoom]]** is a project/topic specific room on FOSDEM, holding up to 60 people. It is public but doesn't tend to draw the crowds the main FOSDEM talks tend to get. In general, the FOSDEM public consists of developers and more advanced users and people interested in X.org and the topic in the [[talk scheduled|fosdem2010]] then will attend such talks. + +The [[DevRoom|DevRoom]] is free and open to everyone, there is no registration required. If the devroom is dangerously full, like during the 2006 Xgl or the 2008 Gallium talk, you will just be denied access :) + +Due to FOSDEMs Distribution mini-conf, we will no longer have access to the enormous room we had last year (which we used rather well). We have room [[AW.124|http://archive.fosdem.org/2009/maps/campus]], in the building across the main campus road from the main building, which has some nice luxuries like some windows for ventilation. + +On Saturday, the 6th of February, the same [[DevRoom|DevRoom]] as the X.org one will be used as the coreboot [[DevRoom|DevRoom]]. Due to limited coverage, on Sunday, from 9 until 12, the [[DevRoom|DevRoom]] will be used by the [[OpenMoko|OpenMoko]] project. + + +### DevRoom Talks Schedule + +<a name="schedule"></a> + +Sunday: + +* 9.00-12:00: [[OpenMoko|OpenMoko]] [[DevRoom|DevRoom]]. +* 12.00: [[Nicolai Hähnle : Towards GLSL in the r300 Gallium driver|fosdem2010]] +* 13.00: [[Daniel Stone : Polishing X11 and making it shiny.|fosdem2010]] +* 14.00: [[Luc Verhaegen : The free software desktop’s graphics driver stack.|fosdem2010]] +* 15.00: [[Jerome Glisse : GPU Userspace - kernel interface & Radeon kernel modesetting status.|fosdem2010]] +* 16.00: [[Mikhail Gusarov : X on e-Paper.|fosdem2010]] +The [[fosdem website|http://fosdem.org/2010/schedule/rooms/aw1.124]] also has a page with our schedule. + +Once again, [[Michael Larabel from phoronix|http://phoronix.com]] will be covering this event and even produce HDTV videos this year. + + +### DevRoom Talks + +<a name="glisse"></a> +#### Jerome Glisse : GPU Userspace - kernel interface & Radeon kernel modesetting status. + +The GPU is one of the most complex piece of hardware in modern computer. With kernel modesetting, more part of the driver move from userspace to the kernel allowing a cleaner support for suspend/resume and others GPU specific handling. The complexity of OpenGL driver, and also driver for new API such as OpenCL, are in userspace and will more than likely stays there. This presentation will look at the uniq problem of GPU kernel API to userspace. How userspace can interface with the kernel to submit GPU command in an as efficient as possible way. A brief review of what have been done and what is done now for various GPU, and insight on what might be better solution in the future will be given. Last part of the presentation will devolve to the status of radeon kernel modesetting which is now the largest driver inside the linux kernel with more the 70 000 lines of code and supporting more than 7 different GPU families. + +<a name="mgusarov"></a> +#### Mikhail Gusarov : X on e-Paper. + +e-Paper is a relatively new display type with very unusual characteristics. Some of them, such as greyscale, bring back memories of the distant past, whereas others, like a 1Hz refresh rate, are completely unique. This talk will outline the special requirements that e-Paper imposes on X. + +<a name="daniels"></a> +#### Daniel Stone : Polishing X11 and making it shiny. + +There are a few niggles about X11 today that mean every embedded device vendor patches the server in various unpleasant ways, whereas on the desktop it just looks suboptimal and we suck it up. This talk will cover a few parts of X11, such as client-side cursors, the video API, Composite, RandR, which currently need to be improved to make X11 look as good as it possibly can, without going to Wayland or X12. + +<a name="libv"></a> +#### Luc Verhaegen : The free software desktop’s graphics driver stack. + +4 years after the modular X tree was released, we can clearly see that we did not fully satisfy all expectations and that we are really holding the free software desktop back. In this talk, the current situation gets analysed, and the next step, providing more integrated graphics driver stacks, a change that will make life easier for all involved, is introduced and demonstrated. + +<a name="nha"></a> +#### Nicolai Hähnle : Towards GLSL in the r300 Gallium driver + +After a very brief overview of some relevant details of the hardware-level programming interface of Radeon R300-R500 shader hardware, I explain the high-level structure of how fragment and vertex programs are compiled in the modern Gallium 3D driver and how we got there. Finally, I talk about the big remaining challenges for full GLSL support. + +This is a fairly technical, hardware-specific talk. However, it is kept (hopefully) understandable to people who haven't spent hours writing shader compilers, and there will probably be some musing about which parts of code could possibly be shared with other drivers in the future. + + +## Social Event + +<a name="social"></a> + +The social event, which was reduced to just getting a table somewhere anyway, will be decided Ad-Hoc. + + +## Further FOSDEM information + +For more information about the FOSDEM event, there's always the [[FOSDEM website|http://www.fosdem.org/]]. It includes city maps, information about transportation and a list of hotels. + +If you would like a complete overview of FOSDEM, then maybe [[last years site|http://www.fosdem.org/2009]] will be of interest. + + +## Registration and further information + +<a name="contact"></a> Feel free to just mail us, libv at skynet dot be and eich at suse dot de, or the xorg mailinglist, or poke us on irc in #xorg-europe on freenode.net. diff --git a/fosdem2012.mdwn b/fosdem2012.mdwn new file mode 100644 index 00000000..ce411cf3 --- /dev/null +++ b/fosdem2012.mdwn @@ -0,0 +1,80 @@ + + +# X.Org DevRoom at FOSDEM2012 + +* Time: **4th & 5th** of **February 2012**. +* Place: At **[[FOSDEM 2012|http://fosdem.org/]]** in Brussels, Belgium. +X.Org will this year have its sixth X.Org [[DevRoom|fosdem2012]] at FOSDEM. The goal of X.Org [[DevRoom|DevRoom]] at FOSDEM is to have X.Org/Mesa/Wayland and related projects' developers meet, discuss and hack and have a very clear presence at [[one of the most highly regarded Free and Open Source community events|http://www.fosdem.org/]]. So FOSDEM is the perfect place to get exposed to both other developers and the (advanced) user community. + + +## X.Org at FOSDEM Schedule + + +### Sunday, 4th of February 2012: + +* 11.00 - 19.00: [[X.Org Devroom|fosdem2012]]. + +### Sunday, 5th of February 2012: + +* 9.00 - 11.00: [[X.Org Devroom|fosdem2012]]. +* 12.00 - 17.00: [[OpenICC Devroom|http://www.freedesktop.org/wiki/OpenIcc/Events/Fosdem/2012]]. + +## X.Org DevRoom + +<a name="devroom"></a> + +A **[[DevRoom|DevRoom]]** is a project/topic specific room on FOSDEM, holding (this time) up to 85 people. It is public but doesn't tend to draw the crowds the main FOSDEM talks tend to get. In general, the FOSDEM public consists of developers and more advanced users and people interested in X.Org/Mesa/Wayland and the topic in the [[talk scheduled|fosdem2012]] then will attend the [[DevRoom|DevRoom]]. + +This year, due to the obvious close relationship with the openICC project, we are sharing the [[DevRoom|DevRoom]] with them. Depending on both projects needs, the time available might still change in future. This is [[their wiki page|http://www.freedesktop.org/wiki/OpenIcc/Events/Fosdem/2012]] for their part of the event. + +We will have the K.3.401 room in a new building, which offers seating for up to 85 persons. + +The [[DevRoom|DevRoom]] is free and open to everyone, there is no registration required. If the devroom is dangerously full, like during the 2006 Xgl or the 2008 Gallium talk, you will just be denied access :) + + +### DevRoom Talks Schedule + +<a name="schedule"></a> + +Saturday: + +* (10.00: room setup, hopefully.) +* 11.00: [[Eric Anholt : Intel userspace.|http://fosdem.org/2012/schedule/event/intel_userspace]] +* 12.00: [[Daniel Stone and Peter Hutterer : Input in a modern world - input methods and multitouch.|http://fosdem.org/2012/schedule/event/xorg_input]] +* 13.00: [[Chris Wilson: Cairo: How to render tomorrow's user interfaces.|http://fosdem.org/2012/schedule/event/xorg_cairo]] +* 14.00: [[Daniel Vetter : dma_buf buffer sharing.|http://fosdem.org/2012/schedule/event/dma_buf]] +* 15.00: [[Martin Peres : Nouveau: Recap, on-going and future work.|http://fosdem.org/2012/schedule/event/nouveau]] +* 16.00: [[Luc Verhaegen : Liberating ARM's Mali GPU.|http://fosdem.org/2012/schedule/event/mali]] +* 17.00: [[Keith Packard : X Server 1.12 and beyond.|http://fosdem.org/2012/schedule/event/xserver]] +* 18.00: [[Francisco Jerez : Compute in the open graphics stack.|http://fosdem.org/2012/schedule/event/opencl]] +Sunday: + +* 9.00: [[Robert Bragg and Neil Roberts : Writing a Wayland Compositor.|http://fosdem.org/2012/schedule/event/wayland_compositor]] +* 10.00: [[Jesse Barnes : KMS plane support in Wayland.|http://fosdem.org/2012/schedule/event/kms_planes]] +* 11.00: [[Alon Levy: Xspice: Integrating spice-server into Xorg.|http://fosdem.org/2012/schedule/event/xorg_xspice]] +* 11.30: [[Robert Bradford and Kristian Hogsberg : Wayland Q & A for toolkit developers.|http://fosdem.org/2012/schedule/event/wayland_qa]] +* 12.00: [[Kai-Uwe Behrmann : Colour Management in Compositors.|http://fosdem.org/2012/schedule/event/cm_compositors]] +* 13.00: OpenICC [[DevRoom|DevRoom]]. +* 14.00: OpenICC [[DevRoom|DevRoom]]. +* 15.00: OpenICC [[DevRoom|DevRoom]]. +* 16.00: OpenICC [[DevRoom|DevRoom]]. +[[The full schedule is available here, including talk abstracts.|http://fosdem.org/2012/schedule/track/xorgopenicc_devroom]] + + +## Social Event + +<a name="social"></a> + +libv will probably be getting a table at the excellent "Le Mirabelle" again. If some sponsor for this turns up, great, but otherwise we just pay for ourselves as we have done the last few years. Make sure you catch libv beforehand (friday, or saturday before noon), so he can order a suitably sized table. + + +## Further FOSDEM information + +For more information about the FOSDEM event, there's always the [[FOSDEM website|http://www.fosdem.org/]]. It includes city maps, information about transportation and a list of hotels. + +If you would like a complete overview of FOSDEM, then maybe [[last years site|http://www.fosdem.org/2011]] will be of interest. + + +## Registration and further information + +<a name="contact"></a> Feel free to just mail libv at skynet dot be, or the [[x events mailinglist|http://lists.x.org/mailman/listinfo/events]], or poke libv on irc in #xorg-devel on freenode.net. diff --git a/fosdem2013.mdwn b/fosdem2013.mdwn new file mode 100644 index 00000000..8b2e76dc --- /dev/null +++ b/fosdem2013.mdwn @@ -0,0 +1,28 @@ + + +# X.Org DevRoom at FOSDEM2013 + +* Time: Saturday the **2nd** of **February 2013**. +* Place: At **[[FOSDEM 2013|http://fosdem.org/]]** in Brussels, Belgium. +The goal of X.Org [[DevRoom|DevRoom]] at FOSDEM is to have X.Org/Mesa/Wayland and related projects' developers meet, discuss and hack and have a very clear presence at [[one of the most highly regarded Free and Open Source community events|http://www.fosdem.org/]]. So FOSDEM is the perfect place to get exposed to both other developers and the (advanced) user community. + +Sadly the [[DevRoom|DevRoom]] is limited to only a single day this year, namely saturday. This makes scheduling kind of tight, and the massive ARM GPU driver block was partly moved to a mainline talk to relieve this scheduling tightness. + + +### DevRoom Talks Schedule + +<a name="schedule"></a> + +[[https://fosdem.org/2013/schedule/track/xorg/|https://fosdem.org/2013/schedule/track/xorg/]] + + +## Further FOSDEM information + +For more information about the FOSDEM event, there's always the [[FOSDEM website|http://www.fosdem.org/]]. It includes city maps, information about transportation and a list of hotels. + +If you would like a complete overview of FOSDEM, then maybe [[last years site|http://www.fosdem.org/2012]] will be of interest. + + +## Contact + +<a name="contact"></a> Please mail libv at skynet dot be. diff --git a/geode.mdwn b/geode.mdwn new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/geode.mdwn diff --git a/glide.mdwn b/glide.mdwn new file mode 100644 index 00000000..5fd9f3a4 --- /dev/null +++ b/glide.mdwn @@ -0,0 +1,15 @@ + + +# glide + +Driver for Glide2x (3Dfx) based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/glide.4.html]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/glint.mdwn b/glint.mdwn new file mode 100644 index 00000000..fd64d69a --- /dev/null +++ b/glint.mdwn @@ -0,0 +1,15 @@ + + +# glint + +Driver for 3Dlabs, TI based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/glint.4.html]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/i128.mdwn b/i128.mdwn new file mode 100644 index 00000000..367509e0 --- /dev/null +++ b/i128.mdwn @@ -0,0 +1,35 @@ + + +# i128 + +Driver for Number Nine based video chips. License: MIT + + +## History + +The i128 driver was initially written for XFree86 4.0 by Robin Cutshaw. Adam Jackson is the current maintainer. + +1.0.0: Base driver as of Xorg 6.8.2. + +1.1.0: Partial EXA support (Solid and Copy operations) + + +## Future plans + +* Composite hook for EXA +* DRM driver +* Xv acceleration (requires DRM support) +* Upload and Download hooks for EXA (requires DRM support) +* Smarter handling of SGI 1600SW flat panel +* DRI driver +See also the [[NumberNine page on the DRI wiki|http://dri.freedesktop.org/wiki/NumberNine]]. + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/i128.4.html]] for the current release for configuration options. + * There is also a [[README file|http://www.freedesktop.org/~xorg/current/doc/i128.4.html]] containing additional information about known problems and hints. + +## Known Issues + +See [[bugzilla|https://bugs.freedesktop.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&component=Driver%2Fi128&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=]]. diff --git a/i740.mdwn b/i740.mdwn new file mode 100644 index 00000000..e96cb054 --- /dev/null +++ b/i740.mdwn @@ -0,0 +1,15 @@ + + +# i740 + +Driver for Intel i740 based video chips. License: MIT + + +## Documentation and Support + + * There is also a [[README file|http://xorg.freedesktop.org/archive/X11R7.0/doc/html/i740.4.html]] containing additional information about known problems and hints. + +## Known Issues + + +### Release 6.7.0 diff --git a/index.mdwn b/index.mdwn new file mode 100644 index 00000000..75dbbfa8 --- /dev/null +++ b/index.mdwn @@ -0,0 +1,58 @@ +The X.Org project provides an open source implementation of the X Window System. The development work is being done in conjunction with the [[freedesktop.org|http://freedesktop.org]] community. The [[X.Org Foundation|XorgFoundation]] is the educational non-profit corporation whose [[Board|BoardOfDirectors]] serves this effort, and whose [[Members|Membership]] lead this work. + +The current X.Org release is [[X11R7.7|Releases/7.7]]. The next major release will be [[X11R7.8|Releases/7.8]]. Information about all [[releases|Releases]] is available. _(Important: If you have an older release, please see the [[Security page|Development/Security]] for information on security updates.)_ + +You may be interested in: + +* [[Documentation]] +* Development-related [[news|News]]. +* X.Org [[events|Events]]. +* [[Press releases|Other/Press]]. +* [[The Annual Report on the State of the X.Org Foundation|XorgFoundation/Reports/]] +* [[Related projects|RelatedProjects]]. + +## Reporting problems, asking questions and getting help + +* Check to see if your question is answered in the [[FAQ]]. +* Use the `xorg` product in the [[freedesktop bugzilla|https://bugs.freedesktop.org]] to report bugs against X.Org. ([[Gnome's bugzilla suggestions|http://bugzilla.gnome.org/]] are well worth looking over if you are new to reporting bugs with systems like bugzilla.) +* Check the [[Xorg mailing list archives|http://lists.freedesktop.org/archives/xorg/]] +* Send other questions or comments to [[the xorg mailing list|mailto:xorg@freedesktop.org]]. +* Or get help on [[XorgIRC]]. + +## Development + +* The [[DeveloperStart]] page includes information for developers along with links to per-module developer pages. + +## Mailing Lists + +On [[XorgMailingLists]] you can find a list of X-related mailing lists hosted on lists.freedesktop.org. More mailing lists on X Window System and related technologies along with subscription directions are available at [[XOrg Foundation|http://lists.x.org/]]. + + +## Getting X + +The best place to get X is from your operating system or distribution vendor. X.Org currently provides no binaries. + +There are many [[Mirrors]] from which you can download source code to the X Window System. If you would like to be a mirror, feel free to do so and add yourself to the [[Mirrors]] page. + +Development snapshots are currently on hiatus; most modules now update slowly enough that frequent snapshots aren't needed. + + +## Security + +For security advisories please check our [[SecurityPage]]. + +Please notify us of any security issues by sending mail to [[xorg_security@x.org|mailto:xorg_security@x.org]] . + + +## Sponsorship + +The X.Org Foundation welcomes sponsorship (both cash and in-kind), and tries hard to put the donations of sponsors to transparent good use. The Foundation is an extremely low-overhead all-volunteer organization. If you are interested in contributing, please see our [[SponsorshipPage|SponsorshipPage]]. + + +## Acknowledgements + +Our thanks go to [[Portland State University|http://www.pdx.edu/]] and [[Massachusetts Institute of Technology|http://web.mit.edu]] for providing the hosting of x.org/freedesktop.org, to [[Sun|http://sun.com]] and [[HP|http://hp.com]] for providing the x.org/freedesktop.org hardware, and to Sun and others who have provided generous financial sponsorship and in-kind support. + +Our thanks also go to the contributors to the X Window System technology over the years. Many of these are acknowledged in previous distribution [[release notes|http://www.x.org/X11R6.8.0/doc/RELNOTES6.html]]. + +This wiki is undergoing [[conversion]]. If you have a fd.o shell account, you can help! diff --git a/logo.png b/logo.png Binary files differnew file mode 100644 index 00000000..948cb77e --- /dev/null +++ b/logo.png diff --git a/mga.mdwn b/mga.mdwn new file mode 100644 index 00000000..53ea6309 --- /dev/null +++ b/mga.mdwn @@ -0,0 +1,15 @@ + + +# mga + +Driver for Matrox based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://wiki.x.org/current/doc/mga.4.html]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/nv.mdwn b/nv.mdwn new file mode 100644 index 00000000..5a661329 --- /dev/null +++ b/nv.mdwn @@ -0,0 +1,42 @@ + +Driver for NVIDIA based video chips. License: MIT + + +## Status + +Please see [[http://people.freedesktop.org/~aplattner/nv|http://people.freedesktop.org/~aplattner/nv]] for release information. + + +## 3D Acceleration Status + +At present the nv driver has no 3D acceleration. Nvidia will not provide the hardware specifications needed to add 3D support. However, some reverse engineering has been done for the Riva, TNT, and Geforce hardware. The UtahGLX project has basic 3D acceleration support. Help is needed to port this to DRI. For details see the [[DRI Nvidia Page|http://dri.freedesktop.org/wiki/nVidia?action=highlight&value=CategoryHardware]]. A Freedesktop.org project called [[nouveau|http://nouveau.freedesktop.org/wiki/]] has been started to work on 3D support. See the project's [[Feature Matrix|http://nouveau.freedesktop.org/wiki/RequiredFunctionality]] for current development status. For additional info on 3D acceleration support in general, see the [[free3d.org wiki|http://www.free3d.org/]]. + + +## Documentation and Support + + * Please check the [[nv(4) manual page|http://www.x.org/releases/current/doc/man/man4/nv.4.xhtml]] for the current release for configuration options. + +## Source code + + * [[Released version tarballs|http://www.x.org/releases/individual/driver/]] + * [[Current nv source in git|http://cgit.freedesktop.org/xorg/driver/xf86-video-nv]] + +## Known Issues + + * Check the Freedesktop.org Bugzilla for [[nv driver bugs|https://bugs.freedesktop.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__all__&product=xorg&content=nv]]. + +## Maintainers + + * X.org: [[Aaron Plattner|http://people.freedesktop.org/~aplattner/]] of NVIDIA + * XFree86: [[Mark Vojkovich|http://www.xfree86.org/~mvojkovi/]] of NVIDIA + +## Related Resources + + * [[Nvida Driver Internals|http://developer.nvidia.com/object/xdevconf_2006_presentations.html]] Xdevconf presentation by Andy Ritger of Nvidia + * [[XFree86 nv driver|http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/nv/]] nvidia driver CVS + * [[berliOS|http://svn.berlios.de/viewcvs/haiku/haiku/trunk/src/add-ons/accelerants/nvidia/]] nvidia driver CVS + * [[nvidia forum|http://www.nvnews.net/vbulletin/forumdisplay.php?f=14]] - Official forum for Linux nvidia users + * [[nvidia website|http://www.nvidia.com/]] + * [[NVIDIAProprietaryDriver|NVIDIAProprietaryDriver]] - X.Org Wiki page about nVidia's proprietary closed-source driver. + * [[Comparison of NVIDIA Graphics cards|http://en.wikipedia.org/wiki/Comparison_of_NVIDIA_Graphics_Processing_Units]] - Wikipedia page comparing NVIDIA hardware features + * [[NVIDIA and FOSS|http://en.wikipedia.org/wiki/NVIDIA_and_FOSS]] Wikipedia page on the friction between Nvidia and the Free/Open Source community due to their continued refusal to provide technical documentation on the hardware that would assist developers in writing drivers.
\ No newline at end of file diff --git a/radeon.mdwn b/radeon.mdwn new file mode 100644 index 00000000..720ba81e --- /dev/null +++ b/radeon.mdwn @@ -0,0 +1,89 @@ + + +# radeon + +Driver for ATI/AMD Radeon based video chips, everything from Radeon 7000 (R100) to Radeon HD 7000 (Southern Islands) series. Part of [[xf86-video-ati|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati]], ie. also known as the ”ati” driver. License: MIT + + +## Latest News + +* _30 Jan 2013_: **7.1.0**: Enable full 2D acceleration for SI (glamor), few bug fixes. <small>[ [[changelog|http://lists.x.org/archives/xorg-announce/2013-January/002154.html]] ]</small> +* _6 Nov 2012_: **7.0.0**: First KMS only release, enable 2D tiling by default on r6xx+ asics, xserver 1.13 support including prime, glamor support, SI support. <small>[ [[changelog|http://lists.x.org/archives/xorg-announce/2012-November/002093.html]] ]</small> +* _29 Jun 2012_: **6.14.6**: Few bugfixes, final release with UMS support (future releases will support only KMS) <small>[ [[changelog|http://lists.x.org/archives/xorg-announce/2012-June/001985.html]] ]</small> +* _7 Jun 2012_: **6.14.5**: Solid picture accel, tiling fixes, new PCI-IDs, 6xx-9xx Xv improvements, support for upcoming xserver API changes, bug fixes <small>[ [[changelog|http://lists.x.org/archives/xorg-announce/2012-June/001979.html]] ]</small> +* _28 Mar 2012_: **6.14.4**: Trinity APU support, 2D tiling on R6xx+, KMS tiling for r1xx-r2xx, lots of bug fixes <small>[ [[changelog|http://lists.x.org/archives/xorg-announce/2012-March/001922.html]] ]</small> +* _2 Nov 2011_: **6.14.3**: Llano APU support, KMS page flipping fixes, vdpau/XvMC support, tiling fixes <small>[ [[changelog|http://lists.x.org/archives/xorg-announce/2011-November/001750.html]] ]</small> +* _26 May 2011_: **6.14.2**: Cayman (Radeon HD 6900) acceleration support, Fusion APU tiling fixes, other fixes <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2011-May/001672.html]] ]</small> +* _17 Mar 2011_: **6.14.1**: Cayman (Radeon HD 6900) support (shadowfb, kms-only), big endian support <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2011-March/001628.html]] ]</small> +* _3 Feb 2011_: **6.14.0**: KMS EXA/Xv support for Evergreen GPUs (Radeon HD 5000 series), Fusion APUs (Ontario series) and Northern Islands GPUs (Radeon HD 6000 series but not 6900), KMS pageflipping support for all radeons <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2011-February/001602.html]] ]</small> +Latest changes in the development tree can be seen at: [[http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/]] + + +## Status + +See [[RadeonFeature|RadeonFeature]] and [[RadeonProgram|RadeonProgram]] for driver feature and supported program lists. For more 3D information see [[Radeon 3D acceleration Portal|http://dri.freedesktop.org/wiki/Radeon]]. + + +## What about other drivers? + +For an alternative R500/R600/R700 driver see [[radeonhd|radeonhd]]. Radeon has some features not available in radeonhd and vice versa, but generally they are starting to be quite close while radeon supports all the cards and radeonhd only r5xx-r7xx. + +The differences between radeon and radeonhd with r5xx-r7xx series: + +* radeon supports the kernel mode-setting (KMS) +* radeon supports tear-free video playback +* radeon supports TV-out +* (radeonhd was for long the one with HDMI audio support, but 2.6.33 kernel now has HDMI audio support for ati as well) +The reasons for two different drivers are historical, and starting to be a thing of the past as all the new DRM (direct rendering manager), 3D and KMS (kernel mode setting) work is done in a single place. radeonhd driver is abandoned and unsupported. Please use radeon. + +For R6xx and above there is also an [[ATIProprietaryDriver|ATIProprietaryDriver]] available, which is worse in many aspects but has better 3D performance and features. The proprietary driver included support for R3xx-R5xx GPUs until the March 2009 release. + + +## Documentation and Support + +Build instruction can be found from [[radeonBuildHowTo|radeonBuildHowTo]] + +Please check the included manual page (old version [[here|http://ftp.x.org/pub/X11R7.0/doc/html/radeon.4.html]]) for configuration options. To see or submit real-world reports on the 3D acceleration performance of this driver, see the [[free3d.org wiki|http://www.free3d.org]] + +There is an IRC channel #radeon on irc.freenode.net for radeon users and developers. + +* Note: You will need to have a registered nickname on freenode to chat in the channel. /msg nickserv register <pass> <email> or /msg nickserv identify <pass> +[[Submit|https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon]] a bug report. [[View|https://bugs.freedesktop.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=xorg&component=Driver/Radeon]] open bugs. + +Development mailing lists are: + +[[http://lists.x.org/mailman/listinfo/xorg-driver-ati|http://lists.x.org/mailman/listinfo/xorg-driver-ati]] - for the ati/radeon driver + +[[http://lists.freedesktop.org/mailman/listinfo/xorg|http://lists.freedesktop.org/mailman/listinfo/xorg]] - for general Xorg development + +[[http://lists.freedesktop.org/mailman/listinfo/mesa-dev|http://lists.freedesktop.org/mailman/listinfo/mesa-dev]] - Mesa / 3D support development. + + +### TV Out Support + +Please check [[radeonTV|radeonTV]] for information about TV out support. + + +### Dual-head Support + +See the [[XRandR 1.2 documentation|http://wiki.x.org/wiki/Projects/XRandR]] for how to set up multiple monitors. + + +## Known Issues + + +## History + +(moved from Latest News) + +* _6 Jul 2010_: **6.13.1**: server 1.9 support, evergreen accel disabled explicitly, kms uevent + sync support, rn50 fixes, enable color tiling on kms on r300->r500, xv cleanup and large vertex number fixes <small>[ [[changelog|http://lists.x.org/archives/xorg-driver-ati/2010-July/016250.html]] ]</small> +* _15 Mar 2010_: **6.12.192**: **6.13.0rc2**: Mostly bug fixes. The r6xx/r7xx domain fix improves KMS EXA DFS (and hence [[GetImage|GetImage]]) performance significantly. <small>[ [[changelog|http://lists.x.org/archives/xorg-driver-ati/2010-March/014354.html]] ]</small> +* _15 Mar 2010_: **6.12.6**: bug fix release. <small>[ [[changelog|http://lists.x.org/archives/xorg-driver-ati/2010-March/014353.html]] ]</small> +* _2 Mar 2010_: **6.12.191**: pre-release for the upcoming 6.13 release: KMS/DRI2 support, support for new hardware, basic power management, Displayport. <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2010-March/001265.html]] ]</small> +* _2 Mar 2010_: **6.12.5**: bug fix release. <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2010-March/001264.html]] ]</small> +* _10 Sep 2009_: **6.12.4**: brown paper bag release for X.org 7.5. <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001033.html]] ]</small> +* _9 Sep 2009_: **6.12.3**: bug fixes backported from master, along with PCI IDs for some new hardware. <small>[ [[changelog|http://lists.freedesktop.org/archives/xorg-announce/2009-September/001026.html]] ]</small> +* _17 Apr 2009_: AMD [[releases|http://lists.x.org/archives/xorg-driver-ati/2009-April/009362.html]] initial code branches for 3D support on R6xx/R7xx (see more below) +* _8 Apr 2009_: **6.12.2**: Bug fixes, and r2xx/r3xx textured video improvements. <small>[ [[changelog|http://lists.x.org/archives/xorg-driver-ati/2009-April/009192.html]] ]</small> +* _18 Mar 2009_: **6.12.1**: Bug fixes for R6xx/R7xx, and avivo load detection fix. <small>[ [[changelog|http://lists.x.org/archives/xorg-driver-ati/2009-March/008952.html]] ]</small> +* _13 Mar 2009_: **6.12.0**: EXA and Xvideo support for R6xx/R7xx series, and bug fixes. <small>[ [[changelog|http://lists.x.org/archives/xorg-driver-ati/2009-March/008886.html]] ]</small>
\ No newline at end of file diff --git a/radeon/package.zip b/radeon/package.zip Binary files differnew file mode 100644 index 00000000..d73897b9 --- /dev/null +++ b/radeon/package.zip diff --git a/radeonBuildHowTo.mdwn b/radeonBuildHowTo.mdwn new file mode 100644 index 00000000..18bcc779 --- /dev/null +++ b/radeonBuildHowTo.mdwn @@ -0,0 +1,563 @@ + +[[!toc ]] + + +# Building new version from git + +It is possible to compile either stable or development version of [[radeon|radeon]] from git. + +Changes to stable branch should be upgraded by distribution packages but in practice distributions don't follow the stable branch for released versions. If your distribution has failed to upgrade to the latest stable version you might get better stability by compiling new version from branch that matches your distribution version. + +Development branch (master) is for bleeding edge development where you might get regression but also better performance and features. But if you decide that new features are worth the possible regression and bugs that happen in development you are more than welcome to upgrade to the latest code base. It is good idea to join our irc channel #radeon@freenode to get help for possible problems in bleeding edge code. + + +## Stable branch + + +### xf86-video-ati (ddx) + +Upgrading to the latest bug fix code is simple because you don't have to upgrade only driver packages. First it is good idea to upgrade xf86-video-ati that provide 2D and mode setting code for xserver. You will need to clone the git repository from anongit.freedesktop.org. + + +[[!format txt """ +git clone git://anongit.freedesktop.org/xorg/driver/xf86-video-ati +"""]] +Now you have cloned the git repository but code that was checked out is master branch which includes the bleeding edge code changes. Sometimes development is done in another specific GIT branch, you can check remote branches via: + + +[[!format txt """ +git branch -r +"""]] +You can easily switch to other branches (here: cayman_accel) or back to the master branch: +[[!format txt """ +git checkout -b cayman_accel origin/cayman_accel +git checkout master +"""]] +Now you have to solve build dependencies for the driver. Your package manager should have easy functionality for installing all the necessary packages. But for example there is: + + +[[!format txt """ +apt-get build-dep xserver-xorg-video-ati (Debian/Ubuntu) +yum-builddep xorg-x11-drv-ati (Fedora) +"""]] +Now you have to configure and build the code like any other program. It is good practice to install driver without overwriting files installed by package manager. This can be done using few configuration option. We want to install driver to a clean place where it is easy to remove in case you want to get rid of it. +[[!format txt """ +./autogen.sh --prefix=/opt/xorg +make +sudo make install +"""]] +Then you need to add configuration instruct xserver to load your self compiled driver. Adding following lines to xorg.conf will do the trick. +[[!format txt """ +Section "Files" + ModulePath "/opt/xorg/lib/xorg/modules,/usr/lib/xorg/modules" +EndSection +"""]] +Now restart your xserver and have fun with new bug fixes :) + + +### Mesa3D + +The Mesa3D library provides OpenGL with software and hardware rendering. There are also more libraries related to hardware accelerated graphics. Installing mesa to a location outside /usr is a bit more tricky. Problem here is that it is hard to make AIGLX load the dri driver from a non-system location. + +There are multiple stable threads depending on your distribution so you should check your mesa version and renderer with **glxinfo** command. +[[!format txt """ +glxinfo | grep ^OpenGL | egrep 'version|renderer' +OpenGL renderer string: Mesa DRI R200 (RV250 4C66) x86/MMX/SSE2 TCL DRI2 +OpenGL version string: 1.3 Mesa 7.11.1 +"""]] +Checkout mesa from GIT master branch ("clone" the entire repository): +[[!format txt """ +git clone git://anongit.freedesktop.org/mesa/mesa + +cd mesa <--- Your local "copy" (your local GIT repository) +"""]] +Branches were named mesa_X_Y_branch where X is major and Y minor number (nomenclature changed with creation of 7.8 GIT branch). Switch to a specific GIT branch (here: 7.11): +[[!format txt """ +git checkout -b 7.11 origin/7.11 +"""]] +To see all GIT branches available, run 'git branch -r' within local GIT repository/branch. + +Now you need again build dependencies which you should install for package libgl1-mesa-dri (See the example above). After you have installed all build dependencies we have to configure, build and install mesa. Prefix is again /opt/xorg for easy clean up if something goes wrong. You can of course use what ever you prefer. Example case enables all ATI drivers, but you would only need radeon, one of the specific drivers for your own card (r200, r300 or r600) and swrast for software fall back in case of problems with DRI or Gallium driver. + + +[[!format txt """ +DRI_DRIVERS="radeon,r200" +GALLIUM_DRIVERS="r300,r600,swrast" +./autogen.sh --prefix=/opt/xorg --with-dri-drivers=$DRI_DRIVERS --with-gallium-drivers=$GALLIUM_DRIVERS +make +sudo make install +"""]] +HINT: Software rasterizer (swrast) dri driver is used as fallback solution. + +**Remember to read the instruction how to configure loading of new driver** + + +## Configuring system to load mesa and libdrm from /opt/xorg + +Now comes the tricky part because you have to configure your system to load correct libraries when any application tries to load them. You have to configure ld to load first from /opt/xorg/lib so custom mesa libraries are loaded. Another tricky part is to load dri driver which requires environment variable set to point to /opt/xorg/lib/dri. + +/etc/ld.so.conf.d/a-local-xorg.conf (new file) or add to begin of /etc/ld.so.conf if directory doesn't exists. +[[!format txt """ +/opt/xorg/lib +"""]] +and to /etc/environment you need to add new environment variable that tells libgl where to look for dri drivers (example r300_dri.so) +[[!format txt """ +LIBGL_DRIVERS_PATH=/opt/xorg/lib/dri/ +"""]] +After changes to the files you have to run **ldconfig** as root to update the linker cache. + +You can now test new dri driver in a terminal if you export **LIBGL_DRIVERS_PATH**. If everything works you can now restart to load new settings for all applications. + +Problem with this configuration is that AIGLX doesn't respect it. This means that compiz doesn't get advantage of new driver. + +It is possible to get the new libGL and dri drivers used without setting LIBGL_DRIVERS_PATH: + +* you need to build mesa with --with-dri-driverdir=/opt/xorg/lib/dri/ (or --with-dri-driverdir=/opt/xorg/lib/dri/ for 32-bit) +* check that /opt/xorg takes precedence: + +[[!format txt """ +ldconfig -p | grep libGL.so + libGL.so.1 (libc6,x86-64, OS ABI: Linux 2.4.20) => /opt/xorg/lib/libGL.so.1 + libGL.so.1 (libc6,x86-64, OS ABI: Linux 2.4.20) => /usr/lib/libGL.so.1 + libGL.so (libc6,x86-64, OS ABI: Linux 2.4.20) => /opt/xorg/lib/libGL.so +"""]] +* if system's libGL takes precedence it might be due to OS ABI, in that case build mesa with --enable-glx-tls + +## Before GettingStarted: Avoid known pitfalls + +Distribution packages have often extra patches applied which might break compatibility with git sources. In that case you would have to get distro patches and apply them on top of source from git. +### Checking for hardware 3D acceleration + +glxinfo will give details about OpenGL rendering. Old fashioned guides for checking "direct rendering: Yes" are long outdated because swrast software rasterizer can do direct rendering. +[[!format txt """ +glxinfo | grep OpenGL +"""]] +Important part of output is renderer string that should read Mesa DRI <dri driver> <details> +[[!format txt """ +OpenGL renderer string: Mesa DRI R200 (RV280 5C61) 20090101 x86/MMX+/3DNow!+/SSE TCL DRI2 +"""]] +While software will output: +[[!format txt """ +OpenGL renderer string: Software Rasterizer +"""]] + +### Removing AMD/ATI proprietary Linux display driver + +You have to first remove fglrx because it overwrites our userspace files and conflicts with our kernel modules. Maybe some day drivers can coexists but not yet :/ + +First remove all fglrx packages and check that fglrx.ko is not left in /lib/modules/`uname -r`. If it is there you can just rm it and do depmod -a. + +Next step is to reinstall mesa and libdrm. Which should be handled easily by your package manager or make install. + +Last but not least is removing fglrx configurations from xorg.conf. With xserver 1.6 or higher you can just rename xorg.conf and trust the auto detect to do the right things. + +Now you can reboot to clean system when open driver can function correctly. + +For Debian systems: +[[!format txt """ +apt-get update +apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri <--- libGL.so + mesa3d DRI drivers +"""]] +**WARNING:** The proprietary drivers from AMD/ATI and nVidia are known to overwrite Xserver extensions, for example GLX extension (libglx.so)! +[[!format txt """ +apt-get install --reinstall xserver-xorg-core <--- libglx.so of xserver +"""]] + +## Updating git tree + +Updating git repository has two phases. First part is downloading changes and updating the history data for git. Second part is updating your local branch to match remote changes. +[[!format txt """ +git fetch && git rebase origin +"""]] +If you have any build problems after updating your source code run **make clean and autogen.sh**. + + +## Removing self compiled driver + +If you at any reason want to get rid of your self compiled driver it is simple as removing the configuration option from xorg.conf, /etc/ld.so.conf.d/ and environment. Then you can just restart computer and you are back at using the driver from package manager. + +Removing the extra libraries is also easy with rm -r /opt/xorg. + + +## Bleeding edge code from development branch + +You will most likely have to upgrade a lot of stuff depending on how fresh your distro is. But minimum requirement is to have the latest xserver from the latest stable branch, latest stable kernel (some features might be only in rc kernels), libdrm master, mesa master and xf86-video-ati master. + +Compiling and configuration is similar to stable branch with few exceptions. + +* You may have to configure libdrm with --enable-radeon-experimental-api (If your distribution enables it or you want to use KMS) +* create /opt/xorg/share/aclocal +* libdrm [[http://cgit.freedesktop.org/mesa/drm/|http://cgit.freedesktop.org/mesa/drm/]] has to be build and installed before mesa or ddx +* You will need extra environment variables so configure script will find all self compiled dependencies + +[[!format txt """ +export PKG_CONFIG_PATH=/opt/xorg/lib/pkgconfig:/opt/xorg/share/pkgconfig +export LDFLAGS=-L/opt/xorg/lib CPPFLAGS=-I/opt/xorg/include +export ACLOCAL="/usr/bin/aclocal -I /opt/xorg/share/aclocal" +"""]] +**UPDATE: With libdrm >= 2.4.18 libdrm_radeon is built by default, now** (configure-option --enable-radeon-experimental-api is obsolete). + +[1] See commit 520c658706aa896d64f374cc74065394111f6122 [["radeon: enable by default now that kms is out of staging"|http://cgit.freedesktop.org/mesa/drm/commit/?id=520c658706aa896d64f374cc74065394111f6122]]. + + +### Distro-specific development packages + +Some distributions provide easy way to install development version of all required packages from single source. This makes beta testing a lot easier when you can get fresh packages without recompiling everything. + +* Ubuntu: xorg-edgers provides good packages nearly daily. [[https://launchpad.net/~xorg-edgers/+archive/ppa|https://launchpad.net/~xorg-edgers/+archive/ppa]] +* Debian: Brice Goglin provided packages with KMS and DRI2 support in experimental branch, see his blog [["Debian/X.org notes - Radeon KMS and DRI2 in experimental"|http://bgoglin.livejournal.com/19346.html]]. + +## Kernel-based ModeSetting + +Kernel-based [[ModeSetting|ModeSetting]] (short: KMS) moves a lot of graphics card control logic to kernel which makes it possible to write more advanced 3D and 2D drivers. Kernel side mode setting improves VT switching and provides full resolution console. + +KMS also moves DRI infrastructure to version 2 which will provide better performance for 3D drivers in future. But as always is case in large rewrite of basic infrastructure performance will go down at first because of missing features and not optimized code. + +Current features in kernel side are + +* Mode setting +* Memory management +* Scheduling access to graphics card +After mode setting and memory management part has been finished there will be work to make dynamic power management work. + + +### Prerequisites for radeon-KMS + +For a better understanding of the correlation of all involved software components please have a closer look at Yang "yangman" Zhao's blog-article: [["Linux Graphics Driver Stack Explained"|http://yangman.ca/blog/2009/10/15/linux-graphics-driver-stack-explained/]]. + +Basic and minimum requirements and recommendations (Update from 15-Apr-2012): + +* **Linux-kernel** r100-r500 >=2.6.32 | r600/r700 >=2.6.33 | evergreen >=2.6.34 (initial support) | latest-3.0: 3.0.28 | latest-3.2: 3.2.15 | latest-stable: 3.3.2 +* **libdrm** >=2.4.18 (minimum) | latest-stable: 2.4.33 +* **mesa** r100-r500 >=7.7.x | r600/r700 >=7.8.x | latest-7.11: 7.11.2 | latest-8.0: 8.0.2 +* **ddx (aka xf86-video-ati)** >=6.13.x | latest-stable: 6.14.4 +* **xorg-server** >=1.6.2 (minimum) | preferred >=1.7.x | latest-1.10: 1.10.6 | latest-1.11: 1.11.4 | latest-1.12: 1.12.1 +NOTE-1: With Linux-2.6.33-rc6-git1 drm-radeon-kms has left staging driver area, see commit [["drm/radeon/kms: move radeon KMS on/off switch out of staging."|http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f71d0187987e691516cd10c2702f002c0e2f0edc]]. + +NOTE-2: For r600+ (r600 and higher) you might need [[extra firmware|radeonBuildHowTo]]. + +NOTE-3a: Initial evergreen 3D-acceleration support: For DDX see commit [["Merge branch 'evergreen_accel' of git+ssh://git.freedesktop.org/git/xorg/driver/xf86-video-ati"|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=be8f45cbd313b68ad663f303c64edb4525b8f981]] and for Mesa see commit [["r600g: add initial evergreen support"|http://cgit.freedesktop.org/mesa/mesa/commit/?id=50526e094f4c66957c7f74c190c35903bc82fb62]] + +NOTE-3b: Evergreen 3D-acceleration: Recommended: Linux-kernel >=2.6.38 + xf86-video-ati >=6.14.1 + mesa >=7.10.2 (r600 classic and gallium have 3D-acceleration whereas r600g is these days preferred) + +NOTE-4: Linux v2.6.32.y and v3.0.y kernels have longterm support (LTS). + +NOTE-5: Linux v3.2.y kernels will be shipped with upcoming Ubuntu 12.04 (LTS) and Debian wheezy (and maintained by Ubuntu/Debian kernel-teams). + +NOTE-6: Experimental Trinity (TN) APU support: Linux-kernel >=3.4-rc1, latest-stable libdrm + ddx and mesa from Git master. + + +### Important Linux kernel config parameters to enable radeon-KMS + + +[[!format txt """ +CONFIG_DRM_RADEON=m +CONFIG_DRM_RADEON_KMS=y +CONFIG_FRAMEBUFFER_CONSOLE=y +# CONFIG_FB_RADEON is not set +"""]] +NOTE-1: A radeon kernel-module gives more flexibility (e.g. debug), for built-in solution change CONFIG_DRM_RADEON from "=m" to "=y". + +NOTE-2: Disable old radeon framebuffer device, new is usage of kernel framebuffer device (fbcon) and radeondrmfb driver. + + +### Packages to solve build dependencies + +Unfortunately, it highly depends on your distribution on having all required development packages and libraries installed. + + +#### Solve build-deps using package-manager + +The best (first) strategy is to solve the build dependencies using the distribution's package-manager. + +For Debian distribution this would be: +[[!format txt """ +apt-get build-dep libdrm <--- Userspace interface to kernel DRM services (development files, radeon-specific, etc.) +apt-get build-dep mesa <--- A free implementation of the OpenGL API (DRI modules, GLX runtime, GLX development files, etc.) +apt-get build-dep xserver-xorg-video-ati <--- X.Org X server -- AMD/ATI display driver +apt-get build-dep xorg-server <--- Xorg X server (core server, development files, etc.) +"""]] +Anyway, this might work or not. If the packages in the distribution's repository are too old, consult first your distro's support for help. + +Other solutions that might help: For example in Debian there exists also an experimental distribution repository with latest software. In the worst case... There could be new stuff in the distro's own SCM (GIT or SVN) repositories, where you have to checkout and build by yourself. + + +#### Solve build-deps manually + +That is really hard to say... It mostly depends on the freshness of your distribution and its included packages. + +Here, the strategy would be to look into the configure* and Makefile* scripts and/or to start compiling each package and check for error-messages. This is *no* fun. + +To make it a bit easier, we have a look into the build-order and into the build.sh script from xorg-devel (see [1]): + +1. macros +1. protos +1. libdrm (*before* ddx and mesa) +1. ddx (aka xf86-video-ati) +1. (mesa) <--- Optional, only if you want 3D-acceleration +1. xserver +Again, within the diverse GIT repos there are explicitly depends on other development packages and/or libraries. You have to solve them first! Easiest way would be to check out and build via the recommended script from [1]. As GIT software is mostly Work-In-Progress, you might ran into other problems. A good orientation if the diverse components do build from GIT together is to look at the so-called "tinderbox" [2] (build failures are listed). + +Another *rough* way is to check out from GIT and create missing packages in the distro's format (deb, rpm or whatever). + +Please, also have a closer look at "[[ModularDevelopersGuide|ModularDevelopersGuide]] - The X.Org Modular Tree Developer's Guide" [3]. + +[1] [[http://cgit.freedesktop.org/xorg/util/modular/tree/build.sh|http://cgit.freedesktop.org/xorg/util/modular/tree/build.sh]] + +[2] [[http://tinderbox.x.org/|http://tinderbox.x.org/]] + +[3] [[http://wiki.x.org/wiki/ModularDevelopersGuide|http://wiki.x.org/wiki/ModularDevelopersGuide]] + + +### Experimental patches and development repositories + +The kernel-related DRM development flow in Dave Airlie's linux GIT repository [1]. + +[1] [[http://cgit.freedesktop.org/~airlied/linux|http://cgit.freedesktop.org/~airlied/linux]] + + +#### List of active GIT branches in DRM kernel repository + +Dave Airlie gives an overview over all the drm-related development GIT branches in his email [["drm git branches revisited"|http://article.gmane.org/gmane.comp.video.dri.devel/40626]] to dri-devel mailing-list. + +Dave decided to move to freedesktop GIT platform after <kernel.org> suffered a [[security breach|https://www.linuxfoundation.org/news-media/blogs/browse/2011/08/cracking-kernelorg]]. + + +#### drm-next experimental branch + +Especially drm-next GIT branch has the latest (experimental) stuff for radeon users. + +Checkout drm-next GIT branch: +[[!format txt """ +git clone git://people.freedesktop.org/~airlied/linux +cd linux +git checkout -b drm-next origin/drm-next +"""]] +How to build kernel is not part of this guide because it is distribution specific. You should check your distribution documentations for guidance. + +To be in "sync" with this experimental kernel, it is also recommended to have libdrm, mesa and ddx from GIT master. + + +#### Additional patches for reviewing and testing + +Patches are sent to dri-devel and mesa3d-dev mailing-list (see [1] and [2]), before they are acknowledged and accepted in the diverse GIT branches. + +[1] [[http://lists.freedesktop.org/archives/dri-devel/|http://lists.freedesktop.org/archives/dri-devel/]] [2] [[http://lists.freedesktop.org/archives/mesa-dev/|http://lists.freedesktop.org/archives/mesa-dev/]] + + +# Troubleshooting + + +## radeon-KMS issues + + +### Module for frame buffer console + +First of all check that you **don't** load _radeonfb_, _uvesafb_ or _vesafb_ module. This includes no vga parameters for kernel when using KMS. Console is provided by **fbcon** and **radeondrmfb** frame buffer console. So it is best to make sure that fbcon module is loaded. + + +### Hints to dig deeper into radeon-KMS problems on startup + +If you can't boot with KMS enabled the easiest way to debug problems is to boot into runlevel-3 (text console, VT) with KMS disabled or blacklist the radeon kernel-module. Then try to unload/load drm and radeon kernel-modules via modprobe commands (preferable over ssh and from a second machine). + +Booted into runlevel-3 (grub-line: Append "radeon.modeset=0" means KMS disabled): +[[!format txt """ +modprobe -r -v drm radeon <--- Unload drm and radeon kernel-module (-r: remove, -v: verbose) +modprobe -v drm debug=1 <--- Additional for debugging DRM issues (maximum debug-level is 15) +modprobe -v radeon modeset=1 <--- Load radeon kernel-module with KMS support +"""]] +NOTE-1: Depending on your distribution you have to use "radeon.modeset=0,1" (0: KMS disabled, 1: KMS enabled) or "nomodeset" and "modeset=1". + +NOTE-2: Some distributions like Debian have no runlevel-3 defined, so blacklist the radeon kernel-module (or disable the start of graphical login-manager like kdm or gdm). + + +### Check if radeon-KMS is enabled before X is started + +First, make sure the radeon kernel-module is loaded with KMS enabled before X is started. + +There are several possibilities to enable drm-radeon-kms on startup: + + +#### Append parameter to boot-menue + +Append "radeon.modeset=1" as a parameter to grub/grub2 line (so called "Kernel command line"). + + +#### Add to grub2 configuration + +Use /etc/default/grub for this (edit file or run the echo-line below), followed by a renew of /boot/grub/grub.cfg (entries for boot-menue) via 'update-grub' command. +[[!format txt """ +echo 'GRUB_CMDLINE_LINUX="radeon.modeset=1"' >> /etc/default/grub <--- or edit the file and change manually +update-grub +"""]] + +#### Activate via radeon.conf in /etc/modprobe.d directory + +A good place to put persistent parameters for kernel-modules in general is /etc/modprobe.d directory, for radeon kernel-module use /etc/modprobe.d/radeon.conf. +[[!format txt """ +cat /etc/modprobe.d/radeon-kms.conf +options radeon modeset=1 +"""]] +When KMS is *not* enabled before X is started, you might see the following error in your Xorg.log file (thanks TMM for providing a paste on IRC): +[[!format txt """ +(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. +[dri] This chipset requires a kernel module version of 1.17.0, +[dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. +[dri] If using kernel modesetting, make sure your module is +[dri] loaded prior to starting X, and that this driver was built +[dri] with support for KMS. +[dri] Disabling DRI +"""]] + +### radeon-KMS with AGP gfxcards + +AGP gfxcards have a lot of problems so if you have one it is good idea to test PCI/PCIE mode using **radeon.agpmode=-1**. Another common solution to agp problems is disabling accelerated download from screen. You can see details with **man exa** how to do this. + + +### Missing firmware + +This is not a KMS problem, but people often report X does *not* start (thus it's included in the troubleshooting list). The real cause for this is the drm cannot find a missing radeon firmware (or microcode). This depends on the Linux-kernel version you use. To fix this issue simply install the package containing the radeon firmware files or consult your distribution's support. + + +[[!format txt """ +dmesg | egrep -i 'firmware|microcode' +"""]] + +### Check if your ddx and mesa-dri driver have KMS support + +Your xf86-video-ati video-driver for X (the "DDX", 2D) doesn't have support for KMS? NO, then you have to rebuild it against libdrm_radeon library. + +As a consequence this also means that you have to **rebuild mesa** against same new libdrm. Mesa-dri drivers (3D, accelerated) don't have KMS support without built against libdrm_radeon either. + +Furthermore, check if you have fitting components of the Linux graphics driver stack. + + +[[!format txt """ +sudo lsof | grep ^Xorg | egrep '_drv.so|_dri.so' | egrep 'radeon|r?00' +Xorg 19919 root mem REG 8,2 13107136 302055 /usr/lib/dri/r300_dri.so +Xorg 19919 root mem REG 8,2 1000892 554894 /usr/lib/xorg/modules/drivers/radeon_drv.so + +sudo egrep '_drv.so|_dri.so' /var/log/Xorg.0.log | egrep 'radeon|r?00' +(II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so +(II) AIGLX: Loaded and initialized /usr/lib/dri/r300_dri.so + +sudo ldd /usr/lib/dri/r?00_dri.so | grep radeon + libdrm_radeon.so.1 => /usr/lib/libdrm_radeon.so.1 (0xb7447000) + +sudo ldd /usr/lib/xorg/modules/drivers/radeon_drv.so | grep radeon + libdrm_radeon.so.1 => /usr/lib/libdrm_radeon.so.1 (0xb75da000) +"""]] +The output of ldd commands should clearly indicate a link to libdrm_radeon. + + +## Missing Extra Firmware + +All radeon gfxcards r600+ (r600 and higher) require extra firmware (ucode) files [1] to work properly with acceleration (Thanks agd5f for clarification on IRC). According to license issues [2] and the fact that no new firmware files will be shipped in upstream kernels, you need to activate the following kernel-config parameters: + + +[[!format txt """ +CONFIG_FIRMWARE_IN_KERNEL=y +CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" +CONFIG_EXTRA_FIRMWARE="radeon/CEDAR_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin radeon/CYPRESS_me.bin radeon/CYPRESS_pfp.bin radeon/CYPRESS_rlc.bin radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin radeon/JUNIPER_rlc.bin radeon/R600_rlc.bin radeon/R700_rlc.bin radeon/REDWOOD_me.bin radeon/REDWOOD_pfp.bin radeon/REDWOOD_rlc.bin" +"""]] +You can omit those firmware files for which you do not actually have hardware. Copy *.bin to /lib/firmware/radeon directory. + +UPDATE: Extra ucode files are now in linux-firmware GIT repository [3] (Thanks airlied for information on IRC). + +[1] [[http://people.freedesktop.org/~agd5f/radeon_ucode/|http://people.freedesktop.org/~agd5f/radeon_ucode/]] + +[2] [[http://people.freedesktop.org/~agd5f/radeon_ucode/LICENSE.radeon|http://people.freedesktop.org/~agd5f/radeon_ucode/LICENSE.radeon]] + +[3] See commit d9076a54d74e371a11e1206b4a26e2e428045b9e [["radeon: add RLC firmwares from AMD."|http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=commit;h=d9076a54d74e371a11e1206b4a26e2e428045b9e]] + + +## Use 32-bit GL applications on 64-bit systems + +32-bit applications (such as wine) will need a 32-bit libGL and mesa dri drivers. If you've only built the 64-bit libraries, your 32-bit apps may still be using the distro provided 32-bit libGL and dri (if you have already installed them), which will probably just result in slowness and wrong image being displayed. + +To make 32-bit apps use the new driver (the examples below show 64-bit libs installed in /lib (Debian), your distro may install to /lib64 instead (Fedora and others): + +* build libdrm from git (here for Debian 64-bit, Info: The original libdrm libs from ia32-libs package will be replaced): + +[[!format txt """ +./autogen.sh --prefix=/usr --libdir=/usr/lib32 CFLAGS="-m32 -O2 -g" +"""]] +* build mesa as 32-bit: + +[[!format txt """ +DRI_DRIVERS="radeon,r200,r300,r600,swrast" +DRI_DRIVER_DIR="/opt/xorg/lib32/dri" +./autogen.sh --prefix=/opt/xorg --with-dri-drivers=$DRI_DRIVERS --with-dri-driverdir=$DRI_DRIVER_DIR --enable-32-bit --libdir=/opt/xorg/lib32 --disable-gallium --enable-glx-tls +make +sudo make install +"""]] +* Run ldconfig to update dynamic linker run-time bindings: + +[[!format txt """ +sudo ldconfig +"""]] +* Check that the desired libGL is used - libGL from /opt/xorg should be first in all cases: + +[[!format txt """ +sudo ldconfig -p | grep libGL.so + libGL.so.1 (libc6,x86-64, OS ABI: Linux 2.4.20) => /opt/xorg/lib/libGL.so.1 + libGL.so.1 (libc6,x86-64, OS ABI: Linux 2.4.20) => /usr/lib/libGL.so.1 + libGL.so.1 (libc6, OS ABI: Linux 2.4.20) => /opt/xorg/lib32/libGL.so.1 + libGL.so.1 (libc6, OS ABI: Linux 2.4.20) => /usr/lib32/libGL.so.1 + libGL.so (libc6,x86-64, OS ABI: Linux 2.4.20) => /opt/xorg/lib/libGL.so + libGL.so (libc6, OS ABI: Linux 2.4.20) => /opt/xorg/lib32/libGL.so + libGL.so (libc6, OS ABI: Linux 2.4.20) => /usr/lib32/libGL.so +"""]] +* Check that the new 32-bit (mesa) dri driver is loaded: + +[[!format txt """ +$mesa32-builddir/progs/xdemos/glxinfo | grep OpenGL +OpenGL vendor string: Advanced Micro Devices, Inc. +OpenGL renderer string: Mesa DRI R600 (RV730 9498) 20090101 x86/MMX/SSE2 TCL DRI2 +OpenGL version string: 2.0 Mesa 7.8-devel +OpenGL shading language version string: 1.10 +OpenGL extensions: +"""]] + +## radeon-KMS power-management + +Linux-kernel >=2.6.35 has now power-management code for radeon gfxcards R100-R700 (see [1]). + +NOTE: Linux-kernel(s) from upstream or drm-next GIT branch might have better support (WIP). + + +### Change power-management method + +There exist two basic power-management (short: PM) methods "dynpm" and "profile" set via sysfs: +[[!format txt """ +echo "dynpm" > /sys/class/drm/card0/device/power_method +or +echo "profile" > /sys/class/drm/card0/device/power_method + +cat /sys/class/drm/card0/device/power_method +profile +"""]] +The "profile" method exposes 4 profiles that can be selected from: 1. "default" 2. "auto" 3. "low" 4. "high" In the meantime there has been a 5th "mid" profile introduced (see [2]). + +How to get/select the PM profile method? +[[!format txt """ +cat /sys/class/drm/card0/device/power_profile +default +echo "low" > /sys/class/drm/card0/device/power_profile +"""]] +WARNING: !!! the low power management setting does not work properly with displays active on some laptops !!! + +NOTE: See also [[KMS Power Management Options|http://wiki.x.org/wiki/RadeonFeature#KMS_Power_Management_Options]] + +[1] [[http://lists.freedesktop.org/archives/dri-devel/2010-May/000492.html|http://lists.freedesktop.org/archives/dri-devel/2010-May/000492.html]] [2] [[http://www.spinics.net/lists/dri-devel/msg01028.html|http://www.spinics.net/lists/dri-devel/msg01028.html]] + + +# Reporting bugs + +If problem is 3D relate correct place to report it is [[https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa|https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa]]. + +Because driver is split between DDX and Mesa all 2D and xv related problems should be reported to [[https://bugs.freedesktop.org/enter_bug.cgi?product=xorg|https://bugs.freedesktop.org/enter_bug.cgi?product=xorg]]. + +You should include **xorg.log** and **dmesg** at minimum. Also exact steps to reproduce the problem will help a lot in solving the problem. Any extra debugging info you have gathered is welcome too. Please select text/plain mime type for any text attachments so they are easier to read. + +**Debug symbols** are important when submitting backtraces so you should take little bit time to install them. There is usually easy way to install them from distribution provided packages. Minimum for debug symbols is mesa, ddx and xorg core to give easily readable backtraces. diff --git a/radeonTV.mdwn b/radeonTV.mdwn new file mode 100644 index 00000000..87e18392 --- /dev/null +++ b/radeonTV.mdwn @@ -0,0 +1,101 @@ + + +# Radeon TV-Out + +In 2007 Alex Deucher added preliminary TV-Out-support based on the gatos-code to the randr12-branch of the ati-driver. The branch has now been merged to the [[git HEAD of xf86-video-ati|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/]]. + + +## Driver Releases + +Starting from the 6.7.191 pre-release the X.org ati driver supports TV-Out on selected cards. That means stable version [[6.8.0|http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.8.0.tar.bz2]] and newer have the support. A new enough driver is also included starting in eg. Fedora 8 and Ubuntu 7.10. + + +## How to build + +See [[RadeonTVbuildHowto|RadeonTVbuildHowto]]. + + +## How to use + +You can enable TV-Out either dynamically (by issuing commands to the running X server) or statically (through the xorg.config file, before starting the X server). For testing, the dynamic method is probably easier. + + +### How to use: R5xx / R6xx / R7xx + +Newer R600 / R700 series cards (Radeon HD X2000 - X4870) need this option in xorg.conf: + +* [[!format txt """ +Option "ATOMTvOut" "TRUE" +"""]] +The same Option can be applied to R5xx cards too (or at least some of that series). It has been checked to work on x1650 (RV530LE) - this line really needed to detect S-Video tv-out. + + +### Enabling TV-Out Dynamically + +TV-out may be enabled by using a recent driver and xrandr utility: + +1. xrandr --addmode S-video 800x600 +1. xrandr --output S-video --mode 800x600 +1. xrandr --output S-video --set "tv standard" ntsc + +### Enabling TV-Out Statically + +Several options need to be specified. See the radeon(4) manpage for a description. In particular, you must set "TVStandard" to match your flavour of video. + +This recipe is not definitive, but it has worked. + +In the "Device" section: + +* [[!format txt """ + Driver "radeon" + Option "TVDACLoadDetect" "TRUE" + Option "TVStandard" "ntsc" + Option "monitor-S-video" "TV-monitor" +"""]] +In the "Monitor" Section: + +* [[!format txt """ + Option "PreferredMode" "800x600" +"""]] +In the "Screen" section: + +* [[!format txt """ + DefaultDepth 24 + SubSection "Display" + Depth 24 + Modes "800x600" + EndSubSection +"""]] + +## History + + +### How we got here from the GATOS Patch + +There was a very old effort by the gatos-project to support TV Out on ATI Radeons. It was GPL-licensed in the past, but in 2007 all authors agreed with relicensing under MIT-license, so that it was brought to a xf86-video-ati's branch and later on merged to the main driver. + +[[randr-1.2 branch of xf86-video-ati|http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/log/?h=randr-1.2]] + +[[arklinux-patch (latest)|http://arklinux.org/~bero/xf86-video-ati-6.6.192-tvout.patch]] + +[[Gentoo bug with updated patch|https://bugs.gentoo.org/show_bug.cgi?id=127642]] + +[[Update to below patch by Wei-Tsun Sun|http://www.ece.auckland.ac.nz/~wsun013/tvout/index.html]] + +[[Patch up to xorg 7.0 by Rune Petersen|http://megahurts.dk/rune/tv_output.html]] + +[[Original gatos code|http://gatos.sourceforge.net/theater_out.php]] + + +#### Relicensing + +[[Frederico Ulivi (original author) agreed to relicense the code under a MIT-license (which allows inclusion in the xorg-driver)|http://sourceforge.net/mailarchive/forum.php?thread_name=20070612082434.HM.0000000000001On@fulivi.bos-mail-wwl15.lycos.com&forum_name=gatos-devel]] + +[[All others agreed to the relicensing|http://sourceforge.net/mailarchive/message.php?msg_name=200707250044.20812.ml@hboeck.de]] + + +### atitvout + +On some older cards the tv out can be enabled with atitvout, which is not developed anymore: + +[[atitvout by Lennart Poettering|http://0pointer.de/lennart/projects/atitvout/]] diff --git a/radeonhd.mdwn b/radeonhd.mdwn new file mode 100644 index 00000000..20b78119 --- /dev/null +++ b/radeonhd.mdwn @@ -0,0 +1,520 @@ + + +# radeonhd - A Driver for AMD GPG r5xx/r6xx/r7xx Chipsets + +The _radeonhd_ driver, or _xf86-video-radeonhd_, is an X.org video driver for codenamed R500-R700 graphics devices. It was developed by the X11 community, mostly centered around Novell and AMD, with the free documentation provided by AMD. + +The driver supports full modesetting (read: any mode is usable, not only those provided by the BIOS), and is compatible to [[RandR 1.3|Projects/XRandR]]. 2D and Xv (video) acceleration is provided for all supported GPUs; 3D acceleration via Mesa is supported for r5xx/rs690 GPUs (X1xxx) and is in progress for r6xx/r7xx GPUs (HD2xxx-HD4xxx). + +**Status 09/2010**: Linux distributions, including Novell's openSUSE, have now abandoned radeonhd as the default driver, instead using the [[radeon|radeon]] driver. radeon has more features, including Kernel Mode-Setting support and more 3D support, and it supports all Radeon generation from original R100 Radeons to R800 Radeons (HD 5000 series). Radeonhd can be continued to be updated as long as there are people find it useful. + +[[!toc 1]] + +Subpages: + +* [[radeonhd packages for your distribution|radeonhd:packages]] +* [[how to install from latest git|radeonhd:INSTALL]] +* [[how to setup 2D acceleration for r6xx/r7xx|radeonhd:r6xx_r7xx_branch]] +* [[how to setup DRI|radeonhd:DRI]] +* [[how to setup 3D for r6xx/r7xx|radeonhd:experimental_3D]] (**experimental**) +* [[r600_demo: experimental 3D engine bringup tool|radeonhd:r600_demo]] +* [[r[67]xx Errata Sheet and explanations of difficult GPU subsystems|radeonhd:r6xxErrata]] +* [[list of things to do|radeonhd:TODO]] +* [[feature list|radeonhd:feature]] + +# Recent Changes + +**Version 1.3.0** + +* Added support for RV740, M92, M93, M97. +* Added support for HDMI audio on RS690 and R700. +* Added support for power management. +* Implemented almost correct analysis of [[PowerPlay|PowerPlay]] AtomBIOS tables. +* 2D acceleration (EXA) is enabled by default now, except on RV740. +* Backlight handling finally fixed - compatible with xbacklight 1.1.1. +* Overhaul of memory controller setup. Fixes many "MC not idle" issues. +* Overhaul of cursor handling. Fixes most cursor bugs. +* Selectable color space for XVideo on R6xx/R7xx. +* Tons of bug fixes (DDC, EXA, LUT, RandR, AtomBIOS). +* More quirk table entries. +* Shave support (cleaner compilation output). +* All warnings fixed. +* Some start of Developer's documentation in README.coding. +**Version 1.2.5** + +* Added 2D acceleration for R6xx and R7xx (disabled by default). +* Added XVideo support for R6xx and R7xx (disabled by default). +* Added support for RS880 and RV790. +* Added RandR 1.3 mandatory properties. +* Refactoring of MC code. +* Enable DRI support by default on R5xx and RS6xx. +* LUT (color lookup table) fixes. +* Tons of quirk table entries and bug fixes. +* Fix register accesses for processors that reorder memory writes. +**Version 1.2.4** + +* Added HDMI support. +* Added support for RV710, RV730 (DCE 3.2). +* Added screen rotation support. +* Added RandR 1.3 panning support. +* Many acceleration and build fixes. +**Version 1.2.3** + +* Added Command Submission infrastructure. +**Version 1.2.2** + +* Added [[DRI|radeonhd:DRI]] support (R5xx and RS6xx). +* Added support for RV770, RS780, M82, M86, and M88. +* Added XVideo support. +* Added CP based 2D acceleration (R5xx and RS6xx). +* Added EXA render acceleration (R5xx and RS6xx). +* Added support for AtomBIOS based mode setting. +* Added support for scaled modes. +* Added RandR support for backlight control. +* Lots of modesetting related bug fixes. +**Version 1.2.1** + +* Build-fixes for systems without -DNDEBUG, and for rhd_dump +* Added two new RV670 devices. +**Version 1.2.0** + +* Added support for RV620, RV635, and R680. +* Added 2D acceleration for R5xx (including RS6xx), both XAA and EXA. +* Added support for DDIA block (second digital output) on RS690. +* Added support for interlaced modes +* Added additional layers for splitting outputs into encoders and transmitters as needed for new hardware. +* Added support for [[DragonFly|DragonFly]] BSD. +* Improved RandR corner cases. +* Improved handling of secondary cards. +* Implemented foundation work for future TV support. +* Huge number of bugfixes and minor updates. + +# Supported Hardware + +The _radeonhd_ driver supports video cards based on + +* R500 style hardware: R5xx, RV5xx, RS6xx, RS740, M52 and up +* R600 style hardware: R6xx, RV6xx, RS780, M64 and up +* R700 style hardware: RV7xx +Note that this simple classification of the chipsets isn't exactly correct, because often the individual components are of different generations, especially on mobility chipsets. + +See [[supported chipsets in radeonhd git HEAD|http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=blob_plain;f=README]] for up to date detail information. + + +# Development + +Development of the driver is driven by the community, with several of the developers funded by Novell and AMD. If you want to contribute to this project, [[join the mailing list|mailto:radeonhd+subscribe@opensuse.org]], and have a look at the [[list of things to do|radeonhd:TODO]] and the [[open bugzilla entries|https://bugs.freedesktop.org/buglist.cgi?query_format=advanced&product=xorg&component=Driver%2Fradeonhd&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED]]. + +You do not necessarily have to be a coder to help, there is documentation to be done, users to be helped, you name it. That said, the radeonhd driver project is - as almost all open software development projects - understaffed and likes to welcome any contributions. + + +# More Information + +The mailing list for the _radeonhd_ driver is [[radeonhd@opensuse.org|mailto:radeonhd@opensuse.org]] , you can subscribe to this mailing list by sending a mail to [[radeonhd+subscribe@opensuse.org|mailto:radeonhd+subscribe@opensuse.org]]. More information on this mailing list at [[http://lists.opensuse.org/radeonhd/|http://lists.opensuse.org/radeonhd/]]. + +Overview of recent updates to _radeonhd_: [[http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd|http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd]]. + +There is also an IRC channel #radeonhd on freenode.net. IRC logs at [[phoronix' radeonhd.org|http://radeonhd.org/]]. + +The [[radeonhd:packages|radeonhd:packages]] page lists your source for dep, rpm, etc. packages. + +ATI is providing [[free documentation|http://ati.amd.com/developer/open_gpu_documentation.html]] for the chips. Beware, this is _extremely_ technical. The documentation is [[mirrored on X.org|http://www.x.org/docs/AMD/]]. For r[67]xx development information see also the [[r600_demo|radeonhd:r600_demo]] subpage. + +For an alternative X.org driver see _[[radeon|radeon]]_. In addition r500-r700, it also supports older Radeons and is developed by partially different people. It is currently the default X.org driver. Both _radeon_ and _radeonhd_ have an overlapping feature set, and both should support all r500-r700 cards. If either does not work for you, try the other one. Co-operation is happening in both directions. More information about various available drivers for r500-r700 on the [[radeon|radeon]] page, section ”[[What about other drivers?|radeon]]”. + + +# Getting and updating the radeonhd source code + +Released radeonhd tarballs can be downloaded from **[[ftp://ftp.freedesktop.org/pub/individual/driver/|ftp://ftp.freedesktop.org/pub/individual/driver/]]** + +The name of the tarball will be xf86-video-radeonhd-<version>.tar.bz2 + +The developer version of radeonhd is maintained in the git repository found at **git://anongit.freedesktop.org/git/xorg/driver/xf86-video-radeonhd** + +You can find information on using git at the git website [[http://git.or.cz/|http://git.or.cz/]] and a short intro at [[http://www.freedesktop.org/wiki/Infrastructure/git/Developers|http://www.freedesktop.org/wiki/Infrastructure/git/Developers]] + +You can get a copy of the repository like this: +[[!format txt """ + $ git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-radeonhd +"""]] +This will create a directory _xf86-video-radeonhd_ in the current directory by default, or the given directory _my-radeonhd_ otherwise. + +If you have not made any local changes and want to update you source code with the newest stuff from the official _radeonhd_ repository, you can run this: +[[!format txt """ + $ git pull +"""]] +If you HAVE made local changes and committed them locally to your master branch (with `git commit -a`), you will be better off running +[[!format txt """ + $ git fetch + $ git rebase origin +"""]] +If you're using more branches, read the git docs. + + +# Installation + +Note: The following assumes that you checked out the latest git version of radeonhd. If you're using a released version in form of a tarball, exchange _autogen.sh_ with _configure_. Also make sure you have the necessary development files for X11 driver compilation (e.g. xorg-x11-server-sdk in openSUSE). + +With X.Org 7.0 and later: +[[!format txt """ + $ ./autogen.sh + $ make +"""]] +Then as root: +[[!format txt """ + # make install +"""]] +This will litter all kinds of compiled files throughout your source tree. + ** Please note: ** `make install` will usually install to `/usr/local`. On Linux X is usually installed in `/usr`. To change this, you need to add the argument `--prefix /usr` to `autogen.sh`, i.e.: `./autogen.sh --prefix /usr`. Depending on which system you use you might have to specify a libdir if you are on a 64bit system. Check if the directory `/usr/lib64` exists on your system. If it does, please use `./autogen.sh --prefix /usr --libdir /usr/lib64`. + +With X.Org prior to 7.0: +[[!format txt """ + $ xmkmf -a + $ make EXTRA_INCLUDES="-I/usr/include/xorg -I/usr/include/drm" all +"""]] +and as root: +[[!format txt """ + $ make install +"""]] +This uses imake and is for compatibility with older systems. + +To avoid building in your source tree, do: +[[!format txt """ + $ mkdir _b && cd _b + $ ../autogen.sh + $ make + $ make install +"""]] +Runs the build in _b/ - and if something is completely messed up, you can safely remove the _b/ directory and create a new one without affecting any source files. + +Hint: If you happen to have multiple branches in your git source tree, you + + * can have per-branch __b-BRANCH/_ build trees and __i-BRANCH/_ install trees. ("... configure ... --prefix=$PWD/_i-BRANCH") +Note that none of these methods will install the rhd_conntest tool. The "xmkmf" method always requires a separate "make" run in utils/conntest. The other two will build rhd_conntest by default if its requirements are met. + +Please note you need [[updated drm kernel modules|radeonhd:r6xx_r7xx_branch]] and proper configuration (xorg.conf) for 2D and Xv on R6xx/R7xx. + + +# Known Bugs & Limitations + +The following subsystems have not been implemented yet or show some limitations: + +* 3D acceleration is active by default only on R5xx and RS6xx right now. [[Experimental support for R6xx and R7xx|radeonhd:experimental_3D]] is available, but not for the faint of heart. Also, there is an experimental [[3D bringup tool|radeonhd:r600_demo]] for testing on 6xx/7xx. +* 2D acceleration is active by default now, except on RV740. +* No TV and Component connector support so far. +* Suspend & Resume isn't completely tested, but works on a variety of hardware. Your mileage may vary. Note that typically you need some BIOS workarounds on the kernel command line, ask your distribution for that. +* Powermanagement has to be enabled explicitely. Depending on your hardware, the fan might run at full speed. This turned out to be really tricky. +See also [[RadeonFeature|RadeonFeature]] and [[RadeonProgram|RadeonProgram]] for a features and supported 3D program lists. + +The following known bugs have not been resolved yet (ordered by severity): + +* Digital output on PCIEPHY (RS780) doesn't light up unless connected at boot time. Affects mostly displays connected to laptops thru DVI/HDMI. It is a problem with the AtomBIOS byte code parser which is used at the moment. The only work around is to boot with this output connected at boot time. +* [[Bug 14500|https://bugs.freedesktop.org/show_bug.cgi?id=14500]]: External monitor does not display native resolution +* Some cards seem to provide broken connector tables. We're constantly fixing those. Please report if you have one. + +# Reporting Errors + +Report bugs at: [[https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/radeonhd|https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/radeonhd]]. + +When reporting an error with [[bugzilla|https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/radeonhd]], please be sure to attach your `xorg.conf` and `Xorg.0.log`. Please use `-logverbose 7` for the Xserver in this case. If the error is related to RandR, please verify the xrandr version you are using, and attach the output of `xrandr -q; xrandr -q --verbose`. + +If you want to report a crash try to get a decent stack backtrace (`bt full`) in gdb. You have to compile with debugging information (`-O0 -g3`) or install -debuginfo packages for that. If a -debuginfo package for the Xserver is available for your distribution, please install it as well. It does not have any negative side effects apart from using space on your harddisk. + +If you don't get any output on your monitors at all, please add `Option "NoRandR"` to the "Device" section in your `xorg.conf`, and verify whether this issue is related to RandR or to general modesetting. + +The following messages are absolutely normal in your Xorg.0.log (as we don't have 3D acceleration yet): +[[!format txt """ + (EE) AIGLX error: dlopen of /usr/lib/dri/r600_dri.so failed + (EE) AIGLX: reverting to software rendering +"""]] + +# git Bisecting + +If you stumble over a regression and the source of the issue cannot be determined easily, you may have to git-bisect the issue. This helps us identifying the commit that introduced the issue. As you have to compile the driver yourself in this process, make sure you have the necessary development files (e.g. xorg-x11-server-sdk in openSUSE). See [[Installation|radeonhd]] for more tips about compiling the driver. + +First get a copy of the repository if you don't have that already: +[[!format txt """ + $ git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-radeonhd +"""]] +Otherwise make sure that the copy you have is recent (if you can already reproduce the regression with your current state, you should _NOT_ do that): +[[!format txt """ + $ git pull +"""]] +Identify the last known good version (e.g. the last released version), and the first known broken version. The `gitk` command can help you by visualizing the history. You need to know the SHA1-ids (alternatively, known names as 1.2.4 or master). + +Start a new git-bisect session: +[[!format txt """ + $ git bisect start [bad] [good] +"""]] +E.g. if you just noted that with the current git master changing the backlight level is no longer working, while it was working with 1.2.5, do "`git bisect master 1.2.5`". If you remember that you tested git commit bc42c63 and it still worked, you can save some time by "`git bisect master bc42c63`". + +You will have to do the following in a loop until git tells you that you are done: + +* git presentes you a commit to try out. So configure and make: + +[[!format txt """ + $ ./autogen.sh && make && sudo make install +"""]] +* If this worked out, test the driver. This depends on what exactly you are trying to verify. E.g. for the theoretical backlight issue restart the Xserver (so the new driver is loaded) and test, whether you can change the backlight level. Caveat: Depending on what you need to test this can be arbitrarily complex. E.g. when debugging memory controller setup you just _have_ to to reboot before testing. Every time. +* If the checked out version runs fine, do: + +[[!format txt """ + $ git bisect good +"""]] +* If the checked out version is broken, do: + +[[!format txt """ + $ git bisect bad +"""]] +* You will get a new commit to try out. +At the end git will present you a single commit that first exhibits the broken behavior. This git commit number is _the_ important information for the regression you analyzed. + + +# Troubleshooting, Q & A + +See also examples below for a complete setup. + + +## I get strange build errors about "no rule to make target ..." + +You've probably pulled in some new source files when you updated your sources from git. In this case you should do: +[[!format txt """ +$ make distclean +$ ./autogen.sh +$ make +"""]] +Sometimes in such cases the build doesn't break in such cases but the driver crashes apparently for new reason. Before reporting an error, please try if those steps above make things work already. + + +## autogen.sh / configure doesn't work + +If during running autogen.sh / configure you get +[[!format txt """ +autoreconf: running: /usr/bin/autoconf +configure.ac:35: error: possibly undefined macro: XORG_DRIVER_CHECK_EXT + If this token and others are legitimate, please use m4_pattern_allow. + See the Autoconf documentation. +autoreconf: /usr/bin/autoconf failed with exit status: 1 +"""]] +your system lacks one or more of these files: +[[!format txt """ + /usr/share/aclocal/xorg-macros.m4 + /usr/share/aclocal/xorg-server.m4 + /usr/share/aclocal/xorgversion.m4 +"""]] +Make sure you have all required X.org development packages installed. These may be called _xorg-dev_, _xorg-x11-server-sdk_ and _xorg-x11-util-macros_, or something similar. + + +## 3D applications aren't working + +Please read how to [[setup DRI support|radeonhd:DRI]]. + + +## I only get a very jittery display + +You probably used the `fglrx` driver before. It doesn't restore the linebuffer completely on exit. You have to reboot your system to get this fixed. In some rare cases you might even have to power it off and restart it. Suspend to disk & resume is reported to work on many systems as well. + + +## My monitor isn't detected + +On R5xx hardware the description of the hot plug detection (HPD) pins in the AtomBIOS connector table is often broken. Please try using +[[!format txt """ +Option "HPD" "swap" +"""]] +in the "Device" section. If this helps, please test all outputs (as far as possible with your equipment), and report your findings to the mailing list. Reports should include your Xorg.0.log (the working version) and your results regarding testing. + +If this doesn't help, please try: +[[!format txt """ +Option "HPD" "off" +"""]] +This disables HPD detection completely. In some cases the HPD pin of the GPU doesn't seem to be connected to the DVI connector although it is advertised in the BIOS. + +**NOTE**: Option "HPD" should always only be a workaround until the quirks table in the driver has been updated. ALWAYS report if it is needed to get your monitor running. + +If you are using a KVM switch for your analog monitor and this monitor isn't detected correctly please try without the KVM switch. Analog displays are detected thru 'load detection' ie detection of the terminating resistors on the monitor side. The VGA standard requires 75 Ohm resistors on the RGB lines. Some KVM switches seem to not meet these requirements. + + +## My monitor section isn't used any longer + +Right. This is standard with RandR. Now the monitor sections have to specified with +[[!format txt """ +Option "monitor-<output_name>" "<monitor_name>" +"""]] +in the "Device" section. You can get all output names of your card with `xrandr -q`. See also example below. + +Behavior of monitor sections is different to standard modesetting in radeonhd. With standard modesetting a monitor section replaces the EDID detected monitor (thus typically reducing the maximum mode size to 1024x768), in RandR it doesn't. It's not exactly clear in which cases which parameters are overridden by the monitor section and how to override EDID detected parameters and modes in the RandR case. + + +## The driver doesn't start on my laptop. I have 4GB of main memory, BTW + +Some machines with M72, M83, and possibly other IGP chipsets (especially laptops) with more than 2GB of memory exhibit this BIOS issue. Apparently, the MTRR table is not setup correctly. One possibility is to reduce the amount of RAM, the more reasonable (but only little tested so far) alternative is to enable the MTRR sanitizer in the kernel. +[[!format txt """ +grep "CONFIG_MTRR" /boot/config* +"""]] +to check whether CONFIG_MTRR is active for your kernel. If it is, boot with +[[!format txt """ +enable_mtrr_cleanup mtrr_spare_reg_nr=0 +"""]] +, otherwise you have to recompile your kernel with this option enabled. + + +## The cursor shows weird corruptions at some points of the screen + +This is [[Bug 13405|https://bugs.freedesktop.org/show_bug.cgi?id=13405]]: Hardware cursor corruption. Presumably fixed with git commit [[4be5f7152f71|http://cgit.freedesktop.org/xorg/driver/xf86-video-radeonhd/commit/?id=4be5f7152f71c292f16b6e30c59c07b282ea4772]] (not in any release yet). + + +## How do I enable / disable an output after a monitor has been plugged in / removed? + + +[[!format txt """ +xrandr --auto +"""]] + +## How do I set up multiple monitors? + + +[[!format txt """ +xrandr --output <output_name> --right-of <other_output_name> +"""]] +If this fails, the most common reason is the following: The X.org framebuffer cannot be resized after initialization (yet). You have to either configure this statically (see below), or specify the maximum needed size with +[[!format txt """ +Virtual <width> <height> +"""]] +in the "Display" subsection of the "Screen" section. + +If xrandr is not able to unclone displays (monitors show the same screen still), and you have set virtual correctly, it can also be that you need a newer xrandr (1.2.3 or git), and potentially also a newer xserver. You can try to explicitly set the used Crtc with `--crtc 1` or 0. + +`xrandr -q` prints the maximum frame buffer size in the first line of its output. + + +## How do I configure a multimonitor setup statically? + +Add (mostly empty) monitor sections for your monitors like described in the answer above. Then add +[[!format txt """ +Option "RightOf" "<other_monitor_name>" +"""]] +to the monitor section representing your right monitor. Alternatively, you can use `LeftOf` - working correctly only with the latest Xserver (bugfix). Of course there's also `Above` and `Below`. + +You can also use `<other_output_name>` instead of `<other_monitor_name>`. Also read `man 5 xorg.conf`. + + +## My monitors have different resolutions. But both show the same lower resolution on startup + +This seems to be a general RandR issue. Can be changed with `--output <output> --auto` during runtime, or with `Option "PreferredMode" "<mode>"` with newer Xservers (known to be buggy up to Xserver 1.4.0). + + +## My Gnome/KDE/whatever panel shows up on the wrong monitor + +Add your preferred monitor to +[[!format txt """ +Option "RROutputOrder" "<monitor_name>" +"""]] +in the "Device" section. This reorders the RandR outputs, which is reflected in the Xinerama screen order. You can specify any number of outputs, separated by spaces or comas. Note that this is a radeonhd specific option, it won't work with other drivers. + + +## Panels and maximized windows span all my monitors + +Make sure you have enabled xinerama support for your window manager. For instance, on Gentoo enable the xinerama USE-flag and rebuild the affected packages by issuing the following command +[[!format txt """ +emerge -aND world +"""]] + +## xrandr returns with BadMatch (invalid parameter attributes) + +Get a newer xrandr (1.2.3 or git), and potentially also a newer xserver. If it still happens, send a mail to [[radeonhd@opensuse.org|mailto:radeonhd@opensuse.org]] or file a bug at freedesktop.org. You can get the newest xrandr from git by +[[!format txt """ +git-clone git://anongit.freedesktop.org/git/xorg/app/xrandr +"""]] + +## How do I set -logverbose 7 when I run a display manager (xdm/kdm/gdm)? + +There is a display manager configuration file which lists the command line to use when starting the Xserver. It usually `/etc/X11/xdm/Xservers`. In this file you will find a line like: +[[!format txt """ +:0 local /usr/bin/X -nolisten tcp -br vt7 +"""]] +Please add `-logverbose 7` at the end of this line. + + +## Why is radeonhd so much slower than avivo? + +There may be an old, obsolete line in your `xorg.conf` file from some _fglrx_ setup a long time ago: +[[!format txt """ +Option "mtrr" "no" # ancient, obsolete option: REMOVE IT! +"""]] +If you have such a line, removing it can speed up radeonhd considerably. + +General note: As a rule, one does not need any `xorg.conf` file with Xserver 1.4 and up, so it is always a good idea to make sure you _really_ need all the statements in there. + + +## How do I get a multi card setup to work? + +Make sure you have a config file with one Device section for each card. Each device section should be referenced from it's own Screen section which itself should be referenced in the Layout section. + +Depending on which version of the Xserver and OS you are using you may need to take additional steps. On Linux you may need to do: + +* On Linux you need to boot with the boot option pci=rom. +* after booting do: + * [[!format txt """ + # echo 1 > /sys/bus/pci/devices/<pci_bus_id>/rom + +"""]] +* Some users have reported they also need to do: + * [[!format txt """ + # setpci -s <pci_bus_id> ROM_ADDRESS=xxxx0001 + # setpci -s <pci_bus_id> COMMAND=2 + +"""]]replace <pci_bus_id> with the PCI bus ID and xxxx with the hex digits you can obtain thru ` lspci -nv `. + +# Examples + +Example xorg.conf (minimal for Xserver 1.3 and up), e.g. no input devices or modes configured, monitors configured by EDID data): +[[!format txt """ +Section "Monitor" + Identifier "External" + Option "RightOf" "Panel" +EndSection + +Section "Monitor" + Identifier "Panel" +EndSection + +Section "Device" + Identifier "MyCard" + Driver "radeonhd" + Option "monitor-VGA_1" "External" + Option "monitor-PANEL" "Panel" + Option "RROutputOrder" "PANEL" +EndSection + +Section "Screen" + Identifier "MyScreen" + Device "MyCard" + DefaultDepth 24 + SubSection "Display" + Depth 24 + ## This is superfluous and actually harmful with a + ## static configuration. Enable for dynamic config only. + #Virtual 2704 1050 + EndSubSection +EndSection +"""]] +Example call to configure multiple screens dynamically (set Virtual in `xorg.conf` for that to work): +[[!format txt """ +xrandr --output VGA_1 --right-of PANEL +"""]] + +# Glossary + +This is a list of abbreviations and words which you will stumble upon when you are digging deeper. + +* [[!table header="no" class="mointable" data=""" + CP | command processor + CS | command submission + [[DRI|http://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure]] | Direct Rendering Infrastructure + [[DRM|http://en.wikipedia.org/wiki/Direct_Rendering_Manager]] | Direct Rendering Manager + [[EXA|http://en.wikipedia.org/wiki/EXA]] | + [[GEM|http://en.wikipedia.org/wiki/Graphics_Execution_Manager]] | graphics execution manager + KMS | kernel based mode setting + MC | memory controller + [[XAA|http://en.wikipedia.org/wiki/XAA]] | XFree86 Acceleration Architecture +"""]] diff --git a/radeonhd:DRI.mdwn b/radeonhd:DRI.mdwn new file mode 100644 index 00000000..b4e96bea --- /dev/null +++ b/radeonhd:DRI.mdwn @@ -0,0 +1,153 @@ + + +# How to setup DRI with radeonhd + +Please note that there is **only very experimental [[3D support for r6xx based cards|radeonhd:experimental_3D]]** so far! There is also a [[3D bringup tool|radeonhd:r600_demo]] available that is already capable of rendering textured triangles. Additionally, there is also EXA and Xv acceleration in master. Both the demo program, the EXA/Xv support, and the experimental 3D driver require a drm built from the r6xx-r7xx branch of mesa/drm (or, for Linux, drm-next is preferable) in order to operate. + +The RS6xx IGP parts have a 2D engine and a 3D engine from the R4xx family so do not require "R6xx support". + +The rest of this page relates only to R5xx or RS690 for now. + +So in order to enable DRI on your r5xx card or 690-based motherboard you need + +* Recent DRM kernel module + libdrm +* Recent Mesa (7.2 should suffice) +* Recent Xserver (for i386 1.3.0 is enough, x86_64 needs 1.5.0 or later) +* Recent radeonhd (version 1.2.2 or later - earlier versions did not allow 2D and 3D at the same time) +[[!toc 2]] + + +## Known Issues + +* x86_64 is only working correctly with a current Xserver (1.4.99.x) +* Mipmap textures are broken +* Texture upload after suspend to disk is partially broken +* Movewindow support is missing (partially superfluous) +* googleearth doesn't render anything. Apparently it falls back into a slow path (antialiased lines), but that is probably only part of the story. + +## Building + +It's a smart idea to pull all this source down into it's own self contained area, in case you need to blow it all away cleanly and redo the git clone, builds, etc. So in this case we'll use /var/tmp/radeonhd-dri as the main area. Don't use /tmp, this is cleared on reboot on some distributions. + + +[[!format txt """ + SRC="/var/tmp/radeonhd-dri" + mkdir $SRC + cd $SRC +"""]] +Please note that the following information is quite Linux-centric at the moment. + + +### Sources + +If you want to test the bleeding edge for the main components, we suggest using the git heads, because there are probably still bugs lurking somewhere. +[[!format txt """ + git clone git://anongit.freedesktop.org/git/mesa/drm + git clone git://anongit.freedesktop.org/git/mesa/mesa + git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-radeonhd + #git clone git://anongit.freedesktop.org/git/xorg/xserver +"""]] +Apparently you need to fetch and build the Xserver only on x86_64, and only if you don't have 1.5.0 or higher - don't update if not necessary, this is painful! + + +### Preconditions + +You will stumble upon some preconditions, the following should help here (using released versions whenever possible). You can unpack the released versions with `tar xvfj` <file>. If they don't work, try the according git tree, you can find the path to the git repository on the [[gitweb page|http://gitweb.freedesktop.org/]]. + +Mesa needs dri2proto: + +* [[ftp://ftp.freedesktop.org/pub/individual/proto/dri2proto-1.1.tar.bz2|ftp://ftp.freedesktop.org/pub/individual/proto/dri2proto-1.1.tar.bz2]] +When building a newer Xserver you will have to fetch and install a number of newer prototypes and libraries. This includes: + +* [[ftp://ftp.freedesktop.org/pub/individual/proto/xextproto-7.0.3.tar.bz2|ftp://ftp.freedesktop.org/pub/individual/proto/xextproto-7.0.3.tar.bz2]] +* [[ftp://ftp.freedesktop.org/pub/individual/proto/xproto-7.0.13.tar.bz2|ftp://ftp.freedesktop.org/pub/individual/proto/xproto-7.0.13.tar.bz2]] +* `git clone git://anongit.freedesktop.org/git/xorg/proto/inputproto` +* [[ftp://ftp.freedesktop.org/pub/individual/lib/pixman-0.10.0.tar.bz2|ftp://ftp.freedesktop.org/pub/individual/lib/pixman-0.10.0.tar.bz2]] +Also, after building the Xserver you have to build and install all input drivers you are using as well. Apparently, you need the very latest bits for them to be compilable, and they have to be compiled against the new ABI of the Xserver. At least this includes: + +* `git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-input-mouse` +* `git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-input-keyboard` +* **or** ` git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-input-evdev` +Also, for the DRM kernel modules you need the kernel sources of your running kernel installed in /usr/src - all major distributions do this correctly nowadays if kernel sources are installed from your distribution. + +You may also run into a problem where your libpciaccess it out of date and you need to pull down the latest from git: + +* `git clone git://anongit.freedesktop.org/git/xorg/lib/libpciaccess` +and build it with the usual manner. This seems to show up on x86_64 builds when the xf86-video-radeonhd build croaks. + + +### Installation + +The drm package contains two subsystems, which have to be built and installed separately at the beginning. There's no reason to actually build all the _other vendor_ drm modules, so we'll just build the one we're interested in. In order to make sure that the correct module is loaded check that `extra` is part of the `search` list in `/etc/depmod.conf` - in Ubuntu this typically isn't. + + +[[!format txt """ + cd $SRC/drm + ./autogen.sh --prefix=/usr + make + make install (as root) + cd linux-core + make DRM_MODULES="radeon" + make install (as root) + depmod -a (as root) +"""]] +After that, all other subsystems have to be built and installed in the same way, in the order mentioned below: +[[!format txt """ + cd $SRC/<subsystem> + ./autogen.sh --prefix=/usr + make + make install (as root) +"""]] +If using a released package (a `.tar.bz2`), there is no `autogen.sh`. In that case (and _only_ in that case) you have to call `./configure` with the same arguments. Depending on your distro, you might want to add `--libdir /usr/lib64` to `./autogen.sh`. + +The subsystems have to be built and installed in the following order: + +* dri2proto +* mesa (add `--with-dri-drivers=radeon,r300,swrast` to `./autogen.sh` to speed up the build considerably) +* Xserver: only if there is need to build the xserver, which is quite painful: + * xextproto + * xproto (is named x11proto in the git repository) + * inputproto + * pixman + * xserver + * xf86-input-mouse + * xf86-input-keyboard + * xf86-input-evdev (if used) +* radeonhd + +### Notes for Experienced Users + +If you have a little experience with building and installing foreign packages, you might want to use a different `--prefix` in order to not override your installed configuration. In that case you will have to additionally set +[[!format txt """ + export ACLOCAL="aclocal -I $PREFIX/share/aclocal" + export PKG_CONFIG_PATH=$PREFIX/$LIB/pkgconfig" + export LD_LIBRARY_PATH=$PREFIX/$LIB + export PATH=$PREFIX/bin:$PATH +"""]] +with `$PREFIX` being the directory to be installed to and `$LIB` being "lib" on i386 and "lib64" on x86_64 (might be distribution dependent). + +You can also use build dirs for all subsystems (except for the kernel module and the Mesa subsystem, which uses autoconf, but not automake) by creating a `build` directory, changing into that directory and calling `../autogen.sh [args]`. This has the advantage that the source directory remains untouched. Again, this doesn't work for Mesa and the drm kernel module. + + +## Configuration + +DRI is inactive by default. + +In order to activate DRI, you have to add +[[!format txt """ + Option "DRI" +"""]] +to the driver section of your `xorg.conf`. + + +## Troubleshooting, Q & A + + +### Only the first invocation of a OpenGL program works as expected + +You're probably running an older Xserver (< 1.4.99.x) on an x86_64 machine. This is known to exhibit this bug. + + +### I only get "Error: coudn't get an RGB, Double-buffered visual." + +Same as above. Xserver is too old. diff --git a/radeonhd:INSTALL.mdwn b/radeonhd:INSTALL.mdwn new file mode 100644 index 00000000..f5b07c2d --- /dev/null +++ b/radeonhd:INSTALL.mdwn @@ -0,0 +1,108 @@ + +_This is a little howto or install-diary of how i got the radeonhd driver (with xv-support for now) working for my system: debian testing (squeeze) and HD4850. I needed to search on a few different sites to get it finally to work, because there are some errors in any existing howto at x.org or there are some information missing, and people keep asking questions for it in the IRC, so so i decided to create this page, which I think this page is pretty useful._ + +Preconditions: + + +[[!format txt """ +apt-get install checkinstall build-essential git-core configure-debian automake xorg-dev libtool autoconf pciutils-dev libpciaccess-dev mesa-common-dev libgl1-mesa-dev libdrm-dev x11proto-dri2-dev +"""]] +im not sure if _libdrm-dev_ is needed because you have to compile your own version of it - please confirm somebody. _x11proto-dri2-dev_ is only aviable for testing (squeeze) [[x11proto-dri2-dev|http://packages.debian.org/squeeze/x11proto-dri2-dev]] +[[!format txt """ +apt-get build-dep xserver-xorg-video-radeonhd +"""]] +Create a working directory whereever you want to (~/ or /var/tmp/ for example): + + +[[!format txt """ +SRC="/your/working/directory" +mkdir $SRC +cd $SRC +"""]] +Get and install **DRM**: +[[!format txt """ +git clone git://anongit.freedesktop.org/mesa/drm +cd drm/linux-core +git checkout -b r6xx-r7xx-support origin/r6xx-r7xx-support +cd .. +./autogen.sh --prefix=/usr +make +make install # as root +"""]] +An alternativ for _make & make install_ is _checkinstall_. In the queries you have to answer as necessary. + + +[[!format txt """ +[...] +./autogen.sh --prefix=/usr +checkinstall # as root +# there is a warning: *** Warning: The package version "2.4.3 [...] is not a debian policy complaint one. Please specify an alternate one +# just type in the version yourself: "2.4.3" +sudo dpkg -i --force all *.deb +"""]] +_force all_ is needed, because it overwrites some files of the libdrm-dev package. As mentioned earlier, I'm not sure if this package is needed for the installation. + +Build the modules (_drm.ko/radeon.ko_) and install them: +[[!format txt """ +cd linux-core +make DRM_MODULES="radeon" +sudo make install +sudo depmod -a +"""]] +leave drm and return to your workspace: +[[!format txt """ +cd $SRC +"""]] +Get and install **xf86-video-radeonhd**: +[[!format txt """ +git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-radeonhd +cd xf86-video-radeonhd +./autogen.sh --prefix=/usr +make +make install # as root +"""]] +If you want to, use _checkinstall_ again like above. + +Edit your xorg.conf: + +The _Section "Device"_ in your xorg.conf should look like below: +[[!format txt """ +Section "Device" + Identifier "Configured Video Device" + Driver "radeonhd" + Option "AccelMethod" "EXA" + Option "DRI" +EndSection +"""]] +and you have to add this to your xorg.conf +[[!format txt """ +Section "DRI" + Mode 0666 +EndSection +"""]] +At this point i prefer rebooting the machine, but stopping x, reload the (new) drm-module and start x again should be enough. + +To update **DRM** to its newest version do this: +[[!format txt """ +cd $SRC +cd drm +git pull +make clean +./autogen.sh --prefix=/usr +make +make install # as root +cd linux-core +make clean +make DRM_MODULES="radeon" +make install # as root +"""]] +To update **xf86-video-radeonhd** to its newest version do this: +[[!format txt """ +cd $SRC +cd xf86-video-radeonhd +git pull +make clean +./autogen.sh --prefix=/usr +make +make install # as root +"""]]
\ No newline at end of file diff --git a/radeonhd:TODO.mdwn b/radeonhd:TODO.mdwn new file mode 100644 index 00000000..669f0aa4 --- /dev/null +++ b/radeonhd:TODO.mdwn @@ -0,0 +1,35 @@ + + +# radeonhd: List of things to do + +If you want to work on one of those things, be sure that + +1. you understand the feature well enough to implement this +1. if anyone else is working on the feature he/she wants to cooperate with you +1. you announce it on the according mailing list +1. you update the information on this wiki page accordingly (add yourself as the one working on it). +It's best to announce that you _plan_ to work on a feature on the mailing list and see what the other developers and users think about that. Be sure to include enough information in the announcement, so people have something to comment on. + +Also note that "working on" reports here are by no means priority indicators - they just claim that someone is aware of this issue, and has considered to work on it. No more, no less. + +Feel free to add additional (technical!) TODOs, but don't consider this do be a bug tracking list, or a general wish list. + + +## radeonhd X11 driver + +Please announce work on the [[radeonhd mailing list|http://lists.opensuse.org/radeonhd/]]. + +* **Tiling support for the framebuffer**. This will accelerate 3D a lot. As this tackles a lot of subsystems quite a number of changes are involved, and support for r6xx needs more flexibility than for r6xx. (working on: Egbert Eich) +* **2D and 3D acceleration lock up each other**. First estimation by Luc Verhaegen: R5xx3DSetup() is called on every context change (e.g. from 3D application to Xserver), and apparently not waiting correctly for the chip to settle. +* **XVideo support** needs some love. E.g. bicubic filtering, support for various color spaces, etc. (working on: Alexander Deucher) +* **Full RandR 1.3 properties support**. All mandatory properties are already supported, still there are a number of additional properties that are not implemented yet. (working on: Matthias Hopf) +* **TV out support**. +* **Kernel modesetting.** radeonhd's DRI and kernel modesetting are currently mutually exclusive. Also being able to utilize kernel modesetting itself would be interesting. + +## r6xx DRI driver + +Please announce work on the [[radeonhd mailing list|http://lists.opensuse.org/radeonhd/]], for the moment. Until the r6xx driver is actually available in any form, then we will change to the dri mailing list. + +Currently the r6xx DRI driver is basically non-existing. If you want to contribute, first play a bit with the [[3D bringup tool|radeonhd:r600_demo]] and verify that everything works as indicated on your GPU as well. + +(working on: Matthias Hopf) diff --git a/radeonhd:feature.mdwn b/radeonhd:feature.mdwn new file mode 100644 index 00000000..0a504d5c --- /dev/null +++ b/radeonhd:feature.mdwn @@ -0,0 +1,61 @@ + + +## Feature Matrix for radeonhd + +**This page is only for free [[radeonhd|radeonhd]] driver.** + +**See [[RadeonFeature|RadeonFeature]] for radeon (xf86-video-ati). THIS PAGE IS NOT FOR [[FGLRX/CATALYST|ATIProprietaryDriver]] DRIVERS PROVIDED BY AMD/ATI.** + +Also check out the [[RadeonProgram|RadeonProgram]], [[GalliumStatus|GalliumStatus]], and [[ATIRadeon|http://dri.freedesktop.org/wiki/ATIRadeon]] at DRI wiki. + + * "**DONE**" means that it is implemented and relatively bug-free. + * "**MOSTLY**" means that it is implemented but has some known bugs. + * "**WIP**" means that someone has started on the initial implementation. + * "**BIOS**" means only if supported by your BIOS. No software support. Yet. + * "**SLOW**" means that the feature is implemented and bug-free, but slow. Improvements may or may not be planned. + * "**STALLED**" means that whatever code has been written is accumulating color and texture similar to that 3 week old slice of pizza in your fridge. + * "**N/A**" means that the feature is not supported by the hardware. + * "**N/N**" means that the feature will not be implemented, because a better alternative is or will be available. + * "**TODO**" means that someone needs to write the code. The required knowledge to write the code may or may not be known. Please ask on #radeon/#radeonhd if you want to get your feet wet on this. + * "**UNKNOWN**" means that the current status of this item isn't known. You are free to update it if you know. [[!table header="no" class="mointable" data=""" + **2D features** || | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + DDX (X server) Modesetting || | DONE | DONE | DONE | DONE | TODO + Kernel Modesetting || | N/N | N/N | N/N | N/N | TODO + DRI2 || | TODO | TODO | TODO | TODO | TODO + ShadowFB || | DONE | DONE | DONE | DONE | TODO + Old 2D Acceleration (XAA) || | DONE | DONE | N/N | N/N | N/N + 2D Acceleration (EXA) || | DONE | DONE | DONE | DONE | TODO + Overlay Xv || | N/N | N/N | N/N | N/N | N/N + Textured Xv || | DONE | DONE | DONE | DONE | TODO + XvMC || | TODO | TODO | TODO | TODO | TODO + **Output** || | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + Dual-link DVI || | DONE | DONE | DONE | DONE | TODO + XRandR 1.2 || | DONE | DONE | DONE | DONE | TODO + TV Out || | TODO | TODO | TODO | TODO | TODO + [[DisplayPort|DisplayPort]] || | N/A | N/A | TODO | TODO | TODO + HDMI Audio || | DONE | TODO | DONE | DONE | TODO + **Other** || | **RS690** | **R500** | **R600** | **R700** | **Evergreen** + Power Saving (Powerplay) || | TODO | TODO | TODO | TODO | TODO + Suspend Support || | DONE | DONE | DONE | DONE | TODO + Console restore || | DONE | DONE | DONE | DONE | TODO +"""]] + + +### Feature dependency tree + + +[[!format txt """ +memory manager -+-> KMS -+-> advanced power management (dynamic control of clocks etc..) + | | + | +-> run X without root privileges + | + +-> advanced 3D (OpenGL 1.5+) via chip-specific Mesa code + | + +-> DRI2 / RDR -+-> Flicker-free 3D with compositing + | + +-> Gallium3D -+-> advanced 3D (OpenGL 1.5+, GLSL) via generic Mesa code + | + +-> video decode acceleration + | + +-> OpenCL +"""]]
\ No newline at end of file diff --git a/radeonhd:packages.mdwn b/radeonhd:packages.mdwn new file mode 100644 index 00000000..2770a8bf --- /dev/null +++ b/radeonhd:packages.mdwn @@ -0,0 +1,26 @@ + + +# radeonhd packages + +Links to packages of [[radeonhd|radeonhd]] for different systems. + + +## deb-based systems + + * [[Debian|http://www.debian.org/]]: 2008-04-22: Version 1.2.1-1 in unstable. [[Debian radeonhd package page|http://packages.qa.debian.org/x/xserver-xorg-video-radeonhd.html]] + * [[Ubuntu|http://www.ubuntu.com/]]: 2008-01-03: Version 1.1.0-1 in Hardy (universe). [[Ubuntu radeonhd package page|https://launchpad.net/ubuntu/+source/xserver-xorg-video-radeonhd]]. Unofficial packages at [[https://wiki.ubuntu.com/XorgOnTheEdge|https://wiki.ubuntu.com/XorgOnTheEdge]] + +## ports-based systems + + * [[FreeBSD|http://www.freebsd.org/]]: [[ports/x11-drivers/xf86-video-radeonhd/ in cvsweb|http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-drivers/xf86-video-radeonhd/]] + * [[Gentoo|http://www.gentoo.org/]]: x11-drivers/xf86-video-radeonhd (to install, run **emerge -av xf86-video-radeonhd**) + * [[NetBSD|http://www.netbsd.org/]]: [[The NetBSD Packages Collection: x11/xf86-video-radeonhd|ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/x11/xf86-video-radeonhd/README.html]] + * [[OpenBSD|http://www.openbsd.org/]]: ??? + +## rpm-based systems + + * [[Fedora|http://fedoraproject.org]]: + * Easy command for F-10, F-11: `yum [--enablerepo=updates-testing] update xorg-x11-drv-radeonhd` + * The [[koji xorg-x11-drv-radeonhd page|http://koji.fedoraproject.org/koji/packageinfo?packageID=5156]] has the newest packages for F-10, F-11, and rawhide. Those will eventually filter down into your normal updates* yum repositories. + * Cf. [[viewcvs|http://cvs.fedoraproject.org/viewcvs/rpms/xorg-x11-drv-radeonhd/]], [[koji page|http://koji.fedoraproject.org/koji/packageinfo?packageID=5156]], [[update status|https://admin.fedoraproject.org/updates/xorg-x11-drv-radeonhd]], [[pkgdb bugs|https://admin.fedoraproject.org/pkgdb/packages/bugs/xorg-x11-drv-radeonhd]], [[fedora bz bugs|https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=xorg-x11-drv-radeonhd]], [[fdo bz bugs|https://bugs.freedesktop.org/buglist.cgi?quicksearch=radeonhd]]. + * [[openSUSE|http://www.opensuse.org/]]: [[radeonhd openSUSE search results|http://benjiweber.co.uk:8080/webpin/index.jsp?searchTerm=radeonhd]]
\ No newline at end of file diff --git a/s3.mdwn b/s3.mdwn new file mode 100644 index 00000000..9b93d335 --- /dev/null +++ b/s3.mdwn @@ -0,0 +1,14 @@ + + +# s3 + +Driver for S3(except !ViRGE or Savage) based video chips. License: MIT + + +## Documentation and Support + + +## Known Issues + + +### Release 6.7.0 diff --git a/s3virge.mdwn b/s3virge.mdwn new file mode 100644 index 00000000..01f82a98 --- /dev/null +++ b/s3virge.mdwn @@ -0,0 +1,5 @@ + + +# s3virge + +Driver for S3 ViRGE based video chips. License: MIT diff --git a/savage.mdwn b/savage.mdwn new file mode 100644 index 00000000..af64deca --- /dev/null +++ b/savage.mdwn @@ -0,0 +1,15 @@ + + +# savage + +Driver for S3 Savage based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://dri.freedesktop.org/wiki/S3Savage]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/sis.mdwn b/sis.mdwn new file mode 100644 index 00000000..a1c1062e --- /dev/null +++ b/sis.mdwn @@ -0,0 +1,27 @@ + + +# sis + +Driver for Silicon Integrated Systems (SiS) video chips. + +License: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3) The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/SiS.4.html]] for the current release for configuration options. + * There is also a [[README file|http://www.freedesktop.org/~xorg/current/doc/sis.4.html]] containing additional information about known problems and hints. + * Author and maintainer's [[website|http://www.winischhofer.net/linuxsisvga.shtml]] with complete documentation and updates + +## Known Issues + + +### Release 6.7.0 + + * Pixmap 24->32 and 32->24 conversion not advertised + * 661/741/760 support has problems (chipsets were not on the market then) + * On 1400x1050 and 1600x1200 panels, some modes don't work + +### Release 6.8.1 + + * None known
\ No newline at end of file diff --git a/to_convert2 b/to_convert2 new file mode 100644 index 00000000..5216c870 --- /dev/null +++ b/to_convert2 @@ -0,0 +1,596 @@ +BoardOfDirectors(2f)Elections(2f)2011(2f)qa +fosdem2013 +CategoryServerInternals +ChangeLogStyle +CrossCompilingXorgJhbuild +XDevConf +XDevConf(c38a)mbridge2005 +Fosdem2006DevRoomAttendants +Development(2f)Documentation(2f)PointerAccelerationAsOf16 +Development(2f)Documentation(2f)VersionNumberScheme +Development(2f)Documentation(2f)WritingDocumentation +Other(2f)Press(2f)X11R76Released +ChangesForX11R71 +PressReleases(2f)X11R72Released +Other(2f)Press(2f)X11R72Released +DeprecatedInX11R7 +X11R71Release +X11R72Issues +X11R72Release +ChangesForX11R73 +ChangesForX11R72 +X11R7and69TODO +X11R70Release +PressReleases(2f)X11R71Released +Other(2f)Press(2f)X11R71Released +Other(2f)Press(2f)X11R75Released +MattDew(2f)docbooktest +Development(2f)Documentation(2f)DocBookConversion +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +HelpOnLinking(2f)NotesLinks +XDC2007(ee8080)Notes(ee8081) +Events(2f)XDC2008(2f)Notes +Events(2f)XDS2010(2f)Notes +XDC(ee8080)2007(ee8081)Notes +Events(2f)XDS2008(2f)Notes +xdc2007notes +XKBLayoutCreationNotes +Events(2f)XDC2009(2f)Notes +XDC2007Notes +ReleaseNotes670 +Events(2f)XDC2011(2f)Notes +X11R68PostPartumNotes +Events(2f)XDS2007(2f)Notes +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +HelpOnLinking(2f)NotesLinks +XDC2007(ee8080)Notes(ee8081) +Events(2f)XDC2008(2f)Notes +Events(2f)XDS2010(2f)Notes +XDC(ee8080)2007(ee8081)Notes +Events(2f)XDS2008(2f)Notes +xdc2007notes +XKBLayoutCreationNotes +Events(2f)XDC2009(2f)Notes +XDC2007Notes +ReleaseNotes670 +Events(2f)XDC2011(2f)Notes +X11R68PostPartumNotes +Events(2f)XDS2007(2f)Notes +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +HelpOnLinking(2f)NotesLinks +XDC2007(ee8080)Notes(ee8081) +Events(2f)XDC2008(2f)Notes +Events(2f)XDS2010(2f)Notes +XDC(ee8080)2007(ee8081)Notes +Events(2f)XDS2008(2f)Notes +xdc2007notes +XKBLayoutCreationNotes +Events(2f)XDC2009(2f)Notes +XDC2007Notes +ReleaseNotes670 +Events(2f)XDC2011(2f)Notes +X11R68PostPartumNotes +Events(2f)XDS2007(2f)Notes +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +china(20)hotels +Events(2f)XDS2010(2f)Hotels +Events(2f)XDC2012(2f)Hotels +BookingAmsterdam(20)Hotels +Events(2f)XDC2012(2f)Proceedings +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Events(2f)XDC2012(2f)PublicTransportation +Events(2f)XDC2012(2f)Weekend +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +HelpOnLinking(2f)NotesLinks +XDC2007(ee8080)Notes(ee8081) +Events(2f)XDC2008(2f)Notes +Events(2f)XDS2010(2f)Notes +XDC(ee8080)2007(ee8081)Notes +Events(2f)XDS2008(2f)Notes +xdc2007notes +XKBLayoutCreationNotes +Events(2f)XDC2009(2f)Notes +XDC2007Notes +ReleaseNotes670 +Events(2f)XDC2011(2f)Notes +X11R68PostPartumNotes +Events(2f)XDS2007(2f)Notes +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +HelpOnLinking(2f)NotesLinks +XDC2007(ee8080)Notes(ee8081) +Events(2f)XDC2008(2f)Notes +Events(2f)XDS2010(2f)Notes +XDC(ee8080)2007(ee8081)Notes +Events(2f)XDS2008(2f)Notes +xdc2007notes +XKBLayoutCreationNotes +Events(2f)XDC2009(2f)Notes +XDC2007Notes +ReleaseNotes670 +Events(2f)XDC2011(2f)Notes +X11R68PostPartumNotes +Events(2f)XDS2007(2f)Notes +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Events(2f)XDS2008(2f)Recordings +Events(2f)XDC2011(2f)Attendees +Events(2f)XDS2007(2f)Attendees +Events(2f)XDC2012(2f)Attendees +Events(2f)XDS2008(2f)Attendees +Events(2f)XDS2010(2f)Attendees +Events(2f)XDC2009(2f)Attendees +Events(2f)XDC2008(2f)Attendees +china(20)hotels +Events(2f)XDS2010(2f)Hotels +Events(2f)XDC2012(2f)Hotels +BookingAmsterdam(20)Hotels +HelpOnLinking(2f)NotesLinks +XDC2007(ee8080)Notes(ee8081) +Events(2f)XDC2008(2f)Notes +Events(2f)XDS2010(2f)Notes +XDC(ee8080)2007(ee8081)Notes +Events(2f)XDS2008(2f)Notes +xdc2007notes +XKBLayoutCreationNotes +Events(2f)XDC2009(2f)Notes +XDC2007Notes +ReleaseNotes670 +Events(2f)XDC2011(2f)Notes +X11R68PostPartumNotes +Events(2f)XDS2007(2f)Notes +Antivirus(20)Software(20)program(20)for(20)Mobile(20)Devices +Events(2f)XDC2011(2f)Program +Events(2f)XDC2012(2f)Program +Events(2f)XDS2008(2f)Program +wiki(2f)Events(2f)XDS2010(2f)Program +Events(2f)XDC2008(2f)Program +Events(2f)XDC2009(2f)Program +Events(2f)XDS2010(2f)Program +ProgrammingDocumentation +RadeonProgram +Events(2f)XDS2007(2f)Program +Fosdem2006DevRoomAttendants +Fosdem2006HotHouseParticipants +FrontPage +HelpMiscellaneous(2f)ExperimentalFeatures +HelpMiscellaneous(2f)FrequentlyAskedQuestions +HelpOnActions(2f)AttachFile +HelpOnConfiguration(2f)EmailSupport +HelpOnConfiguration(2f)CascadingStyleSheets +HelpOnConfiguration(2f)EmailSupport +HelpOnConfiguration(2f)SecurityPolicy +HelpOnConfiguration +HelpOnFormatting +HelpOnInstalling(2f)ApacheOnMacOsx +HelpOnInstalling(2f)ApacheOnUnix +HelpOnInstalling(2f)ApacheOnWin32 +HelpOnInstalling(2f)ApacheWithFastCgi +HelpOnInstalling(2f)ApacheWithModPython +HelpOnInstalling(2f)BasicInstallation +HelpOnInstalling(2f)InternetInformationServer +HelpOnInstalling(2f)TroubleShooting +HelpOnInstalling(2f)TwistedWeb +HelpOnMacros +HelpOnMacros(2f)Include +HelpOnMacros(2f)MailTo +HelpOnPageDeletion +HelpOnProcessors +HelpOnSmileys +HelpOnSpellCheck +HelpOnTables +HelpOnThemes +HelpOnUpdating +Fosdem2006HotHouseParticipants +Events(2f)XDC2012(2f)XDC2012AbstractIanRomanick +XInputHotplug +InterWiki +InterWikiMap +LinuxTagMeeting2005Zack +LinuxTagMeetingLuc +LinuxTagOrganization2006 +LinuxTagMeetingGunnar +LinuxTagMeeting2005DavidR +LinuxTagMeeting2005 +LinuxTagMeetingMatthias +LinuxTagMeetingGianFilippo +LinuxTagMeeting2005Participants +LinuxTagMeetingLars +LinuxTagMeetingZack +LinuxTag2005Infos +LinuxTagMeeting2005Schedule +LinuxTagMeeting2005Lars +LinuxTagMeeting +LinuxTagMeetingParticipants +LinuxTagMeeting2005GianFilippo +LinuxTagMeetingDaniel +LinuxTagMeeting2005Gunnar +LinuxTagInfos +LinuxTagMeeting2005Matthias +LinuxTagMeetingDavidR +LinuxTagMeetingSchedule +LinuxTagMeeting2005Daniel +LinuxTagMeeting2005KaiUwe +LinuxTagMeetingKaiUwe +LinuxTagMeeting2005Luc +LinuxTag2005Infos +LinuxTagMeeting2005Participants +LinuxTagMeeting2005Schedule +MakingReleases +Events(2f)XDC2012(2f)XDC2012AbstractOliverMcFadden +MesaSolo +Events(2f)XDC2012(2f)XDC2012AbstractMichaelLarabel +MichaelLarabel +MichaelVerret +MoinMoin(2f)TextFormatting +OpenMotif +Other(2f)Press(2f)CFP2012_supplemental +Other(2f)Press(2f)CFP2012 +Other(2f)Press(2f)CFP2012_supplemental +PageSize +Events(2f)XDC2012(2f)XDC2012AbstractPeterHutterer +XOrgInputDriverSpec +XInputCoordinateTransformationMatrixUsage +Development(2f)Documentation(2f)InputEventProcessing +XInputSpec +XInputHotplug +Development(2f)InputOverhaul +InputDriverRoadmap +Development(2f)Documentation(2f)XorgInputHOWTO +InputEventProcessing +Development(2f)Documentation(2f)MPX +Mirrors +FTPXOrgMirrors +SecurityTalkAgenda +StructuredText +SystemInfo +TitleIndex +UpdateProblems +UserPreferences +HelpOnUserPreferences +WantedPages +WordIndex +X11R682ReleasePlan +Other(2f)Press(2f)X11R682Released +X11R6970ReleasePlan +X11R68ScreenShots +X11R68Release +X11R6970Testing +PressReleases(2f)X11r682Released +X11R682Release +PressReleases(2f)X11R6970Released +X11R681Release +X11R6970ReleaseStatus +PressReleases(2f)X11r682Released(22) +X11R69Release +X11R68ReleaseStatus +X11R68PostPartumNotes +X11R68ReleasePlan +Other(2f)Press(2f)X11R6970Released +Other(2f)Press(2f)X11R76Released +ChangesForX11R71 +PressReleases(2f)X11R72Released +Other(2f)Press(2f)X11R72Released +DeprecatedInX11R7 +X11R71Release +X11R72Issues +X11R72Release +ChangesForX11R73 +ChangesForX11R72 +X11R7and69TODO +X11R70Release +PressReleases(2f)X11R71Released +Other(2f)Press(2f)X11R71Released +Other(2f)Press(2f)X11R75Released +XDevConf +XDevConf(c38a)mbridge2005 +XKBLayoutCreationNotes +XKB +fosdem2013 +XsltVersion +apm +Dating(20)Success(20)For(20)Single(20)Boomer(20)Women(2c20)Should(20)I(20)Consider(20)Cougar(20)Dating(3f202d20)Dating(20)Benjamin(20)Braddock +GSoCApplication +Flash(20)Games(20)or(2e20)Full(20)Generation(20)Games +HelpOnInstalling(2f)WikiInstanceCreation +XInputCoordinateTransformationMatrixUsage +LatiaR +Lasers(2b)and(2b)aviation(2b)safety +LinuxTagOrganization2006 +PVD(2c)PVD(2b)coatings +Development(2f)Documentation(2f)XServerStableBranchManagement +MarinaLatini +Development(2f)Documentation(2f)InputEventProcessing +Development(2f)Documentation(2f)Security +BuildingDocumentation +Development(2f)Documentation(2f)Multitouch +A(20)Few(20)Questions(20)On(20)Realistic(20)debt(20)consolidation(20)loans(20)Solutions +Terminology(20)Intended(20)for(20)Wedding(20)Invitations(203a20)An(20)overview +ConfigurationHelp +edible(20)Arrangements(20)Coupons(20)creative(20)concepts(20)33 +Proactol(20)creative(20)ideas(20)49 +XorgFoundation(2f)Reports(2f)2010 +ModularizationWorkingGroup +Every(20)organization(20)wants(20)qualified(20)marketing(20)and(20)advertising(202d20)check(20)why(20)Seo(20)is(20)known(20)as(20)a(20)appropriate(20)method(20)of(20)drawing(20)clients(20)interest +Development(2f)Documentation(2f)ServerProfiling +Development(2f)Documentation(2f)Multiseat +ati +installation(2f)yesevpajaron +Lifeflow(20)Meditation(20)Is(20)the(20)Simpler(20)Way(20)to(20)Achieve(20)Deep(20)Meditation +Humor(20)seems(20)to(20)be(20)the(20)very(20)best(20)response(20)for(20)any(20)complications(20)folks(20)need(20)to(20)control +Development(2f)Documentation(2f)KdriveDrivers +HelpOnInstalling(2f)InternetInformationServer +NatishaG3 +HelpOnConfiguration(2f)CascadingStyleSheets +Housing(2b)renovation +In(20)which(20)and(20)how(20)you(20)can(20)easily(20)develop(20)you(20)Search(20)engine(20)optimization(20)expertise +Development(2f)Documentation(2f)UsingEclipse +Development(2f)Documentation(2f)WritingDocumentation +WebStatistics +Information(20)on(20)Significant(20)Aspects(20)Throughout(20)it(20)support +Development(2f)Documentation(2f)ReleaseHOWTO +Development(2f)Documentation(2f)CursorHandling +HelpOnSlideShows(2f)900_Last_but_not_least(3a)_Running_your_presentation(2e) +MatildaLrn +Prudent(20)Strategies(20)In(20)debt(20)consolidation(20)loans(202d20)Some(20)Useful(20)Questions +Search(20)Engine(20)Optimisation +Donations +HelpOnConfiguration(2f)EmailSupport +Development(2f)Documentation(2f)XGE +WikiCourse(2f)BasicIntroduction(2f)210_Organisation_and_Structure +Documentation +Other(2f)Press(2f)501c3StatusDetermination +Development(2f)Documentation(2f)git +SizeGenetics(20)Stretcher(20)Evaluation(202a20)Read(20)Before(20)getting(20)Discounted(20)Promotion +PeopleProjectsPresentation +wiki(2f)Development(2f)Documentation(2f)Obsolescence +High(20)Fiber(20)Diet(20)Nuggets(20)of(20)information(20)64 +Development(2f)Documentation(2f)Performance +Development(2f)Documentation(2f)Glossary +Wedding(20)Invitation(20)Wording(20)Basics +male(20)Edge(20)Nuggets(20)of(20)information(20)49 +KatiaNh +HelpOnConfiguration(2f)SecurityPolicy +UserDocumentation +Development(2f)Documentation(2f)DevPrivates +XKBLayoutCreationNotes +Development(2f)Documentation(2f)DocBookConversion +Development(2f)Documentation(2f)SubmittingPatches +Development(2f)Documentation(2f)HowVideoCardsWork +SiteNavigation +zara(20)Shoes(20)Nuggets(20)of(20)information(20)49 +atidrivers +Development(2f)Documentation(2f)Protocol(2f)OpCodes +Development(2f)Documentation(2f)VersionNumberScheme +ATIProprietaryDriver +Development(2f)Documentation(2f)WrappingFunctions +Seoul(2c20)the(20)introduction(20)of(20)foreign(20)language(20)specialists(2022)International(20)Taxi(22) +debt(20)consolidation(202d20)New(20)Insights +Flash(20)Games(20)vs(2e20)Full(20)Generation(20)Games +Development(2f)Documentation(2f)MPX +NatishaS +Development(2f)Documentation(2f)XserverSourceLayout +Development(2f)Documentation(2f)PointerAcceleration +Development(2f)Documentation(2f)PointerAccelerationAsOf16 +Development(2f)Security(2f)Organization +Development(2f)Documentation(2f)XorgVideoHOWTO +ModularizationDevelPlan +AngelikaTi +Development(2f)Documentation(2f)XorgInputHOWTO +search(2b)engine(2b)optimization +HelpOnInstalling(2f)BasicInstallation +Development(2f)Documentation(2f)Obsolescence +Expensive(20)Games(20)or(2e20)Full(20)Creation(20)Games +HelpOnSlideShows(2f)100_Creating_the_slides +FAQMigration +XorgDeveloperDocumentation +ProgrammingDocumentation +Development(2f)Documentation(2f)ClientSideThreads +TheShopper(27)sInformationToShort(20)Cocktail(20)Dresses +XorgFoundation +UserDocumentation(2f)GettingStarted +Bank(2b)of(2b)Communications +Popular(20)Interview(20)Questions(20)Differ(20)Per(20)Occupations +HelpOnNavigation +LookingGlassIntegration +HelpOnAdministration +GitMigration +Development(2f)Documentation(2f)GrabProcessing +MatildaBv +Expert(20)Search(20)engine(20)optimization(20)and(20)suchmaschinenoptimierung(3a20)Outsource(20)the(20)Job(20)or(20)decide(20)to(20)educate(20)yourself(20)and(20)diy +WikiCourse(2f)BasicIntroduction(2f)191_Creating_new_Pages +Development(2f)Documentation(2f)UsingCtags +Drivers(20)and(20)documentation(20)for(20)ATI(2f)AMD(20)GPUs +Development(2f)Documentation(2f)ServerDebugging +HelpOnConfiguration +atimisc +JLatia +HelpOnPageCreation +Development(2f)Documentation(2f)BuildingDocumentation +ModularizationProposal +X(2e)Org(2d)GSoC2008(2d)Application +Tava(20)Tea(20)creative(20)concepts(20)19 +Events(2f)XDC2012(2f)PublicTransportation +HelpOnUpdating +Adultdating_587 +atimisc +chips +IntelLaptopChips +cyrix +fbdev +fosdem2006Daniel +fosdem2006Egbert +fosdem2006Luc +fosdem2006Matthias +fosdem2006Stephane +AMDGeodeDriver +geode +GeodeDriver +glide +glint +Casement(20)Window(20)sexcam(20)Handles +i128 +i740 +imstt +IntelMemoryChannels +IntelVideoDriver +Intel28Branch +IntelGraphicsDriver +IntelLaptopChips +Intel29Branch +intel +neomagic +newport +openscourse +nsc +r128 +radeonhd(3a)experimental_3D +vmware(2f)vmware3D +(d098d0b3d0bed180d18c20d094d0b5d0bcd187d0b5d0bdd0bad0be) +radeonhd(3a)r600_demo +Exam(2b)Microsoft(2b)74(2d)137(2b)Demo +radeonhd(3a)r6xx_r7xx_branch(272727)experimental(272727) +radeonhd(3a)r6xx_r7xx_branch +radeon(3a)r6xx_r7xx_branch +CvsBranches +Server14Branch +radeonhd(3a)r6xx_r7xx_branch(272727)experimental(272727) +Intel28Branch +Server13Branch +Server12Branch +Server19Branch +Development(2f)Documentation(2f)XServerStableBranchManagement +Server17Branch +Server16Branch +Intel29Branch +Server111Branch +Server110Branch +Server15Branch +Server112Branch +radeonhd(3a)r6xx_r7xx_branch +Server18Branch +CvsBranchnames +radeon(3a)r6xx_r7xx_branch +Server113Branch +rendition +siliconmotion +sunbw2 +suncg14 +suncg3 +suncg6 +sunffb +sunleo +suntcx +tdfx +Present(20)And(20)Future(20)Market(20)Trends(20)For(20)Mortgage(20)Savings(20)Account +tga +hotgal1 +Canada(20)Mortgage(20)Savings(20)Account(202d20)What(20)exactly(20)is(20)up(20)for(20)grabs(20)For(20)2010(2d)2011(3f) +tseng +VgaArbiter +vga +Lasers(2b)and(2b)aviation(2b)safety +bellaviahansard204 +via +Vivian56 +Sylvia5 +VivianLke +SylviaLv diff --git a/trident.mdwn b/trident.mdwn new file mode 100644 index 00000000..30246e73 --- /dev/null +++ b/trident.mdwn @@ -0,0 +1,15 @@ + + +# trident + +Driver for Trident based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.freedesktop.org/~xorg/current/doc/trident.4.html]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/vesa.mdwn b/vesa.mdwn new file mode 100644 index 00000000..c3c9aeba --- /dev/null +++ b/vesa.mdwn @@ -0,0 +1,15 @@ + + +# vesa + +Driver for VESA based video chips. License: MIT + + +## Documentation and Support + + * Please check the [[manual page|http://www.x.org/archive/X11R7.0/doc/html/vesa.4.html]] for the current release for configuration options. + +## Known Issues + + +### Release 6.7.0 diff --git a/vmware.mdwn b/vmware.mdwn new file mode 100644 index 00000000..eb82a3e8 --- /dev/null +++ b/vmware.mdwn @@ -0,0 +1,36 @@ + + +# Drivers for VMware virtual graphics + + +## Drivers + +The Xorg graphics driver for the VMware virtual graphics- and mouse devices consist of + +* xf86-video-vmware - The video driver. Driver binary is vmware_drv.so. The version 12.0 contains support for accelerated OpenGL. +* xf86-input-vmmouse - The mouse driver. Driver binaries are vmmouse_drv.so and vmmouse_detect +* The kernel video driver - vmwgfx. This currently resides in kernel 3.2.0 and higher. + +### 3D support + +Don't miss [[our 3D page|vmware/vmware3D]]! + + +## Maintainer + +VMware currently maintain these drivers. The maintainer email is <linux-graphics-maintainer-at-vmware-dot-com>. Patches touching the driver should have an Acked-by: or Signed-off-by: from a maintainer, and new releases are cut by a maintainer only. Please send patches and release requests to the xorg-devel mailing list with a CC to the maintainer email. + + +## License + +MIT-style. + + +## News + +* 2012-02-10 Zack Rusin has pushed a patch to mesa master which makes accelerated OpenVG run on vmwgfx EGL, in addition to the OpenGL and OpenGL-ES APIs (OpenVG requires the egl_gallium EGL driver, not the egl_dri2 EGL driver). This patch will be cherry-picked for mesa 8.0, but OpenVG and OpenGL-ES on vmwgfx is still experimental and not officialy supported. +* 2012-02-10 The kernel driver version 2.4.0 now contains support for fake page-flipping. This is to enable support for the Wayland demo compositor to run on vmwgfx EGL on the drm platform. I'ts called "fake" because currently it's implemented as a blit operation, and we don't yet support sync-to-vblank. The fake page-flipping support will probably enter linux 3.4.0, but anyone eager to try out can use the standalone vmwgfx kernel driver. +* 2012-02-07 Our enhanced drivers with [[RandR12|RandR12]]+ and 3D support are now enabled by default in ubuntu 12.04 daily build isos. +* 2012-01-24 VMware Workstation 8.0.2 and VMware Player 4.0.2 have been released. These releases contain correctness- and performance fixes for Linux 3D. +* 2012-01-13 An alpha version of a 3D / KMS [[/RandR12|vmware/RandR12]] - capable xf86-video-vmware is due to be released in the next few days Refer to our [[3D|vmware/vmware3D]] page for additional information. +* 2012-01-11 xf86-video-vmware 11.1.0 was released. This is a stable release.
\ No newline at end of file diff --git a/vmware/vmware3D.mdwn b/vmware/vmware3D.mdwn new file mode 100644 index 00000000..5dd6a0af --- /dev/null +++ b/vmware/vmware3D.mdwn @@ -0,0 +1,32 @@ + + +# Support for 3D acceleration and RandR 1.2 in xf86-video-vmware + + +## What's needed + +* xf86-video-vmware >= 11.9.x. The stable release will be named 12.0.0 +* A linux kernel with the post-staging version of the vmwgfx driver enabled. The vmwgfx kernel driver version should be 2.3.0 or higher. +* A Mesa release or checkout from the 8.0 branch with the dri-vmwgfx and xa-vmwgfx targets enabled. +* VMware Workstation 8.0.2, VMware Fusion 4.1.2 or VMware Player 4.0.2. Strictly the driver should run with Workstation 8.0, Fusion 4.0 or Player 4.0, but glxSwapBuffers will be very slow and there might be some additional rendering problems as well. In short: At least don't try to benchmark the driver performance withouth a recommended version of Workstation, Fusion or Player. +* libdrm does not need any specific vmware options enabled. + +## Generic User Notes + +* Due to the way software- (2D) and accelerated (Video, 3D) contents are mixed, certain operations may be slow when both accelerated contents and software contents overlap. Mixing software- and accelerated contents in a virtual environment is tricky and we've tried to optimize the driver to give the best possible interactive experience for most use cases and the new 3D-enabled compositors. +* XRender will usually not be accelerated unless operating on previously rendered 3D- or video surfaces. Therefore setups that use XRender for big operations, like XRender-enabled compositing managers, may consume a lot of CPU on large screens. The interactivity feeling when running, for example Kwin with Xrender effects enabled should be fairly good, particularly if your processor is fast. +* On multi-monitor setups the glxSwapBuffers operations are still a bit slow. This will be addressed in future Workstation / Fusion releases. To somewhat work around this problem, it's possible to reduce the Workstation / Fusion GUI update frequency using the following .vmx file option: (The number is the minumum delay in microseconds between GUI updates). + [[!format txt """ +svga.frameRateLimitUS = 15000 +"""]] +* Applications that warp the cursor, like games or the Compiz spinning cube will not work well with VMmouse enabled, since it uses the host cursor. If this becomes a problem for you, please use the following .vmx file option to disable VMmouse, and use the VMware relative USB mouse instead: (Motion ungrab will be lost and you'll see a slightly increased cursor lag). [[!format txt """ +mouse.vusb.enable = "TRUE" +"""]] +* The VMware absolute USB mouse device may, on many distributions, be detected by the udev system as a joystick. This may lead to games moving the cursor to the upper left corner or the game constantly registering a leftward-upward motion. To work around this, please disable joystick use in the game's setup, or if you have another joystick, select that one instead. +* If you use fancy RandR 1.2 features, like rotation and / or scaling and at the same time use VMMouse, cursors may not behave as expected. In that case, set up the relative USB mouse as described above. The driver is only capable of displaying a single hardware cursor at a time, so if more cursors need to be displayed, like when cloning outputs, the driver will automatically revert to software cursors. + +## Generic Developer Notes + +* What is SAA, and why wasn't EXA used? SAA or "Shadow Acceleration Architecture" is a simple acceleration architecture with combines code from both EXA and Intel's UXA. SAA is very simple and intended to be used by drivers that really don't want to accelerate everything, and if the driver needs to accelerate, SAA attempts to accurately track exactly what contents is accelerated. The idea behind this is that it's often more costly to set up the accelerator state than to perform the render operation in software on cached memory. The drawback is that large copies or render operations are slower. EXA and UXA aren't tracking rendered areas carefully enough, and modifying EXA to do that would have required invasive changes in internal- and driver EXA apis. However, it should, with a decent amount of work and testing, be possible to implement SAA as an EXA migration policy. +* Is xf86-video-vmware eventually going to accelerate 2D and XRender fully? Possibly, but in virtual environments, migration between guest contents (software rendered stuff) and hypervisor contents (accelerated stuff) is slow and painful. Creation and destruction of accelerated pixmaps is also a very slow operation. The fact that [[D3D9|D3D9]] doesn't support logicops is also a limiting factor. To fully support 2D and XRendeR operation means that we must be able to accelerate everything, and when there are fallbacks we need render in software and blend the result onto the destination, possibly using logicops and non-rectangular shapes for things like diagonal lines. The question then arises whether this will actually give better interactivity than the current mixing of software- and accelerated contents. +* What is XA and how is SAA and XA related? XA is a freestanding acceleration API that is intended to be useful for X acceleration architectures. The VMware driver is using it to handle acceleration requests from SAA, but it could also theoretically be interfaced with EXA or UXA. The XA version used by xf86-video-vmware is naturally using Gallium3D to accelerate, but it should also be possible to implement XA on top of EGL, for example. XA has support for XRender-like operations and YUV conversions. It's used by xf86-video-vmware to accelerate XRender when needed, for accelerated copies when needed (glxSwapBuffers or compositing of previously accelerated contents), and for the textured XVideo adaptor.
\ No newline at end of file |
