Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 25may2020
Date: Mon, 25 May 2020 15:11:16 -0700
Message-ID: <EF27EE71-46C9-426B-93EC-A7DDC61E804E@getmailspring.com> (raw)
In-Reply-To: <CAPweEDy4iGcxj9J3p9MdJDhMku6_f6Xj4zMusU-AxHWa+_G8Hg@mail.gmail.com>

On May 25 2020, at 2:35 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> in your wiki home page you will find a link to bugs assigned to you.  the
> default action is basically "monitor and do that list".

Thanks that makes it easy. I saw you assigned me 'Bug 337 - Convention
for register outputs in *OutputData structures is to use "Data"', and
looked at your comment. Is this simply reorg or is there something
additional I should be aware of?
 
> one to add:
> 
> if you can also find the "interfaces" issue, and assign it to
> yourself, you
> will see a list of interfaces in the last comment, including "serialized
> irq" which you shouls find somewhere from raptor engineering.
> 
> can you track the source code down, add them to the wiki  under the right
> subdurectory (shakti mclass) and also crossreference them in the bugtracker?


Are you referring to "Bug 304 - Define minimum viable interface set for
180nm ASIC", comment #6?
```
Luke Kenneth Casson Leighton 2020-05-20 23:14:26 BST

conversation notes from Tim (Raptor Engineering)

priority:

* 2x SPI master
* 4x I2C master
* 2x UART
* 4x LPC master
* EINT* Serialsed IRQ (LPC, from PCIe) - 15 or so IRQs, these are
PC>PCIe>OpenPower mappings

Quad SPI raptorengineering
LPC bridge github raptorengineering
```

I searched for "raptor serialized irq, and only found references to
raptors lpc-spi-bridge-fpga gitlab repo. Is this what we need
https://gitlab.raptorengineering.com/raptor-engineering-public/lpc-spi-bridge-fpga?
An in terms of adding the source code to the wiki, do you want me to
just copy and paste the 1000+ line verilog file or files to the
soc/libreriscv/shakti/m_class directory? Or do you want me to do
something similar to what you did for sdram.mdwn in the same directory?

```
# SDRAM

* <https://bitbucket.org/casl/c-class/src/3fba75dfbd0c64815eb8ec6dc965666812c44bae/src/peripherals/sdram/?at=master>
* <https://opencores.org/projects/sdr_ctrl>
```

Cole

_______________________________________________
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: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 12:30 Luke Kenneth Casson Leighton
2020-05-25 14:20 ` Tobias Platen
2020-05-25 14:27   ` Luke Kenneth Casson Leighton
2020-05-25 16:39 ` Michael Nolan
2020-05-25 18:29   ` Luke Kenneth Casson Leighton
2020-05-25 17:41 ` Cesar Strauss
2020-05-25 18:47   ` Luke Kenneth Casson Leighton
2020-05-25 19:30 ` Jacob Lifshay
2020-05-25 19:40   ` Luke Kenneth Casson Leighton
2020-05-25 21:06     ` Cole Poirier
2020-05-25 21:35       ` Luke Kenneth Casson Leighton
2020-05-25 22:11         ` Cole Poirier [this message]
2020-05-25 22:45           ` Luke Kenneth Casson Leighton
2020-05-25 23:22             ` Cole Poirier
2020-05-25 23:40               ` Luke Kenneth Casson Leighton
2020-05-26  0:11                 ` Cole Poirier

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=EF27EE71-46C9-426B-93EC-A7DDC61E804E@getmailspring.com \
    --to=colepoirier@gmail.com \
    --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