From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Yves-Alexis Perez <corsac@debian.org>
Cc: Manoj Iyer <manoj.iyer@canonical.com>,
ibm-acpi-devel@lists.sourceforge.net,
Matthew Garrett <mjg@redhat.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [ibm-acpi-devel] [PATCH] thinkpad-acpi: recognize Lenovo as version string in newer V-series BIOS
Date: Sat, 10 Mar 2012 13:06:09 -0300 [thread overview]
Message-ID: <20120310160609.GA6254@khazad-dum.debian.net> (raw)
In-Reply-To: <1331387907.2833.33.camel@scapa>
On Sat, 10 Mar 2012, Yves-Alexis Perez wrote:
> On sam., 2012-03-10 at 01:28 -0300, Henrique de Moraes Holschuh wrote:
> > So far so good, but what driver functionality works well in these new
> > lenovo boxes?
>
> V-series are Ideapad, so I'm not really sure this need to be added to
> thinkpad-acpi.
Yeah, it is not a thinkpad, not even in name.
However, it just might have enough of the thinkpad ACPI API to work,
thus my question. What good does thinkpad-acpi do in a Lenovo Ideapad
V-series? If it does something useful, we can support it (but it
likely needs more than just this patch to be safe).
If it doesn't do anything useful, consider this as an absolute NACK
(i.e. I will outright revert it if it lands). Loading thinkpad-acpi on
a notebook that doesn't benefit from it is harmful in the long term, as
thinkpad-acpi can suddenly start calling weird stuff in ACPI on that box
and do something bad. There is a real reason why we restrict IBM-era
stuff to IBM thinkpads, etc.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2012-03-10 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 23:32 Manoj Iyer
2012-03-09 23:32 ` Manoj Iyer
2012-03-10 4:28 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2012-03-10 13:58 ` Yves-Alexis Perez
2012-03-10 16:06 ` Henrique de Moraes Holschuh [this message]
2012-03-12 21:34 ` Manoj Iyer
2012-03-12 23:02 ` Henrique de Moraes Holschuh
2012-03-12 23:57 ` Manoj Iyer
2012-03-13 15:53 ` Manoj Iyer
2012-03-13 20:07 ` Henrique de Moraes Holschuh
2012-03-13 20:19 ` Manoj Iyer
2012-03-20 16:03 ` 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=20120310160609.GA6254@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=corsac@debian.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®