* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-03-17 17:53 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 #35 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #34)
> (In reply to Jean-Paul.Chaput from comment #33)
> > Are you on Coriolis commit b07a4722 ? (the latest one).
>
> I'm on 'devel' branch and up to date, but my latest commits are from
> 9/02/2020, so maybe I'm just on different repo?
>
> My git config says:
>
> > [remote "origin"]
> > url = https://www-soc.lip6.fr/git/coriolis.git
read comment #25 again, jock - specifically noting the change of URLs.
l.
--
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-17 18:07 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 #36 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #35)
> read comment #25 again, jock - specifically noting the change of URLs.
Yeah you're right, guys, I'm sorry.
--
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 260] New: Figure out creating userspace-driven explicit synchronization for Linux Kernel sync_file and dma_fence
From: bugzilla-daemon @ 2020-03-17 18:15 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=260
Bug ID: 260
Summary: Figure out creating userspace-driven explicit
synchronization for Linux Kernel sync_file and
dma_fence
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: programmerjake@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
Blocks: 54, 140
NLnet milestone: ---
See conversation at:
https://lists.freedesktop.org/archives/mesa-dev/2020-March/224262.html
sync_file is required for implementing Vulkan's standard extension for
synchronizing cross-process
Referenced Bugs:
http://bugs.libre-riscv.org/show_bug.cgi?id=54
[Bug 54] Kazan Vulkan driver operational
http://bugs.libre-riscv.org/show_bug.cgi?id=140
[Bug 140] Implement AMDVLK / RADV Mesa Vulkan Driver NLNet 2019-10-042
--
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-17 18:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzzojEUrOU3vYcza0qB9rM7asNMnaSCCSfG9rE9Nz4i7A@mail.gmail.com>
On Fri, Mar 13, 2020, 03:13 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> 1). bad: it is seriously demeaning to use the phrase "non-paranoid" -
> to ACCUSE potential users of rust of "being paranoid". can i suggest,
> jacob, raising that as a severe and high-priority issue with the rust
> community to get that removed effective immediate?
>
Fixed: https://github.com/rust-lang/rustup/pull/2265
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 260] Figure out creating userspace-driven explicit synchronization for Linux Kernel sync_file and dma_fence
From: bugzilla-daemon @ 2020-03-17 18:25 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-260-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=260
--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
This may require creating a new kernel driver.
--
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-17 18:55 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 #38 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #37)
> Created attachment 44 [details]
> I think this picture is correct
>
> I'll get back to 'ChipConf' tomorrow.
oleeeee! it's so preeetttyyy :) we got to the bottom of it. hurrah.
if you press Ctrl-I then you can enable Filter-tab "Process Tools",
and see the actual cells.
personally i find it absolutely bleedin fascinating.
zoom in close and then use Ctrl-Right-Mouse and it will show you
the name of any instances at that mouse-point (VIAs, METAL traces,
and the Cells themselves.
you can then, if you are feeling particularly fascinated / horrified
by the level of detail, search (grep) for that name back in the
*vst* files:
grep subctk_33_sff1 *.vst
for example.
ok so let's start again, tomorrow, from here:
http://bugs.libre-riscv.org/show_bug.cgi?id=217#c20
btw i have to travel down to Essex tomorrow, i'm catching a coach at
6pm, overnight. i'll have internet access (through a WIFI-4G router)
just no laptop set up. most likely i'll be "properly" back online by
thursday evening. so if you get messages from me which are both
obtuse and badly spelled, you know i'm pecking one-finger at a hand-held
device.
--
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] [Bug 260] Figure out creating userspace-driven explicit synchronization for Linux Kernel sync_file and dma_fence
From: Luke Kenneth Casson Leighton @ 2020-03-17 18:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <bug-260-13-3LBZ0jGPxO@http.bugs.libre-riscv.org/>
On Tue, Mar 17, 2020 at 6:25 PM <bugzilla-daemon@libre-riscv.org> wrote:
>
> http://bugs.libre-riscv.org/show_bug.cgi?id=260
>
> --- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
> This may require creating a new kernel driver.
appreciate the heads-up.
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] next tasks
From: Luke Kenneth Casson Leighton @ 2020-03-17 18:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7dzA-DTeQL3KyFdq8V=-e0hAL6E9jmccS2Jk-EQU_+qA@mail.gmail.com>
On Tue, Mar 17, 2020 at 6:23 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Fri, Mar 13, 2020, 03:13 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > 1). bad: it is seriously demeaning to use the phrase "non-paranoid" -
> > to ACCUSE potential users of rust of "being paranoid". can i suggest,
> > jacob, raising that as a severe and high-priority issue with the rust
> > community to get that removed effective immediate?
> >
>
> Fixed: https://github.com/rust-lang/rustup/pull/2265
wow that's fantastic, they listened.
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] priority picker
From: Luke Kenneth Casson Leighton @ 2020-03-17 21:51 UTC (permalink / raw)
To: Libre-RISCV General Development
https://git.libre-riscv.org/?p=nmutil.git;a=blob;f=src/nmutil/picker.py;h=0e50fd24f1131cb40ff306030f0dcfb107d0c22e;hb=a6130a92485d572182ab80a2da279997388ef52e#l64
i just created something called "MultiPriorityPicker" which is quite cute.
PriorityPicker is an important "selector" of which (unary-encoded). This is
used to select which Function Unit's output will get access to a given register
file port, for example.
Except... what happens if we have multiple register file ports? (which we do)
Err... who gets access to which port?
that's what the MultiPriorityPicker is for. basically it is an array
of PriorityPickers (see
https://libre-riscv.org/3d_gpu/architecture/6600scoreboard/)
the PriorityPickers are connected in a cascade, where the output of
each *accumulates* a mask that *prevents* downstream PriorityPickers
from picking already-picked outputs.
in addition, in order to help select a particular "port", an index
(currently in binary, i may change that to unary later) is set - again
in an incrementing cascade - such that whichever Picker's output has a
"1" set it is *guaranteed* to also be allocated a unique "index" as
well.
this "index" can be used to say which "port" on the register file, for
example, that the "Picker" is permitted to write (or read) from.
it also has uses for the LOAD/STORE buffer: namely the
Load/Store-FunctionUnit's have to know which "port" to write into the
(multi-input) LD/ST Buffer (aka cache).
all good fun.
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 258] Finish implementing support for Power in simple-soft-float
From: bugzilla-daemon @ 2020-03-18 4:37 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-258-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=258
--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
Just finished some refactoring in preparation for supporting Power's weird FP
status flags.
--
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-18 5:23 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|IN_PROGRESS |RESOLVED
--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
Luke, it looks like you probably have something that works just as well as this
would, so I'm resolving the bug.
--
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] [Bug 258] Finish implementing support for Power in simple-soft-float
From: Luke Kenneth Casson Leighton @ 2020-03-18 6:57 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <bug-258-13-BAO9vOEHas@http.bugs.libre-riscv.org/>
On Wednesday, March 18, 2020, <bugzilla-daemon@libre-riscv.org> wrote:
> http://bugs.libre-riscv.org/show_bug.cgi?id=258
>
> --- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
> Just finished some refactoring in preparation for supporting Power's weird
> FP
> status flags.
the FP HDL needs a big update to bring out status bits. then another one
to add rounding modes, which is quite a bit of work.
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-18 6:59 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
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lkcl@lkcl.net
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(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.
--
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] [Bug 258] Finish implementing support for Power in simple-soft-float
From: Jacob Lifshay @ 2020-03-18 7:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz1e-RXfd8-dD6Q4QPPQfcVNCCbJ4e8Vb1mD2ZrJVCDiw@mail.gmail.com>
On Tue, Mar 17, 2020, 23:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Wednesday, March 18, 2020, <bugzilla-daemon@libre-riscv.org> wrote:
>
> > http://bugs.libre-riscv.org/show_bug.cgi?id=258
> >
> > --- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
> > Just finished some refactoring in preparation for supporting Power's
> weird
> > FP
> > status flags.
>
>
> the FP HDL needs a big update to bring out status bits. then another one
> to add rounding modes, which is quite a bit of work.
>
Adding status bits and adding rounding modes should be done together,
because they are closely interrelated, especially inexact and underflow.
If you do them separately, you will only be making more work for yourself.
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] NLNet Funding Proposals for the Libre RISC-V SoC: call for participation
From: Adrienne G. Thompson @ 2020-03-13 1:19 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton
Cc: Libre-RISCV General Development, Discussão do LibrePlanet
In-Reply-To: <CAPweEDwWtgCXscytqhzWRo_Jdt9qvYF8DgKBy6NQXYjw8b9_JQ@mail.gmail.com>
On Thu, Mar 12, 2020 at 7:46 PM Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> just a quick followup: we got the funding.
>
Congrats Luke!!
All the very best for the project. Assembler used to be a lot of fun.:)
As I mentioned, once I'm done with the fundraising I'll be writing a lot of
code in Python - but it's all for C-Graph!
Cheers
Adrienne
--
Freedom - no pane, all gaiGN!
GNU C-Graph - http://www.gnu.org/software/c-graph
Code Art Now - http://codeartnow.com
Abertheid Campaign - http://www.abertheid.info
Follow me on Twitter @AdrienneGT @GNUcgraph
_______________________________________________
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 261] New: power_enums.py to read SPRs from sprs.csv
From: bugzilla-daemon @ 2020-03-18 12:11 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=261
Bug ID: 261
Summary: power_enums.py to read SPRs from sprs.csv
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Specification
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
power_enums.py SPRs Enum to read from this:
http://libre-riscv.org/openpower/isatables/sprs.csv
--
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 261] power_enums.py to read SPRs from sprs.csv
From: bugzilla-daemon @ 2020-03-18 13:31 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-261-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=261
Michael Nolan <mtnolan2640@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtnolan2640@gmail.com
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Michael Nolan <mtnolan2640@gmail.com> ---
Done: 474eb33c
--
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 261] power_enums.py to read SPRs from sprs.csv
From: bugzilla-daemon @ 2020-03-18 13:59 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-261-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=261
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #1)
> Done: 474eb33c
ah magic that was quick! :)
--
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 261] power_enums.py to read SPRs from sprs.csv
From: bugzilla-daemon @ 2020-03-18 14:31 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-261-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=261
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
oops i'd forgotten to put in the extra fields (length, priv yes/no), added them
to the csv file and *then* discovered you'd learned that the key-names aren't
unique. had a lovely time re-introducing the suffixes you added, michael :)
--
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-18 14:31 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 #39 from Jock Tanner <tanner.of.kha@gmail.com> ---
I'm glad I managed to fix my Pycharm in terms of introspecting the Coriolis
Python extensions. It was a stale skeleton cache. I deleted it manually (the
usual “Invalidate and restart” did not do the trick), and everything suddenly
started to work, including code completion.
I made a wrapper function around 'Pin.create()', that tries to use some
defaults for simpler use. I may got some of the defaults wrong though. Maybe
more appropriate values can be deducted from the Hurricane's guts. Please have
a look.
https://git.libre-riscv.org/?p=soclayout.git;a=blob;f=experiments7/doAlu16.py;hb=HEAD#l40
--
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 178] first coriolis2 tutorial, workflow and "test project" page
From: bugzilla-daemon @ 2020-03-18 14:38 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-178-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=178
--- Comment #212 from Jock Tanner <tanner.of.kha@gmail.com> ---
I don't know if I'm expected to react somehow, but for me it's fine. I only
think if anyone could enlighten me about the due procedures.
(In reply to Luke Kenneth Casson Leighton from comment #210)
> for this one, i'm going to suggest:
>
> * EUR 250 to jock for the (crucial) questions and for helping get to buster
> * EUR 200 to tobias for the early checking of the tutorial
> * EUR 700 to be donated to LIP6.fr for the huge amount of bugfixing by JP
> * EUR 150 to Staf for his insights
> * EUR 1200 to me for the persistent head-banging against brick walls
>
> Cole, as long as you are in Europe, you helped find some early bugs in the
> tutorial page, and made some useful edits, however if you are outside of
> Europe, most of what NLNet would transfer to you would go in banking fees.
> we can if you like work something out.
--
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 261] power_enums.py to read SPRs from sprs.csv
From: bugzilla-daemon @ 2020-03-18 14:40 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-261-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=261
--- Comment #4 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> oops i'd forgotten to put in the extra fields (length, priv yes/no), added
> them to the csv file and *then* discovered you'd learned that the key-names
> aren't unique. had a lovely time re-introducing the suffixes you added,
> michael :)
Oh no!
I'm thinking I could either make the enum value a namedstruct/SPR object that
contains the length/privelages, or make a separate dict of structs/objects for
that information. Thoughts on which way to go?
Side note, why would they make them duplicate anyhow? That seems somewhat
nutty.
--
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-18 15:15 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 #40 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #39)
> I'm glad I managed to fix my Pycharm in terms of introspecting the Coriolis
> Python extensions. It was a stale skeleton cache. I deleted it manually (the
> usual “Invalidate and restart” did not do the trick), and everything
> suddenly started to work, including code completion.
exccellent.
> I made a wrapper function around 'Pin.create()', that tries to use some
> defaults for simpler use. I may got some of the defaults wrong though. Maybe
> more appropriate values can be deducted from the Hurricane's guts. Please
> have a look.
looks great to me. the docstring quality is excellent.
i did my usual "make myself go over the code by making
whitespace cleanups" i find it's a good way to "review" by making my fingers
"do" if you know what i mean. you'll need to do a git pull, there.
FIXED is a good default. 2.0 for the track-width, we might want to have
a class that sets that, at some point, rather than a function.
so the next two things, i think:
1. can you make a function which creates the BLOCKAGE "things"?
then call it from add() and sub(). defaults to 2,3,4 however allow
it to be parameterisable.
2. add() and sub() are near-duplicates and to some extent so is alu16.
could you make a function which both add() and sub() call, and break
out pieces for alu16()? for example, the "find and place" add and sub
we want the actual "parameterisation" to be as basic and as bleedingly
obvious as possible by keeping it compact, with everything "coriolis-related"
behind functions which are well-commented as to what they do.
so for add() and sub() they should be calling functions that, effectively,
take nothing more than:
- the cell name
- the size
- the pins.
err... that's it!
the task after that is where the "real" stuff starts if you know what i mean.
you see how there's a massive amount of whitespace at the top of alu16.ap
and at the bottom? with tracks that, because of the VIAs, you can't fit
any multi-layer routing, so (apart from the very top 50 which is really
puzzling, must raise a bug with Jean-Paul about it) there's very little
opportunity to "optimise it".
however... this is entirely a problem of our own making, becaise both add()
and sub() have inputs at the *top* and outputs at the *bottom*.
what is needed instead is:
* inputs on add() and sub() to be *ALL* at the top (NORTH)
- A+B to still be interleaved (just spaced closer together)
and on the LEFT of NORTH
- O to be in the RIGHT side of NORTH
* when "placed" inside alu16, the "add" cell needs to be *ROTATED*
(not Orientation.ID), clockwise and
"sub" needs to be rotated *anti*-clockwise
* alu16 A and B input and O output - just for fits and giggles - to be
brought closer together (not as spaced-out across the whole of the cell)
whilst still left on their respective sides.
* place-and-route attempted in the same way.
you _will_ find that the route of add() / sub() will go "quirky" i.e. if
certain combinations of the pins are given, the routing will not work
("error, pin is too far away from cell" that sort of thing)
you just have to experiment until you find a working combination.
this kind of thing is basically the "core" of what needs doing: looking at
how the router reacts, then going "hmmm" when it fails.
as we progress through to larger blocks, we will need to plan things
a bit carefully.
for example: there will be about *THIRTY* of these ALUs - some of them
extremely large - coming off of a *SINGLE* bus (!!). i.e. the data
*in* comes *back* to the same location as the data *out*, back onto
the same bus.
therefore, when we get to that point, the "thinner" each ALU is, the
better. in other words, we need a "chain" of pipeline stages, where
half of them go one direction, then the data "turns" round, and the
stages for the last half come *back* the other way. that way we have
the inputs arriving back at the same place as the outputs, and ta-daa,
we can route them onto the same bus.
basically this here - alu16 - is a trial run of that concept, which will
be massively expanded by about 100 times larger than add() and sub() are,
right now.
(!!) :)
oh.
yes.
nearly forgot.
third task: we need to compute (auto-calculate) the size of alu16 based
on the relative size of add(), sub(), and the remaining components.
that one we might have to ask Jean-Paul about.
erm, why are we discussing this under this bugreport? must create
a new one, really (doh).
--
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 178] first coriolis2 tutorial, workflow and "test project" page
From: bugzilla-daemon @ 2020-03-18 15:18 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-178-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=178
--- Comment #213 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #212)
> I don't know if I'm expected to react somehow, but for me it's fine. I only
> think if anyone could enlighten me about the due procedures.
ok see https://libre-riscv.org/about_us/ create yourself a user-page
on the wiki (template one of the existing ones, use mine as i have
more "headings"), then put EUR amount in a "pending" section, with
the heading "NLNet 2019 Coriolis2 Layout proposal 2019-10-029" and
put the date on that as well.
the RFP will go in to NLNet once i hear back from them. are you in
Europe? if so it's ok to put in small(ish) amounts.
(In reply to Tobias Platen from comment #211)
> 200 for me looks good
great, can you do the same as jock?
--
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 261] power_enums.py to read SPRs from sprs.csv
From: bugzilla-daemon @ 2020-03-18 15:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-261-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=261
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #4)
> Oh no!
:) ehh it was fiiine
> I'm thinking I could either make the enum value a namedstruct/SPR object
> that contains the length/privelages, or make a separate dict of
> structs/objects for that information. Thoughts on which way to go?
hmmm... separate doesn't make a lot of sense, people might think they're
somehow not related.
> Side note, why would they make them duplicate anyhow? That seems somewhat
> nutty.
sigh i know, welcome to an "organically-grown" ISA. they should have put a
prefix "H" or "S" in front of them, with "U" for "userspace".
--
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