From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Chris Cheney <ccheney@cheney.cx>
Cc: len.brown@intel.com, tony@atomide.com,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net,
patches@x86-64.org, ak@suse.de, pavel@ucw.cz
Subject: Re: [PATCH] x86_64 VIA chipset IOAPIC fix
Date: Mon, 29 Mar 2004 19:17:50 -0800 [thread overview]
Message-ID: <20040329191750.4bec9da3.rddunlap@osdl.org> (raw)
In-Reply-To: <20040326043447.GD9248@cheney.cx>
On Thu, 25 Mar 2004 22:34:47 -0600 Chris Cheney <ccheney@cheney.cx> wrote:
| On Thu, Mar 25, 2004 at 11:21:51PM -0500, Len Brown wrote:
| > On Thu, 2004-03-25 at 22:35, Tony Lindgren wrote:
| > > * Chris Cheney <ccheney@cheney.cx> [040325 19:06]:
| > > > On Wed, Mar 24, 2004 at 07:34:34PM -0800, Tony Lindgren wrote:
| > > >
| > > > BTW - Does this also solve the problem with needing USB to be compiled
| > > > directly into the kernel in 64bit mode?
| > >
| > > OK, tried it and it does not help there. Also loding ACPI processor and
| > > thermal zone compiled in hangs the machine, but loading them as modules
| > > work.
| >
| > where does it hang when processor and thermal are compiled-in?
|
| You had mentioned before there is a way to decompile SSDT with 3rd party
| (non iasl.exe) asl tools, do you happen to know where to get them? Also
| does the usual dsdt override patch (acpi.sf.net) allow you to override
| the ssdt or does it only work for the dsdt?
There are some non-Intel ACPI (dumping) tools in CVS (acpidump and
pmtools/acpi*) at this SF.net project:
https://sourceforge.net/projects/acpi/
I expect that I need to make those available as tarballs.
And Len has pmtools (and dmidecode) available here:
http://www.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
However, I'm not aware of any of these decompiling the SSDT...
--
~Randy
next prev parent reply other threads:[~2004-03-30 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 3:34 Tony Lindgren
2004-03-26 0:15 ` Len Brown
2004-03-26 0:47 ` Tony Lindgren
2004-03-26 3:04 ` Chris Cheney
2004-03-26 3:11 ` Tony Lindgren
2004-03-26 3:13 ` Len Brown
2004-03-26 3:20 ` Chris Cheney
2004-03-26 3:35 ` Tony Lindgren
2004-03-26 4:21 ` Len Brown
2004-03-26 4:34 ` Chris Cheney
2004-03-26 5:10 ` Tony Lindgren
2004-03-30 3:17 ` Randy.Dunlap [this message]
2004-03-26 5:02 ` Tony Lindgren
2004-04-16 10:53 HurryLin
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=20040329191750.4bec9da3.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=ccheney@cheney.cx \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
/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
Powered by JetHome