* Re: [libre-riscv-dev] Introduction
From: Staf Verhaegen @ 2020-06-16 8:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 582 bytes --]
Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
>
>
> Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API.
Have you guys validated gitlab ?
It seems you guys are trying to reinvent the wheel. gitlab for example
has issue boards, supports check lists in issues etc.
gitlab the company may not be better the Microsoft but the source code
is free. You can host your own gitlab, like the LIP6 people are doing.
greets,
Staf.
[-- Attachment #2: Type: text/plain, Size: 177 bytes --]
_______________________________________________
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] daily kan-ban update 15jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-16 10:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5b8xWBMVy7=88O5t=OzDQ=qqGOGuabUxHqjJXzNcTxzw@mail.gmail.com>
On Tue, Jun 16, 2020 at 4:09 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> planning on working on the div pipeline today, many other things have
> distracted from that.
i hear ya :)
_______________________________________________
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] Introduction
From: Luke Kenneth Casson Leighton @ 2020-06-16 10:59 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <e4436780b9c80da269ddc9cc66ad8cb709d31183.camel@fibraservi.eu>
On Tue, Jun 16, 2020 at 9:51 AM Staf Verhaegen <staf@fibraservi.eu> wrote:
>
> Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
> >
> >
> > Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API.
>
> Have you guys validated gitlab ?
yes we evaluated gitlab.
* from a security perspective it is a nightmare (vast amounts of code
and involving arbitrary code execution)
* from a code volume perspective there is extra cost involved in the hosting.
* the load average on my server jumped to a permanent 0.6 (60% cpu
utilisation) with *NO USERS*
* load time was well over 20 seconds due to the amount of javascript shit.
> It seems you guys are trying to reinvent the wheel. gitlab for example
> has issue boards, supports check lists in issues etc.
yes it does. the hassle associated with it unfortunately has already
eliminated it from consideration.
> gitlab the company may not be better the Microsoft but the source code
> is free.
unfortunately the hosting, security audit, maintenance and hassle is
not monetarily zero cost.
> You can host your own gitlab, like the LIP6 people are doing.
they have employees specifically dedicated to that task, as do raptor
engineering.
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
* Re: [libre-riscv-dev] Yehowshua Tasks
From: Luke Kenneth Casson Leighton @ 2020-06-16 11:58 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzEK_1kr5CxX8fYrjracQhEaSVaPfXVZ=iCzJcAq5R7SA@mail.gmail.com>
one fundamental aspect of what we are doing: anything that has the
slightest possibility of causing "irreversible damage" absolutely has to
have both a "hold off" and "go die" signal.
nothing and i mean nothing can be allowed to proceed unless it has a 100%
chance of success because we are *not* doing a "transaction / rollback /
history" system, we are doing a *shadow* (write-hold) system.
if there is any possibility of a memory write causing an exception, that is
the *very definition of causing damage*!
the memory write therefore must be subdivided into two phases:
1) to check if the write WOULD succeed ***IF*** permitted to proceed
2) after notification and receiving permission to proceed, ***ONLY*** then
proceeding with the actual commit to memory.
this has implications as i understand it even for the L1 Cache.
it is *not* ok to have phase 1 proceed, the notification go back, "yes
there is room in the cache for you" followed in phase 2 "actually i lied,
we need to raise an exception now".
so to make this clear:
* phase 1 is the only time that exceptions can be raised.
* phase 2 is absolutely fundamentally the part where no exceptions of any
kind can be raised. the write MUST occur... or if it genuinely cannot we
will be required to halt the processor as it is a serious critical mistake
on our part or fundamental data corruption event, from the hardware.
this has implications that phase 1 may need to "hold" resources (reserve
cache lines, reserve TLB entries) for a short duration until it receives
either the "proceed" or "cancel" signal.
i do not know if Minerva L1 can handle that because there is zero code
comments.
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
* Re: [libre-riscv-dev] Introduction
From: Staf Verhaegen @ 2020-06-16 12:33 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDws6xaaAEMQGbQJmcM7obGfKrvREmyu7mqP96SWXaR9rg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1218 bytes --]
Luke Kenneth Casson Leighton schreef op di 16-06-2020 om 11:59 [+0100]:
> On Tue, Jun 16, 2020 at 9:51 AM Staf Verhaegen <staf@fibraservi.eu> wrote:
> > Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
> > >
> > > Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API.
> >
> > Have you guys validated gitlab ?
>
> yes we evaluated gitlab.
> * from a security perspective it is a nightmare (vast amounts of codeand involving arbitrary code execution)
What security implication are you considering for a fully open source project ?
You could not use the release feature of gitlab for example.
> > It seems you guys are trying to reinvent the wheel. gitlab for examplehas issue boards, supports check lists in issues etc.
>
> yes it does. the hassle associated with it unfortunately has alreadyeliminated it from consideration.
Isn't it time to reevaluate if people are planning to implement kanban boards and other things on top of the bugzilla REST API?
Developing, maintaining, auditing that code will also have cost implications.
greets,
Staf.
[-- Attachment #2: Type: text/plain, Size: 177 bytes --]
_______________________________________________
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] Introduction
From: Staf Verhaegen @ 2020-06-16 12:42 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDws6xaaAEMQGbQJmcM7obGfKrvREmyu7mqP96SWXaR9rg@mail.gmail.com>
Luke Kenneth Casson Leighton schreef op di 16-06-2020 om 11:59 [+0100]:
> On Tue, Jun 16, 2020 at 9:51 AM Staf Verhaegen <staf@fibraservi.eu> wrote:
> > Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
> > >
> > > Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API.
> >
> > Have you guys validated gitlab ?
>
> yes we evaluated gitlab.
Alternatively I played in the past with kanboard (kanboard.org). You can find a bugzilla plugin for it on the net but it does not seem to be official so needs to be tested.
greets,
Staf.
_______________________________________________
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] Introduction
From: Luke Kenneth Casson Leighton @ 2020-06-16 13:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <f248aa42dfb0d4be598e3253eaf8c8ae6f98b59b.camel@fibraservi.eu>
On Tue, Jun 16, 2020 at 1:33 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
> What security implication are you considering for a fully open source project ?
one of NLNet's grant recipients was hacked via their (unfunded)
infrastructure being used to develop the (funded) code.
the hackers gained control of the git repositories and inserted
malicious code directly into the git repositories, as code commits,
pretending to be from one of the developers.
this was then downloaded by thousands of unsuspecting users interested
in privacy-respecting applications and trusting that the project -
funded by NLNet - would provide it.
NLNet-funded projects, by nature of them being directed towards
privacy, are *automatic* high-value hacking targets.
> You could not use the release feature of gitlab for example.
who is going to stop working on everything that they are doing and
focus solely and exclusively on the evaluation for fitness of purpose,
and perform the full security audit of the (massive) github codebase,
and work out its required configuration?
this has been discussed many times. every time everyone says "why
don't you just use gitlab, it's so simple and has everything you
need", unfortunately not being aware of the time and resource
implications both from the initial install, migration, training,
resource utilisation and maintenance. we simply do not have time or
resources to cover all of that.
the unix philosophy serves us extremely well: each tool shall do one
thing and do it well.
gitlab fundamentally violates that.
this is a perspective that can only really be fully appreciated when
you have tried to do simple web development tasks that pull in 250
megabytes of dependencies.
> > > It seems you guys are trying to reinvent the wheel. gitlab for examplehas issue boards, supports check lists in issues etc.
> >
> > yes it does. the hassle associated with it unfortunately has alreadyeliminated it from consideration.
>
> Isn't it time to reevaluate if people are planning to implement kanban boards and other things on top of the bugzilla REST API?
there is existing kanban board code. we do not have to write one at all
https://github.com/leif81/bzkanban
however Cole feels inclined to write something and i am not going to
say "no you can't do that".
> Developing, maintaining, auditing that code will also have cost implications.
my brother dan has a business need which happens to match precisely
with what we also need.
therefore we are not paying for it.
in addition it is a *focussed* and incremental enhancement, where we
get the opportunity to input and decide what *we* want.
not what gitlab says we need.
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
* Re: [libre-riscv-dev] Yehowshua Tasks
From: Yehowshua @ 2020-06-16 13:50 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyaGajktrgnr_d=X8zgbTuJukRc1uuXnxrkWqGkr53ieg@mail.gmail.com>
>
> it is *not* ok to have phase 1 proceed, the notification go back, "yes
> there is room in the cache for you" followed in phase 2 "actually i lied,
> we need to raise an exception now”.
Right. So I read through the Minerva cache and understand about
98% of it. There is a cache miss signal. And also a bus error signal
for example, if the cache tries to flush to the main memory via the
wishbone bus and it fails, it will raise bus_err.
What is the difference between hold off and go die?
I’m trying to write a simple unit bench for minerva L1Cache today.
Is there an NLNet task covering this?
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] Yehowshua Tasks
From: Luke Kenneth Casson Leighton @ 2020-06-16 14:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <A49F3570-7103-4FF2-BD60-7896CA427FFC@gatech.edu>
On Tue, Jun 16, 2020 at 2:50 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > it is *not* ok to have phase 1 proceed, the notification go back, "yes
> > there is room in the cache for you" followed in phase 2 "actually i lied,
> > we need to raise an exception now”.
>
> Right. So I read through the Minerva cache and understand about
> 98% of it. There is a cache miss signal. And also a bus error signal
> for example, if the cache tries to flush to the main memory via the
> wishbone bus and it fails, it will raise bus_err.
ok the bus_err one would be an exception, and would fall into phase (1).
the cache miss signal: that would be an indicator to the FSM that
further work needs to be done. this would i imagine still be part of
phase (1).
i *believe* this is taken care of by the time we get to the
LoadStoreUnitInterface. i.e. i anticipate that CachedLoadStoreUnit
will use the cache-miss signal to determine if it should check the
address on the outgoing Wishbone Bus.
i.e., from CachedLoadStore Unit:
Phase (1) for a LOAD
- put the address into the cache. get a "ok or cache miss" (this on same cycle)
- if "miss", put the address out onto the WB Bus (this may take
another cycle and that's ok)
we must HOLD LoadStoreUnit.m_stall indefinitely until such time as
EITHER the cache OR the WB Bus comes back with "yes this will succeed
100% if allowed to proceed".
Phase (2) for a LOAD
- ONLY after the first phase (m_valid but not m_load_error) is raised
will the external dependency tracker drop "m_stall"
it will be absolutely critical to have a unit test (and preferably a
Formal Correctness test) that confirms that at no time will
m_load_error be raised during Phase (2).
> What is the difference between hold off and go die?
they're shadow matrix signals. the logic is actually brain-dead
simple (only a few gates)
https://libre-soc.org/3d_gpu/shadow.jpg
* "hold off" prevents write. it delineates phase 1 and phase 2.
that's both its definition and its job. i believe it corresponds
directly to LoadStoreInterface.m_stall [or possibly x_stall. there's
no documentation here, and x_ and m_ are non-standard conventions].
* "go die" will terminate all current state (full hard reset), free
all held resources, without causing any damage of any kind. this has
to be done on the same clock cycle that the "die" is raised. (not on a
"sync" in other words).
another word for "go die" would be simply "cancel" or "reset". i'm
not seeing any evidence of anything in Minerva loadstore.py which
suggests that such cancellation is possible.
so that would be a specific task that would need to be added.
> I’m trying to write a simple unit bench for minerva L1Cache today.
> Is there an NLNet task covering this?
no - feel free to make one, and refer to the archives (here).
also please do create one for investigating adding "cancel" (go_die)
to loadstore.py. it should do a full hard-reset (withdraw all pending
states back to idle without causing any "damage")
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] daily kan-ban update 16jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-16 14:44 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday:
* debugged LD/ST for test_core.py and got the unit tests functional
* talked about cache and memory architecture
* talked to Alain about getting apache2 set up on loopback for
bugzilla so we can use the REST API
today:
* started on a brain-dead instruction issuer which will allow us to at
least actually run instructions
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] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Luke Kenneth Casson Leighton @ 2020-06-16 14:55 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzjwSo-00xzgrdmNhufVja9mh34oCf6y2w6Bce3v_DWPg@mail.gmail.com>
hi folks they've not received confirmation back from everyone who said
they'd like to participate, so they want to move it to THURSDAY.
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=6&day=18&hour=13&min=0&sec=0&p1=136&p2=224&p3=179&p4=83&p5=176&p6=256
_______________________________________________
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] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Yehowshua @ 2020-06-16 15:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxcMy6Ds-xeCmoeRak1X=4aHouu2vRetx4Wk6OwmNxSFw@mail.gmail.com>
> hi folks they've not received confirmation back from everyone who said
> they'd like to participate, so they want to move it to THURSDAY.
>
OK. Looks like the same time - should work…
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] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Cesar Strauss @ 2020-06-16 16:53 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDxcMy6Ds-xeCmoeRak1X=4aHouu2vRetx4Wk6OwmNxSFw@mail.gmail.com>
Em 16/06/2020 11:55, Luke Kenneth Casson Leighton escreveu:
> hi folks they've not received confirmation back from everyone who said
> they'd like to participate, so they want to move it to THURSDAY.
>
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=6&day=18&hour=13&min=0&sec=0&p1=136&p2=224&p3=179&p4=83&p5=176&p6=256
I intend to participate.
Regards,
Cesar
_______________________________________________
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] Introduction
From: Cole Poirier @ 2020-06-16 18:29 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyn3DUScGhGVALpUx1QYRi=u4USDr-jEyaWncxOfgC16Q@mail.gmail.com>
On Jun 16 2020, at 6:13 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> the unix philosophy serves us extremely well: each tool shall do one
> thing and do it well.
>
> gitlab fundamentally violates that.
Indeed. My application will be specific to our needs with regard to
organization and planning, without *any* extraneous things like managing
CI tests/builds/deployments.
> this is a perspective that can only really be fully appreciated when
> you have tried to do simple web development tasks that pull in 250
> megabytes of dependencies.
This is the reason I will be writing the application in Elm, all
dependencies are *compiled* into the application at *compile* time, the
resulting transpiled-to-js compressed binary is pretty tiny compared to
most javascript frameworks, or vanilla js applications that have
comprable functionality. But comes with the added benefit of
guaranteeing there will be *zero* runtime errors.
>> > yes it does. the hassle associated with it unfortunately has
>> alreadyeliminated it from consideration.
>>
>> Isn't it time to reevaluate if people are planning to implement
>> kanban boards and other things on top of the bugzilla REST API?
>
> there is existing kanban board code. we do not have to write one at all
> https://github.com/leif81/bzkanban
>
> however Cole feels inclined to write something and i am not going to
> say "no you can't do that".
I will be effectively 'cloning' various different existing js projects
functionality, but while complex GUI apps are a very significant
undertaking in js, in Elm, a language built and designed from the ground
up to build high-performance single page web apps, cloning the
functionality of 1,000s of lines of javascript is a vastly simpler
though non-trivial undertaking.
> my brother dan has a business need which happens to match precisely
> with what we also need.
>
> therefore we are not paying for it.
>
> in addition it is a *focussed* and incremental enhancement, where we
> get the opportunity to input and decide what *we* want.
>
> not what gitlab says we need.
Yes, I will implement only what we need from existing projects not take
all of the extraneous 'features' that various people have added over the
years. It should load very quickly and perform well even on low-bandwith
connections and low-spec devices. I am building the foundation of this
single-page web-app for Dan, and it will serve a dual purpose being the
foundation of our bug tracker's *additional* not replacement buzilla
frontend. But, as I have to work on bug/budget/time/etc. tracking
functionality specific to our projects needs, *some* money will be
needed for that.
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] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Cole Poirier @ 2020-06-16 18:57 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxcMy6Ds-xeCmoeRak1X=4aHouu2vRetx4Wk6OwmNxSFw@mail.gmail.com>
On Jun 16 2020, at 7:55 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> hi folks they've not received confirmation back from everyone who said
> they'd like to participate, so they want to move it to THURSDAY.
Sure, no problem.
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] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Luke Kenneth Casson Leighton @ 2020-06-16 19:00 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <35F7329E-16F7-48E4-95F7-A9C28844194C@getmailspring.com>
On Tue, Jun 16, 2020 at 7:57 PM Cole Poirier <colepoirier@gmail.com> wrote:
> On Jun 16 2020, at 7:55 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> > hi folks they've not received confirmation back from everyone who said
> > they'd like to participate, so they want to move it to THURSDAY.
>
> Sure, no problem.
excellent, that's 4 of us. anise and elle too?
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
* Re: [libre-riscv-dev] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Cole Poirier @ 2020-06-16 19:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyh=zYWxR-tPj_xj06r18rNxLteb7=spNTY4QKVxvvvTQ@mail.gmail.com>
> On Jun 16, 2020, at 12:01 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> excellent, that's 4 of us. anise and elle too?
Unfortunately not, they aren’t quite as gung ho as I am. A very common mistake with my sister Anais’ name, is thinking of it as anise. Just think of it as Anna-Eace :)
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] Abuse on salsa.debian.org from user programmerjake-guest
From: Jacob Lifshay @ 2020-06-16 19:23 UTC (permalink / raw)
To: Bastian Blank; +Cc: salsa-admin, Libre-RISCV General Development
In-Reply-To: <20200616191054.5hjibnmgo6joaag3@shell.thinkmo.de>
Sorry about that, I'll disable it for now.
On Tue, Jun 16, 2020, 12:10 Bastian Blank <waldi@debian.org> wrote:
> Hi Jacob
>
> A deploy key associated with your user (fingerprint
> 45:ba:9b:13:b5:57:13:23:7d:6b:7a:19:e7:74:fa:0a) is used to push mirror
> four projects, including
> https://salsa.debian.org/Kazan-team/soc and
> https://salsa.debian.org/Kazan-team/soclayout
>
> This mirror process runs every minute, even if no changes are detected.
> As pushing is a pretty expensive operation, I consider this abuse of the
> service.
>
> Please fix your push to only run if changes are available. You can for
> example add the push to the `post-receive` hook on the repository,
> instead of using cron or similar.
>
> Please acknowledge that you understand the problem and that you have
> fixed it.
>
> Regards,
> Bastian
>
> --
> Warp 7 -- It's a law we can live with.
>
_______________________________________________
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] Abuse on salsa.debian.org from user programmerjake-guest
From: Jacob Lifshay @ 2020-06-16 19:35 UTC (permalink / raw)
To: Bastian Blank; +Cc: salsa-admin, Libre-RISCV General Development
In-Reply-To: <CAC2bXD4kXdPoiTG=Zf6N3Ff9FkEyq-NNbopLTg9Gk53HACE-Jg@mail.gmail.com>
On Tue, Jun 16, 2020, 12:23 Jacob Lifshay <programmerjake@gmail.com> wrote:
> Sorry about that, I'll disable it for now.
>
I disabled the cron job till one of us has a chance to fix it.
I created a bug report on our bugzilla instance in case you want to follow
it.
https://bugs.libre-soc.org/show_bug.cgi?id=387
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] *DAY MOVED* 2pm UK time, 18 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Hendrik Boom @ 2020-06-17 1:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDxcMy6Ds-xeCmoeRak1X=4aHouu2vRetx4Wk6OwmNxSFw@mail.gmail.com>
On Tue, Jun 16, 2020 at 03:55:48PM +0100, Luke Kenneth Casson Leighton wrote:
> hi folks they've not received confirmation back from everyone who said
> they'd like to participate, so they want to move it to THURSDAY.
>
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=6&day=18&hour=13&min=0&sec=0&p1=136&p2=224&p3=179&p4=83&p5=176&p6=256
No problem. On Thursgay I'll only be double-booked instead of triple-booked.
-- hendrik
>
> _______________________________________________
> 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
^ permalink raw reply
* Re: [libre-riscv-dev] Introduction
From: Lauri Kasanen @ 2020-06-17 6:17 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <F9A987F8-01ED-4404-B33B-32165A7BE0B3@getmailspring.com>
On Tue, 16 Jun 2020 11:29:45 -0700
Cole Poirier <colepoirier@gmail.com> wrote:
> This is the reason I will be writing the application in Elm, all
> dependencies are *compiled* into the application at *compile* time, the
> resulting transpiled-to-js compressed binary is pretty tiny compared to
> most javascript frameworks, or vanilla js applications that have
> comprable functionality. But comes with the added benefit of
> guaranteeing there will be *zero* runtime errors.
How is the browser compatibility of what it generates? E.g. if it uses
some feature X that needs Chrome Y or FF unstable, and doesn't work in
FF LTS or other older browsers.
- Lauri
_______________________________________________
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] first version of test issuer is functional
From: Luke Kenneth Casson Leighton @ 2020-06-17 11:30 UTC (permalink / raw)
To: Libre-RISCV General Development
i got these working, overnight:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/simple/test/test_issuer.py;hb=HEAD
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/simple/issuer.py;hb=HEAD
this is a module and associated unit test that are specifically
designed to be as simple and as absolutely clear as possible, and are
specifically intended to test the combined Function Units yet at the
same time actually allow "arbitrary code execution" including loops.
at present the instructions are pushed into a TestMemory (16 words),
and read out sequentially, disregarding changes made by the Branch
Unit. this because that is what the Simulator currently does, and so
consequently all the Function Unit tests are *also* designed to
*produce* changes to the PC, but not to actually listen to them.
to be able to run programs in a loop (and have them verified) it is
necessary to first to go back to the qemu-simulator comparator
(test_sim.py), add the capability to the *Simulator* (ISACaller) to be
able to read instructions from a memory area, and then finally come
back to the hardware and do the same thing.
given that we need to be able to run the original unit tests as well
(the ones that just receive a list of instructions), this "listening
to PC" will have to be done as a mode, both by the simulator and by
the hardware.
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
* Re: [libre-riscv-dev] daily kan-ban update 16jun2020
From: Yehowshua @ 2020-06-17 13:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw+yM2iMw=+9ce9auO0VWsV8VYLB_Zm9gxTE-Zib0cxGw@mail.gmail.com>
Yesterday:
* Talked with Dan Leighton
Today
* still working on unit test for minerva cache
_______________________________________________
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] daily kan-ban update 16jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-17 13:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <557D0B89-201E-472F-AEEA-C827D0586D08@gatech.edu>
On Wed, Jun 17, 2020 at 2:35 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Yesterday:
>
> * Talked with Dan Leighton
>
> Today
>
> * still working on unit test for minerva cache
great. (today's the 17th btw :)
_______________________________________________
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] daily kan-ban update 17jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-17 13:41 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday:
* created an initial test instruction memory SRAM
* got a unit test running that reads from it
today:
* get the simulator (ISACaller) to read its instructions from a simulated memory
btw alain is getting 5.0.6 bugzilla running on apache2 via a proxy
redirect so that the REST API works, and we can actually finally
actually have a kan-ban board to look at.
---
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
page: next prev 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