public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Pingenot <trelane@digitasaru.net>
To: Len Brown <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 00:04:39 -0600	[thread overview]
Message-ID: <20040202060434.GA6038@digitasaru.net> (raw)
In-Reply-To: <1075665236.2392.16.camel@dhcppc4>

>From Len Brown on Sunday, 01 February, 2004:
>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?!

-Joseph

  reply	other threads:[~2004-02-02  1:52 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 ` ACPI -- Workaround for broken DSDT Len Brown
2004-02-02  6:04   ` Joseph Pingenot [this message]
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=20040202060434.GA6038@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox