mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "Matthew Garrett" <mjg59@srcf.ucam.org>
Cc: "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: Wed, 2 Jul 2008 16:30:11 +0000	[thread overview]
Message-ID: <dd18b0c30807020930u43405fd5v2e328b6b76b833b0@mail.gmail.com> (raw)
In-Reply-To: <20080702115527.GA3396@srcf.ucam.org>

On Wed, Jul 2, 2008 at 11:55 AM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Wed, Jul 02, 2008 at 02:48:20PM +0300, Eduard - Gabriel Munteanu wrote:
>> On Wed, 2 Jul 2008 11:09:35 +0100
>> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>> > We've made a huge number of workarounds for buggy DSDT
>> > implementations.
>>
>> Of course, I myself used a custom DSDT for my laptop. But I was saying
>> that these workarounds generally do not belong to the kernel realm.
>
> Of course they do. Nothing else is going to fix them up.
>
>> This isn't the regular "Pentium F00F bug" stuff; instead bugs in DSDTs
>> consist of compiling issues, non-standard compliant, plainly bad
>> code, Windows-only stuff, which can all be unique for every model of a
>> laptop for example. While the kernel may be able to get around some of
>> that stuff, the kernel won't have any Asus, Acer etc. specific
>> workarounds.
>
> Windows doesn't have any Asus/Acer/whatever workarounds either. We just
> need to be compatible with the Windows implementation. There's a
> minority of cases where that isn't good enough, but almost every DSDT
> issue can (and should) be handled by Linux if the machine works under
> Windows.
>
> --
> Matthew Garrett | mjg59@srcf.ucam.org
>

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
I can  adjust it, So I can feel at ease knowing that it's correct.
regards;
-- 
Justin P. Mattock

  reply	other threads:[~2008-07-02 16:30 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 [this message]
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
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=dd18b0c30807020930u43405fd5v2e328b6b76b833b0@mail.gmail.com \
    --to=justinmattock@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®