* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-19 6:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=186
--- Comment #89 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok i fixed some dumb off-by-one errors in decode_fieldsn.py and the gas example
works (yay!) am tempted to suggest throwing a ton more random stuff at 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
* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-19 15:29 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=186
--- Comment #90 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #89)
> ok i fixed some dumb off-by-one errors in decode_fieldsn.py and the gas
> example works (yay!) am tempted to suggest throwing a ton more random stuff
> at it.
Yep, looks like you fixed the register thing.
I'll get to adding more instructions later today
--
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-19 15:33 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=186
--- Comment #91 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #90)
> Yep, looks like you fixed the register thing.
dang that was a good guess
> I'll get to adding more instructions later today
i love this idea. btw did we raise a specific bugreport for using gnu-as?
--
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-19 17:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=186
--- Comment #92 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #91)
>
> i love this idea. btw did we raise a specific bugreport for using gnu-as?
Yes: http://bugs.libre-riscv.org/show_bug.cgi?id=212
--
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 262] New: power virtual memory needed (radix?)
From: bugzilla-daemon @ 2020-03-20 8:39 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=262
Bug ID: 262
Summary: power virtual memory needed (radix?)
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: Other
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
an MMU is needed, particularly one that is compatible with an available
simulator or preexisting implementation.
power-gem5 has a well documented implementation.
--
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 262] power virtual memory needed (radix?)
From: bugzilla-daemon @ 2020-03-20 8:47 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-262-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=262
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://github.com/power-gem5/gem5/commit/373f7af347628151d23e6a5f81ae280f686df1f2
example
https://github.com/power-gem5/gem5/blob/gem5-experimental/src/arch/power/radix_walk_example.txt
--
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-20 11:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> (In reply to Jacob Lifshay from comment #1)
> > Luke, it looks like you probably have something that works just as well as
> > this would, so I'm resolving the bug.
>
> maayybee... i don't know. it's taking me considerable time to piece
> together.
nope, struggling. and the N-N-way comparisons for the high MSBs is going to
kill power usage. took me a while to realise what you were saying about using
a LRU (we have a PLRU implementation here):
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/TLB/ariane/plru.py;hb=HEAD
can you take a look? assume that each LD/ST buffer has *two* "ports",
one that is 16 bytes wide with address port0_addr and is normally used,
the other is *8* bytes wide (actually, 7), is *always* at port0_addr+16,
and deals with misalignments.
actually, that's a red herring. to clarify: it's safe to assume that
misalignments have been "dealt with" by being pre-split into separate
"aligned" ports.
also assume that addresses+len are expressed as:
* top bits numbered 4 and up as a binary address
* LSBs 0 to 3 as a 16-bit unary "mask" which *also* encapsulates data length
(with no misalignments, which means that some mask bit groups will be
non-power-2 long)
also assume that it is *guaranteed* - by this class - that there will be
ZERO overlaps. as in, absolutely guaranteed.
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/addr_match.py;h=0312504eb818c5e77d8a85d3948f733663b34b2e;hb=43415447fa3601f27b7994076823cea4cc3323a5#l143
it's the top MSBs of the address that are not covered by that (because it's
too much).
i figured, rather than a ring buffer, a PriorityPicker could identify QTY 1
address to put through, then all other address MSBs go through... the PLRU?
i get lost at this point.
--
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-03-20 12:09 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 #43 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://gitlab.lip6.fr/vlsi-eda/alliance-check-toolkit/-/commit/956491910c352d09bff46a246e2fe932a897a06f#8a49416afcb7336c552d1692aafbe93cff01cf63
useful input there.
--
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 181] test and install public-inbox
From: bugzilla-daemon @ 2020-03-20 12:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-181-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=181
--- Comment #50 from vklr@vkten.in <vklr@vkten.in> ---
Public-inbox Rev 2
Hey I worked out setup from Mailman2 mbox archives to public-inbox.
Steps are in the attachment.
pi-rev2.txt
--
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 181] test and install public-inbox
From: bugzilla-daemon @ 2020-03-20 12:51 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-181-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=181
--- Comment #52 from vklr@vkten.in <vklr@vkten.in> ---
Addition
--------
For public-inbox-watch always use listid option
in ~/.public-inbox/config
So that it picks up only mailing list posted emails only.
--
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] Please go through the new public-inbox elaborate setup revison
From: Veera @ 2020-03-20 12:59 UTC (permalink / raw)
To: libre-riscv-dev
Hi,
I finally worked out what was required from public-inbox + exim4 + mailman2.
Please see the Bugzilla page http://bugs.libre-riscv.org/show_bug.cgi?id=181
for the attached doc which has elaborate setup instructions.
Regards,
Veera
_______________________________________________
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 262] power virtual memory needed (radix?)
From: bugzilla-daemon @ 2020-03-20 13:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-262-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=262
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |programmerjake@gmail.com
--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
interesting reading: https://yarchive.net/comp/powerpc_page_tables.html
--
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-20 13:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |---
Status|RESOLVED |CONFIRMED
--- Comment #4 from Jacob Lifshay <programmerjake@gmail.com> ---
ok, reopening
--
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] [OT]: Dropbox rewriting their sync engine in Rust instead of Python
From: Jacob Lifshay @ 2020-03-20 14:09 UTC (permalink / raw)
To: Libre-RISCV General Development
found this interesting:
https://dropbox.tech/infrastructure/rewriting-the-heart-of-our-sync-engine
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 181] test and install public-inbox
From: bugzilla-daemon @ 2020-03-20 18:27 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-181-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=181
--- Comment #53 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #51)
> Created attachment 46 [details]
> New detailed setup instructions
>
> pi-rev2.txt
>
> New detailed instructions for setup.
fantastic. modified accordingly.
for next time (libre-soc lists) we definitely want to use -V2.
--
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] Please go through the new public-inbox elaborate setup revison
From: Luke Kenneth Casson Leighton @ 2020-03-20 18:30 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200320125953.GA28527@lily.local>
On Fri, Mar 20, 2020 at 1:00 PM Veera <vklr@vkten.in> wrote:
>
> Hi,
>
> I finally worked out what was required from public-inbox + exim4 + mailman2.
hurrah!
> Please see the Bugzilla page http://bugs.libre-riscv.org/show_bug.cgi?id=181
> for the attached doc which has elaborate setup instructions.
excellent. we now need to decide which lists we want (names). i
suggest "retiring" the libre-riscv-dev list. also, it doesn't
entirely make sense to have two archives, one pipermail, one
public-inbox. i'm advocating we just have public-inbox web archives
as it's clear that they're clonable.
i *really* need offline mail, i will be using a 3G/4G/WIFI router for
the next... err... N months.
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-20 18:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #4)
> ok, reopening
thanks. whew. oh. one other thing: if it can be N-way-ported (assume that
the L1 cache will at some point be dual-ported, minimum) that would be handy.
if there are several LDs, on 16-byte boundaries for example, we don't want the
L1 cache to be the bottleneck just because it's only possible to read/write one
cache line at a time.
i'm keeeenly aware that this implies we would be need a maaassive 256-bit-wide
data bus to the L1 cache.
oink.
welcome to GPUs :)
--
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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-03-20 18:54 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=184
--- Comment #4 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #0)
> These should be *new* lists on libre-soc.org (retire libre-riscv-dev)
>
> 1) Libre-SOC-Dev, for hardware and software development (productive)
> discussion
> 2) Libre-SOC-Org, for discussion about related to the organization
> itself, such as funding, investing, finances, domain change, website
> design, members, ethics, business, administration, you get my point
> 3) Libre-SOC-Misc, for everything else (the non serious stuff that I
> can safely ignore unlike the first two which should have important
> stuff only)
> 4) Bugtracker separate list, readonly announce only, and replyto set to
> bugzilla ready for when/if incoming bugzilla is ever set up
I think the above proposal is a good idea. When we finally shut-down
libre-riscv-dev, I think we should send out a single notification email to
everyone who's subscribed even if they have mail delivery turned off. We should
also announce our name & domain change on crowdsupply.
Is everyone ok with the above plan?
--
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] Epic MegaGrants - Libre RISC-V 3D GPU / CPU / VPU Update Requested
From: lkcl . @ 2020-03-20 18:55 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <S5FnE000000000000000000000000000000000000000000000Q7I4G100pl0vbJabQmW_qCxWW6V98Q@sfdc.net>
(hi folks, thanks for getting in touch, hope you don't mind me cc'ing
this onto our mailing list, we operate on the basis of full
transparency and i thought it best to reply in this case to our list).
On Fri, Mar 20, 2020 at 4:57 PM Epic <@epicgames.com> wrote:
>
> Hi Luke,
>
> Thank you for applying to the Epic MegaGrants program. Due to the extensive volume of applications, it has taken us much longer than we anticipated to review your application.
not a problem.
> In an effort to expedite the process, we're reaching out to inquire about any project updates that we should consider before proceeding with the final stages of review.
well, we have (summary) updates here, i'm due to write another one:
https://www.crowdsupply.com/libre-risc-v/m-class
the main crucial piece of news is: we put in eight NLNet Grant
applications (and they were all accepted). however we cancelled two
of them because during the exploratory phase we learned that:
* gcc compiler development is insanely expensive and people are hard
to find outside of the "industry". one company (one of the best)
quoted us USD 50,000 for a preliminary 3 month prototype, and their
commercial rates are a quarter of a MILLION a year.
* OpenCL, which would have been nice, we just had too much else to do
with such a small team. we'd really like to put that back on track.
also significant: one of the NLNet Grants is for a 180nm test ASIC,
we've a tape-out deadline of October 2020. NLNet's sponsorship allows
us to cover this cost.
however if we want to get to 45nm or below, that's where it gets
expensive: USD 250,000 for 45nm masks, and that amount *doubles* every
step in geometry, to the point where if we wanted to do 7nm it would
be a whopping $10m for the mask charges.
> If this is the case, please respond to this email with new information that is representative of your latest progress (builds, videos, images, etc), with the proper permission settings enabled for us to access the content.
everything's entirely public already. we've done a big update / reorg
on the wiki (https://libre-riscv.org/) and the side-bar shows the main
links to repos, bugtracker, etc.
> If we should proceed with your application as it was originally submitted, you may also let us know by replying to this email.
yes please.
> if we do not hear from you within the next 14 days, we will consider this application closed.
>
> Thank you for your continued patience and support!
not a problem, thank you for reaching out. please do remember, it's
worth reiterating: if you *donate* to us via the NLNet Charitable
Foundation (who will then help us manage finances), it's entirely a
tax-deductible contribution for EpicGames. also, if you would like to
set some conditions for the use of the funds (must be used to achieve
certain objectives), they're by far and above the best route to
"manage" that in a safe way.
if however that doesn't suit you (for whatever reason) we are in the
process of setting up a Public Benefit Corporation, based out of
Altanta, through the Georgia Tech "CREATE-X" Entrepreneurial
Programme.
whatever you decide, we're grateful for you considering this at all.
warmly,
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-20 19:07 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
--- Comment #6 from Jacob Lifshay <programmerjake@gmail.com> ---
Was assuming that the L1 cache has a single cache-line-sized R or W port,
though having 2 ports makes it even better.
Remember that we probably want another cache-line-sized port for communication
with the L2 and the rest of the SoC.
--
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-20 19:53 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #6)
> Was assuming that the L1 cache has a single cache-line-sized R or W port,
> though having 2 ports makes it even better.
here's the code i'd like to drop-in-place (literally), i.e. just use it.
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/minerva/units/loadstore.py;hb=HEAD
that's already set up for "masking" - bear in mind it's only 32-bit-wide
so the x_mask signal is only 4 bits: we need to expand that to 16-bits
and it will fit perfectly with the 16-bit "mask" from the PartialAddressBitmap
class.
so the other end of the interface, jacob, is the LoadStoreUnitInterface. a
test can be written which bypasses the cache, for now, to make life a bit
simpler.
> Remember that we probably want another cache-line-sized port for
> communication with the L2 and the rest of the SoC.
one step at a time :)
wait... ahh... everything memory-wise goes through the L1 cache. the cores are
"slaves" of the wishbone bus (not masters). all communication is done by way
of memory-addressing (all peripherals are memory-addressable).
even "management" of the L2 cache (and L1 "flush" commands) etc. should ideally
be done by way of memory-addressable "registers".
or, we have a special side-channel wishbone bus that communicates "messages".
basically drops a pre-determined data structure (a nmigen Record) onto the
side-channel WB bus at a known "address", it gets routed to where is needed,
and the recipient decodes it as "commands".
but as far as communication with periherals is concerned, they're *all*
memory-addressable. all of them. any "setup" is done by way of "Registers"...
which are also simply memory-addressable... over the WB memory bus.
some of those, because they are I/O, cacheing is not permitted. so we have to
be on the lookout for that.
--
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-20 20:21 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/minerva/cache.py;hb=HEAD
they set the cache up to be a maximum of 2-way. however that's not the same as
the number of read/write ports. arg.
ok i found a diagram which explains it:
https://libre-riscv.org/3d_gpu/architecture/set_associative_cache.jpg
it shouuuld be relatively straightforward to augment that to be dual-ported,
although let's not do that straight away.
--
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] Please go through the new public-inbox elaborate setup revison
From: Veera @ 2020-03-20 21:05 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxJt0ZkSEWf4NqvEjhOZ=2_op_KPQAcD-yWMur-HReH0A@mail.gmail.com>
On Fri, Mar 20, 2020 at 06:30:00PM +0000, Luke Kenneth Casson Leighton wrote:
> On Fri, Mar 20, 2020 at 1:00 PM Veera <vklr@vkten.in> wrote:
> >
> > Hi,
> >
> > I finally worked out what was required from public-inbox + exim4 + mailman2.
>
> hurrah!
>
> > Please see the Bugzilla page http://bugs.libre-riscv.org/show_bug.cgi?id=181
> > for the attached doc which has elaborate setup instructions.
>
> excellent. we now need to decide which lists we want (names). i
> suggest "retiring" the libre-riscv-dev list. also, it doesn't
You said we need archived http urls of libre-riscv-dev lists to save google
search engine hits we have already. What about it?
> entirely make sense to have two archives, one pipermail, one
> public-inbox. i'm advocating we just have public-inbox web archives
> as it's clear that they're clonable.
>
Hey, but pipermail archives are nice to browse.
In that case we should set mailman settings:
DEFAULT_ARCHIVE_PRIVATE = 1
# So no public viewable archive dir is made
ARCHIVE_TO_MBOX = 1
# do not use builtin mailman html archiving, archive to mbox only
Mbox archives are backable, while maildir is difficult to backup and
restore.
> i *really* need offline mail, i will be using a 3G/4G/WIFI router for
> the next... err... N months.
>
The public-inbox Xapian search is good.
And raw power of linux command line search tools with plains files available
in git will be great.
Regards,
Veera
> 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]: Dropbox rewriting their sync engine in Rust instead of Python
From: Cole Poirier @ 2020-03-20 21:47 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6cPB7FF0NrQfYY6hu=Fu6x_oiiX7FhfL3NJr7bX2BC4A@mail.gmail.com>
> On Mar 20, 2020, at 7:10 AM, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> found this interesting:
> https://dropbox.tech/infrastructure/rewriting-the-heart-of-our-sync-engine
>
> Jacob
Me too! I absolutely adore this-week-in-rust.org, so many interesting and educational things about rust—every week!
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 181] test and install public-inbox
From: bugzilla-daemon @ 2020-03-21 0:28 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-181-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=181
--- Comment #54 from vklr@vkten.in <vklr@vkten.in> ---
Forgot to add.
Please edit: test1.git/description
So that nice description is shown by public-inbox-httpd
--
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