From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] kodi: Enable raspberry-pi2 build support
Date: Sat, 7 May 2016 22:50:43 +0200 [thread overview]
Message-ID: <20160507225043.56bdc54f@free-electrons.com> (raw)
In-Reply-To: <1461702074-14376-1-git-send-email-bmauduit@beneth.fr>
Hello,
On Tue, 26 Apr 2016 22:21:14 +0200, Beno?t Mauduit wrote:
> +Original commit from "popcornmix" [0], and fixed by "wsnipex" [1] on Kodi branch master.
> +Commit-id in xbmc/kodi upstream git :
> +[0] Commit-id : 253ec417519afe9415612add80ff5a1753208b75
> +[1] Commit-id : 1da2f07be715865bf7cf9731d7147dc4f43459be
In these are two patches upstream, then it should be two patches in
Buildroot as well.
> +
> +Addition to original patches :
> + * Add optimization flag for rpi2 in main xbmc build
> + * Add -mtune & -mvectorize-with-neon-quad flag in "tools/depends" build
Why are you doing those additional changes compared to upstream?
Like Yann said, we prefer to not backport too much stuff, except when
it's actually fixing a problem (which is not the case here).
Yann, will you send a patch that reverts your commit adding explicit RPi
2 support in the Kodi package ? This way we can have this for 2016.05,
and when a new Kodi release is done with built-in support for RPi2, we
can revisit this.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-07 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 20:21 [Buildroot] [PATCH 1/1] kodi: Enable raspberry-pi2 build support Benoît Mauduit
2016-04-26 20:32 ` Thomas Petazzoni
2016-04-26 20:54 ` Bernd Kuhls
2016-04-27 9:08 ` Benoît Mauduit
2016-05-08 7:38 ` Yann E. MORIN
2016-04-26 21:00 ` Yann E. MORIN
2016-05-07 20:50 ` Thomas Petazzoni [this message]
2016-05-08 7:38 ` Yann E. MORIN
2016-05-12 13:06 ` Benoît Mauduit
2016-05-12 17:26 ` Bernd Kuhls
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=20160507225043.56bdc54f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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