Searched hist:228631 (Results 1 - 7 of 7) sorted by relevance
| /freebsd-11-stable/sys/dev/uart/ | ||
| H A D | uart_tty.c | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
| /freebsd-11-stable/sys/dev/dcons/ | ||
| H A D | dcons_os.c | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
| /freebsd-11-stable/sys/dev/usb/serial/ | ||
| H A D | usb_serial.c | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
| /freebsd-11-stable/sys/sys/ | ||
| H A D | cons.h | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
| /freebsd-11-stable/sys/kern/ | ||
| H A D | kern_cons.c | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
| /freebsd-11-stable/sys/dev/sio/ | ||
| H A D | sio.c | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
| /freebsd-11-stable/sys/dev/syscons/ | ||
| H A D | syscons.c | diff 228631 Sat Dec 17 13:17:31 MST 2011 avg kern cons: introduce infrastructure for console grabbing by kernel At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months |
Completed in 178 milliseconds