public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Eric Piel <Eric.Piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
Cc: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATHC] Relaxed syntax for the processor PBLK length
Date: Mon, 31 Jan 2005 15:58:36 +0100	[thread overview]
Message-ID: <20050131145836.GA1145@poupinou.org> (raw)
In-Reply-To: <41FD3E02.8010701-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>

On Sun, Jan 30, 2005 at 09:05:22PM +0100, Eric Piel wrote:
> Hello,
> 
> In the original DSDT of my laptop (Acer TravelMate 614) the processor 
> PBLK length is declared to be 5. The legal and only allowed value is 6. 
> This is an error in the DSDT and actually it is 6. Allowing Linux ACPI 
> to read also processor PBLK length of 5 works and permits the processor 
> to have the C-states correctly detected. In turn it allows the processor 
> to get less hot (so this is eventually useful).
> 
> I've noticed that some other Acer DSDT also have this length 
> mis-indicated. The attached patch adds some logic to the ACPI to allow a 
> processor PBLK length of 5 when the syntax is relaxed.
> 

You should consider to disable C3 in this case IMHO.

Thanks,

-- 
Bruno Ducrot

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


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-01-31 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 20:05 [PATHC] Relaxed syntax for the processor PBLK length Eric Piel
     [not found] ` <41FD3E02.8010701-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
2005-01-30 21:39   ` Johan Vromans
2005-01-30 22:43   ` Richard Dawe
2005-01-31 14:58   ` Bruno Ducrot [this message]
     [not found]     ` <20050131145836.GA1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-01-31 15:11       ` Eric Piel
     [not found]         ` <41FE4ABF.9040100-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
2005-01-31 15:29           ` Bruno Ducrot
     [not found]             ` <20050131152931.GC1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-01-31 15:44               ` Eric Piel
2005-01-31 15:47               ` Herman Sheremetyev
2005-01-31 15:59               ` Dominik Brodowski
     [not found]                 ` <20050131155917.GA4416-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-01-31 16:14                   ` Eric Piel
     [not found]                     ` <41FE595D.5020605-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
2005-01-31 16:26                       ` Dominik Brodowski
     [not found]                         ` <20050131162628.GA4911-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-01-31 16:29                           ` Dominik Brodowski
2005-01-31 16:36                   ` Bruno Ducrot
     [not found]                     ` <20050131163603.GE1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-01-31 18:53                       ` Dominik Brodowski

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=20050131145836.GA1145@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=Eric.Piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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