Video: QtQuickPlayground running on Raspberry Pi
Here’s some video to keep you interested while we busy ourselves sifting through a neck-deep pile of entries for the logo competition. This is QtQuickPlayground, an example application which demonstrates QtQuick, running under Mer. QtQuick is new to me (it probably is to you too, unless you’re intimate with the innards of your Nokia phone) – it allows the user to build UIs and apps, and here it’s running unaccelerated. The developers at Maemo say acceleration is their next job, but it’s still looking pretty good. Thanks again to Martin Brook for doing the development work on this.
In logo competition news, we’d like to thank you all for your entries – we’ve been pretty overwhelmed by the response. I’ll be posting the shortlist of the very best that we ended up choosing from along with the winner when we’ve come to a decision early next week.
Is making acceleration work the biggest thing software-wise to do before release? What are the other major obstacles? Last time I asked you said:
> Finish final board design
> Finish initial firmware image
> Test run of final boards
> CE/FCC certification of boards if necessary
> Mass production of final boards
How much progress has been made on those things? I really admire the work you are doing to give young people a platform to learn about computers on, I can only imagine what I would have attempted to do if I’d had one as a child.
The final board design is nearly complete – I hope we’ll have artwork to show you in the next couple of weeks. We’re working on the firmware image, and the final boards will come when that design’s in – as will the other points you mention.
Happily for us, acceleration isn’t something we need to do; it’s a third-party job. Plenty of software is running on the development boards we have already and has either been accelerated by the people who make that software, or didn’t need accelerating in the first place.
Awesome, can’t wait.
A. what if after deploy there will be bugs in firmware? will you provide upgrade that we can “flash” on RaspberryPI by ourself? In other words, will you provide “post-sell” firmware support/upgrade?
B. it is not clear the part related to video accelleration. It mean i am in charge to provide video accelleration to my code? there are not syscall i can use? Please explain. In oter wird, the usual videogame you show as example is rewrite to use the accelleration ad it is not only a “apt-get install game_name” from repository?
Bugs on the GPU binary can be easily fixed by updating the blob on the SD card, once the new binary is released. Although its pretty well tested, so finding bugs there is unlikely. The bootloader can be updated in a similar fashion I believe.
Bugs in userland libraries will also be simple to fix – just update the SD card to the new libraries.
Acceleration is provided by Linux libraries – OpenGL ES, Open VG and video API’s (exactly what available here is subject to change at the moment). In the case of Quake some minor code changes were required to iniitialise the OpenGL and convert it to GL ES.
At first , it mostly won’t be as simple as apt-get because many games etc won’t be using the acceleration libraries. We expect that to change as more people get their hands on the boards and port more software to use acceleration.
the reply is clear. thanks.
Great work guys. Can’t wait to see the final product.
One question though. Why is the display not running at full resolution? And, for that matter, why is it only using one part of the display instead of scaling the output? Has that not been implemented yet? Or is that just due to the program not taking up the full screen?
I guess that’s only the software that was running. At the end you can see the console screen, which uses the full display.
Glenn De Backer
Hmm QTQuick is not that new and also not limited to nokia phones. Remember seeing it mentioned on Slashdot some time ago.
That being said I’m really happy with this because I’m planning of using a form of QT embedded on the rasberry pi :-) Seems to be a good combination
Like I said – new *to me*, not new! We’re really pleased to see it running.
the app is hardcoded for N900. Once I get the GLES drivers on I will update to 1920×1080.
Brilliant – thanks again for all the work you’re doing on this, and for the video.
You’d have one more entry if it wasn’t for that stupid cold I got the last few weeks. :(
I must say this looks very interesting, I can hardly wait for the final board design to come out :D
Looks like it is running in full screen mode, by directly calling opengl es API from Qt? Is there any X integration for Raspberry Pi?
I assume it is the old Mer, Maemo based instead of merprojects.org, right?
Yes, X works. LXDE runs fine on top of it. Could probably do with some work to accelerate it, as I *think* it just uses DirectFB at the moment. Some sort of OpenVG back end to X would be good – I think one exists, but not sure how mature it is.
This is indeed using the brand new Mer relaunched yesterday :)
An ARM GNU/Linux box for $25. Take a byte! « majestyx's blog
[…] Video: QtQuickPlayground running on Raspberry Pi […]