public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: "Grover,
	Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Stefan Behlert <behlert-l3A5Bk7waGM@public.gmane.org>,
	ACPI mailing list
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	trenn-l3A5Bk7waGM@public.gmane.org, "Brown,
	Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: ACPI C4 support
Date: Mon, 1 Mar 2004 20:39:17 +0100	[thread overview]
Message-ID: <20040301193917.GA2869@poupinou.org> (raw)
In-Reply-To: <20040301192738.GA9459-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

On Mon, Mar 01, 2004 at 08:27:38PM +0100, Pavel Machek wrote:
> Hi!
> 
> > > [mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of 
> > > Stefan Behlert
> > > > No.  pblk_length is 0 or 6.  Not 5 nor 7 ;)
> > > 
> > > Sorry, I don't understand: We've a Laptop with a DSDT with
> > >   Processor (\_PR.CPU0, 0x01, 0x00001010, 0x07)
> > > in it.
> > > Comment from the responsible BIOS-team:
> > > "Our processor block object is 7 bytes in length because we 
> > > also support
> > >  C4 (P_LVL4) which is at <P_BLK>+6.  Therefore, the 
> > > size/length must be
> > >  reported as 7 and not 6."
> > > 
> > > Is the '7' the BIOS-developer mentioned the same '7' as 
> > > mentioned by you?
> > 
> > This is wrong.
> > 
> > There is confusion here because what older systems do on C3 is different
> > from what more recent systems do on C3, at the electrical level. I know
> > at least internally the improved C3-like state was called "C4" but to
> > the OS it just looks just like C3, and the value for C4 should go in
> > P_LVL3. P_BLK length should remain 6.
> > 
> > The only way to get more than C1, C2, and C3 is via the _CST object.
> > 
> > Please tell the BIOS developer this. I have an old BIOS developers guide
> > version that agrees with them but I just asked the experts internally
> > and they said no.
> 
> If there is old BIOS guide telling them to use length of 7, could we
> make Linux accept that? Its likely a lot of developers have read
> that...
> 
> Allowing length of 7 is one line change; if we do it, such notebooks
> will be able to use C1..C3, but not C4. That does not seem too bad...
> 

The problem is that, from strict acpi point of view, it will be too easy
to allow '7', and _CST support is much better.  Don't ask me why, I'm not
an expert.  So perhaps it may be possible to add the (bahh, beurk)
length of 7 if there exist a bad written bios developper guide released
apparently by Intel, at least as a non pedantic acpi option?

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  parent reply	other threads:[~2004-03-01 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 19:03 ACPI C4 support Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84702C932FD-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-03-01 19:16   ` Pavel Machek
2004-03-01 19:27   ` Pavel Machek
     [not found]     ` <20040301192738.GA9459-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-03-01 19:39       ` Bruno Ducrot [this message]
     [not found]         ` <20040301193917.GA2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-02 22:22           ` Stefan Seyfried
  -- strict thread matches above, loose matches on Subject: below --
2004-03-01 21:26 Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A8470255F035-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-03-02  9:52   ` Bruno Ducrot
2004-02-28 16:10 Pavel Machek
     [not found] ` <20040228161011.GA10448-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-03-01 15:28   ` Bruno Ducrot
     [not found]     ` <20040301152810.GT2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-01 18:09       ` Stefan Behlert
     [not found]         ` <20040301180958.GI2624-l3A5Bk7waGM@public.gmane.org>
2004-03-01 19:48           ` Bruno Ducrot
     [not found]             ` <20040301194825.GB2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-02 10:17               ` Stefan Behlert

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=20040301193917.GA2869@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=behlert-l3A5Bk7waGM@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=pavel-AlSwsSmVLrQ@public.gmane.org \
    --cc=trenn-l3A5Bk7waGM@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