Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Tobias Platen <hacks2019@platen-software.de>,
	Tobias Platen <tplaten@posteo.de>,
	 Tobias Platen <libre-soc@platen-software.de>,
	 Libre-RISCV General Development
	<libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] tobias: note the comment here in bug #216
Date: Fri, 5 Jun 2020 16:51:11 +0100
Message-ID: <CAPweEDy0F-HLhs-aR7S48YdHwZjo8kqoSA==rYZ8HBcse4b6=Q@mail.gmail.com> (raw)

tobias i have not seen an acknowledgement that this has been actioned:
https://bugs.libre-soc.org/show_bug.cgi?id=216

it would be much easier if you could acknowledge things. i have to
spend considerable time tracking through the git logs, monitoring them
and cut/pasting commit log messages into the bugtracker on your behalf.

with the large number of things that i am tracking, not having a response
makes it extremely difficult for me.

if you can respond and track the bugreports, and reply in them "actioned
this change as required" and so on, it cuts the amount of work that i have
to do considerably.

thanks.

l.

proof_datamerger.py:

                for b in range(0,8):

just range(8).  there is no need to specify a start range of 0

            comb += dut.addr_array_i[j].eq(AnySeq(dut.array_size))
            comb += dut.data_i[j].eq(AnySeq(16+128))

AnySeq is for synchronous data where the value changes on every clock.
use AnyConst instead which will not change.


---
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

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPweEDy0F-HLhs-aR7S48YdHwZjo8kqoSA==rYZ8HBcse4b6=Q@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=hacks2019@platen-software.de \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    --cc=libre-soc@platen-software.de \
    --cc=tplaten@posteo.de \
    /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