From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ducrot Bruno Subject: Re: eisa_set_level_irq(acpi_fadt.sci_int) Date: Fri, 17 Oct 2003 17:41:07 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20031017154107.GI8668@poupinou.org> References: <1066254483.2535.51.camel@dhcppc4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1066254483.2535.51.camel-D2Zvc0uNKG8@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Len Brown Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-acpi List-Id: linux-acpi@vger.kernel.org On Wed, Oct 15, 2003 at 05:48:04PM -0400, Len Brown wrote: > What does eisa_set_level_irq() do for us? > > As its presence breaks the !CONFIG_PCI build, I deleted it and found > that ACPI in PIC mode seems to work just fine without it (at least on 2 > of 2 systems tested so far) > This ensure SCI interrupt is correctly initialized for (poorly) written BIOS. Without it, this break one of my laptop, and certainly others as well. -- Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com