All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Valerio Felici <valerio-3NZjWNnCfY8@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: Error in dsdt from asus a3527nuh
Date: Thu, 11 Nov 2004 22:45:21 +0800	[thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F84041AC058@pdsmsx403> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3304 bytes --]

I hesitate to ask you , but would you tell me what kind of kernel error you could have, before going to fixing dsdt.

Thanks
Luming 

>-----Original Message-----
>From: acpi-devel-admin@lists.sourceforge.net 
>[mailto:acpi-devel-admin@lists.sourceforge.net] On Behalf Of 
>Valerio Felici
>Sent: 2004年11月11日 22:35
>To: acpi-devel@lists.sourceforge.net
>Subject: Re: [ACPI] Error in dsdt from asus a3527nuh
>
>Alle 22:08, mercoledì 10 novembre 2004, Moore, Robert ha scritto:
>> Just create one, Method (_INI) under _SB_
>>
>Ok, I've just made that and you can see the attached diff file.
>I don't know if my changes are correct.
>Now I don't got errors but various warning as you can see here:
>-------
>iasl -tc dsdt.dsl
>
>Intel ACPI Component Architecture
>ASL Optimizing Compiler / AML Disassembler version 20040527 
>[May 27 2004]
>Copyright (C) 2000 - 2004 Intel Corporation
>Supports ACPI Specification Revision 2.0c
>
>dsdt.dsl  1592:                 Scope (\_SB.PCI0)
>Warning  2031 -           Internal compiler error ^  (Not 
>using optimized 
>name-  did not find node)
>
>dsdt.dsl  2053:                                 Store (ACPS (), \ACPF)
>Warning  2030 -  Called method may not always return a value ^
>
>dsdt.dsl  2054:                                 Store (DCPS 
>(0x00), \DCPF)
>Warning  2030 -  Called method may not always return a value ^
>
>dsdt.dsl  2266:                     Method (ACPS, 0, Serialized)
>Warning  2019 -                                   ^ Not all 
>control paths 
>return a value (ACPS)
>
>dsdt.dsl  2350:                     Method (DCPS, 1, Serialized)
>Warning  2019 -                                   ^ Not all 
>control paths 
>return a value (DCPS)
>
>dsdt.dsl  3105:                 Scope (\_SB.PCI0)
>Warning  2031 -           Internal compiler error ^  (Not 
>using optimized
>name -  did not find node)
>
>dsdt.dsl  3133:                         If (ACPS ())
>Warning  2030 -                                   ^ Called 
>method may not
>always  return a value
>
>dsdt.dsl  3167:                 Scope (\_SB.PCI0)
>Warning  2031 -           Internal compiler error ^  (Not 
>using optimized
>name - did not find node)
>
>dsdt.dsl  3484:                         If (LNot (DCPS (0x00)))
>Warning  2030 -                                         ^ Called method
>may not always return a value
>
>dsdt.dsl  4552:                 Scope (\_SB.PCI0)
>Warning  2031 -           Internal compiler error ^  (Not 
>using optimized
>name -  did not find node)
>
>ASL Input:  dsdt.dsl - 7943 lines, 271919 bytes, 3643 keywords
>AML Output: DSDT.aml - 27867 bytes 873 named objects 2770 
>executable opcodes
>
>Compilation complete. 0 Errors, 10 Warnings, 0 Remarks, 809 
>Optimizations
>-------
>Well, what can I do now?
>Is that dsdt good to test? or I'm still in errors.
>Many thank as always
>-- 
>A presto
>-Valerio-
>
N\x18¬HS^µéšŠX¬²š'²ŠÞu¼’ɶ¬x\x04„.)îÄLi­ë,\x11Ø­Š‰Ý£	塧g£\aè¬TD\x10¸§»\x15¨®WQy§^®À¡¢'\x1e\x03\x06«uh§êߢ¶Þ²×Zµ¦Ú±ê'.)îÆ^[m§ÿÚvÊ,vw(›ö‰

             reply	other threads:[~2004-11-11 14:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 14:45 Yu, Luming [this message]
2004-11-11 14:58 ` Error in dsdt from asus a3527nuh Valerio Felici
  -- strict thread matches above, loose matches on Subject: below --
2004-11-11 15:07 Yu, Luming
2004-11-11 16:58 ` Valerio Felici
     [not found] <37F890616C995246BE76B3E6B2DBE05502982B70@orsmsx403.amr.corp.intel.com>
     [not found] ` <37F890616C995246BE76B3E6B2DBE05502982B70-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-11 14:35   ` Valerio Felici
2004-11-09 20:54 Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE0550294974F-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org >
2004-11-10 17:05   ` valerio-3NZjWNnCfY8
2004-11-09 20:31 Valerio Felici
     [not found] ` <200411092131.27258.valerio-3NZjWNnCfY8@public.gmane.org>
2004-11-09 20:49   ` Nate Lawson

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=3ACA40606221794F80A5670F0AF15F84041AC058@pdsmsx403 \
    --to=luming.yu-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=valerio-3NZjWNnCfY8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.