linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Diehl <lists@mdiehl.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug question: resources
Date: Fri, 08 Feb 2002 01:34:12 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101313194317021@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101290913112826@msgid-missing>

On Thu, 7 Feb 2002, Greg KH wrote:

> On Thu, Feb 07, 2002 at 08:42:46AM -0800, Stephen Williams wrote:
> > 
> > I spend  lot of time during a typical day powering down, changing
> > the board and/or soldering wires, and rebooting. I would *love*
> > to be able to just change a card on a live system.
> 
> Ok, here's the code that I have.  I don't know if this works.  Heck,
> I've never even compiled it :)
> 
> This code was written by Vladimir Kondratiev.

Wow - thanks!

When I saw your hotplug-skeleton I was thinking I should try something
like this for my OB800: it has an built-in scsi-HA which is detected
during pci-busscan only if the proprietary cable is connected (My guess is
the power is simply routed thru some magic in the plug...) Hence one has
to reboot to make use of the scsi if booted without the cable connected.

But all one would need is to rescan the bus later whenever one wants to
connect or disconnect. Note that there is no real hotplug controller there
to create (un)plug notifications. But there are some changing registers
in the northbridge so one could even poll with say 1 sec intervall for
connections. Anyway, there is probably nothing which provides real hot
(un)plugging on the active scsi bus. So I really prefer to do this by
hand whenever I switch scsi cabling.

I just tried this patch and it seems to be almost exactly what I was
looking for. However, I first had to disable the "print IRQ routing" path
because it Oopsed for me (in pcibios_get_irq_routing_table(), fwiw).
No big deal and now its working really fine:

cable connected, insmod pcibus:
  scsi-HA detected+registered, bar's allocated, lspci -vvvxxx looks fine

modprobe ncr53c8xx and friends:
  PIRQ routed, HA detected, scsi-device found

mount /dev/scd0 -> normal operation

reverse unmount, rmmod, disconnect and then insmod pcibus again:
  pci-device removed, lspci and /proc/ioports cleaned

Turns out it's a real useful tool for me. I'm going to improve it a little
bit (probably next weekend...)

Thanks.

Martin


_______________________________________________
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-08  1:34 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
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 [this message]
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-101313194317021@msgid-missing \
    --to=lists@mdiehl.de \
    --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).