Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] turbovnc: new package
Date: Fri, 03 Nov 2017 01:20:35 +0200	[thread overview]
Message-ID: <59FBA843.7010006@petroprogram.com> (raw)
In-Reply-To: <20171102222811.4d501282@windsurf>

Hi

2.11.2017, 23:28, Thomas Petazzoni kirjoitti:
>> I posted question to github if bzip2, freetype2 and zlib can be external
>> dependencies or if they contain some TurboVNC specific stuff.
> Thanks. Let's see what upstream says.
>
> Best regards,
>
> Thomas

Yeah. Im actually pretty excited to test and see how well TurboVNC 
server will perform with
Raspberry Pi 2 or 3 after reading about TurboVNCs possibility of
using multithreading on multi-core systems and other acceleration tricks.

https://github.com/TurboVNC/turbovnc/blob/master/doc/performance.txt

And then there is this:
https://github.com/TurboVNC/turbovnc/issues/95

I did not even know that there are 3 different implementations of
SIMD-accelerated zlib's out there.
:-O

-S-

  reply	other threads:[~2017-11-02 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 12:40 [Buildroot] [PATCH v2 1/1] turbovnc: new package Stefan Fröberg
2017-11-01  6:06 ` Baruch Siach
2017-11-01  9:53   ` Thomas Petazzoni
2017-11-02 21:21     ` Stefan Fröberg
2017-11-02 21:28       ` Thomas Petazzoni
2017-11-02 23:20         ` Stefan Fröberg [this message]
2017-11-03 22:17         ` Stefan Fröberg
2017-11-06 13:13         ` Stefan Fröberg
2017-11-06 19:59           ` Baruch Siach
2017-11-06 20:05             ` Thomas Petazzoni
2017-11-06 22:19           ` Arnout Vandecappelle
2017-11-06 22:38             ` Thomas Petazzoni
2017-11-07 13:28               ` Stefan Fröberg
2017-11-01 19:18   ` Stefan Fröberg

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=59FBA843.7010006@petroprogram.com \
    --to=stefan.froberg@petroprogram.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