On 10/19/2011 04:24 AM, Wolfgang Spraul wrote:
So... it's still a valid question whether moving pins from one bank
to another will force us to deal with two different bitstreams now.
Yes, it will.
> Is that for single-link or dual-link?
Single-link, which I think will cause plenty of PCB rout
> On the M1, there are plenty of suitable I/Os available in bank 2, so
> we'll use it. We need a minimum of 8 I/Os (4 differential pairs: RGB
> + clock).
Is that for single-link or dual-link?
I kind of like the idea of routing a full set of dual-link wires to
the DVI-I connector now. Even if we d
> Whether this end is imminent of not, I don't know. But if this
> change makes you need a separate bitstream, then that's an issue
> you probably couldn't avoid for very long anyway.
That doesn't really answer my question. The ability to provide one
bitstream to work across all Milkymist One boar
Wolfgang Spraul wrote:
> Would that make it difficult to have one bitstream that works across
> all Milkymist One boards?
I'd say that this would be the kind of change that accelerates
the process that ends with the inability of having a common
bitstream :)
Whether this end is imminent of not, I
> Would moving some of the bank 0 I/Os to bank 2 to make room be an
> option ? If bank 0 is U22A, SD_* and LED1/2 may be suitable
> candidates for a relocation.
Would that make it difficult to have one bitstream that works across
all Milkymist One boards?
__
S?bastien Bourdeauducq wrote:
> * TMDS is supported in banks 0 and 2 with VCCO=3.3V (Reference
> document:
Bank 0 = U22A and bank 2 = U22C ?
> On the M1, there are plenty of suitable I/Os available in bank 2, so
> we'll use it. We need a minimum of 8 I/Os (4 differential pairs: RGB
> + clock).
W
Hi,
here are some resources for supporting DVI on the M1:
* DVI-A and DDC are already present from VGA. We simply use the same
schematics, with the different connector.
* For DVI-D, we have to use TMDS signaling. It is supported directly by
the FPGA I/Os.
* DVI-A and DVI-D can be combined into
