Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-03-16 22:01 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=217

--- Comment #7 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)
> ok, jock, i thought about it: i have a specific task for you :)
> 
> * take benchs/nmigen/ALU16 and create (cut/paste) experiments7
>   in soclayout
> * in doAlu16.py, in each of add(), sub() and alu16(), *replace*
>   the hand-coded addition of Pins (Pin.create) with explicit
>   use of ChipConf from cumulus/src/plugins/chip/Configuration.py
> 
> the only thing to watch out for is that BLOCKAGE2 through BLOCKAGE5
> are added in add() and sub().  it *may* be necessary to create a
> separate function for that, we just have to see.
> 
> if necessary, for now, take a copy of Configuration.py and add it
> to experiments7 in the soclayout repo, so that you can edit it.
> or, better (preferred), subclass it.
> 
> just get stuck in, and see how that goes?

Luke and everybody,

I played with the example for several days, but I afraid I have no answers, but
only more questions.

First of all, I'm not sure what the result of the 'doAlu16.py' script should
be, and how running of the script relates to running 'make' with different
targets. I thought I can find some documents on this, but I couldn't.

I think the script is not working anyway. The most I can get out of it is

> [ERROR] NegociateWindow::createTrackSegment(): No track near axis of <id:7676 Horizontal b(15) METAL2 [320l 400l] [320l 400l] 2l rpD:0 ----UC---T-----ri-tt-> (after adjust).

Is something wrong with my setup?

Oh, and it was only after I fixed an error with forgotten import:

(~/alliance-check-tookit/benchs/nmigen/ALU16/doAlu16.py:523)
>     showPythonTrace( __file__, e, False )

but 'showPythonTrace()' is not defined.

I thought I could get something out of documentation, but it seems very scarce
to me. I could not find an API reference manual (neither Python nor C++), but
then I was starting to think it wouldn't help me either.

It also makes me wonder why all the examples are totally devoid of meaningful
comments or docstrings, as if they aren't meant for didactic purposes, but just
for spinning off new devices. Like boilerplates. Except they are too big for
boilerplates, and not exactly working.

I hope I was able to somehow address the issue of creating the layer Luke
mentions:

https://git.libre-riscv.org/?p=soclayout.git;a=blob;f=experiments7/doAlu16.py;hb=HEAD#l25

But otherwise I am lost. And the overall quality of the Python code I'm dealing
with in Coriolis makes me want to poke my eyes out. I'm terribly sorry if I
offended someone, but at the same time I'm sure I'm not the only one saying
this. I wonder why it is so bad and where to start improving it.

-- 
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] next tasks
From: Jacob Lifshay @ 2020-03-16 18:51 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <5CD6DF89-FF40-4732-9E42-1EB2092969B8@gatech.edu>

On Mon, Mar 16, 2020, 11:30 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> Also, I’d imagine in the future that we’d want to have speedy unit-testing
> etc etc, and considering ventilator offers multi-core support, we could see
> the speedup benefit of throwing our unit tests at a 64 core risen 3990x for
> example.
>

I'd be very surprised if it scales that far, that would usually require an
entirely different simulator architecture.

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] next tasks
From: Immanuel, Yehowshua U @ 2020-03-16 18:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4nb6AA0Anc2w1Rf5f6c6CFXYbqOrD4WyszqZHXOcMZfw@mail.gmail.com>


If we decide we don't want rpython, then I would suggest Rust — I’ve

Like I’ve mentioned before, I’m all for Rust.
If I remember correctly, we’re implementing POWER 3.0 and Gem5 only has support for 2.7(2.7 and 3.0 - wow sounds like Python versions :)…

Anyways, one thing we should strongly consider making the simulator take advantage of multiple cores.

Honestly, we could implement a single cycle CPU in RTL and the compile it into C++ with Verilator.
To me, this seems to be the way to go.

1. Verilator Creates quite speedy cycle accurate C++ models
2. RTL is a really natural way to describe a CPU - duh
3. A single cycle CPU is about 3 - 4 days worth of labor
4. If we did the Single cycle CPU reference simulator in BSV for example, it’d simulate even faster than it would in verilator

I know using an RTL implementation of a CPU to test other RTL implementations seems unatural, but if we’d want to catch errors like pipeline and flushing behaviors in our CPU, then what makes more sense than a single cycle reference?

Also, I’d imagine in the future that we’d want to have speedy unit-testing etc etc, and considering ventilator offers multi-core support, we could see the speedup benefit of throwing our unit tests at a 64 core risen 3990x for example.

@Lauri, Jacob, and Luke - Thoughts and Comments?

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

* [libre-riscv-dev] [Bug 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-16 17:25 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=216

--- Comment #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
could everyone just have a look at this and see if i've got it right:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/addr_match.py;h=0312504eb818c5e77d8a85d3948f733663b34b2e;hb=182e4cd214022a8ce0a498c2ceeca223a282f329

the idea is as described: turn the last 4 bits of the address, plus the
length (1,2,4,8 bytes) into a bitmap, equal in length to a cache line
(actually, 2 cache lines) i.e. 2x 16-bits

then you do *unary* bit-wise compare on those, but *binary* compare on
the remainder of the address.

the tricky bit is that the roll-over (misaligned on a 16-byte boundary)
will need *three* compares:

* address-equal, compare 1st cache line (16 LSBs of the bitmap)
* 1st address PLUS ONE equal to *2nd* address:
  - compare 8 bytes of 1st address's SECOND cache line (bits 16-23) with
    first 8 bytes of 2nd address's FIRST cache line (bits 0-7)
* reverse - *2nd* address PLUS ONE equal to 1st address
  - likewise reverse on bitmap.

confusing as hell, hence why it needs checking.

-- 
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] [OT] Minecraft garbage collection
From: Luke Kenneth Casson Leighton @ 2020-03-16 16:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD66SdbQwh+q-E5PPaCBKn1B=AGgKBbkqCpNULBp5HtGGA@mail.gmail.com>

On Mon, Mar 16, 2020 at 4:22 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> That's a good idea, however, the version (0.7) that is more than just a
> simple toy only uses OpenGL [ES] since it predates Vulkan and I stopped
> working on it several years ago to work on newer versions, additionally,
> the graphics it generates is simple enough that it can run with full
> graphics effects on OpenGL 1.5, so it wouldn't stress that many codepaths
> in the Vulkan driver.

awww, i quite liked it :)

> I think a better idea is to use the Vulkan demo programs written by Sasha
> Willems since the programs do some pretty complex graphics stuff with
> really fancy shaders:
> https://github.com/SaschaWillems/Vulkan

niiice.

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] [OT] Minecraft garbage collection
From: Jacob Lifshay @ 2020-03-16 16:22 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwm-200POBES18grkwVKwxbo9uo3JLkn_8DVDK6Y8AMBw@mail.gmail.com>

On Mon, Mar 16, 2020, 06:23 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Sun, Mar 15, 2020 at 12:11 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > On Sun, Mar 15, 2020 at 6:41 AM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > > Pretty pictures: https://hackaday.io/project/7018/gallery
> >
> > oooo :)
>
> i thought about this, and realised that, actually, we need a (full) 3D
> test application... that *you* understand, jacob.  might as well be
> this one.  so we could - in a roundabout way - actually justify at
> least using it and, if anything needs fixing, include its improvement
> as part of any test suite augmentation.
>

That's a good idea, however, the version (0.7) that is more than just a
simple toy only uses OpenGL [ES] since it predates Vulkan and I stopped
working on it several years ago to work on newer versions, additionally,
the graphics it generates is simple enough that it can run with full
graphics effects on OpenGL 1.5, so it wouldn't stress that many codepaths
in the Vulkan driver.

I think a better idea is to use the Vulkan demo programs written by Sasha
Willems since the programs do some pretty complex graphics stuff with
really fancy shaders:
https://github.com/SaschaWillems/Vulkan

The CPU-side code is actually quite straightforward if you are familiar
with the Vulkan API.

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] [OT] Minecraft garbage collection
From: Luke Kenneth Casson Leighton @ 2020-03-16 13:22 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw4Yj4FnB3pcCsHdrsT7GjZHRdszh7z6vjz1Pth1LT0FQ@mail.gmail.com>

On Sun, Mar 15, 2020 at 12:11 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Sun, Mar 15, 2020 at 6:41 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > Pretty pictures: https://hackaday.io/project/7018/gallery
>
> oooo :)

i thought about this, and realised that, actually, we need a (full) 3D
test application... that *you* understand, jacob.  might as well be
this one.  so we could - in a roundabout way - actually justify at
least using it and, if anything needs fixing, include its improvement
as part of any test suite augmentation.

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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Staf Verhaegen @ 2020-03-16 11:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <20200316112700.bef98590e39c27ae3b1cb63d@gmx.com>

[-- Attachment #1.1: Type: text/plain, Size: 680 bytes --]

Lauri Kasanen schreef op ma 16-03-2020 om 11:27 [+0200]:
> On Mon, 16 Mar 2020 09:53:38 +0100Staf Verhaegen <staf@fibraservi.eu> wrote:
> > Lauri Kasanen schreef op ma 16-03-2020 om 09:14 [+0200]:
> > > 486 and 586 patents had expired years ago, and we had Chinese 1 GHzimplementations of those (vortex86). Now they have 686 models, so Itake pentium pro patents are also up for use.
> > 
> > I think these were because Via had cross-patent license agreement with Intel.
> 
> DMP is not related to VIA. Via's C and Nano lines happened muchearlier, with the licensing.

I stand corrected; it was SiS which did the first Vortex86 and sold that line to DM&P.

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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-16 10:34 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200316112700.bef98590e39c27ae3b1cb63d@gmx.com>

https://github.com/power-gem5
this boots a 64-bit BE linux kernel, plus a basic initramfs and has
telnet in to the console.
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 241] OpenPOWER SImulation is needed of standards
From: bugzilla-daemon @ 2020-03-16  9:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-241-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=241

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
thanks to hugh, he pointed me in the direction of this:
https://github.com/power-gem5

it works however it leaks memory like a sieve

-- 
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Lauri Kasanen @ 2020-03-16  9:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <b096323f4ec162fed13b590ec9acd9899a5c120c.camel@fibraservi.eu>

On Mon, 16 Mar 2020 09:53:38 +0100
Staf Verhaegen <staf@fibraservi.eu> wrote:

> Lauri Kasanen schreef op ma 16-03-2020 om 09:14 [+0200]:
> > 486 and 586 patents had expired years ago, and we had Chinese 1 GHzimplementations of those (vortex86). Now they have 686 models, so Itake pentium pro patents are also up for use.
>
> I think these were because Via had cross-patent license agreement with Intel.

DMP is not related to VIA. Via's C and Nano lines happened much
earlier, with the licensing.

- 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

* Re: [libre-riscv-dev] video about open source & endurance
From: Luke Kenneth Casson Leighton @ 2020-03-16  9:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5N2wmmunUF38Dj4goMdN7O72wJhOXz_eR1h98FBiYL4w@mail.gmail.com>

On Mon, Mar 16, 2020 at 1:30 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

> no, that's correct. it's talking about how things from back then were
> designed to last a long time and how modern proprietary computing stuff is
> not and how open source software is more likely to last a long time.

i know someone who does long-term support on hardware designs.   20
years and above.

he *only* uses software libre PCB CAD packages.

why?

because he takes the *entire* source code - of the entire operating
system - not just the PCB CAD packages (KiCAD usually) - the entire
*operating system* - snapshotting absolutely everything.

why?

because in 15 years time, the way that modern computing is going, the
possibility of being able to successfully run that PCB CAD software,
developed 15 years ago, and fix any PCB issues for the customer, is
extremely remote bordering on negligeable.

and that's even in the open source community.

you will also be keenly aware that the open source community
completely fails to respect and honour "version compatibility and
upgradeability".

so do not buy the kool-aid that open source is and will be
"compatible".  yes it will be around, however the chances of being
able to successfully run even a version of a tool from 6 months ago
let alone 15 years is extremely borderline.

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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Staf Verhaegen @ 2020-03-16  8:53 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <20200316091420.15087a26fab1be3d5fc23953@gmx.com>

[-- Attachment #1.1: Type: text/plain, Size: 680 bytes --]

Lauri Kasanen schreef op ma 16-03-2020 om 09:14 [+0200]:
> On Sun, 15 Mar 2020 12:43:45 -0700Jacob Lifshay <programmerjake@gmail.com> wrote:
> > Later (for Libre-SOC v2 or v3), it might be a good idea to add support forx86 and x86_64 user-mode since the patents for the base ISA will haveexpired by then. This would help give us an advantage since it would allowus to run legacy software.
> 
> 486 and 586 patents had expired years ago, and we had Chinese 1 GHzimplementations of those (vortex86). Now they have 686 models, so Itake pentium pro patents are also up for use.

I think these were because Via had cross-patent license agreement with Intel.

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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Jacob Lifshay @ 2020-03-16  7:28 UTC (permalink / raw)
  To: Lauri Kasanen; +Cc: Libre-RISCV General Development
In-Reply-To: <20200316091420.15087a26fab1be3d5fc23953@gmx.com>

On Mon, Mar 16, 2020, 00:13 Lauri Kasanen <cand@gmx.com> wrote:

> On Sun, 15 Mar 2020 12:43:45 -0700
> Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > Later (for Libre-SOC v2 or v3), it might be a good idea to add support
> for
> > x86 and x86_64 user-mode since the patents for the base ISA will have
> > expired by then. This would help give us an advantage since it would
> allow
> > us to run legacy software.
>
> 486 and 586 patents had expired years ago, and we had Chinese 1 GHz
> implementations of those (vortex86). Now they have 686 models, so I
> take pentium pro patents are also up for use.
>
> x86_64 should become free around 2022 by my estimation.
>

The amd64 spec was first published in august 2000 according to wikipedia,
so that may mean the base ISA patents expire in 2020.

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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Lauri Kasanen @ 2020-03-16  7:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7fz6_KfymY5kMTFojHQsrmTGC2XZ958F1ju7s6tg-91A@mail.gmail.com>

On Sun, 15 Mar 2020 12:43:45 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:

> Later (for Libre-SOC v2 or v3), it might be a good idea to add support for
> x86 and x86_64 user-mode since the patents for the base ISA will have
> expired by then. This would help give us an advantage since it would allow
> us to run legacy software.

486 and 586 patents had expired years ago, and we had Chinese 1 GHz
implementations of those (vortex86). Now they have 686 models, so I
take pentium pro patents are also up for use.

x86_64 should become free around 2022 by my estimation.

- 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

* Re: [libre-riscv-dev] video about open source & endurance
From: Jacob Lifshay @ 2020-03-16  1:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <DD7C25A6-90EF-4976-9C8E-64EDFC11C7E5@gatech.edu>

On Sun, Mar 15, 2020, 18:24 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> An iron fireman?
> Did you mean to send something different?
>

no, that's correct. it's talking about how things from back then were
designed to last a long time and how modern proprietary computing stuff is
not and how open source software is more likely to last a long time.

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] video about open source & endurance
From: Immanuel, Yehowshua U @ 2020-03-16  1:29 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <DD7C25A6-90EF-4976-9C8E-64EDFC11C7E5@gatech.edu>

Oh! He’s setting technological longevity as the standard by which to measure software progress. Got it.

Level1 tech- he also reverse engineered TB3 I believe and wrote AMD drivers before intel opened up TB3 to AMD.

Sent from my iPad
_______________________________________________
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] video about open source & endurance
From: Immanuel, Yehowshua U @ 2020-03-16  1:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6Vf-769p8zbA7k2gEwiBdZo8AgpDRp8d2uZNZziTTN2w@mail.gmail.com>

An iron fireman?
Did you mean to send something different?

Sent from my iPad

_______________________________________________
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Immanuel, Yehowshua U @ 2020-03-16  0:25 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz5_tursqTv6=V1J2JdmoC5MyFS7sD_W-wufRqUR+VNfA@mail.gmail.com>


Haha, lets just wait until we’ve got some customers before pulling that stunt.
Also, literally, everybody including MS, Amazon, Apple, would be on our side.

Bad news for intel...

Sent from my iPad
_______________________________________________
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] video about open source & endurance
From: Jacob Lifshay @ 2020-03-15 23:05 UTC (permalink / raw)
  To: Libre-RISCV General Development

found this interesting:

https://youtu.be/Ck9nMq1D_BU

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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Luke Kenneth Casson Leighton @ 2020-03-15 22:32 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <cfa98578-64b2-2778-48b4-25e2492ebc9d@vany.ca>

On Sun, Mar 15, 2020 at 10:23 PM Adam Van Ymeren <adam@vany.ca> wrote:

> Technically they'll have an easy time suing you.

so... how would that go?  what do you think the headline news would
be?  and what would the EFF, FSF and the SFLC's response be if we
asked them for help?  have a guess... :)

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 259] can't set "parent bug budget"
From: bugzilla-daemon @ 2020-03-15 22:30 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-259-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=259

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ohh ok so when i added new milestones they were of course "inactive".
ok thanks.

-- 
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 259] can't set "parent bug budget"
From: bugzilla-daemon @ 2020-03-15 22:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-259-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=259

Jacob Lifshay <programmerjake@gmail.com> changed:

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

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
I had enabled where the field only appears when the nlnet milestone is set,
however that works by individually enabling for each milestone. I enabled the
two new milestones so it should work now.

See "Field only appears when:" in
http://bugs.libre-riscv.org/editfields.cgi?action=edit&name=cf_budget_parent

-- 
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] LibreSOC - RISCV and POWER dual architecture feasibility
From: Adam Van Ymeren @ 2020-03-15 22:23 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAC2bXD6RAdzQ9w1+54PapjH4HnYewGVDp7jtDs1xAAk_efJEWw@mail.gmail.com>


On 2020-03-15 6:10 p.m., Jacob Lifshay wrote:
> On Sun, Mar 15, 2020, 15:04 Staf Verhaegen <staf@fibraservi.eu> wrote:
>
>> If you consider implementing x86 instruction set you also need to
>> consider the risk of patent lawsuits being filed at you...
>>
> that's true, but if you only implement the parts where all the patents have
> expired, then they'll have a hard time suing you for patent infringement.

Technically they'll have an easy time suing you.  Its easy to sue anyone
for anything.  They may have a hard time winning however.

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

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 259] New: can't set "parent bug budget"
From: bugzilla-daemon @ 2020-03-15 22:21 UTC (permalink / raw)
  To: libre-riscv-dev

http://bugs.libre-riscv.org/show_bug.cgi?id=259

            Bug ID: 259
           Summary: can't set "parent bug budget"
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

http://bugs.libre-riscv.org/show_bug.cgi?id=248
jacob wassup here, i can only set a parent bugnumber when the NLNet milestone
is 2019-10-02?

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