Raspberry Pi Rtems-Graphical-Toolkit

Wed May 16 09:39:29 UTC 2018

Hi all,

Thank you and i am sorry for long delay :)

Unfortunately we haven't decided yet what kind of license it will be.
So I can not tell anything about realization right now. (I hope that we
will be able to disccus it later :) )

I think it will be very good if RTEMS has some kind of input subsystem
(keyboards,  mouse, touchscreen) with standard API.

Best regards,
Mikhail

On 9 May 2018 at 18:49, Kirspel, Kevin <Kevin-Kirspel at idexx.com> wrote:

> I am interested in your work as well.  I ported Qt 5.9 to a NXP LPC3250
> last year.  I updated RTEMS LIBBSD to support EVDEV and added to the RTEMS
> MMAP interface to support MMAP handlers in frame buffer drivers.  I was
> successful in getting the QT Quick clock demo application to run on RTEMS
> using the LinuxFB plugin.  I would be interested to see how you created
> your RTEMS plugin.
>
>
>
> Kevin Kirspel
>
> Electrical Engineer - Sr. Staff
>
> Idexx Roswell
>
> 235 Hembree Park Drive
> <https://maps.google.com/?q=235+Hembree+Park+Drive+%0D%0A+Roswell+GA+30076&entry=gmail&source=g>
>
> Roswell GA 30076
> <https://maps.google.com/?q=235+Hembree+Park+Drive+%0D%0A+Roswell+GA+30076&entry=gmail&source=g>
>
> Tel: (770)-510-4444 ext. 81642
>
> Direct: (770)-688-1642
>
> Fax: (770)-510-4445
>
>
>
> *From:* users [mailto:users-bounces at rtems.org] *On Behalf Of *Joel
> Sherrill
> *Sent:* Wednesday, May 09, 2018 12:07 PM
> *To:* Mikhail Svetkin <mikhail.svetkin at gmail.com>
> *Cc:* users at rtems.org; Emre Cetin <hsnemrecetin at gmail.com>
> *Subject:* Re: Raspberry Pi Rtems-Graphical-Toolkit
>
>
>
> Very nice blog Mikhail! And it looks to be great work!
>
>
>
> Thank you for the complimentary things you said about RTEMS features.
>
>
>
> I have a few questions.
>
>
>
> + Is this going to show up in the Qt free edition?
>
>
>
> + Any ideas on what RTEMS could do to improve our side of the
>
> hosting Qt equation? Graphics has always been a challenge.
>
>
>
> FWIW I took a stab at estimating porting Qt a few years ago. It is a large
>
> body of software and a lot is just not appropriate for most embedded
> devices.
>
> I got a reasonable subset to build but never got funding to do the actual
> work.
>
> I am quite thrilled your effort was more successful.
>
>
>
> Thanks.
>
>
>
> --joel
>
>
>
> On Fri, May 4, 2018 at 1:23 PM, Mikhail Svetkin <mikhail.svetkin at gmail.com>
> wrote:
>
> Hi all,
>
>
>
> We started some researches (including Qt on RTEMS), take a look if you are
> interested.
>
>
>
> http://blog.qt.io/blog/2018/05/03/qt-microncontrollers-mcu/
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.qt.io_blog_2018_05_03_qt-2Dmicroncontrollers-2Dmcu_&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=VsNfyIS5DVnaDqkssy4rCWAdJUrP8apiqX-Yw8YA7-k&e=>
>
>
>
>
>
> Mikhail Svetkin
> Software Engineer
>
> The Qt Company
> Sandakerveien 116
> <https://maps.google.com/?q=Sandakerveien+116+%0D%0A0484,+Oslo,+Norway&entry=gmail&source=g>
> 0484, Oslo, Norway
> mikhail.svetkin at qt.io
> +47 488 62 204
> http://qt.io
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__qt.io_&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=3WFQKF32z-8mZnp8v3cPM65-YC6hYDFxelQD2aXuSRU&e=>
>
> [image: Image removed by sender.]
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__qt.io_&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=3WFQKF32z-8mZnp8v3cPM65-YC6hYDFxelQD2aXuSRU&e=>
>
> [image: Image removed by sender.]
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_Qt&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=cddGdGn6jiAflCXK8SIQCt7r47vINFgyPfysbgDhRlw&e=>
>
> [image: Image removed by sender.]
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_qtproject&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=LWR01ky9SX_wPV7NLmjf_9any42WG1RC1YESYhdtyMk&e=>
>
> [image: Image removed by sender.]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_the-2Dqt-2Dcompany_&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=SR7KPT7KOJ9ONluL6iPamxvv44YSWfhc3h6p_Bw6EO4&e=>
>
> [image: Image removed by sender.]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_104580575722059274792&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=GBc5V8aXaSKeuEDp5cqY5sePJNBdHDl-Ld21U__n-1E&e=>
>
> [image: Image removed by sender.]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_QtStudios&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=2-IP13syCEs_A_VmscBvlDxnNNV5hXN8yZFvjAKY0MQ&e=>
>
>
>
>
> Best regards,
> Mikhail
>
>
>
> On 1 May 2018 at 19:01, Kirspel, Kevin <Kevin-Kirspel at idexx.com> wrote:
>
> Another option is to not use X11 and draw directly to the frame buffer
> device (i.e. /dev/fb0).  Qt supports this.
>
>
>
> Kevin Kirspel
>
> Electrical Engineer - Sr. Staff
>
> Idexx Roswell
>
> 235 Hembree Park Drive
> <https://maps.google.com/?q=235+Hembree+Park+Drive+%0D%0A+Roswell+GA+30076&entry=gmail&source=g>
>
> Roswell GA 30076
> <https://maps.google.com/?q=235+Hembree+Park+Drive+%0D%0A+Roswell+GA+30076&entry=gmail&source=g>
>
> Tel: (770)-510-4444 ext. 81642
>
> Direct: (770)-688-1642
>
> Fax: (770)-510-4445
>
>
>
> *From:* users [mailto:users-bounces at rtems.org] *On Behalf Of *Emre Cetin
> *Sent:* Tuesday, May 01, 2018 12:15 PM
> *To:* users at rtems.org
> *Subject:* Fwd: Raspberry Pi Rtems-Graphical-Toolkit
>
>
>
>
>
> ---------- Forwarded message ----------
> From: *Emre Cetin* <hsnemrecetin at gmail.com>
> Date: 2018-05-01 19:13 GMT+03:00
> Subject: Re: Raspberry Pi Rtems-Graphical-Toolkit
> To: Chris Johns <chrisj at rtems.org>
>
> Thank you for your help Chris, I did what you said and it worked. However,
> I learned that Qt Applications works with X11 libraries in systems like
> Rtems. And I have to compile the nxlib library for raspberrypi BSP in the
> rtems-graphical-toolkit for X11. 'graphics\nxlib.bset' in rsb can not be
> build as mentioned in "https://lists.rtems.org/
> pipermail/devel/2015-August/012358.html
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.rtems.org_pipermail_devel_2015-2DAugust_012358.html&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=2qOzfS7qOLo1pWDBn2daTfb11BT4SII6DAGj7Nybgz0&s=FP3leA0B8WdfvIUwiGG0f2VRmehMyQCINAcYMEOWL8k&e=>".
> I understand that the nxlib is included in microwindows library anymore,
> but when I build 'graphics/microwindows.bset', will I also build nxlib?.
> BSP 's X11 header files and so on. How do I add X11 header files to BSP and
> other necessary files? What should I do at this point?
>
>
>
> Best wishes,
>
> Emre
>
>
>
> 2018-05-01 3:22 GMT+03:00 Chris Johns <chrisj at rtems.org>:
>
> On 01/05/2018 02:49, Emre Cetin wrote:
> > Hello everyone,
>
> Hi and welcome.
>
> > I have a Rtems project with Raspberry pi, I need to compile a simple QT
> program.
> > I tried to run this project on Beaglebone Black, but it may not be as
> fast as it
> > should be, it seems easier on Rpi. And I work on the Rpi 1 model B. In
> the last
> > few days I am trying to establish the necessary libraries for QT, but I
> have not
> > been successful.
>
> This sounds like an interesting project.
>
> > I've been working on Rtems-Graphical-Toolbase, but I have not
> > been successful in compilation. I tried a lot of ways but I do not know
> how to
> > load libraries manually yet, I am new to embedded systems.
>
> Welcome to embedded and embedded real-time software.
>
> >
> > I finally used these instructions, it seemed the easiest way to me;
> >
> > (in right directory)
> > ../source-builder/sb-set-builder \
> >     --prefix=$HOME/development/rtems/compiler/5 \
> >     --rtems-bsp=arm/raspberrypi \
> >     --log=graphic-build-log.txt \
> >     --with-rtems-bsp=raspberrypi \
> >     --pkg-tar-files \
> >     graphics/freetype2.bset \
> >     graphics/libjpeg.bset \
> >     graphics/libpng.bset \
> >     graphics/libtiff.bset \
> >     graphics/t1lib.bset \
> >     graphics/microwindows.bset
> >
> > RTEMS Source Builder - Set Builder, 5 (f3b1700dfd4d)
> > Build Set: graphics/microwindows.bset
> > Build Set: graphics/freetype2.bset
> > config: graphics/freetype-2.4.10-1.cfg
> > package: freetype-v2.4.10-arm-rtems5-1
> > error: hash: freetype-2.4.10.tar.gz: insecure: md5
> > Build FAILED
> >
> > It seems that new packages are causing problems, and I do not know how
> to update
> > the codes. Can you give me some advice?
>
> A change went into the RSB in October last year to stop using the MD5 and
> SHA1
> checksums as they are insecure. The ticket that covered this issue is:
>
>  https://devel.rtems.org/ticket/2536
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__devel.rtems.org_ticket_2536&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=2qOzfS7qOLo1pWDBn2daTfb11BT4SII6DAGj7Nybgz0&s=W5nqzhQZQ8MD2Qny_KmidQ3uYRpLeCKJeVIEUl3iORE&e=>
>
> It would seem some packages were missed and they need a better checksum.
> Could
> you please reopen the ticket and indicate the issue you have by pasting in
> the
> above output?
>
> FYI the fix is easy, run a sha512 command on your host on the file or patch
> which should be in the `sources` or `patches` directory and then update
> the line
> in the related file. The freetype config file is:
>
>  rtems/config/graphics/freetype-2.4.10-1.cfg
>
> On the line starting with `%hash` change `md5` to `sha512` and paste in the
> SHA512 checksum.
>
> I see ...
>
>  libjpeg-9a-1.cfg
>  libpng-1.5.24-1.cfg
>  libpng-1.6.21-1.cfg
>  libtiff-4.0.2-1.cfg
>  libtiff-4.0.6-1.cfg
>  microwindows-0.93-dev-1.cfg
>  t1lib-5.1.2-1.cfg
>
> ... are still using MD5 and will need updating.
>
> We welcome patches, it is often the fastest way to get something like this
> fixed. :)
>
> Thanks
> Chris
>
>
>
>
>
>
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.rtems.org_mailman_listinfo_users&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=GvLnp4QsFLEnTgp-tcu5NsRIPM5VycdbAjJQFCY4cJ0&e=>
>
>
>
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.rtems.org_mailman_listinfo_users&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=3l9d5ztgZL8IrTHvJLI4-LwXD6K3_k4zrzE8gCCTKBg&s=GvLnp4QsFLEnTgp-tcu5NsRIPM5VycdbAjJQFCY4cJ0&e=>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20180516/35283a86/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 347 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20180516/35283a86/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 437 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20180516/35283a86/attachment-0005.jpg>