This package is a kernel module. Original method to actually use it is
to download it from sourceforge, run its make script which in doing so
it calls the make from /usr/src/linux to build just this module and put
it in /lib/modules/version/kernel/drivers/char/omnibook.ko then modprobe
it and use it. Now I decide I want to change a usb driver or something
unrelated in the kernel. So I make modules_install. Doing that clears
out the lib/modules/... directory. So now I have to remember to go back
into the omnibook tree and make && make install it. Every time I rebuild
the kernel. And if I forget to do that and reboot, I can't see my
battery level or use the volume buttons...
There is a script that comes with the omnibook module that would
effectively integrate it like this for 2.4 kernels, though it would not
do so for 2.6, and the 2.6-style Kconfig files were not included. I did
submit these new/changed files upstream but have seen no response to it.
Even if it did have a script to cleanly add it to 2.6, that would still
be extra effort each time I grab a new rev of kernel. Having it here as
a patch, all I need to do is add one line to any current kernel ebuild
to get it to add this functionality to my kernel every time, and I don't
have to worry about forgetting to rebuild an outside kernel module every
time I change something in the kernel.
And if this makes someone else's life easier too, then so much the
better.
On Thu, 2004-02-26 at 07:06, Collins Richey wrote:
> Why is it necessary to "roll your own"? Or is this patch something
> concocted by kernel developers and not yet released? Are the kernel
> developers even aware of this problem (they should be)? etc., etc.
>
> I guess the point is: I hope this isn't just a one-off, and I hope that
> a more standard approach will come from this!?
>
> My $.02.
--
Scott Taylor - <[EMAIL PROTECTED]>
BOFH Excuse #141:
disks spinning backwards - toggle the hemisphere jumper.
--
[EMAIL PROTECTED] mailing list
