Convert notes into blockquotes
This commit is contained in:
parent
832fb15e54
commit
8ed9dea394
105 changed files with 884 additions and 411 deletions
9
11-05.md
9
11-05.md
|
|
@ -61,9 +61,12 @@ adapter cycle-eater, as measured in cycles lost to wait states, is
|
|||
indeed much worse on AT-class computers than it is on the PC, and it's
|
||||
worse still on more powerful computers.
|
||||
|
||||
------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
 *How bad is the display adapter cycle-eater on an AT? It's this bad: Based on my (not inconsiderable) experience in timing display adapter access, I've found that the display adapter cycle-eater can slow an AT—or even a 386 computer—to near-PC speeds when display memory is accessed.*
|
||||
------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
> 
|
||||
> How bad is the display adapter cycle-eater on an AT? It's this bad:
|
||||
> Based on my (not inconsiderable) experience in timing display adapter
|
||||
> access, I've found that the display adapter cycle-eater can slow an
|
||||
> AT—or even a 386 computer—to near-PC speeds when display memory is
|
||||
> accessed.
|
||||
|
||||
I know that's hard to believe, but the display adapter cycle-eater gives
|
||||
out just so many display memory accesses in a given time, and no more,
|
||||
|
|
|
|||
Loading…
Reference in a new issue