The other day, I was considering how fast/good(/expensive) an ADC would have to be to capture VGA at say 1600x1200 24-bit @ 70 Hz... around 160 Msps with ~10 bits of resolution on 3 channels at least (RGB; a little lower res for VSYNC and HSYNC). Octopart parametric search says it would cost ~$40 for ADCs alone in small quantities (I don't have chip sampling vendor hookups anymore.). :'( This was going to be for a DIY IP VGA KVM because I was considering how to not spend $400-2000 on an actual new/used Avocent.
VGA is really easy to generate, most FPGA dev kits have a VGA Pong clone or VGA demo... so I can see how having HDMI would be awesome to have video and audio in the 21st century.
What about HDMI input? What I'm imagining is an HDMI freeze button, to buffer a single frame. Many projectors have that feature built in, but some don't, and I wish I could build it as an external hardware device.
I'm sure there are other use cases for a freeze button, and the idea of having it as a separate device is something so obvious to me that I'm surprised it doesn't already exist.
Probably should be illegal.
Info (21057): Implemented 1509 device resources after synthesis - the final resource count might be different
Info (21058): Implemented 15 input pins
Info (21059): Implemented 33 output pins
Info (21060): Implemented 87 bidirectional pins
Info (21061): Implemented 1240 logic cells
Info (21064): Implemented 128 RAM segments
Info (21065): Implemented 2 PLLs
I haven't been focusing on resource usage yet, but I think there's big savings potential in packet_assembler.sv since it's using around 300 cells just for parity computation.How does this work? Isn't the Apache license somewhat more restrictive than the MIT license? Why bother with both?
I've been writing a lot of Rust lately, and started providing both after their big relicensing push: https://github.com/diesel-rs/diesel/issues/82
The FPGA I'm using has HDMI and was made by Arduino, but they are not an HDMI Adopter: https://store.arduino.cc/usa/mkr-vidor-4000. "Raspberry Pi Trading Ltd" is one though.
There's a parameter to make the output be DVI only if it's a concern, I'll make a note of this in the README.
For example, the F18Amk2 project at https://atariage.com/forums/topic/280138-f18a-mk2/ which is implementing a TMS9918A has hit this problem.
I am inclined to agree that enforcement isn't 100%, but wanted to flag this up as it's relevant to your users. Thanks for adding the note!
?