From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ffmpeg issue with MIPS
Date: Wed, 3 Jan 2018 23:05:07 +0100 [thread overview]
Message-ID: <20180103230507.11741c21@windsurf.lan> (raw)
In-Reply-To: <CAMbDF3+pfHWMz1iYOxY-rnBJkBRhxw534dGacPbKMLF_+OQTHg@mail.gmail.com>
Hello,
Please keep the Buildroot mailing list in Cc. Thanks!
On Wed, 3 Jan 2018 22:56:33 +0100, Johannes Schmitz wrote:
> > - What is your Buildroot configuration ?
> >
> > - What is the exact MIPS processor you're running this on ?
> >
> > - Does it work when --disable-mipsfpu is passed, or when
> > --enable-mipsfpu is passed ?
> >
>
> - glibc toolchain
I need the exact Buildroot .config file, to see which specific CPU you
have chosen, and other configuration knobs.
> - It does work when --disable-mipsfpu is forced
OK.
> - See hardware information here: https://elinux.org/CI20_Hardware
>
> - additional FPU related information we found during the discussion:
> https://dmz-portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking#10.5.2._Setting_the_FPU_mode
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-03 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 21:43 [Buildroot] ffmpeg issue with MIPS Johannes Schmitz
2018-01-03 21:50 ` Thomas Petazzoni
[not found] ` <CAMbDF3+pfHWMz1iYOxY-rnBJkBRhxw534dGacPbKMLF_+OQTHg@mail.gmail.com>
2018-01-03 22:05 ` Thomas Petazzoni [this message]
2018-01-03 22:13 ` Johannes Schmitz
2018-01-03 23:32 ` Johannes Schmitz
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=20180103230507.11741c21@windsurf.lan \
--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