Subject: Re: [9front] mnt reform hdmi
Date: Sat, 03 Sep 2022 13:29:00 -0700 [thread overview]
Message-ID: <F24F76429F6EB8D298397BE4E09CFF4D@thinktankworkspaces.com> (raw)
I think I recall reading that it is DVI
Quoth Thaddeus Woskowiak <email@example.com>:
> On Sat, Sep 3, 2022 at 5:51 AM Steve Simon <firstname.lastname@example.org> wrote:
> > having spent years (literally) getting an hdmi interface working properly (certified) i would run from it as fast as you can.
> > too fancy, too bodged together and too much security that plainly doesnt work (mut must be supported).
> > i can offer some code to decode cec to human if you really want to go down that route.
> Is the mnt reform HDMI port providing true HDMI or DVI via an HDMI
> port? From memory licensing for HDMI is a PITA so many choose to
> ignore all the HDMI crap and just output plain DVI eliminating the
prev parent reply other threads:[~2022-09-03 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 2:49 william
2022-09-03 3:03 ` Sigrid Solveig Haflínudóttir
2022-09-03 9:47 ` Steve Simon
2022-09-03 11:31 ` Thaddeus Woskowiak
2022-09-03 20:29 ` william [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).