Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
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 update 04aug2020
Date: Wed, 5 Aug 2020 20:02:46 +0100
Message-ID: <CAPweEDynfs123E+vbuBpeMKRB3Q_Cgs-xFYFW8HuvK8PLTo60w@mail.gmail.com> (raw)
In-Reply-To: <20200805205506.4836c315587bdc10c33064f2@platen-software.de>

On Wed, Aug 5, 2020 at 7:55 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> On Wed, 5 Aug 2020 19:39:20 +0100
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> > this means that instead of having a 16 bit mask to cover 128 bits of
> > data,  a whopping *128* bit mask is needed and that's precisely what
> > we do not want.
> I think now understand my mistake in thinking and how to solve the problem.

cool.

basically, the mask is wishbone "sel", set to a granularity of 8 bits
(one byte) per bit of "sel".

if you read the wishbone spec, concentrating on when "sel" is not just
a single bit, you'll see clearly what is needed.

we are propagating that byte-per-bit mask RIGHT THE WAY THROUGH THE
ENTIRE DESIGN.

it starts at LD/ST - right back when a byte, half-word, word or dword
LD/ST is requested - and goes - will go - through the ENTIRE design

through PortInterface.

through LDSTSplitter.

through DataMerger.

through the L1 cache which will need to respect byte-level masks

through the L2 cache which will need to respect byte-level masks.

through the wishbone buses which will need to respect byte-level masks

through to the DDR / SDR bus which will *ALSO* need to respect byte-level masks.

eeeeverything and i *mean* everyting.

SDR (DDR1, SDRAM) does in fact accept byte-level masks.

if at any time we encounter a memory system which does *NOT* respect
byte-level masks, then we have a problem and will have to rethink.

l.

_______________________________________________
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: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 12:45 Luke Kenneth Casson Leighton
2020-08-04 15:34 ` Luke Kenneth Casson Leighton
2020-08-04 17:18 ` Tobias Platen
2020-08-04 17:32   ` Luke Kenneth Casson Leighton
2020-08-05 16:40     ` Tobias Platen
2020-08-05 16:48       ` Tobias Platen
2020-08-05 17:08         ` Luke Kenneth Casson Leighton
2020-08-05 17:37           ` Tobias Platen
2020-08-05 18:39             ` Luke Kenneth Casson Leighton
2020-08-05 18:55               ` Tobias Platen
2020-08-05 19:02                 ` Luke Kenneth Casson Leighton [this message]

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=CAPweEDynfs123E+vbuBpeMKRB3Q_Cgs-xFYFW8HuvK8PLTo60w@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