From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7] add Phonon support to qtopia4
Date: Tue, 9 Dec 2008 11:45:01 +0100 [thread overview]
Message-ID: <20081209114501.247dc1dc@hcegtvedt> (raw)
In-Reply-To: <200812091135.00129.markus.heidelberg@web.de>
On Tue, 9 Dec 2008 11:34:59 +0100
Markus Heidelberg <markus.heidelberg@web.de> wrote:
> Hans-Christian Egtvedt, 09.12.2008:
> > On Mon, 8 Dec 2008 23:00:09 +0100
> > Markus Heidelberg <markus.heidelberg@web.de> wrote:
<snipp>
> > The reason playback is so slow is that you are probably not using
> > the pixel coprocessor (PICO) to do the work. That was why getting
> > gst-ffmpeg (libavcodec) with the AVR32 patches to work would be very
> > nice.
>
> This optimization with using the PICO should also be possible for Qt
> output, independent of video playback, shouldn't it?
>
No, you will have to write optimized assembly to take advantage of the
PICO. Qt does not use the PICO by default, not even DSP or SIMD
instructions.
> > > So currently I'm using mplayer -geometry
> > >
> >
> > And with the AVR32 patch, this is quite optimized and uses the PICO.
>
> Sounds comprehensible, I had not really thought about it.
> Are there plans or have there already been efforts to get the AVR32
> patch into mainline ffmpeg? The mplayer version rc1 in buildroot is
> quite old, OK rc2 is not very new, too. But it seems as if the big
> atmel patch is preventing from updating.
>
I am looking into porting the PICO stuff for ffmpeg to upstream ffmpeg,
and instead use that for mplayer. Then it should be easy to bump the
version to rc2 as well.
--
Best regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2008-12-09 10:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 1:44 [Buildroot] [PATCH 0/7] add Phonon support to qtopia4 Markus Heidelberg
2008-11-19 1:49 ` [Buildroot] [PATCH 1/7] package: add liboil package Markus Heidelberg
2008-11-25 7:27 ` [Buildroot] [PATCH 1/7 v2] " Markus Heidelberg
2008-12-02 22:51 ` Thomas Petazzoni
2008-12-03 6:15 ` Hans-Christian Egtvedt
2008-12-03 9:06 ` [Buildroot] [PATCH 1/7] " Thomas Petazzoni
2008-11-19 1:50 ` [Buildroot] [PATCH 2/7] package/multimedia: add libtheora package Markus Heidelberg
2008-11-19 1:50 ` [Buildroot] [PATCH 3/7] package/multimedia: add gstreamer package Markus Heidelberg
2008-11-19 1:51 ` [Buildroot] [PATCH 4/7] package/multimedia: add gst-plugins-base package Markus Heidelberg
2008-11-19 1:52 ` [Buildroot] [PATCH 5/7] package/multimedia: add gst-plugins-good package Markus Heidelberg
2008-11-19 1:52 ` [Buildroot] [PATCH 6/7] package/multimedia: add gst-plugins-ugly package Markus Heidelberg
2008-11-19 1:53 ` [Buildroot] [PATCH 7/7] qtopia4: add Phonon support Markus Heidelberg
2008-11-25 7:25 ` [Buildroot] [PATCH 0/7] add Phonon support to qtopia4 Markus Heidelberg
2008-11-25 7:27 ` Hans-Christian Egtvedt
2008-11-25 7:33 ` Markus Heidelberg
2008-12-08 18:03 ` Hans-Christian Egtvedt
2008-12-08 22:00 ` Markus Heidelberg
2008-12-09 6:02 ` Hans-Christian Egtvedt
2008-12-09 10:34 ` Markus Heidelberg
2008-12-09 10:45 ` Hans-Christian Egtvedt [this message]
2008-12-09 13:34 ` Thiago A. Corrêa
2008-12-09 13:58 ` Hans-Christian Egtvedt
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=20081209114501.247dc1dc@hcegtvedt \
--to=hans-christian.egtvedt@atmel.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