linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug question: resources
Date: Thu, 07 Feb 2002 08:43:29 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101307160722854@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101290913112826@msgid-missing>

On Tue, Feb 05, 2002 at 05:17:02PM -0800, Stephen Williams wrote:
> 
> I have in front of me an Adex Electronics PCI bus extender with a
> disconnect switch. I would like to use this to plug PCI boards into
> a Linux system, configure the device, and turn it on. The idea is to
> test hardware, not to provide an end-user tool.
> 
> So the question is valid: Is there a way under Linux to grab a bunch
> of PCI resources after the system is already running? Detach them
> again?

Yes there is.  And I even have patch around here that will do exactly
what you are looking for.  Someone sent it to me a while ago in relation
to the pci hotplug drivers.  I think they had that same extender.

If I remember, the code would basically walk the pci bus when you told
it to (loaded the driver), and create new pci devices for any new
devices found.  Then the module would fail to load, freeing up the
kernel memory again.  Nice idea, but odd implementation :)

The interupt values it would get from the BIOS I think
(IO_APIC_something...), which the IBM PCI Hotplug driver also relies on.
But if you look at the current Compaq pci hotplug driver, it doesn't use
this, and it seems to just recycle interrupts.  Actually that portion of
the Compaq driver seems a bit odd to me now...

I don't think it did anything about removals.

Let me know if you're interested in the code and I'll dig it up.  Enough
interest and I'll port it to the existing pci hotplug core and put it in
the main kernel (but I'd really like to be able to test the driver
myself before I do that...)

thanks,

greg k-h

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2002-02-07  8:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 11:37 PCI hotplug question: resources Dirk Stieler
2002-02-05 13:55 ` Matti Aarnio
2002-02-06  1:17 ` Stephen Williams
2002-02-06 10:20 ` Matti Aarnio
2002-02-06 17:55 ` Chris Brand
2002-02-07  8:43 ` Greg KH [this message]
2002-02-07 16:42 ` Stephen Williams
2002-02-07 23:51 ` Greg KH
2002-02-08  1:06 ` Donald Becker
2002-02-08  1:34 ` Martin Diehl
2002-02-08 15:44 ` John Carlson

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=marc-linux-hotplug-101307160722854@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.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).