lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs
jimmythehorn has quit [Ping timeout: 256 seconds]
lekernel has joined #milkymist
mumptai has joined #milkymist
bhamilton has joined #milkymist
bhamilton has quit [Client Quit]
bhamilton has joined #milkymist
bhamilton has left #milkymist [#milkymist]
playthatbeat has quit [Remote host closed the connection]
playthatbeat has joined #milkymist
bhamilton has joined #milkymist
<lekernel> bhamilton, btw you can ask questions here too
<bhamilton> great :)
bhamilton has quit [Quit: Leaving.]
<GitHub87> [migen] sbourdeauducq pushed 2 new commits to master: http://git.io/9iw8-A
<GitHub87> migen/master 7a74dae Sebastien Bourdeauducq: actorlib/spi: add DMAWriteController
<GitHub87> migen/master fd089b1 Sebastien Bourdeauducq: actorlib/dma_asmi/OOOWriter: fix tag offset
<lekernel> found the problem :)
<lekernel> yay!!!
<lekernel> pairs of 2 bits were swapped ...
<lekernel> gosh this sort of bug can be so annoying ...
<lekernel> now the picture looks perfect
<larsc> hm, yea that's what i expected, just couldn't figure out which two
<larsc> which two were swapped?
<lekernel> all pairs
<lekernel> all 5 pairs of 2 bits in the 10-bit words
<larsc> ha, I stopped at trying to swap at a 4 bit boundary...
<lekernel> and no more strange behavior like lines with the wrong size etc. except at beginning and end
<larsc> that was due to the vsync character being wrong and it thought that was data
<larsc> yea
<larsc> actually are you sure that this is all?
<larsc> the the vsync bit seems to be flipped
<lekernel> updated the data
<larsc> when I count the control character I get this
<larsc> 1237 FOUND 2 0b101010100 0b1010101011
<larsc> 4 FOUND 2 0b10101011 0b1101010100
<larsc> 1236 FOUND 2 0b1010101011 0b101010100
<larsc> 6 FOUND 2 0b1101010100 0b10101011
<larsc> while I expect the numbers to be the other way around
<larsc> well not count the control characters, but count the transistions of hsync on <-> hsync off
<lekernel> mh?
<larsc> If vsync is off the transistion of hsync off to on should be the transition of c=0 to c=1
<larsc> right?
<lekernel> I think so
<lekernel> what do you see instead?
<larsc> well a transition from c=3 to c=2
<larsc> I think
<lekernel> hsync and vsync can have negative polarity - that's defined in EDID and enabled by default iirc
<lekernel> maybe it's just that
<larsc> ah
<larsc> that makes sense then
<larsc> uhm yea, 640x480 has negative polarity for both hsync and vsync
<lekernel> are there any modes that have positive polarity? (ie do I need to care about that, or just hardcode negative polarity?)
<larsc> I think 720p, 1080p has positive polarity
<larsc> negative polarity is mostly used for legacy modes, or something
<lekernel> grmbl
<lekernel> how is the gateware supposed to autodetect that?
<larsc> check which character comes after de goes from high to low
<larsc> or count the characters
<larsc> iirc vsync and hsync polarity are actually supposed to help to distiguish between modes
<lekernel> ok, so when de goes from high to low, it's usually hsync, and sometimes vsync+hsync ?
<lekernel> it can never be vsync alone
<lekernel> right?
<larsc> the pattern is de nothing hsync nothing de
<larsc> or vsync hsync+vsync vsync
<larsc> the first symbol after de goes low will always be both hsync and vsync off
<lekernel> ok so if c=3 immediately after de=0 then polarity is negative?
<larsc> I'd just take the c after de=0 and xor all other c's with it
<lekernel> good idea
sh4rm4 has quit [Ping timeout: 276 seconds]
sh4rm4 has joined #milkymist
<GitHub45> [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/nsChhw
<GitHub45> milkymist-ng/master 6307331 Sebastien Bourdeauducq: dvisampler/datacapture: swap bit pairs
<GitHub91> [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/qiTZQQ
<GitHub91> milkymist-ng/master 4259699 Sebastien Bourdeauducq: dvisampler: add RawDVISampler
<Fallenou> congratz :)
lekernel has quit [Quit: Leaving]