| *** tpb <[email protected]> has joined #litex | 00:00 | |
| *** slagernate <[email protected]> has joined #litex | 00:16 | |
| *** Emantor <[email protected]> has quit IRC (Quit: ZNC - http://znc.in) | 01:20 | |
| *** Emantor <[email protected]> has joined #litex | 01:21 | |
| *** nelgau <[email protected]> has quit IRC () | 01:45 | |
| *** nelgau <[email protected]> has joined #litex | 01:55 | |
| *** nelgau <[email protected]> has quit IRC () | 03:07 | |
| *** nelgau <[email protected]> has joined #litex | 03:08 | |
| *** Degi <[email protected]> has quit IRC (Ping timeout: 250 seconds) | 03:53 | |
| *** Degi <[email protected]> has joined #litex | 03:55 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 05:42 | |
| *** TMM_ <[email protected]> has joined #litex | 05:43 | |
| *** slagernate <[email protected]> has quit IRC (Ping timeout: 252 seconds) | 06:12 | |
| *** Brinx <[email protected]> has joined #litex | 07:41 | |
| *** MoeIcenowy <[email protected]> has quit IRC (Ping timeout: 265 seconds) | 07:59 | |
| *** MoeIcenowy <MoeIcenowy!~MoeIcenow@2001:19f0:6001:1697:e4bb:508c:a443:348a> has joined #litex | 08:04 | |
| *** Brinx <[email protected]> has quit IRC (Remote host closed the connection) | 08:08 | |
| *** Brinx <[email protected]> has joined #litex | 08:09 | |
| *** Brinx <[email protected]> has quit IRC (Ping timeout: 268 seconds) | 08:14 | |
| *** Brinx <[email protected]> has joined #litex | 08:41 | |
| *** Brinx <[email protected]> has quit IRC (Remote host closed the connection) | 09:02 | |
| *** Brinx <[email protected]> has joined #litex | 09:02 | |
| *** Brinx <[email protected]> has quit IRC (Ping timeout: 264 seconds) | 09:07 | |
| *** Brinx_ <[email protected]> has joined #litex | 09:07 | |
| *** Brinx_ <[email protected]> has quit IRC (Remote host closed the connection) | 09:54 | |
| *** Brinx <[email protected]> has joined #litex | 09:54 | |
| *** _franck_4 <[email protected]> has quit IRC (Read error: Connection reset by peer) | 09:58 | |
| *** _franck_4 <[email protected]> has joined #litex | 09:58 | |
| *** Brinx <[email protected]> has quit IRC (Ping timeout: 260 seconds) | 09:59 | |
| *** DoubleJ2 <DoubleJ2!~DoubleJ@user/doublej> has joined #litex | 12:49 | |
| *** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has quit IRC (Ping timeout: 268 seconds) | 12:52 | |
| *** DoubleJ2 is now known as DoubleJ | 12:52 | |
| *** Brinx <[email protected]> has joined #litex | 13:06 | |
| *** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has quit IRC (Quit: Not all those who wander are lost) | 13:40 | |
| *** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has joined #litex | 13:45 | |
| *** Brinx <[email protected]> has quit IRC (Remote host closed the connection) | 15:40 | |
| *** Brinx <[email protected]> has joined #litex | 15:41 | |
| *** Brinx <[email protected]> has quit IRC (Ping timeout: 250 seconds) | 15:45 | |
| tpw_rules | does dolu1990 have an irc nick? | 18:34 |
|---|---|---|
| tnt | he's not on irc AFAIK | 18:37 |
| tpw_rules | ah. is there a good way to contact him? wanted to talk about handling of the pythondata repos. might just send a PR if there's not | 18:41 |
| tnt | There is a gitter https://gitter.im/SpinalHDL/VexRiscv | 18:43 |
| tpb | Title: SpinalHDL/VexRiscv - Gitter (at gitter.im) | 18:43 |
| tpw_rules | actually this might be a question more for mithro | 18:44 |
| *** pbsds <[email protected]> has joined #litex | 18:46 | |
| *** coco3431 <coco3431!~coco3431@69-215-128-137.lightspeed.cicril.sbcglobal.net> has joined #litex | 18:47 | |
| tpw_rules | mithro: i think it would be good if the pythondata concept had scope for additional code with the repo, or we did something else for the CPUs which are generated | 18:49 |
| tpw_rules | it's pretty inconvenient to have the driver code which converts the cpu request to a generator invocation as a part of litex itself and some CPUs also do additional setup and downloads prior to generation which makes tracking versions complicated | 18:49 |
| mithro | I would just send a PR. | 18:51 |
| mithro | tpw_rules: it would be great if the pythondata repos handled generated CPUs better | 18:51 |
| mithro | tpw_rules: I just never got around to doing the "run command between git pull and git commit + push" bit | 18:52 |
| tpw_rules | minerva sort of does what i want where the options are directly passed to code in the pythondata repo but it's done by shelling out to another python | 18:52 |
| tpw_rules | in my mind there would be a little more intelligence so you can call a function directly on the data module to do that, or maybe query it for some option descriptions | 18:54 |
| tpw_rules | but that doesn't fit the template or "just run a command" model | 18:54 |
| mithro | tpw_rules: the complete code is at https://github.com/litex-hub/pythondata-auto/blob/master/update.py | 18:54 |
| tpw_rules | and that sort of code doesn't quite belong in litex because it's cpu specific and cpu isolated and not dependent on litex, and it doesn't quite belong upstream for a lot of the cpus because they are used in other applications or not python themselves | 18:55 |
| mithro | tpw_rules: the code was almost completely written while I was avoiding doing something more important | 18:56 |
| tpw_rules | maybe i'm reading more into some grand plan than there really is :) i have a bad habit of that | 18:56 |
| tpw_rules | let's try again more directly | 18:57 |
| tpw_rules | from what i get from issues and glancing at the code, your pythondata-auto tool wants to completely control the content of the pythondata repos and generate them from scratch using that .ini. but there are good reasons imo to add more stuff to them. how should that be done | 18:58 |
| mithro | tpw_rules: the pythondata-auto already copies files from the template | 19:00 |
| tpw_rules | maybe this is something to push upstream, but most of the CPUs don't have a working build command anyway without code from litex | 19:00 |
| mithro | tpw_rules: no reason it couldn't also pull extra stuff from another repo or something | 19:00 |
| tpw_rules | i was more thinking a semi-automatic approach where there's some script to generate the initial layout and separate ongoing maintenance to merge upstream code/update submodules, run build commands, and update the __init__.py metadata. then glue code would be subject to the normal PR process and ideally change relatively infrequently | 19:03 |
| tpw_rules | having an additional pythondata-specific source repo seems complex to me | 19:04 |
| tpw_rules | (that actually raises the question, why are the commits copied instead of using submodules?) | 19:05 |
| mithro | I would say we want to keep the modules updating as quickly as the upstream, so that prevents manual intervention. | 19:05 |
| tpw_rules | you wouldn't need to manually intervene to keep upstream updating though | 19:06 |
| tpw_rules | that ongoing maintenance i mention would be fully automatic. we would just have to think a bit about what parts of the repo the bot and humans should touch | 19:07 |
| mithro | The main reason for not having humans touch the output is the version number issue | 19:08 |
| mithro | The current version numbers are the sum of the source and pythondata-auto | 19:09 |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 19:10 | |
| *** TMM_ <[email protected]> has joined #litex | 19:10 | |
| mithro | Version number needs to keep going forward and incrementing for things like PyPi to work | 19:11 |
| tpw_rules | ah that makes sense | 19:14 |
| mithro | Versioning is hard | 19:15 |
| mithro | But I /think/ most stuff can either go upstream or in LiteX directly? | 19:17 |
| mithro | The only reason you might want glue code in the auto repos is that you want to share it between LiteX and a non-LiteX project? | 19:18 |
| tpw_rules | i mean the pythondata readme template sort of casts that as the default case | 19:37 |
| tpw_rules | more concretely i'm not sure how you would have the bot run a build command without introducing a circular dependency | 19:38 |
| *** pbsds <[email protected]> has quit IRC (Ping timeout: 265 seconds) | 20:09 | |
| *** coco3431 <coco3431!~coco3431@69-215-128-137.lightspeed.cicril.sbcglobal.net> has quit IRC (Quit: Client closed) | 20:09 | |
| *** pbsds <[email protected]> has joined #litex | 20:57 | |
| *** slagernate <[email protected]> has joined #litex | 21:02 | |
| *** slagernate <[email protected]> has quit IRC (Ping timeout: 252 seconds) | 21:21 | |
| *** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has quit IRC (Quit: Bye) | 23:46 | |
| *** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has joined #litex | 23:47 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!