Posts by jernej

lucize I don't own any A20 board so I can't help you much with U-Boot issues. Maybe removing projects/Allwinner/patches/u-boot folder will help?

Even if you manage to build image, video playback won't work unless you disable HW acceleration. For HW acceleration you would need at least 5.1 kernel (RC version will be available in two weeks) and additional ffmpeg patches, which are currently in the work.

ruslakall Can you connect serial console to it? Serial output would be very useful in diagnosing the issue. What is your TV native resolution? Can you connect it to any other display? 1080p computer monitor would be best.

New update files are uploaded for A64 and H3, along with updated addon repository (needed due to Kodi bump).

What's new:

- Kodi 18.1

- Linux 5.0-rc8

- 4K H264 decoding supported

- fixed 4K downscaling (watching 4K videos on 1080p screen)

- minor decoding speed improvements

- H264 memory optimizations (*might* help for OPi Lite & One, but I'm not sure)

- HDMI CEC fix

Known issues:

- some H264 and HEVC videos are still not correctly decoded, investigation is ongoing.

- Kodi screen calibration is not stored (fix in Kodi 18.2)

Quote from riku

any eta when this will move from beta to kodi 18.1 ?

I can upload new updates today, but except Kodi update, 4K H264 decoding and maybe HDMI CEC fix, nothing else would be new. I'm still struggling with some problematic H264 and HEVC videos.

If you think that's ok, then I can do it.

Quote from Gumel

How to make an analog TV output on this assembly.

Analog TV out driver is not yet completed, although anyone with some Linux driver skills could use existing but old patches for that functionality.

Quote from majorkalina

I do not know if it's all and if it's enough.

You need whole series, not just that patch. Series is enough for kernel side, but ffmpeg side is still missing.

Quote from majorkalina

I applied patches from kernel/git/next/linux-next.git, but I am confused about support for DRM format modifiers. Please, can You suggest a path?

There are no ffmpeg patches for this yet. Maybe wait until they are ready? Or you want to be proactive and help us with programming?

tothb001

No, there is no any other image with kernel 3.4.113, only OE 7. It would be hard to make a newer one, since some packages rely on some kernel features which weren't present 7 years ago.

Regarding RPi with 512 MiB of RAM check this post #209

Quote from marcins

I know only probably this is problem with alsa / pulseaudio config.

Sadly, no. DW HDMI driver has to be improved, but yes, alsa config needs to be improved too.

andreabak It could be that some metadata are not set correctly. I haven't had time to look into that yet.

tothb001 I'll remove images for boards with 512 MiB of RAM soon. They won't be officially supported.

marcins 1024x768 resolution means that Linux failed to read EDID data from monitor. Because of that, it selected fallback resolution 1024x768. This issue is more common than I thought. For me, it usually helps to unplug HDMI cable on both sides and reconnect. Sometimes it also helps to unplug board completely (all cables) and left it for a few minutes. I really don't know what the issue is and it happens rarely for me, so I don't know how to test possible solutions.

psyapathy yes, it doesn't contain anything AW related. You would have to clone my repo and merge commits from that one. You have to learn a bit about git tool to do that.

lumpi latest update should fix crashing addons. It uses different repo which has addons specifically compiled for Allwinner boards.

orgonth There are probably a lot of drivers missing. The best way would be that you make a PR against allwinner branch which enables drivers you want. Please do that for both, 32 and 64 bit arm architectures at the same time.

BTW, streaming was not actually well tested. Just few seconds once. I guess error handling has to be improved, but that is known already.

psyapathy Sorry, no time to actually debug that. You can however try to build your own image and your own addon. Use following repository:

GitHub - jernejsk/LibreELEC.tv: Just enough OS for KODI

Command to build OrangePi Win image:

PROJECT=Allwinner ARCH=arm DEVICE=A64 UBOOT_SYSTEM=orangepi_win make image

Command to build addon:

PROJECT=Allwinner ARCH=arm DEVICE=A64 scripts/create_addon <addon name>

andreabak OpenELEC image used kernel which doesn't consider EDID at all. This was one of the pain points. You had to change fex file if your monitor didn't support 1080p. Besides, only 1080p, 720p and few other patched-in resolutions were supported. Here, on mainline kernel, a lot of stuff is based on EDID. Can you post output of following command?

edid-decode /sys/class/drm/card0-HDMI-A-1/edid

There are some other possible differences. AFAIK, mainline HDMI driver doesn't set correctly metadata like colorimetry, aspect ratio, etc. This might also be the problem.

andreabak Can you make some photo or video what it is and what it should be? I played video you referenced, but with that latest test update, it works same regardless DRM or GPU rendering (both HW decoded) or even completely SW decoded and GPU rendered. I can see flashing bars from 16 to 235. That's on PC monitor.

Quote from psyapathy

I install Gamestarer. I try to run it, it hangs on the splash screen and goes back to Kodi.

This is possible?

Did you updated to latest version which uses rebuilt addons so they shouldn't crash anymore? If yes then it might be an actual bug in addon. Note that I don't test addons nor fix bugs in them.

andreabak Please test this:

libreelec-h3.arm-9.1-devel-20190130174140-064c56c.tar

Full range is forced here and I think it should work well for monitors, but not TVs.

The issue here I think it's mix up between input range and output range. DRM property description doesn't explain it very well. If this works for you, I'll have a talk about it with other developers to find acceptable solution.

Quote from marcins

It is hard to test anything because system is write protected..

Depends what you want to do. Usually you have to update build system (mostly by adding patches), build update file and update board with it. It takes minute or few at most once you have good setup. That's the way I develop LE.

Quote from marcins

Any plans to run Passthrough?

Eventually, yes, but not by me since I don't have AVR.

andreabak It turns out that color range and color encoding are pretty easy to implement. Can you test following update:

libreelec-h3.arm-9.1-devel-20190129185238-064c56c.tar

You can see what encoding & range is used for video, if you run "modetest -M sun4i-drm" command during video playback via ssh. Both properties are set by Kodi to values based on video metadata and AFAIK you can't override them.

It seems that driver used BT601 full range transformation till now.

Quote from LubMich

Someone has already modified the dtb / dts file for the i2s sound on gpio?

I've already decompiled the file ... but this is a new file for me ... so I'm looking for an example ...

I don't have any experience with external I2S codecs, but I can give you few pointers. First you have to make sure that wanted I2S node is enabled. It should be already present in decompiled DT, you just have to change status from "disabled" to "okay" (with quotes). Secondly, you have to define I2S pins (ARM: dts: sun8i-h3: Add pin settings for I2S0. · codekipper/linux-sunxi@b397fd0 · GitHub) and assign pins to I2S node. Thirdly, you have to integrate codec into DT (for example, connect control interface to I2C and create simple soundcard node for audio interface).

Here you have example for uda1380 (driver needs one patch if you also have this codec): DEMO - i2s on H3 with uda1380 for OPi2 · codekipper/linux-sunxi@d1c85a6 · GitHub

marcins

Passthrough doesn't work yet, currently only linear PCM (LPCM) works. So if you can't get EDID to show more than 2 channels for LPCM, it won't work (EDID is source of information for driver to know what audio capabilities TV/AVR has).

andreabak

BT601/BT709 to full/limited range conversion is not implemented in display driver yet. I'm not sure which conversion is currently used. I took a look what needs to be done and it doesn't seem too complicated. Wait for it a bit.

marcins check your edid decode output. It has following data:

Audio data block
    Linear PCM, max channels 2

Which means only 2 channels are supported for linear PCM on your device. Do you use AVR? If yes, how it is connected? board <-> AVR <-> TV ? Using HDMI ARC may not work correctly.