Thank you Sean for letting us know that Qt3d runs on the IMX6 and Tegra K1
platform. Your work is invaluable. Qt3d works well on desktop so I have
faith that it will run on many other embedded platforms. I will have uses
that can will take advantage of these two platforms.

The Raspberry Pi is a powerful platform that will use Qt3d eventually and
properly.  So many developers, like me, are on shoestring budgets and I
want to reach them as the world needs lower priced platforms.

One of your developers has a Raspberry Pi. His name is James Turner. I
spoke with him at Sigraph and he showed an enthusiasm for getting it up and
running on the Raspberry Pi.

Pierre

On Tue, Aug 1, 2017, 3:17 AM Sean Harmer <sean.har...@kdab.com> wrote:

> Hi,
>
> On Tuesday, 1 August 2017 08:20:27 BST Pierre Chicoine wrote:
> > First, thank you KDAB for your contribution of Qt3D. It has a lot of
> > potential and looks thoroughly thought out. Especially you Sean. I will
> try
> > that multiple window stuff you sent me soon.
> >
> > I should mention that I've tried Yocto also on the Raspberry Pi. It
> doesn't
> > work. My guess is that there are no embedded boards supported, no matter
> > how expensive or inexpensive as no one has responded with any platform on
> > any device except desktop and Android and that's probably a high end
> > smartphone but I don't know. I would go to a more expensive board but
> > cannot afford wasting time testing all manner of embedded boards. Also I
> > have to think about my future customers and projects and how much they
> are
> > willing to spend on this. IOT must be reasonably priced.
>
> I already said I've had it working on iMX6 - this was with both a yocto
> image
> and with QNX (both ES2). The Tegra K1 works with its out of the box image
> once
> you build Qt for it - which you can even do in situ once you enable some
> swap
> space! I also know the guys at TQC have it running on boot2qt images even
> with
> a <1sec boot time.
>
> > Qt3D is a great project for non embedded devices. It has great potential.
> > At this stage, though, I believe Qt3D was a mistake for me and I should
> > have continued with OpenGL ES2, I would have had it working on OpenGL ES
> on
> > the Raspberry  by now.
>
> Qt 3D works fine on ES 2. The issue is the GLSL compilers in some of the
> binary
> blob drivers. But you will hit the same issues even if using pure ES2 vs Qt
> 3D. Yes we could try to work around the compiler issues by providing
> modified
> shaders for these but it's a pain.
>
> I've asked for someone here to try to locate a rasp pi 3 and see what needs
> fixing there. It's purely shader issues. There's nothing fundamentally
> wrong
> we're doing for ES 2 support.
>
> Cheers,
>
> Sean
> --
> Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
> KDAB (UK) Ltd, a KDAB Group company
> Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090
> Mobile: +44 (0)7545 140604
> KDAB - Qt Experts
>
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to