[Libre-soc-dev] daily kan-ban update 08sep2020

[Cole Poirier]

On Tue, Sep 8, 2020 at 1:22 PM Luke Kenneth Casson Leighton
<lkcl at lkcl.net> wrote:
>
> On Tue, Sep 8, 2020 at 9:02 PM Cole Poirier <colepoirier at gmail.com> wrote:
> > Luke, I uploaded the CR-XER debug vhdl interface that I  did the new
> > version of yesterday
> > https://bugs.libre-soc.org/attachment.cgi?id=103&action=diff
> > (https://bugs.libre-soc.org/show_bug.cgi?id=484).
>
> yeah i saw, just haven't got to it yet.

No worries, thanks for the update.

> > Yesterday:
> >
> > Worked on icache.vhdl about 10% to go.. 15% if I include icache_tb.vhdl.
>
> excellent.

Two processes left to convert now. Should be done tomorrow.

> > This morning:
> >
> > Fixed the remaining issues in the libre-soc vulkan driver setup, there
> > were necessary files missing from the src/libre-soc/vulkan dir but
> > copying the files that meson errored on not finding from
> > src/amd/vulkan to src/libre-soc/vulkan
>
> ah ask vivek about that, on #251.

Thanks, will do... tomorrow.

> > allowed me to compile and
> > install successfully. Do we have a copy hosted on git.libre-soc.org,
>
> push to here please https://git.libre-soc.org/?p=mesa.git;a=summary

Will do.

> > or should I be making a pull request to vivek's branch on the
> > freedesktop mesa?
>
> how?  that only works if you have an account on the gitlab system, doesn't it?

I had no idea, was simply asking for guidance, pushing to
git.libre-soc.org is my preferred option so it's all worked out
nicely.

> > Updated the wiki documentation page for this, and updating the
> > associated script now, will push shortly.
>
> excellent.
>
> > This afternoon:
> >
> > Finish icache.py first translation pass.
> >
> > Review luke's comments on D-Cache if I have time.
>
> you have time.  the reason that you have time is because if you don't
> correct your understanding of how the mistakes occurred in dcache.py,
> you'll continue to repeat them in icache.py.

Very true.

> at which point, because i've gone to the trouble of explaining them to
> you, i won't correct them myself, i'll leave them for you to spend
> *your* time correcting them.
>
> ergo: you do, in fact, have time :)

You are, as is often the case, indeed correct. Thanks for this needed
course correction.

I'm still recovering from my road trip so I'm pretty exhausted. Don't
have the energy to review and commit tonight, I'm literally falling
asleep at my keyboard. Will do so first thing tomorrow morning,
apologies for this violation of the principle of "commit, and commit
often."

Cole