Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] daily kan-ban update 03jun2020
From: Jacob Lifshay @ 2020-06-04  0:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwOG8gQWh_CbrHkmWj1LVaoUc8mCdVDwvkDAze++JnvUQ@mail.gmail.com>

continuing working on the div and mul pipelines

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] using a stage chain in a stage
From: Luke Kenneth Casson Leighton @ 2020-06-04  1:20 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6Znt5PPj6n22eRV-fnGt6kdRotWFKeX2uxDcm3T57rLw@mail.gmail.com>

On Thursday, June 4, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> I'm trying to build the div pipe, however, the ispec and ospec need to
> be different than the currently existing code since that is FP
> specific, there needs to be additional io signals that are not
> included in all the FP*Data classes. Additionally, I don't want to
> just overwrite the existing FPDiv pipe code since I'm not planning on
> adding FP div support right away, and the code needs to be refactored
> somewhat since the FPdiv pipe code is currently generic over being
> 16/32/64-bit at compile-time and the new code will need to be able to
> dynamically switch between them at runtime, once FP is added again.


ah we're not doing dynamic partitioning.  we are doing 64 bit only,
standard POWER9 and will refactor later.





>
> Luke, or whoever's available, can you give me an example of a
> combinatorial stage chain that is used inside a single stage without
> being wired as the inputs and outputs, along with getting all the
> pipekls stuff connected properly?


i placed a cookie cut version here already:


https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/div/pipeline.py;hb=HEAD

ctx will automatically pick up the context, which contains op, which is the
operand data structure.  you should stick with CompALUSubset for now.



> Somewhat unrelated, I moved all the unused code out of the fpdiv
> folder and into the unused folder


ah good, ok.

 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] using a stage chain in a stage
From: Jacob Lifshay @ 2020-06-04  1:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwvg1bQ9MLxrk660J9v_DwssibnkYtyFJ_Mqvf-6NN_cg@mail.gmail.com>

On Wed, Jun 3, 2020 at 6:20 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Thursday, June 4, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > I'm trying to build the div pipe, however, the ispec and ospec need to
> > be different than the currently existing code since that is FP
> > specific, there needs to be additional io signals that are not
> > included in all the FP*Data classes. Additionally, I don't want to
> > just overwrite the existing FPDiv pipe code since I'm not planning on
> > adding FP div support right away, and the code needs to be refactored
> > somewhat since the FPdiv pipe code is currently generic over being
> > 16/32/64-bit at compile-time and the new code will need to be able to
> > dynamically switch between them at runtime, once FP is added again.
>
>
> ah we're not doing dynamic partitioning.  we are doing 64 bit only,
> standard POWER9 and will refactor later.

I'd assume, once we add FP support again, you want to support more
than just fp64, fp32 and fp16 would be nice too even if not
dynamically partitioned. :)

> > Luke, or whoever's available, can you give me an example of a
> > combinatorial stage chain that is used inside a single stage without
> > being wired as the inputs and outputs, along with getting all the
> > pipekls stuff connected properly?
>
>
> i placed a cookie cut version here already:
>
>
> https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/div/pipeline.py;hb=HEAD
>
> ctx will automatically pick up the context, which contains op, which is the
> operand data structure.  you should stick with CompALUSubset for now.

Ok, so I guess the idea is to not use the ieee754.fpdiv code for now
and just write a whole bunch of new code that uses
ieee754.div_rem_sqrt_rsqrt?

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] using a stage chain in a stage
From: Luke Kenneth Casson Leighton @ 2020-06-04  1:32 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwvg1bQ9MLxrk660J9v_DwssibnkYtyFJ_Mqvf-6NN_cg@mail.gmail.com>

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/div/pipe_data.py;hb=HEAD

sorry, CompLogicalOpSubset.  unless carry-in, sticky overflow etc are
needed, which i don't think they are.

each subset grabs only the fields from the instruction decode
(Decode2Execute1Type) that the pipeline actually needs.

that subset is supposed to be dropped into ctx.op, see IntegerData class.
all ospec and ispec classes derive from IntegerData at the moment.

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] using a stage chain in a stage
From: Luke Kenneth Casson Leighton @ 2020-06-04  1:37 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD61vK0OXNCuO-ccHWENoNvucssG8+MiwiJ60ivj9Jzp0Q@mail.gmail.com>

On Thursday, June 4, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Wed, Jun 3, 2020 at 6:20 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > On Thursday, June 4, 2020, Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > > I'm trying to build the div pipe, however, the ispec and ospec need to
> > > be different than the currently existing code since that is FP
> > > specific, there needs to be additional io signals that are not
> > > included in all the FP*Data classes. Additionally, I don't want to
> > > just overwrite the existing FPDiv pipe code since I'm not planning on
> > > adding FP div support right away, and the code needs to be refactored
> > > somewhat since the FPdiv pipe code is currently generic over being
> > > 16/32/64-bit at compile-time and the new code will need to be able to
> > > dynamically switch between them at runtime, once FP is added again.
> >
> >
> > ah we're not doing dynamic partitioning.  we are doing 64 bit only,
> > standard POWER9 and will refactor later.
>
> I'd assume, once we add FP support again, you want to support more
> than just fp64, fp32 and fp16 would be nice too even if not
> dynamically partitioned. :)


:)

the problem comes when the dynamic repartitioning hits mantissa and
exponents that *change* in bitsize.

believe it or not, IBM actually do this in their POWER9 core.  paritioned
FP.

Michael and i looked at this and it means statically allocating the largest
size of mantissa and exponent signals then ignoring *parts* of those bits
depending on the exponent sizes etc. dynamically.

it all got horribly complicated for shift and we left it for now.




>
> > > Luke, or whoever's available, can you give me an example of a
> > > combinatorial stage chain that is used inside a single stage without
> > > being wired as the inputs and outputs, along with getting all the
> > > pipekls stuff connected properly?
> >
> >
> > i placed a cookie cut version here already:
> >
> >
> > https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/
> div/pipeline.py;hb=HEAD
> >
> > ctx will automatically pick up the context, which contains op, which is
> the
> > operand data structure.  you should stick with CompALUSubset for now.
>
> Ok, so I guess the idea is to not use the ieee754.fpdiv code for now
> and just write a whole bunch of new code that uses
> ieee754.div_rem_sqrt_rsqrt?


yes exactly.

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 03jun2020
From: Cole Poirier @ 2020-06-04  3:46 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDy2pa63GJDPG7Ak_0KqgyQ6gbXknJARaCwEKH9fTbRgOQ@mail.gmail.com>

On Jun 3 2020, at 5:32 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Thu, Jun 4, 2020 at 1:09 AM Cole Poirier <colepoirier@gmail.com> wrote:
> 
>> Yes sorry about that, part was intentional, which I see now was clearly
>> a silly thing to do, the other part was that I managed to really mess up
>> the 'resolution' of merge conflicts.
> 
> your responsibility to sort out :)

I think I have, but we shall see...
 
> welcome to working on the same file.
> 
> suggestion: do regular "git pulls".  this doesn't work with rebase, so
> you have to use "git stash" followed by "git pull" followed by "git
> stash apply" and then work it out from there.
> 
> or you can use "git stash show -p {0}" (after doing "git stash list"
> to find the right one) prior to "git stash apply" and that will give
> you the diff before applying it.
> 
> which.... if you want, you can pipe that diff into a file, then use
> "patch", which has the advantage of putting rejected patches into
> ".rej" files, which you can then manually sort out.
> 
> l.

Ooooh, this is very cool, will be 'bookmarking' this for future use.

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] daily kan-ban update 03jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-04 11:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <DE69CBB7-67F9-41E3-9846-6864E35E0413@getmailspring.com>

On Thu, Jun 4, 2020 at 4:46 AM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Jun 3 2020, at 5:32 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > On Thu, Jun 4, 2020 at 1:09 AM Cole Poirier <colepoirier@gmail.com> wrote:
> >
> >> Yes sorry about that, part was intentional, which I see now was clearly
> >> a silly thing to do, the other part was that I managed to really mess up
> >> the 'resolution' of merge conflicts.
> >
> > your responsibility to sort out :)
>
> I think I have, but we shall see...
>
> > welcome to working on the same file.

btw, another thing: if you're constantly running into commit
conflicts, it means that you're "panicking and omg omg i can't
possibly commit this i need to leave it a few days because i'm not
confident omg it might not work might damage something omg omg argh
argh"

do a small change, commit it immediately, push it immediately.

do another small change, commit it immediately, push it immediately.

if you were working last night, and committed something without
pushing it, you'll now find that you have another conflict to resolve,
because i've replaced all of the long signal names with the
convenience variables.

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 04jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-04 12:10 UTC (permalink / raw)
  To: Libre-RISCV General Development

yesterday:

* brief review of Cole's TRAP pipeline work (looks good, more comments added)
* helped Jacob point in right direction (int div pipeline stages
needed, FP is out)
* converted some more MultiCompUnit unit tests to shared code with
test_pipe_caller(s)
* started on a "Simple" (brain-dead) core and connecting up read-ports

morning:

* investigating sorting out internet connectivity.  currently have to
bypass ISP HTTPS traffic blocks by using an HTTPS proxy over a VPN
(!).  the majority of major web sites (zoom, accounts.google.com,
instagram)

* connecting up write-ports to brain-dead core.

today:

* checking the new brain-dead core and running a first unit test
against it, see if it actually reads/writes to/from regfiles.

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 04jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-04 13:32 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzHERzHaawmeEui+jtuL_MLWg=raBgix5PCco+zS3gtdQ@mail.gmail.com>

On Thu, Jun 4, 2020 at 1:10 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> * checking the new brain-dead core and running a first unit test
> against it, see if it actually reads/writes to/from regfiles.

it does actually read and write regfiles.  tested with ALU operations
as well as Logical ones, so far.

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 362] New: improvements to nmigen and yosys
From: bugzilla-daemon @ 2020-06-04 13:40 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 362
           Summary: improvements to nmigen and yosys
           Product: Libre-SOC's first SoC
           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: ---

improvements to nmigen and yosys are needed, including CXXSim, a
new backend for yosys that allows a 20 to 100x performance increase
in simulation speed.

-- 
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 175] NLNet 2019 Wishbone proposal 2019-10-043
From: bugzilla-daemon @ 2020-06-04 13:41 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-175-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
 total budget (EUR)|26000                       |36000
  for completion of|                            |
       task and all|                            |
           subtasks|                            |

-- 
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 362] improvements to nmigen and yosys
From: bugzilla-daemon @ 2020-06-04 13:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-362-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
    NLnet milestone|---                         |NLNet.2019.10.Wishbone
 total budget (EUR)|0                           |10000
  for completion of|                            |
       task and all|                            |
           subtasks|                            |
    parent task for|                            |175
  budget allocation|                            |

-- 
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] daily kan-ban update 04jun2020
From: Tobias Platen @ 2020-06-04 15:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDxM0DQTM+MQ0=mQnmhW6X=xCv6Ogi73cKxSzbRPoVVZ7g@mail.gmail.com>

morning: thinking ways how to implement DualPortSplitter

rest of the day: looking into the new NonProductionCore class and its test case

tomorrow: implement DualPortSplitter

_______________________________________________
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-06-04 16:49 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

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

--- Comment #55 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
proof_datamerger.py:

                for b in range(0,8):

just range(8).  there is no need to specify a start range of 0

            comb += dut.addr_array_i[j].eq(AnySeq(dut.array_size))
            comb += dut.data_i[j].eq(AnySeq(16+128))

AnySeq is for synchronous data where the value changes on every clock.
use AnyConst instead which will not change.

-- 
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] daily kan-ban update 04jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-04 16:51 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200604170008.37195181180cf07952445434@platen-software.de>

On Thu, Jun 4, 2020 at 4:00 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> morning: thinking ways how to implement DualPortSplitter

it's already partly implemented by LDSTSplitter.

i need to focus on debugging at the moment, i'll be able to
context-switch to this tomorrow.

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] daily kan-ban update 04jun2020
From: Jacob Lifshay @ 2020-06-04 18:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzHERzHaawmeEui+jtuL_MLWg=raBgix5PCco+zS3gtdQ@mail.gmail.com>

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

> * investigating sorting out internet connectivity.  currently have to
> bypass ISP HTTPS traffic blocks by using an HTTPS proxy over a VPN
> (!).  the majority of major web sites (zoom, accounts.google.com,
> instagram)
>

wow! would motivate me to get a different ISP if possible, that's garbage
tier service if that's not just a temporary problem.

today:
work on div and mul pipelines
read through cxxrtl yosys backend that whitequark's been writing, found a
bug:
https://github.com/YosysHQ/yosys/issues/2111

attending OpenPower virtual coffee meeting later

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] daily kan-ban update 04jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-04 19:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5Kc4P+X5u=-fbJt8cvjtwyKtsrBZorw8c9y=TMpfQ8qw@mail.gmail.com>

On Thursday, June 4, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Thu, Jun 4, 2020, 05:11 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > * investigating sorting out internet connectivity.  currently have to
> > bypass ISP HTTPS traffic blocks by using an HTTPS proxy over a VPN
> > (!).  the majority of major web sites (zoom, accounts.google.com,
> > instagram)
> >
>
> wow! would motivate me to get a different ISP if possible, that's garbage
> tier service if that's not just a temporary problem.
>
>
the timing is exactly when you also had issues.

they are GBP 20 a month for unlimited data, on mobile 4G/LTE.

the data usage in our house is over 200MB a month.

it would cost us well over USD 150 a month by any other provider.

there is no hardline and it is not my house.



> today:
> work on div and mul pipelines


great.  i have the dumb-core operational (no instruction fetch, no LDST),
so when they're ready they can drop straight in.



> read through cxxrtl yosys backend that whitequark's been writing, found a
> bug:
> https://github.com/YosysHQ/yosys/issues/2111


cool.  that's some complex code.


> attending OpenPower virtual coffee meeting later


ah it's not running tonight.  hugh has a scheduling conflict.

next week.

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] [Bug 363] New: inconsistency between isel and mfcr unit test on bit-ordering of CR
From: bugzilla-daemon @ 2020-06-04 19:51 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 363
           Summary: inconsistency between isel and mfcr unit test on
                    bit-ordering of CR
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            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: ---

very weird.

when storing the bits in the CR (full_cr vs individual CRs) the ordering
is wrong.

-- 
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 363] inconsistency between isel and mfcr unit test on bit-ordering of CR
From: bugzilla-daemon @ 2020-06-04 19:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-363-13@https.bugs.libre-soc.org/>

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

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

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
*sigh*.  Because POWER.

-- 
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] daily kan-ban update 04jun2020
From: Yehowshua @ 2020-06-04 20:15 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyW_CYyeg5wnEZNKRRZZJRumx3UnHWerGsGL03NEfjgtg@mail.gmail.com>


> On Jun 4, 2020, at 3:02 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> the timing is exactly when you also had issues.
> 
> they are GBP 20 a month for unlimited data, on mobile 4G/LTE.
> 
> the data usage in our house is over 200MB a month.
> 
> it would cost us well over USD 150 a month by any other provider.
> 
> there is no hardline and it is not my house.

Fortunately for you, Elon Musk is planning to launch Stalins
this winter. Merry Christmas.

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] daily kan-ban update 04jun2020
From: Yehowshua @ 2020-06-04 20:15 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <E7A0D9DE-E072-4698-ABE4-10B8E9D4AC96@gatech.edu>

**starlink

_______________________________________________
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 04jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-04 20:25 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <144168D9-31BB-4321-904E-0546EEA4F6CA@gatech.edu>

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

> **starlink


you were probably right the first time :)

i heard that people were shooting down google blimps, hacking the hardware
to get it to serve *their* local community needs, patching up the holes and
sending them back up.

can't exactly do that with a satellite, oh well

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] [Bug 363] inconsistency between isel and mfcr and crand unit test on bit-ordering of CR
From: bugzilla-daemon @ 2020-06-04 20:52 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-363-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
            Summary|inconsistency between isel  |inconsistency between isel
                   |and mfcr unit test on       |and mfcr and crand unit
                   |bit-ordering of CR          |test on bit-ordering of CR
             Status|RESOLVED                    |CONFIRMED

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
reopening.  crand inconsistency as well.

-- 
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] daily kan-ban update 03jun2020
From: Cole Poirier @ 2020-06-04 22:24 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxGLYbpPs7Ju9iMXWYD6iq-HunNCCL8LgSvazjyu8Chig@mail.gmail.com>

On Jun 4 2020, at 4:02 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> On Thu, Jun 4, 2020 at 4:46 AM Cole Poirier <colepoirier@gmail.com> wrote:
>> 
>> On Jun 3 2020, at 5:32 pm, Luke Kenneth Casson Leighton
>> <lkcl@lkcl.net> wrote:
>> > On Thu, Jun 4, 2020 at 1:09 AM Cole Poirier <colepoirier@gmail.com> wrote:
>> >
>> >> Yes sorry about that, part was intentional, which I see now was clearly
>> >> a silly thing to do, the other part was that I managed to really
>> mess up
>> >> the 'resolution' of merge conflicts.
>> >
>> > your responsibility to sort out :)
>> 
>> I think I have, but we shall see...
>> 
>> > welcome to working on the same file.
> 
> btw, another thing: if you're constantly running into commit
> conflicts, it means that you're "panicking and omg omg i can't
> possibly commit this i need to leave it a few days because i'm not
> confident omg it might not work might damage something omg omg argh
> argh"
> 
> do a small change, commit it immediately, push it immediately.
> 
> do another small change, commit it immediately, push it immediately.
> 
> if you were working last night, and committed something without
> pushing it, you'll now find that you have another conflict to resolve,
> because i've replaced all of the long signal names with the
> convenience variables.
> 
> l.

Not to worry, you helped me break the bad habit of not committing
immediately a few weeks ago :) Was just that we were working on the same
file within 15 min of each other.

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] daily kan-ban update 04jun2020
From: Cole Poirier @ 2020-06-04 22:28 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDzHERzHaawmeEui+jtuL_MLWg=raBgix5PCco+zS3gtdQ@mail.gmail.com>

On Jun 4 2020, at 5:10 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> yesterday:
> 
> * brief review of Cole's TRAP pipeline work (looks good, more comments added)

Thanks Luke, it's really helping me get work done and make progress each
day, and hopefully being able to do so a bit more independently than
last week.

Today:

Review Luke's comments and TODOs in TRAP pipeline, implement required changes.

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

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