Sorry; let me qualify that - 2.6 isn't yet generally "fully supported". I was thinking of compiling so as to be able to load kernel modules, and specifically to handle the changes in 'kbuild' in 2.6.6 (which were useful changes in the kernel, in my view).
There are outstanding 2.6 issues otherwise, as far as I'm aware (i.e., unless Dave has solved them all already).
I can look into your idea of separating a KOPTS from XOPTS. That's partly the purpose of MODOPT, but it doesn't consider all possible kernel options. In fact, what you're thinking may be different from what you're suggesting. Accomodating all possible kernel config options will require something like a kernel-aware autoconf macro set, and thus an autoconf-based 'configure' and Makefiles. I'm working towards that, but I'm now off on an "experimental" branch that may not become mainline LiS soon (if ever). It will be up to Dave to choose what stays experiment and what becomes mainline, and I'm content with leaving him with that choice (though not content if I can't experiment in the first place...).
-John
John A. Boyd Jr. wrote:
I haven't seen this, but then, I hadn't thought about CONFIG_REGPARM.
But can I suggest that this might be a 2.6.4 issue that might be resolved in 2.6.6? 2.6.5 and before didn't support symbols that aren't properly kernel-built very well; 2.6.6 does better. 2.17.K doesn't support 2.6.6, though, but again, my post-K patches to Dave might be of interest, since they do fully support 2.6.6.
_______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
