public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Lynch <rusty@linux.co.intel.com>
To: Stanley Wang <stanley.wang@linux.co.intel.com>
Cc: Scott Murray <scottm@somanetworks.com>, Greg KH <greg@kroah.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	PCI_Hot_Plug_Discuss <pcihpd-discuss@lists.sourceforge.net>
Subject: Re: [Pcihpd-discuss] [RFC] Enhance CPCI Hot Swap driver
Date: 28 Jan 2003 00:40:26 -0800	[thread overview]
Message-ID: <1043743227.10693.10.camel@vmhack> (raw)
In-Reply-To: <Pine.LNX.4.44.0301291538190.10354-100000@manticore.sh.intel.com>

On Tue, 2003-01-28 at 23:50, Stanley Wang wrote:
> Hi, Scott,
> After reading your CPCI Hot Swap support codes, I have a suggestion
> to enhance it:
> How about to make it be full hot swap compliant?
> I mean we could also do some works like "disable_slot" when we receive
> the #ENUM & EXT signal. Hence the user could yank the hot swap board 
> without issuing command on the console.
> How do you think about it?
> 

How does this behavior translate to "full hot swap compliant"?  I assume
you are talking about wording from PICMG 2.16, which in my opinion
describes the full software stack, not just the driver.  Any kind of
full CPCI solution would have all the user space components to
coordinate disabling a slot before the operator physically yanks the
board (and therefore behave as PICMG specifies).  I'm not so sure the
driver knows enough to make a policy decision on what to do when an
operator bypasses the world and just yanks a board out with no warning.

    --rustyl


  reply	other threads:[~2003-01-29 16:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  7:50 [RFC] Enhance CPCI Hot Swap driver Stanley Wang
2003-01-28  8:40 ` Rusty Lynch [this message]
2003-01-29 18:21   ` [Pcihpd-discuss] " Scott Murray
2003-01-30  0:35     ` Stanley Wang
2003-01-29 18:18 ` Scott Murray
2003-01-30  0:44   ` Stanley Wang
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 19:51 [Pcihpd-discuss] " Ed Vance
2003-01-29 22:09 ` Scott Murray

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=1043743227.10693.10.camel@vmhack \
    --to=rusty@linux.co.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=scottm@somanetworks.com \
    --cc=stanley.wang@linux.co.intel.com \
    /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