* [libre-riscv-dev] BlueSpec Floating Point
From: Immanuel, Yehowshua U @ 2020-03-29 16:09 UTC (permalink / raw)
To: Libre-RISCV General Development
I have recently been playing with BlueSpec and they have some libraries for generating floating point that also come with some formal methods I think.
We should look into this as it might save some time for reconfigurable FP. Also, Bluespec compiler is now open source under a license that’s basically the BSD license, see here: https://github.com/B-Lang-org/bsc/blob/master/LICENSES/LICENSE.hbc
I’ve successfully built BSC on MacOS too, so its pretty flexible - not to mention fast.
We can take emitted BSC Verilog and perhaps convert it into nMigen once we’ve ran all the formal tests on the FP unit in BSV.
If you guys want - I can actually work on the FP unit in BSV and see how that goes.
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-29 16:14 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <F07E7FAF-3BA5-4DE2-B2A4-99DA65503C4E@gatech.edu>
On Sun, Mar 29, 2020 at 5:03 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> Haha - well Georgia Tech where I am is more or less like an ISP so I have Gigabit internet when on campus - so no problems here.
yehyeh. this is normal. then we get someone like myself: in the
process of developing this project, just in the past two years i've
been to India, China, Taiwan, Okinawa Japan, Thailand, Hong Kong,
Spain, Belgium, Holland, England, Scotland, Canada, the U.S (briefly),
and so use
> I haven’t used chroot in years so I can look into that -
https://libre-riscv.org/HDL_workflow/coriolis2/
schroot. cole's looking at scripting that page (it's a matter of just
cut/pasting those commands) because it's needed for the build/test
server. do kick his tyres (yes, you cole :) ) and encourage him to
"release early, release often". as in, "i'll wait until it's perfect
and completed" *actively* prevents and prohibits collaboration. so if
you've got something, check it in *immediately*, ok?
(the OpenSourceEcology project actually have a rule that if you wait
more than 60 seconds before committing a file into an online
repository, that's a major red flag / violation of the collaborative
development rules)
> I’ve just always had a good experience with containers for snapshots.
snapshots. the key word there is: snapshots. as in, "something that
is expected to be thrown away rather than upgraded". as in, a
*multi-gigabyte download*.... each time.
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] Building Docker Containers
From: Immanuel, Yehowshua U @ 2020-03-29 16:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzWsAHJae6gz0rOV5vbUiU83SmkwOf-DyuqZ=xVteJxAA@mail.gmail.com>
> snapshots. the key word there is: snapshots. as in, "something that
> is expected to be thrown away rather than upgraded". as in, a
> *multi-gigabyte download*.... each time.
Docker DOES pull in commit layers. So you can specify layers. Like a GIt layer onto of a python layer, ontop of a ubuntu layer etc. So docker can check which layers changed and just update those - so no need for huge downloads everytime IF you specify docker layer dependencies correctly.
You usually do this in your docker file with “from ubuntu:” for “from python3”
You can also build your own layers etc…
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-29 16:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzWsAHJae6gz0rOV5vbUiU83SmkwOf-DyuqZ=xVteJxAA@mail.gmail.com>
On Sun, Mar 29, 2020 at 5:14 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Sun, Mar 29, 2020 at 5:03 PM Immanuel, Yehowshua U
> <yimmanuel3@gatech.edu> wrote:
> >
> > Haha - well Georgia Tech where I am is more or less like an ISP so I have Gigabit internet when on campus - so no problems here.
>
> yehyeh. this is normal. then we get someone like myself: in the
> process of developing this project, just in the past two years i've
> been to India, China, Taiwan, Okinawa Japan, Thailand, Hong Kong,
> Spain, Belgium, Holland, England, Scotland, Canada, the U.S (briefly),
> and so use
sorry wrote the other bit and accidentally hit send.
use mobile broadband routers. of course, for many reasons including
because i have been abroad, i don't have personal access bank account
that i can register a Contract SIM with, on credit.
therefore i use PAYG SIMS which are FIVE times more expensive.
we absolutely cannot assume that all developers, the world over, who
want to contribute to and use this project have massive bandwidth *or
even a permanent internet connection at all*.
it's why i've been pushing to get public-inbox installed, because it's
git backed. that means people can be entirely offline and still
write messages.
the only bugbear is bugzilla, and it *might* be possible to create a
gateway between bugzilla and bugseverywhere.
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-29 16:24 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <4B863442-6244-4412-92B0-EA073D1A6CEB@gatech.edu>
On Sun, Mar 29, 2020 at 5:19 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> > snapshots. the key word there is: snapshots. as in, "something that
> > is expected to be thrown away rather than upgraded". as in, a
> > *multi-gigabyte download*.... each time.
>
> Docker DOES pull in commit layers. So you can specify layers. Like a GIt layer onto of a python layer, ontop of a ubuntu layer etc. So docker can check which layers changed and just update those - so no need for huge downloads everytime IF you specify docker layer dependencies correctly.
>
> You usually do this in your docker file with “from ubuntu:” for “from python3”
> You can also build your own layers etc…
yes. not interested [and don't have time to find out what the hell is
going on]. not after the complete failure of exactly such a "layer"
setup involving google auth, kubernetes and couchdb 2.3.1 *stable*
docker release resulted in a 1.2 GB download.
i don't trust it, have never liked it, it's badly written, insecure,
and just because everyone in the world thinks it's the best thing ever
doesn't actually make that true - not to someone who's done pretty
much every major type of virtual container for linux that's existed
since 1995. (i manage a 15-year-old server that went through *three*
live conversions: XEN, to KVM, to LXC where it is, now).
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-29 16:26 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <F07E18CF-3C93-4B89-BEF6-DB6F503E8882@gatech.edu>
On Sun, Mar 29, 2020 at 5:05 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> It sounds like Coriolis Python-C++ API isn’t the best. I know this isn’t super easy to do, even with help from tools like Swig.
>
> HOWEVER, given that we have direct access to Jean Paul - that’s a big benefit at the moment.
basically, yes. the alternatives (which do exist) are... inconvenient
(language-wise), and we don't have a working relationship with them.
and, it's 20 years old, and silicon-proven.
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] Building Docker Containers
From: Jacob Lifshay @ 2020-03-29 17:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx+Cg-wota_Np-LyyvSxkT=Kt-YJwhe=oB719=Gf88vuQ@mail.gmail.com>
I'm in the process of adding .gitlab-ci.yml files to all the repos, they
will be used for running CI on the git mirrors on debian salsa using my
build server. I'm writing them to be based on the debian:10 docker image
(basically a debian 10 minimal install) such that anyone who wants can copy
and run the commands from the .gitlab-ci.yml knowing that they are tested
on every commit. See
https://git.libre-riscv.org/?p=nmutil.git;a=blob;f=.gitlab-ci.yml;hb=HEAD
for a WIP version for nmutil.
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-29 17:54 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
Michael Nolan <mtnolan2640@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #1 from Michael Nolan <mtnolan2640@gmail.com> ---
Fixed in 1c9a58b
--
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-29 18:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-riscv.org/?p=soc.git;a=summary
remember ti git push it tho :)
--
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] BlueSpec Floating Point
From: Luke Kenneth Casson Leighton @ 2020-03-29 18:45 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <DE994CBE-320B-4F0D-BFBE-D885E6F620EA@gatech.edu>
On Sunday, March 29, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> I have recently been playing with BlueSpec and they have some libraries
> for generating floating point that also come with some formal methods I
> think.
ah good.
>
> We should look into this as it might save some time for reconfigurable FP.
maybe, maybe not. the ieee754 fp library, in nmigen, is not just
reconfigureable at the bit level, the pipelines are reconfigureable as
well. i just described that partly only yesterday.
> Also, Bluespec compiler is now open source under a license that’s
> basically the BSD license, see here: https://github.com/B-Lang-org/
> bsc/blob/master/LICENSES/LICENSE.hbc
good... the problem is, that doesn't help with the actual programmability.
i worked in india with one of the best people in this field (see pinmux
code) and it was hell. really.
>
> I’ve successfully built BSC on MacOS too, so its pretty flexible - not to
> mention fast.
> We can take emitted BSC Verilog and perhaps convert it into nMigen once
> we’ve ran all the formal tests on the FP unit in BSV.
the unprogrammability and learning curve, right at a pressure point where
we are about to start using code that took over six months to design and
verify, makes this not a viable idea.
however *cross* verification, running them side by side, *is* i think
viable and useful.
the reasoning there is that we can use them, running side by side, in the
unit tests, and seek out discrepancies.
it'll take a week to run but that's ok.
>
> If you guys want - I can actually work on the FP unit in BSV and see how
> that goes.
yes please.
also if you can work out how the formal proofs work, and how to extract the
links into the BSV code or plug in the nmigen library, that would be really
handy.
we have an NLNet budget for FP.Formal proof work btw.
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-29 18:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7VX8h35n0o4j32yfbCe98g7Kzg7e7On5bsu5ozf+UPfA@mail.gmail.com>
On Sunday, March 29, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> I'm in the process of adding .gitlab-ci.yml files to all the repos, they
> will be used for running CI on the git mirrors on debian salsa using my
> build server. I'm writing them to be based on the debian:10 docker image
> (basically a debian 10 minimal install) such that anyone who wants can copy
> and run the commands from the .gitlab-ci.yml knowing that they are tested
> on every commit.
did you happen to include python3.6 and 2.7 ?
See
> https://git.libre-riscv.org/?p=nmutil.git;a=blob;f=.gitlab-ci.yml;hb=HEAD
> for a WIP version for nmutil.
great. for test builds it's a reasonable approach. i wouldn't personally
choose that route, we have to be careful about disk space on the talos test
server however bandwidth there is not an issue.
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] Building Docker Containers
From: Jacob Lifshay @ 2020-03-29 18:59 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxoz3F7DVMc9Lni-gNWGA6Ze+gV5QXOCmv_cNdH59mzDA@mail.gmail.com>
On Sun, Mar 29, 2020, 11:48 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Sunday, March 29, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > I'm in the process of adding .gitlab-ci.yml files to all the repos, they
> > will be used for running CI on the git mirrors on debian salsa using my
> > build server. I'm writing them to be based on the debian:10 docker image
> > (basically a debian 10 minimal install) such that anyone who wants can
> copy
> > and run the commands from the .gitlab-ci.yml knowing that they are tested
> > on every commit.
>
>
> did you happen to include python3.6 and 2.7 ?
>
It just installs the debian python3 package, so python 3.6 I think. Python
2 can be added when we need it.
>
> See
> >
> https://git.libre-riscv.org/?p=nmutil.git;a=blob;f=.gitlab-ci.yml;hb=HEAD
> > for a WIP version for nmutil.
>
>
> great. for test builds it's a reasonable approach. i wouldn't personally
> choose that route, we have to be careful about disk space on the talos test
> server however bandwidth there is not an issue.
>
My build server has a 120GB ssd, so if it works there, it should work on
the talos server.
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] BlueSpec Floating Point
From: Immanuel, Yehowshua U @ 2020-03-29 19:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx6eo5TS1DJH0XcqLkRQn930RFM=Ve4Q=0maJkgL6b7pA@mail.gmail.com>
Sent from my iPad
> On Mar 29, 2020, at 2:46 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> also if you can work out how the formal proofs work, and how to extract the
> links into the BSV code or plug in the nmigen library, that would be really
> handy.
Currently, BSV uses the SMT Yices solver.
_______________________________________________
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] BlueSpec Floating Point
From: Immanuel, Yehowshua U @ 2020-03-29 19:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx6eo5TS1DJH0XcqLkRQn930RFM=Ve4Q=0maJkgL6b7pA@mail.gmail.com>
On Mar 29, 2020, at 2:46 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> we have an NLNet budget for FP.Formal proof work btw.
Ok. I’ll see what I can do for floating point in BSV and how well formal can work.
_______________________________________________
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] BlueSpec Floating Point
From: Luke Kenneth Casson Leighton @ 2020-03-29 19:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <D1B215CC-F3D4-40F3-ABA2-A9FA5D6E081A@gatech.edu>
On Sunday, March 29, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
>
>
> Sent from my iPad
>
> > On Mar 29, 2020, at 2:46 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> >
> > also if you can work out how the formal proofs work, and how to extract
> the
> > links into the BSV code or plug in the nmigen library, that would be
> really
> > handy.
>
> Currently, BSV uses the SMT Yices solver
excellent.
same as yosys.
did they do DIRECT to yices or did they go via symbiyosis?
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] BlueSpec Floating Point
From: Luke Kenneth Casson Leighton @ 2020-03-29 19:05 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <2C95DE0F-A444-4A00-A01B-DE730D8614BB@gatech.edu>
On Sunday, March 29, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
>
> On Mar 29, 2020, at 2:46 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> >
> > we have an NLNet budget for FP.Formal proof work btw.
>
> Ok. I’ll see what I can do for floating point in BSV and how well formal
> can work.
if nothing else we can lift what they did and replicate it.
can you raise a bugreport and crossreference this discussion?
sublink it under the IEEE754 Formal Proof milestone.
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] BlueSpec Floating Point
From: Immanuel, Yehowshua U @ 2020-03-29 19:32 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx6=8QM=vHtDpjBgNKh6YX+LEKKo7NeBtkpeAhnzcurFQ@mail.gmail.com>
Yep. I have an assignment due Wednesday - so I’ll tackle this after that.
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] Building Docker Containers
From: Immanuel, Yehowshua U @ 2020-03-29 19:33 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7+fTte-Q_e4Pp5DuxBeeRYpJBbd+d8XPZ4DuZnxPNgiw@mail.gmail.com>
On Mar 29, 2020, at 2:59 PM, Jacob Lifshay <programmerjake@gmail.com<mailto:programmerjake@gmail.com>> wrote:
My build server has a 120GB ssd, so if it works there, it should work on
the talos server.
Careful there - you need to specify what architecture you’re using if changing to Docker PPC.
Docker by default assumes x86. Look at Raspberry Pi docker for details on how this can be done.
As I understand it, Talos is PPC non?
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] Building Docker Containers
From: Jacob Lifshay @ 2020-03-29 19:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <63C306BA-4137-4CE6-820D-2C3F040B1238@gatech.edu>
On Sun, Mar 29, 2020, 12:33 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
>
>
> On Mar 29, 2020, at 2:59 PM, Jacob Lifshay <programmerjake@gmail.com
> <mailto:programmerjake@gmail.com>> wrote:
>
> My build server has a 120GB ssd, so if it works there, it should work on
> the talos server.
>
> Careful there - you need to specify what architecture you’re using if
> changing to Docker PPC.
> Docker by default assumes x86. Look at Raspberry Pi docker for details on
> how this can be done.
> As I understand it, Talos is PPC non?
>
Talos is powerpc64el. Thanks for the heads-up regarding assuming x86. I was
referring to failing due to running out of disk space, which should be
nearly the same between Power and x86. I have not yet tested the gitlab CI
on the Talos, I'm trying to get it to work on x86 first. Also, since gitlab
CI is running on my local build server which I can walk over to and plug in
a keyboard and display if I need to, it might be easier to debug than if it
was running on a remote server somewhere.
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-29 19:57 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <63C306BA-4137-4CE6-820D-2C3F040B1238@gatech.edu>
On Sunday, March 29, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
>
>
> On Mar 29, 2020, at 2:59 PM, Jacob Lifshay <programmerjake@gmail.com<
> mailto:programmerjake@gmail.com>> wrote:
>
> My build server has a 120GB ssd, so if it works there, it should work on
> the talos server.
>
> Careful there - you need to specify what architecture you’re using if
> changing to Docker PPC.
> Docker by default assumes x86. Look at Raspberry Pi docker for details on
> how this can be done.
> As I understand it, Talos is PPC non?
yes.
it would be good to have Makefiles and/or install.sh scripts and other
automated install things which can be called by people setting up from
scratch.
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] Building Docker Containers
From: Jacob Lifshay @ 2020-03-29 20:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzoGYPdxLS4HVRUNbKmmr+Z0byFjW3f2VYNxoCEpqGafA@mail.gmail.com>
On Sun, Mar 29, 2020, 12:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Sunday, March 29, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
> wrote:
>
> >
> >
> > On Mar 29, 2020, at 2:59 PM, Jacob Lifshay <programmerjake@gmail.com<
> > mailto:programmerjake@gmail.com>> wrote:
> >
> > My build server has a 120GB ssd, so if it works there, it should work on
> > the talos server.
> >
> > Careful there - you need to specify what architecture you’re using if
> > changing to Docker PPC.
> > Docker by default assumes x86. Look at Raspberry Pi docker for details on
> > how this can be done.
> > As I understand it, Talos is PPC non?
>
>
> yes.
>
> it would be good to have Makefiles and/or install.sh scripts and other
> automated install things which can be called by people setting up from
> scratch.
>
The gitlab CI can be set up such that it just runs the install script, if
needed. currently, the script is short enough that I don't think that's
necessary.
The install script and/or gitlab CI just runs the required make, setup.py,
and/or cargo build commands.
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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-29 20:17 UTC (permalink / raw)
To: Libre-RISCV General Development
So I was wondering how to run unit tests for the PPC FPU. We can obviously do this on the Talos server, but also playstation 3.
I have some old PPC Macs, but they are 32 bit not 64 bit.
Sony’s playstation 3 however is ppc64. Also, Sony officially supported Linux on PS3 FAT models only which you can pick up on eBay for $50 - $70.
So I think this is a good route to explore if anyone needs immediate/direct access to PPC64 for unit testing. I’m considering ordering one myself.
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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-29 20:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAF1D9AC-F167-4B48-AE93-BADA36932AE8@gatech.edu>
Sony’s official link.
https://www.playstation.com/ps3-openplatform/
Ubuntu was officially supported by Sony, so I imagine Debian should be a no brainer.
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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-29 20:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAF1D9AC-F167-4B48-AE93-BADA36932AE8@gatech.edu>
On Sun, Mar 29, 2020, 13:18 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> So I was wondering how to run unit tests for the PPC FPU.
I'm planning on making files containing the list of test cases and expected
outputs by using the talos. That way, the unit tests can be run on any
computer without requiring a power processor.
We can obviously do this on the Talos server, but also playstation 3.
>
> I have some old PPC Macs, but they are 32 bit not 64 bit.
>
> Sony’s playstation 3 however is ppc64. Also, Sony officially supported
> Linux on PS3 FAT models only which you can pick up on eBay for $50 - $70.
>
another option is one of the power macs, since they are 64-bit and can have
multiple faster cores (unlike the PS3's single power core -- the cell
broadband engine cores are not power cores) and are much more easily
upgradable. I've seen some for around $100.
I know debian works on them since I used to have one but got rid of it when
moving several years ago.
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] Building Docker Containers
From: Cole Poirier @ 2020-03-29 20:51 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4P_1ZONMmqQ+tc92JiOTB4JHVW96akVwDvtZgX+HWvvg@mail.gmail.com>
On Mar 29 2020, at 1:02 pm, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Sun, Mar 29, 2020, 12:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>> it would be good to have Makefiles and/or install.sh scripts and other
>> automated install things which can be called by people setting up from
>> scratch.
>
> The gitlab CI can be set up such that it just runs the install script, if
> needed. currently, the script is short enough that I don't think that's
> necessary.
> The install script and/or gitlab CI just runs the required make, setup.py,
> and/or cargo build commands.
>
> Jacob
Luke, I'm doing this on the Kazan gitlab in the libre-soc-dev-env-setup
repository
(https://salsa.debian.org/Kazan-team/libre-soc-dev-env-setup). I'm
planing on making many smaller scripts that each do only one spefic
thing (eg. install yosys, install all general software prereqs from apt,
etc.). These scripts can then be combined as needed for specific
purposes/set-ups. I will write the basic use cases as these
purpose-specific aggregations, specifically the entirety of the HDL
workflow setup.
Cole
_______________________________________________
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