From owner-freebsd-current Mon Jun 23 13:54:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29935 for current-outgoing; Mon, 23 Jun 1997 13:54:42 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29918 for ; Mon, 23 Jun 1997 13:54:27 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id OAA07518; Mon, 23 Jun 1997 14:53:16 -0600 (MDT) Message-Id: <199706232053.OAA07518@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Terry Lambert cc: jseger@freebsd.scds.com, current@FreeBSD.ORG Subject: Re: Activehome X10 Interface In-reply-to: Your message of "Mon, 23 Jun 1997 13:32:02 PDT." <199706232032.NAA01609@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 14:53:15 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > > I searched the list and the only reference I could find that came close was: > > [ ... ] > > > 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. When/if someone has time to read this code thru could they comment on how this issue is handled in the code? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD