*** tpb has joined #timvideos | 00:00 | |
*** seaLne has quit IRC | 00:08 | |
*** seaLne has joined #timvideos | 00:10 | |
*** Neuron1k has quit IRC | 00:21 | |
*** panther has joined #timvideos | 02:01 | |
panther | mithro, hi | 02:04 |
---|---|---|
*** panther is now known as sab_123 | 02:04 | |
CarlFK | hi sab_123 | 02:55 |
sab_123 | hi | 02:56 |
*** panther has joined #timvideos | 03:03 | |
*** sab_123 has quit IRC | 03:03 | |
mithro | I'll be around in about an hour | 03:18 |
mithro | I'm around now | 04:05 |
panther | mithro, cool | 04:06 |
*** panther is now known as sab_123 | 04:06 | |
sab_123 | i still dont understand the MPSSE | 04:06 |
sab_123 | how is the data packet actually sent | 04:06 |
sab_123 | where is the doc for this | 04:06 |
sab_123 | or is it not documented at all? | 04:06 |
sab_123 | http://www.ftdichip.com/Support/Documents/AppNotes/AN2232C-01_MPSSE_Cmnd.pdf | 04:07 |
sab_123 | For example | 04:08 |
sab_123 | section 3.3 | 04:08 |
sab_123 | will USB FIFO have | 04:08 |
sab_123 | 0x10 0xlengthl 0xlength 0xdata | 04:09 |
sab_123 | is this how it is? | 04:09 |
sab_123 | I bit bang 0xdataa out | 04:09 |
sab_123 | and what is no read in these sections | 04:10 |
sab_123 | mithro, I meant the data in the buffer | 04:18 |
mithro | sab_123: I believe so | 04:18 |
sab_123 | because without that | 04:19 |
sab_123 | we really dont know how ot handle this data | 04:19 |
sab_123 | JTAG seems to have byte mode, mithro | 04:19 |
sab_123 | dont understand that | 04:19 |
sab_123 | they say it is only single pin, mithro | 04:19 |
mithro | sab_123: what do you mean? The commands are like "clock this data out", "clock this data in", "clock this data out and in at the same time" | 04:21 |
sab_123 | i mean that JTAG is 4 pins | 04:22 |
sab_123 | but they clock data byte wise | 04:22 |
sab_123 | and they have a bit mode | 04:22 |
sab_123 | so I dont understand | 04:22 |
sab_123 | and this is just the device side | 04:22 |
sab_123 | not the usb side, mithro | 04:23 |
mithro | Byte just means you have to clock it out 8 bits | 04:23 |
sab_123 | yes | 04:23 |
sab_123 | but there arent enough pins | 04:23 |
sab_123 | for JTAG, mithro | 04:23 |
mithro | sab_123: what do you mean there aren't enough pins? | 04:23 |
sab_123 | mithro, JTAG is a 4 pin interface | 04:23 |
sab_123 | TDO, TMS,TCK and something else | 04:24 |
sab_123 | THis data sent from libftdi is now in FX2's buffer | 04:24 |
mithro | There is TDO, TDI, TCK and TMS/CS mentioned in that document | 04:24 |
sab_123 | yes | 04:24 |
sab_123 | those are single pins | 04:24 |
sab_123 | not a bus | 04:24 |
mithro | Correct | 04:24 |
sab_123 | so how do you clock a byte out | 04:24 |
sab_123 | you can only clokc bits | 04:24 |
mithro | Same way you would clock out 8 bits | 04:24 |
sab_123 | mithro, there seems to be something I am missing here | 04:25 |
sab_123 | libftdi on computer sends a command saying 0xcommand 0xlength 0xdata | 04:25 |
sab_123 | so now lets say 0xcommand is section 3.3 | 04:25 |
sab_123 | clock data out byte wise | 04:25 |
mithro | It means that the data is just whole bytes, so you are always going to end up clocking out multiples of 8 bits | 04:27 |
sab_123 | ah | 04:29 |
*** hyades_zombie has quit IRC | 04:29 | |
sab_123 | confusing nomenclature | 04:29 |
sab_123 | byte wise means send 8 bit data on a bus | 04:29 |
sab_123 | anyway,mi | 04:30 |
sab_123 | anyway, mithro | 04:30 |
sab_123 | I have submitted the proposal | 04:30 |
sab_123 | mithro, if you have any suggestions, please let me know | 04:30 |
*** hyades_zombie has joined #timvideos | 04:30 | |
mithro | xfxf: ping? | 04:46 |
xfxf | pong | 04:46 |
mithro | xfxf: Have you seen a video example or something which shows a mixing desk controlling the fades using one of the fade sticks? | 04:47 |
xfxf | i've used proprietary gear? | 04:47 |
xfxf | so, directly, yes | 04:48 |
mithro | xfxf: Just want an example which shows the wipes control by a hardware slider | 04:48 |
xfxf | ooh sorry | 04:48 |
xfxf | you mean do i know of a video | 04:48 |
xfxf | i thought it was a wierd question :) | 04:48 |
xfxf | mithro: https://youtu.be/beS6DhVe8yU?t=115 | 04:51 |
xfxf | it's a DIY thing but shows the fader | 04:51 |
mithro | xfxf: thanks, that is perfect! | 04:52 |
mithro | xfxf: so, you going to do hacking then? :P | 05:04 |
*** Neuron1k has joined #timvideos | 05:10 | |
*** tija has joined #timvideos | 05:48 | |
*** Bertl_zZ is now known as Bertl | 06:04 | |
*** Neuron1k has quit IRC | 06:04 | |
*** se6astian|away is now known as se6astian | 06:48 | |
*** se6astian is now known as se6astian|away | 06:53 | |
*** panther has joined #timvideos | 06:57 | |
*** sab_123 has quit IRC | 06:57 | |
xfxf | mithro: prob gonna poke at the setup and vocto at some point over the weekend, ya | 06:58 |
xfxf | and test that fix you wanted me to | 06:58 |
*** panther_ has joined #timvideos | 07:01 | |
*** panther_ has quit IRC | 07:03 | |
*** panther_ has joined #timvideos | 07:04 | |
*** panther has quit IRC | 07:04 | |
*** ssk1328 has joined #timvideos | 07:26 | |
*** aom has joined #timvideos | 07:40 | |
mithro | hello aom | 07:54 |
aom | Hello! | 08:07 |
mithro | aom: So, just wanted to say I like your proposal quite a bit even though I've put quite a lot of comments on it | 08:09 |
aom | About developing environment, I must choose migen ? or better migen? | 08:09 |
aom | thanks for many comments. now i modify them. | 08:10 |
mithro | aom: Unless there is a significant reason not to use migen, we should be using migen | 08:10 |
mithro | aom: We can use Verilog, but only if there is a large project that we want to reuse - like the lm32 or the or1k cores | 08:10 |
mithro | we shouldn't use VHDL, as we don't have good FOSS tools for supporting them | 08:11 |
aom | Okay! i will learn migen developing skill! | 08:11 |
mithro | migen should be pretty easy to pick up if you know either VHDL or Verilog | 08:11 |
mithro | You will also probably find it much quicker to do development in once you are use to it | 08:11 |
mithro | aom: Did you understand the idea of reusing the existing LiteEth stuff and the RTP headers instead of doing the Ethernet MIO stuff? | 08:12 |
mithro | aom: Did that make sense? | 08:12 |
aom | yes, I understand! | 08:13 |
mithro | aom: It's cool that you have 4 Atlys boards :) - I'm down to 3 I think (I've lent mine out to people) | 08:14 |
aom | yes! and I have other xilinx boards. and i have developing tools like ISE. so I can easily test the hardware!! | 08:15 |
mithro | aom: while initially during development you can do things like hard code IP addresses and stuff, it would be good as an extension goal to allow dynamic discovery and configuration using something like Avahi / mDNS | 08:16 |
mithro | aom: I'd also recommend giving building the HDMI2USB-misoc-firmware building a go (after you have finished your proposal) - See instructions here -> https://github.com/timvideos/HDMI2USB-misoc-firmware/tree/master/scripts | 08:16 |
tpb | Title: HDMI2USB-misoc-firmware/scripts at master · timvideos/HDMI2USB-misoc-firmware · GitHub (at github.com) | 08:16 |
aom | that is greate ! i will check it. | 08:17 |
mithro | aom: _florent_ in this channel is also the developer of LiteEth and most of the firmware, so if you have specific questions about how things work, he is a good person to ask | 08:18 |
*** seaLne has quit IRC | 08:19 | |
*** seaLne has joined #timvideos | 08:19 | |
mithro | aom: You might also consider with this approach that you can develop one side at a time and might be able to use a normal computer on the otherside too | 08:19 |
mithro | seaLne: ping? | 08:19 |
mithro | aom: might make things a bit easier while developing stuff | 08:19 |
mithro | aom: You probably want to start with something like 640x480 when debugging as well (before getting 720p working) | 08:20 |
aom | sorry, what do you mean the approach?? i cannot get it. | 08:22 |
mithro | aom: If you are using RTP, it is easy for you to go FPGA->Ethernet->Computer rather then FPGA->Ethernet->FPGA | 08:23 |
aom | i understand it! exactly, its better to reuse existing LiteETH and RTPtimestamper. | 08:26 |
mithro | aom: any questions before I disappear for a couple of hours? | 08:26 |
aom | nothing now! anyway I complete my document. | 08:27 |
aom | Thank you for much feedback! | 08:27 |
mithro | aom: feel free to ask in the channel if you do, I'm try and answer when I get back | 08:28 |
*** ssk1328 has quit IRC | 08:28 | |
*** Bertl is now known as Bertl_oO | 08:37 | |
*** sab has quit IRC | 08:53 | |
*** thaytan has quit IRC | 09:18 | |
*** Sewar has quit IRC | 09:41 | |
*** aom has quit IRC | 09:44 | |
*** Sewar has joined #timvideos | 09:49 | |
*** Sewar has quit IRC | 09:53 | |
*** hyades_zombie has quit IRC | 09:53 | |
*** hyades_zombie has joined #timvideos | 09:54 | |
*** Sewar has joined #timvideos | 10:00 | |
*** hyades_z- has joined #timvideos | 10:01 | |
*** kflux has joined #timvideos | 10:05 | |
*** hyades_zombie has quit IRC | 10:06 | |
*** kflux has quit IRC | 11:03 | |
*** thaytan has joined #timvideos | 11:52 | |
*** ChanServ sets mode: +v thaytan | 11:52 | |
*** ssk1328 has joined #timvideos | 12:06 | |
ssk1328 | mithro: The original github issue of my project <https://github.com/timvideos/getting-started/issues/34>, referred to issues 27 of misoc-firmware issue tracker | 12:09 |
tpb | Title: [HDMI2USB] Add "hardware mixing" support to HDMI2USB firmware · Issue #34 · timvideos/getting-started · GitHub (at github.com) | 12:09 |
ssk1328 | https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/27 | 12:09 |
tpb | Title: Support mixing the two HDMI inputs together · Issue #27 · timvideos/HDMI2USB-misoc-firmware · GitHub (at github.com) | 12:09 |
ssk1328 | This particular issue tracker referred to developing some test cases for verifying the working of board. https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/185 | 12:11 |
tpb | Title: Embed a wide range of test patterns · Issue #185 · timvideos/HDMI2USB-misoc-firmware · GitHub (at github.com) | 12:11 |
ssk1328 | That's why I added a section for overall testing of board issues like overscan/underscan/aspect ratio in my timeline(week11) | 12:15 |
mithro | ssk1328: as you are only mixing and not transforming,overscan/understand/aspect ratio shouldn't be a problem for you | 12:27 |
mithro | ssk1328: you should be more concerned with color mixing | 12:27 |
ssk1328 | Okay. | 12:27 |
ssk1328 | I will add joystick and scaling things instead of that. | 12:28 |
mithro | ssk1328: the joystick thing is more about having something cool to show off :) | 12:28 |
ssk1328 | Yeah. Pretty Cool :) | 12:28 |
mithro | ssk1328: eventually we'd like to support things like MIDI and DMX controllers for doing the fades | 12:30 |
mithro | ssk1328: if we get your and aom's stuff working together, that will also be super awesome | 12:30 |
*** tija has quit IRC | 13:38 | |
*** Neuron1k has joined #timvideos | 14:25 | |
mithro | _florent_: ping? | 14:37 |
mithro | wb Neuron1k | 14:37 |
Neuron1k | Hi mithro | 14:37 |
_florent_ | mithro: yes? | 14:45 |
mithro | _florent_: any idea how much work it would be to get the HDMI2USB firmware onto master misoc/migen? I saw you have ported a lot of your stuff recently? | 14:45 |
_florent_ | most of the work will be around the DMA since some modules have been removed, but in a first we can copy these modules in HDMI2USB | 14:51 |
_florent_ | doing that it's probably a few days of work | 14:52 |
mithro | _florent_: maybe that is worth trying to do before we have GSoC students hacking on things? | 14:53 |
*** rohitksingh has joined #timvideos | 15:24 | |
*** ssk1328 has quit IRC | 15:50 | |
*** jp111 has joined #timvideos | 16:07 | |
*** jp111 has quit IRC | 16:11 | |
*** panther has joined #timvideos | 16:36 | |
*** panther_ has quit IRC | 16:36 | |
*** panther has quit IRC | 16:47 | |
*** rohitksingh has quit IRC | 17:38 | |
*** rohitksingh has joined #timvideos | 18:11 | |
*** Neuron1k has quit IRC | 18:57 | |
*** vikram9866 has joined #timvideos | 20:06 | |
*** vikram9866 has quit IRC | 20:09 | |
*** rohitksingh has quit IRC | 20:12 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!