From owner-freebsd-arch@FreeBSD.ORG Tue Sep 21 10:14:38 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E3DC16A4CE for ; Tue, 21 Sep 2004 10:14:38 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61A6743D2D for ; Tue, 21 Sep 2004 10:14:37 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i8LAEZWg070627; Tue, 21 Sep 2004 12:14:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce M Simpson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 21 Sep 2004 03:07:51 PDT." <20040921100751.GD842@empiric.icir.org> Date: Tue, 21 Sep 2004 12:14:35 +0200 Message-ID: <70626.1095761675@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: arch@freebsd.org Subject: Re: [HEADSUP] naming of tty devices. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 10:14:38 -0000 In message <20040921100751.GD842@empiric.icir.org>, Bruce M Simpson writes: >On Mon, Sep 20, 2004 at 09:38:45AM +0200, Poul-Henning Kamp wrote: >> Other drivers have resorted to various variations of this scheme >> (if they were copy&pasted from sio.c) or rolled their own private >> naming system. In other words: it's a pretty mess right now. > >I've noticed the third-party software modem drivers in ports have this >problem. I looked at what it would take if we were to rewrite them as >uart(4) attachments and was pleasantly surprised to find it'd eliminate >the reckless forking of sio(4). > >However, eliminating the naming inconsistency here can only be a good >thing; if uart(4) can be kept in sync with these tty changes so much >the better. uart is one of our tty drivers and as such it will be part of this. (That also means that uart drivers will get cua* and init/lock functionality). To some extent I'm not entirely sure that lumping anything uart finds into one name-category (ttyu*) makes sense, but that is a detail decision which can be looked at in the isolated context of uart later. -- 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.