All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Bob Copeland <me@bobcopeland.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] [PATCH] ath5k: convert LED code to use mac80211 triggers
Date: Wed, 09 Jul 2008 09:00:48 +0200	[thread overview]
Message-ID: <48746220.8010703@gmx.de> (raw)
In-Reply-To: <b6c5339f0807081922q2941a597m6e135fc7fb907fb@mail.gmail.com>

Bob Copeland wrote:
> On Tue, Jul 8, 2008 at 7:08 PM, Helge Deller <deller@gmx.de> wrote:
>> I tested it against Linus' head version (it applied with minor
>> modifications) on my HP NC6000 laptop with this built-in Atheros card:
> [...]
>> Basically it works, but I think the sc->led_on in:
>>> +     sc->led_on = 0;  /* active low */
>> needs to be:
>>> +     sc->led_on = 1;  /* active high */
>> for the AR5212 in the HP laptop.
> 
> Thanks for the test!
> 
>> See also the changes to if_ath_pci.c in:
>>  http://madwifi.org/attachment/ticket/1018/led.patch
>> and
>>  http://madwifi.org/ticket/1018
>> for an old discussion about madwifi for LEDs in the HP box.
> 
> So current madwifi doesn't have this change unless I missed something?

Yes, the patch has not been applied yet.

>  It appears to use active-low leds in the current version regardless
> of the vendor.

Yes.

Helge

      parent reply	other threads:[~2008-07-09  7:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 18:11 [PATCH] ath5k: convert LED code to use mac80211 triggers Bob Copeland
2008-06-25 12:12 ` Nick Kossifidis
2008-06-25 13:56   ` Bob Copeland
2008-06-26  2:35     ` Bob Copeland
2008-07-08 23:08       ` Helge Deller
2008-07-09  2:22         ` [ath5k-devel] " Bob Copeland
2008-07-09  2:40           ` Bob Copeland
2008-07-09  6:57             ` Helge Deller
2008-07-09  7:00           ` Helge Deller [this message]

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=48746220.8010703@gmx.de \
    --to=deller@gmx.de \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.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 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.