[libre-riscv-dev] [Bug 137] NLNet 2019 Video Acceleration Proposal

[bugzilla-daemon at libre-riscv.org]

http://bugs.libre-riscv.org/show_bug.cgi?id=137

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to cand from comment #4)
> Each codec is of different complexity. The audio codecs usually only have a
> single hotspot, while at the other end AV1 has several dozen.

thought so.

> I'll do a
> quick pass later, to get rough figures on those.

great.

> I thought the simulator would be part of the implementation loop?

hmmm yes, however think about it: several CODECs will share the same opcodes. 
you don't make a YUV2RGB opcode for VP9 and a different one for MPEG :)

so i was kinda leaning towards them being on their own (aggregated) iterative
cycle, if you know what i mean.

if we can get a rough idea in advance of the sorts of opcodes needed, bear in
mind that for the most part they need to be "scalar" in nature because the
Vector System adds that hardware-for-loop on top *of* scalar operations, it
would be very handy.

then those can also be analysed as to a simulation implementation timescale and
hw timescale and budget as well.

we are not going to be able to predict exactly everything here, that is what
the iterations are for.  we just need a start.

-- 
You are receiving this mail because:
You are on the CC list for the bug.