From: "Justin Mattock" <justinmattock@gmail.com>
To: "Alexey Starikovskiy" <aystarik@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, 4 Jul 2008 16:23:32 +0000 [thread overview]
Message-ID: <dd18b0c30807040923v37e2d8c3id680d76b9cf494bf@mail.gmail.com> (raw)
In-Reply-To: <486E0A64.5020903@gmail.com>
On Fri, Jul 4, 2008 at 11:32 AM, Alexey Starikovskiy <aystarik@gmail.com> wrote:
> 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.
>
Hello;
So adding acpi_osi=Darwin will work for boot parameter. Also I wanted
to apologize If I pissed you off,
I didn't quite understand what was really happening, and now after
looking into the scenario, I think I need to find out
what is going on with my GPE's, this way you're detector(ec.c) won't
be going off so frequently.
regards;
--
Justin P. Mattock
next prev parent reply other threads:[~2008-07-04 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 6:39 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
2008-07-04 16:23 ` Justin Mattock [this message]
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=dd18b0c30807040923v37e2d8c3id680d76b9cf494bf@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=aystarik@gmail.com \
--cc=eduard.munteanu@linux360.ro \
--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
all inboxes | Powered by JetHome®