From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
Ben Greear <greearb@candelatech.com>,
David Woodhouse <dwmw2@infradead.org>,
Christian Lamparter <chunkeey@googlemail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Hacking PCI-ids to allow Atheros NIC into Lenovo laptop.
Date: Wed, 21 Mar 2012 11:15:13 +0000 [thread overview]
Message-ID: <20120321111513.GA26854@srcf.ucam.org> (raw)
In-Reply-To: <CAJ-Vmok+_suTznXcAJ4tdGo3npFvtW+PiqQMQqqH3JN70aX3Qg@mail.gmail.com>
On Tue, Mar 20, 2012 at 10:01:05PM -0700, Adrian Chadd wrote:
> On 12 March 2012 18:11, Luis R. Rodriguez <mcgrof@frijolero.org> wrote:
>
> >> Exposing it as either an smbios table or in ACPI somewhere would be the
> >> two most typical methods for doing this. It's easy to spec an ACPI table
> >> for it if you think there'd be any vendor interest.
> >
> > Better than what we have today, no alternative proposal.
>
> Is there any current "vendor space" in ACPI that we can write to and
> leverage as a kind of example test case?
Not really. In theory the ACPI namespace is only usable if you've pushed
something through the ACPI process - in practice, grabbing a table name
first and asking questions later tends to work fine.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-03-21 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 21:52 Hacking PCI-ids to allow Atheros NIC into Lenovo laptop Ben Greear
2012-03-12 22:13 ` Florian Fainelli
2012-03-12 22:16 ` Julian Calaby
2012-03-12 22:32 ` Christian Lamparter
2012-03-12 22:36 ` Ben Greear
2012-03-13 0:53 ` Luis R. Rodriguez
2012-03-13 0:57 ` Matthew Garrett
2012-03-13 1:11 ` Luis R. Rodriguez
2012-03-21 5:01 ` Adrian Chadd
2012-03-21 11:15 ` Matthew Garrett [this message]
2012-03-13 0:58 ` Ben Greear
2012-03-13 3:13 ` Julian Calaby
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=20120321111513.GA26854@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=adrian@freebsd.org \
--cc=chunkeey@googlemail.com \
--cc=dwmw2@infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.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 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).