Change bold code snippets to inline code blocks
This commit is contained in:
parent
f658bfbb40
commit
3c76d884ef
185 changed files with 1772 additions and 1772 deletions
10
33-03.md
10
33-03.md
|
|
@ -106,15 +106,15 @@ an uneasy feeling, so I'd be most interested in hearing from any
|
|||
readers.
|
||||
|
||||
A final point is that the process of loading both the palette RAM and
|
||||
DAC registers involves performing multiple **OUT**s to the same
|
||||
DAC registers involves performing multiple `OUT`s to the same
|
||||
register. Many people whose opinions I respect recommend delaying
|
||||
between I/O accesses to the same port by performing a **JMP \$+2**
|
||||
between I/O accesses to the same port by performing a `JMP \$+2`
|
||||
(jumping flushes the prefetch queue and forces a memory access—or at
|
||||
least a cache access—to fetch the next instruction byte). In fact, some
|
||||
people recommend two **JMP \$+2** instructions between I/O accesses to
|
||||
people recommend two `JMP \$+2` instructions between I/O accesses to
|
||||
the same port, and *three* jumps between I/O accesses to the same port
|
||||
that go in opposite directions (**OUT** followed by **IN** or **IN**
|
||||
followed by **OUT**). This is clearly necessary when accessing some
|
||||
that go in opposite directions (`OUT` followed by `IN` or `IN`
|
||||
followed by `OUT`). This is clearly necessary when accessing some
|
||||
motherboard chips, but I don't know how applicable it is when accessing
|
||||
VGAs, so make of it what you will. Input from knowledgeable readers is
|
||||
eagerly solicited.
|
||||
|
|
|
|||
Loading…
Reference in a new issue