From: Jan Slezak <jan.slezak-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
To: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: ACPI DSDT language
Date: Tue, 28 Jan 2003 11:47:03 +0100 [thread overview]
Message-ID: <200301281147.03925.jan.slezak@centrum.cz> (raw)
Hi,
I would like to know what way should be buffers handled when are passed as arguments to
ACPI methods. I don't have a time to read the ACPI specs so I hope someone knows.
I find out by tracing my /_TZ/TMP method that they are passed by value so following
construction (part of my original DSDT slightly modified) doesn't work (PNPG called)
because PGET is not modified:
Method (SX33, 2, NotSerialized)
{
If (LLess (Arg1, SizeOf (Arg0)))
{
CreateByteField (Arg0, Arg1, SX20)
Store (Something, SX20)
}
}
Method (PNPG, 1, NotSerialized)
{
.
.
Name (PGET, Buffer (8) {})
SX33 (PGET, 2)
Return (PGET)
}
I need to know it to decide wheter it is my BIOS or the linux ACPI implementation what is
buggy and to decide whether to send my DSDT patch to my notebook manufacturer (DELL).
Thanks,
Jan
P.S.: If it is right behaviour and the BIOS is buggy I don't understand why the ACPI
(actually ACPI battery info) is working under WinXP, where there is no DSDT override and
no buggy feature workaround in the biosinfo.inf for my DELL.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next reply other threads:[~2003-01-28 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 10:47 Jan Slezak [this message]
[not found] ` <20030128133617.GM32050@poup.poupinou.org>
[not found] ` <3E37A000.DB4190B@centrum.cz>
[not found] ` <20030129121715.GP32050@poup.poupinou.org>
2003-01-29 13:39 ` ACPI DSDT language Jan Slezak
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 16:24 Moore, Robert
2003-01-30 9:49 ` Jan Slezak
2003-01-30 16:32 Moore, Robert
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=200301281147.03925.jan.slezak@centrum.cz \
--to=jan.slezak-arb0bu7prfprbkcemvbida@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@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