From: Ed Vance <EdV@macrolink.com>
To: "'Rusty Lynch'" <rusty@linux.co.intel.com>,
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: Wed, 29 Jan 2003 11:51:43 -0800 [thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D1A33D71@EXCHANGE> (raw)
On Tue, January 28, 2003 at 12:40 AM, Rusty Lynch wrote:
>
> 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.
How is this functionally different from ejecting a PCMCIA card in use? Is
the driver obligated to do more than prevent a system crash and present
errors to user level until the last close?
Ed
next reply other threads:[~2003-01-29 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 19:51 Ed Vance [this message]
2003-01-29 22:09 ` Scott Murray
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 7:50 Stanley Wang
2003-01-28 8:40 ` [Pcihpd-discuss] " Rusty Lynch
2003-01-29 18:21 ` Scott Murray
2003-01-30 0:35 ` Stanley Wang
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=11E89240C407D311958800A0C9ACF7D1A33D71@EXCHANGE \
--to=edv@macrolink.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rusty@linux.co.intel.com \
--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
all inboxes | Powered by JetHome®