|
Lines 130-136
Link Here
|
| 130 |
|
130 |
|
| 131 |
<p> |
131 |
<p> |
| 132 |
The details of how these elements interplay is somewhat complex. Hopefully the |
132 |
The details of how these elements interplay is somewhat complex. Hopefully the |
| 133 |
following section will break the concepts into more easily digestable pieces, |
133 |
following section will break the concepts into more easily digestible pieces, |
| 134 |
such that developers and users wishing to enhance or use this new system will |
134 |
such that developers and users wishing to enhance or use this new system will |
| 135 |
have the knowledge needed to do so. |
135 |
have the knowledge needed to do so. |
| 136 |
</p> |
136 |
</p> |
|
Lines 219-230
Link Here
|
| 219 |
<path>.config</path> and <path>bzImage</path> will no longer be in |
219 |
<path>.config</path> and <path>bzImage</path> will no longer be in |
| 220 |
<path>/usr/src/linux</path> as they were before. <mail |
220 |
<path>/usr/src/linux</path> as they were before. <mail |
| 221 |
link="latexer@gentoo.org">Peter Johanson</mail> has written a new 2.6 kernel |
221 |
link="latexer@gentoo.org">Peter Johanson</mail> has written a new 2.6 kernel |
| 222 |
guide oriented at end users which emphasises the kbuild changes and in |
222 |
guide found <uri |
| 223 |
particular the new locations of these files. |
223 |
link="http://www.gentoo.org/doc/en/2.6-koutput-user.xml">here</uri> oriented at |
|
|
224 |
end users which emphasizes the kbuild changes and in particular the new |
| 225 |
locations of these files. |
| 224 |
</p> |
226 |
</p> |
| 225 |
|
227 |
|
| 226 |
<!-- TODO What guide? Where? --> |
|
|
| 227 |
|
| 228 |
</body> |
228 |
</body> |
| 229 |
</section> |
229 |
</section> |
| 230 |
</chapter> |
230 |
</chapter> |
|
Lines 429-439
Link Here
|
| 429 |
</pre> |
429 |
</pre> |
| 430 |
|
430 |
|
| 431 |
<p> |
431 |
<p> |
| 432 |
Most ebuilds will generally need one patch to the makefiles to enabled outputing |
432 |
Most ebuilds will generally need one patch to the makefiles to enabled |
| 433 |
to a different directory, and then do some sedding if is_koutput() returns true. |
433 |
outputting to a different directory, and then do some sedding if is_koutput() |
| 434 |
The example ebuild below will show how that is handled. For those ebuilds |
434 |
returns true. The example ebuild below will show how that is handled. For those |
| 435 |
needing to more work by hand (nvidia-kernel is one), there are a few functions |
435 |
ebuilds needing to more work by hand (nvidia-kernel is one), there are a few |
| 436 |
that may be called individually for more find grained control. |
436 |
functions that may be called individually for more find grained control. |
| 437 |
</p> |
437 |
</p> |
| 438 |
|
438 |
|
| 439 |
<table> |
439 |
<table> |
|
Lines 604-612
Link Here
|
| 604 |
<c>KMOD_KOUTPUT_PATCH</c>. These can be set as needed to specify which |
604 |
<c>KMOD_KOUTPUT_PATCH</c>. These can be set as needed to specify which |
| 605 |
sources should be unpacked by kmod_src_unpack() and a file to patch if |
605 |
sources should be unpacked by kmod_src_unpack() and a file to patch if |
| 606 |
we find that koutput is being used. <c>KMOD_KOUTPUT_PATCH</c> will |
606 |
we find that koutput is being used. <c>KMOD_KOUTPUT_PATCH</c> will |
| 607 |
<b>not</b> be applied if it is discovered that the 2.6 kernel is still outputing |
607 |
<b>not</b> be applied if it is discovered that the 2.6 kernel is still |
| 608 |
to <path>/usr/src/linux</path> in the old fasion. Here is a trimmed down version |
608 |
outputting to <path>/usr/src/linux</path> in the old fashion. Here is a trimmed |
| 609 |
of the src_compile() function: |
609 |
down version of the src_compile() function: |
| 610 |
</p> |
610 |
</p> |
| 611 |
|
611 |
|
| 612 |
<pre caption="src_compile() function"> |
612 |
<pre caption="src_compile() function"> |
