public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
Cc: "Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>,
	"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RE: ACPI -- Workaround for broken DSDT
Date: Thu, 12 Feb 2004 11:19:57 +0100	[thread overview]
Message-ID: <20040212101957.GS13262@poupinou.org> (raw)
In-Reply-To: <20040209122256.K74314-Y6VGUYTwhu0@public.gmane.org>

On Mon, Feb 09, 2004 at 12:29:45PM -0800, Nate Lawson wrote:
> On Wed, 4 Feb 2004, Scott T. Smith wrote:
> > On Wed, 2004-02-04 at 21:15, Brown, Len wrote:
> > > Windows doesn't have to do anything.  By being first to ship ACPI, that
> > > implementation provided the defacto ACPI compliance test to which all
> > > BIOS' are tested -- even if that implementation is not ACPI spec
> > > compliant.  No, only under dire circumstances will we emulate Windows
> > > bugs in Linux.
> >
> > So basically we shouldn't use ACPI then, and instead use APM?
> >
> > If Linux ACPI could emulate the bugs that Windows has, then ACPI would
> > work on Linux on most platforms right away.  That would make Linux more
> > accessible to people.  Linux already has a bunch of hacks to support
> > broken hardware which presumably Windows can work around; this seems to
> > be just another one of those.
> 
> We're doing something slightly different with ACPI on FreeBSD.  We add
> hacks^Wworkarounds for buggy DSDT whenever possible but they are under a
> kernel option, #ifndef ACPICA_PEDANTIC.  The default is for this option to
> give maximum compatibility with the stock DSDT, at the expense of spec
> correctness.  However, by adding that option and compiling a kernel, OEMs
> could test against ACPI-CA as a reference implementation while ordinary
> users get maximum compatibility.
> 
> I think the ACPI-CA developers should take a similar tact.  Len, who is on
> the Linux side, could suggest distribution maintainers use the option that
> gives maximum Windows compatibility when shipping a distro.  Bob, who is

I strongly discourage that a Linux distribution maintainer will take a kind of
ownership for qualifiyng that say system is compatible with their
distro.  For my 'real' work, we have to work with some distribution that
is somehow 'qualified' for say software, or say hardware driver, even
though that do not make sense.  For example, if you want to install, and
qualify, Oracle under Linux, you have *no choice* for the distribution
to be used.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  parent reply	other threads:[~2004-02-12 10:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05  5:15 RE: ACPI -- Workaround for broken DSDT Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8AB6-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-05  6:55   ` Scott T. Smith
     [not found]     ` <1075964148.5017.7.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-05 10:00       ` Bruno Ducrot
2004-02-09 20:29       ` Nate Lawson
     [not found]         ` <20040209122256.K74314-Y6VGUYTwhu0@public.gmane.org>
2004-02-09 21:23           ` Len Brown
2004-02-11 16:37           ` ACPI_STRICT_COMPLIANCE (was RE: RE: ACPI -- Workaround for broken DSDT) Len Brown
     [not found]             ` <1076517428.12955.32.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-11 17:51               ` Nate Lawson
2004-02-12 10:19           ` Bruno Ducrot [this message]
2004-02-05  7:29   ` RE: ACPI -- Workaround for broken DSDT Andi Kleen
     [not found]     ` <20040205082926.660974d2.ak-l3A5Bk7waGM@public.gmane.org>
2004-02-05 12:09       ` Bas Mevissen
2004-02-05 11:34   ` Bas Mevissen
  -- strict thread matches above, loose matches on Subject: below --
2004-02-11  6:31 Yu, Luming
2004-02-05 14:33 Cagle, John (ISS-Houston)
     [not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD1066111ED-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2004-02-05 15:19   ` Andi Kleen
     [not found]     ` <20040205161923.37eebc64.ak-l3A5Bk7waGM@public.gmane.org>
2004-02-05 16:07       ` Bas Mevissen
     [not found]         ` <40226A58.5080004-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
2004-02-05 16:24           ` Andi Kleen
     [not found]             ` <20040205172405.01777986.ak-l3A5Bk7waGM@public.gmane.org>
2004-02-05 17:15               ` Bas Mevissen
2004-02-05 15:55   ` Bas Mevissen
2004-02-06 19:33   ` Bruno Ducrot
2004-02-05  8:10 Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8AB9-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-05  8:58   ` Luca Capello
     [not found]     ` <402205B0.3000607-wlebWZzHoyE@public.gmane.org>
2004-02-05 22:43       ` Karol Kozimor
2004-02-05 15:44   ` Scott T. Smith
     [not found]     ` <1075995857.5758.43.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-05 16:13       ` Bas Mevissen
2004-02-04  7:22 Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8A9F-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-04  7:49   ` Arjen Verweij
2004-02-05  2:18   ` Scott T. Smith

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=20040212101957.GS13262@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=nate-Y6VGUYTwhu0@public.gmane.org \
    --cc=scott-j3vAvQ9dNB9ByuSxxbvQtw@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