public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	mochel@osdl.org
Subject: Re: PnP Model
Date: 04 Feb 2003 10:45:08 -0600	[thread overview]
Message-ID: <1044377110.1776.16.camel@mulgrave> (raw)
In-Reply-To: <1044290479.21009.7.camel@irongate.swansea.linux.org.uk>

On Mon, 2003-02-03 at 10:41, Alan Cox wrote:
> On Mon, 2003-02-03 at 15:31, James Bottomley wrote:
> > The last issue is probably that we'd like the ISA probes to be run after
> > all the rest of the busses so that all resources in use in the system
> 
> They need to run very early on in some ways. We don't want to assign a
> PnP device over something we didnt know exists. We can scan the other
> busses first safely but we can't activate devices or do anything else
> until the ISA unsafe probes run. Those also have some very careful
> ordering especially in networking. NE2000 must run early, other probes
> can make some cards move around so must also be ordered


It strikes me that we can make use of the bus matching logic for this. 
For ISA, since we have no concept of a card id, we could instead match
on when the binding should occur (i.e. ISA_BIND_EARLY and
ISA_BIND_LATE).  Thus each driver picks its binding type and we run bind
early before all other busses and bind late after them (probably by
simulating a hotplug event that says hey I suddenly found a bunch of ISA
cards of type ISA_BIND_LATE).  It's a bit of an abuse of what bus
matching is supposed to do, but it should work for the purpose

James




  reply	other threads:[~2003-02-04 16:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 15:31 PnP Model James Bottomley
2003-02-03 16:41 ` Alan Cox
2003-02-04 16:45   ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-04 19:53 PnP model Grover, Andrew
2003-02-04 22:56 ` Alan Cox
2003-02-06 18:49 ` Adam Belay
2003-02-04 19:25 Grover, Andrew
2003-02-04 19:40 ` John Bradford
2003-02-02 20:36 [PATCH][RFC] Resource Management Improvements (1/4) Adam Belay
2003-02-03 13:55 ` PnP model Jaroslav Kysela
2003-02-03 15:45   ` Alan Cox
2003-02-03 20:43   ` Adam Belay
2003-02-04  9:46     ` Russell King
2003-02-04 10:18       ` Jaroslav Kysela
2003-02-04 10:49         ` Russell King
2003-02-05 21:34           ` Adam Belay
2003-02-07  8:56             ` Jaroslav Kysela
2003-02-04 10:40     ` Jaroslav Kysela

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=1044377110.1776.16.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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