From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9021] Kodi - Broken: Illegal instruction (core dumped)
Date: Sun, 24 Jul 2016 21:18:23 +0000 [thread overview]
Message-ID: <bug-9021-163-MZhkfWGeYo@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9021-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9021
--- Comment #2 from Bernd Kuhls <bernd.kuhls@t-online.de> ---
Please provide more infos about the crash, as a hint for required logs read
http://kodi.wiki/view/HOW-TO:Submit_a_bug_report#Right.2C_so_what_information_do_you_guys_need.3F
Please also read
http://kodi.wiki/view/Raspberry_Pi_FAQ#Raspberry_Pi_known_issues
Buildroot contains some patches for Kodi 16.1 but there maybe more patches
needed
to support raspberry pi. Since I do not own such a box I can not test it
myself,
the machine where I run Kodi on has in Intel CPU, its GPU is used for hardware
decoding using vaapi.
To get a hint about what might be needed for the raspberry pi have a look at
http://forum.kodi.tv/showthread.php?tid=231092
or try my Kodi 17 branch: https://github.com/bkuhls/buildroot/tree/kodi17
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-07-24 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 16:54 [Buildroot] [Bug 9021] New: Kodi - Broken: Illegal instruction (core dumped) bugzilla at busybox.net
2016-07-24 20:46 ` [Buildroot] [Bug 9021] " bugzilla at busybox.net
2016-07-24 21:10 ` bugzilla at busybox.net
2016-07-24 21:18 ` bugzilla at busybox.net [this message]
2016-09-12 14:44 ` bugzilla at busybox.net
2016-09-16 6:32 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-9021-163-MZhkfWGeYo@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox