Saturday, 2019-08-03

*** tpb has joined #litex00:00
*** somlo has joined #litex03:15
*** daveshah has quit IRC09:53
*** daveshah has joined #litex10:08
*** ambro718 has joined #litex11:41
*** ambro718 has quit IRC13:31
*** ambro718 has joined #litex13:56
CarlFKmithro: hdmi2usb listens on port 20 (telnet) right ?21:22
mithroCarlFK: You mean the firmware on the opsis / atlys?21:25
mithroTelnet is generally 2321:25
CarlFKwhoops, - ok 2321:26
*** tumbleweed has joined #litex21:26
CarlFKmithro: does the firmware have enough plumbing so that port 80 send/receive json or something of that nature21:27
mithroCarlFK: Kinda - it would be non-trivial but doable21:27
mithroCarlFK: your better of starting with hdmi2usbd21:28
CarlFKmithro: is the firmware is collecting debug stats even when it isn't displaying them ?21:35
*** ambro718 has quit IRC21:37
mithroCarlFK: unclear, for some yes...21:38
CarlFKmithro: the thought is:  step 1: get port 80 to respond.. step 2: send "get /v1/stats/everything" and get back the state of everything, and reset the error counters.  so a .js in a browser can pole that every second21:43
CarlFK"get /v1/..." might be validated for that string21:44
mithroDo it with hdmi2usbd then people can develop without hardware21:45
CarlFKstep 3 is "get or post /v1/cmd/ connect input0 output1"21:45
mithroOr even just write up a python web server that does that21:46
CarlFKI'm trying to avoid interfering with the current setup21:46
mithroGet a the GUI stuff going and then someone will have the incentive to do the hardware side21:47
mithroJust use a fake server first21:48
CarlFKI have a long time chicago python friend say "I just did something like that.  I'll help you with the .js side"21:49
mithroThe .js side being?21:49
CarlFKthe UI in a browser21:50
CarlFKwhich is kinda in my grasp, but I would rather work with someone who is good at it21:50
mithroSo, make him a fake python http server with the json endpoints for him to work against21:51
CarlFKthat's a bit of work that will get thrown out21:51
mithroHe can then start the UI stuff before the firmware on the server even works21:52
mithroThe python server is like couple of hours of work that you don't need my help with21:53
tumbleweedit's a bit of work that will continue to be useful for UI development21:53
mithroThe C firmware side would take me a couple of days at a minimum21:53
CarlFKyeiks - full 8 hour days?21:54
CarlFKI was going to bug Ben H to help me make it respond 200 OK and then see how much I could do21:55
mithroC is not an easy language to work on, bare metal C is even worse21:55
CarlFKthis assumed I can figure out how to build21:55
mithroIf you had the GUI working and it looked good, then I'm sure someone would do the C side21:56
CarlFKmithro: that would be me - but I'll be bugging you about building21:57
CarlFKmaybe flashing too.  I think my pi is still the only thing I have that I have any confidence in21:57
mithroYou need that too work reliably if you want to do development21:58
mithroSo, go write the Python fake, unblock your friend and then come back to this21:59
CarlFKmithro: is there a file that enumerates? all the states?  (I think those are the words I want)22:01
CarlFK  in here right ?22:02
tpbTitle: HDMI2USB-litex-firmware/firmware at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
CarlFKthese 2 blocks are alarmingly  similar:22:04
tpbTitle: HDMI2USB-litex-firmware/ci.c at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
tpbTitle: HDMI2USB-litex-firmware/ci.c at master · timvideos/HDMI2USB-litex-firmware · GitHub (at

Generated by 2.13.1 by Marius Gedminas - find it at!