<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">diary of a window system hacker</title>
<subtitle type="html"><![CDATA[
can't think of a clever byline
]]></subtitle>
<id>http://www.fooishbar.org/blog/2005/Jan/24</id>
<link rel="alternate" type="text/html" href="http://www.fooishbar.org/blog" />
<link rel="self" type="text/xml" href="http://www.fooishbar.org/blog/2005/Jan/24" />

<author>
<name>Daniel Stone</name>
<uri>http://www.fooishbar.org/blog/2005/Jan/24</uri>
<email>daniel@fooishbar.org</email>
</author>
<rights>Copyright 2004-2009 Daniel Stone, licensed under Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License</rights>
<generator uri="http://pyblosxom.sourceforge.net/" version="1.3.2 2/13/2006">
PyBlosxom http://pyblosxom.sourceforge.net/ 1.3.2 2/13/2006
</generator>

<updated>2005-01-24T13:43:00Z</updated>
<!-- icon?  logo?  -->

<entry>
<title type="html">xorg isn&apos;t ready?</title>
<category term="/tech/x" />
<id>http://www.fooishbar.org/blog/2005/01/24/erich-2005-01-24-13-43</id>
<updated>2005-01-24T13:43:00Z</updated>
<published>2005-01-24T13:43:00Z</published>
<link rel="alternate" type="text/html" href="http://www.fooishbar.org/blog/tech/x/erich-2005-01-24-13-43" />
<content type="html">Erich Schubert asserts that &lt;a
href=&quot;http://blog.drinsama.de/erich/en/linux/debian/2005012301-xorg&quot;&gt;X.Org is
not ready for Sarge&lt;/a&gt;.  Firstly, it was never proposed for Sarge (monolithic
or modular), so that&apos;s kind of a moot point.
&lt;br /&gt;&lt;br /&gt;
Secondly, he points to a &lt;a
href=&quot;https://bugs.freedesktop.org/show_bug.cgi?id=2361&quot;&gt;bug opened today&lt;/a&gt;
on Radeon, and declares that it is undoubtedly only one of a massive number
of problems waiting under the surface.  This bug only affected one very
specific class of chips (rv100/rv200, aka Radeon 7000/7200; not r100 or r200,
which are the same class), it was opened today with a patch from Dave Airlie,
and as I read that blog entry, I had a test X.Org build running around my
machine with that patch already included, as I&apos;d seen the leadup to that bug
on IRC, and had an X.Org upload planned anyway.  So, I doubt a problem that
only affected an infinitesmal percentage of users (Radeon 7500s are far more
popular than 7000s in that class, and I&apos;m not entirely convinced anyone
actually owns a 7200), that was resolved as soon as it conclusively came up,
can be a pointer to anything.
&lt;br /&gt;&lt;br /&gt;
In fact, I think you will find the amount of hardware support in X.Org (out
of the largest three vendors, all have new chipsets supported in X.Org that
aren&apos;t supported in XFree86 4.3 -- ATI&apos;s r4xx series[0], nVidia&apos;s GeForce6
series of chips[1], and Intel&apos;s i9xx series[2], are totally unsupported) is
so vastly improved that, even if the &apos;everything is broken and no-one
noticed until now&apos; allegation is true, the staggering weight of hardware
supported under X.Org but not under XFree86 would be enough to counter
this.  Also, with Ubuntu, Fedora Core, Mandrake, SuSE, FreeBSD, Gentoo,
and everyone else on the planet using X.Org at this stage, I think if it
had massive problems, then it would be *very* well-documented.
&lt;br /&gt;&lt;br /&gt;
I don&apos;t think extrapolating from one specific (and very quickly-fixed) problem
to all of X.Org being totally unusable is valid, or fair.
&lt;br /&gt;&lt;br /&gt;
PS: Ubunt&lt;strong&gt;u&lt;/strong&gt;.
&lt;br /&gt;
PPS: r100 is Radeon 7500, rv100 is Radeon 7000, and rv200 is Radeon 7200;
     neither of the latter two are very widely-used at all.
&lt;br /&gt;&lt;br /&gt;
[0]: Not to mention &lt;strong&gt;massively&lt;/strong&gt; improved display detection
     for every other chipset.&lt;br /&gt;
[1]: I believe Debian&apos;s XFree86 packages have some of this support backported,
     but not all.&lt;br /&gt;
[2]: And for i8xx chipsets also, widescreen/non-standard displays are detected
     and set up just fine without needing to use 855patch, 865resolution, or
     any of that class of monumental hacks.
</content>
</entry>
</feed>
