Saturday, 2018-10-27

*** tpb has joined #timvideos00:00
*** tactics__ has quit IRC01:54
*** futarisIRCcloud has joined #timvideos02:08
nrossimithro: if you are still around. Managed to get Vivado to install and vivado --help run entirely within the OE build. However it does have the draw back of being copied once (to store it in sstate). Have not had a chance to test ISE though03:02
mithronrossi: Is there a way to "provide" vivido as part of the host/building system? I think RP had a suggestion?03:24
nrossimithro: yes there are a couple of ways, probably the most effective is to have a recipe that provides some wrapper scripts in the recipe sysroot that just source the xilinx tools and call the associated executables03:36
mithronrossi: That actually sounds reasonable pleasant because it seems like you could have *either* it is installed in the sysroot via your method above **or** you provide the fake wrappers which shell out to your host?03:56
mithroshorne: I see you just pushed a "OpenRISC GCC Toolchain 9.0.0-20181026" ?03:57
nrossimithro: yep exactly, and you can select which one using a PREFERRED_PROVIDER setting03:57
mithroThat is "interesting"  -- Release: GCC 6.5Release date: October 26, 201803:58
mithroIs GCC 6.5 a "long term supported" release or something?03:59
nrossimithro: isn't 6.5 the last of the 6.x tree? https://gcc.gnu.org/ml/gcc/2018-10/msg00221.html04:00
tpbTitle: Jakub Jelinek - GCC 6.5 Released (at gcc.gnu.org)04:00
mithronrossi: That is what I mean, is the GCC 6.x tree special in some way?04:00
mithroOh interesting - "This is also the last release from the GCC 6 branch"04:02
mithronrossi: I'm very interested in see if you put together all the stuff you have done, does is actually create something similar to litex-buildenv but "better"04:08
futarisIRCcloudnrossi: Me too. Where is your OE stuff?04:09
nrossimithro: the xilinx tools stuff is just wip commits on the meta-hdl "wip" branch https://github.com/nathanrossi/meta-hdl/tree/wip04:13
tpbTitle: GitHub - nathanrossi/meta-hdl at wip (at github.com)04:13
nrossiand the openrisc changes are on a oe-core branch here: https://github.com/nathanrossi/openembedded-core/tree/nrossi/or1k (i plan to submit some of that upstream after oe-core does their imminent release)04:15
tpbTitle: GitHub - nathanrossi/openembedded-core at nrossi/or1k (at github.com)04:15
*** Kripton has quit IRC04:52
*** Kripton has joined #timvideos04:54
mithronrossi: Could we maybe put a "burn down" or similar type of "thing needed to still be done" list in the doc at https://docs.google.com/document/d/1hBvcE83vDRn5EVzcv4Qv_dcGlDuXp5pNI-_yzrEOwxs/edit ? -- I'm a bit unsure about how close / far away we are from being able to replicate litex-buildenv style functionality.....05:18
tpbTitle: Google Docs - create and edit documents online, for free. (at docs.google.com)05:18
nrossimithro: sure, but out of query is the desire to have it capable of building the HDMI2USB project at first?05:20
mithronrossi: The first targets would be - HDMI2USB firmware, Linux, bare metal MicroPython (and maybe Zephyr)05:21
mithronrossi: The order isn't all that important I guess?05:21
nrossimithro: no not really, just want to make sure I have something to target :)05:22
mithroMicroPython is kind of my current focus05:22
mithroAnd it does have the advantage of being able to be small enough to sensibly usable on the iCE40 devices which have the open toolchain while also working on the "big" boards too05:23
mithronrossi: Did I share https://github.com/timvideos/litex-buildenv/wiki/HowTo-FuPy-on-a-Digilent-Arty-A7 ?05:23
tpbTitle: HowTo FuPy on a Digilent Arty A7 · timvideos/litex-buildenv Wiki · GitHub (at github.com)05:23
mithronrossi: So maybe it makes sense to target the MicroPython initially?05:24
nrossimithro: sure i will target that first05:24
mithronrossi: FYI - If it turns out that doing things this way with Yocto / OE works well enough that I can throw away conda+crappy shell scripts and do more actual interesting FPGA work, then I will owe you big time!05:27
nrossimithro: :) we will see05:27
cr1901_modernnrossi: Does yocto/openembedded build on Windoze?05:28
nrossicr1901_modern (IRC): it can target mingw. But for building on windows no. WSL though i believe has had some success05:28
cr1901_modernHrm, that's prob gonna be an issue. The conda situation isn't great, but with the present setup it's possible to use litex-buildenv under an MSYS2 environment05:29
cr1901_modernif you're careful*05:30
mithronrossi: What is the difference between "building" and "targeting" ? Do you mean you could build an SDK package which lets someone do "development" on windows, but not build the whole thing?05:30
nrossimithro: yer, so you can get it to build the tools (gcc, qemu, iverilog, yosys, etc) that will run on windows. But running bitbake/OE/yocto itself on windows is just in general a no go05:31
cr1901_modernmithro: That's actually fine. I think the idea was to try to use travis for all deps nyway.05:32
nrossiAlso as soon as you want to build things like the Linux kernel your just gonna have a bad time trying to do that one windows05:32
cr1901_modernbuild linux on Windows is most certainly not supported right now as-is anyway05:32
cr1901_modernit _may_ be possible from an msys2 prompt05:32
nrossisure, but if thats a future goal to support with litex then you are likely unable to support that for windows05:33
nrossialso, whilst you might be able to build the kernel, building the rootfs and programs will prove challenging ;)05:34
mithronrossi: qemu all the say! :-P05:35
mithros/say/way/05:35
mithronrossi: What about Mac?05:35
cr1901_modernAs long as one can _use_ litex-buildenv from Windows after the switch to yocto, then I don't really have a problem with building all the deps on linux/travis05:36
nrossimithro: same a windows, and likely in a broken state as it is not well supported by yocto (meta-darwin)05:36
mithroWe don't support Mac *at all* at the moment05:36
nrossimithro: well, it is something that could be improved, there are other users out there that have asked about macos support with yocto05:38
mithronrossi: Someone was playing with the idea of using wine to run ISE / Vivado on Mac -- I think they got it to install and compile stuff but never got around to integrating it into the build environment...05:39
nrossimithro: interesting, although i imagine that it would be more functional to build open tools for macos no?05:40
mithroYes :-)05:40
mithroIt was more impressive just from actually making it do something other than just segfault (segfaulting seems to be the natural state for vendor released toolchains ;-)05:42
nrossicr1901_modern (IRC): just for curiosity, your reason for using windows, choice? or work enforced?05:42
cr1901_modernchoice05:42
nrossimithro: yes, even on the supported distros apparently :)05:42
*** rohitksingh has joined #timvideos05:57
*** mcarden_ has quit IRC06:07
*** mcarden has joined #timvideos06:07
*** rohitksingh has quit IRC06:11
nrossimithro: added a table to the doc for the lite-buildenv components and the state for it in OE06:13
*** rohitksingh has joined #timvideos06:24
*** rohitksingh has quit IRC06:34
*** rqou has quit IRC06:39
*** rqou has joined #timvideos06:39
*** futarisIRCcloud has quit IRC06:57
*** futarisIRCcloud has joined #timvideos07:21
*** rohitksingh has joined #timvideos07:22
*** rohitksingh has quit IRC08:30
*** futarisIRCcloud has quit IRC09:37
*** rohitksingh has joined #timvideos10:53
*** rohitksingh has quit IRC11:08
*** mauz555 has joined #timvideos11:27
*** mauz555 has quit IRC14:52
*** mauz555 has joined #timvideos14:53
*** mauz555_ has joined #timvideos15:02
*** mauz555 has quit IRC15:03
*** mauz555 has joined #timvideos15:09
*** mauz555_ has quit IRC15:11
*** rohitksingh has joined #timvideos15:35
*** rohitksingh has quit IRC15:53
*** rohitksingh has joined #timvideos16:00
rohitksinghcr1901_modern: looks like your patches in OpenOCD have been merged now! :)16:10
cr1901_modernrohitksingh: Holy smokes, so they are :o...16:13
*** rohitksingh has quit IRC16:13
*** rohitksingh1 has joined #timvideos16:13
*** rohitksingh1 has joined #timvideos17:11
*** rohitksingh1 has quit IRC17:14
*** rohitksingh has joined #timvideos17:15
*** rohitksingh has quit IRC17:17
*** rohitksingh has joined #timvideos17:17
*** rohitksingh1 has joined #timvideos17:21
*** rohitksingh has joined #timvideos17:28
*** rohitksingh1 has quit IRC17:33
*** mauz555 has quit IRC17:37
*** rohitksingh has quit IRC17:48
*** rohitksingh has joined #timvideos17:51
*** rohitksingh has quit IRC17:56
*** rohitksingh has joined #timvideos17:56
*** rohitksingh has quit IRC18:26
*** rohitksingh has joined #timvideos18:28
*** Kripton has quit IRC18:47
*** Kripton has joined #timvideos18:57
*** tpb has joined #timvideos19:35
mithronrossi: Thanks!19:49
*** rohitksingh has joined #timvideos19:52
*** rohitksingh has quit IRC20:41
CarlFKmithro: you wrote this for me in .. 2012 or something: https://github.com/CarlFK/veyepar/blob/master/dj/scripts/fixunicode.py21:06
tpbTitle: veyepar/fixunicode.py at master · CarlFK/veyepar · GitHub (at github.com)21:06
CarlFKin #positivepython  techalchemy: wow that is super awesome, mind if i swipe it?21:07
CarlFKme: yes21:07
CarlFKhere to pass on the thanks21:07
mithroCarlFK: Ha - I'm not sure I actually wrote that...21:08
mithroCarlFK: https://github.com/CarlFK/veyepar/commit/dc33c66bb154501988ed72ee32a920e8feebb83521:09
tpbTitle: Making fixunicode more robust and also fix stderr. · CarlFK/[email protected] · GitHub (at github.com)21:09
CarlFK2014 - close enough21:09
mithroCarlFK: https://github.com/CarlFK/veyepar/commit/d38e4c6cc379697d2607dfe3fae69fa44fe105e4#diff-2031d030bedffc622b376f32b4fd0151 -- looks like that came from you?21:09
tpbTitle: print unicode chars out to term · CarlFK/[email protected] · GitHub (at github.com)21:09
mithroI just cleaned it up21:10
CarlFKI'm guessing you wrote it and I commited it21:10
mithroCarlFK: I think it came from https://github.com/mithro/rcfiles/commits/master/python/force_unicode.py ?21:11
tpbTitle: History for python/force_unicode.py - mithro/rcfiles · GitHub (at github.com)21:11
CarlFKthat explains how you wrote it as fast as you did ;)21:12
cr1901_modernhttps://github.com/enjoy-digital/litex/issues/117#issuecomment-433655547 Huh... is the SPI flash core really that small...21:18
cr1901_moderneven a minimal UART is like 100 LUTs21:18
*** sc00bz1 has quit IRC23:09
*** sc00bz has joined #timvideos23:14

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