* [libre-riscv-dev] nlnet 2019 standards update - video and 3d acceleration standards
From: Immanuel, Yehowshua U @ 2020-04-06 16:02 UTC (permalink / raw)
To: Libre-RISCV General Development
https://libre-riscv.org/nlnet_2019_standards/
- Is this NLNet grant still valid now that we have moved to POWER?
- Do we need to update the objectives a little since we are now on POWER?
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-06 16: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 #52 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #50)
> Sorry for another big delay on my part.
no problem. we still need to get the MoU signed. money's allocated,
just not accessible yet.
>
> (In reply to Luke Kenneth Casson Leighton from comment #45)
> > so could you track down that auto-box-size computing function and then
> > look at removing all hard-coded parameters?
>
> 'Module.compute_ab()' added.
great.
> > you'll likely need to run add.build() manually, then sub.build() manually,
>
> I kinda anticipated such changes in workflow, so I divided the submodules
> processing into 'build()' and 'place()' phases beforehand. Now I added an
> utilities such as 'Module.submodules' iterator and
> 'Module.find_submodule(name)'.
excellent
> > *then* in ALU16()'s build constructor it will have access to the
> > (computed) width+height of each,
>
> Also not a problem: after 'build_submodules()' it can be accessed via
> submodule's 'ab' property.
>
> > *then* it can compute its width and
> > height.
>
> Here I stumbled on how to get the end result.
>
> > ALU16 computes its height based on:
> > max(Add.H, Sub.H, middle-stuff-H) + 100 (to give room for the routing)
> >
> > and its width based on:
> > Add.W + Sub.W + middle-stuff-W + 20-or-so
>
> I tried this approach, but middle stuff size calculates as 650×650 and
> everything bloats. And there are many “unplaced design” errors. =(
yes.
ok, you'll see i've done a lot of experimentation, i went back to using
an iterative try-it-and-see approach
hum
also i did this:
* changed the I/O pins for ALU16 so that they are closer to the middle
* put all the pins for add and sub at the top (this needed experimentation
just to get an I/O config for each that would "pass" routing)
* made add's pins a *mirror* of sub's pins (you'll see why, next)
* *ROTATED* add and sub so that their inputs/outputs "faced" each other
* put in a hard-coded positioning for the "middle" placement (ALU16
little stuff)
* called place *only* (for all the little stuff)
* after the place, *only* call route *not* place-and-route
what happens if you call place-and-route after place, the entire box is
filled with "dummy cells" that go *underneath* (overlap) the add() and
sub() boxes.
whoops
this only showed up because of the rotation of add() and sub().
the reason for doing the rotate (and mirror) is to get the add() and sub()
I/O to try to "connect" with dead-straight lines, right across the
middle-stuff.
however this (if you think about it carefully) creates an artificial barrier
where no VIAs can be properly placed.
whoops.
ah.
just found what might be a serious bug: two routes trying to occupy the
same space.
jean-paul, i will raise a bugreport on gitlap.lip6.fr
--
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-04-06 16:58 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 #53 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/8
--
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] nlnet 2019 standards update - video and 3d acceleration standards
From: Luke Kenneth Casson Leighton @ 2020-04-06 17:08 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <DA8C67BB-72E6-4678-9C97-2E83ACF7E332@gatech.edu>
On Mon, Apr 6, 2020 at 5:02 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> https://libre-riscv.org/nlnet_2019_standards/
>
> - Is this NLNet grant still valid now that we have moved to POWER?
yes - thank goodness i alerted them in advance to the change, and they
were happy with it.
> - Do we need to update the objectives a little since we are now on POWER?
mmmm they stay the same. hybrid CPU / GPU / VPU. the details on the
other hand, yes those get to change. not least, a rewrite of SV is
needed to "fit" POWER. which is going to be a damn nuisance.
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] Removing orphan pages from the wiki
From: Luke Kenneth Casson Leighton @ 2020-04-06 17:11 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <81FEF361-F930-4827-8204-5B89A14DDEA2@gatech.edu>
On Mon, Apr 6, 2020 at 3:56 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> The wiki has some orphan pages in the git Repo…
probably.
> I’ll reply back with the list of files later, but, we should probably clean this up.
the sitemap's sort-of for that.
> Also, @Luke, do you think you could add “Updates” to the toolbar, linking to the Crowd Supply page?
done. i liked the updates page you created, i'd prefer to link to
that and have individual summaries plus date plus link on our site.
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] CI passes for soc.git!!!
From: Luke Kenneth Casson Leighton @ 2020-04-06 17:12 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7+D3Ht8_FHvt=frsR4bsr=GqHKTzaE7udOd3gpPBn1HA@mail.gmail.com>
On Mon, Apr 6, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Mon, Apr 6, 2020, 04:08 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> >
> > can you please merge what you did (and work in master in future unless
> > there's a really *really* compelling and critical reason for doing
> > so)?
> >
>
> So, just merge despite the commit mess?
yehyeh don't worry about it too much. i nit-pick however that's in
case it needs a partial roll-back [that really bugs me: reversion of
partial commits is a bitch]. if you're sure it's fine just merge them
in.
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-06 17: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 #54 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #53)
> https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/8
jean-paul i think we need your help on this one. are we pushing
the auto-router too hard, not giving it enough space? i do see
some tracks going in weird directions (doubling back)
https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/7
--
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] Removing orphan pages from the wiki
From: Immanuel, Yehowshua U @ 2020-04-06 17:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyohMP+aLfPeryNjmAQOZbtQf1vedwUxx=sRXM+Ht8fbQ@mail.gmail.com>
> done.
Awesome. Is there a way to move it near the top of the stack?
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Removing orphan pages from the wiki
From: Luke Kenneth Casson Leighton @ 2020-04-06 18:22 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <191D8A57-C14E-4B9C-83B9-BC819AE8AB8E@gatech.edu>
On Mon, Apr 6, 2020 at 6:53 PM Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> > done.
>
> Awesome. Is there a way to move it near the top of the stack?
>
yes. if you have the git repo access, or if you just go to
http://libre-riscv.org/sidebar/ you can edit it just like any other page.
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] Removing orphan pages from the wiki
From: Immanuel, Yehowshua U @ 2020-04-06 18:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDya4+LH=u7gKSe4a2Y=5B+LEaLgGZJUYgxJUX1SpUUA4w@mail.gmail.com>
done.
_______________________________________________
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] CI passes for soc.git!!!
From: Jacob Lifshay @ 2020-04-06 19:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwEjiPFd1dDwL=0VsJgxqn0AVjeKvr6=e2-KOqe2JVKWw@mail.gmail.com>
On Mon, Apr 6, 2020, 10:13 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Mon, Apr 6, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > On Mon, Apr 6, 2020, 04:08 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> > wrote:
> >
> > >
> > > can you please merge what you did (and work in master in future unless
> > > there's a really *really* compelling and critical reason for doing
> > > so)?
> > >
> >
> > So, just merge despite the commit mess?
>
> yehyeh don't worry about it too much. i nit-pick however that's in
> case it needs a partial roll-back [that really bugs me: reversion of
> partial commits is a bitch]. if you're sure it's fine just merge them
> in.
>
Merged but now it broke the build, so I pushed it to fix-tests. Will figure
it out a little later when I'm not sshing into my desktop through my phone.
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] CI passes for soc.git!!!
From: Luke Kenneth Casson Leighton @ 2020-04-06 20:34 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6N_QC1MBwD8k2qX0VsEazU414yDiw9HduO_ehDqyfs0g@mail.gmail.com>
On Mon, Apr 6, 2020 at 8:15 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Merged but now it broke the build, so I pushed it to fix-tests. Will figure
> it out a little later when I'm not sshing into my desktop through my phone.
*grin* ok
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-06 21:32 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
Alain D D Williams <addw@phcomp.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CONFIRMED
Resolution|FIXED |---
--- Comment #10 from Alain D D Williams <addw@phcomp.co.uk> ---
git.libre-soc.org does not have an IPv6 address.
It should be 2a00:1098:82:f::1
--
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-06 21:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Alain D D Williams from comment #10)
> git.libre-soc.org does not have an IPv6 address.
>
> It should be 2a00:1098:82:f::1
added to /etc/bind/libre-soc.db
--
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] CI passes for soc.git!!!
From: Jacob Lifshay @ 2020-04-07 0:07 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDymCOBBubkYsnXQNpGg4QsQ1Y0ra3UAYg+1Kkryyn=N+Q@mail.gmail.com>
On Mon, Apr 6, 2020 at 1:35 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Mon, Apr 6, 2020 at 8:15 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > Merged but now it broke the build, so I pushed it to fix-tests. Will figure
> > it out a little later when I'm not sshing into my desktop through my phone.
Turns out that a later commit on master fixed it, so I pushed my
changes to master and deleted the fix-tests branch.
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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-07 0:16 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #39 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=5d496a6b50ec3b9e00586e777651c60a1921688d
michael that should just be for fieldname in op_fields otherwise a lot more
fields get added than is necessary.
op_fields includes the names of everything spotted during parsing... that is
*not* a GPR.
no need to exclude RS RA RT either because i already excluded them back in the
parser.
--
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] CI passes for soc.git!!!
From: Luke Kenneth Casson Leighton @ 2020-04-07 0:22 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD694G4jYPwuW1KEJmW8EMZU4sjpu4anufnQ+auBiWpWgg@mail.gmail.com>
On Tuesday, April 7, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Turns out that a later commit on master fixed it, so I pushed my
> changes to master and deleted the fix-tests branch.
ok cool.
i suspect it was the git submodules.
i believe it may be essential to do submodule updates then individual
separate commit of .gitmodules.
one way to do this: by committing groups of files *not* with git commit -a
but explicitly listing them
then finally the last commit with .gitmodules only
if a commit includes both files *and* an alteration to .gitmodules then
merging breaks.
frickin nuisance. lots of people have given up using submodules because of
this
must research it properly.
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 5:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #2 from Jock Tanner <tanner.of.kha@gmail.com> ---
Another thing that is slightly bugging me here is lookahead carry units. Should
we reconfigure them "on the fly" together with adders/subtractors? Is that
viable? Multiplexers can introduce enough delay to make the whole looking-ahead
thing inefficient comparing to simple serial carry propagation.
--
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] finishing off the crowdsupply update
From: Jacob Lifshay @ 2020-04-07 7:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxofq_y_LTp_ApXQCYuZ=aKHcJEnL=64HcyeC9OF7Yyrg@mail.gmail.com>
On Fri, Apr 3, 2020, 14:53 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Fri, Apr 3, 2020 at 9:31 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
>
> > Everything looks good to me!
>
> likewise.
>
> > So, I think the rest of what we need to do is:
> >
> > 1. Figure out if crowdsupply supports redirects for renaming our project.
> > 2. Update the crowdsupply description of our project to reflect
> > changing our name to Libre-SOC.
> > 3. Publish our update. (only after above is complete, since that's
> > when everyone will come look at the crowdsupply page).
>
> everything is controlled by Joshua Lifton. i get a chance to *ask*
> him if it's possible to change the redirects. i also have to remember
> how to log in and...
>
> oh, i just remembered, the description is in the crowdsupply wiki :)
Any response yet from Joshua Lifton?
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-07 8:12 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 #55 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #54)
> (In reply to Luke Kenneth Casson Leighton from comment #53)
> > https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/8
>
> jean-paul i think we need your help on this one. are we pushing
> the auto-router too hard, not giving it enough space? i do see
> some tracks going in weird directions (doubling back)
>
> https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/7
Hello Luke & Jock,
I'm going to look into it this afternoon or tomorrow. I've been
busy with integrating the analog resistor devices then reviewing
a little the Python code. I'm also working on improving the
Python/C++ interface, going from C preprocessor macros to
C++ templates (have to [re]learn things here), and preparing
the move toward Python 3.
For the MoU, only the Sorbonne University can sign it on my
behalf, so I did forward it to my contact lawyer. Hoping it
would not take too long to process in thoses troubled times.
Best regards,
--
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] finishing off the crowdsupply update
From: Luke Kenneth Casson Leighton @ 2020-04-07 9:38 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6PUmmJqh8PnvzT4K+j8V5XaV9nFeAD3Y9kMJyEmtdqxg@mail.gmail.com>
On Tue, Apr 7, 2020 at 8:50 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Any response yet from Joshua Lifton?
nno - it can take a while. they're extremely busy and a small team.
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-07 9:46 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 #56 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #55)
> (In reply to Luke Kenneth Casson Leighton from comment #54)
> > (In reply to Luke Kenneth Casson Leighton from comment #53)
> > > https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/8
> >
> > jean-paul i think we need your help on this one. are we pushing
> > the auto-router too hard, not giving it enough space? i do see
> > some tracks going in weird directions (doubling back)
> >
> > https://gitlab.lip6.fr/vlsi-eda/coriolis/issues/7
>
> Hello Luke & Jock,
>
> I'm going to look into it this afternoon or tomorrow.
appreciated.
> I've been
> busy with integrating the analog resistor devices then reviewing
> a little the Python code. I'm also working on improving the
> Python/C++ interface, going from C preprocessor macros to
> C++ templates (have to [re]learn things here), and preparing
> the move toward Python 3.
ok. well, given that the code is actually working, the less disruption
that we have (say, for example... by *not* moving to python 3 so that
we don't have to spend another 3-7 days recompiling and working out
issues and redesigning the scripts and installation instructions) the better.
> For the MoU, only the Sorbonne University can sign it on my
> behalf, so I did forward it to my contact lawyer.
if there is a way to emphasise to him that it is NOT a contract,
and that both LIP6 and other individuals with families are reliant
on him getting an answer - fast - for receiving money - that would
be... good.
--
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 267] The efficiency of adder/subtractor
From: bugzilla-daemon @ 2020-04-07 9:48 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-267-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=267
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #2)
> Another thing that is slightly bugging me here is lookahead carry units.
you'll need to send me some links so i can take a look at what you mean.
> Should we reconfigure them "on the fly" together with adders/subtractors? Is
> that viable? Multiplexers can introduce enough delay to make the whole
> looking-ahead thing inefficient comparing to simple serial carry propagation.
if you can put some links here as to what you're comparing (descriptions,
tutorials, gate-level diagrams) i can get up to speed and follow the
conversation.
--
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 11:02 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #12 from Alain D D Williams <addw@phcomp.co.uk> ---
Please add to /etc/bind/libre-soc.db an IPv6 address for lists.libre-soc.org
--
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 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-07 11:21 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #13 from Alain D D Williams <addw@phcomp.co.uk> ---
Please create DNS entries for inbox.libre-soc.org
IPv4 & IPv6
Ta
--
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