| *** tpb <tpb!~supybot@underwood.mithis.com> has quit IRC | 01:00 | |
| *** tpb <tpb!~supybot@underwood.mithis.com> has joined #f4pga | 01:00 | |
| *** littlebo1eep <littlebo1eep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 01:23 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 01:24 | |
| *** littlebo1eep <littlebo1eep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 04:41 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 04:47 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 05:44 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 06:26 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 06:49 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 06:55 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 07:05 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 07:12 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 08:06 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 08:33 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 08:40 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 08:41 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 08:51 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 09:12 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 10:28 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 10:35 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 13:02 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 13:10 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 13:50 | |
| F4PGASlackBridge | <umartinezcorral> @gergo check https://github.com/hdl/packages. AFAIAA, at the moment there is no direct replacement for the whole Conda environment used in F4PGA examples. However, there is work in progress to achieve it. All "external" tools (yosys, vpr, nextpnr, etc.) are available through system package managers, through tarballs or as containers. Python utilities are being split from repo arch-defs (and moved to repo | 13:51 |
|---|---|---|
| F4PGASlackBridge | f4pga). With Python utilities moved away, the arch-defs-install tarballs should contain assets and TCL scripts only (need to double check). Last, yosys plugin are a separated repo. Note that during the last years and until very recently F4PGA did need specific variants of VPR, Yosys, etc. The upstreams would not work, so Conda was somehow required. Now, most of the tweaks are upstream, so other packaging/distribution | 13:51 |
| F4PGASlackBridge | solutions can step in. | 13:51 |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 13:51 | |
| *** adjtm <adjtm!~adjtm@53.red-83-56-237.dynamicip.rima-tde.net> has quit IRC | 15:23 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 15:38 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 15:45 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 15:53 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga | 16:34 | |
| lkcl | umartinezcorral: the libre-soc team runs with their own reproducible-build package-installation scripts that are public and publicly available | 16:39 |
| lkcl | the base-line chrooted repro OS is debian/10 | 16:39 |
| lkcl | https://git.libre-soc.org/?p=dev-env-setup.git;a=tree;hb=HEAD | 16:40 |
| tpb | Title: git.libre-soc.org Git - dev-env-setup.git/tree (at git.libre-soc.org) | 16:40 |
| lkcl | included is yosys ghdl iverilog symbiyosys nmigen symbiflow verilator nextpnr-ecp5 nextpnr-xilinx coriolis2 and most FPGA-loaders | 16:41 |
| lkcl | one of the very first things we did was exclude conda. it is... quite mad to have an installer that installs an installer that installs an installer | 16:41 |
| lkcl | docker -> conda -> pip3 -> package | 16:42 |
| lkcl | ! | 16:42 |
| lkcl | we solved the need for conda (before the upstreaming) through explicit package-installation within the chroot, using specific git checkouts. | 16:43 |
| lkcl | if ever you've tried working with docker, with its ever-changing specification file-format that results in utterly incompatible unreproducible builds, you'll understand and appreciate why we chose a debian/10 chroot :) | 16:44 |
| lkcl | feel free to add the link to dev-env-setup on https://github.com/hdl/packages | 16:45 |
| lkcl | with a note that our goal is *reproducible* stable builds that are still close to bleeding-edge | 16:46 |
| lkcl | and that we have had people use debootstrap even on archlinux to successfully install the (required) debian/10 schroots | 16:47 |
| lkcl | umartinezcorral: noticed that you list "awesome" quality as whether each tool/project has a markdown file, which we do, indeed, so i added a top-level README so that people can find them | 17:03 |
| lkcl | https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=README.mdwn;hb=HEAD | 17:03 |
| tpb | Title: git.libre-soc.org Git - dev-env-setup.git/blob - README.mdwn (at git.libre-soc.org) | 17:03 |
| mithro | acomodi: ping? | 17:54 |
| F4PGASlackBridge | <acomodi> mithro: pong | 18:35 |
| F4PGASlackBridge | <acomodi> I just saw some updates on the license server on GH | 18:36 |
| F4PGASlackBridge | <acomodi> Regarding the custom runners, commands do not actually require `sudo` | 18:38 |
| mithro | acomodi: Where are the customer runners actually running? | 20:16 |
| F4PGASlackBridge | <pgielda> @mithro Not sure if this is what you mean when you're asking, but eacg is run in a container on a separate dedicated machine in GCP (one machine per job, spinned by the coordinator and killed after the job) | 20:22 |
| mithro | @pgielda: Well more on which GCP project and such | 20:23 |
| F4PGASlackBridge | <pgielda> If you're more specifically asking which GCP project then we can probably discuss this outside of this channel | 20:24 |
| F4PGASlackBridge | <pgielda> (It depends which repo also, there is more than one project) | 20:25 |
| mithro | At the moment I mostly care about the prjxray | 20:27 |
| F4PGASlackBridge | <pgielda> This one I *think* is in the older one | 20:27 |
| F4PGASlackBridge | <pgielda> But I will check and confirm that on priv | 20:27 |
| F4PGASlackBridge | <pgielda> (Also will tell you the exact name of it) | 20:27 |
| mithro | acomodi / pgielda: I *think* I have put enough information into https://github.com/f4pga/prjxray/issues/1913 | 20:35 |
| F4PGASlackBridge | <pgielda> Ok. I am pretty sure we are filtering everything that is not needed for security reasons by default so obviously will have to think how to relax that in a smart way | 20:37 |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 21:04 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC | 21:12 | |
| F4PGASlackBridge | <umartinezcorral> @lkcl I understand your motivations. I do maintain https://hdl.github.io/containers/, which uses Debian Bullseye as the main "collection". There is also https://github.com/hdl/Termux-packages (Termux is essentially a debian chroot on Android). Hence, I see how the container approach can compare to using a Debian chroot (with regard to reproducibility and maintenance effort). May I know why you use "regular | 21:15 |
| F4PGASlackBridge | scripts" instead of deb recipes? In hdl/containers, things are starting to look like PKGBUILD recipes (e.g. https://github.com/hdl/containers/tree/main/debian-bullseye/pono) so I'm every once in a while thinking about switching to "proper" recipes. Using pacman on Debian feels weird, but I find deb cumbersome compared to PKGBUILD. Nevertheless, neither of "linux containers" or a Debian chroot fulfill one of the main | 21:15 |
| F4PGASlackBridge | requirements to choose Conda back when SymbiFlow was created: builds on multiple platforms (linux, windows and linux). Therefore, even though I do personally think that "having linux binaries only is acceptable", there is value for the community in having a solution which is significantly more popular in fields where knowledge about CS is not so important. On the other hand, both libre-soc's packages and hdl/containers do | 21:15 |
| F4PGASlackBridge | lack some of the individual tools used in F4PGA. In hdl/containers I do cheat by installing Conda inside a container; however, that's just a temporary solution to speed-up CI, until all the individual tools/utils are packaged. From a user point of view, the only "single command to install everything" for generating xc7 bitstreams using yosys and vpr is Conda (or Conda in a container). How does the default libre-soc flow | 21:15 |
| F4PGASlackBridge | compare to the ones currently supported in F4PGA? Is Coriolis2 equivalent to VPR or nextpnr in https://f4pga.readthedocs.io/en/latest/_images/parts.svg ? Or is it the main entrypoint which wraps other tools? Is FPGA synthesis supported in libre-soc flows or is it focused on ASICs? | 21:15 |
| F4PGASlackBridge | <umartinezcorral> Done. | 21:15 |
| F4PGASlackBridge | <umartinezcorral> I'm not sure to understand... Is that a reference to https://github.com/hdl/awesome ? In hdl/awesome, it is irrelevant whether a repo/tool has a top-level README. "Awesome list" is an existing concept that is used for listing resources for various topics/areas. The difference between hdl/awesome and other "awesome lists" is that each item in hdl/awesome is a markdown file | 21:15 |
| F4PGASlackBridge | (https://github.com/hdl/awesome/tree/develop/content/items), instead of having all the items written in a single markdown source. | 21:15 |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC | 22:03 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga | 22:03 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC | 22:41 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga | 22:43 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC | 22:44 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga | 22:44 | |
| *** indy <indy!~indy@dsl-static-104.213-160-167.telecom.sk> has quit IRC | 23:03 | |
| *** indy <indy!~indy@dsl-static-104.213-160-167.telecom.sk> has joined #f4pga | 23:07 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 23:32 | |
| lkcl | umartinezcorral: many of the dependencies aren't themselves debian packages. | 23:32 |
| lkcl | i've been following how debian operates since around 1994-5. | 23:32 |
| lkcl | for example, i think it was debian packaging of.... gitlab which uses both golang and node.js packages | 23:33 |
| lkcl | required something like an astounding *hundred+* dependent packages to be created before they could even get to the top-level gitlab | 23:34 |
| lkcl | and the reason is that it is absolutely completely unacceptable in debian to depend on insecure network installs such as "pip3 install {insert package}" | 23:35 |
| lkcl | every dependency *has* to be independently vetted, packaged, all copyright of all files checked and listed in a debian/copyright file. | 23:35 |
| lkcl | it's an astonishing amount of work | 23:35 |
| lkcl | or | 23:36 |
| lkcl | we could simply go with our own scripts, based (pretty much) on what everyone else has done already. | 23:36 |
| *** adjtm <adjtm!~adjtm@79.116.131.231> has joined #f4pga | 23:36 | |
| lkcl | the symbiflow ones were based on the instructions online, looking at the archlinux package as well, looking at the requirements.txt, extracting what was relevant (not installing risc-v compiler for example) | 23:38 |
| lkcl | > "I find deb cumbersome compared to PKGBUILD" | 23:38 |
| lkcl | yes, most people do, but once someone has done the work, you know that you won't get hit by a copyright lawsuit because of a missing copyright notice in one of the files | 23:39 |
| lkcl | and if you're operating in a country or a situation with an unreliable internet connection you can ask someone to send you a USB/DVD with debian packages, confident that every single dependency will be available, all GPG-signed and not tampered with | 23:40 |
| lkcl | > "both libre-soc's packages and hdl/containers do lack some of the individual tools used in F4PGA" | 23:41 |
| lkcl | our needs are quite focussed: if we need something else, it'll get added. if someone contributes it, i'll add it too. | 23:42 |
| lkcl | > "How does the default libre-soc flow compare to the ones currently supported in F4PGA?" | 23:43 |
| lkcl | i don't know because i've not installed F4PGA (and would be unlikely to do so, because i looked at conda, and went "no, not doing it") | 23:45 |
| lkcl | > " Is Coriolis2 equivalent to VPR or nextpnr in https://f4pga.readthedocs.io/en/latest/_images/parts.svg" | 23:45 |
| lkcl | no, coriolis2 is equivalent to (pretty much the entirety of) the piecemeal tools that comprise openlane | 23:46 |
| lkcl | it performs VLSI layout and has been tested on 360, 180 and 130 nm | 23:47 |
| lkcl | at up to 130,000 cells (around 800,000 transistors), fully-automated layout (ls180). | 23:47 |
| lkcl | > " Is FPGA synthesis supported in libre-soc flows or is it focused on ASICs?" | 23:51 |
| lkcl | both | 23:51 |
| lkcl | we're developing ASIC-ready HDL, using nmigen, and it needs to be run in simulators and also on FPGAs. | 23:51 |
| lkcl | ah ok, i didn't quite follow about the "awesome" list, i'd not seen it before :) | 23:51 |
| lkcl | nice idea. still, misunderstanding inspired me to write a README, heh | 23:53 |
| lkcl | > "builds on multiple platforms (linux, windows and linux)" | 23:57 |
| lkcl | yes, this is a good thing, for many reasons. | 23:58 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
