Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

Jordan Hargraphix SvgaBGI goes MIT license (Announce)

posted by Khusraw E-mail, Bucharest, Romania, 24.12.2020, 12:46
(edited by Khusraw on 24.12.2020, 13:01)

> Thank you. According to the DOCs, and it seems so in the code, during
> initalization it will use VESA BytesPerLine. This was added in original
> 3.51A: "The driver no longer assumes that logical and real line lengths are
> identical (this is when controlling via VESA driver.

I don't know which driver doesn't assume it, because the latest driver I know still assumes it, being the driver that made the bug manifest to me. As you can see in cards.asi, the value for the number of bytes per scan line is correctly saved in "BytesPerLine", but in the calculations from svga.asm the driver uses "MaxX" instead of "BytesPerLine" ("MaxX" being the width in pixels, in case you know a line of code where "MaxX" gets the value of "BytesPerLine", please point it to me).

; VESA-Infos wurden erfolgreich geholt, es:di zeigt auf den VESA-Info Block.
; Zuerst mal die Anzahl Bytes pro Scanzeile holen und in der globalen
; Variable BytesPerLine speichern. Dies berschreibt die Vorbelegung von
; Init, bisher steht dort derselbe Wert wie in MaxX.

@@L2:   mov     ax, [(VESA_InfoBlock es:di).BytesPerLine]
        mov     [BytesPerLine], ax

---
Glory to God for all things

 

Complete thread:

Back to the forum
Board view  Mix view
22632 Postings in 2109 Threads, 402 registered users, 320 users online (0 registered, 320 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum