summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_intr.c
diff options
context:
space:
mode:
authoriedowse <iedowse@FreeBSD.org>2001-06-20 16:47:23 +0000
committeriedowse <iedowse@FreeBSD.org>2001-06-20 16:47:23 +0000
commita4c30a870ecf7d7d23259d7902957c614a43491c (patch)
tree9c65929450215310ad4e0f96a7fcbd7ba74e4341 /sys/kern/kern_intr.c
parent8a223ad3ced39a21f12ed05f9d6b6adc39bb4ab3 (diff)
downloadFreeBSD-src-a4c30a870ecf7d7d23259d7902957c614a43491c.zip
FreeBSD-src-a4c30a870ecf7d7d23259d7902957c614a43491c.tar.gz
The serial console break-to-debugger support only functioned while
the console device was open. At other times, the interrupts that are used to detect the break signal or ~^B sequence were disabled, so these events would not be noticed until the next open (e.g. the next kernel printf). This was mainly a problem while there was no getty running on the console, such as during bootup or shutdown. For serial consoles with break-to-debugger support, we now enable the generation of interrupts at attach time, and we leave them enabled while the device is closed. Reviewed by: bde (I've since made chages as per his suggestions)
Diffstat (limited to 'sys/kern/kern_intr.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud