From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
Date: Sat, 13 Jun 2020 03:37:32 +0000
Message-ID: <bug-376-13-Wserrlqp5T@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #25 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i took a look at the OPENCAPI PDF on the proposed interfaces. IBM put OpenCAPI
2 was on top of 8x PCIe 4.0
the later slides, blacked out, show rhat POWER7 was in 40nm.
later, by the time they move to 25GBit/s, they are for POWER9 which is in 14nm.
this, in conjunction with the power requirements, basically tells us that there
is an unachievable mismatch between 25.6 Gbit/s SERDES and a 40/45nm target.
if we were instead to target 14nm or below, we could achieve a 25 GBit/s SERDES
PHY.
this however would require that, as our first major production chip, we seek a
minimum of USD 20 million funding.
if however we stick to PCIe @ 3200 mhz, this *is* achievable in 40/45nm. with
sufficient lanes it becomes possible to reach the bandwidth required, and to
not expect investors to take a huge risk on an unproven team.
alternatively, we stick with plain DDR3/4 because it is also achievable, but
expensive and timeconsuming (SymbioticEDA: 8 to 12 months fulltime work on a
PHY, USD 600,000).
alternatively, we use multiple HyperRAM interfaces and overclock the protocol,
connecting to a suitable FPGA that either has a DDR3/4 interface *or* suitable
SERDES sufficient to do OpenCAPI. the ECP5G springs to mind although its DRAM
interface is only capable of 200mhz (400mhz DDR).
the advantage of a 3200 mhz SERDES is that it is useful for a large number of
things that rely on a PCIe PHY. OpenCAPI, HMC, and PCIe itself.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
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: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 13:30 [libre-riscv-dev] [Bug 376] New: " bugzilla-daemon
2020-06-12 13:31 ` [libre-riscv-dev] [Bug 376] " bugzilla-daemon
2020-06-12 13:52 ` bugzilla-daemon
2020-06-12 15:14 ` bugzilla-daemon
2020-06-12 15:27 ` bugzilla-daemon
2020-06-12 16:17 ` bugzilla-daemon
2020-06-12 16:29 ` bugzilla-daemon
2020-06-12 17:26 ` bugzilla-daemon
2020-06-12 17:34 ` bugzilla-daemon
2020-06-12 17:44 ` bugzilla-daemon
2020-06-12 18:00 ` bugzilla-daemon
2020-06-12 18:01 ` bugzilla-daemon
2020-06-12 18:08 ` bugzilla-daemon
2020-06-12 18:13 ` bugzilla-daemon
2020-06-12 21:51 ` bugzilla-daemon
2020-06-12 21:52 ` bugzilla-daemon
2020-06-12 22:00 ` bugzilla-daemon
2020-06-12 22:05 ` bugzilla-daemon
2020-06-12 22:19 ` bugzilla-daemon
2020-06-12 22:32 ` bugzilla-daemon
2020-06-12 22:55 ` bugzilla-daemon
2020-06-12 23:02 ` bugzilla-daemon
2020-06-12 23:11 ` bugzilla-daemon
2020-06-12 23:14 ` bugzilla-daemon
2020-06-13 0:20 ` bugzilla-daemon
2020-06-14 5:06 ` [libre-riscv-dev] effects of powered-off chip sections on current leakage Jacob Lifshay
2020-06-14 11:30 ` Luke Kenneth Casson Leighton
2020-06-14 20:07 ` Jacob Lifshay
2020-06-14 22:08 ` Cesar Strauss
2020-06-13 3:37 ` bugzilla-daemon [this message]
2020-06-14 17:27 ` [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces bugzilla-daemon
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=bug-376-13-Wserrlqp5T@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--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