public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Slezak <jan.slezak-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI DSDT language
Date: Wed, 29 Jan 2003 14:39:57 +0100	[thread overview]
Message-ID: <3E37D9AD.44F24BDF@centrum.cz> (raw)
In-Reply-To: 20030129121715.GP32050@poup.poupinou.org

Ducrot Bruno píše:
> 
> On Wed, Jan 29, 2003 at 10:33:52AM +0100, Ing. Jan Slezak wrote:
> > Ducrot Bruno pí?e:
> > >
> > > On Tue, Jan 28, 2003 at 11:47:03AM +0100, Jan Slezak wrote:
> > > > 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)
> > > >     }
> > > >
> > >
> > > Why don't make something like that instead:
> > >
> > >     Method (PNPG, 1, NotSerialized)
> > >     {
> > >       .
> > >       .
> > >         Name (PGET, Buffer (8) {})
> > >         Store (something, Index(PGET, 2))
> > >         Return (PGET)
> > >     }
> > >
> > > (unless 'something' is not 8-bits long, though)
> > >
> > > --
> > > Ducrot Bruno
> > >
> > > --  Which is worse:  ignorance or apathy?
> > > --  Don't know.  Don't care.
> >
> >
> > Sure, it is possible and I modified my DSDT in a similar way, but I want
> > to know if the original DSDT is correct (by specs, let's say
> > theoreticaly). I don't want to beat my notebok manufacturer and get the
> > answer "it is by spec" then.
> 
> Ah, yep, I have not read carrefully your first email.
> 
> By spec (2.0b, somewhere in 5.5.3 to 5.5.4):
> any namespace creation in a control method can only be acceded in the control method.
> 
> Here, the buffer PNPG will be created only for _internal_ use of PNPG.
> 
> When the SX33(PGET, 2) occur, the control method SX33 can not have direct
> access of PGET, but of a _local copy_ of the buffer (which is referenced by Arg0)
> but still only for _internal_ use of SX33.
> 
> Please note also that 'Return (PGET)' at end of PNPG control method will actually create
> a _copy_ for the caller of PNPG (the initial PGET will be destroyed at end of
> the method).
> 
> Cheers,
> 
> --
> Ducrot Bruno
> 
> --  Which is worse:  ignorance or apathy?
> --  Don't know.  Don't care.

Great! So I'm going to send my DSDT fix to Dell and ask them to apply it
to official BIOS.

Thanks,
Jan


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  parent reply	other threads:[~2003-01-29 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 10:47 ACPI DSDT language Jan Slezak
     [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       ` Jan Slezak [this message]
  -- 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=3E37D9AD.44F24BDF@centrum.cz \
    --to=jan.slezak-arb0bu7prfprbkcemvbida@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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