ArmV8 / Aarch64 / ARM64... what would it take?

Want a new feature? Discuss what you would like to see in Ultibo.
User avatar
Ultibo
Site Admin
Posts: 2092
Joined: Sat Dec 19, 2015 3:49 am
Location: Australia

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby Ultibo » Fri May 18, 2018 12:03 am

Gavinmc42 wrote:Bit more on the 64 to 32 bit pointer issue for the VC4.
Fixable in Paul's OMXMMAL code?

You have to remember that the use of 32 bit pointers is intrinsically woven into almost every layer of the userland code and cannot be easily fixed by simple changes to header definitions.

It seems to be possible but it requires someone to do the heavy lifting of checking and adjusting every element of the interaction between the CPU and GPU, so far no one seems to have taken that on.
Ultibo.org | Make something amazing
https://ultibo.org
Gavinmc42
Posts: 1436
Joined: Sun Jun 05, 2016 12:38 pm
Location: Brisbane, Australia

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby Gavinmc42 » Fri May 18, 2018 1:00 am

Just starting playing with Fedora28 Aarch64, like Gentoo64 it uses the V3D stuff
https://fedoraproject.org/wiki/Architec ... berry_Pi_3
https://nullr0ute.com/2018/04/the-raspb ... in-fedora/

Both are now using the mainstream Linux driver and Eric Anholt has even more going into 4.18
This is in config.txt for both

Code: Select all

# This isn't used by mainline VC4 driver so reduce to lowest supported value
gpu_mem=16


How do we use the Linux V3D mainstream code in Ultibo?
As source reference or called lib?
Thinking ahead to Pi4/5, VC5/6, Vulkan too.
Other architectures/SBC's will also use KVM, DRM, V3D/Vulkan at least for the foreseeable future.

I use Ultibo because I find Linux hard to understand, use, maintain etc...... plus it is bloatware for my single purpose apps.

Running Ultibo on other SBC's that have other GPU's will be hard unless we use existing methods that someone else has figured out ;)
Anyway just something to think about after all those status boxes are green :D
Gavinmc42
Posts: 1436
Joined: Sun Jun 05, 2016 12:38 pm
Location: Brisbane, Australia

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby Gavinmc42 » Wed Jun 27, 2018 6:14 am

You have to remember that the use of 32 bit pointers is intrinsically woven into almost every layer of the userland code and cannot be easily fixed by simple changes to header definitions.


Is there clues here
https://github.com/anholt/mesa/blob/mas ... iling_lt.c

Code: Select all

 if (gpu_stride == 8) {
 
 } else {
assert(gpu_stride == 16);
 
fredvs
Posts: 30
Joined: Tue Sep 25, 2018 11:57 am

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby fredvs » Wed Oct 31, 2018 1:56 pm

Hello.

Big congratulations for that impressive project.

I am in the exploring phase of Ultibo and have lot of wow trying it on my Rpi3.

I develop also in Pascal (with Delphi, FPC and testing MSElang) and I am fan of fpGUI and MSEgui, so Ultibo is more than a dream... it exists!

Could it be possible to make Ultibo run on "common" mobiles (those that use Android) with mobile-ARM cpu?

Thanks.

Fre;D
pik33
Posts: 817
Joined: Fri Sep 30, 2016 6:30 pm
Location: Poland
Contact:

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby pik33 » Wed Oct 31, 2018 6:31 pm

Could it be possible to make Ultibo run on "common" mobiles (those that use Android) with mobile-ARM cpu?


This is all documentation (or rather lack of it) problem and then the work power to add all these hardware dependent units which will work on these platforms.
User avatar
Ultibo
Site Admin
Posts: 2092
Joined: Sat Dec 19, 2015 3:49 am
Location: Australia

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby Ultibo » Wed Oct 31, 2018 10:30 pm

fredvs wrote:Could it be possible to make Ultibo run on "common" mobiles (those that use Android) with mobile-ARM cpu?

Hello, in general it is possible to add the necessary support for any hardware or device to Ultibo.

But as pik33 points out it requires time to do it and sometimes documentation (especially for commercial devices like phones) is hard to come by.

We also have to be careful to use our time wisely and put effort into the things that will provide the most benefit to people wanting to use Ultibo, that means choosing hardware that is easy to obtain and has information available for anyone wanting to create projects. We will add more targets to Ultibo but right now the focus is on expanding the features and adding the things that are most wanted.
Ultibo.org | Make something amazing
https://ultibo.org
fredvs
Posts: 30
Joined: Tue Sep 25, 2018 11:57 am

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby fredvs » Thu Nov 01, 2018 8:48 pm

@pik33 and Ultibo: Thanks for answer.

OK, I will stay to explore Ultibo + Rpi.

I did seen that you have implemented fpGUI for Ultibo --> Great (I have many fpGUI open-source applications! https://github.com/fredvs).

So I did try the fpGUI-Ultibo demos (aggcanvas, canvastest and helloword).

All 3 did compile and produce kernel7.img and aggcanvas.elf, canvastest.elf and helloword.elf.

But copying kernel7.img and aggcanvas.elf and the RPi3 firmware on the sd-memory gives only a beautiful square in middle of screen filled with rainbow-colors (see picture).

Image

I have the same result for canvastest.elf and helloword.elf too (only a colored screen).

Maybe I miss something (The HelloTiger demo works like charm).

Thanks.

Fre;D
pik33
Posts: 817
Joined: Fri Sep 30, 2016 6:30 pm
Location: Poland
Contact:

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby pik33 » Fri Nov 02, 2018 6:56 am

If you dowloaded the Ultibo installer 2.0.029 and you have RPi3B+ (the newest) you have to upgrade and recompile RTL.
User avatar
Ultibo
Site Admin
Posts: 2092
Joined: Sat Dec 19, 2015 3:49 am
Location: Australia

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby Ultibo » Fri Nov 02, 2018 9:49 am

fredvs wrote:I did seen that you have implemented fpGUI for Ultibo --> Great (I have many fpGUI open-source applications! https://github.com/fredvs).
...

But copying kernel7.img and aggcanvas.elf and the RPi3 firmware on the sd-memory gives only a beautiful square in middle of screen filled with rainbow-colors (see picture).

HI Fred,

If you happen to be using a Pi 3B+ then pik33 may be correct about needing the latest RTL, but since you said that other examples work then that may not be the problem.

As per the Readme, fpGUI is still a work in progress and the only items working (somewhat) are those three examples. It's possible we may have broken something while adding other recent changes so we'll test them again when we have a chance.

We're taking a bit of a detour and adding some other items before we come back to fpGUI even though the FreeType font support that was originally missing is now resolved. Along the way we're hoping to make it possible to support not only fpGUI but a much wider choice of interfaces depending on your preference.
Ultibo.org | Make something amazing
https://ultibo.org
fredvs
Posts: 30
Joined: Tue Sep 25, 2018 11:57 am

Re: ArmV8 / Aarch64 / ARM64... what would it take?

Postby fredvs » Fri Nov 02, 2018 12:31 pm

Hello and thanks for answers.

If you happen to be using a Pi 3B+ then pik33 may be correct about needing the latest RTL, but since you said that other examples work then that may not be the problem.

Ha, ok, I will try with latest RTL.

Along the way we're hoping to make it possible to support not only fpGUI but a much wider choice of interfaces depending on your preference.

Martin's MSEgui is **very** great and mature and would be perfect for Ultibo.

Thanks.

Fre;D

Return to “Feature requests”

Who is online

Users browsing this forum: No registered users and 0 guests