From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 22:24:36 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A2BE1065672 for ; Tue, 4 Nov 2008 22:24:36 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id F24418FC14 for ; Tue, 4 Nov 2008 22:24:35 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id C1CF31CDA4; Tue, 4 Nov 2008 23:24:34 +0100 (CET) Date: Tue, 4 Nov 2008 23:24:34 +0100 From: Ed Schouten To: Jille Timmermans Message-ID: <20081104222434.GZ1165@hoeg.nl> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> <4910C0DF.2040501@lissyara.su> <4910C505.9070809@quis.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9kBr9UDtZsI8nE8z" Content-Disposition: inline In-Reply-To: <4910C505.9070809@quis.cx> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Alex Keda , Alexey Dokuchaev , current@freebsd.org Subject: Re: device snp build broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 22:24:36 -0000 --9kBr9UDtZsI8nE8z Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Jille, Alex, Alexey, * Jille Timmermans wrote: > Alex Keda schreef: > > Jille Timmermans =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> Hello, > >> > >> snp(4) in -CURRENT is currently not supported. > >> Ed made a patch for it; which worked for me. > >> You can get the latest version from: > >> > >> http://people.freebsd.org/~ed/mpsafetty/ > >> > >> (The patch-set also includes other things; like a new /dev/console) > >=20 > > What was the reason not to support the device? > Ed rewrote the TTY system and left out snp(4): > * He didn't thought anyone was really needing it > * Because it reads from a TTY, and writes to another TTY; it would have > caused problems with blocking (full queues, etc) >=20 > After a while he got convinced to fix snp(4). > It is now experimental, so only available through his patchset. >=20 > But it will make it into HEAD before 8.0. >=20 > Ed: Please correct me if I'm wrong somewhere The main problem with snp(4) was that its design didn't really fit into the model of the new TTY layer that I imported back in August. The reason the new snp(4) isn't available in SVN yet, is because it isn't finished. It doesn't return the traditional snp(4) status codes and doesn't allow descriptors to /dev/snp to switch to a different TTY after being used. I really want to fix at least the first issue, but so far I haven't found {time,interest,etc}. The new snp(4) code is already pretty sweet - it works a lot better than the old driver. Maybe someone else is interested in fixing it? --=20 Ed Schouten WWW: http://80386.nl/ --9kBr9UDtZsI8nE8z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkQy6IACgkQ52SDGA2eCwWeBgCfRF0Cb0/KCwoUziBqwY3lhOM4 EocAnilZh1SFdp+I5VJsn43xnRouwRdY =FzkR -----END PGP SIGNATURE----- --9kBr9UDtZsI8nE8z--