From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [ath5k-devel] [PATCH] Fix transmit LED on Acer Aspire One
Date: Mon, 23 Feb 2009 22:00:28 +0100 [thread overview]
Message-ID: <49A30E6C.9010701@gmail.com> (raw)
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, ...
next reply other threads:[~2009-02-23 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 21:00 Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 3:07 [PATCH] Fix transmit LED on Acer Aspire One Peter Chubb
2009-02-23 19:37 ` John W. Linville
2009-02-23 19:56 ` [ath5k-devel] " Bob Copeland
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=49A30E6C.9010701@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.