Messages in this thread |  | | Date | Wed, 29 Jan 2003 13:21:19 -0500 (EST) | From | Scott Murray <> | Subject | Re: [Pcihpd-discuss] [RFC] Enhance CPCI Hot Swap driver |
| |
On 28 Jan 2003, 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
Slight nitpick, I'm pretty sure you mean PICMG 2.12 here, it's the (somewhat lame IMO :) hotswap software spec, 2.16 is the packet switched backplane stuff.
> 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.
Exactly.
Scott
-- Scott Murray SOMA Networks, Inc. Toronto, Ontario e-mail: scottm@somanetworks.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |