Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Nov 2008 23:24:34 +0100
From:      Ed Schouten <ed@80386.nl>
To:        Jille Timmermans <jille@quis.cx>
Cc:        Alex Keda <admin@lissyara.su>, Alexey Dokuchaev <danfe@nsu.ru>, current@freebsd.org
Subject:   Re: device snp build broken?
Message-ID:  <20081104222434.GZ1165@hoeg.nl>
In-Reply-To: <4910C505.9070809@quis.cx>
References:  <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> <4910C0DF.2040501@lissyara.su> <4910C505.9070809@quis.cx>

next in thread | previous in thread | raw e-mail | index | archive | help

--9kBr9UDtZsI8nE8z
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Jille, Alex, Alexey,

* Jille Timmermans <jille@quis.cx> 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 <ed@80386.nl>
 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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081104222434.GZ1165>