From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Raspberry Pi: recommendations for web kiosk
Date: Thu, 26 Jun 2014 19:01:28 +0200 [thread overview]
Message-ID: <20140626170127.GA3742@ned> (raw)
In-Reply-To: <CAAXf6LUR=nSyh3GPk037uYUOE3hRngWmrj+YOxiQe6RD75TRBw@mail.gmail.com>
On Thu, Jun 26, 2014 at 03:15:25PM +0200, Thomas De Schampheleire wrote:
> Hi Eric,
>
> On Thu, Jun 26, 2014 at 2:42 PM, Eric Le Bihan
> <eric.le.bihan.dev@free.fr> wrote:
> > Hi!
> > On Wed, Jun 25, 2014 at 03:02:29PM +0200, Thomas De Schampheleire wrote:
> >> Hi,
> >>
> >> We currently use a Raspberry Pi as a simple web-wall. It cycles every
> >> two minutes between two (non-local) web pages, one of which contains a
> >> few iframes.
> >>
> >> While this can hardly be called a resource-intensive task, the
> >> Raspberry Pi by no means performs this fluently. The pages load
> >> relatively slow, and administration tasks on this pi also suffer from
> >> hickups.
> >>
> >> The pi currently contains a raspbian image (not done by me, I swear!
> >> :-) ) and uses chromium in kiosk mode to display the web pages.
> >>
> >> My basic question is: can I expect to get better performance by
> >> setting up a custom buildroot image, or is rpi so poor in performance,
> >> even for this mundane task?
> >> Which packages should I select to achieve this?
> >>
> >> Do I need an X.org or not really?
> >> If X.org is needed, does 'Kdrive / tinyX' work on rpi, or should I
> >> select modular x.org, and how do these compare.
> >> (as you notice, I have never set up embedded boards with graphical stuff).
> >>
> >> Which browser should/could I use? Preferably something that can run in
> >> fullscreen mode as this is a kiosk-like board.
> >>
> >> Is rpi-userland needed / recommended? How would I benefit from it?
> >>
> >> Any other recommendations/tips are welcome too, of course.
> > Just my two cents: how about using a custom application based on QtWebkit with
> > EGLFS [1]?
> >
>
> This is not a commercial product, but rather an internal information
> screen used on the workfloor. So writing custom applications, which I
> assume is quite some work, is not acceptable. I am hoping for a more
> or less out-of-the-box solution...
Well, thanks to QML and QtWebkit, that is pretty doable. I hacked a quick
example at https://github.com/elebihan/webkiosk, inspired by the Qt examples.
AFAIK, running it with the '-platform eglfs' option should do the trick (not
tested, my RPi is out of order :-( )
Best regards,
ELB
next prev parent reply other threads:[~2014-06-26 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 13:02 [Buildroot] Raspberry Pi: recommendations for web kiosk Thomas De Schampheleire
2014-06-26 12:42 ` Eric Le Bihan
2014-06-26 13:15 ` Thomas De Schampheleire
2014-06-26 14:11 ` Maxime Hadjinlian
2014-06-26 17:01 ` Eric Le Bihan [this message]
2014-07-02 9:04 ` Thomas De Schampheleire
2014-07-03 16:34 ` Arnout Vandecappelle
2014-07-03 21:07 ` Eric Le Bihan
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=20140626170127.GA3742@ned \
--to=eric.le.bihan.dev@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.