linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Coatti <fabio.coatti@gmail.com>
To: "Hin-Tak Leung" <hintak.leung@gmail.com>
Cc: reinette chatre <reinette.chatre@intel.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"mjg@redhat.com" <mjg@redhat.com>
Subject: Re: iwlagn rfkill and 2.6.31 on Intel Corporation PRO/Wireless 5100 AGN
Date: Thu, 17 Sep 2009 11:16:19 +0200	[thread overview]
Message-ID: <200909171116.19281.fabio.coatti@gmail.com> (raw)
In-Reply-To: <3ace41890909161615u64d2878i8ddb52c2ba03ea52@mail.gmail.com>

I
> Hmm, I recently looked to the interaction between rfkill and hal, and
> may be able to answer that. The kernel rfkill module also exports its
> state via either /dev/rfkill or sysfs's /sys/class/rfkill (depending
> on kernel version; I think /dev/rfkill is new to
> 2.6.31/wireless-testing/compat-wireless, and not in 2.6.30). hald or
> devicekit (again, depend on distro/kernel version) monitors those, and
> informs NetworkManager via d-bus messaging when the rkfill state
> changes. NetworkManager then if up/down the device and tell
> wpa_supplicant accordingly. So the ifconfig-interface-up is supposed
> to happen automatically, if hald/devicekit works and talk to
> NetworkManager.
> 
> i.e. the waking-up should happen automatically if you have the
> combination of hald/devicekit and networkmanager.
> 
> Does this answer your question?
> 

Indeed; it's a good explanation of what's going on. Now I'll follow each step 
of your descripiton and I'll try to find out where the chain breaks :)


Many thanks for your help.

  reply	other threads:[~2009-09-17  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 13:21 iwlagn rfkill and 2.6.31 on Intel Corporation PRO/Wireless 5100 AGN Fabio Coatti
2009-09-16 13:25 ` John W. Linville
2009-09-16 14:57   ` Fabio Coatti
2009-09-16 16:30     ` reinette chatre
2009-09-16 22:05       ` Fabio Coatti
2009-09-16 23:15         ` Hin-Tak Leung
2009-09-17  9:16           ` Fabio Coatti [this message]
2009-09-17 12:39             ` Hin-Tak Leung

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=200909171116.19281.fabio.coatti@gmail.com \
    --to=fabio.coatti@gmail.com \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mjg@redhat.com \
    --cc=reinette.chatre@intel.com \
    /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).