Hi!
> > Well, I don't know whether this is good or bad. Yes, this makes the
> > module stay in the kernel as long as there are any mice or keyboards
> > connected.
> >
> > I don't know if this is desirable.
>
> I think it is.
>
> > I myself, while developing, depend quite a lot on inserting/removing
> > these modules most of the time without having to unplug the mice.
>
> Yes, but you should acknowledge that this need only affects you as
> an individual. What about this:
>
> #include <module.h>
> #ifdef USB_BEING_DEVELOPED /* to ease rmmod/insmod with mouse in */
> # undef MOD_INC_USE_COUNT
> # define MOD_INC_USE_COUNT /* nothing */
> # undef MOD_DEC_USE_COUNT
> # define MOD_DEC_USE_COUNT /* nothing */
> #endif
>
> and then
>
> export CC="gcc -DUSB_BEING_DEVELOPED~
>
> ?
>
> Note that I definitely don't like ifdef's in the middle of code, but
> this can go at the beginning of the files.
I do not think this is good idea.
The module CAN be removed. You loose your mouse, but that's it. I
think we really need two numbers, as vojtech suggested.
Pavel
PS: At worst, define new MOD_INC_USE_COUNT_SOFT, which means "don't
unload me automatically, but allow unload on user request". And
#define MOD_INC_USE_COUNT_SOFT MOD_INC_USE_COUNT untill we have
something better.
--
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents me at [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
