Skip to content

Commit 3764cc9

Browse files
committed
updated readme
1 parent 91cc52f commit 3764cc9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,8 @@ I want to get the board out to a few people before opening the flood gates. I'm
5353
begin trying it on M2s and M3s, I want to see what the results are. It *appears* that it should work just fine, and may even work on an M1 with the
5454
right signal placement, but I'm well aware that with hardware you never know for sure until you've actually seen the results.
5555

56-
I did some experimentation with providing my own on-board clock and ignoring the dot clock from the TRS-80, which produced something that *kind of* works.
57-
Unfortunately I would need to oversample the signals considerably (probably at least 10X) and then come up with an algorithm for using the oversampled
56+
I did some experimentation with providing my own on-board clock and ignoring the dot clock from the TRS-80, which produced something that *kind of* works. I
57+
would need to oversample the signals considerably (probably at least 10X) and then come up with an algorithm for using the oversampled
5858
signals, and at this point that's just a bit beyond my Verilog skills. I'll probably keep toying around with it over time. It's clearly possible, but
5959
just not as easy as taking the dot clock from the motherboard and using it to synchronize the incoming video. I suspect this is why many -ToVGA boards
6060
have subtle issues that require options and menu systems to work around. For now the production version of the board still requires the dot clock.

0 commit comments

Comments
 (0)