[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49611220.6010400@shaw.ca>
Date: Sun, 04 Jan 2009 13:46:40 -0600
From: Robert Hancock <hancockr@...w.ca>
To: Andi Kleen <andi@...stfloor.org>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Arjan van de Ven <arjan@...radead.org>,
linux-kernel@...r.kernel.org, mingo@...e.hu, fweisbec@...il.com,
linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org,
linux-acpi@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH 0/4] Fastboot revisited: Asynchronous function calls
Andi Kleen wrote:
> Linus Torvalds <torvalds@...ux-foundation.org> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists