From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban 07may2020 update
Date: Fri, 8 May 2020 03:26:11 +0100
Message-ID: <CAPweEDzUw8jNQaZ4eJDQQwBrt1-uMPEyzdE8TN-VrRijJAxVoA@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6EWrcrxbva=XeUokF3Csu4t0cF0LWVw8mCwZUJ55Ku7g@mail.gmail.com>
On Friday, May 8, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> I attended the OpenPower virtual coffee meeting, there was an interesting
> suggestion to see if we could move to a later tapeout than october, to
> avoid burnout due to deadline crunch.
i've written to Staf to see what is available. if you recall we have an
agreement to let him use the Oct2020 slot. so he is "2nd in queue".
there were other ideas to do a simpler processor for that slot. however
these would likely go to the *back* of the queue (as a new request for that
slot: "3rd in queue").
>
> I also weighed in on nmigen signed/unsigned sign extension/zero
> extension/truncation operators:
> https://github.com/nmigen/nmigen/issues/381
ah as long as they are explicit rules that in no way change current
behavior (like the signed shift one which caused unit tests to inexplicably
fail for no reason right when we do not need the hassle) we're good.
> still slowly getting through the load/store unit stuff, progress may be a
> little slow since I have a bunch of stuff I need to do at home as well.
ok.
remember, address is divided as:
* bits 0 to 3 plus len turned into 16 bit mask
* bit 4 is for odd-even L1 cache bank selection.
* bits 5 thru 11 go through a 2D AddrMatch, as part of the DMs
* bits 12 and above need checking in 1D, *only* in the L0CacheBuffer.
however if you completely ignore *everything* and i mean everything other
than PortInterface (and the prototype L0CacheBuffer) and just do a
comparison on the full bits 5 thru 48 we can add the information from
AddrMatch later.
the task needed really is genuinely much simpler than it seems. estimated
about... 100 lines of code.
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
next prev parent reply index
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 10:26 Luke Kenneth Casson Leighton
2020-05-07 18:25 ` Michael Nolan
2020-05-07 18:48 ` Tobias Platen
2020-05-07 18:55 ` Luke Kenneth Casson Leighton
2020-05-07 23:23 ` Jacob Lifshay
2020-05-07 23:28 ` Yehowshua
2020-05-08 2:26 ` Luke Kenneth Casson Leighton [this message]
2020-05-08 8:41 ` Staf Verhaegen
2020-05-08 8:51 ` Yehowshua
2020-05-08 9:08 ` Luke Kenneth Casson Leighton
2020-05-08 10:46 ` Luke Kenneth Casson Leighton
2020-05-08 11:02 ` Staf Verhaegen
2020-05-08 11:18 ` Luke Kenneth Casson Leighton
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=CAPweEDzUw8jNQaZ4eJDQQwBrt1-uMPEyzdE8TN-VrRijJAxVoA@mail.gmail.com \
--to=lkcl@lkcl.net \
--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