GNUtoo has quit [Remote host closed the connection]
f_[xmpp] has joined #linux-amlogic
luka177 has quit [Ping timeout: 240 seconds]
luka177 has joined #linux-amlogic
jacobk has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
luka177 has joined #linux-amlogic
Danct12 has left #linux-amlogic [A-lined: This user has been AViVA-lined!]
Danct12 has joined #linux-amlogic
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
ldevulder has quit [Quit: Leaving]
jacobk has joined #linux-amlogic
vagrantc has joined #linux-amlogic
kenny has quit [Ping timeout: 260 seconds]
kenny has joined #linux-amlogic
<lvrp16>
f_: both the codec hw ip is completely proprietary to Amlogic.
<lvrp16>
that might make it pretty difficult to RE.
<f_>
too bad..but I wasn't going to reverse-engineer vdec
<f_>
That might make it difficult to RE though, indeed
JohnnyonFlame has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
<cyrozap>
IIRC the AMRISC registers and memory are visible to the host, so reverse engineering the ISA should be fairly straightforward. Even with purely static analysis of the firmware binaries I was able to identify possible jump instructions. So, really it's just a matter of time and energy that needs to be spent to RE that ISA--it didn't look like anything really exotic, and a 5- or 6-bit opcode space in
<cyrozap>
28-bit instruction words means there aren't too many instructions to RE in the first place.
jacobk has quit [Ping timeout: 255 seconds]
<cyrozap>
My guess is that AMRISC is just your basic textbook MIPS-like 32-bit RISC CPU, and once the ISA is RE'd it should be straightforward to RE the video decoder hardware.