RE: RE: ACPI -- Workaround for broken DSDT

["Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>]

On Thu, 2004-02-05 at 00:10, Brown, Len wrote:
> > On Wed, 2004-02-04 at 21:15, Brown, Len wrote: 
> > > The strategy is to improve ACPI on Linux such that all 
> > Linux distros are
> > > able to successfully ship ACPI enabled kernels.
> > > 
> > > When we reach that stage, the OEMs will use these commercial Linux
> > > products when they validate their platforms -- fixing DSDT problems
> > > themselves before the 1st BIOS is released to the public.
> > 
> > realistically, that's 3-5+ years away.  In the meantime, what are
> > existing users to do?  (i.e. those of us who don't like reading 430+
> > pages of the spec)
> 
> Linux users should buy machines from OEMs that support Linux,
> and not buy machines from OEMs that ignore Linux.  There are
> OEMS that validate their platforms with Linux today -- this isn't
> 3-5 years away.

That argument simply doesn't work for laptops (which seems to me to be
the main driving force behind ACPI, but I recognize ACPI is useful for
desktops too).  There are too many reasons to pick one machine over
another, including weight, size, price/performance, screen quality
(size/resolution), keyboard quality/layout/size, touchpad vs nipple,
etc.  In the end, it's a compromise of course, so it'd be nice if there
was one less constraint on my purchasing decision (i.e. ACPI).

	Scott



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn