Posts by chewitt

Current situation is improved from 2019 when previous post was written, but still a long way from a solution and those commits don't directly help.

The demod chip is from Availink and we have now direct contact with them and they are (or were, no updates since the summer) working on a public release of their previously closed-source drivers and we/me persuaded them to publish under GPLv2 to things can eventually go upstream. They also have a pile of tuner drivers to work with their demod, although some of the drivers have dubiouos code provenance so might never be upstreamable too the kernel. The current missing pieces are: a) the large amount of work to deconstruct the Amlogic/Android style monolithic driver so that all the component driver bits are standalone/configurable via kernel defconfig (and thus correctly supporting upstream APIs), and b) somene needs to write a GBM/V4L2 compliant demux driver as the one from the Amlogic BSP is written around the BSP memory drivers, and c) someone will need to write a deinterlace IP driver, although that's easier and recent work on Allwinner to do similar provides some prior-art and clues on how to do it.

Using the WP1 as the headend is by far the best idea, as the above ^ isn't going to happen anytime soon.

On what device?

Nothing official and I appear to have deleted the local branch I did my initial experiments with. The upstream kernel repo is here: Branches · xdarklight/linux · GitHub but there are few device-tree files and converting ye olde 3.10 kernel ones is not the simple eyeball aand copy/paste job of newer hardware. There is also no mainline u-boot support for Meson8 so it's a little fiddly to come up with the changes to make the image. Progress is also rather slow and sporadic .. Martin has been rather busy with day-job work recently.

Quote from fat-tony

Ok, thanks. Will await driver development. (What's PT audio, though?).

Pass-Through (and anything else needing high bitrates)

Current PT audio support is a userspace hack and the audio drivers need to be extended with proper HBR support.

Nobody on staff has Jetson boards so it would need to be a community created effort.

Quote from adm

Any idea ? wrong dtb ?

From the level of useful info in your bug report, reading tea-leaves will be more pruductive at finding the problem (at least you get a cup of tea).

Quote from g7ruh

there are at least 2 users still out here . Keep up the hard work on Slice, please.

There are 79 of you in total (declining slowly with time). Currently there are no plans to release further Slice-specific images, e.g. LE10. I'm not entirely sure what the status of things is upstream and how realistic it is to configure Slice support using the RPi images. I think we hand everything back to the community to figure out.

LE 9.2.6 is/was a general release for all hardware inluding Slice boxes.

erbas thanks for confirming. The change CE made works but we create /storage/.cache/ssh via tmpfiles.d so IMHO the correct fix (which is in the image you tested) is simply adding a depedency on systemd-tmpfiles-setup.service (or perhaps network.target) to ensure it completes before the SSH daemon starts.

Perhaps install the "locale" add-on and change it to UTF8 or en_US (something other than POSIX)?

erbas I've never seen this problem in all my testing, but see if the images in Index of /testing/9.80/ change anything?

Quote from Wulfeken

I have no sound coming from my Pi to TV via HDMI... I have gone over the sound menu in detail.. made sure that pass through is checked... what am I missing, can someone please HELP???

HDMI is connected to the port nearest the power connector?

It looks like that logic has been ported to mainline u-boot: include/configs/mx6cuboxi.h · master · U-Boot / U-Boot · GitLab and there are similar configs for udoo and wandboard. It's not clear to me what changes might be needed for filenames and/or other files in the boot partition, I'm not sure extlinux is the best option here. Anyway.. it's late o'clock here so something to look into over the weekend.

HDR is not supported on RPi4 in any releases yet. Still being worked on. Still some way to go.

Ahh, indeed, that woud explain!

vpeter so I can see that the dual/quad versions all share the same u-boot defconfig, which supports the idea of consolidating images to three: cubox, udoo, wandboard. I can also see that wandboard has more dtb's than we currently create images for (revb1, revd1 were added upstream). It's simple to repackage and accomodate that, see Commits · chewitt/LibreELEC.tv · GitHub and I think the simplicity of image naming trumps adding more dedicated images (and I'm doing the same thing with Odroid N2/N2+ in the next Amlogic bump). I'm interested to know what happens when users with a quad board don't change the dtb name and boot using the dual dtb? (or should the defaults be switched to quad?). Also, looking at the device-tree files in the kernel, didn't we (you) also used to ship an image for the Hummingboard devices?

It might be missing the firmware, in which case you'll need to share "dmesg | paste" output so we can see the error message that tells us which file can't be found (so we can pick/add it).