linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Arjan van de Ven <arjan@infradead.org>,
	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
Subject: Re: [PATCH 0/4] Fastboot revisited: Asynchronous function calls
Date: Sun, 04 Jan 2009 13:46:40 -0600	[thread overview]
Message-ID: <49611220.6010400@shaw.ca> (raw)
In-Reply-To: <87fxjyopie.fsf@basil.nowhere.org>

Andi Kleen wrote:
> Linus Torvalds <torvalds@linux-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.

  reply	other threads:[~2009-01-04 19:46 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 17:24 [PATCH 0/4] Fastboot revisited: Asynchronous function calls Arjan van de Ven
2009-01-04 17:28 ` [PATCH 1/4] fastboot: Asynchronous function calls to speed up kernel boot Arjan van de Ven
2009-01-04 18:33   ` Linus Torvalds
2009-01-04 18:40     ` Arjan van de Ven
2009-01-04 18:49     ` Arjan van de Ven
2009-01-04 19:05   ` Andi Kleen
2009-01-04 19:09     ` Arjan van de Ven
2009-01-04 19:49       ` Andi Kleen
2009-01-04 19:52         ` Andrew Morton
2009-01-04 17:29 ` [PATCH 2/4] fastboot: make scsi probes asynchronous Arjan van de Ven
2009-01-04 18:05   ` Matthew Wilcox
2009-01-04 18:13     ` Arjan van de Ven
2009-01-04 18:38       ` Jaswinder Singh Rajput
2009-01-04 18:44         ` Arjan van de Ven
2009-01-04 17:30 ` [PATCH 3/4] fastboot: make the libata port scan asynchronous Arjan van de Ven
2009-01-04 17:31 ` [PATCH 4/4] fastboot: make ACPI bus drivers probe asynchronous Arjan van de Ven
2009-01-05  2:03   ` Zhao Yakui
2009-01-05  1:58     ` Arjan van de Ven
2009-01-05  2:51       ` Zhao Yakui
2009-01-05  2:51         ` Arjan van de Ven
2009-01-05  5:30           ` Zhao Yakui
2009-01-04 18:16 ` [PATCH 0/4] Fastboot revisited: Asynchronous function calls Linus Torvalds
2009-01-04 18:31   ` Arjan van de Ven
2009-01-04 18:54     ` Linus Torvalds
2009-01-04 19:05       ` Arjan van de Ven
2009-01-04 19:11         ` Linus Torvalds
2009-01-04 19:19           ` Arjan van de Ven
2009-01-05 16:21         ` Alan Cox
2009-01-05 21:13           ` Arjan van de Ven
2009-01-05 21:21             ` Linus Torvalds
2009-01-04 19:11       ` Andi Kleen
2009-01-04 19:46         ` Robert Hancock [this message]
2009-01-04 19:27   ` Linus Torvalds
2009-01-04 19:48     ` Arjan van de Ven
2009-01-04 21:44   ` Alan Cox
2009-01-11 13:14   ` Pavel Machek
2009-01-05  6:01 ` Nigel Cunningham
2009-01-05  8:47   ` Frederic Weisbecker
2009-01-05 10:53   ` Arjan van de Ven
2009-01-05 11:18     ` Nigel Cunningham
2009-01-07  2:41     ` Shaohua Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49611220.6010400@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).