All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] ffmpeg: default to --cpu=generic for MIPS architecture
Date: Sat, 26 Mar 2016 21:57:41 +0100	[thread overview]
Message-ID: <5n9jscxh1d.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20160319143556.34d7b41a@free-electrons.com

Am Sat, 19 Mar 2016 14:35:56 +0100 schrieb Thomas Petazzoni:

> Dear Vicente Olivert Riera,
> 
> On Fri, 18 Mar 2016 14:06:06 +0000, Vicente Olivert Riera wrote:
>> Signed-off-by: Vicente Olivert Riera
>> <Vincent.Riera@imgtec.com>
>> ---
>>  package/ffmpeg/ffmpeg.mk | 5 +++++
>>  1 file changed, 5 insertions(+)
> 
> Why ? Your commit log only says what the patch is doing, but not why.

Hi Thomas,

this patch prevents this message from ffmpeg configure:

WARNING: unknown CPU. Disabling all MIPS optimizations.

I will add a description about this in my re-spin of Vicentes patch 
series. Please note that the ffmpeg 3.0 bump will not only need updates 
for Kodi but also libdcadec, mediastreamer, opencv, opencv3, squeezelite 
and freerdp; all of them are currently part of my WIP patch series.

Regards, Bernd

  reply	other threads:[~2016-03-26 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 14:06 [Buildroot] [PATCH 1/3] ffmpeg: bump to version 3.0 Vicente Olivert Riera
2016-03-18 14:06 ` [Buildroot] [PATCH 2/3] ffmpeg: cosmetic change. Puts mipsfpu conf opts in one line Vicente Olivert Riera
2016-03-19 13:35   ` Thomas Petazzoni
2016-03-18 14:06 ` [Buildroot] [PATCH 3/3] ffmpeg: default to --cpu=generic for MIPS architecture Vicente Olivert Riera
2016-03-19 13:35   ` Thomas Petazzoni
2016-03-26 20:57     ` Bernd Kuhls [this message]
2016-03-18 15:41 ` [Buildroot] [PATCH 1/3] ffmpeg: bump to version 3.0 Bernd Kuhls
2016-03-18 16:21   ` Vicente Olivert Riera
2016-03-18 17:00     ` Bernd Kuhls
2016-03-18 17:07       ` Vicente Olivert Riera
2016-03-18 19:04         ` Bernd Kuhls
2016-03-22 20:07           ` 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=5n9jscxh1d.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.