From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Grover,
Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Randy.Dunlap" <rddunlap-3NddpPZAyC0@public.gmane.org>,
mflt1-DTdK3Ks6N5kHTnRCetW4+N0b+6lKrnBL@public.gmane.org,
acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: DSDT in initrd
Date: Mon, 19 May 2003 16:53:32 +0200 [thread overview]
Message-ID: <20030519145332.GJ346@poupinou.org> (raw)
In-Reply-To: <A5974D8E5F98D511BB910002A50A6647054FC40A-MgY+aF+eRfZviC08c4yzC1DQ4js95KgL@public.gmane.org>
On Mon, May 19, 2003 at 07:38:21AM -0700, Brown, Len wrote:
> I agree with Andy that the OSDs should avoid the DSDT distribution and
> support business. It is the OEM's job to ship a working BIOS, and they will
> do so if they want to pass the OSD's certification test suite.
>
> The concept of a DSDT override is a workaround -- fine for bringup,
> development, hackers, enthusiasts, wizards etc. But somebody who pays money
> for a production box that runs Linux will buy one that the OSD certifies and
> supports.
>
> So unless the Linux community wants to slide down the slippery slope of
> running any old broken BIOS -- forever -- we should maintain -- indeed
> sharpen -- our ability to reject bad firmware -- and generously apply that
> ability when the OEM goes before an OSD for certification.
>
Most trouble come with laptops, not servers (almost all servers
that I have tested work without any real troubles for now).
BUT there is indeed a need to provide workarounds for
_laptops_ users.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-19 14:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 14:38 DSDT in initrd Brown, Len
[not found] ` <A5974D8E5F98D511BB910002A50A6647054FC40A-MgY+aF+eRfZviC08c4yzC1DQ4js95KgL@public.gmane.org>
2003-05-19 14:53 ` Ducrot Bruno [this message]
2003-05-19 15:26 ` Michael Frank
2003-05-20 16:56 ` Markus Gaugusch
[not found] ` <Pine.LNX.4.53.0305191725350.9728-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-05-20 18:01 ` Matthew Wilcox
[not found] ` <20030520180149.GJ31518-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-05-20 18:03 ` Markus Gaugusch
2003-05-21 7:23 ` Nathan Gray
2003-05-21 8:07 ` Gunter Ohrner
2003-05-21 8:07 ` Markus Gaugusch
2003-05-21 15:05 ` Richard Black
[not found] ` <3ECB95CB.2020109-VXdhtT5mjnY@public.gmane.org>
2003-05-21 16:52 ` Ducrot Bruno
2003-05-21 18:07 ` Nathan Gray
-- strict thread matches above, loose matches on Subject: below --
2003-05-17 1:17 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847E96EA0-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-05-18 20:07 ` Mark Santcroos
[not found] ` <20030518200724.GB631-ScjxTogt4I4lGuH5DXb43w@public.gmane.org>
2003-05-19 10:10 ` Adachi, Kenichi
2003-05-16 22:50 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A2A7-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-05-16 23:04 ` Randy.Dunlap
2003-05-17 9:30 ` Markus Gaugusch
2003-05-20 15:37 ` Christian Zoz
2003-05-16 1:41 Brown, Len
[not found] ` <A5974D8E5F98D511BB910002A50A6647054FC400-MgY+aF+eRfZviC08c4yzC1DQ4js95KgL@public.gmane.org>
2003-05-16 5:58 ` Markus Gaugusch
2003-05-16 6:24 ` Michael Frank
2003-05-13 4:28 Michael Frank
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=20030519145332.GJ346@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mflt1-DTdK3Ks6N5kHTnRCetW4+N0b+6lKrnBL@public.gmane.org \
--cc=rddunlap-3NddpPZAyC0@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