Remove 4.3BSD tty compatibility

I would like to use the current momentum of the sgtty.h removal and kill the remaining parts of the COMPAT_43 tty handling in the kernel, too. (There are some further network-related COMPAT_43 fragments that are not touched by this.) The diff below has only been tested as far as building and

rtsx(4) diff

rtsx_read_cfg returns 0 on success. Index: dev/ic/rtsx.c === RCS file: /cvs/src/sys/dev/ic/rtsx.c,v retrieving revision 1.6 diff -u -p -r1.6 rtsx.c --- dev/ic/rtsx.c 6 Dec 2013 21:03:03 - 1.6 +++ dev/ic/rtsx.c

Re: rtsx(4) diff

On Sun, Dec 08, 2013 at 11:29:36AM -0500, David Hill wrote: rtsx_read_cfg returns 0 on success. Committed, thanks! Index: dev/ic/rtsx.c === RCS file: /cvs/src/sys/dev/ic/rtsx.c,v retrieving revision 1.6 diff -u -p -r1.6

Re: Remove 4.3BSD tty compatibility

Christian Weisgerber na...@mips.inka.de wrote: The diff below has only been tested as far as building and running a kernel. I'm throwing this out so people with a better understanding of the kernel can tell me if I'm missing something. Please ignore this for the time being. There is more

TIMEOUT_INITIALIZER()

this lets you init a timeout when its declared, much like how things like MUTEX_INITIALIZER or RWLOCK_INITIALIZER work. ok? Index: sys/sys/timeout.h === RCS file: /cvs/src/sys/sys/timeout.h,v retrieving revision 1.24 diff -u -p

TIMEOUT_INITIALIZER() for src/sys/dev.c to avoid timeout_initialized()

this is a demonstration of using TIMEOUT_INITIALIZED(). because we know the timeout is always set up correctly, we dont have to test for it all over the place. Index: rnd.c === RCS file: /cvs/src/sys/dev/rnd.c,v retrieving revision