Maybe you can use lebain-9. Other than that I think it is a matter of mounting the image in a Linux environment and copying out the driver. At any rate we can pull the kernel configuration, check for any related modules, and copy the userspace binary Mali driver. I have to look into it more.
It seems LeMaker had the source to build the Lebain-9 with Mali and opencl maybe we can send them a message and see if it is possible for LeMaker to share that source Code with us.
It’s been quite a while since the release of the Hikey970. No real support has been shown by neither hikey nor hisilicon. Apparently they leave the opensource community with an impossible task of getting drivers for the hardware inside the board. It is quite a dissapointment to spend money on a board and to intend to develop on it but to find out it has been yet another piece of abandonware.
Where are the days that companies took pride in making an effort to make things work.
The board in its current state is no more practical than an ordinary raspberry pi. It’s supposed to have great GPU and NPU but alas it’s inaccessable. Is this the way to treat your customers? promises but no real delivery? I am very disapponted. (and that is an understatement) When the board became available I ordered one immediately. It said ‘comes with Linux installed.’ But only at delivery it appeared that Android was running and no Linux available. After long waits a crippled Debian image is delivered that lacks drivers for the board. I had already installed debian on mine with the aarch64 repo from debian.org and hoped that the hikey970 debian image would be a serious upgrade. but no, it appears to be exactly the same, no drivers no nothing. If they can build an fbdev driver it means that they have the SDK up and running. They only need to re run a compile with the proper settings for X11 and release the binary to the public. But no, no developer shows up on the support forum nor any binary shows up. Is this plain disregard for the customers who put up their hard earned cash to buy the board? We really can’t tell but clearly they don’t care.
Dear Hikey and Hisilicon,
I would like to request some decent support on this board and a release of drivers for the hardware.
If you are not interested in giving support then please have the decency to reimburse my spending on the board and the time invested.
The mali Driver is available.
It seems it will take a few of us to get everything running smoothly.
I am just a individual Learning what i can as i go.
If everything was done for us I don’t think I would enjoy it as much. I’m more than sure if you ask specific questions relating to specific problems someone will help.
I have a pretty big project started myself.
I am scripting the complete Ubuntu Bionic & Kernel & Drivers into a interactive builder that i am calling the Bionic Builder. Maybe once i have completed it you can test it out and see if you feel a little better.
If a few of us that are halfway knowledgeable got together as a group and worked through fixing issues we could accomplish a lot. I think part of the problem is that the information regarding many issues is scattered about. Answers are out there you just have to find them.
When i Initially purchased the hikey 970 I had hoped that the software and drivers were more mature. But when you buy a development board thats what you get A Dev Board made for developing.
When I get a little further along I will share my work with everyone.
I hope to have something good together within about a week.
Again though I am just a ordinary guy. So don’t expect miracles. But i have fixed some of the issues.
6.The latest Lebian from Lemaker has delivered userspace binary driver for G72. The binary library is /usr/lib/aarch64-linux-gnu/libmali.so. By installing the pocl, two OpenCL platforms can be found on Hikey 970. (Notice that Mali-G72 does not support cl_khr_fp64. )
The OpenCL driver for the mali G72 indeed is there but don’t you think it’s a bit under powered to do NPU tasks compared to the real NPU in the system?
Also the SDK from ARM to build the X11 drivers is only available to the vendors and not to opensource developers. Which implicitly means that there is no opportunity to do this work without these vendors. The availability of the OpenCL driver shows that the SDK is in use by those who released the driver and that they have not performed a build that supports X11.
In short: GPU and NPU are not accessible to developers that use Linux as their base platform.
To say that OpenCL is a viable solution feels like Lamborghini stating that being towed by a truck means that your sports car can do the distance. It simply defeats the purpose of having the hardware in the first place. There are plenty ARM boards available and those have similar specs for OpenCL and raw CPU power. It is the addition of the NPU and the Mali G72 OpenGLES that would actually distinguish this board from others. Unfortunately there is still no driver in sight but there are devices being sold at the moment which have the Kirin970 and those definitely shine in performance. So apparently the Hikey970 is being left out on all those. I really don’t see why this has to be the status quo. By the time that any open source developer has created anything close to a working driver for the fast hardware, the hardware will be obsolete in comparison with the newer offerings.
Technology is fast paced and Kirin980 is there already. It would be sad if this very capable board will go in history as a yet another abandoned development board.
The desktop X11 performance is really not on par even with a raspberry pi. The old Tegra K1 board that sits next to the Hikey970 is almost 100 times faster in graphics. That’s a 5 year old system with Cortex A15. NVidia actually has been releasing new drivers yearly for the graphics system. The latest GeForce RTX 2080 Ti appears to be ‘only’ 70 times faster in benchmarks than the K1. (Can’t check that but https://browser.geekbench.com/cuda-benchmarks seems to know.)
All of those libraries can be found in the AOSP source tree.
And there is the Kenel Driver.
The dts file path: arch/arm64/boot/dts/hisilicon/kirin970-gpu.dtsi
So I was under the impression that those were what we needed.
What are we missing?
As far as the NPU stuff It’s new to me so i have no Idea what you can even do with it.
The thing i am most interested in is using the M.2 Pcie and mini Pcie for expansion. After I get the Bionic-Builder completed I am going to work on the pcie.
I have several expansion Cards some that are for GPU Mining. I believe it may be possible to add a Graphics Card.
Have you sent any messages to hikey? Maybe they will build what you are looking for. I did send them a question about the pcie ports and they gave a decent response. I believe i used the support on the LeMaker Site.
AOSP source tree… Binary drivers for Android, not for Linux like Debian or Ubuntu.
The ones in Debian are not for X11 and unfortunately libhybris is 32 bit only so we cannot use the ones from AOSP in a wrapper.
On the site of Odroid they have the Odroid-N2 announcement that explains that there will not be any X11 drivers for the latest Mali GPUs because ARM has stopped supporting X11. If lucky there may be a Wayland driver for their GPU.
Apparently there won’t be future support for anything else but Android.
Would have been nice to know this beforehand.
Using a different graphics card is certainly a possibility.
If the card comes with binary drivers for x86 that would not be a good idea.
To get the right graphics card it should be fully supported using open source drivers. The specific connector you showed is something I have been looking for too. Most important should be that the driver can be compiled on the hikey970 and that the PCI bus can properly communicate over that bus. Some mini PCI implementations have reduced the PCI memory window to something like 32MB or less and make it impossible to really use the graphics card over the external PCI.
So in short, it requires careful selection of the graphics card and there is no guarantee that the PCI bus can support the card.
I am willing to try the same here. Does the adapter fit on the hikey970?
I don’t think anyone ever messaged them. One of the individuals above in a previous post mentioned that Arm would not be releasing or supporting the X-11 driver for the mail g72.
I agree i am a bit upset about this board myself.
They definitely hyped it up and it has the hardware but the lack of drivers is a shame.
I purchased this board specifically because it has the Mini Pcie Slot and the M.2 Key M Pcie slot. I can’t find much documentation on getting cards to work in these slots though. I have a 512 Gb ssd in the M.2 slot but its not functioning yet.
In my mind the slots are the biggest asset of the board. If we can get them working correctly then we can use the expansion cards I posted above to add a Graphics Card.
If i can add a graphics card and get the NVME SSD Working I will be happy. Ive spent the last week or so building Ubuntu 18.04 and the kernel. I have been unable to get the display working properly. It just remains black. It flashes back and fourth between Analog and Hdmi on my monitor a couple times but never comes up.
I am going to try using the custom EDID.bin loaded by the kernel to try and resolve the issue. It’s disappointing to have so much trouble just getting the display to work.
My monitor is fine and with the Leubuntu 16.04 it works to some degree. Everything displays normal until i drag a Browser window then it freezes and glitches out.
If i leave the system on and it goes into power save to turn off the display then after that the display will not come back on. I have to reboot the board. Even more interesting If i leave it on overnight after the screen goes to sleep even rebooting wont get the display back up. I have to actually re-install ubuntu again for the screen to work again.
It’s sad that the most basic thing of all The Display wont work right.
I spent $75 on the dragonboard and no problems with display at all.
I spend $350 on hikey 970 and expected it to be supported enough to get things working right but unfortunately unless you can fix everything yourself your out of luck.
I have not given up yet but i’m not positive i can get this thing working correctly on my own. Seems we need to get a few of us together and work together on fixing the problems and bringing up the pci slots.
I did come across this patch set for DRM and i am hoping it will help with the display problems.
All together there are a lot of changes made here.
25 files changed, 475 insertions(+), 95 deletions(-)
He didnt put up the modified files or it would be easy.
Only the diff.
So all the patches have to be done by hand.
I’ve not been able to test it out myself but I understood the theory is that the drivers without wayland or X11 do provide graphics support via EGL. The idea is that they can support a wayland compositor that uses EGL for was that they work with a wayland compositor whose backend renders using EGL.
Having said that I don’t recall seeing any success reports with this approach…
It explains the status of the drivers.
ARM dropped support for X in their releases after r16 (Jan 2017). This is a massive pain as that’s what we all still use. Only wayland, fbdev and android are supported after that