Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 280] POWER spec parser needs to support fall-through cases
From: bugzilla-daemon @ 2020-04-05 22:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-280-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=280

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #4)

> Um, I don't think the pseudocode in the Power spec was ever supposed to be
> Python,

it's not, however it turns out to be a whitespace-indented one, probably
through expediency and a desire for compact clarity.

i *began* with GardenSnake.py and rapidly morphed it to match the PDF
pseudocode grammar.

it *outputs* python AST because that was what GardenSnake did, and it's worked
well.

however python lacks switch/case about which i always wondered "wth?" and it
makes sense now: case fall-through seriously messes with an already complex
three-pass process.

> so I have no issues with changing the grammar file to more
> accurately match the spec pdf even if the grammar doesn't match Python as
> closely.

the "hard" way is to try and mess with one of the existing stages.

the pseudo syntax does this:

do while test
    foo

by recognising the keyword "while" i managed to insert an extra token ":" when
the newline occurs.

this trick means that the tokens *look* like they were this:

do while test:
    foo

and of course that now looks exactly like python "while" and it was easy to
add.

i therefore have absolutely no problem messing with the token stream to "get
the desired outcome" :)


> > i've made quite a few minor changes, some of them necessary (to support
> > syntax such as CR0[x] rather than CR0_subscript_x, some of them, well,
> > not being lazy, just "trying to get it working fast"
> > 
> > yet-another-preprocessor-stage - even if it is line-based rather than
> > ply-lexer-based, looking for 2 "case" statements (or case followed by
> > default) which are lined up, and inserting the ghost word "fallthrough"
> > would "do the trick"
> 
> I think having the grammar correctly reflect the actual syntax that is used
> is probably a better way to go than adding preprossing cludges to add
> `fallthrough` everywhere.

i'd put it as an actual keyword, which is silently added by the lexer and
silently removed by the yacc parser, if it made any difference.

however by matching against NAME it makes life simpler and easier.

i think what is happening is that

case(5): somename

is matching against "small single line suite".

by then detecting "if len(statements) == 1 and statements[0] == "fallthrough""
that does the trick.

i know - it's awful.  

> The space-counting done by the lexer translates the spaces into the INDENT
> and DEDENT tokens.

yes.  the person who wrote GardenSnake.py copied the algorithm from the python
c interpreter and transliterated it to python ply lexer.

i had a loovely time getting it to recognise whitespace, properly.  changed the
actual lexer context to trick it into swapping fron whitespace-aware to
non-aware :)


> The following algorithm should work to translate lines:
> 
> def lexer(lines):
>     """ lines is a iterator that returns each line
>         of text without the trailing newline """

unfortunately, stripping the newlines removes vital information, particularly
when discerning small statements after a colon from "suites".

a suite is defined as the following tokens

NEWLINE INDENT stmts DEDENT

where the algorithm you wrote (minus NEWLINE stripping) identifies indent and
dedent

oh... er, 1 sec...

>         yield from tokenize(line)
>         yield NL

ah interesting.  so the NL *isn't* removed?

-- 
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] auto-generated simulator working??
From: Luke Kenneth Casson Leighton @ 2020-04-05 22:22 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5+QNd21Uzh-BkoE-6gaP0+7v3sfkegr6XP_AU=YfMt+Q@mail.gmail.com>

On Sunday, April 5, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Sun, Apr 5, 2020 at 1:20 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > moo?  it's working? holy cow!
>
> Yay!!


good job by michael, integrating the autogenerator real fast.

this basically cuts months off of creating a simulator.

we have now like... 200 opcodes? only 4 of them tested, mind :) but that's
200 opcodes in *under 10 days*

if we implement the PC and the CR flags it will be possible to execute mini
programs.

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 280] POWER spec parser needs to support fall-through cases
From: bugzilla-daemon @ 2020-04-05 22:32 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-280-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=280

--- Comment #6 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #5)
> (In reply to Jacob Lifshay from comment #4)
> > The following algorithm should work to translate lines:
> > 
> > def lexer(lines):
> >     """ lines is a iterator that returns each line
> >         of text without the trailing newline """
> 
> unfortunately, stripping the newlines removes vital information,
> particularly when discerning small statements after a colon from "suites".
> 
> a suite is defined as the following tokens
> 
> NEWLINE INDENT stmts DEDENT
> 
> where the algorithm you wrote (minus NEWLINE stripping) identifies indent
> and dedent
> 
> oh... er, 1 sec...
> 
> >         yield from tokenize(line)
> >         yield NL
> 
> ah interesting.  so the NL *isn't* removed?

No, NL tokens are retained, however duplicate NL tokens coming from empty
lines/comment lines are stripped. The idea is that it should never produce two
NL tokens right after each other.

However, the way I wrote it you can't do the following:

if True:
    # just a comment here, no actual statements;

    # python has a `pass` statement for this case
next_statement

since it will produce "if" "True" COLON NL next_statement
rather than "if" "True" COLON NL INDENT NL DEDENT next_statement

However, the following will work:

if True:
              # empty line with comment

    pass
next_statement

it will produce "if" "True" COLON NL INDENT "pass" NL DEDENT next_statement

-- 
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] Who Buys Talos Workstations?
From: Immanuel, Yehowshua U @ 2020-04-05 22:45 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzTKUUs+S04kwPAfOykNP_JFFz37SW8UwaVgAE65Jv+BA@mail.gmail.com>

> you misunderstand the purpose of the wiki.  if you find something cool
> or useful *do not wait to ask* - just add it.

@Cole, what page did you add it to? I have some other links I’d like to drop in as well.

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

* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-05 23:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=269

--- Comment #32 from Michael Nolan <mtnolan2640@gmail.com> ---
I'm trying to get addpcis working (so I can test NIA and CIA without messing
with branches), and the instruction builds the displacement from "concat(d0,
d1, d2)". We don't have separate d0, d1, and d2 fields, but we do have a D
field and a d0_d1_d2 field. Should this sort of thing (I expect we'll run into
this again with shifts) be corrected in the ISA spec, or by adding the relevant
fields in in fields.text?

-- 
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] added CI to soc.git as well as attempting to fix all tests
From: Jacob Lifshay @ 2020-04-06  0:17 UTC (permalink / raw)
  To: Libre-RISCV General Development

I pushed a new branch with my changes since basically everything is
changed and I didn't split my commits up very well.
On my computer, out of 234 tests, there are 4 errors and 1 failure.

https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=refs/heads/fix-tests

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] added CI to soc.git as well as attempting to fix all tests
From: Jacob Lifshay @ 2020-04-06  0:44 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5UHKiiHJtDYwyPefgiwfaL+stpY_QuS7X3JJHccKwHwQ@mail.gmail.com>

On Sun, Apr 5, 2020 at 5:17 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> I pushed a new branch with my changes since basically everything is
> changed and I didn't split my commits up very well.
> On my computer, out of 234 tests, there are 4 errors and 1 failure.
>
> https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=refs/heads/fix-tests

better url:
https://git.libre-riscv.org/?p=soc.git;a=tree;h=refs/heads/fix-tests;hb=refs/heads/fix-tests

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] sorry state of ieee754fpu repo -- CI desperately needed
From: Jacob Lifshay @ 2020-04-06  0:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxdGWzGyz-GKvjqNUn8Pmh7W4GdZtVHsJr_vhBOmY6ptw@mail.gmail.com>

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

^ permalink raw reply

* Re: [libre-riscv-dev] sorry state of ieee754fpu repo -- CI desperately needed
From: Jacob Lifshay @ 2020-04-06  1:06 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6nw7pgNFug9yNiZ3uzGykPKe-Xq+4_+TOe_OKR6oOJvQ@mail.gmail.com>

On Sun, Apr 5, 2020 at 5:59 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Fri, Apr 3, 2020 at 4:10 AM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> > 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.

One idea is to store all the scraped build logs in a git repo, which
makes it easy to move it around and incrementally download stuff.
We're working on doing the same thing for the mailing list.

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] CI passes for soc.git!!!
From: Jacob Lifshay @ 2020-04-06  1:36 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7s5+NQ_TcKYg_cza7OSNQpLyP9eg82W9zdgreY0=9bnQ@mail.gmail.com>

On Sun, Apr 5, 2020 at 5:44 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sun, Apr 5, 2020 at 5:17 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> >
> > I pushed a new branch with my changes since basically everything is
> > changed and I didn't split my commits up very well.
> > On my computer, out of 234 tests, there are 4 errors and 1 failure.
> >
> > https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=refs/heads/fix-tests
>
> better url:
> https://git.libre-riscv.org/?p=soc.git;a=tree;h=refs/heads/fix-tests;hb=refs/heads/fix-tests

CI passes!!!

https://salsa.debian.org/Kazan-team/soc/-/jobs/649686

I added @unittest.skip() to test_iq, Luke or whoever can fix that test.

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] Who Buys Talos Workstations?
From: Luke Kenneth Casson Leighton @ 2020-04-06  1:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <15501845-4EEC-4C1A-AFE6-F4795EBD2F48@gatech.edu>

On Sunday, April 5, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> > you misunderstand the purpose of the wiki.  if you find something cool
> > or useful *do not wait to ask* - just add it.
>
> @Cole, what page did you add it to? I have some other links I’d like to
> drop in as well.


there's a top level resources page which is as good as any.

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 283] New: reversion of fields.text to fields.txt needed
From: bugzilla-daemon @ 2020-04-06  1:49 UTC (permalink / raw)
  To: libre-riscv-dev

http://bugs.libre-riscv.org/show_bug.cgi?id=283

            Bug ID: 283
           Summary: reversion of fields.text to fields.txt needed
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

https://libre-riscv.org/recentchanges/

jacob i went through this one already, symlinks and so on don't work, and the
page gets converted to /fields/ which is not what is desired.

the nonstandard extension gets ikiwiki to leave the file alone, thus allowing
it to be downloaded unmodified.

-- 
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 283] reversion of fields.text to fields.txt needed
From: bugzilla-daemon @ 2020-04-06  1:54 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-283-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=283

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hm.  it *might* be ok.  checking at 3am is a bit challenging.  tomorrow.

-- 
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-06  2:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=269

--- Comment #33 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #32)
> I'm trying to get addpcis working (so I can test NIA and CIA without messing
> with branches), and the instruction builds the displacement from "concat(d0,
> d1, d2)". We don't have separate d0, d1, and d2 fields, but we do have a D
> field and a d0_d1_d2 field. Should this sort of thing (I expect we'll run
> into this again with shifts) be corrected in the ISA spec, or by adding the
> relevant fields in in fields.text?

they're already there, what i did however was to take d0,d1,d2 and cat them
with underscores into a compound named field.

   d0,d1,d2 (16:25,11:15,31)
        Immediate fields that are concatenated to specify a
        16-bit signed two's complement integer which is
        sign-extended to 64 bits.
        Formats: DX

what should actually happen is that 3 fields should be created.

might need to keep the compound name as well.

hmmm line 225

https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/decoder/power_fields.py;h=26b59d46863fcd313e6d952b8f5fab22129afef0;hb=1117d7c3cd52cc73a757f3c6f62c6602551d7ad3#l225

i apologise, i write these types of line-based parsers on a one-off basis quite
regularly, without expectation of modifying them, afterwards.

i think that one would be easier to process back in decode_instructions.

line 24

https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/decoder/power_fields.py;h=26b59d46863fcd313e6d952b8f5fab22129afef0;hb=1117d7c3cd52cc73a757f3c6f62c6602551d7ad3#l24

here it is just collecting d0,d1,d2 *without* splitting by commas

but in between the brackets *is* split

err nowait, line 213 is where the brackets are silently discarded (spec[1:-1])

then split by comma to recognise 16, 23:24, 31

then split by colon to recognise slices from indices

so hmmm..

suggest taking f from line 210 and splitting it by comma.  if no commas skip
this next bit.

then take s from line 213

use zip on those two lists.

then *recreate* the lines as if they were actually in fields.text with "%s:
[%s]"


 d0 : [16]
 d1 ....
 d2 ....

append those together and *re-call* decodeinstrfields, and do res.update() on
the return dict.

only do that if f from line 210 has a comma in it.

sorry it is 3:30 am if that is totally confusing i can tackle it tomorrow
morning

-- 
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 283] reversion of fields.text to fields.txt needed
From: bugzilla-daemon @ 2020-04-06  2:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-283-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=283

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #1)
> hm.  it *might* be ok.  checking at 3am is a bit challenging.  tomorrow.

I ended up with the file named fields.text and a symlink named fields.txt.

I changed the download code in soc.git to name the local file fields.txt, but
download through the fields.text url.

-- 
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-06  2:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=269

--- Comment #34 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
sorry should be

fs = f.split(",")
ss = spec[1:-1].split(",")
individualfields = []
for f0, s0 in zip(fs, ss):
  txt = "%s (%s)" 
  indfls.append(txt)
if len(fs) > 1:
  res.update(decodeinstrflds(indflds))

something like that, around line 211

-- 
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-06  2:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=269

--- Comment #35 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #32)

> field and a d0_d1_d2 field. Should this sort of thing (I expect we'll run
> into this again with shifts) be corrected in the ISA spec,

fields.txt was taken directly from the PDF. so modifying it is problematic.  it
should be a direct correspondance with the PDF.

when we get the 3.0 spec source code this will become a lot easier.

and also those files will either go or they will themselves be aurogenerated
directly from that spec source file.

-- 
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] Following the PowerISA
From: Immanuel, Yehowshua U @ 2020-04-06  2:46 UTC (permalink / raw)
  To: Libre-RISCV General Development

On the website, we have:

> The Libre RISC-V Project is building a hybrid CPU/GPU SoC. As the name of the project implies, 
> we will be following the RISC-V ISA due to it being open-source and also because of the huge 
> software and hardware ecosystem building around it. 

Since we are now doing userspace RISCV+POWER and system-wide POWER, I imagine this section should be updated?
_______________________________________________
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] Following the PowerISA
From: Immanuel, Yehowshua U @ 2020-04-06  2:51 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <68333793-489F-4F74-88C2-7DA0BCA206A6@gatech.edu>

Also on the website we have: https://libre-riscv.org/resources/#index9h1


TODO get in touch: Other RISC-V GPU attempts
• https://fossi-foundation.org/2019/09/03/gsoc-64b-pointers-in-rv32

• http://bjump.org/manycore/

• https://resharma.github.io/RISCV32-GPU/


Did we ever contact them? Should I do 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

* [libre-riscv-dev] Open Power Registration
From: Immanuel, Yehowshua U @ 2020-04-06  3:01 UTC (permalink / raw)
  To: Libre-RISCV General Development

Are we officially a member of the OpenPower community yet?
Last I heard, our application was in the final phases of processing correct?

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

* [libre-riscv-dev] [Bug 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-06  3:07 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=269

--- Comment #36 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #35)
> (In reply to Michael Nolan from comment #32)
> 
> > field and a d0_d1_d2 field. Should this sort of thing (I expect we'll run
> > into this again with shifts) be corrected in the ISA spec,
> 
> fields.txt was taken directly from the PDF. so modifying it is problematic. 
> it should be a direct correspondance with the PDF.

maintain a set of patches for fields.txt?

-- 
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] Following the PowerISA
From: Immanuel, Yehowshua U @ 2020-04-06  3:40 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A03CD901-D668-44EC-8212-F63C65EA79E5@gatech.edu>

As you can probably tell, I’m going through the resources page and organizing it.

I found a broken link:

https://github.com/riscv/riscv-sbi-doc/blob/master/riscv-sbi.md

I’m assuming it refers to this?

https://github.com/riscv/riscv-sbi-doc/blob/master/riscv-sbi.adoc

If so, I’ll just replace it with a GitHub commit-based link - more permanent.

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

* [libre-riscv-dev] GStreamer and RUST
From: Immanuel, Yehowshua U @ 2020-04-06  5:56 UTC (permalink / raw)
  To: Libre-RISCV General Development

Eventually when we get around to the VPU, we’ll be working closely with Gstreamer, which, has new rust bindings available.

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] Following the PowerISA
From: Immanuel, Yehowshua U @ 2020-04-06  6:28 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <510B76DF-5A8A-4833-86E2-F5CA805A767C@gatech.edu>

https://libre-riscv.org/resources/

I’ve finished going through all the links on the resources page and performed a massive re-organization(basically moved links around into neat sections), and added a couple sections based on my research into the user demographic of POWER systems.

Request for comments…

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] Who Buys Talos Workstations?
From: Immanuel, Yehowshua U @ 2020-04-06  6:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzWMgbG8Q=YxYMChEdJXyMY5YAmD-cgFS5Khe3pdjDcWw@mail.gmail.com>

As mentioned earlier, I’ve been having some meetings at the startup school Create-X and one of the topics that comes up frequently concerns target markets, who else has had success in our space, and competitors.

One question I’ve been looking into is just how successful is FOSS/libre hardware, and who needs it?
I’ll add my findings to the wiki later.

Fantastic Interview with RaptorCS I found on the wiki resources page that talks about who needs open auditable systems that RaptorCS provides below:

https://www.youtube.com/watch?v=o5Ihqg72T3c&feature=youtu.be

Main benefits of POWER that I was able to glean:
 - POWER is really good at handling behemoth amounts of IO - far superior to x86
 - POWER works well with OpenCAPI, delivering somewhere near 5 - 10x speedup relative to PCIE Gen4
 - According to Raptor, IBM takes feedback on POWER ISA quite seriously and works hard to improve for next spec
 - Very easy to add data hungry accelerator to POWER systems, again, because of OpenCapi
 - RaptorCS customers tend to desire direct control over the on-mobo BMC, which RaptorCS provides through FOSS firmware - can guarantee physical hardware access not necessarily equal to root access
 - 99% of Debian APT supported - AMD ROCM works out of the box.

After some digging around, RaptorCS solutions are not necessarily too expensive, the hardware is enterprise grade and falls in that price bracket. Also, included in that higher price tag is the peace of mind knowing that your system is fully auditable.

I will add this information to the resources section soon.

# Commodity POWER hardware available:

You can buy a Raptor Blackbird 4-core POWER9 system for $1468. While this seems a bit expensive compared to a comparable high end i7 intel system, you get access to the processor data sheet, pinouts, and mobo. All firmware, etc. Also, OpenCAPI seems to be a big reason alone customers are wiling to pay the extra price tag.
https://www.raptorcs.com/content/BK1B01/intro.html


Lastly, any intel or AMD system integrator using an x86/64 chip is not even allowed to provide mobs schematics under NDA alone.

You can also by the T2080 chip from digikey for $273. It comes with a full data sheet and everything.
I couldn’t find any benchmarks, but from the spec sheet, I’d hazard performance is comparable to a mid end i5 processor. Makes sense that this chip see notable use in the auto and defense industry as it has respectable DSP capabilities. Its only viable ARM competitor is Nvidia Jetson which is notably cheaper. System integration with T2080 seems notably easier however as it is has no NDAs.
https://www.digikey.com/product-detail/en/nxp-usa-inc/T2080NXE8TTB/568-13639-ND/7648244


Conclusion:
RaptorCS clearly demonstrates that a FOSS hardware business model is economically feasible. Encouraging news for us!

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

page:   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