All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Len Brown <lenb@kernel.org>,
	Azael Avalos <coproscefalo@gmail.com>,
	Thomas Renninger <trenn@suse.de>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Lin, Ming M" <ming.m.lin@intel.com>
Subject: Re: [PATCH v2 4/4] toshiba_acpi: Add blacklist for models with hotkey problems
Date: Thu, 5 Jan 2012 14:58:31 -0600	[thread overview]
Message-ID: <20120105205831.GH25386@ubuntu-macmini> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E3256C799D@ORSMSX101.amr.corp.intel.com>

On Thu, Jan 05, 2012 at 08:46:43PM +0000, Moore, Robert wrote:
> > My only guess is that Windows is more permissive about this sort of
> > thing than ACPICA is, but by my reading of the spec throwing a fatal
> > error is what's supposed to happen.
> 
> If it is true that Windows will execute this code without error, then ACPICA should be changed to match the Windows behavior. ACPICA is now a "Windows compatible" implementation of ACPI, but that of course means we are attempting to be compatible with a black box ACPI implementation. On the other hand, it may be the case that Windows never executes this code, so the error is not seen on Windows.
> 
> We would like to investigate this further. Please send or point me to the acpidump for this machine.

I posted the ACPI tables at the following link. Let me know if there's
anything I can do to help.

http://people.canonical.com/~sforshee/toshiba-acpi/nb505-acpi-tables.txt

Thanks,
Seth


      reply	other threads:[~2012-01-05 20:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 19:02 [PATCH v2 0/4] toshiba_acpi: Expanded hotkey support Seth Forshee
2012-01-03 19:02 ` [PATCH v2 1/4] ACPI: EC: Add ec_get_handle() Seth Forshee
2012-01-05 18:22   ` Matthew Garrett
     [not found]   ` <CAPbh3ruqMQ8UFSehm7vX5i8YWzRFwF5=TX_f4n4dVkvmQa9Njw@mail.gmail.com>
2012-01-05 19:34     ` Seth Forshee
2012-01-07 20:55       ` Konrad Rzeszutek Wilk
2012-01-07 21:26         ` Matthew Garrett
2012-01-03 19:02 ` [PATCH v2 2/4] toshiba_acpi: Support alternate hotkey interfaces Seth Forshee
2012-01-05 18:25   ` Matthew Garrett
2012-01-05 19:43     ` Seth Forshee
2012-01-05 19:47       ` Matthew Garrett
2012-01-03 19:02 ` [PATCH v2 3/4] toshiba_acpi: Support additional hotkey scancodes Seth Forshee
2012-01-03 19:02 ` [PATCH v2 4/4] toshiba_acpi: Add blacklist for models with hotkey problems Seth Forshee
2012-01-05 18:26   ` Matthew Garrett
2012-01-05 19:32     ` Seth Forshee
2012-01-05 19:34       ` Matthew Garrett
2012-01-05 20:04         ` Seth Forshee
2012-01-05 20:09           ` Matthew Garrett
2012-01-05 20:24             ` Seth Forshee
2012-01-05 20:46       ` Moore, Robert
2012-01-05 20:58         ` Seth Forshee [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=20120105205831.GH25386@ubuntu-macmini \
    --to=seth.forshee@canonical.com \
    --cc=coproscefalo@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=robert.moore@intel.com \
    --cc=trenn@suse.de \
    /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.