* [libre-riscv-dev] [Bug 208] implement CORDIC in a general way sufficient to do transcendentals
From: bugzilla-daemon @ 2020-04-13 14:35 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-208-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=208
--- Comment #3 from Michael Nolan <mtnolan2640@gmail.com> ---
I was able to translate the linked myhdl code to nmigen and implement both a
state machine based and pipelined cordic here:
https://git.libre-soc.org/?p=ieee754fpu.git;a=tree;f=src/ieee754/cordic;h=3f06900baa42651410d661739fb616e4b3020c52;hb=77f150cff440bed025e2487b6f0fcda9f529290b
You can configure the width, as well as the number of cordic rounds per
pipeline stage. There are some accuracy issues with it though - it exactly
matches the behavior of the myhdl one, but the results it gives can be off by
1% or so from that obtained using sin() or cos() on 16 bit numbers.
--
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-13 14:16 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyd5+RY6khpoOVCHPBR+8s5q4oOkQVpZzpvubQeSb9W2w@mail.gmail.com>
https://groups.google.com/forum/#!topic/comp.arch/qeMsE7UxvlI
https://libre-soc.org/3d_gpu/architecture/6600scoreboard/
https://www.youtube.com/watch?v=ohHbWRLDCfs
this is quite a significant core change to the 6600 scoreboard engine,
so i'm soliciting outside help in reviewing it. ironically (and very
much to the point) i realised an error towards the end of the
description.
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] email support for gitlab-ci-archiver
From: Luke Kenneth Casson Leighton @ 2020-04-13 11:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD58bwoQPSjdMrBvRzrNN3cywm0j902WMwaFoup9Y-5dDg@mail.gmail.com>
On Monday, April 13, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> I fixed the issues with ignoring new jobs.
> I also added support for calling external programs/shell scripts to
> build the emails and stuff,
fantastic.
--
---
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] email support for gitlab-ci-archiver
From: Jacob Lifshay @ 2020-04-13 11:50 UTC (permalink / raw)
To: Libre-RISCV General Development
I fixed the issues with ignoring new jobs.
I also added support for calling external programs/shell scripts to
build the emails and stuff, since after thinking about it a bit, we're
going to probably want to reconfigure which emails get sent to who
relatively often, so having that logic in a shell script may make it
easier to maintain.
The program to run is configured in the email.command value in the config toml:
[email]
command = ["bash", "-c", "env | sort | grep '^GITLAB_CI_ARCHIVER_' && cat"]
The build log is piped to the stdin and everything gitlab-ci-archiver
knows (except for things like access tokens which shouldn't be spread
around) is sent in a whole list of environment variables. The above
email command will print all the environment variables as well as the
build log.
The list of environment variables is constructed from the JSON that
the server returns.
Part of the list of env vars:
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_0_FILENAME=job.log
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_0_FILE_FORMAT=null
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_0_FILE_TYPE=trace
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_0_SIZE=1470134
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_EXPIRE_AT=null
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_FILE=null
GITLAB_CI_ARCHIVER_JOB_ARTIFACTS_LEN=1
GITLAB_CI_ARCHIVER_JOB_COMMIT_AUTHORED_DATE=2020-04-10T16:07:07Z
GITLAB_CI_ARCHIVER_JOB_COMMIT_AUTHOR_EMAIL=lkcl@lkcl.net
GITLAB_CI_ARCHIVER_JOB_COMMIT_AUTHOR_NAME=Luke Kenneth Casson Leighton
GITLAB_CI_ARCHIVER_JOB_COMMIT_COMMITTED_DATE=2020-04-10T16:07:07Z
GITLAB_CI_ARCHIVER_JOB_COMMIT_COMMITTER_EMAIL=lkcl@lkcl.net
GITLAB_CI_ARCHIVER_JOB_COMMIT_COMMITTER_NAME=Luke Kenneth Casson Leighton
GITLAB_CI_ARCHIVER_JOB_COMMIT_CREATED_AT=2020-04-10T16:07:07Z
GITLAB_CI_ARCHIVER_JOB_COMMIT_ID=93d7d7931939585cce484b468f516412514f2719
GITLAB_CI_ARCHIVER_JOB_COMMIT_MESSAGE=connect up ALU properly to pass
full InternalOp subset over, MUL now works
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
* Re: [libre-riscv-dev] purism sponsorship
From: Luke Kenneth Casson Leighton @ 2020-04-13 9:20 UTC (permalink / raw)
To: Libre-RISCV General Development, Nicole Faerber
In-Reply-To: <48543a40743a4f9b9841fee67c90ca808310753b.camel@puri.sm>
On Mon, Apr 13, 2020 at 10:17 AM Nicole Faerber <nicole.faerber@puri.sm> wrote:
>
> Hi Luke & team,
>
> Thank you for your kind words and I would like to use the opportunity
> to tell you that we are really sorry having to stop supporting the
> project. But the current economic crisis also hits us and we need to
> consolidate our expenses and focus on paying our staff first.
no problem at all, nicole. btw something to consider: if you have
software engineers on your team who would like to help, NLNet's
donations are available for tasks! bear in mind that the donations
from NLNet will need to go directly to them.
warmest,
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] purism sponsorship
From: Nicole Faerber @ 2020-04-13 9:09 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton, Libre-RISCV General Development
In-Reply-To: <CAPweEDywyYh0gaoiNuyYp=Xy7Fg9Q3B8Kjm75NnOoYXdwtp66w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]
Hi Luke & team,
Thank you for your kind words and I would like to use the opportunity
to tell you that we are really sorry having to stop supporting the
project. But the current economic crisis also hits us and we need to
consolidate our expenses and focus on paying our staff first. I hope
for your kind understanding. Hopefully we will all meet again soon on
the other side of this tunnel.
Thank you for all your work!
Cheers
nicole
On Sun, 2020-04-12 at 10:57 +0100, Luke Kenneth Casson Leighton wrote:
> (bcc'ing Purism team, apologies for 3rd person references)
>
> ended a few months ago, we found out a couple of days ago from an
> over-worked NLNet team. i am however still extremely grateful to
> them, the significance of their donations cannot be underestimated as
> it was at a crucial time when there was only one NLNet Grant.
>
> also the flexibility it gave us in donating to necessary tasks that
> were outside of the NLNet (fixed) agreement was much needed and
> appreciated.
>
> with many thanks and gratitude,
>
> l.
>
>
>
--
Purism SPC
CTO
PGP: B224 22D6 A8E1 9937 86B3 312D 8B4F FA35 5CA3 82C1
https://puri.sm
[-- Attachment #2: Type: text/plain, Size: 177 bytes --]
_______________________________________________
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] fork of qt contingency
From: Luke Kenneth Casson Leighton @ 2020-04-13 8:25 UTC (permalink / raw)
To: Libre-RISCV General Development
https://news.slashdot.org/story/20/04/12/1940232/open-source-advocates-hope-they-dont-have-to-fork-qt
in case anyone was wondering, from the recent discussions of relying
on salsa, if hosting resources suddenly going away was "hypothetical":
it's not.
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] purism sponsorship
From: Jacob Lifshay @ 2020-04-12 14:29 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDywyYh0gaoiNuyYp=Xy7Fg9Q3B8Kjm75NnOoYXdwtp66w@mail.gmail.com>
On Sun, Apr 12, 2020, 02:57 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> (bcc'ing Purism team, apologies for 3rd person references)
>
> ended a few months ago, we found out a couple of days ago from an
> over-worked NLNet team. i am however still extremely grateful to them, the
> significance of their donations cannot be underestimated as it was at a
> crucial time when there was only one NLNet Grant.
>
> also the flexibility it gave us in donating to necessary tasks that were
> outside of the NLNet (fixed) agreement was much needed and appreciated.
>
Should definitely add this important news to the crowdsupply update
>
_______________________________________________
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-12 12:32 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx0yR0QoE-UGHLyvgnVLnFNkRJm2zhz=tJ6ixYU6YRxKw@mail.gmail.com>
https://libre-soc.org/3d_gpu/compunit_multi_rw.png
argh. the addition of Carry (and other registers) means that the
"simple" 2-in, 1-out Computation Unit is not going to work.
additionally, there are actually 3-in 2-out operations such as the
int-mul-and-add, and FP operations will need to modify FPSCR as well.
the original 6600 CompUnits *specifically* waited until *both*
incoming operand Register Read Ports were free, choosing *one signal
pair* (Rd_Req and Go_Read) to synchronise that.
with the strong possibility of not *having* more than two read ports
per stratification of the Register File (HI-ODD32, LO-ODD32,
HI-EVEN32, LO-EVEN32) the original scheme is not going to work.
therefore where previously there was only one RD_REQ-GO_RD pair,
*multiple* (individual) RD_REQ-GO_RD pairs are needed.
this requires some additional logic. where previously, the logic was
just simply: ISSUE, GO_RD, GO_WR, where only one of those can be
active at any one time, it now has to be:
* ISSUE
* send out multiple RD-REQs
* wait for *ALL* GO_RD responses to come in
* ONLY THEN send out WR-REQs
* wait for *ALL* GO_WR responses to come in
* reset back to the start.
complicated.
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] purism sponsorship
From: Luke Kenneth Casson Leighton @ 2020-04-12 9:57 UTC (permalink / raw)
To: Libre-RISCV General Development
(bcc'ing Purism team, apologies for 3rd person references)
ended a few months ago, we found out a couple of days ago from an
over-worked NLNet team. i am however still extremely grateful to them, the
significance of their donations cannot be underestimated as it was at a
crucial time when there was only one NLNet Grant.
also the flexibility it gave us in donating to necessary tasks that were
outside of the NLNet (fixed) agreement was much needed and appreciated.
with many thanks and gratitude,
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Luke Kenneth Casson Leighton @ 2020-04-12 5:44 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5pBQ7D-UZ_6chGtEBJM-Z-BFYJ4oqdVq9kiw1ef=o_mg@mail.gmail.com>
On Sunday, April 12, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> the .gitlab-ci.yml file works fine, however the python code has
> missing imports and missing classes which make the tests fail even if
> you try to set them to skip, since they fail before invoking the test
> function, which is where the skip decorator works.
current highest priority is getting the core execution engine up and
running.
this is my current focus as we need to demonstrate actual ability to
execute POWER instructions very rapidly in order to engage with IBM
Engineers who are waiting on us.
having the memory subsystem up and running is becoming a high priority.
the FP code is not a high priority and will not be for about a month.
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Jacob Lifshay @ 2020-04-12 3:46 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <ec39a39c-0518-a849-502b-72e18fd89a1b@paape.io>
On Sat, Apr 11, 2020 at 8:56 AM Frieder Paape <frieder@paape.io> wrote:
>
> Hi,
>
> finally I found some time to look into this, I've seen that Jacob
> already wrote the CI test and its working fine. My next steps would be
> to mark all tests that are currently failing as skipped. And then fix
> them one by one.
the .gitlab-ci.yml file works fine, however the python code has
missing imports and missing classes which make the tests fail even if
you try to set them to skip, since they fail before invoking the test
function, which is where the skip decorator works.
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
* Re: [libre-riscv-dev] Pitch Speech
From: Luke Kenneth Casson Leighton @ 2020-04-11 22:29 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <EB466AE6-6840-450D-ABB0-7ED1283532C2@gatech.edu>
On Saturday, April 11, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> > Basically - the question was - what else does LIbreSOC offer besides
> being an open ARM chip,
>
> We’re obviously not ARM, but then I have to explain what POWER is…
if you make the deliberate mistake of saying "POWER PC" they get it because
of apple laptops.
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] Pitch Speech
From: Luke Kenneth Casson Leighton @ 2020-04-11 22:28 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <914BA2FD-9C48-4DB5-97DE-92EC56F6E6E1@gatech.edu>
On Saturday, April 11, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> > lower power, lower software development costs, lower hardware costs
> > due to no licensing royalties.
>
> Yep yep. But the thing I’ve found really catches on is the GPU aspect.
>
> Basically - the question was - what else does LIbreSOC offer besides being
> an open ARM chip,
> and the answer that caught people’s attention was, we have a non-trash GPU
> solution.
yes.
here is those benefits i mentioned.
lower power because it is integrated (a hybrid) single CPUGPUVPU.
lower software development cost because not only is the source code
entirely libre, the drastically simpler driver model combined with the full
source means that single-stepping into the ACTUAL 3D ENGINE is possible.
that is flat out impossible on a proprietary GPU, not because you can't
single step across a kernel level PCIe bus to a completely different
processor, but how the hell do you synchronise debugging when the remote
instruction set is utterly different from the main core??
lower hardware costs due to no licensing is pretty obvious.
--
---
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] Pitch Speech
From: Immanuel, Yehowshua U @ 2020-04-11 20:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwOA0bdEcmqz=dtyrnb_gmdeyo5T2VsakCQQN1VdxJo3Q@mail.gmail.com>
> Basically - the question was - what else does LIbreSOC offer besides being an open ARM chip,
We’re obviously not ARM, but then I have to explain what POWER is…
Yehowshua
_______________________________________________
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] Pitch Speech
From: Immanuel, Yehowshua U @ 2020-04-11 20:01 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwOA0bdEcmqz=dtyrnb_gmdeyo5T2VsakCQQN1VdxJo3Q@mail.gmail.com>
> lower power, lower software development costs, lower hardware costs
> due to no licensing royalties.
Yep yep. But the thing I’ve found really catches on is the GPU aspect.
Basically - the question was - what else does LIbreSOC offer besides being an open ARM chip,
and the answer that caught people’s attention was, we have a non-trash GPU solution.
So I tried to capture that on our front page.
Yehowshua
_______________________________________________
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] Pitch Speech
From: Luke Kenneth Casson Leighton @ 2020-04-11 19:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <7C1067DC-1DF4-4953-A233-6F943CBBBB8E@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sat, Apr 11, 2020 at 7:42 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> So I’ve talked with other entrepreneurs and VCs in the hardware area - and one thing I noticed is it took me over a minute to explain why LibreSOC is useful - which is too long!!
lower power, lower software development costs, lower hardware costs
due to no licensing royalties.
very simple.
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] Pitch Speech
From: Immanuel, Yehowshua U @ 2020-04-11 18:42 UTC (permalink / raw)
To: Libre-RISCV General Development
So I’ve talked with other entrepreneurs and VCs in the hardware area - and one thing I noticed is it took me over a minute to explain why LibreSOC is useful - which is too long!!
So after much thinking, I condensed the utility of LibreSOC into the 15 second essentials.
Please have a look here.
https://libre-soc.org
Also, is it possible to turn of the sub .1 .2… on the Jumbotron header?
Possible throughout the website overall - it’s not as helpful as I had thought it’d be.
Yehowshua
_______________________________________________
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Luke Kenneth Casson Leighton @ 2020-04-11 16:10 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <ec39a39c-0518-a849-502b-72e18fd89a1b@paape.io>
On Sat, Apr 11, 2020 at 4:56 PM Frieder Paape <frieder@paape.io> wrote:
>
> Hi,
>
> finally I found some time to look into this, I've seen that Jacob
> already wrote the CI test and its working fine. My next steps would be
> to mark all tests that are currently failing as skipped. And then fix
> them one by one.
>
> I am however a bit confused about my tasks because Luke says I should
> give priority to the CI logging, which I believe Jacob has already taken
> care of in rust. I do know the language so I could help out there as well.
great. the sooner we can free jacob up to help with the hardware
design on the memory subsystem the better (this is rapidly becoming a
critical path task, jacob)
> Finally I have access to Jacobs build server now. I'd like to ask again
> what my tasks here are. I can see if I can reconfigure gitlab-runner to
> limit it's disk space. Also I understood that I should try and install
> gitlab on the server?
yes please - sufficient to run ci.
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Frieder Paape @ 2020-04-11 15:55 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6nw7pgNFug9yNiZ3uzGykPKe-Xq+4_+TOe_OKR6oOJvQ@mail.gmail.com>
Hi,
finally I found some time to look into this, I've seen that Jacob
already wrote the CI test and its working fine. My next steps would be
to mark all tests that are currently failing as skipped. And then fix
them one by one.
I am however a bit confused about my tasks because Luke says I should
give priority to the CI logging, which I believe Jacob has already taken
care of in rust. I do know the language so I could help out there as well.
Finally I have access to Jacobs build server now. I'd like to ask again
what my tasks here are. I can see if I can reconfigure gitlab-runner to
limit it's disk space. Also I understood that I should try and install
gitlab on the server?
Frieder
On 2020-04-06 02:59, Jacob Lifshay wrote:
> On Fri, Apr 3, 2020 at 4:10 AM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>> On Fri, Apr 3, 2020 at 11:52 AM Frieder Paape <frieder@paape.io> wrote:
>>> Alright, it would finally be a chance for me to get a foot in the door
>>> since gitlabs CI is something I know about and fixing tests will lead to
>>> me getting an idea what the code is about.
>> ok great.
>>
>> jacob you good with that?
>>
>> and with frieder helping on the backend server? (will need your ssh
>> pubkey, frieder)
> Sure, sounds good. A warning: gitlab-runner thinks it can use all the
> free disk space, so you may want to figure out how to reconfigure it
> to not use all the space.
>
> I put some manual git syncing code in /home/git-mirroring so you can
> add the new gitlab instance as an additional target repo.
>
> Instructions on https://libre-riscv.org/resources/server-setup/git-mirroring/
>
> Do note that I configured iptables to specifically block all local
> addresses from docker, so if you try to run gitlab inside a docker
> container it will probably not work.
>
>> we can, say, use... EUR 500 from the Purism budget, and see how it goes?
>>
>> one top priority thing, working out how we can archive copies of all
>> messages generated by CI
>>
>> and in particular, recover the ones already generated, even if it
>> means writing a web scraper.
> Should be relatively easy to use gitlab's API.
>
>> we absolutely cannot rely on salsa as an uncontrolled resource. we
>> are guests on that machine and should in no way rely on that hosting
>> to continue to be provided (and no i am not running gitlab on the 1GB
>> memory allocation vCPU behind libreriscv!)
> Luke, do note that we are currently relying on the combination of
> github and debian salsa to host Kazan's source code, so if they both
> kick us out, we'd have to move all the source. We could probably add
> some more mirrors using the above git-mirroring script since due to
> your selection of port 922 instead of port 22 for ssh, gitlab doesn't
> support push mirroring to libre-riscv.org.
>
> Jacob
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
_______________________________________________
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] libre-soc status: simulator and hardware "first instruction" execution
From: Luke Kenneth Casson Leighton @ 2020-04-11 11:33 UTC (permalink / raw)
To: openpower-hdl-cores, Libre-RISCV General Development
hurrah, after a *lot* of preparation creating various components, the
python-based simulator (only 10 days old) "executed" its first
instructions last week, and, on the basis of that work, the hardware
version was adapted to use the same code as used and tested by the
simulator, and also executed its first actual POWER-decoded
instruction, today.
it was actually three instructions in the hardware: two addi and one
add. the simulator has had add, addpcis, ld, st and mtcrf for around
a week.
the hardware engine - based on the Cray CDC 6600 superscalar
out-of-order architecture (yes, really) - has been operational for
almost a year, with an "internal" (test-only) micro-code that allowed
its operation, including speculative (single-path-cancellable rather
than dual-path cancellable) branches, LD/ST and basic arithmetic, to
be confirmed as functional and not corrupting data.
getting it to understand POWER ISA required replacing that test-only
micro-code, developed last year, with Anton's microwatt-based internal
decoder format. thanks to Michael Nolan's help over the past couple
of months, that decoder was completed, tested, proven (via the
simulator) and was straightforward to drop in place.
we now need to plumb in additional instructions, and convert the LD/ST
and Branch ALUs to understand the microwatt Internal decode format.
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: Luke Kenneth Casson Leighton @ 2020-04-11 11:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxaZhpjimhOqt5+cyQmezm9b6N-i3aVE8r2UdYco8EyBA@mail.gmail.com>
decoded instruction and executed add and addi! w00t!
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] [Bug 137] NLNet 2019 Video Acceleration Proposal 2019-10-031
From: bugzilla-daemon @ 2020-04-11 11:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-137-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=137
--- Comment #18 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
status: MoU signed, sent to NLNet. bob to countersign.
--
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] [Bugzilla] Your account libre-riscv-dev@lists.libre-riscv.org is being impersonated
From: Jacob Lifshay @ 2020-04-10 18:29 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxNK3eAx7080R8eyyicoUBiD-AGd3gWYSkcb9OhCS2YUw@mail.gmail.com>
On Fri, Apr 10, 2020, 11:19 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Fri, Apr 10, 2020 at 7:11 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> > I turned on attachment emails at
> > https://bugs.libre-soc.org/userprefs.cgi?tab=email for the mailing list,
> > didn't seem to help.
>
> this might just be personal user preferences.
>
it is, hence why I edited them for the libre-riscv-dev user using sudo.
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-10 18:27 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 #15 from Jacob Lifshay <programmerjake@gmail.com> ---
Maybe it would be a good idea to ask marc.info to add our mailing lists to
their archive:
https://marc.info/?q=about
--
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