it seems to me that aux/vga uses shb/ehb (start/end horizontal blank) to
really mean shs/ehs (start/end horizontal sync)?

there are some vgadb entries that specify shs *smaller* than shb and the
edid parser does the following:

        m->x = ha;
        m->ht = ha+hb;
        m->shs = ha;                            <- *WHAT* 
        m->shb = ha+hso;                        <- *WHAT*
        m->ehb = ha+hso+hspw;           <- *WHAT*
        m->ehs = ha+hb;                         <- *WHAT*

where:

ha = horizontal active
hb = horizontal blanking
hso = horizontal sync pulse offset (relative to start of blank)
hspw = horisontal sync pulse width

the hardcoded vesa standard modes in vesadb.c seem to use the field
in the right way i think.

interestinly, shs and ehb are rarely given in vgadb and we default
to: shs = shb and ehs = ehb when omited, so this might explain why
stuff works at all.

so what is going on here?

--
cinap

Reply via email to