From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC 0/6] Freescale i.MX multimedia libraries
Date: Thu, 20 Dec 2012 00:37:30 +0100 [thread overview]
Message-ID: <1355960256-10786-1-git-send-email-arnout@mind.be> (raw)
This patch series adds Freescale's proprietary multimedia libraries for
the i.MX platform.
I only tested it on mx6q (SabreLite). I'm sending it now even though there
are still a few major shortcomings, so Peter (and others) have the chance
to test it on different platforms while I'm on vacation.
These are the things I'd like to see improved - feedback is very welcome!
* The platform stuff. A separate choice in imx-lib and gst-fsl-plugins
really doesn't work, because they are not kept consistent (the 'select'
doesn't always work).
* The binary libraries are linked against glibc, so there probably
should be a dependency on glibc/eglibc as well. However, for
gst-fsl-plugins, not everything depends on the binary libraries.
For instance, the VPU encoder/decoder only requires a firmware blob.
Unfortunately, it still didn't work with uClibc (didn't spend much time
on it though).
* All the binary libraries are installed, even though they are for
other platforms. The whole thing is about 10MB.
* I couldn't find an official upstream download site, so I used a mirror,
but it risks disappearing unexpectedly.
* More stuff should be selectable (e.g. which gst plugins to build).
The extraction of the .bin self-extractors if fortunately just slightly
messy :-) The legal-info on the other hand is horrible - as usual,
the proprietary projects are much less conscientious about legal stuff
and the typical open source project...
For the platform stuff, one idea I had was to create a new menu for
platform-specific packages. In that menu, you'd have a menuconfig per
platform, and this menu could give a SoC choice. The platform-specific
menus can collect all the platform-specific packages which are now
"polluting" the rest of the menus. For example:
menu "Platform-specific packages"
menuconfig "Freescale i.MX"
choice "i.MX SoC"
config "i.MX 51"
config "i.MX 6"
endchoice
menuconfig "Freescale QorIQ"
menuconfig "Raspberry Pi"
menuconfig "Snowball"
source "package/snowball-hdmiservice"
source "package/snowball-init"
menuconfig "TI Davinci"
How does this sound?
Regards,
Arnout
next reply other threads:[~2012-12-19 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 23:37 Arnout Vandecappelle [this message]
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 1/6] imx-lib: new package Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 2/6] libfslvpuwrap: " Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 3/6] firmware-imx: " Arnout Vandecappelle
2013-01-14 15:24 ` Peter Korsgaard
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 4/6] libfslparser: " Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 5/6] libfslcodec: " Arnout Vandecappelle
2012-12-20 1:06 ` Benoît Thébaudeau
2012-12-20 8:19 ` Arnout Vandecappelle
2012-12-20 9:08 ` Peter Korsgaard
2012-12-20 10:34 ` Arnout Vandecappelle
2012-12-20 10:50 ` Peter Korsgaard
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 6/6] gst-fsl-plugins: " Arnout Vandecappelle
2013-01-14 15:22 ` [Buildroot] [PATCH RFC 0/6] Freescale i.MX multimedia libraries Peter Korsgaard
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=1355960256-10786-1-git-send-email-arnout@mind.be \
--to=arnout@mind.be \
--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