From: Matt Domsch <Matt_Domsch@dell.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: trelane@digitasaru.net, bluefoxicy@linux.net,
linux-kernel@vger.kernel.org
Subject: Re: ACPI -- Workaround for broken DSDT
Date: Mon, 2 Feb 2004 08:38:36 -0600 [thread overview]
Message-ID: <20040202083836.A20843@lists.us.dell.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC8A85@hdsmsx402.hd.intel.com>; from len.brown@intel.com on Sun, Feb 01, 2004 at 11:33:44PM -0500
On Sun, Feb 01, 2004 at 11:33:44PM -0500, Brown, Len wrote:
> For non-vendor supplied solutions, you might also follow the DSDT link
> here: http://acpi.sourceforge.net/
Len, this is a really good idea making this available. May I suggest
you also have people provide patches between the original and their
modified versions, so it's easy for everyone to see what was changed?
Thanks,
Matt (who's not looking forward to pulling 20 systems from the
hardware library and flashing BIOSses to pull the original DSDT to
compare with what users suggest need to be fixed for each one before
he can file bug reports with the BIOS writers...)
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-02-02 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 4:33 ACPI -- Workaround for broken DSDT Brown, Len
2004-02-02 14:38 ` Matt Domsch [this message]
2004-02-17 11:47 ` Pavel Machek
2004-02-18 3:32 ` Joseph Pingenot
2004-02-03 1:03 ` Joseph Pingenot
2004-02-03 1:32 ` Stian Jordet
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 7:22 Brown, Len
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB5C@hdsmsx402.hd.intel.com>
2004-02-01 19:53 ` Len Brown
2004-02-02 6:04 ` Joseph Pingenot
2004-01-31 19:39 john moser
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=20040202083836.A20843@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=bluefoxicy@linux.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trelane@digitasaru.net \
/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