| 01:00 | mumptai | left the channel |
| 03:41 | Bertl | off to bed now ... have a good one everyone!
|
| 03:41 | Bertl | changed nick to: Bertl_zZ
|
| 05:16 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 06:58 | fredy__ | joined the channel |
| 06:59 | fredy | left the channel |
| 07:41 | mumptai | joined the channel |
| 08:33 | schmoggie1 | left the channel |
| 10:16 | Dest123 | joined the channel |
| 10:55 | anuejn | some more experiments resulted in this plot: https://files.niemo.de/fifo_interface_idle.svg
|
| 10:56 | anuejn | interestingly the "bursts" the ft601 accepts are always 2k in size
|
| 11:08 | mumptai | left the channel |
| 11:09 | mumptai | joined the channel |
| 11:10 | mumptai | left the channel |
| 11:10 | anuejn | when we force the burst size to 1k we get pretty exactly half the bandwidth
|
| 11:10 | anuejn | (180Mbyte /s)
|
| 11:28 | se6ast1an | anuejn: so this all seems to hint at 360MB/s being some kind of hard limit I assume?
|
| 11:36 | vup | we think it has to do with the mode we are using, there are two modes: 245 and 600
|
| 11:37 | vup | currently we are using the 245 mode, and this indeed looks like it might be kind of a hard limit in this mode
|
| 11:39 | vup | however we think using the 600 mode it might be possible to get better performance, and one can then have multiple parallel channels, which means that even if the ft601 is busy sending the packets for one of the channels, it might accept new data on one of the other channels and thus decreasing the number of cycles we are not sending anything
|
| 11:41 | anuejn | but we are not shure if it is worth the labour to put into that performance optimization
|
| 11:41 | anuejn | even if we would get like 380 Mb/s that is not much more and probably quite some additional work
|
| 11:42 | se6ast1an | I see
|
| 11:42 | se6ast1an | sustainable 360MB/s is indeed a very good value for one plugin module
|
| 11:43 | se6ast1an | which we could double by using 2
|
| 11:45 | anuejn | ok so it would be sufficient for doing 16:9 4k 12bit 24fps (which is 339.7386 megabyte/s)
|
| 11:45 | anuejn | so i think it is not worth the additional time investment
|
| 12:00 | se6ast1an | agreed
|
| 12:01 | se6ast1an | what steps are required to actually get video data to/from the usb3 plugin module?
|
| 12:01 | se6ast1an | I assume it require zynq gateware changes as well
|
| 12:02 | mumptai | joined the channel |
| 12:41 | anuejn | probably
|
| 12:41 | anuejn | and a working usb3 plugin
|
| 12:41 | anuejn | and some gataware on the machxo
|
| 13:06 | Dest123 | left the channel |
| 13:35 | danieeel | changed nick to: danieel
|
| 13:38 | anuejn | ft60x-rs should be usable now :)
|
| 13:38 | anuejn | https://github.com/apertus-open-source-cinema/ft60x-rs
|
| 13:39 | se6ast1an | great!
|
| 13:45 | Bertl_zZ | changed nick to: Bertl
|
| 13:45 | Bertl | morning folks!
|
| 13:48 | se6ast1an | good day!
|
| 13:52 | anuejn | morning :)
|
| 14:02 | Dest123 | joined the channel |
| 14:36 | Dest123 | left the channel |
| 16:23 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 18:54 | Bertl | off for now ... bbl
|
| 18:54 | Bertl | changed nick to: Bertl_oO
|
| 19:29 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 19:57 | illwieckz | left the channel |
| 19:58 | illwieckz | joined the channel |
| 21:32 | Dest123 | joined the channel |
| 21:49 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 22:32 | Dest123 | left the channel |
| 23:29 | mumptai | left the channel |