From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] jpeg-turbo: new package
Date: Mon, 04 Jun 2012 09:51:02 +0200 [thread overview]
Message-ID: <87aa0jseft.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CA+pfegFoEQB_=byD-fyvZt_0SJYy5Dtu5dhATDh29ay66Fk6tg@mail.gmail.com> (Murat Demirten's message of "Sun, 3 Jun 2012 14:17:25 +0300")
>>>>> "Murat" == Murat Demirten <mdemirten@yh.com.tr> writes:
Murat> Hi,
Murat> Your solution will work. Adding a PROVIDES mechanism need more
Murat> work (like the what is provides-default of jpeg?). I'm not
Murat> changing anything in patch now. I'm not sure about that to add a
Murat> generic PROVIDES mechanism because it will increase the
Murat> buildroot complexity if only used by jpeg-turbo. When we see
Murat> that there are more packages like this, we have to add generic
Murat> PROVIDES mechanism.
Murat> jpeg-turbo's performance gain depends to type of images you're
Murat> working on too. We tested it on mips and arm platform (yes, it
Murat> make difference on mips too) and it is %30-%50 times faster than
Murat> libjpeg (I don't have the exact results now). It is a big
Murat> difference when you have to make lots of jpeg decompression in
Murat> your program.
Is there any reason to NOT use jpeg-turbo? Isn't it source level
compatible with the "normal" libjpeg?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-06-04 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 2:57 [Buildroot] [PATCH] jpeg-turbo: new package Murat Demirten
2012-06-03 7:21 ` Thomas Petazzoni
2012-06-03 10:12 ` Murat Demirten
2012-06-03 10:53 ` Samuel Martin
2012-06-03 11:17 ` Murat Demirten
2012-06-04 7:51 ` Peter Korsgaard [this message]
2012-06-04 8:41 ` Murat Demirten
-- strict thread matches above, loose matches on Subject: below --
2012-06-03 11:04 Murat Demirten
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=87aa0jseft.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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