From bb1362cb3b6a5ac6c1d7c79abcaec231ad61532d Mon Sep 17 00:00:00 2001 From: Eitan Adler Date: Mon, 17 Dec 2012 20:42:27 +0000 Subject: [PATCH] "likely isn't relevant since everybody uses PCI/PCIe serial cards" Noted by: imp Approved by: bcr (mentor) --- en_US.ISO8859-1/books/faq/book.xml | 27 --------------------------- 1 file changed, 27 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index 60ac33a640..b0c12fdef7 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -3668,33 +3668,6 @@ kern.timecounter.hardware: TSC -> i8254 - - - Why do I get interrupt conflicts with multi-port serial - code? - - - - When I compile a kernel with multi-port serial code, it - tells me that only the first port is probed and the rest - skipped due to interrupt conflicts. How do I fix - this? - - The problem here is that &os; has code built-in to keep - the kernel from getting trashed due to hardware or software - conflicts. The way to fix this is to leave out the IRQ - settings on all but one port. Here is an example: - - # -# Multiport high-speed serial line - 16550 UARTS -# -device sio2 at isa? port 0x2a0 tty irq 5 flags 0x501 vector siointr -device sio3 at isa? port 0x2a8 tty flags 0x501 vector siointr -device sio4 at isa? port 0x2b0 tty flags 0x501 vector siointr -device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr - - - Why does every kernel I try to build fail to compile,