From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karol Kozimor Subject: Re: asus_acpi still broken on Samsung P30/P35 Date: Thu, 22 Dec 2005 11:53:45 +0100 Message-ID: <20051222105344.GA32356@hell.org.pl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Return-path: Content-Disposition: inline In-Reply-To: Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Brown, Len" Cc: Linus Torvalds , Hanno B??ck , Andrew Morton , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Christian Aichinger List-Id: linux-acpi@vger.kernel.org Thus wrote Brown, Len: > Karol, > Do you have an update of your asus driver in the pipeline > that addresses this? I still believe the only _right_ *workaround* is http://bugme.osdl.org/attachment.cgi?id=6006&action=view I'll take a shot at rediffing it against recent kernels in a couple of hours (unless someone beats me to it). acpi=strict will work until a suitable patch is merged. Note: it's still a workaround, to properly fix this we need to make ACPI interpreter behave predictably, as written in http://bugme.osdl.org/show_bug.cgi?id=5067#c6 -- I believe I still haven't heard from Robert Moore on the feasibility of such a solution. Please also see http://bugme.osdl.org/show_bug.cgi?id=5067 and http://bugzilla.kernel.org/show_bug.cgi?id=5092 for more info. Best regards, -- Karol 'sziwan' Kozimor sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click