Searched hist:193018 (Results 1 - 14 of 14) sorted by relevance
/freebsd-10.2-release/sys/dev/cfe/ | ||
H A D | cfe_console.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/dcons/ | ||
H A D | dcons_os.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/ofw/ | ||
H A D | ofw_console.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/xen/console/ | ||
H A D | console.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/syscons/ | ||
H A D | sysmouse.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
H A D | syscons.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/uart/ | ||
H A D | uart_tty.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/usb/serial/ | ||
H A D | usb_serial.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/nmdm/ | ||
H A D | nmdm.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/rp/ | ||
H A D | rp.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/kern/ | ||
H A D | tty_pts.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
H A D | tty.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/dev/si/ | ||
H A D | si.c | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
/freebsd-10.2-release/sys/sys/ | ||
H A D | tty.h | diff 193018 Fri May 29 06:47:48 MDT 2009 ed Last minute TTY API change: remove mutex argument from tty_alloc(). I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. |
Completed in 357 milliseconds