From: Russ Dill <russ.dill@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
Tulio Magno Quites Machado Filho <tuliom@gmail.com>
Subject: Re: ath5k LEDs on Acer Ferrari 5000 laptop
Date: Mon, 9 Feb 2009 09:22:16 -0700 [thread overview]
Message-ID: <f9d2a5e10902090822i36989c8bl45c4a34c0cbb90b8@mail.gmail.com> (raw)
In-Reply-To: <20090209151221.M9585@bobcopeland.com>
On Mon, Feb 9, 2009 at 8:14 AM, Bob Copeland <me@bobcopeland.com> wrote:
> On Sun, 8 Feb 2009 23:09:49 -0700, Russ Dill wrote
>> I have an Acer Ferrari 5000 laptop with an ath5k wireless chipset. It
>> has an LED built into the rfkill switch on the front of the laptop. I
>> testing various settings within the ath5k driver an the led is on pin
>> 1 (sc->led_pin = 1) and it is active high (sc->led_on).
>
> When you say it is hooked up to rfkill, do you mean that enabling
> the rfkill turns off the led without the emachines patch? Some
> laptops have the led tied to rfkill in such a way that we don't
> actually need/want to program it from software.
>
I mean that there is a physical rfkill switch (actually more like a
toggle button) on the laptop:
http://i146.photobucket.com/albums/r245/MechNinja/IMG_2844.jpg
Because they are just buttons and not actual switches, they are lights
that should indicate whether or not a radio is on or off. This works
for bluetooth, but not for wireless lan. Without informing the driver
of the LED pin, the wireless lan LED never lights. Its a 100% soft
LED.
So no, the LED does not work with or without the emachines patch. It
only works if I instead set sc->led_pin to 1 and sc->led_on to 1. I
only mention the emachines patch because it tries to cover 100% of
AMBIT systems, whereas my laptop wireless chipset identifies as AMBIT,
but its LED is wired differently.
next prev parent reply other threads:[~2009-02-09 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 6:09 ath5k LEDs on Acer Ferrari 5000 laptop Russ Dill
2009-02-09 15:14 ` Bob Copeland
2009-02-09 16:22 ` Russ Dill [this message]
2009-02-09 16:50 ` Bob Copeland
2009-02-09 16:54 ` Johannes Berg
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=f9d2a5e10902090822i36989c8bl45c4a34c0cbb90b8@mail.gmail.com \
--to=russ.dill@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=tuliom@gmail.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