public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sérgio Monteiro Basto" <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
To: Ow Mun Heng <ow.mun.heng-Sjgp3cTcYWE@public.gmane.org>
Cc: acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: latest ACPI CA Patch (20040311) - Where??
Date: Sun, 14 Mar 2004 18:01:27 +0000	[thread overview]
Message-ID: <1079287286.7470.20.camel@darkstar> (raw)
In-Reply-To: <1079143284.4097.10.camel-4/PLUo9XfK8@public.gmane.org>

On Sat, 2004-03-13 at 02:03, Sérgio Monteiro Basto wrote:
> Well, you have to wait for patch be integrated in kernel.
> But you can begin teste new ACPICA sub system and see if can read
> correctly your DSDT or if not, you can override the DSDT write in your
> computer BIOS(?).
> in http://developer.intel.com/technology/iapc/acpi/downloads.htm
> basically in Unix ACPI CA - Unix Build Environment
> and you have to wait that Intel updates his page :)
> you have to do:
> cd compiler 
> make
> to get iasl tool
and you could try 
#!/bin/sh
cat /proc/acpi/dsdt > acpi_dsdt.dat
./iasl  -d acpi_dsdt.dat
./iasl -on -tc acpi_dsdt.dsl
-- 
Sérgio M. B.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click

      parent reply	other threads:[~2004-03-14 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12  3:32 latest ACPI CA Patch (20040311) - Where?? Ow Mun Heng
     [not found] ` <C386328088ED7F4E9F81AFBABDDF60DA04A92629-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
2004-03-13  2:03   ` Sérgio Monteiro Basto
     [not found]     ` <1079143284.4097.10.camel-4/PLUo9XfK8@public.gmane.org>
2004-03-13  8:37       ` Len Brown
2004-03-14 18:01       ` Sérgio Monteiro Basto [this message]

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=1079287286.7470.20.camel@darkstar \
    --to=sergiomb-hho3weeoaswvhhzd4jos4w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ow.mun.heng-Sjgp3cTcYWE@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