os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

"likely isn't relevant since everybody uses PCI/PCIe serial cards"

Browse source 
Noted by:	imp
Approved by:	bcr (mentor)
This commit is contained in:
Eitan Adler 2012-12-17 20:42:27 +00:00
parent bcd4aeb08d
commit bb1362cb3b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=40411
1 changed files with 0 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
en_US.ISO8859-1/books/faq/book.xml
View file

@ -3668,33 +3668,6 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</answer>
</qandaentry>
<qandaentry>
<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,