From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: [9fans] aux/vga hsync/hblank confustion
Date: Sat, 10 Jan 2015 23:50:35 +0100 [thread overview]
Message-ID: <581cb553c4f0794103d1444a810602cd@felloff.net> (raw)
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
next reply other threads:[~2015-01-10 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 22:50 cinap_lenrek [this message]
2015-01-11 8:25 ` kokamoto
2015-01-15 5:21 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=581cb553c4f0794103d1444a810602cd@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).