Veera[m] | lkcl: Hi! I can't git push to libreriscv.git repo though pull is working | 07:57 |
---|---|---|
programmerjake | Veera: see https://lists.libre-soc.org/pipermail/libre-soc-dev/2022-March/004624.html | 08:06 |
programmerjake | sorry | 08:07 |
Veera[m] | programmerjake: read the msg can you renable my write access | 08:22 |
Veera[m] | oho | 08:22 |
programmerjake | sorry, i can't, luke is the only one with the access to change write access | 08:23 |
programmerjake | we'll have to wait for him | 08:23 |
Veera[m] | ok | 08:23 |
lkcl | Veera[m], programmerjake is taking responsibility for giving you the instructions needed. please ask him what you need to do. | 10:05 |
programmerjake | Veera: run `git branch --contains 3fda698000d39457eed8f5a17a2c6980958ceacb` | 10:10 |
programmerjake | if the output contains `master`, then we'll have to rebase your commits | 10:11 |
programmerjake | if it doesn't, then you should be fine | 10:12 |
Veera[m] | ran it does not contains 'master' | 10:13 |
programmerjake | what about `git branch --contains 1d17f24414c4b4e7ebf2d06d30c21f9938d60d09`? | 10:14 |
Veera[m] | ran. it says 'no such commit' | 10:15 |
programmerjake | ok, luke, please re-enable Veera's git access, his repo's fine | 10:15 |
programmerjake | lkcl: ^ | 10:16 |
lkcl | ok great. 1 se | 11:08 |
lkcl | Veera[m], programmerjake, done | 11:08 |
programmerjake | thx. sorry for the trouble. | 11:11 |
lkcl | i have 3 days in which to get FPGA demo running | 11:13 |
lkcl | i haven't even started on ethernet or spi flash | 11:13 |
lkcl | i've only just managed to get HyperRAM operational and only the lower 8 mbytes | 11:13 |
programmerjake | hmm...the ecp5 has enough block ram that you could probably have some kind of rtos in it that you could use as a router...no hyperram, ddr3, or spi flash needed...idk if that meets the requirements though | 11:17 |
lkcl | not in the slightest. | 11:18 |
lkcl | the project is to deliver a router product. that requires OpenWRT. | 11:18 |
lkcl | that in turn requires running a linux kernel | 11:19 |
programmerjake | k | 11:19 |
lkcl | with 2 months spent not being able to get DDR3 memory beyond Icarus Simulation i had to turn, in an emergency, to HyperRAM | 11:19 |
lkcl | ha, hilarious. i had all 32 MBytes accessible yesterday evening | 15:08 |
lkcl | but because i had written the test program to index by *words*, i thought "err there's 4x less *bytes* here" | 15:09 |
lkcl | doh | 15:09 |
zemaye_ | has the idea of continuous integration builds been brought up? I think a lot of the devscript stuff this weekend would have been caught by it | 18:28 |
markos | trying to follow the docs, https://libre-soc.org/openpower/sv/ldst/ | 18:54 |
markos | sv.ld 10.v, 0(in).v seems to be valid according to this | 18:54 |
markos | (where in is: .set in, 5) | 18:54 |
markos | but I'm getting a assembler Error: unrecognized opcode: `sv.ld'` | 18:57 |
markos | setvl seems to be recognized just fine and replaced by a .long equivalent | 18:57 |
markos | also, the tool seems to also replace even commented out #sv.* instructions | 18:59 |
markos | lkcl, ^ | 18:59 |
tplaten | I'm trying on the verilator backend, external_core_top.v is ignored for verilator builds, it is only used for FPGAs | 19:26 |
tplaten | I've pushed my changes to tplaten_3d_game, I get an error in 13. Executing Verilog backend. | 19:37 |
tplaten | ERROR: Non-constant enable $memwr$\memory$external_core_top.v:282587$25668_EN in memory initialization $meminit$\memory$external_core_top.v:282587$25707. (with fpga-target=verilator) | 19:38 |
tplaten | When building for the orangecrab, it takes much more time until I get the unconstrained in LPF error (6 minutes), so I first try to get libre-soc+microwatt peripherials working in verilator. | 20:13 |
tplaten | I had a look at the microwatt_verilator branch, it only supports EXTERNAL_CORE for fpga targets such as the ulx3s, for verilator you can only use the microwatt core, I was expecting you can use either core. | 20:16 |
lkcl | markos, yes anything prefixed "#sv.", the program's not hugely sophisticated. put "# # sv." i.e. some spaces in and it'll "go away". | 21:09 |
lkcl | https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=setup.py;h=e052d15bf78afe9f8ec350843a2079f8c9221b41;hb=6f6b52c92f0bfadce05a071a698a93ff4afd2b7c#l66 | 21:09 |
lkcl | line 66 | 21:09 |
lkcl | https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/sv/trans/svp64.py;h=65aa1768fc2cff1a615bbd27c33babdb1a96099b;hb=6f6b52c92f0bfadce05a071a698a93ff4afd2b7c#l1156 | 21:10 |
lkcl | there you go. | 21:10 |
lkcl | first identify anything starting "#" | 21:10 |
lkcl | ah spaces are not sufficient (due to the strip) | 21:11 |
lkcl | put "# commented out sv." | 21:11 |
lkcl | https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/sv/trans/svp64.py;h=65aa1768fc2cff1a615bbd27c33babdb1a96099b;hb=6f6b52c92f0bfadce05a071a698a93ff4afd2b7c#l1186 | 21:14 |
lkcl | line 1186 | 21:14 |
lkcl | 1185 'sv.stw 5.v, 4(1.v)', | 21:15 |
lkcl | 1186 'sv.ld 5.v, 4(1.v)', | 21:15 |
lkcl | those are examples of working syntax | 21:15 |
lkcl | and there are plenty more 1 sec | 21:15 |
lkcl | if i can find the damn things ) | 21:16 |
lkcl | :) | 21:16 |
lkcl | okaay here we go | 21:18 |
lkcl | https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/decoder/isa/test_caller_svp64_ldst.py;hb=HEAD | 21:18 |
programmerjake | zemaye_: yes, we had been working on getting CI working, but it stalled... i have a computer for CI sitting in my room basically all set up but luke wanted CI build logs to be available on a libre-soc mailing list or git or something, rather than only on debian salsa (the CI server is a gitlab runner configured to use debian salsa as the managing gitlab instance), we never finished getting it set up due to | 22:14 |
programmerjake | disagreements/misunderstandings on who needed to do what.... | 22:14 |
programmerjake | we've been working on other stuff and never got around to finishing getting it working | 22:15 |
lkcl | yeah there's nothing stopping you from going ahead and setting up CI, jacob | 23:07 |
lkcl | what i'm not going to do however is set up a mailing list on the libre-soc server that spews out tens to hundreds of thousands of lines of log files per run, overwhelming the Virtual Machine's 10 GB storage within months | 23:08 |
lkcl | (and i'm not prepared to pay more for it either) | 23:08 |
lkcl | that does not stop *you* from setting up mailman - or other mailing list - on the CI server | 23:08 |
lkcl | and i believe in the bugreport discussion it says - or should say - that i'm happy to do "redirection". | 23:09 |
lkcl | the CI machine is, i believe, already joined to the VPN running on libre-soc so it already has access to SMTP via 10.6.0.1. | 23:09 |
lkcl | storage of hundreds of [irrelevant] gigabytes of logs on your *local* machine is then possible | 23:10 |
lkcl | if any of those logs become important then it is a trivial matter of copying the relevant sections to a bugreport. | 23:11 |
zemaye_ | This is interesting. I have to pop offline. | 23:15 |
programmerjake | well...with git doing compression into packfiles (all logs go into git, the mailing list only has 1-2kB per build), i expect it to be on the order of a few tens/hundreds of kB per build. | 23:18 |
programmerjake | i don't have hundreds of GB of storage in the CI server...iirc it has a 64GB ssd and that's it. | 23:18 |
programmerjake | so that's around 2GB of git repo per year assuming 50 CI builds per day (50 is kinda excessive...our average rate is much lower) | 23:23 |
programmerjake | and around 40MB of mailing list | 23:23 |
programmerjake | -- totally affordable imho | 23:23 |
lkcl | a 64 GB SSD is still 6x larger than the spare capacity of the VM. so, no, sorry. | 23:25 |
lkcl | plus i have to do remote scp backups onto my laptop (rsync) | 23:26 |
lkcl | storage of repeated logs "everything's ok" is not useful - at all. | 23:26 |
programmerjake | most of the 64GB is needed for OS and temporary storage, | 23:26 |
lkcl | we can always get you a bigger SSD/HDD | 23:27 |
lkcl | the VM has to be paid for - by me - on a monthly basis. | 23:27 |
lkcl | extra storage has to be paid for at a cost per megabyte. | 23:27 |
programmerjake | also, the CI server will have availability issues due to being on my local network | 23:28 |
lkcl | perfectly fine | 23:28 |
lkcl | it's a "non-essential" resource | 23:28 |
lkcl | if it can't send out mail to anyone who's subscribed to its list, it will wait until it's back online and re-send | 23:29 |
lkcl | once it gets its OpenVPN link restored | 23:29 |
programmerjake | also, a mailing list is a poor method of handling build emails...ideally we'd send emails to those who broke the build, rather than spamming everyone everytime anyone commits anything | 23:32 |
lkcl | if that's possible, that's great. it can be done via the (open) SMTP port on 10.6.0.1 | 23:33 |
lkcl | if the connection was reliable i'd recommend ssmtp | 23:34 |
lkcl | however if it's not going to be reliable then store-and-forward will be needed, and the default exim4 debian install should be fine, setting 10.6.0.1 as the smtp forwarding host | 23:35 |
programmerjake | i'd use postfix since i'm waay more familiar with it | 23:35 |
lkcl | configure it to "pretend" to be libre-soc.org and by the time the mail gets to the server it'll *be* @libre-soc.org | 23:35 |
lkcl | great | 23:36 |
lkcl | there's no smtp user/password needed for anything on 10.6.0.* | 23:36 |
programmerjake | ok, so i guess i'll work on that today... | 23:38 |
programmerjake | i don't have a public ip, so i'll need some https forwarding set up so people can access the git repo and mailman interface, we also need some kind of allowlist of who we can send build failure emails to, otherwise we'll spam random people if we do something like push gcc's source to one of our repos | 23:43 |
lkcl | that should be perfectly fine, if you can work out the nginx snippet needed for a virtual host (or, simpler, a directory-transparent-proxy) i'll add it. | 23:46 |
lkcl | a virtual host means i have to add a DNS record as well, which is extra work | 23:47 |
programmerjake | imho a virtual host is probably best, avoiding the build server accidentally messing up the main website...may i suggest build.libre-soc.org? | 23:51 |
programmerjake | or build1/libre-soc.org | 23:52 |
programmerjake | build1.libre-soc.org | 23:52 |
lkcl | alain's busy running a training course at the moment, he should be done by the end of the week | 23:56 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!