Message-ID: <44649A2E.4070803@tmr.com>
Date: Fri, 12 May 2006 10:22:38 -0400
From: Bill Davidsen <davidsen@tmr.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.2) Gecko/20060409 SeaMonkey/1.0.1
MIME-Version: 1.0
To: marekw1977@yahoo.com.au,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: acpi4asus
References: <20060511130743.GG15876@mail.muni.cz> <20060511073211.1da40329.akpm@osdl.org> <200605121116.11930.marekw1977@yahoo.com.au>
In-Reply-To: <200605121116.11930.marekw1977@yahoo.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1467
Lines: 30

Marek W wrote:

> I am far from qualified to comment on this, but from a users point of view, is 
> it possible to not have laptop specific code in the kernel?
> I have had two Linux laptops and with both I had ACPI issues.
> The vendors of both laptops (Toshiba Tecra S1 and now an Asus W3V) don't seem 
> to be following standards. With both I seem to need to patch ACPI to get 
> various functions of the laptop to work.
> I would love to see laptop specific functionality definitions exist outside 
> the kernel.
> 
I don't think that forcing laptop users to have their own code outside 
the kernel is really the best approach for either the developers or the 
users. Most users will not have the expertise or time to develop 
patches, so teaching the kernel to handle special cases is likely to 
benefit more users and avoid reinventing the wheel.

Having to maintain and out-of-mainline kernel tree is a time-consuming 
job, and even if you can do it you may delay upgrades or build a kernel 
without the added features if they are not required for normal operation.
-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/