All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: "Mark Wallis" <mwallis@serialmonkey.com>, netdev@vger.kernel.org
Subject: Re: Hardware button support for Wireless cards
Date: Mon, 15 May 2006 15:59:47 +0200	[thread overview]
Message-ID: <200605151559.50838.IvDoorn@gmail.com> (raw)
In-Reply-To: <20060515152513.5095b2d5@griffin.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

On Monday 15 May 2006 15:25, Jiri Benc wrote:
> On Mon, 15 May 2006 22:57:12 +1000, Mark Wallis wrote:
> > Currently, in our rt2x00 (using the devicescape stack) we are firing off an
> > ACPI event so that the hardware button can be handled in userspace. This
> > allows the user to basically do whatever they want when this button is
> > pressed - including bringing down the wireless interface. The problem here
> > is no distro's currently contain scripts to run from this event so for many
> > users it just "doesn't work" without them manually having to write scripts
> > to handle the ACPI even themselves.
> 
> Distributions will need to accommodate to the way d80211 stack works
> anyway, so I see no problem with this.
> 
> > B. should we be firing an ACPI event and getting the distro's to add scripts
> > so when this event is fired they bring down all the wireless interfaces.
> 
> Voting for this. It brings more flexibility.
> 
> This is not a problem of your card only. Is there a standard ACPI
> rf-kill event?

Not sure actually. the approach rt2x00 takes is sending an event ACPI_TYPE_EVENT
with as argument a 0 or 1 depending on the new state of the button.
But I don't know if there is another event that would be more suitable for a hardware button.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-05-15 13:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 12:57 Hardware button support for Wireless cards Mark Wallis
2006-05-15 13:25 ` Jiri Benc
2006-05-15 13:59   ` Ivo van Doorn [this message]
2006-05-15 14:06 ` Sergey Vlasov
2006-05-15 14:37 ` Dan Williams
2006-05-15 15:12   ` Ivo van Doorn
2006-05-15 16:20     ` Jouni Malinen
2006-05-16  3:10       ` Mark Wallis
2006-05-25 15:15         ` [RFC PATCH 0/2] " Ivo van Doorn
2006-05-15 16:19   ` David Zeuthen
2006-05-15 15:27 ` Jason Lunz
2006-05-15 16:01   ` Michael Buesch
2006-05-15 19:12     ` Dan Williams
2006-05-15 19:32       ` Michael Buesch
2006-05-15 19:46       ` Jason Lunz
2006-05-15 21:42         ` Ivo van Doorn
2006-05-15 20:08   ` John W. Linville

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=200605151559.50838.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=jbenc@suse.cz \
    --cc=mwallis@serialmonkey.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.