Gentoo Archives: gentoo-dev

From: Peter Johanson <latexer@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] [RFC] 'koutput' and the future of kernel module ebuilds.
Date: Thu, 12 Feb 2004 19:47:24
1 Hey all,
3 So I'm finally feeling comfortable enough with my latest work on kernel
4 module ebuilds that I want to get some more eyes looking at it and
5 feedback before I start rolling out changes. Most of the info on the
6 work i've been doing is at bug #32737
7 ( Beware, it's a long one.
8 A doc aimed at developers on the topic is available at:
11 First of all, this should in no way break 2.4 kernel module building at
12 all; the impetus for the changes was resolving issues with compiling
13 external modules against 2.6 kernel sources.
15 Second, the changes proposed to kernel-mod.eclass will *not* require
16 people to use the new method of outputting kernel output to seperate
17 directory. This is a new *feature* that will be unveiled eventually once
18 this is fully merged, but it is *not* a requirement. This should ease
19 the transition to this new method. I'm hoping the new method, which i've
20 dubbed "koutput," will be adopted by most users once it is available,
21 documentation is up, and the word is out.
23 The majority of wireless driver ebuilds, as well as nvidia-kernel have
24 been ported to the new kernel-mod eclass, and ati-drivers is next on my
25 list. What i'd like to finally see is a uniform documented, and
26 *VERSATILE* method for kernel modules which is suitable for 2.4, 2.6
27 with normal output, and with 2.6 and the new kbuild feature of
28 outputting to a second directory.
30 A few details may change, but the core of this work is done, and working
31 *very* well. What I need from people is comments on things, TESTING, and
32 help on getting other drivers i haven't gotten to yet ported. Also
33 things like genkernel, etc might need some small tweaking.
35 So please, discuss here, email me, bug me on irc in #gentoo-laptop, call
36 my apartment, stalk me by the guy i buy my NY times from in the morning,
37 whatever, as long as i can get more eyes on this and some testing from
38 the brave.
40 This is *not* a simple thing, as there's *LOTS* going on, so feel free
41 to ask if you need clarification on any points. I'm going to be
42 clarifying and expanding the developer doc a bit, and finishing a user
43 doc at some point soon.
45 *phew*
47 -pete
48 --
49 Peter Johanson
50 <latexer@g.o>
52 Key ID = 0x6EFA3917
53 Key fingerprint = A90A 2518 57B1 9D20 9B71 A2FF 8649 439B 6EFA 3917