From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Hancock Subject: Re: [PATCH 0/4] Fastboot revisited: Asynchronous function calls Date: Sun, 04 Jan 2009 13:46:40 -0600 Message-ID: <49611220.6010400@shaw.ca> References: <20090104092430.7ffd2c41@infradead.org> <20090104103104.6fdda9f2@infradead.org> <87fxjyopie.fsf@basil.nowhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87fxjyopie.fsf@basil.nowhere.org> Sender: linux-scsi-owner@vger.kernel.org To: Andi Kleen Cc: Linus Torvalds , Arjan van de Ven , linux-kernel@vger.kernel.org, mingo@elte.hu, fweisbec@gmail.com, linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org, linux-acpi@vger.kernel.org, akpm@linux-foundation.org List-Id: linux-ide@vger.kernel.org Andi Kleen wrote: > Linus Torvalds writes: > >> That said, I also wonder if we really even need to autoprobe the >> interrupts on any modern hardware. Rather than trying to speed up irq >> probing, maybe we could figure it out some other way.. > > You'll hate that suggestion, but i8250_pnp should already discover > it fine via ACPI on modern systems. ia64 has done it this way > forever. > > It probably won't work on really old system, but one could always > use DMI year to distingush (not pretty, but works usually) Well, we should be able to tell where we got the port information from, if it's somewhere expected to be reliable like PCI configuration, ISAPnP or PnPACPI, or whether we're just probing magical ports and hoping to find something. The only cases on x86 hardware where I would think probing would have to happen would be where the machine was too old to do either ISA Plug & Play or PnPACPI, or if you added in a non-PnP ISA modem or serial card.