svn commit: r40411 - head/en_US.ISO8859-1/books/faq

Eitan Adler eadler at
Mon Dec 17 20:42:28 UTC 2012

Author: eadler
Date: Mon Dec 17 20:42:27 2012
New Revision: 40411

  "likely isn't relevant since everybody uses PCI/PCIe serial cards"
  Noted by:	imp
  Approved by:	bcr (mentor)


Modified: head/en_US.ISO8859-1/books/faq/book.xml
--- head/en_US.ISO8859-1/books/faq/book.xml	Mon Dec 17 20:42:25 2012	(r40410)
+++ head/en_US.ISO8859-1/books/faq/book.xml	Mon Dec 17 20:42:27 2012	(r40411)
@@ -3669,33 +3669,6 @@ kern.timecounter.hardware: TSC -> i82
-	<question id="multiport-serial-interrupts">
-	  <para>Why do I get interrupt conflicts with multi-port serial
-	    code?</para>
-	</question>
-	<answer>
-	  <para>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?</para>
-	  <para>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:</para>
-	  <programlisting>#
-# 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</programlisting>
-	</answer>
-      </qandaentry>
-      <qandaentry>
 	<question id="generic-kernel-build-failure">
 	  <para>Why does every kernel I try to build fail to compile,
 	    even <filename>GENERIC</filename>?</para>

More information about the svn-doc-all mailing list