public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: John Belmonte <john-wanGne27zNesTnJN9+BGXg@public.gmane.org>
Cc: Emma Jane Hogbin
	<emmajane-MHIYrZpDPrNWk0Htik3J/w@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI HOWTO
Date: 20 May 2004 23:11:16 -0400	[thread overview]
Message-ID: <1085109076.12349.535.camel@dhcppc4> (raw)
In-Reply-To: <40A95511.3070109-wanGne27zNesTnJN9+BGXg@public.gmane.org>

On Mon, 2004-05-17 at 20:13, John Belmonte wrote:

> It may be that when you started with ACPI, there was a large gap between 
> ACPI development work and kernel releases.  From my understanding, these 
> days, the 2.4 and 2.6 kernels use the same ACPI system, and improvements 
>   by the ACPI team show up rather quickly in the kernel, especially the 
> 2.6 series.  I'm sure others on this list are more qualified to talk 
> about this than I am.

Emma,
It would be fair to call ACPI on Linux an "emerging technology", and
bugs are being fixed at a rapid rate.  For this reason I do agree that
step 1 should be to run the most recent kernel that is practical.

Note that we support the latest ACPI code on 2.4 and 2.6; both the
latest released kernel and the kernel under development. eg.

2.6.7 (develpment)
2.6.6 (released)

2.4.27 (development)
2.4.26 (released)

The ACPI patch gets absorbed into the development trees about every 5 to
10 days.  We try to make these updates as frequent as practical so that
the ACPI patch never grows too big.

As the released trees are no longer accepting patches, the ACPI patch
for the grows monatonically, but then gets deleted when the development
tree gets released and a new development tree is created.  This is to
encourage users to run (and test;-) the latest kernels.

Also, before any ACPI bugs are reported, it is best to verify that the
machine is running the latest BIOS from the vendor.
The better vendors are actually quite good about releasing BIOS fixes
for systems in the field.

For a number or reasons, I am not a big advocate of running patched
DSDTs -- my view in this area is that is a debugging tool, and that we
should either fix Linux to handle the BIOS, or the BIOS should be
corrected by the vendor.

thanks,
-Len




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click

  parent reply	other threads:[~2004-05-21  3:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 19:01 ACPI HOWTO Emma Jane Hogbin
     [not found] ` <20040517190137.GD5547-Kz9ENIl45+A@public.gmane.org>
2004-05-18  0:13   ` John Belmonte
     [not found]     ` <40A95511.3070109-wanGne27zNesTnJN9+BGXg@public.gmane.org>
2004-05-18 12:37       ` Emma Jane Hogbin
2004-05-21  3:11       ` Len Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-18 14:50 Rockefeller, Harry
     [not found] ` <B774920D825C2D4880A3C1B0D6EF94189A5063-YbQoUGCEyAW+LrQOllSzDQC/G2K4zDHf@public.gmane.org>
2004-05-18 15:36   ` Bruno Ducrot
2004-05-21  4:39   ` Len Brown
     [not found]     ` <1085114355.12354.586.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-21  7:58       ` Michael Frank
2004-05-19 14:47 Rockefeller, Harry
     [not found] ` <B774920D825C2D4880A3C1B0D6EF94189E7BE3-YbQoUGCEyAW+LrQOllSzDQC/G2K4zDHf@public.gmane.org>
2004-05-24 14:35   ` Bruno Ducrot
2004-05-26  2:41 Yu, Luming

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=1085109076.12349.535.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=emmajane-MHIYrZpDPrNWk0Htik3J/w@public.gmane.org \
    --cc=john-wanGne27zNesTnJN9+BGXg@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