[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: Wakeup from a PCI device
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re[2]: Wakeup from a PCI device
- From: Bruce Young <Bruce_Young@ccm.jf.intel.com>
- Date: Fri, 16 Aug 96 08:29:00 PDT
- Cc: pci-sig@znyx.com
- Resent-Date: Fri, 16 Aug 96 08:29:00 PDT
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"E8dk63.0.QI2.i1B5o"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Text item:
I have talked about this with the Hot Plug group a little bit but they are still
looking at how it might be useful. I will defer to them on exactly what
mechanisms they are putting in place and how this pin would be used.
-Bruce Young
---------------
Bruce:
I'll chime in here on this thread. What relationship or involvement
will the wake-up pin have with the hot-swap (live insertion) PCI
efforts underway in the SIG? It seems that the wake-up pin could
serve the purpose of notifying an OS that a new board has been
inserted into the system for hot swap boards.
Regards,
Jim Medeiros
Ziatech Corporation
On Wed, 14 Aug 1996 15:45:52 -0600, you wrote:
>-> I am in favor of adding a wake-up pin. It seems reasonable that
a portable
>-> PC would be expected to wake-up with a modem ring even if the PCI bus was
>-> powered down for power management reasons.
>->
>-> Thanks,
>-> Frank P. Helms 8/14/96
>-> frank.helms@amd.com
>
>I second the emotion.
>
>I would think desktops and servers might use it also, so there is no
>reason to restrict the wakeup pin to laptops.
>
>Bruce Young's message suggested that only comm devices (modems, NICs)
>would use this. I'm not sure one should limit one's thinking. For example,
>an external data collection device might collect a sample only every 15
>minutes. A data collection box running on batteries or solar power could
>benefit also.
>
>--
>
> -- C^2
>
> ___ __ /___ ___
> | / /_ _ \ |
> | / / // / \ |
> | \ / //_/ / |
> |___\_ /____/___|
> /
> H E W L E T T
> P A C K A R D
>
>Charles Curley is not an employee of Hewlett Packard.
>
>This message does not necessarily represent the opinion(s) of HP.
>
>
Text item: External Message Header
The following mail header is for administrative use
and may be ignored unless there are problems.
***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.
To: Mailing List Recipients <pci-sig-request@znyx.com>
Resent-Sender: pci-sig-request@znyx.com
Precedence: list
X-Loop: pci-sig@znyx.com
X-Mailing-List: <pci-sig@znyx.com> archive/latest/3488
Resent-Message-Id: <"d5aoS.0.1J1.DU05o"@dart>
X-Mailer: Forte Agent .99e/32.227
In-Reply-To: <9608142145.AA01853@dwarf.fc.hp.com>
References: <9608142145.AA01853@dwarf.fc.hp.com>
Message-Id: <32140398.2019269@mail.slonet.org>
Date: Fri, 16 Aug 1996 05:24:02 GMT
Subject: Re: Wakeup from a PCI device
Cc: Mailing List Recipients <pci-sig-request@znyx.com>, pci-sig@znyx.com
From: jmedeiro@slonet.org (Jim Medeiros)
Resent-Date: Fri, 16 Aug 1996 05:24:02 GMT
Received: by znyx.com (5.65/1.35)
id AA05356; Thu, 15 Aug 96 22:32:11 -0700
Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.12/SMI-4.1)
id WAA14963; Thu, 15 Aug 1996 22:31:05 -0700
Received: from netcomsv.netcom.com (uumail2.netcom.com [163.179.3.52]) by ormail
.intel.com (8.7.4/8.7.3) with SMTP id WAA03308; Thu, 15 Aug 1996 22:38:53 -0700
(PDT)
Resent-From: pci-sig-request@znyx.com
Received: from ormail.intel.com (ormail.intel.com [134.134.248.3]) by relay.jf.i
ntel.com (8.7.4/8.7.3) with ESMTP id WAA19109; Thu, 15 Aug 1996 22:38:54 -0700 (
PDT)
Return-Path: pci-sig-request@znyx.com
B 4 !