* [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 17:42 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 #34 from Jock Tanner <tanner.of.kha@gmail.com> ---
(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
--
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 17:28 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 #33 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Jock Tanner from comment #31)
> (In reply to Luke Kenneth Casson Leighton from comment #30)
> > (In reply to Jock Tanner from comment #29)
> >
> > > I checked 'dir(Cell)' and it really has no
> > > 'getTerminalNetlistInstanceOccurrences' attribute. My Coriolis is up to
> > > date. Is Alliance toolkit now ahead of Coriolis?
> >
> > remember, coriolis2 is a c++ application (not a pure python application),
> > with "wrapper" python bindings around the c++ code. after the git pull you
> > need to rebuild the c++ code.
>
> My Coriolis is already up to date, on 'devel' branch. Its code didn't change
> since the last time I built it. Just reran 'bootstrap/ccb.py' to make sure.
> And its current C++ code does not contain the identifiers
> 'getTerminalNetlistInstanceOccurrences' or
> 'getNonTerminalNetlistInstanceOccurrences'. The repository is not recursive,
> the names just can't come out of thin air.
>
> The only thing I can come up with is that alliance toolkit is ahead of
> Coriolis. Or what else can it be?
Are you on Coriolis commit b07a4722 ? (the latest one).
The getTerminalNetlistInstanceOccurrences methods were commited with
dfe4d80b four commits ago (and one week). Are you sure you did
rebuild & rinstall Coriolis ? You may check the contents of the
library with:
> nm libhurricane.so | grep TerminalNetlist
You should have lots of references if it is the right 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
* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-03-17 17:24 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 #32 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #31)
> (In reply to Luke Kenneth Casson Leighton from comment #30)
> > (In reply to Jock Tanner from comment #29)
> >
> > > I checked 'dir(Cell)' and it really has no
> > > 'getTerminalNetlistInstanceOccurrences' attribute. My Coriolis is up to
> > > date. Is Alliance toolkit now ahead of Coriolis?
> >
> > remember, coriolis2 is a c++ application (not a pure python application),
> > with "wrapper" python bindings around the c++ code. after the git pull you
> > need to rebuild the c++ code.
>
> My Coriolis is already up to date, on 'devel' branch. Its code didn't change
> since the last time I built it. Just reran 'bootstrap/ccb.py' to make sure.
> And its current C++ code does not contain the identifiers
> 'getTerminalNetlistInstanceOccurrences' or
> 'getNonTerminalNetlistInstanceOccurrences'.
do "git log" | head just to make absolutely sure.
> The repository is not recursive,
> the names just can't come out of thin air.
correct. they're in this git diff:
git diff dfe4d80b e2d69
> The only thing I can come up with is that alliance toolkit is ahead of
> Coriolis.
correct.
which means... you've not git pulled correctly and/or are on the master branch
not the devel branch
https://gitlab.lip6.fr/vlsi-eda/coriolis
here is the commit:
https://gitlab.lip6.fr/vlsi-eda/coriolis/commit/dfe4d80b600601dca1255de6d7066ecabe7985ec
ah.
i know what it is.
(coriolis2)lkcl@fizzy:~/coriolis-2.x/Linux.x86_64/Release.Shared/install$ ls
-altr
total 0
drwxr-xr-x 1 lkcl lkcl 18 Mar 4 04:56 etc
drwxr-xr-x 1 lkcl lkcl 24 Mar 4 04:56 ..
drwxr-xr-x 1 lkcl lkcl 42 Mar 4 04:56 .
drwxr-xr-x 1 lkcl lkcl 26 Mar 4 04:56 share
drwxr-xr-x 1 lkcl lkcl 56 Mar 4 04:56 include
drwxr-xr-x 1 lkcl lkcl 3276 Mar 16 23:10 lib
drwxr-xr-x 1 lkcl lkcl 240 Mar 16 23:10 bin
(coriolis2)lkcl@fizzy:~/coriolis-2.x/Linux.x86_64/Release.Shared/install$
what do you have in this directory?
you wouldn't *happen* to have two subdirectories - one named "lib" and one
named "lib64", would you?
suggestion: blow the entire ~/coriolis-2.x/Linux.x86_64 directory away and
re-run ccb bootstrap.
--
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 17:06 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 #31 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #30)
> (In reply to Jock Tanner from comment #29)
>
> > I checked 'dir(Cell)' and it really has no
> > 'getTerminalNetlistInstanceOccurrences' attribute. My Coriolis is up to
> > date. Is Alliance toolkit now ahead of Coriolis?
>
> remember, coriolis2 is a c++ application (not a pure python application),
> with "wrapper" python bindings around the c++ code. after the git pull you
> need to rebuild the c++ code.
My Coriolis is already up to date, on 'devel' branch. Its code didn't change
since the last time I built it. Just reran 'bootstrap/ccb.py' to make sure. And
its current C++ code does not contain the identifiers
'getTerminalNetlistInstanceOccurrences' or
'getNonTerminalNetlistInstanceOccurrences'. The repository is not recursive,
the names just can't come out of thin air.
The only thing I can come up with is that alliance toolkit is ahead of
Coriolis. Or what else can it be?
--
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] provisional Vulkan ray tracing extension published
From: Luke Kenneth Casson Leighton @ 2020-03-17 16:44 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7CVp6ZTBDDkP4gTzb-txG4skVnBLwF4sNmn3UmKpFj+g@mail.gmail.com>
On Tue, Mar 17, 2020 at 4:30 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Khronos published the provisional version of their non-vendor-specific ray
> tracing extension:
> https://www.khronos.org/news/press/khronos-group-releases-vulkan-ray-tracing
iiinterestiiing
_______________________________________________
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 16:41 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 #30 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #29)
> I checked 'dir(Cell)' and it really has no
> 'getTerminalNetlistInstanceOccurrences' attribute. My Coriolis is up to
> date. Is Alliance toolkit now ahead of Coriolis?
remember, coriolis2 is a c++ application (not a pure python application), with
"wrapper" python bindings around the c++ code. after the git pull you need to
rebuild the c++ code.
--
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] provisional Vulkan ray tracing extension published
From: Jacob Lifshay @ 2020-03-17 16:30 UTC (permalink / raw)
To: Libre-RISCV General Development
Khronos published the provisional version of their non-vendor-specific ray
tracing extension:
https://www.khronos.org/news/press/khronos-group-releases-vulkan-ray-tracing
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-03-17 16:06 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 #29 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Jock Tanner from comment #27)
> (In reply to Luke Kenneth Casson Leighton from comment #25)
> > and alliance-check-toolkit:
> >
> > [remote "origin"]
> > url = https://gitlab.lip6.fr/vlsi-eda/alliance-check-toolkit.git
> >
> > where branch should be "master".
>
> tanner@ibmpc:~/alliance-check-toolkit$ git status
> On branch master
> Your branch is up to date with 'origin/master'.
>
>
> > you should be on:
> >
> > commit 622019240ff7d9c00927ee52556401091436ec2e
> > Merge: e5fa9a6 e385909
> > Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
> > Date: Sun Mar 15 23:59:43 2020 +0100
>
> I was 10 days behind, on e3859099a6f55b14e7b76388a8f885c4b78ea8fd, but now I
> did 'git pull' and don't see changes in relevant files.
Well, Luke, I am on the same commit as you now, and I get this:
> make vst
>
> ...
>
> + sub [.model]
> + /home/tanner/alliance/install/cells/sxlib/on12_x1.vbe [behavioral]
> + /home/tanner/alliance/install/cells/sxlib/on12_x1.ap
> + /home/tanner/alliance/install/cells/sxlib/no4_x1.vbe [behavioral]
> + /home/tanner/alliance/install/cells/sxlib/no4_x1.ap
> + /home/tanner/alliance/install/cells/sxlib/ao2o22_x2.vbe [behavioral]
> + /home/tanner/alliance/install/cells/sxlib/ao2o22_x2.ap
> Traceback (most recent call last):
> File "/home/tanner/alliance-check-toolkit/bin/blif2vst.py", line 71, in <module>
> renameNMigenUniquify( cell )
> File "/home/tanner/alliance-check-toolkit/bin/blif2vst.py", line 32, in renameNMigenUniquify
> for occurrence in topCell.getTerminalNetlistInstanceOccurrences():
> AttributeError: 'Hurricane.Cell' object has no attribute 'getTerminalNetlistInstanceOccurrences'
> make: [mk/synthesis-yosys.mk:73: alu16.vst] Error 1 (ignored)
I checked 'dir(Cell)' and it really has no
'getTerminalNetlistInstanceOccurrences' attribute. My Coriolis is up to date.
Is Alliance toolkit now ahead of Coriolis?
--
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 15:24 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 #28 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #26)
> (In reply to Jean-Paul.Chaput from comment #12)
>
> > 3. Direct command line.
> > I wanted especially the GUI to be able to recover after
> > an exception is raised, to do some forensic.
> > It is far from perfect but did help me much while debugging.
>
> yes that makes sense.
>
> i *think* there may be a better way to do that,
> hmmm https://wiki.python.org/moin/PythonDebuggingTools
>
> ah yes:
> https://docs.python.org/3/library/pdb.html
>
> python3 -m pdb {scriptname.py}
Oh, being unable to use Pycharm's built-in debugger, I had to resort to ipdb.
It's like pdb but nicer. It's possible to just throw
'import ipdb; ipdb.set_trace()'
anywhere in the source file, and it opens its console there.
But exception wrappers are perfectly valid. Sometimes even indispensable. In
Celery tasks, for example. It's just may be more convenient to use
'traceback.print_exception()' inside them instead of 'print()'.
https://docs.python.org/2.7/library/traceback.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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-03-17 15: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 #27 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #25)
> for alliance you should have this in .git/config:
> [remote "origin"]
> url = https://gitlab.lip6.fr/vlsi-eda/alliance.git
>
> where git branch should be "master"
tanner@ibmpc:~/alliance/alliance$ git status
On branch master
Your branch is up to date with 'origin/master'.
> and for coriolis2:
>
> [remote "origin"]
> url = https://gitlab.lip6.fr/vlsi-eda/coriolis.git
> ...
> ...
> [branch "devel"]
> remote = origin
> merge = refs/heads/devel
>
> where git branch should be "devel".
tanner@ibmpc:~/coriolis-2.x/src/coriolis$ git status
Refresh index: 100% (8230/8230), done.
On branch devel
Your branch is up to date with 'origin/devel'.
> and alliance-check-toolkit:
>
> [remote "origin"]
> url = https://gitlab.lip6.fr/vlsi-eda/alliance-check-toolkit.git
>
> where branch should be "master".
tanner@ibmpc:~/alliance-check-toolkit$ git status
On branch master
Your branch is up to date with 'origin/master'.
> you should be on:
>
> commit 622019240ff7d9c00927ee52556401091436ec2e
> Merge: e5fa9a6 e385909
> Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
> Date: Sun Mar 15 23:59:43 2020 +0100
I was 10 days behind, on e3859099a6f55b14e7b76388a8f885c4b78ea8fd, but now I
did 'git pull' and don't see changes in relevant files.
--
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 14: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 #26 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #12)
> 3. Direct command line.
> I wanted especially the GUI to be able to recover after
> an exception is raised, to do some forensic.
> It is far from perfect but did help me much while debugging.
yes that makes sense.
i *think* there may be a better way to do that,
hmmm https://wiki.python.org/moin/PythonDebuggingTools
ah yes:
https://docs.python.org/3/library/pdb.html
python3 -m pdb {scriptname.py}
--
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 14:52 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 #25 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #23)
> (In reply to Luke Kenneth Casson Leighton from comment #22)
> > arse. oh wait - don't run "make lvx". i just tried that, and yes i got
> > an error.
> >
> >
> > do this:
> >
> > make clean
> > make vst <---- makes the VHDL
> > cgt --script=doAlu16
>
> This way I get another error:
>
> > [ERROR] An exception occured while loading the Python script module:
> > "doAlu16"
> > You should check for simple python errors in this module.
> > Python stack trace:
> > #0 in placeAndRoute() at doAlu16.py:46
> > #1 in add() at doAlu16.py:193
> > #2 in ScriptMain() at doAlu16.py:437
> > #3 in runScript() at .../coriolis-2.x/Linux.x86_64/Release.Shared/install/bin/cgt:83
> > Error was:
> > [BUG] Unmanaged Configuration [16843009] = [1+1+0+1,1+0] <id:1493 Net "a(12)" e-- LOGICAL i--- (IN)> in <id:2921 Anabatic::GCell <Box 250l 350l 300l 400l> ----------M---,--A- 9>
ah. that tells me that you may be on the wrong branch (or git repo)
> > The global routing seems to be defective.
> > Trying to continue anyway...
>
> And the picture in cgt looks really funny, more like child's drawing. And
> it's called 'add', not 'alu16.
there's three functions that do routing, and they are all separate functions:
* add() - which uses add.vst to create add.ap
* sub() - which uses sub.vst to create sub.ap
* alu16() - which uses alu16.vst *and* add.ap/vst *and* sub.ap/vst to create
alu16.ap
> Maybe that's all because our toolchain's versions are out of sync?
that seems likely. did you check the git versions i sent a couple of messages
back?
for alliance you should have this in .git/config:
[remote "origin"]
url = https://gitlab.lip6.fr/vlsi-eda/alliance.git
where git branch should be "master"
and for coriolis2:
[remote "origin"]
url = https://gitlab.lip6.fr/vlsi-eda/coriolis.git
...
...
[branch "devel"]
remote = origin
merge = refs/heads/devel
where git branch should be "devel".
and alliance-check-toolkit:
[remote "origin"]
url = https://gitlab.lip6.fr/vlsi-eda/alliance-check-toolkit.git
where branch should be "master".
you should be on:
commit 622019240ff7d9c00927ee52556401091436ec2e
Merge: e5fa9a6 e385909
Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
Date: Sun Mar 15 23:59:43 2020 +0100
Merge branch 'master' of gitlab.lip6.fr:vlsi-eda/alliance-check-toolkit
commit 93cd988d07037b71c3b8497c4c376b1d7d151f71
Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
Date: Wed Nov 13 17:47:22 2019 +0100
Stable AP read/write generation.
commit b07a4722509bfcb2aacdb72d3122793e4bf377ea
Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
Date: Sun Mar 15 23:58:31 2020 +0100
Dynamic detection of Coriolis2 library directory.
--
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-17 14:43 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 #49 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #48)
> > ok just for a laugh i'm going to run public-inbox-httpd, which is
> > now set up on http://inbox.libre-riscv.org/libre-riscv-dev
> So you are using subdomains by adding A records in DNS.
yes. i found that proxy redirect would send to the wrong
path. i don't know why.
> You can also use nginx reverse proxy so that
> http://libre-riscv.org:8080/pi/libre-riscv-dev becomes some path as
> http://libre-riscv.org:80/pi/libre-riscv-dev
i had to use this:
location /{
access_log /var/log/nginx/public-inbox-httpd_access.log;
error_log /var/log/nginx/public-inbox-httpd_error.log;
proxy_set_header HOST $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:8080$request_uri;
proxy_buffering off;
}
efforts to change it to work as location /publicinbox met with...
resistance :)
--
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 14:22 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 #24 from Jock Tanner <tanner.of.kha@gmail.com> ---
BTW I've scaled the bit width of both modules down to 4. I thought it'd be
easier to debug this way, but I got no errors this way. May I share the
pictures?
And I also wonder where the 'op' pin went?
--
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 14:19 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 #23 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #22)
> arse. oh wait - don't run "make lvx". i just tried that, and yes i got
> an error.
>
>
> do this:
>
> make clean
> make vst <---- makes the VHDL
> cgt --script=doAlu16
This way I get another error:
> [ERROR] An exception occured while loading the Python script module:
> "doAlu16"
> You should check for simple python errors in this module.
> Python stack trace:
> #0 in placeAndRoute() at doAlu16.py:46
> #1 in add() at doAlu16.py:193
> #2 in ScriptMain() at doAlu16.py:437
> #3 in runScript() at .../coriolis-2.x/Linux.x86_64/Release.Shared/install/bin/cgt:83
> Error was:
> [BUG] Unmanaged Configuration [16843009] = [1+1+0+1,1+0] <id:1493 Net "a(12)" e-- LOGICAL i--- (IN)> in <id:2921 Anabatic::GCell <Box 250l 350l 300l 400l> ----------M---,--A- 9>
> The global routing seems to be defective.
> Trying to continue anyway...
And the picture in cgt looks really funny, more like child's drawing. And it's
called 'add', not 'alu16.
Maybe that's all because our toolchain's versions are out of sync?
--
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-17 14:12 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 #48 from vklr@vkten.in <vklr@vkten.in> ---
(In reply to Luke Kenneth Casson Leighton from comment #45)
> yippee! thank you, veera. i made one small change to the config:
> set umask=066 because after writing to /home/publicinbox/libre-riscv-dev.git
> if the umask is 077 then gitweb will not be able to see the files for
> publishing them via git.libre-riscv.org
>
Yes. You have to set as your requiremnet.
> wha-hey, it works!
>
> ok just for a laugh i'm going to run public-inbox-httpd, which is
> now set up on http://inbox.libre-riscv.org/libre-riscv-dev
So you are using subdomains by adding A records in DNS.
You can also use nginx reverse proxy so that
http://libre-riscv.org:8080/pi/libre-riscv-dev becomes some path as
http://libre-riscv.org:80/pi/libre-riscv-dev
--
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-17 14:03 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
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #47 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #46)
> > whereas what we want is the mail delivered *from mailman*, where
> > "publicinbox@libre-riscv.org" happens to be one of the recipients.
>
> Yes.
thanks veera. all good! really appreciate your help on this. sorry it took
me a while to work out what was needed.
--
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-17 14:01 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 #46 from vklr@vkten.in <vklr@vkten.in> ---
(In reply to Luke Kenneth Casson Leighton from comment #43)
> wait... hang on... i should check: this should be checking for what
> goes to the *user that is subscribed to the list*.
>
> not the actual list itself, is that correct?
>
> so:
>
> public_inbox:
> debug_print = "R: public_inbox for $local_part@$domain"
> driver = accept
> # require_files = PI_HOME/check.pck
> domains = libre-riscv.org
> check_local_user
> local_parts = publicinbox
> transport = public_inbox_transport
>
> not:
>
> domains = lists.libre-riscv.org
> check_local_user
> local_parts = libre-riscv-dev
>
> this latter i believe would take *all* email sent to
> libre-riscv-dev@lists.libre-riscv.org and push it into public-inbox
>
Yes.
> whereas what we want is the mail delivered *from mailman*, where
> "publicinbox@libre-riscv.org" happens to be one of the recipients.
Yes.
--
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-17 13:49 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 #45 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
yippee! thank you, veera. i made one small change to the config:
set umask=066 because after writing to /home/publicinbox/libre-riscv-dev.git
if the umask is 077 then gitweb will not be able to see the files for
publishing them via git.libre-riscv.org
wha-hey, it works!
ok just for a laugh i'm going to run public-inbox-httpd, which is
now set up on http://inbox.libre-riscv.org/libre-riscv-dev
--
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 13:48 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 #22 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jock Tanner from comment #21)
> (In reply to Luke Kenneth Casson Leighton from comment #20)
> > ok try that, jock - but before doing so, have a look at alu16.ap
> > (if you can)
>
> I dug up this:
>
> http://manpages.ubuntu.com/manpages/bionic/man5/ap.5.html
>
> and I looked at the file knowing approximately what kind of problem it
> solves.
sorry, sorry, i meant "look at it with make cgt" followed by "File-Open"
and type "alu16".
or, yes, use "cgt --script=doAlu16"
the .ap files are basically purely positions of components etc. and the
tracks. looking at them (directly) will drive you nuts :)
> I pulled your changes and did only
>
> make clean
> make lvx
> cgt --script=doAlu16
>
> Still I got exactly the same error as before.
arse. oh wait - don't run "make lvx". i just tried that, and yes i got
an error.
do this:
make clean
make vst <---- makes the VHDL
cgt --script=doAlu16
the reason is: "make lvx" will *already create* the .ap files. however - and
this is quite smart - doAlu16.py is instructed to *pick up* (read) them if they
exist, because we might want to do a bit of work (some place), then save them,
and do some routing later on.
loadCell Catalog.State.Logical will load only the VHDL files (alu16.vhd
then add.vhd and sub.vhd because those are sub-components)
loadCell Catalog.State.Views will load *everything* that exists:
alu16.vhd, alu16.ap, *and* the sub-components of those as well
(add.vhd, add.ap, sub.vhd, sub.ap - you can see the hierarchy
in the log output)
> And the picture is just a
> quarter of the 'make view' picture size.
that's ok - just resize it then press "F"
--
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 13:04 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 #21 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #20)
> ok try that, jock - but before doing so, have a look at alu16.ap
> (if you can)
I dug up this:
http://manpages.ubuntu.com/manpages/bionic/man5/ap.5.html
and I looked at the file knowing approximately what kind of problem it solves.
Still the file is huge and I don't think I can debug the code just by looking
at it. I just wonder how many 'I' records it has. Shouldn't it be like 3
instances? Or is this because each bit slice counts?
> the placement of the cells all over the large area (1100 x 700)
> meant that when it comes to routing, it is a total mess.
>
> what i've done is: limited the "placement" box for the remaining
> (little) components - Cells - of alu16 to be in the MIDDLE.
>
> *between* add and sub.
>
> then, the auto-router can not only successfully connect those up,
> it has room to connect to add and sub as well.
>
> now, it turns out that if you move add and sub down by even 25 units,
> *there is not enough room to add the tracks* connecting them to the
> outside world.
I pulled your changes and did only
make clean
make lvx
cgt --script=doAlu16
Still I got exactly the same error as before. And the picture is just a quarter
of the 'make view' picture size.
--
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-17 11:12 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 #44 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok i think i have it working (tested with mailman@lists.libre-riscv.org)
this is a test of the list
--
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-17 10:44 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 #42 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #41)
> > veera did you modify 900_exim4-config_local_user?
> >
>
> No!
ok. just double-checking.
> > and all other domains (of which there are a few) will be left alone, correct?
> >
>
> Yes, correct.
excellent! i will try it out, now.
> > how do you specify multiple local_parts? we will have multiple lists.
> exim4 lists:
>
> local_parts = libre-riscv-dev : libre-riscv-misc : abc : def
>
> Must give a space before and after the colon.
ah :) thank you.
--
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-17 9:22 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 #41 from vklr@vkten.in <vklr@vkten.in> ---
(In reply to Luke Kenneth Casson Leighton from comment #40)
> exim4: routers - please note order of routers is important
> otherwise mail would reach one and not other router
> 890_local_pi
> 900_exim4-config_local_user
>
> veera did you modify 900_exim4-config_local_user?
>
No!
890_local_pi takes all the mail for test@test.local before
900_exim4-config_local_user does. See test is local user, so by default it gets
delivered to mail_spool by 900_exim4... router.
> also... will this make *all* mail go into the "public_inbox" section?
> (890-local_pi)?
>
> or is it, because it is "local_parts=test", that is a "filter" which
> captures just that email address, test@test.local, correct?
>
Yes. Just this test@test.local email address.
local_parts is one before @
domains in one (full) after @ i.e test.local
> so i will need to change that to:
>
> local_parts=libre-riscv-dev
>
Yes. Exactly.
> and domains to:
>
> domains = lists.libre-riscv.org
>
Yes.
> and all other domains (of which there are a few) will be left alone, correct?
>
Yes, correct.
> how do you specify multiple local_parts? we will have multiple lists.
> is it
>
> local_parts=[libre-riscv-dev, libre-riscv-misc, ....]
>
exim4 lists:
local_parts = libre-riscv-dev : libre-riscv-misc : abc : def
Must give a space before and after the colon.
> i am not sure of the syntax.
--
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