From: Johannes Engel <j-engel@gmx.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Matija Šuklje" <matija.suklje@rutka.net>,
"Alexey Starikovskiy" <aystarik@gmail.com>,
linux-acpi@vger.kernel.org
Subject: Re: Why is it so hard to (get) help on ACPI?
Date: Fri, 18 May 2007 00:16:30 +0200 [thread overview]
Message-ID: <464CD43E.8060409@gmx.de> (raw)
In-Reply-To: <20070517204439.GA23599@srcf.ucam.org>
Matthew Garrett schrieb:
> The kernel's job is to make hardware work. If the hardware works under
> another OS, then it failing to work in Linux is a bug in Linux. So, yes,
> the correct place to fix this sort of thing is in the kernel rather than
> your DSDT.
>
> However, please note that the DSDT is almost entirely irrelevant when it
> comes to things like suspend/resume. Modifying it is hugely unlikely to
> make things work there.
Hm, I do not totally agree. Since in some cases you know that a BIOS
update caused the trouble it seems to be likely in my eyes that these
problems could be fixed by DSDT changes. Please correct me if I'm wrong.
Greetings, Johannes
next prev parent reply other threads:[~2007-05-17 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 18:05 Why is it so hard to (get) help on ACPI? Matija Šuklje
2007-05-17 18:58 ` Alexey Starikovskiy
2007-05-17 19:21 ` Norbert Preining
2007-05-17 19:32 ` Matija Šuklje
[not found] ` <8f8ff01d0705171256m39b6e5t8a69f8095f00594b@mail.gmail.com>
2007-05-17 20:10 ` Matija Šuklje
2007-05-17 20:44 ` Matthew Garrett
2007-05-17 22:16 ` Johannes Engel [this message]
2007-05-17 22:20 ` Matija Šuklje
2007-05-17 22:24 ` Matthew Garrett
2007-05-17 19:52 ` Matija Šuklje
2007-05-17 20:32 ` Len Brown
2007-05-17 20:43 ` Matija Šuklje
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=464CD43E.8060409@gmx.de \
--to=j-engel@gmx.de \
--cc=aystarik@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=matija.suklje@rutka.net \
--cc=mjg59@srcf.ucam.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