From owner-freebsd-arch@FreeBSD.ORG  Wed Apr  9 10:56:46 2008
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 712F31065670
	for <arch@freebsd.org>; Wed,  9 Apr 2008 10:56:46 +0000 (UTC)
	(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.freebsd.org (Postfix) with ESMTP id 35CEB8FC26
	for <arch@freebsd.org>; Wed,  9 Apr 2008 10:56:45 +0000 (UTC)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.61.3])
	by phk.freebsd.dk (Postfix) with ESMTP id CF03317104;
	Wed,  9 Apr 2008 10:56:44 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m39Auikp044322;
	Wed, 9 Apr 2008 10:56:44 GMT (envelope-from phk@critter.freebsd.dk)
To: John E Hein <jhein@timing.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 08 Apr 2008 17:40:32 CST."
	<18428.624.490619.248235@gromit.timing.com> 
Date: Wed, 09 Apr 2008 10:56:44 +0000
Message-ID: <44321.1207738604@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: arch@freebsd.org
Subject: Re: tt_ioctl 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2008 10:56:46 -0000

In message <18428.624.490619.248235@gromit.timing.com>, John E Hein writes:

>I guess I'm leaning toward a separate
>uftdi0.ctl minor device despite what the sourceforge
>linux driver does.

That would be my inclination too.

We had something slightly similar with a sync/async board at one
point.

The driver never made it into the tree for a number of reasons, but
the same problem was present: We have one physical connector, and
it can either be a tty or something else.

By adding a uftdi0.ctl (or whatever you name it, "uftdi0" is probably
even preferable) you get a separate and direct channel to the
device, and you can issue whatever IOCTLs, generic (preferably)
or device specific, it takes to make the port do whatever non-tty
task it is you want.

That seems like the sensible model to me.

> > Otherwise, use ugen, it's easier, simpler and likely faster.
>
>You can't use ugen, [...]

Forget that then.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.