From: Matthew Garrett <mjg59@srcf.ucam.org>
To: andrej.gelenberg@udo.edu
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
Corentin Chary <corentin.chary@gmail.com>,
linux acpi <linux-acpi@vger.kernel.org>,
acpi4asus-user@lists.sourceforge.net
Subject: Re: eeepc-laptop: bugreport
Date: Sun, 15 Nov 2009 18:27:35 +0000 [thread overview]
Message-ID: <20091115182735.GA3585@srcf.ucam.org> (raw)
In-Reply-To: <cone.1258309336.428593.1656.1000@eeekiste>
On Sun, Nov 15, 2009 at 07:22:16PM +0100, andrej.gelenberg@udo.edu wrote:
> Matthew Garrett writes:
>> Though, thinking about it, you're right - we still need to know whether
>> it was a wifi device so we know whether to update the rfkill status. Do
>> Atheros devices still have their PCI class set to ethernet rather than
>> wireless?
>
> cat /sys/bus/pci/devices/0000\:02\:00.0/class
> 0x028000
Unfortunately it's 0x020000 on some earlier Eees, so that's not going to
work. I'd be almost inclined to just leave eeepc-laptop as is, and write
a new driver for the systems with the new interface.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-11-15 18:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cone.1258203372.445001.1633.1000@eeekiste>
[not found] ` <71cd59b00911140641i1502e95bt81d87db848feaf0@mail.gmail.com>
[not found] ` <cone.1258211472.464906.1633.1000@eeekiste>
2009-11-15 9:39 ` eeepc-laptop: bugreport Corentin Chary
2009-11-15 11:53 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-15 12:37 ` Alan Jenkins
2009-11-15 16:06 ` andrej.gelenberg-KJIyc1CJxjQ
[not found] ` <4B002951.4080704@tuffmail.co.uk>
[not found] ` <cone.1258304218.643429.1671.1000@eeekiste>
2009-11-15 17:07 ` Alan Jenkins
2009-11-15 17:17 ` Corentin Chary
2009-11-15 17:32 ` andrej.gelenberg
2009-11-15 17:43 ` Alan Jenkins
2009-11-15 18:05 ` andrej.gelenberg
2009-11-15 18:31 ` Corentin Chary
2009-11-15 18:56 ` Matthew Garrett
2009-11-15 18:06 ` Matthew Garrett
2009-11-15 18:11 ` andrej.gelenberg
2009-11-15 18:15 ` Matthew Garrett
2009-11-15 18:39 ` andrej.gelenberg
2009-11-15 12:44 ` Alan Jenkins
2009-11-15 15:05 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-15 15:54 ` Alan Jenkins
2009-11-15 16:02 ` Matthew Garrett
2009-11-15 16:11 ` Alan Jenkins
2009-11-15 16:14 ` Matthew Garrett
2009-11-15 18:16 ` Matthew Garrett
2009-11-15 18:22 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-15 18:27 ` Matthew Garrett [this message]
2009-11-15 15:56 ` Matthew Garrett
2009-11-15 15:59 ` Alan Jenkins
2009-11-15 15:52 ` Matthew Garrett
2009-11-15 19:19 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-26 15:03 ` Corentin Chary
2009-11-26 16:45 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-26 16:48 ` Matthew Garrett
2009-11-27 11:21 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-27 11:27 ` Alan Jenkins
2009-11-27 12:27 ` andrej.gelenberg
2009-11-27 17:25 ` Matthew Garrett
2009-11-27 20:26 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-27 20:43 ` Corentin Chary
2009-11-27 20:55 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-27 21:58 ` Matthew Garrett
2009-12-07 21:23 ` Corentin Chary
2009-12-07 21:28 ` Matthew Garrett
2009-12-13 21:16 ` [PATCH] eeepc-laptop: disable pci hotplug code when all notifiers fail to load Corentin Chary
2009-12-16 10:58 ` Corentin Chary
2009-11-27 17:19 ` eeepc-laptop: bugreport Matthew Garrett
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=20091115182735.GA3585@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=andrej.gelenberg@udo.edu \
--cc=corentin.chary@gmail.com \
--cc=linux-acpi@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.