Sunday, 2018-03-04

*** tpb has joined #timvideos00:00
mithrohttp://www.garbers.co.za/2017/11/01/code-folding-and-timing-in-travis-ci/01:27
tpbTitle: Code folding and timing in Travis CI (at www.garbers.co.za)01:27
*** futarisIRCcloud has joined #timvideos02:25
*** CarlFK1 has quit IRC03:55
*** futarisIRCcloud has quit IRC04:35
*** hyadez has quit IRC05:47
*** CarlFK has joined #timvideos06:08
*** ChanServ sets mode: +v CarlFK06:08
*** hyadez has joined #timvideos08:43
*** rohitksingh has joined #timvideos09:09
*** rohitksingh has quit IRC09:48
*** rohitksingh has joined #timvideos09:57
*** rohitksingh has quit IRC10:24
*** futarisIRCcloud has joined #timvideos12:30
*** futarisIRCcloud has quit IRC14:40
*** shivm has joined #timvideos16:21
*** suhdood has joined #timvideos17:15
*** shivm has quit IRC18:00
*** suhdood has quit IRC18:37
*** suhdood has joined #timvideos18:37
*** suhdood has joined #timvideos18:38
CarlFK[m]mithro (IRC): https://github.com/enjoy-digital/litevideo/commit/18b88dfee6bf6f4ab55d196747ca00c6c84c2ef219:11
tpbTitle: input/edid: fix scl polarity · enjoy-digital/[email protected] · GitHub (at github.com)19:11
CarlFK[m]jea: bring out the NUC19:12
*** suhdood has quit IRC19:34
*** suhdood has joined #timvideos19:35
felix[m]1Hi y'all! I'm mucking around in your project internals (trying to figure out how things work, being new to all of this): Is there a way to toggle the configuration flags, so that the input/output is enabled automatically on startup? I can see the flags in https://github.com/timvideos/HDMI2USB-litex-firmware/blob/ab27f574f07a1cf5693a6da0da7bd93b7817c7b8/firmware/config.h (I think), but I can't figure out how to set them.20:15
felix[m]1Any hints are very much appreciated. Thanks!20:15
tpbTitle: HDMI2USB-litex-firmware/config.h at ab27f574f07a1cf5693a6da0da7bd93b7817c7b8 · timvideos/HDMI2USB-litex-firmware · GitHub (at github.com)20:15
mithrofelix[m]1: You can change the values here -> https://github.com/timvideos/HDMI2USB-litex-firmware/blob/ab27f574f07a1cf5693a6da0da7bd93b7817c7b8/firmware/config.c#L34-L5720:16
tpbTitle: HDMI2USB-litex-firmware/config.c at ab27f574f07a1cf5693a6da0da7bd93b7817c7b8 · timvideos/HDMI2USB-litex-firmware · GitHub (at github.com)20:16
mithrofelix[m]1: But they are currently hard coded into the firmware20:16
mithrocr1901_modern: ping?20:16
felix[m]1mithro: Thanks a lot! I'll give that a shot (my C is quite rusty to say the least, but I'm, slowly understanding liteX and loving it!)20:17
cr1901_modernmithro: pong20:18
felix[m]1Do you manually set up boards when you do recordings?20:18
mithrocr1901_modern: Would you be able to add support reading and writing those values from the spi flash?20:19
cr1901_modernmithro: Sure, but before I do that, could we go ahead and merge my previous SPI flash changes (which also currently has some conflicts)?20:21
cr1901_modernmithro: I need a software program which prints out my yak-stack :P20:21
cr1901_modernin tree format20:21
cr1901_modernHmmm, I guess this feature doesn't depend on the SPI flash write code20:23
mithrocr1901_modern: Hrm?20:24
cr1901_modernmithro: I was just thinking I wanted my prev code working on the SPI flash committed before I begin working on other things related to SPI flash >>20:24
mithrocr1901_modern: Well the idea would be to allow writing the config values to spiflash20:25
cr1901_modernBut now that I think about it, I'm not sure "reading out config" is all that related to "adding infrastructure to bitbang flash"20:25
cr1901_modernoh, so you just want me to add that functionality on top of the current PR?20:25
mithrocr1901_modern: I think so20:26
cr1901_modernYea sure I can do that :)20:26
mithrocr1901_modern: You said you had litex-buildenv working with the updated litex which uses migen? I assume that wasn't updating the scripts and stuff?20:32
felix[m]1You people are way awesome :-) . Thanks for your efforts, and sorry for the trouble! I'd be glad to help with this if I can (though I'm only slowly finding my way around how things work, and it's probably going to be a while until I can do something useful, but I'd be glad to help testing)20:32
cr1901_modernmithro: No I updated the scripts20:41
mithrocr1901_modern: Pull request please! :-P20:41
cr1901_modernmithro: Please wait 5 mins20:42
*** suhdood has quit IRC20:48
*** cr1901_modern has quit IRC20:59
*** CarlFK has quit IRC21:01
*** cr1901_modern has joined #timvideos21:20
cr1901_modernWell that was fun. Laptop decided to go out to lunch21:21
cr1901_modernmithro: https://github.com/timvideos/litex-buildenv/pull/2721:28
tpbTitle: Merge in LiteX changes by cr1901 · Pull Request #27 · timvideos/litex-buildenv · GitHub (at github.com)21:28
cr1901_modernI tested this against the Arty platform on Linux, and also the mimasv2 platform on Windows21:29
cr1901_modernNext step is to do the same for HDMI2USB I presume?21:32
cr1901_modernmithro: Do these patches https://github.com/timvideos/conda-hdmi2usb-packages correspond to this channel? https://anaconda.org/timvideos/repo?type=conda&label=main21:44
tpbTitle: GitHub - timvideos/conda-hdmi2usb-packages: Conda build recipes for the toolchains needed by LiteX / MiSoC firmware (at github.com)21:44
cr1901_modernIf so I have a PR for openocd since they're glacial at accepting changes21:44
mithroYeah - give me an hour to do something with your pull request21:45
cr1901_modern(well, two PRs, if you can live with the second patch potentially diverging/having changes requested when I submit it upstream)21:45
mithroyes, please do21:45
cr1901_modernIs the second PR acceptable w/ the caveat? (arty s7 board file)21:45
cr1901_modernActually, it should be. As I recall, you cancelled your upstream PR for Arty A7. I'll just submit both.21:46
mithrocr1901_modern: There was already an open PR for the Arty A721:55
cr1901_modernmithro: I understand. But considering the open PR has been open SINCE June, and the devs are STILL req changes, I imagine that if I submit a PR to your conda repo it won't look the same as what gets committed to upstream.22:02
mithrocr1901_modern: That was amore an answer about they I closed the openocd pull request22:02
cr1901_modernAhh fair22:02
cr1901_modernBut still, they are _glacial_ at getting changes in it seems :(22:02
*** techman83 has quit IRC22:03
*** techman83 has joined #timvideos22:04
*** ChanServ sets mode: +v techman8322:04
CarlFK[m](02:15:29 PM) felix: Do you manually set up boards when you do recordings?22:11
* cr1901_modern is currently cleaning up all his remote repos and branches in bulk22:12
cr1901_modernGood lord I have a lot of them22:12
CarlFK[m]felix - once we have somewhat current firmware flashed, we use the defaults22:14
CarlFK[m]so we manually flash, but generally they power up in the state we want them22:14
CarlFK[m]there are exceptions, like "we really need 1024x768, so lets do that for this one talk, and then reset back to 720p"22:15
felix[m]1Ah, that makes total sense! Thanks22:16
*** CarlFK has joined #timvideos22:25
*** ChanServ sets mode: +v CarlFK22:25
mithrocr1901_modern: I reworked your pull request a little bit - just waiting for travis to confirm if things are all good22:30
cr1901_modernmithro: Sure, I understand. For some reason travis didn't start doing a build when I submitted my PR22:31
mithrocr1901_modern: Because it wasn't setup on litex-buildenv22:32
cr1901_modernAhhh, looks like you squashed my commits?22:34
mithrocr1901_modern: I used the "merge-upstream.sh" script to get a nicer commit message22:34
cr1901_modernAhhh I see, cool22:35
cr1901_moderngit log --oneline whatever is pretty amazing22:35
cr1901_modernI'm using it right now to clean up literally dozens of branches22:35
cr1901_modernHow do you know travis is building? I still don't see a marker saying it's doing a build on the PR22:36
mithrohttps://github.com/timvideos/HDMI2USB-litex-firmware/pull/41522:39
tpbTitle: WIP: Update to new LiteX by mithro · Pull Request #415 · timvideos/HDMI2USB-litex-firmware · GitHub (at github.com)22:39
cr1901_modernI'm... not gonna ask how you cherry-picked my commits across repositories22:40
cr1901_modernBad enough you've made me a git intermediate :P22:40
mithrocr1901_modern: Looks like need to update the cut back vivado for your update -> https://travis-ci.org/mithro/HDMI2USB-litex-firmware23:33
mithrocr1901_modern: https://travis-ci.org/mithro/HDMI2USB-litex-firmware/builds/34906078323:34
cr1901_modernGreeeeat23:41
cr1901_modernmithro: I have no idea what this means https://travis-ci.org/mithro/HDMI2USB-litex-firmware/jobs/349060784#L580523:42
mithrocr1901_modern: It means that the cut-back version of vivado we use on travis is missing something that is needed23:42
cr1901_modernmithro: This is unfortunately a case of "works on my machine". I don't know why updating a single path would cause Vivado to bomb like that. Especially since only LiteX should ever see the path changes23:45
mithrocr1901_modern: I'm guessing that migen is using a slightly different set of tcl method calls then litex was previously23:46
cr1901_modernmithro: I'm taking a look23:50
mithrocr1901_modern: I know how to fix it23:50
cr1901_modernmithro: Oh, then could you fix it for me :P?23:50
*** futarisIRCcloud has joined #timvideos23:54
mithrocr1901_modern: Yes - but it will take a while23:58
cr1901_modernmithro: Define "a while". Days? Hours?23:59

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!