From: Len Brown <len.brown@intel.com>
To: bluefoxicy@linux.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI -- Workaround for broken DSDT
Date: 01 Feb 2004 14:53:56 -0500 [thread overview]
Message-ID: <1075665236.2392.16.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0020AEB5C@hdsmsx402.hd.intel.com>
this is probably best addressed to acpi-devel@lists.sourceforge.net
where people over-ride their BIOS ACPI DSDT all the time.
However, there is a reason that it isn't push-button, and that is
because we don't want to encourage people to do it. We'd rather fix
Linux where Linux is broken, or get the OEMs to fix their BIOS where the
BIOS is broken.
thanks,
-Len
On Sat, 2004-01-31 at 14:39, john moser wrote:
> Please CC me all replies.
>
>
> http://abaababa.ouvaton.org/presario/
>
> Please note that a recompiled and fixed DSDT table exists for the
> Compaq Presario
> 2100 series. I would like to be able to simply point my kernel at
> this file at
> compile time from a configuration menu, and compile it in to the
> kernel. I can
> probably find the DSDT load code myself, but compiling external data
> into a
> program and accessing it is something foreign to me (IDE's like
> Borland C++ Builder
> did it for you and so I never was able to learn how with GCC).
>
> This may be useful in the future for broken ACPI. Could someone
> please make a
> quick patch to allow the path of a DSDT table to be defined so that it
> may be
> compiled into the kernel and override the ACPI DSDT table in the
> BIOS? I'll
> peek around, but ACPI and this sort of programming isn't my strong
> point.
>
> If anyone is familiar with this area and would be willing to write up
> a patch,
> please CC me so I don't spend days/weeks trying to figure out how the
> heck to
> do this ;)
>
>
>
> _____________________________________________________________
> Linux.Net -->Open Source to everyone
> Powered by Linare Corporation
> http://www.linare.com/
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next parent reply other threads:[~2004-02-01 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB5C@hdsmsx402.hd.intel.com>
2004-02-01 19:53 ` Len Brown [this message]
2004-02-02 6:04 ` ACPI -- Workaround for broken DSDT Joseph Pingenot
2004-02-04 7:22 Brown, Len
-- strict thread matches above, loose matches on Subject: below --
2004-02-02 4:33 Brown, Len
2004-02-02 14:38 ` Matt Domsch
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
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=1075665236.2392.16.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=bluefoxicy@linux.net \
--cc=linux-kernel@vger.kernel.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