* [libre-riscv-dev] [Bug 340] formal proof of POWER9 SHIFTROT pipeline needed
From: bugzilla-daemon @ 2020-05-27 14:21 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-340-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=340
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=343
--
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 343] compalu_multi write requests need to hook into Data.ok
From: bugzilla-daemon @ 2020-05-27 14:21 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-343-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=343
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=340
--
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 343] compalu_multi write requests need to hook into Data.ok
From: bugzilla-daemon @ 2020-05-27 14:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-343-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=343
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=332
--
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 332] Formal correctness proof needed for CR pipeline
From: bugzilla-daemon @ 2020-05-27 14:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=332
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=343
--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
spotted that the CR proof needs to check Data.ok, currently doing that now.
the reason we "get away" with things working right now is because assigning
a Signal to a Record is done in a bit-wise fashion. the extra bit (Data.ok)
is therefore totally ignored, not just when assigned, but also in the formal
proofs.
--
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 306] Formal Correctness Proof for ALU pipeline
From: bugzilla-daemon @ 2020-05-27 14:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-306-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=306
--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #6)
> (In reply to Luke Kenneth Casson Leighton from comment #5)
> > 70 comb += Assume(a[32:64] == 0)
> > 71 comb += Assume(b[32:64] == 0)
> >
> > michael in the alu proof should those be conditional? with m.If(op.is_32bit)?
>
> oh, yep. Fixed.
star.
--
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 306] Formal Correctness Proof for ALU pipeline
From: bugzilla-daemon @ 2020-05-27 14:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-306-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=306
--- Comment #6 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #5)
> 70 comb += Assume(a[32:64] == 0)
> 71 comb += Assume(b[32:64] == 0)
>
> michael in the alu proof should those be conditional? with m.If(op.is_32bit)?
oh, yep. Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 306] Formal Correctness Proof for ALU pipeline
From: bugzilla-daemon @ 2020-05-27 13:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-306-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=306
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
70 comb += Assume(a[32:64] == 0)
71 comb += Assume(b[32:64] == 0)
michael in the alu proof should those be conditional? with m.If(op.is_32bit)?
--
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] POWER9 formal correctness proofs collaboration
From: Luke Kenneth Casson Leighton @ 2020-05-27 13:12 UTC (permalink / raw)
To: openpower-hdl-cores; +Cc: Libre-RISCV General Development
example:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/alu/formal/proof_main_stage.py;hb=HEAD
one of the critical aspects of LibreSOC is that we do not want to be the
ones who declare our code to be "correct" to our customers: we want our
customers to be in a position to independently confirm it for themselves,
at every level.
consequently, we have to develop Formal Correctness proofs not as an
afterthought but as part of the real time day to day development process.
this leaves behind a morass of code that, strategically, is of enormous
value to other teams.
yet because of there being no defined interfaces, we are "getting on with
it" and consequently the code is designed to interface to LibreSOC's
internal data structures.
as thinge stand, other teams, therefore, would need to do quite a lot of
work before being able to take advantage of the proofs.
in RISC-V, SymbioticEDA set about defining a de-facto industry standard
interface, through which access to the internals of the core to be tested
could "plug in" any given Formal Proof. full access to registers,
pipelines, instructions, memory subsystem, everything, in a well-defined
fashion.
https://github.com/SymbioticEDA/riscv-formal/blob/master/docs/rvfi.md
would anyone like to collaborate on defining a similar such interface, for
POWER9 teams to be able to formally validate their cores?
if so, we have tax deductible donations from NLNet if code is written that
happens to be directly useable for our project. if we take EUR as the
unit, i believe there are up to around 9,000 such gifts available :)
also, second question, has a Compliance Working Group (and mailing list)
been established, as this is the kind of thing that should probably be
raised there (defining an interface, that is).
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] daily kan-ban update 27may2020
From: Luke Kenneth Casson Leighton @ 2020-05-27 12:25 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday:
* altered VirtualRegPort to simplify it and got a proof of concept unit
test, enough to be happy to move on
* added CR and XER regfiles (using VirtualRegPort) and also a Fast Regfile
(PC, LR, CTR, MSR). the Fast regfile is going to be a handful. 3R3W (maybe
more), no way we can use SRAMs.
morning:
* reviewed Tobias's DataMerger class. principle looks good.
* answered Cole about regfile proofs. we work on them together.
* reviewed Systemes Libre Company.
today:
* collaborate with Cole with regfile proofs
* help Cesar with parallel compunit test
* read proof_fu.py again
* do a unit test similar to test_pipe_caller.py which uses MultiCompUnit
derivatives.
--
---
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-27 11:14 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #1)
> Made some very minimal progress on this today. Since I'm still learning how
> to write proofs it takes a long time to get the most basic assumptions of
> the most basic class (Register) from regfile.py sorted enough that I can
> start to reason about them. I think the foundation that I laid today will
> enable me to write some code for this (instead of just written notes from
> working and reasoning through the assumptions of the module) tomorrow. But,
> if this proof is needed before then for the virtual_port tests,
it's not. i have a preliminary virtual_port test running, yesterday.
> Luke please
> feel free to take it over like you did with virtual_port today. I want to
> help, so I don't want my learning while working slowly to be a blocker :)
i don't totally get them either, so we work on it together, over time, ok?
as you have probably noticed, i tend to write "proof-of-concept" unit
tests that at least give a basic level of confidence then move quickly
on. this will allow rapid progress but will bite us in corner-cases.
--
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-05-27 11:10 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 #46 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
tobias, the DataMerger class looks good as a first cut: it looks like it
does the job.
couple of things:
----
+ for j in range(self.addr):
this should be self.array_size
----
+ with m.If(self.addr_match_i[j]>0):
instead of > 0, bool() can (should) be used:
with m.If(self.addr_match_i[j].bool()):
-----
+ with m.If(self.addr_match_i[idx][j] && valid):
ah. in nmigen, you can't use boolean operators (&& or ||) because
there is no operator-overload for "bool". a PEP was actually raised
about this and, rather short-sightedly, turned down.
you therefore have to use the bit-wise operators, and make sure
that the things that you are comparing are only 1 bit wide.
with m.If(self.addr_match_i[idx][j] & valid):
------
+ self.data_o.eq(0)
this line is not needed. combinatorial circuits default to zero unless
you set some of the Signal initialisation arguments.
-----
+ self.data_o.eq(self.data_i[j]|self.data_o)
this isn't python programming, unfortunately: you can't treat Signals in
a loop as "sequentially-accumulating variables".
this is why i said to use treereduce. or, actually, now you can import
ortreereduce, from soc.regfile.regfile.
so do this instead:
l = []
for j in range(self.array_size):
select = self.addr_match_i[idx][j] & valid)
l.append(Mux(select, self.data_i[j], 0)
self.data_o.eq(ortreereduce(l)
see how that works? because hardware is effectively "statically-assigned
variables", you can't really do dynamic-accumulation. or... you can, but
it will create a massive chain of gates and the completion time will be
awful.
:)
so, use a Mux-in-a-loop, and tree-reduce them. strictly speaking we
could hypothetically use the 2nd parameter of nmutil.utils.treereduce
to actually do the Mux there, reduce things down to maybe one or two
lines of code, however that's getting obtuse and "too clever" :)
too clever means the code becomes unreadable.
--
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-27 4:12 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
--- Comment #1 from Cole Poirier <colepoirier@gmail.com> ---
Made some very minimal progress on this today. Since I'm still learning how to
write proofs it takes a long time to get the most basic assumptions of the most
basic class (Register) from regfile.py sorted enough that I can start to reason
about them. I think the foundation that I laid today will enable me to write
some code for this (instead of just written notes from working and reasoning
through the assumptions of the module) tomorrow. But, if this proof is needed
before then for the virtual_port tests, Luke please feel free to take it over
like you did with virtual_port today. I want to help, so I don't want my
learning while working slowly to be a blocker :)
--
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 354] idea/optimisation: make FP CMP also do INT CMP
From: bugzilla-daemon @ 2020-05-27 0:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-354-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=354
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Source Code |ALU (including IEEE754
| |16/32/64-bit FPU)
--
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 354] New: idea/optimisation: make FP CMP also do INT CMP
From: bugzilla-daemon @ 2020-05-27 0:46 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=354
Bug ID: 354
Summary: idea/optimisation: make FP CMP also do INT CMP
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: ---
from mitch alsup on comp.arch:
This all falls out for FREE if you start with FP compare to ZERO and
then figure out how the same logic can be used for integer instead of
the other way around.
I have the logic schematic (3 pages) is you desire to peruse. The overhead
of adding FP to INT compare is around 10% in gate count.
--
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 345] define POWER9 regfiles
From: bugzilla-daemon @ 2020-05-27 0:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-345-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=345
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
added XER and CR based on new VirtualRegPort.
INT and FAST also added, based on RegFileArray
that just leaves SPRs which are massive. may leave that for now.
--
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 351] create a "block" (mass) regfile port (read and write) onto an array-based regfile
From: bugzilla-daemon @ 2020-05-26 23:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-351-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=351
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=353
--
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-26 23:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=351
--
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 351] create a "block" (mass) regfile port (read and write) onto an array-based regfile
From: bugzilla-daemon @ 2020-05-26 23:17 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-351-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=351
--- Comment #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
added a "demo" unit test that seems to show that it's functional. i added
one extra read port and HOLY cow did the number of gates jump. that's just
a 32-bit register. luckily we only need one of them.
--
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] funny article about Rust and technical interviews
From: Jacob Lifshay @ 2020-05-26 22:24 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <958561A0-F4FC-4EE1-9C1C-D75110311BC7@getmailspring.com>
On Tue, May 26, 2020, 15:03 Cole Poirier <colepoirier@gmail.com> wrote:
> On May 26 2020, at 2:25 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> > On Tuesday, May 26, 2020, Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> >> https://blog.mgattozzi.dev/oxidizing-the-technical-interview/
> >>
> >> Amazing and horrifying!
> >
> >
> > :)
> >
> > reminds me of a bare metal ADA howto i saw, when the question came up on
> > comp.arch about not using ADA runtimes that are only designed for
> GNU/Linux.
> >
> > l.
>
> It made my brain hurt. Can one of you more experienced programmers
> please explain the joke to me? Is the objective to show us mere mortals
> our assumptions of safety, etc. lie upon foundations that would scare us
> because our modern programming environments coddle us?
>
The objective is mostly to provoke laughter at the absurdity of what the
interviewee is doing, since they are going waay beyond what is necessary or
practical to run a program even if you were running it on bare metal: using
#![no_core] is like if you decided to write your own stddef.h or stdint.h
if you were writing in C, or writing your own implementation of the int or
bool classes in Python.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 351] create a "block" (mass) regfile port (read and write) onto an array-based regfile
From: bugzilla-daemon @ 2020-05-26 22:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-351-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=351
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
urr ok i removed the mux on the virtual file port, it's now "direct" and only
the wide (full) path is possible. now the next important thing is to have a
test which shows there is no conflict or data corruption when accessing
"small" ports vs the big one.
--
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] funny article about Rust and technical interviews
From: Cole Poirier @ 2020-05-26 22:03 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDwnXhyXdoks=X01-mBJ0OMyYMVqpkBTtTo6skgrzRgSRg@mail.gmail.com>
On May 26 2020, at 2:25 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Tuesday, May 26, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
>> https://blog.mgattozzi.dev/oxidizing-the-technical-interview/
>>
>> Amazing and horrifying!
>
>
> :)
>
> reminds me of a bare metal ADA howto i saw, when the question came up on
> comp.arch about not using ADA runtimes that are only designed for GNU/Linux.
>
> l.
It made my brain hurt. Can one of you more experienced programmers
please explain the joke to me? Is the objective to show us mere mortals
our assumptions of safety, etc. lie upon foundations that would scare us
because our modern programming environments coddle us?
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
* [libre-riscv-dev] [Bug 155] a PLL is needed for the SoC
From: bugzilla-daemon @ 2020-05-26 21:30 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-155-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=155
--- Comment #16 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Staf Verhaegen from comment #15)
> > Input: 24 MHz XTAL
>
> AFAIK there is no crystal oscillator IP available for this project so I
> assumed the input clock would be CMOS.
if we do not have all the pieces, yes we will use a CMOS external clock, this
is the fallback.
Professor Galyco, i may not have made it clear: we are not signing any NDAs and
so need *everything* from scratch that would normally be provided by the
Foundry (under NDA). thank you for raising this, Staf.
did the PLL that you developed also include a XTAL interface?
--
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] funny article about Rust and technical interviews
From: Luke Kenneth Casson Leighton @ 2020-05-26 21:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7dRoRX2QEOfQuj96awHZwqbe6aF_Y86nY4RwGq46bh7w@mail.gmail.com>
On Tuesday, May 26, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> https://blog.mgattozzi.dev/oxidizing-the-technical-interview/
>
> Amazing and horrifying!
:)
reminds me of a bare metal ADA howto i saw, when the question came up on
comp.arch about not using ADA runtimes that are only designed for GNU/Linux.
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] funny article about Rust and technical interviews
From: Jacob Lifshay @ 2020-05-26 20:15 UTC (permalink / raw)
To: Libre-RISCV General Development
https://blog.mgattozzi.dev/oxidizing-the-technical-interview/
Amazing and horrifying!
definitely worth my upvote on Reddit.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 155] a PLL is needed for the SoC
From: bugzilla-daemon @ 2020-05-26 20:12 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-155-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=155
--- Comment #15 from Staf Verhaegen <staf@fibraservi.eu> ---
> Input: 24 MHz XTAL
AFAIK there is no crystal oscillator IP available for this project so I assumed
the input clock would be CMOS.
> So, regarding the specifications, the most important point determining the
> overall architecture is :
> -- Jitter
For a digital circuit jitter of the clock eats in the timing budget, the
critical has to be fast enough to have result for the smallest clock cycle due
to jitter.
Analog/mixed-signal blocks will have their requirement on jitter, like
resolution/bandwidth for an ADC or error rate for SERDES.
--
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: 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