still "Permission denied"
This could be the cause of the issue. Wait for chewitt .
still "Permission denied"
This could be the cause of the issue. Wait for chewitt .
I linked the LE wiki article with instructions for creating a custom keymap in post #192. LE does not run the Amlogic vendor kernel that CE/Odroid wikis are written for. If you continue to use the wrong instructions .. ![]()
And you cannot change permissions on /sys and /proc folders that are owned/managed by the kernel. That's basic Linux sysadmin knowledge. Again, whatever instructions you are following are not for the mainline kernel.
??
I have already created a custom keymap and my remote works fine (as long as the machine is running). The wiki article does not describe how to configure IR remote wakeup.
And you cannot change permissions on /sys and /proc folders that are owned/managed by the kernel. That's basic Linux sysadmin knowledge. Again, whatever instructions you are following are not for the mainline kernel.
OK, so why does that "wakeup" file exist, if at all?
The wiki article does not describe how to configure IR remote wakeup.
The IR wake code is hardcoded in the BL301 component of the boot firmware. ISTR that CE uses a custom version of BL301 source with some closed-source companion code to support external configuration. At some point I'll get around to investigating and then replicating something similar but a) done with open sources and mainline u-boot, b) upstreamed so everyone can benefit. I have a rather long to-do list at the moment though.
OK, so why does that "wakeup" file exist, if at all?
Because Google AI is crap and suggested modifying the device-tree to add wakeup-source; and thus the kernel now blindly exposes support for something that the hardware does not support being controlled from the kernel (it is hardcoded in BL301).
I pushed a set of updated Amlogic images to my test share. Notable changes are:
Once an LE13 beta ships I plan to revise current DVB support to use a new driver from rozpruwacz and start work on support for SC2 (S905X4) and T7 (A311D2) boards.
chewitt It's been quite a while (in the meantime I have been enjoying LE on RPi4 and working great), but this new amvdec is looking great for Amlogic boards. I tested it on the Vero 4K+ with the latest nightly. Only things I noticed were:
I didn't test audio pass-through, the TV is stereo.
CMA at 384MB hasn't been an issue for me in testing on a native 4K screen downscaling might require more. I'll make a note to have a look into that. MPEG1/MPEG4 is something that will be added once we've finished considering the UAPI required.
I'd like to improve deinterlacing on older GX boards but the vendor kernel handles the conversion to progressive post-decode in the DRM layer rather than pre-decode as we do with the ffmpeg filter approach used in newer boards (and Allwinner/Rockchip). The GX era IP looks tied to this mode of operation and Amlogic engineer for deinterlace things isn't forthcoming with answers to questions.
CMA at 384MB hasn't been an issue for me in testing on a native 4K screen downscaling might require more. I'll make a note to have a look into that. MPEG1/MPEG4 is something that will be added once we've finished considering the UAPI required.
I'd like to improve deinterlacing on older GX boards but the vendor kernel handles the conversion to progressive post-decode in the DRM layer rather than pre-decode as we do with the ffmpeg filter approach used in newer boards (and Allwinner/Rockchip). The GX era IP looks tied to this mode of operation and Amlogic engineer for deinterlace things isn't forthcoming with answers to questions.
Yeah that might be the case, both boards (S905D & S905Y2) needed 768MiB (it could live with 640MiB). It looks like there is a meson-di driver which supports the S905Y2, but most of my media is progressive except for the OTA captures from Live TV (which is 1080i or 720p).
On the S905Y2 board (Radxa Zero), I ran into some issues with aborted frames crashing Kodi, other than that the S905D & S905Y2 ran great. The way I ended up with aborted frames was running a 2160p60 H.264 video on the S905Y2, which only supports 2160p30 so it drops half the frames.
Here is a patch to apply to your armsoc-9.0.2 branch if you want it (it's just checking for pic->output is NULL, to avoid the null de-reference crash on the next line for aborted frames from amvdec):
diff --git a/libavcodec/v4l2_request.c b/libavcodec/v4l2_request.c
index 36eec85..c04bb1a 100644
--- a/libavcodec/v4l2_request.c
+++ b/libavcodec/v4l2_request.c
@@ -339,6 +339,10 @@ int ff_v4l2_request_append_output(AVCodecContext *avctx,
{
V4L2RequestContext *ctx = v4l2_request_context(avctx);
+ // start_frame() failed or was never called, there is no OUTPUT buffer
+ if (!pic->output)
+ return AVERROR(EINVAL);
+
// Append data to OUTPUT buffer and ensure there is enough space for padding
if (pic->output->bytesused + size + AV_INPUT_BUFFER_PADDING_SIZE <= pic->output->size) {
memcpy(pic->output->addr + pic->output->bytesused, data, size);
@@ -361,6 +365,10 @@ static int v4l2_request_queue_decode(AVCodecContext *avctx,
uint32_t flags;
int ret;
+ // start_frame() failed or was never called, there is no OUTPUT buffer
+ if (!pic->output)
+ return AVERROR(EINVAL);
+
if (first_slice) {
/*
* Wait on dequeue of the target CAPTURE buffer. Otherwise V4L2 decoder
--
2.53.0
Display More
S905Y2 uses the meson-di driver that I (claudius) wrote recently. This only works on G12A and up. There are hints for mem2mem operations in older SoC databooks, but as Amlogic never used/implented it that way there's no prior art in vendor kernels and the institutional knowledge of how to drive it that way isn't documented and now so long ago that the staff who did it (all in senior positions now) can't remember either. I might see what Fable can achieve by fuzzing the SoC directly, but that's going to burn a ton of tokens when I have other tasks that need them.
I'll have a look at the ffmpeg patch, thanks.
I might see what Fable can achieve by fuzzing the SoC directly, but that's going to burn a ton of tokens when I have other tasks that need them.
Yeah no worries, it's just MPEG2 1080i for me, there is enough CPU power to handle it.