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] Fall 2022 Interfaces
Date: Fri, 12 Jun 2020 12:03:19 +0100
Message-ID: <CAPweEDxge6pt4yx18nHY0Y6-f3rDOAF_Dq70YzbCqg8ud_DQCQ@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD7fSit1+STs+WxMK4u2coY8GBnVgDw9mVjyq3VwUWdDDw@mail.gmail.com>
On Friday, June 12, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Thu, Jun 11, 2020, 19:59 Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > Was talking with Pine64 and Raptor about Fall2022 interfaces which I’m
> > trying to finalize.
> > We can do everything including HDMI, ethernet, DDR4(via OpenCAPI OMI),
> and
> > PCIE with SERDES lanes.
> >
>
> hdmi has issues with libre licensing and DRM content,
indeed. DVI however does not (and is pin compatible). HDMI is just a
protocol over DVI.
> if we're going that
> fast, we should just go with display port or similar, since it's an open
> standard, I think.
i added Richard Herveille's RGBTTL to the list. a TI TFP410a will convert
to at least 1600 x 1200 DVI no problem.
the TFP410a is a well known solution.
if we make it DDR RGBTTL then 1920x1080 is also no problem, via some
Chrontel ASICs.
>
>
> > We need 10rx and 14tx SERDES.
that is one hell of a lot.
> > 4rx and 4tx for the OMI will need to run at 25GHz for DDR4 over OMI.
that may not be enough to handle framebuffers as well as run an OS.
framebuffers are scarily demanding of memory bandwidth and they absolutely
MUST have total absolute top priority.
you cannot have a video scan line go blank. evverrr.
to give some idea: 1920 x 1080 is 2 million pixels. each pixel is 4
bytes. that is 64 million bytes per frame. 60 frames? that is 360
MEGABYTES per second.
DDR3 800 Mhz is only 6400 MB per second so we are looking at 20 percent of
memory bandwidth taken by feeding the framebuffer!!!!
if you want 4k that is now 1200 MEGABYTES per second just to feed the
frickin framebuffer!
doesn't even matter if it contains blank lines, that's 1.2 gigabytes per
second full of zeros!
> >
>
> 25GHz seems *really* fast, probably impractically so unless going to *lots*
> of effort, did you mean 2.5GHz?
no it really is 25GHz.
we will need Rudi from ASICS.ws for this. he can handle that kind of
work. when i went to visit him he was doing some SERDES PHY related work
at these speeds.
i do not know if 45nm can handle it, though.
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: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 2:59 Yehowshua
2020-06-12 3:00 ` Yehowshua
2020-06-12 4:01 ` Jacob Lifshay
2020-06-12 4:33 ` Cole Poirier
2020-06-12 5:46 ` Yehowshua
2020-06-12 7:07 ` Yehowshua
2020-06-12 11:03 ` Luke Kenneth Casson Leighton [this message]
2020-06-12 11:21 ` Luke Kenneth Casson Leighton
2020-06-12 12:38 ` Yehowshua
2020-06-12 13:30 ` Luke Kenneth Casson Leighton
2020-06-12 14:06 ` Hendrik Boom
2020-06-12 14:23 ` Cole Poirier
2020-06-12 19:34 ` Yehowshua
2020-06-12 19:43 ` Yehowshua
2020-06-12 21:42 ` Luke Kenneth Casson Leighton
2020-06-12 23:17 ` Jacob Lifshay
2020-06-13 0:10 ` 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=CAPweEDxge6pt4yx18nHY0Y6-f3rDOAF_Dq70YzbCqg8ud_DQCQ@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