Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

2017-10-27 Thread Rainer Dorsch
Package: ffmpeg
Version: 7:3.4-1
Followup-For: Bug #879800

Dear Maintainer,

I just wanted to confirm that applying the patch you proposed fixes the problem 
for me.

Also I enabled v4l2, since the ffmpeg/kodi is making use of v4l2 to decode 
video streams. I have not tested the LD_PRELOAD option you mentined in the 
rules file (I did not understand how that would work exactly).

Many thanks for the support.

Rainer


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.13.0-1-armmp (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ffmpeg depends on:
ii  libavcodec577:3.4-1
ii  libavdevice57   7:3.4-1
ii  libavfilter67:3.4-1
ii  libavformat57   7:3.4-1
ii  libavresample3  7:3.4-1
ii  libavutil55 7:3.4-1
ii  libc6   2.24-17
ii  libpostproc54   7:3.4-1
ii  libsdl2-2.0-0   2.0.6+dfsg1-4
ii  libswresample2  7:3.4-1
ii  libswscale4 7:3.4-1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
ii  ffmpeg-doc  7:3.4-1

-- no debconf information

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-03 Thread Rainer Dorsch
Hi Paul,

many thanks for your response.

On Mittwoch, 4. Oktober 2017 11:33:25 CEST Paul Wise wrote:
> On Wed, Oct 4, 2017 at 1:33 AM, Rainer Dorsch wrote:
> > I experimented with kodi on the cubox-i without proprietary extensions.
> 
> Since the CuBox i* series of devices use Vivante GPUs and there are
> reverse engineered libre drivers called etnaviv for these GPUs, you
> should be able to get graphics using solely Debian main and no
> proprietary extensions. I note the etnaviv support for libdrm is in
> Debian buster and later and the etnaviv support for mesa is in Debian
> sid and later. If you would like this on Debian stretch or earlier you
> would have to backport Linux, mesa, libdrm and possibly some other
> things.
> 
> https://www.solid-run.com/freescale-imx6-family/cubox-i/cubox-i-specificatio
> ns/ https://github.com/etnaviv
> https://packages.debian.org/search?keywords=etnaviv
> https://packages.debian.org/search?suite=sid=filename=contents
> =etnaviv

I forgot to mention that I am running buster, I have not noticed that I need 
mesa from sid though. Will try that later.

It seems for kodi also a recent ffmpeg is needed, commit from 10 days ago:

http://forum.solid-run.com/viewtopic.php?t=363=22466#p22466

Since ffmpeg 3.3.4 in sid and buster, we need to wait for a new release here 
as well.

But getting X up and running would be a worthwhile intermediate goal :-)

Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


kodi with framebuffer on cubox-i

2017-10-03 Thread Rainer Dorsch
Hello,

I experimented with kodi on the cubox-i without proprietary extensions. So far 
no luck yet, but I think I have not yet hit the hard roadblocks...

First I tried without an X-server directly on framebuffer. How would I tell 
kodi not to search for an X11 display?

I get in the kodi crashlog:

18:07:24.378 T:2932268592   ERROR: X11 Error: No Display found

As far as I understand is xbian running kodi without X11, but they use a lot 
of proprietary extension on their image for the cubox-i. If nobody else has an 
idea, I could start looking at xbian how they start kodi...

Here is the full kodi crashlog:

rd@xbian:~$ cat kodi_crashlog-20171003_180724.log 
## Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Tue Oct  3 18:07:24 CEST 2017
 Kodi Options: 
 Arch: armv7l
 Kernel: Linux 4.12.0-2-armmp #1 SMP Debian 4.12.13-1 (2017-09-19)
 Release: Debian GNU/Linux
## END SYSTEM INFO ##

### STACK TRACE #
gdb not installed, can't get stack trace.
# END STACK TRACE ###

# LOG FILE ##

18:07:14.152 T:2932268592  NOTICE: special://profile/ is mapped to: 
special://masterprofile/
18:07:14.152 T:2932268592  NOTICE: 
---
18:07:14.152 T:2932268592  NOTICE: Starting Kodi from Debian (17.3 Debian 
package version: 2:17.3+dfsg1-2). Platform: Linux ARM (Thumb) 32-bit
18:07:14.152 T:2932268592  NOTICE: Using Release Kodi from Debian x32 build
18:07:14.152 T:2932268592  NOTICE: Kodi from Debian compiled from 
2:17.3+dfsg1-2 by GCC 6.3.0 for Linux ARM (Thumb) 32-bit version 4.9.30 
(264478)
18:07:14.152 T:2932268592  NOTICE: Running on Debian GNU/Linux buster/sid 
unstable, kernel: Linux ARM 32-bit version 4.12.0-2-armmp
18:07:14.152 T:2932268592  NOTICE: FFmpeg version/source: 3.3.4-2
18:07:14.153 T:2932268592  NOTICE: Host CPU: ARMv7 Processor rev 10 (v7l), 2 
cores available
18:07:14.153 T:2932268592  NOTICE: ARM Features: Neon disabled
18:07:14.154 T:2932268592  NOTICE: special://xbmc/ is mapped to: 
/usr/share/kodi
18:07:14.154 T:2932268592  NOTICE: special://xbmcbin/ is mapped to: 
/usr/lib/arm-linux-gnueabihf/kodi
18:07:14.154 T:2932268592  NOTICE: special://xbmcbinaddons/ is mapped to: 
/usr/lib/arm-linux-gnueabihf/kodi/addons
18:07:14.154 T:2932268592  NOTICE: special://masterprofile/ is mapped to: 
/home/rd/.kodi/userdata
18:07:14.154 T:2932268592  NOTICE: special://envhome/ is mapped to: /home/rd
18:07:14.154 T:2932268592  NOTICE: special://home/ is mapped to: 
/home/rd/.kodi
18:07:14.154 T:2932268592  NOTICE: special://temp/ is mapped to: 
/home/rd/.kodi/temp
18:07:14.154 T:2932268592  NOTICE: special://logpath/ is mapped to: 
/home/rd/.kodi/temp
18:07:14.155 T:2932268592  NOTICE: The executable running is: /usr/lib/arm-
linux-gnueabihf/kodi/kodi.bin
18:07:14.155 T:2932268592  NOTICE: Local hostname: xbian
18:07:14.155 T:2932268592  NOTICE: Log File is located: 
/home/rd/.kodi/temp//kodi.log
18:07:14.155 T:2932268592  NOTICE: 
---
18:07:14.196 T:2932268592   ERROR: DBus: Error 
org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower 
was not provided by any .service files
18:07:16.958 T:2932268592  NOTICE: load settings...
18:07:17.022 T:2932268592  NOTICE: Found 1 Lists of Devices
18:07:17.022 T:2932268592  NOTICE: Enumerated PULSE devices:
18:07:17.022 T:2932268592  NOTICE: Device 1
18:07:17.022 T:2932268592  NOTICE: m_deviceName  : Default
18:07:17.022 T:2932268592  NOTICE: m_displayName : Default
18:07:17.023 T:2932268592  NOTICE: m_displayNameExtra: Default Output 
Device (PULSEAUDIO)
18:07:17.023 T:2932268592  NOTICE: m_deviceType  : AE_DEVTYPE_PCM
18:07:17.023 T:2932268592  NOTICE: m_channels: FL,FR
18:07:17.023 T:2932268592  NOTICE: m_sampleRates : 
5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
18:07:17.023 T:2932268592  NOTICE: m_dataFormats : 
AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT
18:07:17.023 T:2932268592  NOTICE: m_streamTypes : No passthrough 
capabilities
18:07:17.023 T:2932268592  NOTICE: Device 2
18:07:17.023 T:2932268592  NOTICE: m_deviceName  : 
alsa_output.platform-sound-spdif.stereo-fallback
18:07:17.023 T:2932268592  NOTICE: m_displayName : Built-in Audio 
Stereo
18:07:17.023 T:2932268592  NOTICE: m_displayNameExtra: Analog Output 
(PULSEAUDIO)
18:07:17.023 T:2932268592  NOTICE: m_deviceType  : AE_DEVTYPE_PCM
18:07:17.023 T:2932268592  NOTICE: m_channels: FL,FR
18:07:17.023 T:2932268592  NOTICE: m_sampleRates : 
5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
18:07:17.023 T:2932268592  NOTICE:  

Re: kodi with framebuffer on cubox-i

2017-10-05 Thread Rainer Dorsch
On Donnerstag, 5. Oktober 2017 12:32:21 CEST Paul Wise wrote:
> On Thu, Oct 5, 2017 at 4:37 AM, Rainer Dorsch wrote:
> > I checked versions now, I should be good, but the xserver still does not
> > start (started with the Xserver now and look to kodi as a second step).
> 
> Please put the full Xorg log on paste.debian.net.

http://paste.debian.net/989216/

> > rd@xbian:~$ apt-cache policy mesa-va-drivers
> 
> The GPU package is libgl1-mesa-dri, video decoding is a completely
> separate matter, no idea about that but I guess the ffmpeg commit you
> mentioned would have to reach Debian for that.

That is also uptodate:

*rd@xbian*:*~*$ apt-cache policy libgl1-mesa-dri 
*rd@xbian*:*~*$ 

Rainer


-- 
Rainer Dorsch
http://bokomoko.de/
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Rainer Dorsch
Hi Jonas,

thanks for your response.

On Mittwoch, 4. Oktober 2017 10:34:00 CEST Jonas Smedegaard wrote:
[...]
> Correction: Debian Kodi is built with --enable-gles on
> armel/armhf/arm64.

Good news :-)

> I have no experience (yet) running Kodi on arm (be it framebuffer or
> X11), but am quite interested in our official package best possible
> covering the needs of our users: In case you (or others following along
> here) figure out some build configuration tuing needed then please do
> not hesitate to file wishlist bugreports :-)

I am not yet there...

> Heck, even if you have only vague dreams like "awww, please get Kodi to
> work from framebuffer on Vivante-based armhf devices" you might also
> file a (wishlist!) bugreport about that, to have a well-defined place to
> collect the details until substantial enough act on it.

Is there any information which is useful for you which should be appended to 
the bugreport?

Thanks
Rainer



-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Rainer Dorsch
Hi Paul,

I checked versions now, I should be good, but the xserver still does not start 
(started with 
the Xserver now and look to kodi as a second step).

On Mittwoch, 4. Oktober 2017 11:33:25 CEST Paul Wise wrote:
> On Wed, Oct 4, 2017 at 1:33 AM, Rainer Dorsch wrote:
> > I experimented with kodi on the cubox-i without proprietary extensions.
> 
> Since the CuBox i* series of devices use Vivante GPUs and there are
> reverse engineered libre drivers called etnaviv for these GPUs, you
> should be able to get graphics using solely Debian main and no
> proprietary extensions. 

*rd@xbian*:*~*$ uname -a 
*rd@xbian*:*~*$ 

> I note the etnaviv support for libdrm is in
> Debian buster and later 

*rd@xbian*:*~*$ apt-cache policy libdrm-etnaviv1  
*rd@xbian*:*~*$ 


> and the etnaviv support for mesa is in Debian
> sid and later. 

*rd@xbian*:*~*$ apt-cache policy mesa-va-drivers  
*rd@xbian*:*~*$ apt-cache policy mesa-vdpau-drivers  
*rd@xbian*:*~*$ 


> If you would like this on Debian stretch or earlier you
> would have to backport Linux, mesa, libdrm and possibly some other
> things.
> 
> https://www.solid-run.com/freescale-imx6-family/cubox-i/cubox-i-specificatio
> ns/ https://github.com/etnaviv
> https://packages.debian.org/search?keywords=etnaviv
> https://packages.debian.org/search?suite=sid=filename=contents
> =etnaviv

But Xorg still rejects to start:

[31.067] (EE)  


Any ideas and hints are welcome

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/
[30.239] 
X.Org X Server 1.19.3
Release Date: 2017-03-15
[30.239] X Protocol Version 11, Revision 0
[30.240] Build Operating System: Linux 3.16.0-4-armmp-lpae armv7l Debian
[30.240] Current Operating System: Linux xbian 4.13.0-1-armmp #1 SMP Debian 4.13.4-1 (2017-10-01) armv7l
[30.240] Kernel command line: console=ttymxc0,115200 quiet
[30.240] Build Date: 07 July 2017  08:55:08AM
[30.240] xorg-server 2:1.19.3-2 (https://www.debian.org/support) 
[30.240] Current version of pixman: 0.34.0
[30.240] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[30.240] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[30.241] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct  4 22:28:37 2017
[30.242] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[30.243] (==) No Layout section.  Using the first Screen section.
[30.243] (==) No screen section available. Using defaults.
[30.244] (**) |-->Screen "Default Screen Section" (0)
[30.244] (**) |   |-->Monitor ""
[30.244] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[30.245] (==) Automatically adding devices
[30.245] (==) Automatically enabling devices
[30.245] (==) Automatically adding GPU devices
[30.245] (==) Max clients allowed: 256, resource mask: 0x1f
[30.245] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[30.245] 	Entry deleted from font path.
[30.246] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[30.246] 	Entry deleted from font path.
[30.246] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	built-ins
[30.246] (==) ModulePath set to "/usr/lib/xorg/modules"
[30.246] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[30.246] (II) Loader magic: 0x581f60
[30.246] (II) Module ABI versions:
[30.246] 	X.Org ANSI C Emulation: 0.4
[30.246] 	X.Org Video Driver: 23.0
[30.246] 	X.Org XInput driver : 24.1
[30.246] 	X.Org Server Extension : 10.0
[30.249] (++) using VT number 7

[30.249] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[30.252] (II) xfree86: Adding drm device (/dev/dri/card1)
[30.264] (II) xfree86: Adding drm device (/dev/dri/card0)
[30.264] (II) no primary bus or device found
[30.264] 	falling back to /sys/devices/soc0/display-subsystem/drm/card1
[30.264] (II) LoadModule: "glx"
[30.265] (II) Loa

Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

2017-10-26 Thread Rainer Dorsch
Package: ffmpeg
Version: 7:3.3.4-2+b1
Severity: normal

Dear Maintainer,

I tried to build ffmpeg 3.4 from source using

dpkg-buildpackage -us -uc

but a test failed in the build process

TESTseek-lavf-flv_fmt
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh fate-seek-lavf-flv_fmt 
"" "" "/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard" 'run 
libavformat/tests/seek 
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv' 
'' '/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/ref/seek/lavf-flv_fmt' '' '1' '' 
'' '' '' '' '' '' '' ''
 /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/libavformat/tests/seek 
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv
 TESTapi-seek
 /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh fate-api-seek "" "" 
"/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard" 'run 
tests/api/api-seek-test 
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv 0 
720' 'null' '' '' '1' '' '' '' '' '' '' '' '' ''
  /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/api/api-seek-test 
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv 0 
720
   /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/ffmpeg -nostdin 
-nostats -cpuflags all -threads 1 -idct simple -flags +bitexact -sws_flags 
+accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1 -thread_type 
frame+slice -i 
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/fate/vsynth2-zlib.avi
 -threads 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 
-flags +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f 
rawvideo -y 
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
   make[2]: Target 'check' not remade because of errors.
   make[2]: Leaving directory 
'/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard'
   dh_auto_test: cd debian/standard && make -j2 check -k returned exit code 2


If there are more outputs I can provide, please let me know.

thanks
Rainer

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.13.0-1-armmp (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ffmpeg depends on:
ii  libavcodec577:3.3.4-2+b1
ii  libavdevice57   7:3.3.4-2+b1
ii  libavfilter67:3.3.4-2+b1
ii  libavformat57   7:3.3.4-2+b1
ii  libavresample3  7:3.3.4-2+b1
ii  libavutil55 7:3.3.4-2+b1
ii  libc6   2.24-17
ii  libpostproc54   7:3.3.4-2+b1
ii  libsdl2-2.0-0   2.0.6+dfsg1-4
ii  libswresample2  7:3.3.4-2+b1
ii  libswscale4 7:3.3.4-2+b1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  

-- no debconf information

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

2017-10-26 Thread Rainer Dorsch
Hi James,

thanks for your immediate reply.

On Donnerstag, 26. Oktober 2017 09:47:30 CEST James Cowgill wrote:
[...]
> On 26/10/17 07:37, Rainer Dorsch wrote:
> > Package: ffmpeg
> > Version: 7:3.3.4-2+b1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I tried to build ffmpeg 3.4 from source using
> 
> Just to clarify. You are building *3.4* here right? I ask because you
> have given two different versions above.
> 

yes, I am building for *3.4*. Since 7:3.3.4-2+b1 is installed, that was 
automatically scanned by reportbug and inserted in the report, I could have 
changed that manually, I think.

> [...]
> 
> > -- System Information:
> > Debian Release: buster/sid
> > 
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
> > 
> > Architecture: armhf (armv7l)
> 
> There is a known build issue with ffmpeg 3.4 on armhf at the moment
> which I have asked upstream about. They have applied the following
> commit which tries to fix it. Could you try applying this patch to see
> if it helps?
> 
> https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/587fadaef1e8163b3e56043e
> 500a3724e7fc5379

Thanks, I will give it a try.
> If that doesn't help, can you provide: the contents of /proc/cpuinfo,

rd@xbian:~$ cat /proc/cpuinfo 
processor   : 0
model name  : ARMv7 Processor rev 10 (v7l)
BogoMIPS: 6.00
Features: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part: 0xc09
CPU revision: 10

processor   : 1
model name  : ARMv7 Processor rev 10 (v7l)
BogoMIPS: 6.00
Features: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part: 0xc09
CPU revision: 10

Hardware: Freescale i.MX6 Quad/DualLite (Device Tree)
Revision: 
Serial  : 
rd@xbian:~$ 

> the full build log

do I get that with 

dpkg-buildpackage -us -uc 2>&1 >build.log

or is that created automatically? If yes, what is the filename?

> , and the contents of the .err file of the failing
> test. 
rd@xbian:/mnt/tmp/rd/debian/ffmpeg$ find -name *.err
./ffmpeg-3.4/debian/standard/tests/data/fate/checkasm-float_dsp.err
rd@xbian:/mnt/tmp/rd/debian/ffmpeg$

Thanks
Rainer

> The test log should tell you what err file you need to look at.
> 
> Thanks,
> James


-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-25 Thread Rainer Dorsch
Hi Jonas,

as you suggested, I created

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879735

for everything which affects kodi on the cubox-i. I summarized the knowledge I 
gained so far, there.

Please follow-up to 879...@bugs.debian.org and  subscribe to it 879735-
subscr...@bugs.debian.org , if you are interested in the discussion.

Thanks
Rainer

On Donnerstag, 5. Oktober 2017 08:09:44 CEST Jonas Smedegaard wrote:
> Quoting Rainer Dorsch (2017-10-04 22:38:58)
> 
> > On Mittwoch, 4. Oktober 2017 10:34:00 CEST Jonas Smedegaard wrote:
> > [...]
> > 
> > > Correction: Debian Kodi is built with --enable-gles on
> > > armel/armhf/arm64.
> > 
> > Good news :-)
> > 
> >> I have no experience (yet) running Kodi on arm (be it framebuffer or
> >> X11), but am quite interested in our official package best possible
> >> covering the needs of our users: In case you (or others following
> >> along here) figure out some build configuration tuing needed then
> >> please do not hesitate to file wishlist bugreports :-)
> > 
> > I am not yet there...
> > 
> >> Heck, even if you have only vague dreams like "awww, please get Kodi
> >> to work from framebuffer on Vivante-based armhf devices" you might
> >> also file a (wishlist!) bugreport about that, to have a well-defined
> >> place to collect the details until substantial enough act on it.
> > 
> > Is there any information which is useful for you which should be
> > appended to the bugreport?
> 
> Don't think of me as the recipient: Think of it as a way to create an
> interest group around a narrow, actionable topic.
> 
> You raised this as a cross-post on two mailinglists somewhat related to
> your topic.  Those are good places to seek help, I just imagine it might
> be even better if then the detailed discussion happening elsewhere only
> among those really interested in that detailed topic (myself included) -
> and I offer a way to do that by use of a wishlist bugreport with the
> kodi package.
> 
> What I imagine is useful is your clues for the puzzle.  And a link to
> the wiki page you might have created for tracking facts about the
> puzzle.
> 
> Ideally, cross-posts to multiple lists come with an explicit invitation
> to which *single* place to follow up.
> 
> 
>  - Jonas


-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Bug#879735: kodi support on cubox-i (i.mx6)

2017-10-25 Thread Rainer Dorsch
Package: kodi
Version: 2:17.3+dfsg1-5
Severity: wishlist

Dear Maintainer,

as you suggested in

https://lists.debian.org/debian-arm/2017/10/msg00014.html

I open a wishlist bug to get kodi on imx6 devices working using the free 
etnaviv driver and mesa support.

Here is some information I collected:

I started to use the configure switches which xbian uses on the cubox-i for 
building kodi:

--with-ffmpeg --enable-optical-drive --enable-dvdcss --enable-gles 
--enable-codec=imxvpu --disable-debug --enable-libbluray --enable-libcec 
--enable-airtunes --enable-airplay --enable-rtmp --enable-pulse  
--disable-joystick --disable-sdl --disable-x11 --disable-wayland 
--disable-vaapi --disable-vdpau --disable-vtbdecoder --disable-openmax 
--enable-rtmp --with-platform=cubox-i

https://github.com/xbianonpi/xbian-package-xbmc/blob/master/build/imx6/config

Since xbian uses a kernel with (non-mainline) vivante drivers instead of (free 
and mainline) etnaviv drivers, they might not work exactly as specified.

I had to remove --enable-codec=imxvpu since Debian does not include

/usr/include/imx-mm/vpu/vpu_wrapper.h

which is in the xbian provided package libfslvpuwrap.

In order to be able to run decode video streams efficiently, it might be 
necessary to add the imxvpuapi later to Debian:

https://github.com/Freescale/libimxvpuapi

Also what I have seen is that debin/kodi-bin.install contains

usr/lib/*/kodi/kodi-xrandr

which I think is not built, when building using --disable-x11

My latest build uses

GL_CONFIG_OPTIONS = --enable-dvdcss --enable-gles --disable-joystick 
--disable-sdl --disable-x11 --disable-wayland --disable-vaapi --disable-vdpau 
--disable-vtbdecoder --enable-rtmp --with-platform=cubox-i

Any insight and hints are welcome.

Thanks
Rainer



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.13.0-1-armmp (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kodi depends on:
ii  kodi-bin   2:17.3+dfsg1-5
ii  kodi-data  2:17.3+dfsg1-5

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:17.3+dfsg1-5
ii  kodi-visualization-spectrum 1.1.1-1

kodi suggests no packages.

-- no debconf information

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers