[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 #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(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.

> > DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,

this for the OS which in our case because it is a hybrid CPUVPUGPU
automatically and inherently includes CPU tasks, GPU tasks and VPU tasks.

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