Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 241] OpenPOWER SImulation is needed of standards
From: bugzilla-daemon @ 2020-03-14 14:18 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-241-13@http.bugs.libre-riscv.org/>

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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
http://pearpc.sourceforge.net/

another one to investigate

-- 
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 241] OpenPOWER SImulation is needed of standards
From: bugzilla-daemon @ 2020-03-14 14:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-241-13@http.bugs.libre-riscv.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://github.com/cebix/macemu/blob/master/SheepShaver/src/emul_ppc/emul_ppc.cpp

another powerpc emulator

-- 
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 241] OpenPOWER SImulation is needed of standards
From: bugzilla-daemon @ 2020-03-14 10:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-241-13@http.bugs.libre-riscv.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://github.com/gem5-gpu

also interesting however possibly as an aside.  however texturisation and
shader functionality were added.

-- 
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 241] OpenPOWER SImulation is needed of standards
From: bugzilla-daemon @ 2020-03-14 10:30 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-241-13@http.bugs.libre-riscv.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://github.com/CSL-KU/SpectreGuard/blob/master/gem5/src/arch/power/isa/formats/integer.isa

this looks reasonable to work with.  it is a code-generator. so the hardware
for-loop will go in as c code outputted as a c for-loop.

-- 
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] Chips Alliance started
From: whygee @ 2020-03-13 21:48 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <80C6AC81-0DAD-4A10-9E90-2E4C26C81195@gmail.com>

On 2020-03-13 22:44, Cole Poirier wrote:
> Coincidentally I came across something in this vein yesterday and I’m
> wondering if it’s something potentially helpful or a YAFOS (Yet
> Another Fake Open Source) project.
> 
> https://www.opencompute.org/wiki/Server/ODSA

as you can guess from the affiliations,
it's a YAFOS because how else would you play with chiplets and such ?
A disguised cartel would be a better name, I think.

> Cole
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

* Re: [libre-riscv-dev] Chips Alliance started
From: Cole Poirier @ 2020-03-13 21:44 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <c97da4ff8f2b5c413fe03cfd63d4bb2a@f-cpu.org>

> On Mar 13, 2020, at 2:29 PM, whygee@f-cpu.org wrote:
> 
> On 2020-03-13 21:27, Luke Kenneth Casson Leighton wrote:
>> https://github.com/chipsalliance/foundation
>> looks like they are making an effort.
> 
> wow.
> 
> how can it look so open and closed at the same time ?
> sheer willpower can do wonders, it seems.
> It feels like the whole "opencores" thing all over again,
> 20 years later, but all the student geeks have turned
> into managers at big companies :-I
> 
>> l.
> yg

Coincidentally I came across something in this vein yesterday and I’m wondering if it’s something potentially helpful or a YAFOS (Yet Another Fake Open Source) project. 

https://www.opencompute.org/wiki/Server/ODSA

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

* Re: [libre-riscv-dev] Chips Alliance started
From: whygee @ 2020-03-13 21:28 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx4Hhd7ae+5i_e-_Cm347ypNDS7WtjWKvhAkQKa7nEAAw@mail.gmail.com>

On 2020-03-13 21:27, Luke Kenneth Casson Leighton wrote:
> https://github.com/chipsalliance/foundation
> 
> looks like they are making an effort.

wow.

how can it look so open and closed at the same time ?
sheer willpower can do wonders, it seems.
It feels like the whole "opencores" thing all over again,
20 years later, but all the student geeks have turned
into managers at big companies :-I

> l.
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] Chips Alliance started
From: Luke Kenneth Casson Leighton @ 2020-03-13 20:27 UTC (permalink / raw)
  To: Libre-RISCV General Development

https://github.com/chipsalliance/foundation

looks like they are making an effort.

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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-13 20:16 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>

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

--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
here's some links to existing code:

the MemFunctionUnits:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/memfu.py;hb=HEAD
this is the "top level" of the mem-matrices, so quite boring

still boring:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/mem_fu_matrix.py;hb=HEAD

ok *now* we are cooking:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/mem_dependence_cell.py;hb=HEAD

however this is really the key bit:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/addr_match.py;hb=HEAD

that is where you get a Pascal's Triangle of address-comparators
*only in the bottom 10 bits*.

the actual algorithm is described in Mitch's book chapters, 11.4.12
i'll attach screenshots for the diagrams in a second.

the code i would like to connect to is here:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/minerva/units/loadstore.py;hb=HEAD

CachedLoadStoreUnit

and here is where the LOADs/STOREs actually get fired off:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/experiment/compldst.py;h=206f44876b00b6c1d94716e624a03e81208120d4;hb=HEAD#l277

here, rather than have that code *arbitrarily* fire off the LD/ST, and *assume*
it will complete in a single cycle:

* stwd_mem_o must be PREVENTED from asserting UNTIL it is absolutely known that
the store will succeed
* load_mem_o must likewise be prevented from asserting until the load is known
to succeed

thus, it is perfectly fine for LOAD (or STORE) to take more than one cycle
(just like any other Function Unit).

yes, i know, if the LD/ST cannot complete (raises an exception) this is a type
of "result", which must result in the cancellation of the instruction (and all
downstream instructions), and an exception raised.

this is TODO however it is important that the information propagate back
through the LOAD/STORE buffer as a potential "result": "LOAD could not take
place due to exception".

-- 
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] changing bugzilla product name
From: Jacob Lifshay @ 2020-03-13 20:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzwvw_zc2Q-PAy3eUetmP06R0jvJkPQ_-g1eHxk0ptbOQ@mail.gmail.com>

On Fri, Mar 13, 2020, 12:57 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Fri, Mar 13, 2020 at 6:47 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > I changed bugzilla's product name from "Libre Shakti M-Class" to
> > "Libre-SOC's first SoC" as well as changing the descriptions for it and
> the
> > "Specification" component.
>
> yeah good idea
>
> > What we are working has evolved to the point that Libre Shakti M-Class
> is a
> > confusing name that doesn't really apply anymore.
>
> *sigh* i kinda like the name - it's non-trademarkeable because
> "Shakti" is the name of Mother Earth (in effect)
>

Interesting, Google translated it to "energy" when I looked it up.

https://en.wiktionary.org/wiki/Shakti

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] changing bugzilla product name
From: Luke Kenneth Casson Leighton @ 2020-03-13 19:56 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD42wKk4cpM-Pcm6iMZ74YdV1nXHVaD1Dfp=rdx3w4Zqsg@mail.gmail.com>

On Fri, Mar 13, 2020 at 6:47 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> I changed bugzilla's product name from "Libre Shakti M-Class" to
> "Libre-SOC's first SoC" as well as changing the descriptions for it and the
> "Specification" component.

yeah good idea

> What we are working has evolved to the point that Libre Shakti M-Class is a
> confusing name that doesn't really apply anymore.

*sigh* i kinda like the name - it's non-trademarkeable because
"Shakti" is the name of Mother Earth (in effect)

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] changing bugzilla product name
From: Jacob Lifshay @ 2020-03-13 18:47 UTC (permalink / raw)
  To: Libre-RISCV General Development

I changed bugzilla's product name from "Libre Shakti M-Class" to
"Libre-SOC's first SoC" as well as changing the descriptions for it and the
"Specification" component.

What we are working has evolved to the point that Libre Shakti M-Class is a
confusing name that doesn't really apply anymore.
_______________________________________________
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 257] New: Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-13 18:40 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 257
           Summary: Implement demo Load/Store queueing algorithm
           Product: Libre Shakti M-Class
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: programmerjake@gmail.com
          Reporter: programmerjake@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
            Blocks: 216
   NLnet milestone: ---

see http://bugs.libre-riscv.org/show_bug.cgi?id=216#c7


Referenced Bugs:

http://bugs.libre-riscv.org/show_bug.cgi?id=216
[Bug 216] LOAD STORE buffer needed
-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-13 18:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>

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

--- Comment #8 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #7)
> jacob, could i ask you the favour of pseudo-coding up the algorithm you
> described?  bear in mind, the DMs will have taken care of separating
> out all LOADs, all STOREs, and all AMOs into batches.
> 
> then we can do a comparison.

Yeah, I can do that.

-- 
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 256] Enhancements to an OpenPOWER ISA-level Simulator are needed
From: bugzilla-daemon @ 2020-03-13 18:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-256-13@http.bugs.libre-riscv.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---


*** This bug has been marked as a duplicate of bug 241 ***

-- 
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 241] OpenPOWER SImulation is needed of standards
From: bugzilla-daemon @ 2020-03-13 18:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-241-13@http.bugs.libre-riscv.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
*** Bug 256 has been marked as a duplicate of this bug. ***

-- 
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 256] New: Enhancements to an OpenPOWER ISA-level Simulator are needed
From: bugzilla-daemon @ 2020-03-13 18:26 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 256
           Summary: Enhancements to an OpenPOWER ISA-level Simulator are
                    needed
           Product: Libre Shakti M-Class
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

The vectorisation and other improvements needed for the LibreSOC need a
simulator in order to test out applications at the assembly-code / binary
level, prior to implementation in hardware.  An instruction-compatible
simulator will be able to execute programs at reasonable speed whereas the
hardware-level simulator will be hundreds of thousands of times slower.  gem5
is a suitable starting point, and the modifications to spike (RV simulator)
need to be ported to it:
https://git.libre-riscv.org/?p=riscv-isa-sim.git;a=tree;h=refs/heads/sv;hb=refs/heads/sv

see this:
https://www.gem5.org/documentation/general_docs/architecture_support/

-- 
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 236] Atomics Standard writeup needed
From: bugzilla-daemon @ 2020-03-13 18:22 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-236-13@http.bugs.libre-riscv.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
See this thread for reason we need something other than Power's already
existing atomic instructions:
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2019-October/003085.html

-- 
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 214] ISAMUX/NS Standard writeup needed
From: bugzilla-daemon @ 2020-03-13 18:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-214-13@http.bugs.libre-riscv.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-February/004190.html

-- 
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 140] Implement AMDVLK / RADV Mesa Vulkan Driver NLNet 2019-10-042
From: bugzilla-daemon @ 2020-03-13 18:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-140-13@http.bugs.libre-riscv.org/>

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

--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
*** Bug 247 has been marked as a duplicate of this bug. ***

-- 
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 247] Implement AMDVLK / RADV Mesa Vulkan Driver
From: bugzilla-daemon @ 2020-03-13 18:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-247-13@http.bugs.libre-riscv.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|CONFIRMED                   |RESOLVED

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---


*** This bug has been marked as a duplicate of bug 140 ***

-- 
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] Rustup security
From: Jacob Lifshay @ 2020-03-13 18:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzzojEUrOU3vYcza0qB9rM7asNMnaSCCSfG9rE9Nz4i7A@mail.gmail.com>

On Fri, Mar 13, 2020, 03:13 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Fri, Mar 13, 2020 at 8:25 AM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > it's similar to installing firefox on windows, where you download and run
> > the executable.
>
> which says it all.
>
> as an aside: when i analysed and derived the security requirements
> that went into debian's package distribution design, it was
> *SEVENTEEN* separate and distinct very specific requirements, any one
> of which, if not complied with, completely and utterly destroyed the
> security chain of package integrity.
>
> https://github.com/rust-lang/rustup#security
>
> "rustup is secure enough for the non-paranoid, but it still needs
> work. rustup performs all downloads over HTTPS, but does not yet
> validate signatures of downloads."
>
> here's the good and the bad:
>
> 1). bad: it is seriously demeaning to use the phrase "non-paranoid" -
> to ACCUSE potential users of rust of "being paranoid".  can i suggest,
> jacob, raising that as a severe and high-priority issue with the rust
> community to get that removed effective immediate?
>

https://github.com/rust-lang/rustup/issues/2262

I don't have permissions to set severity or priority, though I did make a
comment.

>
> 2). bad: relying on HTTPS simply makes the website itself a
> high-priority hacking target.  HTTPS verifies the *channel*, *not* the
> contents.
>

yeah.


> 3). good: at least they recognise that signature validation is critical.
>
> 4). bad: unfortunately they don't describe - at all - how they intend
> to tackle this, and i can pretty much guarantee that if they haven't
> thought about it fully, they *will* get it wrong.  even copying
> something like Redhat package distribution or archlinux distribution,
> they'll get it wrong.
>

They actually do in the list of github issues linked from the above linked
security section:
https://github.com/rust-lang/rustup/issues?q=is%3Aopen+is%3Aissue+label%3Asecurity

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] [Bug 190] Setup Gitlab CI Runner for Kazan on a computer
From: Cole Poirier @ 2020-03-13 16:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-190-13-38h7M7vjlJ@http.bugs.libre-riscv.org/>

> On Mar 10, 2020, at 6:52 PM, bugzilla-daemon@libre-riscv.org wrote:
> 
> http://bugs.libre-riscv.org/show_bug.cgi?id=190
> 
> --- Comment #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> yes. sorry! v busy.  ssh key is all that's needed, we worked out how to
> automatically ssh tunnel over a VPN link so it looks like the public connection
> is to jacob's private machine when it's not :)
> 
> so build server is up. who is configuring it? whoever it is, send me ssh public
> key and preferred username.

Hi Luke,

I will be attempting to set up and configure Jacob’s server this weekend. I will send you a mail later today or tomorrow with my ssh key and preferred username.

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

* Re: [libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page
From: Cole Poirier @ 2020-03-13 16:21 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-178-13-wRaOniTOh1@http.bugs.libre-riscv.org/>

> On Mar 12, 2020, at 10:26 AM, bugzilla-daemon@libre-riscv.org wrote:
> 
> http://bugs.libre-riscv.org/show_bug.cgi?id=178
> 
> --- Comment #210 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> for this one, i'm going to suggest:
> 
> * EUR 250 to jock for the (crucial) questions and for helping get to buster 
> * EUR 200 to tobias for the early checking of the tutorial
> * EUR 700 to be donated to LIP6.fr for the huge amount of bugfixing by JP
> * EUR 150 to Staf for his insights
> * EUR 1200 to me for the persistent head-banging against brick walls
> 
> Cole, as long as you are in Europe, you helped find some early bugs in the
> tutorial page, and made some useful edits, however if you are outside of
> Europe, most of what NLNet would transfer to you would go in banking fees.  we
> can if you like work something out.

Thank you for the consideration Luke, even though I have yet to add my discoveries to the wiki. I reside in Vancouver, Canada so a donation to me would be a waste of the funding we have, in addition I really don’t want to be paid for anything unless it is a substantial contribution to the core of the project (i.e. something that will end up in silicon). Apologies for my lack of communication, I recently started my first career-level job and I’m still in the process acclimating to my new circumstances. That being said, I was able to progress further with the coriolis2 tutorial last weekend, and I plan on trying to repeat this and document it tomorrow. I will edit the wiki with my successful installation steps, and reply here when I inevitably get stuck. Additionally, I plan on setting up and configuring Jacob’s gitlab dev server this weekend. I will leave a reply on the relevant thread.

Best,
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

* [libre-riscv-dev] [Bug 255] New: formal standard documentation of 3D Opcodes
From: bugzilla-daemon @ 2020-03-13 15:59 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 255
           Summary: formal standard documentation of 3D Opcodes
           Product: Libre Shakti M-Class
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Specification
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

Documentation to the level of an ISA Standards Proposal of all hardware
opcodes,
suitable for proposal to the OpenPower Foundation.

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