[REFERENCE] Mali r4p0 for Image builders

Moderators: meveric, mdrjr, odroid

[REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Wed May 21, 2014 10:24 am

As from today we aren't supporting Mali r3p2 anymore. We are moving to r4p0.

We don't need Mali DDX anymore. Instead we use armsoc.
UMP doesn't exist anymore. Mali is now using dma-buf.

To adapt your image or make your image with the new Mali drivers.

Blobs:
EGL/GLESv1/GLESv2 X11 MP400-4 -> http://builder.mdrjr.net/tools/mali-r4p0.txz
EGL/GLESv1/GLESv2 FBDEV MP400-4 -> http://builder.mdrjr.net/tools/r4p0-mp400-fbdev.tar
XU3 Mali T628-MP6 Blobs (FBDEV and X11) -> http://malideveloper.arm.com/develop-fo ... for-linux/

This also includes a example .conf for xorg. (Not needed, just optional).

Armsoc DDX improved by dsd -> https://github.com/mdrjr/xf86-video-armsoc/tree/r4p0
Use the r4p0 branch.

If your defconfig still has UMP it will probably fail to build. Make sure you remove it.
Reference defconfigs doesn't have UMP anymore.

Tests for FBDEV are here -> http://malideveloper.arm.com/develop-fo ... for-linux/


-------------------------------------------------------------------------------------------------


In case anyone want to know this is the EULA.
Code: Select all
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1.   SCOPE AND DEFINITIONS

This End User License Agreement (this “Agreement”) is a legal agreement concerning your use of the Software (defined hereafter) described below. The rights granted to the Software are expressly conditioned upon acceptance of these terms and conditions by the legal entity or person acquiring the license. If you are using the Software as an employee, the company that employs you is the "Licensee" and you are binding the company, and yourself personally, to these terms and conditions by using the Software. References below to "you" or "your" refer to the licensee of the Software. Hardkernel Co., Ltd. (“Hardkernel”) is the "Licensor," regardless of whether you received the Software from Hardkernel directly or an authorized distributor.

1.1   "Software" means the specific software products, MALI-400 MP DDK in object code form, and all related documentation provided to you.


2.   License

2.1   Hardkernel hereby grants Licensee a limited, non-exclusive, non-transferable, irrevocable, restricted right to use the Software in object code form only on the Computer System solely for the purpose of developing application software for Hardkernel devices using the Samsung Exynos 4412 System-on-a-Chip.

2.2   The Software except as permitted elsewhere in the Agreement, the rights granted to you above are conditional upon your compliance with the following obligation:

2.2.1   The Software should be used solely to develop application software for ARM Product.

2.2.2   The Software should be used with silicon chipset manufactured by Licensor.

2.2.3   You will not transfer, assign, lease, lend or rent the Software or documentation, use them to provide service bureau, time-sharing or other services, or otherwise provide or make the functionality thereof available to third parties except as expressly authorized in this Agreement.

2.2.4   You will not disassemble, decompile, reverse engineer, modify or create derivative works of the Software or documentation nor permit any third party to do so, except to the extent such restrictions are prohibited by applicable mandatory local law.

2.2.5   You will not delete or in any manner alter the copyright, trademark or other proprietary rights notices appearing on the Software or documentation as delivered or distributed by Hardkernel. You will reproduce such notices on all copies you are authorized to make of the Software.

3. WARRANTIES AND LIMITATION OF LIABILITY

3.1 No Warranty. Hardkernel does not warrant that the Software will meet your requirements, that the Software will operate in combination with any other equipment, devices, software or systems, or that the operation of the Software will be error-free or uninterrupted. The Software is provided "AS IS" and “WITH ALL FAULTS.” HARDKERNEL DISCLAIMS ALL WARRANTIES, CONDITIONS AND REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING THOSE RELATED TO MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, ACCURACY OR COMPLETENESS OF RESULTS, CONFORMANCE WITH DESCRIPTION, AND NON-INFRINGEMENT. HARDKERNEL SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, CONDITIONS AND REPRESENTATIONS ARISING OUT OF COURSE OF DEALING, USAGE OR TRADE. NO INFORMATION OR ADVICE GIVEN BY HARDKERNEL OR ITS AGENTS, EMPLOYEES, OR REPRESENTATIVES, WHETHER ORAL OR WRITTEN, SHALL CREATE ANY REPRESENTATION OR WARRANTY. YOUR USE OF THE SOFTWARE AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SOFTWARE IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE.

3.2 Limitation of Liability. TO THE EXTENT PERMITTED BY LAW, IN NO EVENT WILL HARDKERNEL BE LIABLE TO YOU FOR ANY DIRECT SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF USE, DATA, BUSINESS OR PROFITS, REVENUE, GOODWILL, ANTICIPATED SAVINGS) OR FOR THE COST OF PROCURING SUBSTITUTE PRODUCTS OR SERVICES ARISING OUT OF THIS AGREEMENT, WHETHER BASED UPON CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), FAILURE OF A REMEDY TO ACCOMPLISH ITS PURPOSE, STRICT LIABILITY OR OTHERWISE, AND EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You may have other rights under applicable mandatory local laws.

4. TERMINATION

4.1 Termination. You may terminate this Agreement at any time by ceasing your use of the Software and deleting all Software and documentation. Hardkernel will have the right to terminate this Agreement if you: (a) breach any material term of the Agreement, and if such breach is capable of cure, you fail to cure such breach within thirty (30) days after receiving written notice thereof; or (b) assert any claim against Hardkernel, its licensees or customers alleging that the Software infringes or misappropriates any of your intellectual property rights. Either party will have the right to terminate this Agreement if the other becomes insolvent or makes an assignment for the benefit of creditors, or a trustee or receiver is appointed for such other party or for a substantial part of its assets, or bankruptcy, reorganization or insolvency proceedings shall be instituted by or against such other party. Termination of this Agreement under this section terminates all licenses granted hereunder.

4.2 Effect of Termination. Upon termination or expiration of this Agreement, all Software licenses and rights to use Confidential Information that are granted thereunder shall terminate. Upon termination of this Agreement or expiration of the license term, you will promptly return to Hardkernel or destroy the applicable Software and confidential information and all copies and portions thereof, in all forms and types of media.

4.3 Survival. Sections 1, 2.2, 3, 4, and 5 will survive the termination of this Agreement.

5. GENERAL

5.1 Confidentiality. You acknowledge and agree that the Software was developed at considerable time and expense and contains valuable trade secrets and confidential information. Accordingly, you agree to maintain the Software in confidence and except as expressly provided in Section 2 (Grant of License), you (i) will not disclose or provide access thereto to any person, or (ii) use the Software for any purpose not expressly authorized hereby, or permit or authorize any other person to do so. The restriction herein shall not apply to the extent that such information is in the public domain or hereafter falls into the public domain through no fault of you. Any combination of Hardkernel trade secrets and information that forms part of the Software shall not be deemed to be public merely because individual parts of the Software are in the public domain. You acknowledge that violations of the confidentiality obligations herein may cause Hardkernel irreparable injury for which an adequate remedy at law may not be available. Therefore, Hardkernel shall be entitled to seek all remedies that may be available under equity, including immediate injunctive relief, in addition to whatever remedies may be available at law.

5.2 Indemnification. To the extent permitted by law, you agree to indemnify, defend and hold harmless Hardkernel, its affiliates, directors, officers, and employees (each a "Hardkernel Indemnified Party") from any and all claims, losses, liabilities, damages, expenses and costs (including without limitation attorneys fees and court costs) incurred by a Hardkernel Indemnified Party as a result of: (i) your breach of this Agreement; or (ii) any claims that the distribution, sale, offer for sale, use or importation of your product (excluding the Software as provided by Hardkernel) infringes or misappropriates any third party intellectual property or proprietary rights.

5.3 Export Control. You agree to comply fully with all relevant export laws and regulations, including those of the United States and the Member States of the European Union. These laws include restrictions on destinations, end-users and end use. You will ensure that neither the Software, nor any direct product thereof are: (a) exported or re-exported directly or indirectly in violation of applicable export laws; or (b) used for any purposes prohibited by applicable export laws, including but not limited to nuclear, chemical, or biological weapons proliferation. You will, at Hardkernel's request, demonstrate compliance with all such applicable export laws, restrictions, and regulations.

5.4 Assignment. You may not assign this Agreement, in whole or in part, by operation of law or otherwise. Any attempt to assign this Agreement without such consent will be void and of no effect. Subject to the foregoing, this Agreement will bind and inure to the benefit of each party's permitted successors and assigns.

5.5 Governing Law and Jurisdiction. This Agreement, including all matters of construction, validity, and performance, shall be governed by and construed and enforced in accordance with the laws of the Republic of Korea (without giving effect to any conflict of law rule that would cause the laws of another jurisdiction to be applied). Any and all disputes between Hardkernel and You in connection with or arising out of this Agreement, which the parties are unable to resolve between themselves, shall be finally settled by arbitration. The arbitration shall be held in Seoul, Korea in accordance with the Rules of Arbitration of the International Chamber of commerce by one or more arbitrator(s) appointed in accordance with the said rules. The arbitration award rendered by the arbitrator(s) shall be final and binding upon the parties.
 
5.6 Nonexclusive Remedy. Except as expressly set forth in this Agreement, the exercise by either party of any of its remedies under this Agreement will be without prejudice to its other remedies under this Agreement or otherwise.

5.7 Force Majeure. Neither party will be responsible for any failure or delay in its performance under this Agreement (except for any payment obligations) due to causes beyond its reasonable control, including, but not limited to, labor disputes, strikes, lockouts, shortages of or inability to obtain labor, energy, raw materials or supplies, war, terrorism, riot, natural disasters or governmental action.

5.8 Entire Agreement; Modification; Interpretation. This Agreement constitutes the complete and exclusive understanding and agreement between the parties regarding its subject matter and supersedes all prior or contemporaneous agreements or understandings, written or oral, relating to its subject matter. Failure to enforce any provision of this Agreement will not constitute a waiver of future enforcement of that or any other provision. Any waiver, modification or amendment of this Agreement will be effective only if in writing and signed by you and an authorized representative of Hardkernel. If for any reason a court of competent jurisdiction finds any provision of this Agreement invalid or unenforceable, that provision will be enforced to the maximum extent permissible and the other provisions of this Agreement will remain in full force and effect.

5.9 U.S. Government End Users.   The Software is a "commercial item" as defined in FAR 2.101.  Government software and technical data rights in the Software include only those rights customarily provided to the public as defined in this Agreement. This customary commercial license in technical data and software is provided in accordance with FAR 12.211 (Technical Data) and 12.212 (Computer Software) and, for Department of Defense purchases, DFAR 252.227-7015 (Technical Data -- Commercial Items) and 227.7202-3 (Rights in Commercial Computer Software or Computer Software Documentation).  Accordingly, all U.S. Government End Users acquire Software with only those rights set forth herein.

END OF TERMS
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Wed May 21, 2014 10:26 am

Is there any change in the blobs from the ones in the Lubuntu 13.10 image?
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Wed May 21, 2014 10:27 am

memeka wrote:Is there any change in the blobs from the ones in the Lubuntu 13.10 image?


Nope.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Wed May 21, 2014 7:33 pm

Just a few questions regarding this...

Any difference in the development headers? I noticed the headers in the Lubuntu 13.10 image were different from the usual r3p2 ones. Just want to check if it actually matters, since there were no headers included in the mali-r4p0.txz linked in the OP.

Also, any chance for X-less blobs in the near or distant future? :)
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Wed May 21, 2014 9:59 pm

youka wrote:Just a few questions regarding this...

Any difference in the development headers? I noticed the headers in the Lubuntu 13.10 image were different from the usual r3p2 ones. Just want to check if it actually matters, since there were no headers included in the mali-r4p0.txz linked in the OP.

Also, any chance for X-less blobs in the near or distant future? :)


No, Headers are the same.

Yes there is... I'll work on getting framebuffer too :)
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Wed May 21, 2014 10:11 pm

mdrjr wrote:Yes there is... I'll work on getting framebuffer too :)

You're my hero if this happens! :D
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby recliq » Fri May 23, 2014 7:17 pm

I'm running debian jessie and I'm trying to upgrade the kernel and use the new mali but I can't find the xserver-xorg-video-armsoc package...
The kernel update script fails while trying to comile the armsoc ddx driver because of this.

Am I missing a apt source?
Right now I havce only this in my /etc/apt/sources.list:
Code: Select all
deb http://ftp.debian.org/debian main contrib non-free
deb-src http://ftp.debian.org/debian main contrib non-free
User avatar
recliq
 
Posts: 111
Joined: Mon Feb 25, 2013 6:07 pm
Location: Germany
languages_spoken: english, german
ODROIDs: 2xU2 + U3 + XU3 + 2xXU4 + C2

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Fri May 23, 2014 7:32 pm

there is no xserver-xorg-video-armsoc in debian.
the source of that is the one in dsd's repository - just clone it and compile it.
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby recliq » Fri May 23, 2014 7:49 pm

Ah ok, thank you!
I will do that.

But I think the the kernel-update script should be corrected then because it's likely to always fail in this case...
Code: Select all
mali_update() {
        if [ "$BOARD" != "odroidxu" ]; then
                echo "*** Updating your Mali Installation to r4p0"
                mkdir /tmp/mali-update
                export ACTUAL_PATH=`pwd`
                cd /tmp/mali-update
                wget builder.mdrjr.net/tools/mali-r4p0.txz
               
                if [ "$DISTRO" = "ubuntu" ] || [ "$DISTRO" = "debian" ]; then
                        # dependencies for building armsoc ddx.
                        # for now on.. we build it on the customer board and avoid the Xorg ABI issue
                        apt-get -y build-dep xserver-xorg-video-armsoc
                        apt-get -y install build-essential git xz
                fi

                # building the ARMSOC and putting into place should be distro-agnostic
                git clone --depth 1 https://github.com/mdrjr/xf86-video-armsoc.git -b r4p0 armsoc-r4p0
                cd armsoc-r4p0
                ./autogen.sh --with-drmmode=exynos
                make -j5
                make install
                cp /usr/local/lib/xorg/modules/drivers/armsoc* /usr/lib/xorg/modules/drivers
                cd ..

                # Mali Blobz
                tar -Jxf mali-r4p0.txz
                cp mali/config/xorg.conf /etc/X11/xorg.conf
                cp -aRP mali/* /usr/lib
                ldconfig
        fi
}
User avatar
recliq
 
Posts: 111
Joined: Mon Feb 25, 2013 6:07 pm
Location: Germany
languages_spoken: english, german
ODROIDs: 2xU2 + U3 + XU3 + 2xXU4 + C2

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby recliq » Fri May 23, 2014 8:21 pm

I think I found another issue:

The configure script for xf86-video-armsoc seems to need some more dependency checking...

1. configure fails if xserver-xorg-dev is not installed with
Code: Select all
checking which DRM driver to use... exynos
./configure: line 18627: syntax error near unexpected token `RANDR,'
./configure: line 18627: `XORG_DRIVER_CHECK_EXT(RANDR, randrproto)'
  configure failed


2. make fails if libudev-dev is missing
User avatar
recliq
 
Posts: 111
Joined: Mon Feb 25, 2013 6:07 pm
Location: Germany
languages_spoken: english, german
ODROIDs: 2xU2 + U3 + XU3 + 2xXU4 + C2

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Fri May 23, 2014 8:27 pm

This should be installed by the build-dep above.. :)
Works on Ubuntu but its failing on debian.. This is what I need to check..
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Fri May 23, 2014 10:29 pm

mdrjr wrote:This should be installed by the build-dep above.. :)
Works on Ubuntu but its failing on debian.. This is what I need to check..


on debian you need something like...
sudo apt-get install xserver-xorg-dev libudev-dev

there might be one more package but I can't remember atm. but xserver-xorg-dev should bring in most of the stuff...
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Fri May 23, 2014 10:54 pm

Actually it would be better to just build-dep any other ddx driver :)
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby recliq » Fri May 23, 2014 11:29 pm

sudo apt-get install xserver-xorg-dev libudev-dev
worked for me.
User avatar
recliq
 
Posts: 111
Joined: Mon Feb 25, 2013 6:07 pm
Location: Germany
languages_spoken: english, german
ODROIDs: 2xU2 + U3 + XU3 + 2xXU4 + C2

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Sat May 24, 2014 2:02 am

updated the script for better debian support :)
I've tested on our stock wheezy image and it works
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby krapapock » Sun Jun 01, 2014 9:49 pm

Sorry ... move to
viewtopic.php?f=79&t=5078
Last edited by krapapock on Sun Jun 01, 2014 10:14 pm, edited 1 time in total.
krapapock
 
Posts: 4
Joined: Sun Jan 26, 2014 1:19 am
languages_spoken: english, french
ODROIDs: U3

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Sun Jun 01, 2014 9:52 pm

This is not the place to ask for help. This is a reference for people that knows how to use this.
Create your own thread asking for help with LOGS! Xorg log , xorg.conf.. to start so we can quite understand what's wrong for you.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Tue Jun 03, 2014 6:21 pm

mdrjr wrote:Yes there is... I'll work on getting framebuffer too :)


So uhh... I don't want to be a nag, but any ETA on this? (like maybe this month? or next month? or later this year?). I'm very eager for this (got projects to do~), but I also don't mind waiting if I know how long I should expect to wait.
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Tue Jun 03, 2014 9:19 pm

I promise to sit down today and work on it for you guys.
So I can have at least an ETA
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Wed Jun 04, 2014 6:26 pm

mdrjr wrote:I promise to sit down today and work on it for you guys.
So I can have at least an ETA


That would be great, thanks :)
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Fri Jun 20, 2014 7:54 pm

Any news on the fb drivers? (sorry for being a nag)
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby odroid » Fri Jun 20, 2014 8:59 pm

ARM Mali supports only x11, Wayland and Android. :(
We are talking to ARM now to hear the possibility in the future.
User avatar
odroid
Site Admin
 
Posts: 28718
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Fri Jun 20, 2014 11:32 pm

is there a way to get wayland going?
this would be beneficial especially for xu
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby odroid » Sat Jun 21, 2014 2:33 am

memeka wrote:is there a way to get wayland going?
this would be beneficial especially for xu


XU doesn't have the Mail. :(
User avatar
odroid
Site Admin
 
Posts: 28718
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Sat Jun 21, 2014 5:36 am

odroid wrote:
memeka wrote:is there a way to get wayland going?
this would be beneficial especially for xu


XU doesn't have the Mail. :(


wayland supports libhybris
https://www.youtube.com/watch?v=wInZgLolKgo
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Mon Jun 23, 2014 2:36 pm

odroid wrote:ARM Mali supports only x11, Wayland and Android. :(


Well, Wayland means X-less EGL/GLES2 support, so if it's possible to get that working, that would be great
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Mon Jun 23, 2014 2:52 pm

youka wrote:
odroid wrote:ARM Mali supports only x11, Wayland and Android. :(


Well, Wayland means X-less EGL/GLES2 support, so if it's possible to get that working, that would be great


lol
yes but that means having drivers that support that :roll:
and anyway wayland does not mean that ;)
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Mon Jun 23, 2014 3:25 pm

memeka wrote:and anyway wayland does not mean that ;)

Oh? I was under the impression Wayland ran on top of EGL... Am I wrong?
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Mon Jun 23, 2014 3:36 pm

youka wrote:
memeka wrote:and anyway wayland does not mean that ;)

Oh? I was under the impression Wayland ran on top of EGL... Am I wrong?


wrong in what wayland is, not necessarly on the big picture (where big picture = something using EGL :D).
WAYLAND is a PROTOCOL. it defines how a display server (called a wayland compositor, e.g. WESTON) communicates with clients. The apps (clients) render content directly in GPU using EGL (modified to include wayland extensions).
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Mon Jun 23, 2014 3:59 pm

Ah! Thanks for the info! :) I'm not that clued up on Wayland, guess I should do a little more research...

Though I'm still wandering about the Mali fb drivers. mdrjr said a few weeks back he'd look into it, but still no word (that I can find) on it. Just wanted to know if it's in development, if it's gonna take long, or if it's not possible, just some sort of feedback
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Mon Jun 23, 2014 4:55 pm

I would say probably taking a while...
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Wed Jun 25, 2014 4:37 pm

Ugh...It's just the fact that I can't get a solid answer out of the only person able to give one. This is why I hate this proprietary closed bs. And I know it's not Hardkernel's fault, but it makes it that all us developers with deadlines can only rely on Hardkernel staff with the access to the DDK (and from what I can gather, mdrjr is the only one working these kinds of things) to eventually get back to us. He promised weeks ago to at least check it out and give us an ETA or just a guestimate timeline even. I would have even been happy with "Sorry, I don't know how long it'll take", because then I know not to sit and wait for something that might come in either a week, or in a year's time, and rather start looking for an alternative (and to be honest, I'd like to stick with using Odroids over hunting for other development platforms).

Like I've said before, I don't mind waiting if I know how long I have to wait. I just find this lack of feedback concerning, considering I've received nothing but great service from Hardkernel and this forum. So if it's taking long, that's fine, if it's not being worked on at all, that's fine too. I'd just like some form of feedback when I ask about something
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby memeka » Wed Jun 25, 2014 4:58 pm

well it's really hard to say, but when I said probably taking a while is because:

* @odroid said they want to release XU2 in Q3 2014 if I am not mistaken - Q3 starts now in july, so that means right now probably all human resources are dedicated on XU2
* according to what @mdrjr said, he is also working on XU, where there is no native EGL + linux solution yet - he said he had not a lot of progress and working on some "ugly" solution - in any case, XU seems like took more of his time than expected
* U3 is currently the most supported

so it would make sense to drop working on U3 for a while and concentrate efforts on the other platforms that are stuck behind. XU is still using 3.4 kernel so probably mdrjr is also working on some newer kernel for that not just Mali...
all of the above looks like lots of work to me - hence that's why I said that working on providing Mali support (new Mali binary blobs) for a board that already has Mali working - for a handful of ppl that don't want to use X looks like very low priority.

if i were hardkernel, my priorities would probably be: XU2 -> XU -> U3, with some more minor distractions (like maybe some kind of shield for XU/XU2 like it was on U3? some cool new stuff like odroid-show, odroid-weather etc...) - and even these projects more important than U3 atm. and maybe even start thinking already on the next board - XU3/U4 ...

(then again maybe mali w/ no X is very simple and takes hours to do and we can have it soon :P)
User avatar
memeka
 
Posts: 4044
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Wed Jun 25, 2014 5:25 pm

Ah, yes. It makes sense that they'd focus their priorities elsewhere now, especially you mentioning the XU2/U4 (or whatever new board(s) they're working on that I completely forgot about). You're also right about those wanting what I want being the minority, and thus, lowest priority. This would make sense if it were alot of work to look into/develop these drivers (or even if it were simple, it'd still be sensible to leave it for later if there were more pressing matters at hand).

My point was more: is he really too busy to reply to a simple question asked by a customer? It was more of a "personal principals" rant than questioning his schedule :) (which I totally expect & respect)
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Thu Jun 26, 2014 12:08 am

First. Sorry. I missed the thread somehow.. Too much holidays here. This worldcup stuff is already taking me out of myself.

Second.. Kinda hard to give you an ETA. I understand that you do relay on us to provide that for you. But we do relay on ARM to talk back to us.
I can't give you an ETA if ARM doesn't reply my issues :(
Simple as that.

If I tell you now.. 1 month.. Its a lie.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby youka » Fri Jun 27, 2014 2:45 pm

mdrjr wrote:First. Sorry. I missed the thread somehow.. Too much holidays here. This worldcup stuff is already taking me out of myself.

Second.. Kinda hard to give you an ETA. I understand that you do relay on us to provide that for you. But we do relay on ARM to talk back to us.
I can't give you an ETA if ARM doesn't reply my issues :(
Simple as that.

If I tell you now.. 1 month.. Its a lie.


Thanks for the feedback :) I actually forgot about the worldcup being there in Brazil...

But yeah, I'll make another plan in the meantime until there's more news on this (or I'll just wait for the next Odroid, hoping it'll support such functionality :D)
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby pws » Mon Jun 30, 2014 3:49 am

memeka wrote:... if i were hardkernel, my priorities would probably be ...

I'd concentrate on the U3+ family and associated HW/SW development platform, as everything else is substantially a distraction to further improving its position in the market, and driving its volume up, and price down. (Although not the latest, the 4412 is hard to beat from a cost-power-performnace perspective, and as it's capable of satisfying a large majority of application requirements, there's little point to spending resources on other things until some alternative becomes more promising.)
pws
 
Posts: 71
Joined: Fri Apr 18, 2014 7:52 am
languages_spoken: english

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Mon Jun 30, 2014 4:24 am

Stop the off-topic please.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby anomaly » Fri Jul 04, 2014 8:50 am

There appears to be no license file in the tarball - are image builders able to redistribute these at all?
anomaly
 
Posts: 33
Joined: Fri Feb 21, 2014 6:01 pm
languages_spoken: english
ODROIDs: Odroid U3
Odroid XU4

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Fri Jul 04, 2014 8:57 am

I've updated OP with the EULA.
As long as you keep this only in use for Exynos 4412 SoC's sold by Hardkernel you are ok to re-distribute.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby anomaly » Fri Jul 04, 2014 11:47 am

Thanks!
anomaly
 
Posts: 33
Joined: Fri Feb 21, 2014 6:01 pm
languages_spoken: english
ODROIDs: Odroid U3
Odroid XU4

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby OverSun » Fri Jul 11, 2014 10:39 pm

Long story short, there was a driver called s5p-tv before, under V4L2 interfaces in kernel, and HDMI under that driver section was used for video output. It is not used anymore and cannot be even compiled because it depends on UMP. But there is also "mixer and videoprocessor" driver there as well in which I'm interested, but cannot enable it because of that movement to armsoc. Is it possible to tie the videoprocessor to new driver, since at least CEC was moved from under s5p-tv to the new driver successfully?
User avatar
OverSun
 
Posts: 1377
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Sat Jul 12, 2014 1:43 am

VP is being used on ARMSOC/ExynosDRM combo its part of the path in the HDMI Block :)

VP/Mixer/PHY/HDMI are all part of the same block that the video will follow inside the SoC.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby OverSun » Sat Jul 12, 2014 2:39 am

Don't see a device exported for v4l2 then... Cannot use it. =(
User avatar
OverSun
 
Posts: 1377
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby OverSun » Mon Jul 14, 2014 8:52 pm

Once more, anyone know how to use exynos-mixer on current drivers to feed it NV12MT picture? Previously it was V4l2 devices and I was able to draw directly on screen without X11 as described here: http://lwn.net/Articles/449661/
I have an idea now that can speed up XBMC expirience drastically on U2/U3, nut I need a way to work with mixer.
As i see in current exynos-mixer implementation there are no v4l2 calls at all, so I assume it doesn't export anything. But there should be another way to work with it. Anyone know how?
User avatar
OverSun
 
Posts: 1377
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Mon Jul 14, 2014 10:56 pm

There's no more direct access to the mixer anymore.
In fact the block that does take the NV12/NV12MT picture is the VP (but it only exists on Exynos4 series).
And I as recall we didn't had direct access to the VP on the s5p-tv driver.. or do we had?
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby OverSun » Tue Jul 15, 2014 12:24 am

Yes we did. I was streaming directly to screen without any X11 running or any drivers via s5p-tv (or s5p-mixer) device exported as V4l2 /dev/video0. And the device was accepting NV12MT without any issues. In fact it has been just the same device as MFC or FIMC, receiving a frame on input and showing it on the screen.
Even with X11 running I could show then a video overlay on top of it.
I dumped the idea to use it as a video output since I thought that time that XBMC controls will not be visible under the video and nobody gonna like it, but lately LiquidAcid give the idea that layers can be arranged intensionally. And as I recall there is a way in XBMC to make a hole in video interface and show all underlay layers. So I thought to try make XBMC and X11 top layer and show video under it. If XBMC would hole background right, I hoped to see the video under and the interface on top of it, when called. That would actually make huge jump in terms of FPS since no EGL would be involved at all in drawing a clip.
But then I found out that new exynos-drm doesn't export itself as V4l2 device and I cannot use it as I did before.
So my thought is if that was possible before, there should be a path to use it other way than V4l2, as I understand V4l2 was just another framework added. So any example on how to draw on screen using exynos-drm would do to make my tests.
User avatar
OverSun
 
Posts: 1377
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby OverSun » Tue Jul 15, 2014 5:05 pm

I've found some drm examples and was able to draw on screen directly without using X, but looks like as you said unfortunately the mixer is not available anymore as it was as V4L2 device. =( Once I start X11, there is no way of opening drm device anymore and I cannot use it. So it looks like if there will be no access to mixer it is a no go once more, since XBMC requires EGL to show interface and this is possible only under X11 for now.
Maybe if I would be that curious I'll revert everything to previous s5p-tv driver, kernel, libraries, and try it back there when mixing was possible, but I'm not sure about that, too much effort in obsolete things.

So long story short, anybody has any good examples of using exynos-mixer on exynos-drm to draw several layers on screen at once?
User avatar
OverSun
 
Posts: 1377
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby Legath » Tue Jul 22, 2014 8:26 pm

Which minimal Xserver xorg version we should use? i try to build armsoc driver inside buildroot environment and i have autogen error

configure.ac:40: error: must install xorg-macros 1.4 or later before running autoconf/autogen
configure.ac:40: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: autom4te failed with exit status: 1
./configure --enable-maintainer-mode
autogen.sh: 27: autogen.sh: ./configure: not found
configure failed
Legath
 
Posts: 26
Joined: Tue Nov 12, 2013 2:50 pm
languages_spoken: english, russian, chinese
ODROIDs: X2,U3

Re: [REFERENCE] Mali r4p0 for Image builders

Unread postby mdrjr » Tue Jul 22, 2014 10:19 pm

This is not the place to ask for help.
You are missing dependencies to build it...
Check your distro to whatever contains it.
Read the first error line.
mdrjr
Site Admin
 
Posts: 11690
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Next

Return to Ubuntu (All Linux'es)

Who is online

Users browsing this forum: No registered users and 2 guests