From: Joseph Pingenot <trelane@digitasaru.net>
To: "Brown, Len" <len.brown@intel.com>
Cc: bluefoxicy@linux.net, linux-kernel@vger.kernel.org
Subject: Re: ACPI -- Workaround for broken DSDT
Date: Mon, 2 Feb 2004 19:03:01 -0600 [thread overview]
Message-ID: <20040203010258.GC6376@digitasaru.net> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC8A85@hdsmsx402.hd.intel.com>
>From Brown, Len on Sunday, 01 February, 2004:
>The vendor should supply a correct DSDT with their BIOS.
>In the case of Dell, you might inquire here: http://linux.dell.com/
>For non-vendor supplied solutions, you might also follow the DSDT link
>here: http://acpi.sourceforge.net/
Hmm. Do vendors generally release these? I know Dell's very shaky on
the Linux support front, at least for desktop/laptop.
Also, how do non-vendor supplied ones get made? Seems like something
you need NDA'ed docs for.
-Joseph
>> >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.
>> How does one get a hold of a fixed DSDT? I've seen postings about
>> how to apply them, but how do they get released? I'd *love* for
>> Dell to release a fix for my Inspiron 8600 (haven't found a fixed
>> DSDT), or to just get a hold of one.
>> *sigh* When will the vendors support Linux?!
next prev parent reply other threads:[~2004-02-03 1:05 UTC|newest]
Thread overview: 11+ 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
2004-02-17 11:47 ` Pavel Machek
2004-02-18 3:32 ` Joseph Pingenot
2004-02-03 1:03 ` Joseph Pingenot [this message]
2004-02-03 1:32 ` Stian Jordet
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 7:22 Brown, Len
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=20040203010258.GC6376@digitasaru.net \
--to=trelane@digitasaru.net \
--cc=bluefoxicy@linux.net \
--cc=len.brown@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.