From: Nathan Gray <n8gray-7GExONQZ6ZKVc3sceRu5cw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RE: ACPI source releases updated (20030509)
Date: Tue, 13 May 2003 11:38:40 -0700 [thread overview]
Message-ID: <b9re0e$u0h$1@main.gmane.org> (raw)
In-Reply-To: 20030513085421.GB1338@enigma.daemon.sh
Sebastian Henschel wrote:
> on the other hand, this patch should not be necessary anyway. users
> should not patch part of their "bios" by themselves to get their system
> to work better. but this is how the situation currently looks like, as
> long as the vendors provide buggy DSDTs. i would consider the patch to
> be temporary, marked as soon-to-be-deleted. :)
I think I would like to see this patch included even if vendors supplied
perfectly good DSDTs. It's kind of interesting to hack on these things and
it could allow the enterprising hacker to improve the functionality of her
machine. For example, on my machine Dell has put almost every device on
interrupt 11 without giving me any way to change them. I'm not an expert,
but from what I've seen in the ACPI spec I think it might be possible for
me to override this decision by hacking the DSDT.
In short, open source is all about hacking and so is this patch. :-)
I think the only criticism I have of this patch is that (IMVeryHO) it
doesn't strike me as suitable for long-term inclusion in the kernel. I
imagine it would be better to allow the user to specify dsdt=/boot/dsdt.img
in the same way he specifies initrd=/boot/initrd.img so that these two
things can be kept cleanly separated.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next prev parent reply other threads:[~2003-05-13 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 22:18 ACPI source releases updated (20030509) Grover, Andrew
2003-05-13 0:48 ` Nathan Gray
2003-05-13 8:54 ` Sebastian Henschel
[not found] ` <20030513085421.GB1338-adzhR0EPeY/7X6WiDY61Ug@public.gmane.org>
2003-05-13 9:38 ` Markus Gaugusch
[not found] ` <Pine.LNX.4.53.0305131133540.10441-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-05-13 13:34 ` Christian Zoz
2003-05-13 11:26 ` Gunter Ohrner
2003-05-13 18:38 ` Nathan Gray [this message]
2003-05-13 18:55 ` Richard Black
2003-05-14 11:12 ` Ducrot Bruno
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='b9re0e$u0h$1@main.gmane.org' \
--to=n8gray-7gexonqz6zkvc3sceru5cw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox