From: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Corentin Chary <corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux acpi <linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
debian-eeepc-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org,
acpi4asus-user
<acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Touchpad led inversed ?
Date: Mon, 01 Mar 2010 12:54:03 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003011251400.4281@localhost.localdomain> (raw)
In-Reply-To: <71cd59b01002210249y5dc3d93aubc79741df7da34f1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
thanks,
Len Brown, Intel Open Source Technology Center
On Sun, 21 Feb 2010, Corentin Chary wrote:
> Hi,
> It seems that touchpad led is inverted on Eee1001HAG
> (http://bugzilla.kernel.org/show_bug.cgi?id=14865).
> If you get a touchpad led on your eeepc , could you test if it is
> working as expected and report the results ?
> Thanks,
>
> Ps: not really related, but if you have to boot with acpi_osi="Linux"
> to be able to use eeepc-laptop,
> please read http://dev.iksaif.net/projects/acpi4asus/wiki/Eeepc-wmi .
BTW.
I'd rather that they use acpi_osi="!Windows 2009" than acpi_osi=Linux
as a workaround -- as the workaround here isn't enabling some special
Linux support (which doesn't actually exist).
The workaround is disabling the new win7 support.
thanks
Len Brown, Intel Open Source Technology Center
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
prev parent reply other threads:[~2010-03-01 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 10:49 Touchpad led inversed ? Corentin Chary
[not found] ` <71cd59b01002210249y5dc3d93aubc79741df7da34f1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-01 17:54 ` Len Brown [this message]
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=alpine.LFD.2.00.1003011251400.4281@localhost.localdomain \
--to=lenb-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=debian-eeepc-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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