This commit is contained in:
gferg 2001-01-24 17:29:30 +00:00
parent 396b02f3e7
commit 5b93e480b1
1 changed files with 8 additions and 4 deletions

View File

@ -8,7 +8,7 @@
<author>
<firstname>Toby</firstname><surname>Russell</surname>
</author>
<pubdate>v0.1, January 2001</pubdate>
<pubdate>v0.5, January 2001</pubdate>
<abstract>
<para>
@ -29,7 +29,7 @@ Even though I know this procedure works I feel obliged to point out that what I
</para>
<para>
Finally, no introduction would be complete without the following words of caution; I feel this mini-HOWTO should be regarded as a 'bare bones' set of instructions and should therefore be followed with all relevant README literature to hand. What follows is not exhaustive by any stretch of the imagination, and needs, at least for beginners, said README stuff.
Finally, no introduction would be complete without the following words of caution; I feel this HOWTO should be regarded as a 'bare bones' set of instructions and should therefore be followed with all relevant README literature to hand. What follows is not exhaustive by any stretch of the imagination, and needs, at least for beginners, said README stuff.
</para>
</sect1>
@ -234,6 +234,10 @@ select the appropriate sub-option of "/dev/agpgart (AGP) support" (again not as
</listitem>
</itemizedlist>
<para>
(It has been pointed out to me that loading these features as modules would be more logical, since they are not required until <command>startx</command> is run. I have not tried the 'loadable module way' yet and will ammend this section of the HOWTO after I have tested it. I recommend the static mode here because I ran this procedure on a test version of the 2.4.0 kernel and it was suggested to me that loading statically was a safer and stabler way to go. Now that 2.4.0 is officially out there, perhaps modules will be more sensible. I'll let you know how it goes. (Thanks to Heron Ordonez for this.))
</para>
<note><title>Note</title>
<para>
The above explanation assumes you have run <command>make menuconfig</command> and so a little thinkology will be required to map it to a situation where <command>make</command> has been issued instead. But only a little.
@ -307,7 +311,7 @@ so that the crisp, shiny, new linux kernel is known by lilo, otherwise (I have e
</para>
<para>
which basically, and here I shall fully expose my weak understanding of this bit, creates the very essential (X won't run without it) module that the i810 requires to do its thing. Pretty scientic stuff there. Sorry about that.
which basically creates the very essential (X won't run without it) driver (character special file) which acts kinda like a 'go-between' for the i810 and the X server. (Thanks to Heron Ordonez for saving me some embarrassment here.) Pretty scientic stuff there. Sorry about that.
</para>
<para>
@ -425,7 +429,7 @@ So if X reports errors about a "shape extender" or "shape extension", you may we
<title>Thank you</title>
<para>
I must point out that I would not have known how to fix the i810 and X4.x problem if it were not for the pioneering efforts of Val Henson who guided me through the process and recommended the 2.4.0 kernel in the first place. I have also received help of a quite delectable variety from Bill McClain, who kindly polished my rough draft with his highly pronounced editing skills until it became the shining beast you have just so enjoyed.
I must point out that I would not have known how to fix the i810 and X4.x problem if it were not for the pioneering efforts of Val Henson who guided me through the process and recommended the 2.4.0 kernel in the first place. And now that this is an ammended version, I would also like to thank Heron Ordonez for pointing out a few problems which I have in part addressed, and will fully address in due course. This is an open process and all comments (politely phrased of course!) are welcome.
</para>
</sect1>