public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: dsdt buggy acpi
Date: Fri, 04 Jul 2008 15:32:52 +0400	[thread overview]
Message-ID: <486E0A64.5020903@gmail.com> (raw)
In-Reply-To: <dd18b0c30807021037g3faffa6kd1ef26f888f36d11@mail.gmail.com>

Justin Mattock wrote:
> On Wed, Jul 2, 2008 at 4:35 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>   
>> On Wed, Jul 02, 2008 at 04:30:11PM +0000, Justin Mattock wrote:
>>
>>     
>>> Hello; what info is supplied with EFI i.g. I'm using a macbook pro.
>>> After looking at:
>>> http://acpi.sourceforge.net/dsdt/view.php I was unable to locate
>>> anything with apple, or at least
>>> couldn't find the manufacture number.
>>> If somebody has already done this, I was wondering if it would be O.K.
>>> if I can attached my dsdt.dsl with the errors,
>>> and my explanation of what I changed, just so If I did something
>>> completely wrong
>>>       
>> iasl will complain about code that the Linux interpreter will happily
>> accept. If the only reason you've made changes is that iasl complains,
>> then it's unlikely that there's any functional difference as a result.
>> Otherwise, work out which changes fix which Linux bugs and file a bug
>> at bugzilla.kernel.org against acpi.
>>
>> --
>> Matthew Garrett | mjg59@srcf.ucam.org
>>
>>     
>
> Hello; I modified dsdt because iasl was complaining, As a result like
> what you said
> "then it's unlikely that there's any functional difference as a
> result" is probably
> what I'm seeing. As for a bug report I already have one filed. As to
> why I'm messing with
> the dsdt, just trying to isolate the problem with the bug I have
> already filed., or at least
> get a better idea of what is happening. Anyways thanks for the info.
> regards;
>
>   

For difference, you should look for "Darwin", this is how MacOS X 
identifies itself to hardware.


Regards,
Alex.

  reply	other threads:[~2008-07-04 11:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  6:39 dsdt buggy acpi Justin Mattock
2008-07-01 14:19 ` Rafael J. Wysocki
2008-07-01 16:18   ` Justin Mattock
2008-07-02  5:25     ` Eduard - Gabriel Munteanu
2008-07-02  6:16       ` Justin Mattock
2008-07-02 10:09       ` Matthew Garrett
2008-07-02 11:48         ` Eduard - Gabriel Munteanu
2008-07-02 11:55           ` Matthew Garrett
2008-07-02 16:30             ` Justin Mattock
2008-07-02 16:35               ` Matthew Garrett
2008-07-02 17:37                 ` Justin Mattock
2008-07-04 11:32                   ` Alexey Starikovskiy [this message]
2008-07-04 16:23                     ` Justin Mattock
2008-07-04 21:45                       ` Justin Mattock

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=486E0A64.5020903@gmail.com \
    --to=aystarik@gmail.com \
    --cc=eduard.munteanu@linux360.ro \
    --cc=justinmattock@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    /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