mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john moser <bluefoxicy@linux.net>
To: linux-kernel@vger.kernel.org
Subject: ACPI -- Workaround for broken DSDT
Date: Sat, 31 Jan 2004 11:39:45 -0800 (PST)	[thread overview]
Message-ID: <20040131193945.955BF7261@sitemail.everyone.net> (raw)

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/

             reply	other threads:[~2004-01-31 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31 19:39 john moser [this message]
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB5C@hdsmsx402.hd.intel.com>
2004-02-01 19:53 ` Len Brown
2004-02-02  6:04   ` Joseph Pingenot
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-02-04  7:22 Brown, Len

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=20040131193945.955BF7261@sitemail.everyone.net \
    --to=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

all inboxes | Powered by JetHome®