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] Pinout, interfaces, Rudi, and Raptor
Date: Fri, 8 May 2020 16:03:55 +0100
Message-ID: <CAPweEDw7FF9jhAY7Bxvzkj2wPLcaRFtmmgtMy+sCTDbioQG4ow@mail.gmail.com> (raw)
In-Reply-To: <3BD26F5C-BB6D-4011-89E6-EC06215DEDEA@gatech.edu>
On Fri, May 8, 2020 at 3:20 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Hello Luke,
> So I see we have some pinout sdefine here.
>
> https://libre-soc.org/shakti/m_class/pinouts/ <https://libre-soc.org/shakti/m_class/pinouts/>
>
>
> My suggestion is to drop the pinmux for now.
it needs writing anyway [not to use Bluespec]. that was *another*
project that took 3 months to do and we can't really use because it's
hard-coded to what the Shakti Team use in IIT Madras. *sigh*.
> We should probably update that page(or create a similar page) to reflect what we’re targeting for October.
already done https://libre-soc.org/180nm_Oct2020/interfaces/
> IIRC, we’re targeting QFP. I don’t see the dimensions or form factor we’re targeting listed there however. We should talk about that.
>
> Also, talked with Tim and SDR could work for the first SBC.
update interfaces page https://libre-soc.org/180nm_Oct2020/interfaces/?updated
> LiteX also supports SDR which is good for us as it doesn’t require a PHY like DDR making it simpler.
yes. and it's silicon-proven via the Shakti Team, in their first 22nm
ASIC from 2 years ago.
> Luke, should I connect Rudi to Tim?
hmmm.... in my mind, the roles do not really match up. they do
however with one of us (by "us" i mean you :) given that i'm trying to
focus on heavily-technical development) as the intermediary
roles:
* Rudi's asked specifically for the interfaces, he'll write a spec as
a PDF and if we say "go" he'll get on with it.
* Tim's role here is as the "customer" plus he's busy.
therefore i suggest:
* *we* need to capture the requirements (of Tim) - by "we" i mean you
* go over them, discuss and approve them (whole team)
* *then* authorise Rudi to go ahead with a design document (i send the message)
* then go over that and discuss and review it (whole team)
* *then* notify Rudi "please go ahead" (i send the message)
l.
_______________________________________________
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: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 14:20 Yehowshua
2020-05-08 15:03 ` Luke Kenneth Casson Leighton [this message]
2020-05-09 9:12 ` Staf Verhaegen
2020-05-09 10:02 ` Luke Kenneth Casson Leighton
2020-05-09 14:39 ` Yehowshua
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=CAPweEDw7FF9jhAY7Bxvzkj2wPLcaRFtmmgtMy+sCTDbioQG4ow@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