From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 284] TypeError Object is not an nMigen signal
Date: Tue, 14 Apr 2020 11:37:40 +0000
Message-ID: <bug-284-13-eXq8Cm6ZML@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-284-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=284
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Tobias Platen from comment #2)
> I am using the https://github.com/nmigen/nmigen repo,
> but our documentation says https://github.com/m-labs/nmigen
please do update the documentation - don't wait, just do it
(and send a message to the list saying that it's been done).
> I am using the soc repo and the Kazan-team pipeline has failed too.
> https://salsa.debian.org/Kazan-team/soc/pipelines/125651/failures.
when those messages are available in a resource controlled by us - not
by debian, not by the proprietary hosting company gitlab - and replicable
by anyone, without requiring a permanent internet connection - i'll take a
look at them.
(reminds me, we really must do something about making bugzilla available
offline)
> The error is a different one in this case:
> ModuleNotFoundError (No module named 'alu_hier')
i'm dealing with some augmentations and changes to the 6600 scoreboard,
which is a particularly complex area.
--
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
next prev parent reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 8:26 [libre-riscv-dev] [Bug 284] New: " bugzilla-daemon
2020-04-14 8:38 ` [libre-riscv-dev] [Bug 284] " bugzilla-daemon
2020-04-14 11:09 ` bugzilla-daemon
2020-04-14 11:37 ` bugzilla-daemon [this message]
2020-04-15 16:57 ` bugzilla-daemon
2020-04-15 21:08 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-284-13-eXq8Cm6ZML@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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