[libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces

[bugzilla-daemon@libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=376

--- Comment #13 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #11)
> (In reply to Jacob Lifshay from comment #7)
> > (In reply to Luke Kenneth Casson Leighton from comment #3)
> > > i am inclined to seriously recommend at least two separate OMI interfaces
> > > (with the option to use them in parallel), one to be connected to a video
> > > DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
> > > with the option to say "i don't care about that, just use one or both for
> > > general shared memory"
> > 
> > I strongly disagree with the idea of partitioning memory interfaces between
> > GPU and CPU tasks,
> 
> ah that is a misunderstanding, to clarify:
> 
> > > arallel), one to be connected to a video
> > > DRAM chip,
> 
> this for the video framebuffer and the video framebuffer only.

That doesn't really work, since the GPU will need lots of memory bandwidth into
the framebuffer since that's where it will be rendering to, potentially drawing
over the same pixels several dozen times. To support that, the memory bandwidth
of both the framebuffer and everything else needs to be spread across all
available memory interfaces.

-- 
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