public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Vernon Mauery <vernux@us.ibm.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>,
	ACPI mailing list <acpi-devel@lists.sourceforge.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	seife@suse.de, rjw@sisk.pl
Subject: Re: [ACPI] Call for help: list of machines with working S3
Date: Thu, 17 Feb 2005 21:13:29 +0100	[thread overview]
Message-ID: <4214FAE9.9090003@gmx.net> (raw)
In-Reply-To: <4214C9D0.1090707@us.ibm.com>

Vernon Mauery schrieb:
> Carl-Daniel Hailfinger wrote:
> 
>>1. A first step towards better DSDTs would be to make the ASL compiler
>>complain about the same things which are complained about by the
>>in-kernel ACPI interpreter. An example would be the following:
>>
>>acpi_processor-0496 [10] acpi_processor_get_inf: Invalid PBLK length [7]
>>
>>The ASL compiler will not complain about it, yet the kernel will
>>refuse to do any processor throttling with a PBLK length of 7.
> 
> 
> This is like getting gcc to complain about run-time bugs in a program.

Oh, gcc does that to a certain extent. For example, it has warnings
like "this comparison is always true" or "value too big for selected
type".


> The compiler of a language (ASL in this case) compiles the language,
> regardless of run-time bugs because it can only detect syntax errors.
> And iasl does that pretty well.  

It is possible to do quite a bit of semantic verification at compile
time, but of course there are limits to everything.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

  reply	other threads:[~2005-02-17 20:14 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 21:11 Call for help: list of machines with working S3 Pavel Machek
2005-02-14 21:36 ` [ACPI] " Carl-Daniel Hailfinger
2005-02-14 23:23 ` Matthew Garrett
2005-02-14 23:47   ` Matthew Garrett
2005-02-15  6:05 ` Alistair John Strachan
2005-02-15 12:12   ` [ACPI] " Lorenzo Colitti
2005-02-15 13:17     ` Alistair John Strachan
2005-02-15 16:07       ` Lorenzo Colitti
2005-02-15 15:41     ` Matthew Garrett
2005-02-15 16:15       ` Lorenzo Colitti
2005-02-15 16:16       ` Lorenzo Colitti
2005-02-15 17:42         ` Alistair John Strachan
2005-02-15 20:43           ` Matthew Garrett
2005-02-15 21:09             ` Lorenzo Colitti
2005-02-16  1:41               ` Alistair John Strachan
2005-02-16  1:54                 ` Pavel Machek
2005-02-16  2:47                   ` Nigel Cunningham
2005-02-16  8:30                     ` Romano Giannetti
2005-02-16 14:25           ` Kjartan Maraas
2005-02-18 20:49             ` Alistair John Strachan
2005-02-20  9:21               ` Luca Capello
2005-02-21 14:25               ` Kjartan Maraas
2005-02-22 14:33               ` Karol Kozimor
2005-02-15 16:05   ` Stefan Seyfried
2005-02-15 12:55 ` [ACPI] " Norbert Preining
2005-02-15 13:17   ` Karol Kozimor
2005-02-15 16:09   ` Carl-Daniel Hailfinger
2005-02-15 17:08     ` Norbert Preining
2005-02-15 18:57       ` Carl-Daniel Hailfinger
2005-02-15 20:21         ` Matthew Garrett
2005-02-15 22:40           ` Carl-Daniel Hailfinger
2005-02-16  9:51         ` Norbert Preining
2005-02-15 19:37       ` Stefan Dösinger
2005-02-17 11:06         ` Norbert Preining
2005-02-17 19:08         ` Norbert Preining
2005-02-17 20:58           ` Stefan Dösinger
2005-02-18 10:46             ` Norbert Preining
2005-02-18 13:38               ` Norbert Preining
2005-02-18 18:04                 ` Stefan Dösinger
2005-02-15 19:47       ` Pavel Machek
2005-02-17 19:09         ` Norbert Preining
2005-02-16  9:34       ` Romano Giannetti
2005-02-16 14:54         ` Carl-Daniel Hailfinger
2005-02-16 16:10           ` Romano Giannetti
2005-02-22 22:08       ` Karol Kozimor
2005-02-24 12:37         ` Norbert Preining
2005-02-24 21:36           ` Karol Kozimor
2005-02-25 17:50           ` Proinnsias Breathnach
2005-02-27 16:57           ` Pavel Machek
2005-02-27 18:04             ` Stefan Seyfried
2005-02-15 16:31 ` Vernon Mauery
2005-02-15 21:28 ` Henrik Brix Andersen
2005-02-16  5:54 ` Stefan Schweizer
2005-02-16  8:48   ` Stefan Dösinger
2005-02-16 15:06     ` Carl-Daniel Hailfinger
2005-02-16 17:43       ` Stefan Schweizer
2005-02-16 19:26       ` Stefan Dösinger
2005-02-17  6:16 ` Len Brown
2005-02-17 10:15   ` Vojtech Pavlik
2005-02-17 23:12     ` Len Brown
2005-02-17 11:00   ` Matthew Garrett
2005-02-17 16:18     ` Carl-Daniel Hailfinger
2005-02-17 16:44       ` Vernon Mauery
2005-02-17 20:13         ` Carl-Daniel Hailfinger [this message]
2005-02-17 19:54       ` Pavel Machek
2005-02-17 20:34         ` Carl-Daniel Hailfinger
2005-02-17 20:42           ` Pavel Machek
2005-02-17 11:02   ` Pavel Machek
2005-02-17 23:19 ` Luca Capello
2005-02-23 19:30 ` Nish Aravamudan
2005-03-02 10:24 ` Stefan Seyfried
2005-03-02 10:57   ` Stefan Seyfried
2005-03-03 16:51 ` Stefan Seyfried
2005-03-03 17:49 ` Avuton Olrich
2005-03-14  6:19 ` Jan De Luyck
2005-03-14  8:00   ` Pavel Machek
2005-03-14 14:39     ` Jan De Luyck
2005-03-15  8:10     ` [ACPI] " Li Shaohua
2005-03-15 11:34       ` Nigel Cunningham
2005-03-15 12:04         ` Pavel Machek

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=4214FAE9.9090003@gmx.net \
    --to=c-d.hailfinger.devel.2005@gmx.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    --cc=seife@suse.de \
    --cc=vernux@us.ibm.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