| *** tpb has joined #photonsdi | 00:00 | |
| *** Bertl_oO is now known as Bertl_zZ | 02:26 | |
| *** se6astian|away is now known as se6astian | 07:44 | |
| *** se6astian is now known as se6astian|away | 08:58 | |
| *** RexOrCine|away is now known as RexOrCine | 09:34 | |
| *** se6astian|away is now known as se6astian | 09:52 | |
| felix_ | hmm, either i'm doing something completely wrong or master of the non-public repo doesn't build with current litex/litevideo/lite* :/ | 11:50 |
|---|---|---|
| felix_ | "Unresolved clock domain: 'pix_o'" - the design doesn't have a clock domain with that name though | 11:57 |
| felix_ | _florent_: ^ | 11:57 |
| Kjetil | Inferred clock? | 12:21 |
| felix_ | _florent_: i tried to build the pcie-screamer-soc with current litex/lite* and got thos error "ERROR: [Common 17-54] The object 'project' does not have a property 'XPM_LIBRARIES'." | 12:35 |
| felix_ | i'm using vivado 2015.5 if that information is important here | 12:35 |
| felix_ | Kjetil: there is a clock domain pix, but i haven't looked at the clock domain management code in migen/litex | 12:36 |
| felix_ | _florent_: probably this patch broke things https://github.com/enjoy-digital/litex/commit/b8be9545cc9df790c1038b0b030f0058e0466095 at least that seems to be a plausible cause for the last bug | 12:46 |
| tpb | Title: build/xilinx/vivado: enable xpm libraries · enjoy-digital/litex@b8be954 · GitHub (at github.com) | 12:46 |
| _florent_ | felix_: i just fixed the axiom_sdi build | 14:51 |
| felix_ | thx | 14:52 |
| _florent_ | felix_: for the XPM_LIBRARIES, it's indeed maybe juste available after a specific version of Vivado, you can remove it or update Vivado :) | 14:52 |
| felix_ | ok | 14:52 |
| _florent_ | felix_: i would strongly recommend you to use latest vivado version, less bugs and faster | 14:53 |
| felix_ | on my new laptop i have the current version, but didn't get around to migrate all projects to it yet, so i'm currently still on my old laptop | 14:55 |
| *** se6astian is now known as se6astian|away | 17:38 | |
| felix_ | i've looked in the logs and the module b was the one without sdi output on the first output; i'll leave it here | 17:49 |
| *** RexOrCine is now known as RexOrCine|away | 17:50 | |
| felix_ | ah, ITU-R BT.2077-0 contains a description of the mapping of the crc bits: "CRCC0 is the MSB of the error detection code". the smpte standard didn't tell that... | 20:56 |
| felix_ | oh and funny thing is that the itu recommendation can just be downloaded from their site... | 20:57 |
| felix_ | https://www.itu.int/dms_pubrec/itu-r/rec/bt/R-REC-BT.2077-0-201506-S!!PDF-E.pdf (if anyone is interested in reading that) | 21:01 |
| Kjetil | The problem is that the SMPTE standards can't :P | 21:14 |
| felix_ | sci-hub to the rescue ;) | 21:21 |
| * felix_ doesn't really understand why those standards aren't publically available by default | 21:22 | |
| felix_ | it's a standard quite a few vendors use and it doesn't contain "security"-by-obscurity drm stuff | 21:24 |
| Kjetil | My guess it is to prevent outsiders from entering the broadcast space | 21:24 |
| felix_ | hm, might be. it's not a very effective prevention though | 21:29 |
| felix_ | .oO(let's make standards that are so bad that noone else will want to implement them) /o\ | 21:29 |
| *** se6astian|away is now known as se6astian | 21:35 | |
| Kjetil | hehe | 21:36 |
| Kjetil | And then you have secondary forums that will specify how to actually use the standards | 21:36 |
| felix_ | yep, exactly like that ;P | 21:37 |
| felix_ | best is though to make them slightly incompatible and then actually use the one with bad or nonexisting documentation. or maybe even add a few bugs to the real specification? *muhaha* | 21:38 |
| Kjetil | almost like Smpte 2110. They almost used RFC4175, but then they didn't | 21:40 |
| felix_ | *sigh* | 21:41 |
| Kjetil | They modified it to something incompatible, because of reasons.. | 21:43 |
| *** se6astian is now known as se6astian|away | 22:15 | |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!