From owner-freebsd-current  Mon Jun 23 14:22:12 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA01320
          for current-outgoing; Mon, 23 Jun 1997 14:22:12 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA01310
          for <current@FreeBSD.ORG>; Mon, 23 Jun 1997 14:22:09 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA01692; Mon, 23 Jun 1997 14:10:27 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199706232110.OAA01692@phaeton.artisoft.com>
Subject: Re: Activehome X10 Interface
To: smp@csn.net (Steve Passe)
Date: Mon, 23 Jun 1997 14:10:27 -0700 (MST)
Cc: terry@lambert.org, jseger@freebsd.scds.com, current@FreeBSD.ORG
In-Reply-To: <199706232053.OAA07518@Ilsa.StevesCafe.com> from "Steve Passe" at Jun 23, 97 02:53:15 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > could this be the post you are thinking of?
> > 
> > Yes.
> 
> I'm really too busy right now to look this code over in detail, but a quick
> scan failed to find any specific handling of the RI line from the activehome.
> I think this code polls the serial input every two seconds instead, which
> is what I suggest avoiding.  For background the activehome expects that the
> PC may be turned off, and tries to get its attention via the RI line.  I'm
> proposing that the proper solution is to attach RI to DCD, and use a signal
> catcher for SIGHUP to notice when the activehome has data instead of
> polling the activehome.

This makes sense... RI is frequently used to wake up "green" machines
in "standby" or other APM power-save modes.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.