Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] [Bug 209] spectre-proof speculative execution
From: Luke Kenneth Casson Leighton @ 2020-05-18 19:38 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <0C5BB73E-D5A4-4EE5-8BDE-C5F48188B74E@gatech.edu>

On Mon, May 18, 2020 at 8:25 PM Yehowshua <yimmanuel3@gatech.edu> wrote:

> > so basically this extends the Dependency Matrix "Shadow" concept actually
> > right down into the Caches.
>
> Exactly - keep in mind that this is only for variant 1.
> I’ll read up on the other variants later.
>
> Why do CPUs have to be so complicated...

Hugh said on one of the Virtual Coffee Calls, he's been in touch with
the IBM engineers for many years.  back when they first met, they told
him - straight up - that CPU design is hard.  however - it took
several years for him to properly and actually appreciate that when
they said "hard" they did not mean it in the ordinary sense of
"certain kinds of software engineering problems are hard", they meant,
like, REALLY hard.

this is why i recommended that we go with python, because not only can
we apply OO (Object-Orientated) techniques, we tap directly into the
"default mindset" behind python, which is that you *do not* write code
- ever - without having an adequate unit test.

this in combination with patiently following Mitch's advice of
drilling down to first principles, i am confident that we'll do fine.

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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 19:43 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #3)
> Do you want me to assume the user has already correctly set up ssh config?

no.  this is for the hackathon.  i'm not giving them accounts yet.

> Or just basic setup with clone via read-only https?

basic clone.  does https work?  i usually use git://... because
git-daemon is running.

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 19:47 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #5 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> (In reply to Cole Poirier from comment #3)
> > Do you want me to assume the user has already correctly set up ssh config?
> 
> no.  this is for the hackathon.  i'm not giving them accounts yet.
> 
> > Or just basic setup with clone via read-only https?
> 
> basic clone.  does https work?  i usually use git://... because
> git-daemon is running.

Ok perfect. Much easier. Https does work, I had to look through the mailing
list, I think you and Jacob discussed it in March 
(https://bugs.libre-soc.org/show_bug.cgi?id=266), and set up this method:
http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/.
Testing the script now, will let you know once I have committed it to
dev-env-setup repo, with the file name 'hdl-dev-repos'.

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 19:53 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #5)

> Ok perfect. Much easier. Https does work, I had to look through the mailing
> list, I think you and Jacob discussed it in March 
> (https://bugs.libre-soc.org/show_bug.cgi?id=266), and set up this method:
> http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/.
> Testing the script now, will let you know once I have committed it to
> dev-env-setup repo, with the file name 'hdl-dev-repos'.

throw it out there anyway - commit it the moment you've written it - so
that other people can take a look.

we have an anti-"i'll-commit-it-when-it's-perfect" development rule, remember?

-- 
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 209] spectre-proof speculative execution
From: bugzilla-daemon @ 2020-05-18 19:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-209-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=209

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
On Mon, May 18, 2020 at 8:25 PM Yehowshua <yimmanuel3@gatech.edu> wrote:

> > so basically this extends the Dependency Matrix "Shadow" concept actually
> > right down into the Caches.
>
> Exactly - keep in mind that this is only for variant 1.

there may still be some impact.  reduction in TLB entry availability
may cause timing alterations.

the L0 Cache/Buffer *might* actually be the accidentally-already-designed
place where speculation stops.  i stress "might".

> I’ll read up on the other variants later.
>
> Why do CPUs have to be so complicated...

:)

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 20:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #7 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)
> (In reply to Cole Poirier from comment #5)
> 
> > Ok perfect. Much easier. Https does work, I had to look through the mailing
> > list, I think you and Jacob discussed it in March 
> > (https://bugs.libre-soc.org/show_bug.cgi?id=266), and set up this method:
> > http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/.
> > Testing the script now, will let you know once I have committed it to
> > dev-env-setup repo, with the file name 'hdl-dev-repos'.
> 
> throw it out there anyway - commit it the moment you've written it - so
> that other people can take a look.
> 
> we have an anti-"i'll-commit-it-when-it's-perfect" development rule,
> remember?

With you, saw this and pushed.

-- 
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 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-18 20:26 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=291

Jean-Paul.Chaput@lip6.fr changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Jean-Paul.Chaput@lip6.fr

--- Comment #10 from Jean-Paul.Chaput@lip6.fr ---
Created attachment 56
  --> https://bugs.libre-soc.org/attachment.cgi?id=56&action=edit
Take a correct snaphost of the Coriolis environment in ~/coriolisenv

-- 
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 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-18 20:30 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=291

--- Comment #11 from Jean-Paul.Chaput@lip6.fr ---
I did miss to attach this to the previous attachement.

My guess for the problem, is that the Coriolis environment was badly set, hence
the helpers import failure. The patch contains a correction. I was not able to
check it in the exact same conditions as the script assumes that the host OS is
already a Debian like.

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 20:33 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #7)
> (In reply to Luke Kenneth Casson Leighton from comment #6)
> > (In reply to Cole Poirier from comment #5)
> > 
> > > Ok perfect. Much easier. Https does work, I had to look through the mailing
> > > list, I think you and Jacob discussed it in March 
> > > (https://bugs.libre-soc.org/show_bug.cgi?id=266), and set up this method:
> > > http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/.
> > > Testing the script now, will let you know once I have committed it to
> > > dev-env-setup repo, with the file name 'hdl-dev-repos'.
> > 
> > throw it out there anyway - commit it the moment you've written it - so
> > that other people can take a look.
> > 
> > we have an anti-"i'll-commit-it-when-it's-perfect" development rule,
> > remember?
> 
> With you, saw this and pushed.

got it.
https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=hdl-dev-repos;hb=HEAD

ah goood, looks like that'll work really well.

and these cover everything and a bit more, yes?
https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=install-apt-reqs;hb=HEAD

if so, that's probably pretty much what the hackathon will need.

-- 
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] closing git https access bug
From: Jacob Lifshay @ 2020-05-18 20:34 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-320-13-pJgdjUyaA4@https.bugs.libre-soc.org/>

On Mon, May 18, 2020, 12:47 <bugzilla-daemon@libre-soc.org> wrote:

> --- Comment #5 from Cole Poirier <colepoirier@gmail.com> ---
> (In reply to Luke Kenneth Casson Leighton from comment #4)
> > (In reply to Cole Poirier from comment #3)
> > > Do you want me to assume the user has already correctly set up ssh
> config?
> >
> > no.  this is for the hackathon.  i'm not giving them accounts yet.
> >
> > > Or just basic setup with clone via read-only https?
> >
> > basic clone.  does https work?  i usually use git://... because
> > git-daemon is running.
>
> Ok perfect. Much easier. Https does work, I had to look through the mailing
> list, I think you and Jacob discussed it in March
> (https://bugs.libre-soc.org/show_bug.cgi?id=266), and set up this method:
> http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/
> .
>

If https is working, we should close the bug report for adding it and move
any remaining issues (gpg signing?) to new bug reports.

Luke, I'll let you do that, since you were the one who brought up the
related issues.

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 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-18 20:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=291

--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #11)
> I did miss to attach this to the previous attachement.
> 
> My guess for the problem, is that the Coriolis environment was badly set,
> hence the helpers import failure. The patch contains a correction. I was not
> able to check it in the exact same conditions as the script assumes that the
> host OS is already a Debian like.

thank you jean-paul.

-- 
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 266] deploy git commit-signing and tag-signing
From: bugzilla-daemon @ 2020-05-18 20:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=266

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Allow read-only git clone   |deploy git commit-signing
                   |over https                  |and tag-signing

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
changing the topic of this bugreport.

-- 
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] closing git https access bug
From: Luke Kenneth Casson Leighton @ 2020-05-18 20:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5d1r_Uq8RwAWnHuHDkgs6hh_cv6J5aJPfSUbpZmw+kaw@mail.gmail.com>

On Mon, May 18, 2020 at 9:35 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> If https is working, we should close the bug report for adding it and move
> any remaining issues (gpg signing?) to new bug reports.
>
> Luke, I'll let you do that, since you were the one who brought up the
> related issues.

good call - i cheated, changed the subject-line of the bugreport :)

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 209] spectre-proof speculative execution
From: bugzilla-daemon @ 2020-05-18 20:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-209-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=209

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
actually, you know what?  collating all "shadow" signals right down into
the L0CacheBuffer might be a really good way to ensure that there is time
for the L0CacheBuffer to "collate" (merge) multiple requests.

right now, as it stands, each request that comes in, if sent immediately
on an elstrided sequence, could be followed up by another request that
*could* have been merged with the 1st into the exact same cache-line...
if only the 1st had been delayed for just one cycle.

if there is a good reason to delay them, this actually could be beneficial.

-- 
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] [Bug 266] deploy git commit-signing and tag-signing
From: Jacob Lifshay @ 2020-05-18 20:53 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-266-13-MpxQXa01Sx@https.bugs.libre-soc.org/>

On Mon, May 18, 2020, 13:43 <bugzilla-daemon@libre-soc.org> wrote:

> https://bugs.libre-soc.org/show_bug.cgi?id=266
>
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Summary|Allow read-only git clone   |deploy git commit-signing
>                    |over https                  |and tag-signing
>
> --- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> changing the topic of this bugreport.


We really shouldn't just repurpose bug reports when the goal of the
original bug report is accomplished, since it makes it quite confusing to
people who weren't paying attention the whole time or are looking through
past bug reports. Additionally, nearly all the comments are on a totally
different topic than what the title was changed to.

Luke, please change the title back, close this bug, and create a new one.

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 266] Allow read-only git clone over https
From: bugzilla-daemon @ 2020-05-18 20:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=266

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|deploy git commit-signing   |Allow read-only git clone
                   |and tag-signing             |over https
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

-- 
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] [Bug 266] deploy git commit-signing and tag-signing
From: Luke Kenneth Casson Leighton @ 2020-05-18 20:57 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5Z8eBTTMR7O5Nxy52JBHKvJMBH=MDeOCk_ixuiQWXzCg@mail.gmail.com>

On Monday, May 18, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Mon, May 18, 2020, 13:43 <bugzilla-daemon@libre-soc.org> wrote:
>
> > https://bugs.libre-soc.org/show_bug.cgi?id=266
> >
> > Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
> >
> >            What    |Removed                     |Added
> >
> > ------------------------------------------------------------
> ----------------
> >             Summary|Allow read-only git clone   |deploy git
> commit-signing
> >                    |over https                  |and tag-signing
> >
> > --- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> > changing the topic of this bugreport.
>
>
> We really shouldn't just repurpose bug reports when the goal of the
> original bug report is accomplished, since it makes it quite confusing to
> people who weren't paying attention the whole time or are looking through
> past bug reports. Additionally, nearly all the comments are on a totally
> different topic than what the title was changed to.
>
> Luke, please change the title back, close this bug, and create a new one.


awww okaaay :)  can't i be totally lazy just once?

(thx for calling this one jacob)



-- 
---
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 322] New: deploy git commit signoff and git tag signing
From: bugzilla-daemon @ 2020-05-18 21:01 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=322

            Bug ID: 322
           Summary: deploy git commit signoff and git tag signing
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: Other
                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: ---

https://bugs.libre-soc.org/show_bug.cgi?id=266#c3

relying solely on https paints a hacking target on our server.  if however the
commits or tags are GPG signed, these are offline, distributed, and harder to
compromise.

this will become relevant when we start doing releases.

-- 
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 322] deploy git commit signoff and git tag signing
From: bugzilla-daemon @ 2020-05-18 21:02 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-322-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=322

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=266

-- 
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 266] Allow read-only git clone over https
From: bugzilla-daemon @ 2020-05-18 21:02 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=266

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=322

-- 
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 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-18 21:02 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=291

--- Comment #13 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Jean-Paul.Chaput from comment #11)
> I did miss to attach this to the previous attachement.
> 
> My guess for the problem, is that the Coriolis environment was badly set,
> hence the helpers import failure. The patch contains a correction. I was not
> able to check it in the exact same conditions as the script assumes that the
> host OS is already a Debian like.

Thank you very much Jean-Paul! I appreciate how busy you are, and how valuable
your time is.

-- 
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 266] Allow read-only git clone over https
From: bugzilla-daemon @ 2020-05-18 21:07 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=266

--- Comment #5 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> changing the topic of this bugreport.

Luke changed back to avoid confusion. Sincere thanks for taking the extra time!

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 21:07 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #9 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #8)
> (In reply to Cole Poirier from comment #7)
> > With you, saw this and pushed.
> 
> got it.
> https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=hdl-dev-repos;hb=HEAD
> 
> ah goood, looks like that'll work really well.
> 
> and these cover everything and a bit more, yes?
> https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=install-apt-reqs;
> hb=HEAD
> 
> if so, that's probably pretty much what the hackathon will need.

Yes, it's the list of all dependencies I've run into errors for not having
installed while trying to build and install the top-level dependencies.

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 21:38 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #10 from Cole Poirier <colepoirier@gmail.com> ---
Tested in a lxc-container of Debian 10. The following command should produce
the desired outcome:

```
cd ~
git clone https://git.libre-soc.org/git/dev-env-setup.git
sudo bash
cd /home/$USER
./dev-env-setup/install-apt-reqs && ./dev-env-setup/yosys-et-al &&
./dev-env-setup/hdl-dev-repos
ctrl-d
```

As I am the assignee, should I now close this bug report?

-- 
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 320] split out software install and deps into separate script
From: bugzilla-daemon @ 2020-05-18 21:45 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-320-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=320

--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
superb.  yes done tested therefore close.  thank you cole.

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