From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Q] cPCI hotplugging
Date: Tue, 16 Jan 2001 22:51:45 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97968994106283@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97958292121643@msgid-missing>
Dan, is your "Hotplug PCI" related to some of the original
PCI driver API updates ("new style") done way early in the
2.3 timeframe? That seemed never to have had followon to
complete it (user mode tools like /sbin/hotplug, cardctl).
I had been asking, but nobody knew of any ... :-)
I'd also be interested in any thoughts you might have about
when users should deal with a GUI, vs have such issues
be fully automated. For example, I'd expect laptop users
would never want a GUI unless that PCI (Cardbus) device
has never been seen before ... while at least some server
admins might feel "safer" with lots of manual controls.
- Dave
----- Original Message -----
From: Zink, Dan <Dan.Zink@COMPAQ.com>
To: 'Matthew Dharm' <mdharm-usb@one-eyed-alien.net>; Miles Lane <miles@megapathdsl.net>
Cc: 'Scott Laird' <laird@internap.com>; David Brownell <david-b@pacbell.net>; Eric
<ebrower@usa.net>; <linux-hotplug-devel@lists.sourceforge.net>
Sent: Tuesday, January 16, 2001 2:30 PM
Subject: RE: [Q] cPCI hotplugging
> To answer Miles' question, I am aware of the /sbin/hotplug stuff that was
> added but hadn't given it a whirl yet. It ought to tie in nicely. We
> did most of our development prior to the appearance of /sbin/hotplug so
> we have another usermode notification method for synchronization with
> the PCI Hot Plug GUI we've written. In addition, our GUI uses the kudzu
> database to find drivers and allow the user to load them. That should
> be unnecessary if /sbin/hotplug does the right thing.
>
> As for the rest of the "infrastructure" work we've done, some of it is
> support that could be applied to any PCI hot plug driver. Some could
> be applied to the kernel's PCI configuration routines.
>
> Dan
>
> -----Original Message-----
> From: Matthew Dharm [mailto:mdharm-usb@one-eyed-alien.net]
> Sent: Tuesday, January 16, 2001 3:19 PM
> To: Miles Lane
> Cc: Zink, Dan; 'Scott Laird'; David Brownell; Eric;
> linux-hotplug-devel@lists.sourceforge.net
> Subject: Re: [Q] cPCI hotplugging
>
>
> Umm... I just want to make sure we're all on the same page, because Miles'
> e-mail sounds like he _might_ be confused.
>
> cPCI != Compaq PCI
>
> cPCI = Compact PCI, which is a hot-swappable bus archetecture (and cabinet
> design, and card form factors, and...)
>
> cPCI has no controller. It's not a controller spec. It's a bus and
> physical spec. Tho the Compaq PCI controller may give you many of the same
> benefits as a real cPCI system.
>
> cPCI is really just PCI, at 33/66MHz and 32/64 bits wide. It supports
> insertion notification, and removal request (open the latches, allow the
> software to shutdown and turn off the LED, then remove the board).
>
> Taking the 2 second look at the web page, it looks like they're working on
> both infrastructure for PCI Hot Plug, as well as a driver for the Compaq
> controller for this thing. I don't know much about this controler, but I'm
> certainly interested in the infrastructure parts.
>
> Matt
>
> On Tue, Jan 16, 2001 at 10:54:45AM -0800, Miles Lane wrote:
> > Zink, Dan wrote:
> >
> > > Funny you should ask... We have developed a driver for the Compaq PCI
> > > Hot Plug Controller that we will be releasing in the next week or two.
> > >
> > > Our SourceForge site is at:
> > > http://opensource.compaq.com/sourceforge/project/?group_id\x13
> > >
> > > I'll be posting a notice to this list when we get the source up there.
> >
> > So, Dan,
> >
> > In Scott's initial note on the topic, he mentioned that cPCI is a
> > hotplugging bus. You may or may not have heard about the recent
> > hotplug developments in the 2.4.0 series kernel. If you already
> > know about it, do you have any idea how your new driver will
> > mesh, if at all, with the new hotplug infrastructure?
> >
> > Miles
>
> --
> Matthew Dharm Home:
> mdharm-usb@one-eyed-alien.net
> Maintainer, Linux USB Mass Storage Driver
>
> What, are you one of those Microsoft-bashing Linux freaks?
> -- Customer to Greg
> User Friendly, 2/10/1999
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-01-16 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 10:21 [Q] cPCI hotplugging Eric
2001-01-15 21:21 ` Matthew Dharm
2001-01-15 22:44 ` David Brownell
2001-01-15 22:48 ` Scott Laird
2001-01-16 16:47 ` Zink, Dan
2001-01-16 18:54 ` Miles Lane
2001-01-16 21:19 ` Matthew Dharm
2001-01-16 22:30 ` Zink, Dan
2001-01-16 22:51 ` David Brownell [this message]
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-97968994106283@msgid-missing \
--to=david-b@pacbell.net \
--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).