linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [ath5k-devel] [PATCH] Fix transmit LED on Acer Aspire One
  2009-02-23 19:37 ` John W. Linville
@ 2009-02-23 19:56   ` Bob Copeland
  0 siblings, 0 replies; 2+ messages in thread
From: Bob Copeland @ 2009-02-23 19:56 UTC (permalink / raw)
  To: John W. Linville
  Cc: Peter Chubb, linux-wireless, ath5k-devel, lrodriguz, jirislaby

On Mon, Feb 23, 2009 at 2:37 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Wed, Feb 18, 2009 at 02:07:05PM +1100, Peter Chubb wrote:
>> +     /* Enable softled on Acer Aspire One */
>> +     else if (pdev->subsystem_vendor == 0x105b && pdev->subsystem_device == 0xe008) {
>> +             __set_bit(ATH_STAT_LEDSOFT, sc->status);
>> +             sc->led_pin = 3;
>> +             sc->led_on = 0;
>> +     }
>>       if (!test_bit(ATH_STAT_LEDSOFT, sc->status))
>>               goto out;
>
> Any comment on this from the ath5k guys?  That 0x105b subvendor ID
> would seem to correspond to "Foxconn International, Inc.", which
> doesn't sound much like "Acer"...

It's already in wireless-testing with similar values.

Not quite apropos to this patch, someone with the ambit chipset said
the values didn't match up with his laptop, so we do need to add a
subsystem_device test I think, but it should have a #define in pci.h.
In any case there's usually no harm in enabling the wrong gpio pin,
unless rfkill happens to sit there.

-- 
Bob Copeland %% www.bobcopeland.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ath5k-devel] [PATCH] Fix transmit LED on Acer Aspire One
@ 2009-02-23 21:00 Xose Vazquez Perez
  0 siblings, 0 replies; 2+ messages in thread
From: Xose Vazquez Perez @ 2009-02-23 21:00 UTC (permalink / raw)
  To: linux-wireless, linville

Bob Copeland wrote:

> On Mon, Feb 23, 2009 at 2:37 PM, John W. Linville
> <linville@tuxdriver.com> wrote:
>> On Wed, Feb 18, 2009 at 02:07:05PM +1100, Peter Chubb wrote:
>>> +     /* Enable softled on Acer Aspire One */
>>> +     else if (pdev->subsystem_vendor == 0x105b && pdev->subsystem_device == 0xe008) {
>>> +             __set_bit(ATH_STAT_LEDSOFT, sc->status);
>>> +             sc->led_pin = 3;
>>> +             sc->led_on = 0;
>>> +     }
>>>       if (!test_bit(ATH_STAT_LEDSOFT, sc->status))
>>>               goto out;
>>
>> Any comment on this from the ath5k guys?  That 0x105b subvendor ID
>> would seem to correspond to "Foxconn International, Inc.", which
>> doesn't sound much like "Acer"...
 >
> It's already in wireless-testing with similar values.
> 
> Not quite apropos to this patch, someone with the ambit chipset said
> the values didn't match up with his laptop, so we do need to add a
> subsystem_device test I think, but it should have a #define in pci.h.
> In any case there's usually no harm in enabling the wrong gpio pin,
> unless rfkill happens to sit there.

from windows drivers:

%ATHER.DeviceDesc.3067%  = ATHER_DEV_04281468.ndi,    PCI\VEN_168C&DEV_001C&SUBSYS_E008105B

ATHER.DeviceDesc.3067        = "Atheros AR5007EG Wireless Network Adapter"


regards,
-- 
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea, Prestige, ...

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-02-23 21:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-23 21:00 [ath5k-devel] [PATCH] Fix transmit LED on Acer Aspire One Xose Vazquez Perez
  -- strict thread matches above, loose matches on Subject: below --
2009-02-18  3:07 Peter Chubb
2009-02-23 19:37 ` John W. Linville
2009-02-23 19:56   ` [ath5k-devel] " Bob Copeland

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).