From owner-freebsd-arch@FreeBSD.ORG  Thu Oct 14 18:53:26 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 962EC16A4CE
	for <arch@freebsd.org>; Thu, 14 Oct 2004 18:53:26 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D030943D31
	for <arch@freebsd.org>; Thu, 14 Oct 2004 18:53:25 +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 i9EIrOgR070820
	for <arch@freebsd.org>; Thu, 14 Oct 2004 20:53:24 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: arch@freebsd.org
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 14 Oct 2004 20:53:24 +0200
Message-ID: <70819.1097780004@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Subject: tty code, status and future...
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 14 Oct 2004 18:53:26 -0000


I'm done hashing tty code for now and I'll take a break away from
it for some time.

Apart from the 3000 lines less copy&paste code we are now able to
safely remove a serial port which is being used (not all drivers
support this yet though).

A number of drivers still need some minor polishing mostly related
to how tty structures are allocated and managed.

The next logical step is to sort out the tty <-> linedisc stuff and
decide where snoop(4) fits into the bigger picture.

When that is sorted out, we can try to remove Giant.

But as I said: I'm taking a break for now, I'll be hacking bufcache
instead.

-- 
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.