* [libre-riscv-dev] gitlab-ci-archiver status
From: Jacob Lifshay @ 2020-04-09 20:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwe6sRq6MqDGTZf=F61D6PUjcG5LMxRstAyhu3ZxjopkA@mail.gmail.com>
On Thu, Apr 9, 2020, 12:32 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Thu, Apr 9, 2020 at 8:21 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> > I used gitlab-ci-archiver to copy the build logs to the git repo's demo
> > branch.
>
> ahh, fantastic.
>
> is that in a position to hand over to frieder or alain?
>
Currently it needs modification to respond properly to adding a new build
to an existing pipeline (if someone clicks rebuild), it currently ignores
all pipelines already committed to the archive git repo. I'd estimate maybe
an hour of work by an experienced Rust programmer is needed.
It also needs code to send out the build failure emails, or that could be
done by a shell script by parsing all the new commits -- so an hour of work
in either bash or Rust -- both should call out to sendmail or equivalent or
we could use something like lettre.at which is a Rust email library. I
would assume the encryption referred to on lettre.at is TLS for email and
not PGP. We should probably set all emails to be forwarded through
libre-soc.org since gmail doesn't like getting emails from a home internet
ip address.
Other than those two things, it should be ready for active service.
The cron job that runs it should also run git push
It has checks to make sure the git repo is set up correctly and that it
won't mess anything up, however it won't work correctly if the repo is
being modified while it runs, so only one instance should run at a time on
each repo.
It's designed to archive the build logs of several gitlab projects at once,
so we should only need to run one instance.
The readme contains instructions for setting it up and using it:
https://salsa.debian.org/Kazan-team/gitlab-ci-archiver/-/blob/master/README.md
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-09 19:36 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #11)
> I'm guessing the source address will be
> git-mirroring@jacob-build-server.programmerjake.tk
ah if you install ssmtp and set it up similar to how it is done on the
ppc64 server, we can make it look like the messages are coming from
libre-soc.org.
take a look in the /etc/ssmtp directory on the pp64 server
> If you can, the Reply-To: header for both special-use mailing lists should
> be set to libre-soc-dev@libre-soc.org
hmmm a case could be made for teaching people "um no you go to the
bugtracker" by rejecting replies. otherwise they will think that they
_should_ reply and we are back to square one.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] more build failures
From: Luke Kenneth Casson Leighton @ 2020-04-09 19:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4Ei-6yKFKXBd1uPtsauGJwf2o7EpihTMJWDdKR+SvbJg@mail.gmail.com>
On Thu, Apr 9, 2020 at 8:21 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Luke, a pile of import errors:
yep, i am sorting out CompUnitALU, reorganising it to use decoder2.
> https://salsa.debian.org/Kazan-team/gitlab-ci-archiver/-/blob/d5411d956d4a7aefc9e6f56e75d0ae1e40175aa7/pipelines/124143/job-656506-log.txt?expanded=true&viewer=simple#L22989
>
> I used gitlab-ci-archiver to copy the build logs to the git repo's demo
> branch.
ahh, fantastic.
is that in a position to hand over to frieder or alain?
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] more build failures
From: Jacob Lifshay @ 2020-04-09 19:21 UTC (permalink / raw)
To: Libre-RISCV General Development
Luke, a pile of import errors:
https://salsa.debian.org/Kazan-team/gitlab-ci-archiver/-/blob/d5411d956d4a7aefc9e6f56e75d0ae1e40175aa7/pipelines/124143/job-656506-log.txt?expanded=true&viewer=simple#L22989
I used gitlab-ci-archiver to copy the build logs to the git repo's demo
branch.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-09 18:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #11 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #10)
> ok http://lists.libre-soc.org/mailman/listinfo looks great, alain.
> two more:
> * libre-soc-builds
> * libre-soc-bugs
>
> both of these need to be subscribable but put into "moderator" mode,
> with only two (authorised) posters permitted. one of those we know
> right now (bugzilla-daemon@libre-soc.org), this should be the
> *only* permitted poster to libre-soc-bugs@lists.libre-soc.org
>
> the other one we will sort out later (with jacob's help and input)
I'm guessing the source address will be
git-mirroring@jacob-build-server.programmerjake.tk
If you can, the Reply-To: header for both special-use mailing lists should be
set to libre-soc-dev@libre-soc.org
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-04-09 14:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-186-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=186
--- Comment #134 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Tobias Platen from comment #133)
> I've tried to run the tests that use GDB, they still fail.
working fine here tobias - you'll need to work out what's missing,
what's going on, by using appropriate print / debug statements.
when you find out please do document it.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-04-09 13:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-186-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=186
Tobias Platen <libre-soc@platen-software.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |libre-soc@platen-software.d
| |e
--- Comment #133 from Tobias Platen <libre-soc@platen-software.de> ---
I've tried to run the tests that use GDB, they still fail.
Traceback (most recent call last):
File "test_sim.py", line 98, in test_sub
self.run_tst_program(program, [1, 2, 3, 4, 5])
File "test_sim.py", line 105, in run_tst_program
qemu_register_compare(simulator, q, reglist)
File "test_sim.py", line 110, in qemu_register_compare
qemu_val = qemu.get_register(reg)
File "/path/to/soc/src/soc/simulator/qemu.py", line 35, in get_register
res = self.gdb.write('-data-list-register-values x {}'.format(num))
File "/usr/local/lib/python3.7/dist-packages/pygdbmi/gdbcontroller.py", line
247, in write
timeout_sec=timeout_sec, raise_error_on_timeout=raise_error_on_timeout
File "/usr/local/lib/python3.7/dist-packages/pygdbmi/gdbcontroller.py", line
285, in get_gdb_response
"Did not get response from gdb after %s seconds" % timeout_sec
pygdbmi.gdbcontroller.GdbTimeoutError: Did not get response from gdb after 1
seconds
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-09 11:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok http://lists.libre-soc.org/mailman/listinfo looks great, alain.
two more:
* libre-soc-builds
* libre-soc-bugs
both of these need to be subscribable but put into "moderator" mode,
with only two (authorised) posters permitted. one of those we know
right now (bugzilla-daemon@libre-soc.org), this should be the
*only* permitted poster to libre-soc-bugs@lists.libre-soc.org
the other one we will sort out later (with jacob's help and input)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] morphing 6600 code to use power decoder
From: Luke Kenneth Casson Leighton @ 2020-04-09 1:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <393761a54bdab5a0ca52e05bbdedf330@f-cpu.org>
On Thursday, April 9, 2020, <whygee@f-cpu.org> wrote:
>
> Could you please elaborate on your system ?
> Is there some sort of buffer to store the immediates
> while waiting for other operands to be ready ?
it's literally as described in Mitch's book chapters. minor alterations
are documented here
https://libre-soc.org/3d_gpu/architecture/6600scoreboard/
you can see in the CompUnit, a latch for immediates and a latch for reg
operands.
one bit says "latch the immediate instead of operand2 as the 2nd input to
the ALU".
very simple.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] morphing 6600 code to use power decoder
From: whygee @ 2020-04-09 0:47 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwDNnrpq=F2=r3i+XsXveheC23fzebRZVTAkL8eejaC+w@mail.gmail.com>
On 2020-04-08 15:26, Luke Kenneth Casson Leighton wrote:
> however one key difference will be that whilst immediates are read from
> the
> opcode, registers are *not* immediately read from the regfile, they are
> done by way of a regfile port bus, and only when available are
> "latched"
> into registers.
>
> only when all read regs become available can the op proceed.
>
> so it is a little different from microwatt which just does, in
> sequence,
> decode read execute write.
>
> it should be fine.
>
> l.
Could you please elaborate on your system ?
Is there some sort of buffer to store the immediates
while waiting for other operands to be ready ?
yg
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-04-08 19:21 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #9 from Alain D D Williams <addw@phcomp.co.uk> ---
I have set up the list Libre-soc-dev here:
http://lists.libre-soc.org/mailman/admin/libre-soc-dev/general
I have copied users across and been through and applied digest choices (by
hand) & administrative 'nomail' settings. I could not set a user 'nomail'
setting for flisu@flisu.pl - they can reset if they want to.
The list should work. I have unset the new-user-welcome-message - so no one
knows that they are on the list - we will set that when we are happy with it;
then send something to the list telling them about it.
When we enable the new list I suggest that we set emergency moderation on the
old one, discard everything sent to it & have the bounce text say something
suitable.
I can also set up a Libre-soc-org list - please tell me that you are happy with
the above first. Should I copy users to that or let people subscribe ?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 182] Move to libre-soc.org
From: bugzilla-daemon @ 2020-04-08 15:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-182-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=182
--- Comment #25 from Alain D D Williams <addw@phcomp.co.uk> ---
Exim config: libre-soc.org added - prov ought to leave libre-riscv.org
Bugzilla config: changed to libre-soc.org
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] test
From: Alain D D Williams @ 2020-04-08 17:09 UTC (permalink / raw)
To: libre-riscv-dev
xxxx
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] GitLab CI Archiver
From: Luke Kenneth Casson Leighton @ 2020-04-08 16:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5CVz8x3rEkt8pu=eVh4mGQV7QZ5AfrmhmapR3EnUfZww@mail.gmail.com>
On Wed, Apr 8, 2020 at 4:42 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Sorry, I ended up writing a Rust program that does at least part of
> what we need (I thought it might take an hour or two -- it took 10):
we need to be careful about that: sysadmin tasks are typically done in
bash, using awk, sed, grep, curl and others.
alain will definitely be unable to work on rust programs: he'll be
able to install and use them but it will take him potentially 3-8
months full-time (doing nothing else) to get to the point where he
could _modify_ - take over - anything written in rust, and maintain
it.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] GitLab CI Archiver
From: Jacob Lifshay @ 2020-04-08 15:42 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyJ3ajKoAuKP0mGe2xDVLxjZeWZTg1kXqnm8pVzMhdzyQ@mail.gmail.com>
On Tue, Apr 7, 2020 at 9:53 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Tue, Apr 7, 2020 at 5:00 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > I'm thinking what will work best is just to build our own system that uses
> > the gitlab api to monitor builds and send emails CCed to the committer and
> > to a mailing list. neither are currently supported by gitlab, it currently
> > sends them all to me since I registered the ssh key for the git mirroring
> > cron job.
>
> i'd very much like to hand that task over to frieder and alain, so
> that we can focus on hardware / software / simulation, if that's ok.
Sorry, I ended up writing a Rust program that does at least part of
what we need (I thought it might take an hour or two -- it took 10):
https://salsa.debian.org/Kazan-team/gitlab-ci-archiver
There's example output in the demo branch.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] morphing 6600 code to use power decoder
From: Luke Kenneth Casson Leighton @ 2020-04-08 13:26 UTC (permalink / raw)
To: Libre-RISCV General Development
i'm making a start on linking up the 6600 experimental code with the power
isa decoder based on microwatt.
given that the 6600 code already was in an "internal opcode" format very
similar in principle to microwatt, this _should_ be relatively
straightforward.
i will start with the CompUnit for fixed integer ALUs, keeping it simple
and passing over cherry picked decoded fields.
however one key difference will be that whilst immediates are read from the
opcode, registers are *not* immediately read from the regfile, they are
done by way of a regfile port bus, and only when available are "latched"
into registers.
only when all read regs become available can the op proceed.
so it is a little different from microwatt which just does, in sequence,
decode read execute write.
it should be fine.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 138] NLNet 2019 Coriolis2 Layout proposal 2019-10-029
From: bugzilla-daemon @ 2020-04-07 19:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-138-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=138
--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Sentence for MoU:
Reducing complexity makes software and hardware we rely on to provide crucial
services and infrastructure more secure and reliable. Making sure that not only
the tools to develop ASICs (coriolis2) but the ASIC itself is fully
transparently developed leaves no opportunity for subversion of hardware.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-07 16:57 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=269
--- Comment #41 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
michael i've just made a half-broken effort to add CR to the simulator.
to get it to work, i added CR (and other special regs) to the list of
parameters that will be passed in and also returned. whether these
should be added to namespace is debatable (probably not), kept separate
instead.
i also created something called FieldSelectableInt which can "refer"
to a subset (of SelectableInt) just like in the Power Decoder.
the idea being to allow CR0 to be "accessed" (arithmetically) including
assignments, and have that actually go *directly* into CR.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Broken build notification from debian salsa
From: Luke Kenneth Casson Leighton @ 2020-04-07 16:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4K5p+_ar__mz02WQ+hrxZe08CR0mH9t0_99vWUrQTJ0w@mail.gmail.com>
On Tue, Apr 7, 2020 at 5:00 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> I'm thinking what will work best is just to build our own system that uses
> the gitlab api to monitor builds and send emails CCed to the committer and
> to a mailing list. neither are currently supported by gitlab, it currently
> sends them all to me since I registered the ssh key for the git mirroring
> cron job.
i'd very much like to hand that task over to frieder and alain, so
that we can focus on hardware / software / simulation, if that's ok.
we only have six months left until the oct 2020 deadline.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Broken build notification from debian salsa
From: Jacob Lifshay @ 2020-04-07 16:41 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4K5p+_ar__mz02WQ+hrxZe08CR0mH9t0_99vWUrQTJ0w@mail.gmail.com>
On Tue, Apr 7, 2020, 09:00 Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Tue, Apr 7, 2020, 08:53 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
>> On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
>> <lkcl@lkcl.net> wrote:
>>
>> > a separate list can be set up, one that is admin-moderator-only, no
>> > subscribes or unsubscribes permitted.
>>
>> hm that wouldn't work, would it... hmm...
>
>
> I'm thinking what will work best is just to build our own system that uses
> the gitlab api to monitor builds and send emails CCed to the committer and
> to a mailing list. neither are currently supported by gitlab, it currently
> sends them all to me since I registered the ssh key for the git mirroring
> cron job.
>
for monitoring the soc repo, you can get the required info in json:
curl
https://salsa.debian.org/api/v4/projects/Kazan-team%2Fsoc/pipelines?scope=finished
>
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 16:29 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=185
--- Comment #21 from Alain D D Williams <addw@phcomp.co.uk> ---
uelves.com is now done to the standard of the others.
I have removed certbot - replaced with my scripts.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Broken build notification from debian salsa
From: Jacob Lifshay @ 2020-04-07 16:00 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzpR4HEg+zOZ1AVvEYdwmm=YWmv0PTwMkDN84-wkyF3Dg@mail.gmail.com>
On Tue, Apr 7, 2020, 08:53 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>
> > a separate list can be set up, one that is admin-moderator-only, no
> > subscribes or unsubscribes permitted.
>
> hm that wouldn't work, would it... hmm...
I'm thinking what will work best is just to build our own system that uses
the gitlab api to monitor builds and send emails CCed to the committer and
to a mailing list. neither are currently supported by gitlab, it currently
sends them all to me since I registered the ssh key for the git mirroring
cron job.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-07 15:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=269
--- Comment #40 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #39)
> https://git.libre-riscv.org/?p=soc.git;a=commitdiff;
> h=5d496a6b50ec3b9e00586e777651c60a1921688d
>
> michael that should just be for fieldname in op_fields otherwise a lot more
> fields get added than is necessary.
>
> op_fields includes the names of everything spotted during parsing... that is
> *not* a GPR.
>
> no need to exclude RS RA RT either because i already excluded them back in
> the parser.
commit 8e261f6ee07e2ccf271f8838daa372d3e2dcb2ed (HEAD -> master, origin/master)
Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Tue Apr 7 16:54:50 2020 +0100
op_fields is passed over (and excludes register names)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Broken build notification from debian salsa
From: Luke Kenneth Casson Leighton @ 2020-04-07 15:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyvmOxf7Yr-J0_hwJQ+owyP_c7aaZW_7Lz80NQtbNAtEg@mail.gmail.com>
On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> a separate list can be set up, one that is admin-moderator-only, no
> subscribes or unsubscribes permitted.
hm that wouldn't work, would it... hmm...
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 15:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=185
--- Comment #20 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #19)
> Bugzilla needs to be updated to send out the correct url.
well spotted. done (in bzla admin interface)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
page: next prev latest
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git