From: Alexey Starikovskiy <aystarik@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Theodore Tso <tytso@MIT.EDU>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: Kernel Version specific vendor override possibilities needed - Revert and provide osi=linux or provide a replacement
Date: Thu, 21 Feb 2008 18:07:26 +0300 [thread overview]
Message-ID: <47BD93AE.7000609@gmail.com> (raw)
In-Reply-To: <20080221145527.GA8768@srcf.ucam.org>
Matthew Garrett wrote:
> On Thu, Feb 21, 2008 at 05:48:33PM +0300, Alexey Starikovskiy wrote:
>
>
>> How about WMI?
>> Do you think that there will be some point in the future,
>> when we could claim that our WMI implementation is the
>> same as Windows + HW manufacturer private driver?
>>
>
> When vendors require custom drivers, we're going to end up requiring a
> custom driver. That's true regardless of how the functionality is
> exposed. The solution there is to encourage vendors not to require
> custom drivers, not to get them to expose the same functionality in two
> different ways.
>
>
It will always be two ways -- Windows way with WMI and other OSes way
without it.
The choice is there to place this non-Windows custom driver -- in C or
in AML.
This is their choice, right? If they choose to not create custom
driver or have some concerns about complexity of its implementation in
C rather than in AML, they should be allowed to choose AML.
next prev parent reply other threads:[~2008-02-21 15:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 1:44 Kernel Version specific vendor override possibilities needed - Revert and provide osi=linux or provide a replacement Thomas Renninger
2008-02-20 10:31 ` Tomas Carnecky
2008-02-20 13:14 ` Henrique de Moraes Holschuh
2008-02-20 15:31 ` Thomas Renninger
2008-02-20 17:32 ` Matthew Garrett
2008-02-20 18:21 ` Thomas Renninger
2008-02-20 18:46 ` Matthew Garrett
2008-02-20 18:23 ` Henrique de Moraes Holschuh
2008-02-20 18:49 ` Matthew Garrett
2008-02-21 3:13 ` Henrique de Moraes Holschuh
2008-02-21 5:31 ` Sergio Monteiro Basto
2008-02-21 15:55 ` Henrique de Moraes Holschuh
2008-02-21 9:15 ` Matthew Garrett
2008-02-21 13:51 ` Theodore Tso
2008-02-21 14:30 ` Matthew Garrett
2008-02-21 14:48 ` Alexey Starikovskiy
2008-02-21 14:55 ` Matthew Garrett
2008-02-21 15:07 ` Alexey Starikovskiy [this message]
2008-02-21 15:50 ` Henrique de Moraes Holschuh
2008-02-26 16:26 ` Thomas Renninger
2008-02-26 16:31 ` Matthew Garrett
2008-02-22 14:07 ` Thomas Renninger
2008-02-22 18:10 ` Matthew Garrett
2008-02-26 16:26 ` Thomas Renninger
2008-02-21 8:41 ` Len Brown
2008-02-21 15:41 ` Thomas Renninger
2008-02-21 15:58 ` Matthew Garrett
2008-02-21 17:15 ` Theodore Tso
2008-02-22 23:36 ` Len Brown
2008-02-23 0:06 ` Len Brown
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=47BD93AE.7000609@gmail.com \
--to=aystarik@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=trenn@suse.de \
--cc=tytso@MIT.EDU \
/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.