linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: linux-input@vger.kernel.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: rfkill-input understanding help
Date: Fri, 11 Jan 2008 20:08:00 +0100	[thread overview]
Message-ID: <200801112008.00927.IvDoorn@gmail.com> (raw)
In-Reply-To: <200801110323.38279.carlos@strangeworlds.co.uk>

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

  reply	other threads:[~2008-01-11 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11  3:33 rfkill-input understanding help Carlos Corbacho
2007-12-30 18:59 ` Ivo van Doorn
2007-12-31  1:00   ` Carlos Corbacho
2008-01-02 19:10     ` Ivo van Doorn
2008-01-11  3:23       ` Carlos Corbacho
2008-01-11 19:08         ` Ivo van Doorn [this message]
2008-01-11 20:34           ` Dmitry Torokhov
2008-01-12  0:32             ` Carlos Corbacho
2008-01-22  0:55               ` Carlos Corbacho
2008-04-12 17:21                 ` Carlos Corbacho
2008-04-13 11:23                   ` Carlos Corbacho
2008-04-14 18:12                     ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801112008.00927.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=carlos@strangeworlds.co.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).