From owner-freebsd-chat@FreeBSD.ORG  Fri Apr 25 07:40:42 2003
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Delivered-To: freebsd-chat@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 29B2037B407
	for <freebsd-chat@freebsd.org>; Fri, 25 Apr 2003 07:40:42 -0700 (PDT)
Received: from hope.caffeinated-systems.com (hope.caffeinated-systems.com
	[209.98.4.50])	by mx1.FreeBSD.org (Postfix) with ESMTP id C37C143FBF
	for <freebsd-chat@freebsd.org>; Fri, 25 Apr 2003 07:40:40 -0700 (PDT)
	(envelope-from jon@caffeinated-systems.com)
Received: by hope.caffeinated-systems.com (Postfix, from userid 1003)
	id C11984D912; Fri, 25 Apr 2003 09:15:32 -0500 (CDT)
Date: Fri, 25 Apr 2003 09:15:32 -0500
From: Jon Passki <jon@caffeinated-systems.com>
To: freebsd-chat@freebsd.org
Message-ID: <20030425141532.GD14108@hope.caffeinated-systems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: Video Out to Video In converter
X-BeenThere: freebsd-chat@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Non technical items related to the community
	<freebsd-chat.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chat>
List-Post: <mailto:freebsd-chat@freebsd.org>
List-Help: <mailto:freebsd-chat-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2003 14:40:42 -0000

Hello,

I'm looking for a device that would allow me to connect, for example, 
a standard PC video output (640x480, 256 color) to a device that could 
in turn convert it back into an abstracted signal.  That device would 
be accessed by, again an example, a local program that would resend 
the information out using the X protocol as a client program. The 
purpose is to access systems that have no means of communications 
other than video and keyboard, without needed a monitor or needed to 
be physically near the system.

This device doesn't need to be so sophisticated that it can autodetect 
every video output on the world and have applicable connector types.  

If a device like this doesn't exist, logically, what seems to be a 
clean way in creating a device like this?  What should be left to the 
device, and what should be configureable to the device driver?  Under 
FreeBSD, what type of device driver best fits this scenario?

Thanks for your time on these vague questions :-)

Jon