narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
_whitelogger_ has joined #linux-amlogic
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
jacobk has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 272 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
jacobk has quit [Ping timeout: 255 seconds]
naoki has joined #linux-amlogic
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
camus has quit [Ping timeout: 258 seconds]
camus has joined #linux-amlogic
chewitt has joined #linux-amlogic
<chewitt> vkoskiv: the kernel patches are likely required to make the rpi-ffmpeg branch work
<chewitt> I wouldn't be surprised if there are sub-optimal things in the memcp paths
<chewitt> the code hasn't really been touched beyond basic "make it compile again" fixups since early 2020
<chewitt> the kernel has likely moved onwards in places causing a little code drift
<chewitt> conformance tests flag a few things
<chewitt> (hence it's all still in staging)
<chewitt> vp9 should work as long as it's 8-bit content
<chewitt> the challenges that I see are that lots of vp9 is 10-bit which results in board lock-up
<chewitt> or it's in 59.94 which results in "Fatal Error, invalid HDMI vclk freq 593406" and nothing plays
ungeskriptet has quit [Quit: The Lounge - https://thelounge.chat]
ungeskriptet has joined #linux-amlogic
ungeskriptet has quit [Client Quit]
ungeskriptet has joined #linux-amlogic
ungeskriptet has quit [Client Quit]
ungeskriptet has joined #linux-amlogic
naoki has quit [Quit: naoki]
chewitt has quit [Quit: Zzz..]
psydroid has joined #linux-amlogic
gabes2 has quit [Quit: The Lounge - https://thelounge.chat]
gabes2 has joined #linux-amlogic
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.
<f_> still reverse-engineering vdec?
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]