[libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets

[libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets

[Luke Kenneth Casson Leighton]

hi folks,

i have the LD/ST CompUnit FSM closer to acceptably operational.  i had
to add some very bad hacks in to get it to work, and also into the
L0CacheBuffer.  luckily the prototype L0CacheBuffer is not intended
for heavy production, it's there as a stop-gap measure.

also we have three additional tasks that have been verbally approved,
kindly, by Michiel from NLNet:

* nmigen and yosys funding: EUR 10,000
* POWER9 core funding: EUR 8,000
* SoC Documentation funding: EUR 6,000

we were running particularly low on the development of the POWER9
core, because (a) it is more complex than RV64GC (b) the core is
covered by the original (first) NLNet Grant, applied for in Nov 2018,
and (c) a full half of that first EUR 50,000 budget was allocated to
Kazan.

this is good news for everyone who has completed tasks in the past 2
months on the POWER9 core because now it will be possible (once the
MoU is signed) to give you donations for completing them.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets

[Yehowshua]

> 
> a full half of that first EUR 50,000 budget was allocated to
> Kazan.

On the note of Kazan, what is currently being done there?
I contacted Anton from Embox, he worked on the Etna-viv drivers 
and he recently joined the mailing list.

Anton, don’t be shy to say hi :)

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets

[Luke Kenneth Casson Leighton]

On Thursday, June 11, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> >
> > a full half of that first EUR 50,000 budget was allocated to
> > Kazan.
>
> On the note of Kazan, what is currently being done there?


nothing for the moment as we need all hands that have some nmigen
experience on the POWER9 core.


> I contacted Anton from Embox, he worked on the Etna-viv drivers
> and he recently joined the mailing list.
>
> Anton, don’t be shy to say hi :)


hi anton, great to know you're around, we have a budget for 3D driver work
if you're interested?

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

[libre-riscv-dev] Kazan status

[Jacob Lifshay]

On Thu, Jun 11, 2020, 12:42 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Thursday, June 11, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > >
> > > a full half of that first EUR 50,000 budget was allocated to
> > > Kazan.
> >
> > On the note of Kazan, what is currently being done there?
>
>
> nothing for the moment as we need all hands that have some nmigen
> experience on the POWER9 core.
>

I'm taking a break on Kazan as stated above, Kazan's current status is that
the SPIR-V to shader-compiler-ir translator and creating shader-compiler-ir
is somewhere around half complete, I've been writing both of those together
to allow rapid modifications to shader-compiler-ir to add support for
SPIR-V features as I encounter them in the process of writing the
translator. At that point, writing the shader-compiler-ir language
reference docs will be the next step, since many of the invariants that the
code follows is not really documented yet. Once shader-compiler-ir is
stable and documented, it will be much more practical to have multiple
people work on different parts of the compiler at the same time, since the
basic interface will not change as much. After that, writing a reference
interpreter will allow us to run some actual shaders, writing the SIMT to
vector translator (the vectorization pass) will be enough to get to where
we should be able to run shaders with the expected execution model and
allow us to have all the parts for a working interpreted shader stack.
Next, writing the shader-compiler-ir to LLVM IR translator and JIT
compiler, creating a trait for a generic shader compiler backend (the part
that translates the final shader-compiler-ir to machine code and allows
executing the JIT compiled code or an interpreter) will allow us to have a
MVP working shader compiler, as well as settling the interface between the
rest of the Vulkan driver and the shader compiler crates.

>
>
> > I contacted Anton from Embox, he worked on the Etna-viv drivers
> > and he recently joined the mailing list.
> >
> > Anton, don’t be shy to say hi :)
>
>
> hi anton, great to know you're around, we have a budget for 3D driver work
> if you're interested?
>

Hi anton, glad to have additional people around who know a lot about 3D
drivers.

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] Kazan status

[Lauri Kasanen]

On Thu, 11 Jun 2020 13:56:22 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:

> I'm taking a break on Kazan as stated above, Kazan's current status is that
> the SPIR-V to shader-compiler-ir translator and creating shader-compiler-ir
> is somewhere around half complete,

Phoronix recently reported that the Vallium cpu implementation of
vulkan was already able to render Talos Principle. If work on it keeps
on at that pace, by Oct when Jacob is free again it will be much
further ahead.

Given this, it would make sense to consider moving to it over Kazan, or
at least checking the possibility.

- Lauri

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] Kazan status

[Anton Bondarev]

Hi, all
I'm Anton from Embox:)

I've some experience with etna-viv and mesa 3d (we ported etna-viv to
Embox). But I'm not sure that I'm an expert in GPU driver.

Anton


чт, 11 июн. 2020 г. в 23:56, Jacob Lifshay <programmerjake@gmail.com>:

> On Thu, Jun 11, 2020, 12:42 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > On Thursday, June 11, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
> >
> > > >
> > > > a full half of that first EUR 50,000 budget was allocated to
> > > > Kazan.
> > >
> > > On the note of Kazan, what is currently being done there?
> >
> >
> > nothing for the moment as we need all hands that have some nmigen
> > experience on the POWER9 core.
> >
>
> I'm taking a break on Kazan as stated above, Kazan's current status is that
> the SPIR-V to shader-compiler-ir translator and creating shader-compiler-ir
> is somewhere around half complete, I've been writing both of those together
> to allow rapid modifications to shader-compiler-ir to add support for
> SPIR-V features as I encounter them in the process of writing the
> translator. At that point, writing the shader-compiler-ir language
> reference docs will be the next step, since many of the invariants that the
> code follows is not really documented yet. Once shader-compiler-ir is
> stable and documented, it will be much more practical to have multiple
> people work on different parts of the compiler at the same time, since the
> basic interface will not change as much. After that, writing a reference
> interpreter will allow us to run some actual shaders, writing the SIMT to
> vector translator (the vectorization pass) will be enough to get to where
> we should be able to run shaders with the expected execution model and
> allow us to have all the parts for a working interpreted shader stack.
> Next, writing the shader-compiler-ir to LLVM IR translator and JIT
> compiler, creating a trait for a generic shader compiler backend (the part
> that translates the final shader-compiler-ir to machine code and allows
> executing the JIT compiled code or an interpreter) will allow us to have a
> MVP working shader compiler, as well as settling the interface between the
> rest of the Vulkan driver and the shader compiler crates.
>
> >
> >
> > > I contacted Anton from Embox, he worked on the Etna-viv drivers
> > > and he recently joined the mailing list.
> > >
> > > Anton, don’t be shy to say hi :)
> >
> >
> > hi anton, great to know you're around, we have a budget for 3D driver
> work
> > if you're interested?
> >
>
> Hi anton, glad to have additional people around who know a lot about 3D
> drivers.
>
> 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

Re: [libre-riscv-dev] Kazan status

[Luke Kenneth Casson Leighton]

On Fri, Jun 12, 2020 at 8:12 AM Anton Bondarev
<anton.bondarev2310@gmail.com> wrote:
>
> Hi, all
> I'm Anton from Embox:)

hi anton :)

> I've some experience with etna-viv and mesa 3d (we ported etna-viv to
> Embox).

nice!  this project? https://github.com/embox

> But I'm not sure that I'm an expert in GPU driver.

yes, porting of drivers is quite different from actually writing them.
at least, the main thing is: you actually know the codebase.

what did you actually do, what did the porting of etnaviv involve?

best,

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev