public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Tippett <matthew-+XluyfkzffvQT0dZR+AlfA@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: 'Craig Whitmore' <lennon-q3Ck4f9/EBK9koe0gwxAeg@public.gmane.org>,
	Matthew Tippett <matthew-+XluyfkzffvQT0dZR+AlfA@public.gmane.org>,
	chbm-tNiY1ywYjSU@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Custom Override for DSDT?
Date: Fri, 13 Dec 2002 17:47:11 -0500	[thread overview]
Message-ID: <3DFA636F.80407@casero.com> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A597-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>

Getting back to the original question, would it make sense to support a 
way of overriding a dsdt to allow a broken BIOS that the manufacturer 
won't fix be usable?

This still keeps standards based ACPI compliance but with the nice twist 
  that we don't have to rely entirely on the manufacturer for the BIOS 
to work.

Regards,

Matthew

Grover, Andrew wrote:
>>From: Craig Whitmore [mailto:lennon-q3Ck4f9/EBK9koe0gwxAeg@public.gmane.org] 
>>
>>>>distributed in windows drivers.
>>>
>>>Continuing with this thread, would it make sense to be ACPI 
>>
>>compliant
>>
>>>but allow 'custom' dsdts to be passed to the acpi subsystem to allow
>>>users to work around less than perfect implementations from
>>>manufacturers.
>>>
>>
>>Just 1 question. What do the manufacturer's say when you tell 
>>them they have
>>a "broken" dsdt? Do they normally fix it? or give some excuse 
>>in a reason
>>why they won't fix it?
> 
> 
> It varies. BIOS bugs exposed by Linux may be prioritized lower due to
> Linux's market position in laptops. They also may not get attention if they
> are on end-of-lifed machines, or rolled into a BIOS update only when enough
> other bugs are fixed to justify a new BIOS's validation and release. (We may
> *say* to them it is a trivial fix, but the only way to know if it breaks
> Windows is for them to test it!)
> 
> There also isn't always a clear way to report BIOS bugs from end users.
> 
> On the upside, the things we're seeing are almost always obviously wrong and
> easy to fix - it's just getting them to make the trivial change.
> 
> Regards -- Andy
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 




-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

  parent reply	other threads:[~2002-12-13 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13 22:31 [PATCH] Add CONFIG_ACPI_RELAXED_AML option Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A597-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-12-13 22:47   ` Matthew Tippett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-13 22:59 Custom Override for DSDT? Grover, Andrew

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=3DFA636F.80407@casero.com \
    --to=matthew-+xluyfkzffvqt0dzr+alfa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=chbm-tNiY1ywYjSU@public.gmane.org \
    --cc=lennon-q3Ck4f9/EBK9koe0gwxAeg@public.gmane.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