summaryrefslogtreecommitdiffstats
path: root/usr.sbin/syslogd/syslogd.c
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2001-08-28 16:35:01 +0000
committerimp <imp@FreeBSD.org>2001-08-28 16:35:01 +0000
commit9c56de3f58ee9f71eb8262d77aa69d804f1603c2 (patch)
treecdb6e5649e73c2442f89954a76c956d0f332bc76 /usr.sbin/syslogd/syslogd.c
parentf241788ed6ee61fb6a1b0c68aca37c5c79728478 (diff)
downloadFreeBSD-src-9c56de3f58ee9f71eb8262d77aa69d804f1603c2.zip
FreeBSD-src-9c56de3f58ee9f71eb8262d77aa69d804f1603c2.tar.gz
It turns out that while Toshiba laptops don't want to route interrupts
multiple times, others do. The last strategy, which was to assume that already routed interrupts were good and just return them doesn't work for some laptops. So, instead, we have a new strategy: we notice that we have an interrupt that's already routed. We go ahead and try to route it, none the less. We will assume that it is correctly routed, even if the route fails. We still assume that other failures in the bios32 call are because the interrupt is NOT routed. Note: some laptops do not support the bios32 interface to PCI BIOS and we need to call it via the INT 2A interface. That is another windmill to till at later. Also correct a minor typo and minor whitespace nits. Strong MFC candidate.
Diffstat (limited to 'usr.sbin/syslogd/syslogd.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud