LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

fix minor typos in Plug-and-Play-HOWTO.sgml

This commit is contained in:
Jason Leschnik 2016-10-24 21:51:38 +11:00
parent 4b2529d628
commit 8e3563c40f
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
LDP/howto/linuxdoc/Plug-and-Play-HOWTO.sgml
View File

@ -961,7 +961,7 @@ everything.
How should you answer this question to your BIOS? If you have at
at least the 2.4 kernel you could answer it either way and Linux will
usually work fine. Even if you have have Windows 2000 or XP on the
usually work fine. Even if you have Windows 2000 or XP on the
same PC, it will usually work OK either way. This is because both
Windows and Linux are supposedly PnP OS's and if the OS is PnP it
should be able to also handle the case where the BIOS has configured
@ -2106,7 +2106,7 @@ sends such a message must first gain control of the main bus so that
it can send the interrupt message. Such a message contains more info
than just "I'm sending an interrupt". It contains an index for the
address of program that needs to be run to service the IRQ. That
index, such as 3, would mean the the cpu find the address it must jump
index, such as 3, would mean for the cpu to find the address it must jump
to in the 3rd element of a special table that the cpu knows about.
Since cards must support MSI and many cards don't, it seems that
@ -2405,7 +2405,7 @@ message could say something like "resource busy", and not clearly
state that it was an interrupt problem.
<sect1>Real Interrupt Conflict
<p>Both the BIOS and the the kernel will not knowingly allow any
<p>Both the BIOS and the kernel will not knowingly allow any
interrupt conflict, so how can they happen? One way is if someone
has put an incorrect IRQ into a configuration file, such as giving a
parameter to a module like: irq=9. In this example, suppose the irq
@ -2456,7 +2456,7 @@ IRQs for legacy ISA devices that are not PnP. These settings may be
wrong and should be checked out, especially if you're having problems.
For example, someone may have reserved an IRQ for an ISA card that has
long since been removed from the PC. If you unreserved this IRQ then
this IRQ is available and and conflict disappears.
this IRQ is available and the conflict disappears.
Sometimes the BIOS will solve the problem of an IRQ shortage by using
what it calls IRQ 0. There is no such IRQ available since the real
@ -2598,7 +2598,7 @@ is an address conflict you get an error message.
communicate with the CPU. The device driver, running on the CPU would
read and write data to/from the I/O address space and main memory.
Unfortunately, this requires two steps. For example, 1. read data from
a device (in IO address space) and temporarily store in in the CPU; 2.
a device (in IO address space) and temporarily store in the CPU; 2.
write this data to main memory. A faster way would be for the device
itself to put the data directly into main memory. One way to do this
is by using ISA <ref id="dma_" name="DMA Channels"> or PCI bus