On Friday 11 January 2008, Carlos Corbacho wrote:
> Well, the good news is that the code I have appears to work. But, I have
> something very strange going on with my kernel (latest ACPI git tree +
> acer-wmi on top) and rfkill-input.
>
> Basically, if I either:
>
> 1) Build rfkill-input into the kernel
>
> or
>
> 2) Build rfkill-input as a module, and use kmod to load it from acer-wmi
>
> Then rfkill-input doesn't work.
>
> If I load rfkill-input manually (or if already loaded by kmod; unload and
> then reload), everything works as expected. The (in progress) code to add
> rfkill support to acer-wmi is here (in case the problem is something wrong
> with the code) - as you can see, it's mostly based on the b43 work.
>
> My kernel config is here, in case I'm missing something obvious:
> http://files.strangeworlds.co.uk/config-acpi-git-20080111
Does it help when you run
request_module("rfkill-input");
_before_ calling acer_rfkill_init_device() ?
Perhaps the rfkill-input needs to be registered before input
devices are being registered. But I am not sure, Dmitry propably
knows more about possible ordering requirements for input
device and input trigger registration.
Ivo
-
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
