linux-sunxi / meta-sunxi Goto Github PK

This project forked from ebutera/meta-sunxi

Official sunxi OpenEmbedded layer for Allwinner-based boards.

License: MIT License

BitBake 35.39% Batchfile 1.52% C 63.09%

meta-sunxi's Introduction

	Linux kernel release 3.x <http://kernel.org/>

These are the release notes for Linux version 3.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong. 

WHAT IS LINUX?

  Linux is a clone of the operating system Unix, written from scratch by
  Linus Torvalds with assistance from a loosely-knit team of hackers across
  the Net. It aims towards POSIX and Single UNIX Specification compliance.

  It has all the features you would expect in a modern fully-fledged Unix,
  including true multitasking, virtual memory, shared libraries, demand
  loading, shared copy-on-write executables, proper memory management,
  and multistack networking including IPv4 and IPv6.

  It is distributed under the GNU General Public License - see the
  accompanying COPYING file for more details. 

ON WHAT HARDWARE DOES IT RUN?

  Although originally developed first for 32-bit x86-based PCs (386 or higher),
  today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
  UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
  IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
  Xtensa, Tilera TILE, AVR32 and Renesas M32R architectures.

  Linux is easily portable to most general-purpose 32- or 64-bit architectures
  as long as they have a paged memory management unit (PMMU) and a port of the
  GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
  also been ported to a number of architectures without a PMMU, although
  functionality is then obviously somewhat limited.
  Linux has also been ported to itself. You can now run the kernel as a
  userspace application - this is called UserMode Linux (UML).

DOCUMENTATION:

 - There is a lot of documentation available both in electronic form on
   the Internet and in books, both Linux-specific and pertaining to
   general UNIX questions.  I'd recommend looking into the documentation
   subdirectories on any Linux FTP site for the LDP (Linux Documentation
   Project) books.  This README is not meant to be documentation on the
   system: there are much better sources available.

 - There are various README files in the Documentation/ subdirectory:
   these typically contain kernel-specific installation notes for some 
   drivers for example. See Documentation/00-INDEX for a list of what
   is contained in each file.  Please read the Changes file, as it
   contains information about the problems, which may result by upgrading
   your kernel.

 - The Documentation/DocBook/ subdirectory contains several guides for
   kernel developers and users.  These guides can be rendered in a
   number of formats:  PostScript (.ps), PDF, HTML, & man-pages, among others.
   After installation, "make psdocs", "make pdfdocs", "make htmldocs",
   or "make mandocs" will render the documentation in the requested format.

INSTALLING the kernel source:

 - If you install the full sources, put the kernel tarball in a
   directory where you have permissions (eg. your home directory) and
   unpack it:

		gzip -cd linux-3.X.tar.gz | tar xvf -

   or
		bzip2 -dc linux-3.X.tar.bz2 | tar xvf -


   Replace "XX" with the version number of the latest kernel.

   Do NOT use the /usr/src/linux area! This area has a (usually
   incomplete) set of kernel headers that are used by the library header
   files.  They should match the library, and not get messed up by
   whatever the kernel-du-jour happens to be.

 - You can also upgrade between 3.x releases by patching.  Patches are
   distributed in the traditional gzip and the newer bzip2 format.  To
   install by patching, get all the newer patch files, enter the
   top level directory of the kernel source (linux-3.x) and execute:

		gzip -cd ../patch-3.x.gz | patch -p1

   or
		bzip2 -dc ../patch-3.x.bz2 | patch -p1

   (repeat xx for all versions bigger than the version of your current
   source tree, _in_order_) and you should be ok.  You may want to remove
   the backup files (xxx~ or xxx.orig), and make sure that there are no
   failed patches (xxx# or xxx.rej). If there are, either you or me has
   made a mistake.

   Unlike patches for the 3.x kernels, patches for the 3.x.y kernels
   (also known as the -stable kernels) are not incremental but instead apply
   directly to the base 3.x kernel.  Please read
   Documentation/applying-patches.txt for more information.

   Alternatively, the script patch-kernel can be used to automate this
   process.  It determines the current kernel version and applies any
   patches found.

		linux/scripts/patch-kernel linux

   The first argument in the command above is the location of the
   kernel source.  Patches are applied from the current directory, but
   an alternative directory can be specified as the second argument.

 - If you are upgrading between releases using the stable series patches
   (for example, patch-3.x.y), note that these "dot-releases" are
   not incremental and must be applied to the 3.x base tree. For
   example, if your base kernel is 3.0 and you want to apply the
   3.0.3 patch, you do not and indeed must not first apply the
   3.0.1 and 3.0.2 patches. Similarly, if you are running kernel
   version 3.0.2 and want to jump to 3.0.3, you must first
   reverse the 3.0.2 patch (that is, patch -R) _before_ applying
   the 3.0.3 patch.
   You can read more on this in Documentation/applying-patches.txt

 - Make sure you have no stale .o files and dependencies lying around:

		cd linux
		make mrproper

   You should now have the sources correctly installed.

SOFTWARE REQUIREMENTS

   Compiling and running the 3.x kernels requires up-to-date
   versions of various software packages.  Consult
   Documentation/Changes for the minimum version numbers required
   and how to get updates for these packages.  Beware that using
   excessively old versions of these packages can cause indirect
   errors that are very difficult to track down, so don't assume that
   you can just update packages when obvious problems arise during
   build or operation.

BUILD directory for the kernel:

   When compiling the kernel all output files will per default be
   stored together with the kernel source code.
   Using the option "make O=output/dir" allow you to specify an alternate
   place for the output files (including .config).
   Example:
     kernel source code:	/usr/src/linux-3.N
     build directory:		/home/name/build/kernel

   To configure and build the kernel use:
   cd /usr/src/linux-3.N
   make O=/home/name/build/kernel menuconfig
   make O=/home/name/build/kernel
   sudo make O=/home/name/build/kernel modules_install install

   Please note: If the 'O=output/dir' option is used then it must be
   used for all invocations of make.

CONFIGURING the kernel:

   Do not skip this step even if you are only upgrading one minor
   version.  New configuration options are added in each release, and
   odd problems will turn up if the configuration files are not set up
   as expected.  If you want to carry your existing configuration to a
   new version with minimal work, use "make oldconfig", which will
   only ask you for the answers to new questions.

 - Alternate configuration commands are:
	"make config"      Plain text interface.
	"make menuconfig"  Text based color menus, radiolists & dialogs.
	"make nconfig"     Enhanced text based color menus.
	"make xconfig"     X windows (Qt) based configuration tool.
	"make gconfig"     X windows (Gtk) based configuration tool.
	"make oldconfig"   Default all questions based on the contents of
			   your existing ./.config file and asking about
			   new config symbols.
	"make silentoldconfig"
			   Like above, but avoids cluttering the screen
			   with questions already answered.
			   Additionally updates the dependencies.
	"make defconfig"   Create a ./.config file by using the default
			   symbol values from either arch/$ARCH/defconfig
			   or arch/$ARCH/configs/${PLATFORM}_defconfig,
			   depending on the architecture.
	"make ${PLATFORM}_defconfig"
			  Create a ./.config file by using the default
			  symbol values from
			  arch/$ARCH/configs/${PLATFORM}_defconfig.
			  Use "make help" to get a list of all available
			  platforms of your architecture.
	"make allyesconfig"
			   Create a ./.config file by setting symbol
			   values to 'y' as much as possible.
	"make allmodconfig"
			   Create a ./.config file by setting symbol
			   values to 'm' as much as possible.
	"make allnoconfig" Create a ./.config file by setting symbol
			   values to 'n' as much as possible.
	"make randconfig"  Create a ./.config file by setting symbol
			   values to random values.

   You can find more information on using the Linux kernel config tools
   in Documentation/kbuild/kconfig.txt.

	NOTES on "make config":
	- having unnecessary drivers will make the kernel bigger, and can
	  under some circumstances lead to problems: probing for a
	  nonexistent controller card may confuse your other controllers
	- compiling the kernel with "Processor type" set higher than 386
	  will result in a kernel that does NOT work on a 386.  The
	  kernel will detect this on bootup, and give up.
	- A kernel with math-emulation compiled in will still use the
	  coprocessor if one is present: the math emulation will just
	  never get used in that case.  The kernel will be slightly larger,
	  but will work on different machines regardless of whether they
	  have a math coprocessor or not. 
	- the "kernel hacking" configuration details usually result in a
	  bigger or slower kernel (or both), and can even make the kernel
	  less stable by configuring some routines to actively try to
	  break bad code to find kernel problems (kmalloc()).  Thus you
	  should probably answer 'n' to the questions for
          "development", "experimental", or "debugging" features.

COMPILING the kernel:

 - Make sure you have at least gcc 3.2 available.
   For more information, refer to Documentation/Changes.

   Please note that you can still run a.out user programs with this kernel.

 - Do a "make" to create a compressed kernel image. It is also
   possible to do "make install" if you have lilo installed to suit the
   kernel makefiles, but you may want to check your particular lilo setup first.

   To do the actual install you have to be root, but none of the normal
   build should require that. Don't take the name of root in vain.

 - If you configured any of the parts of the kernel as `modules', you
   will also have to do "make modules_install".

 - Verbose kernel compile/build output:

   Normally the kernel build system runs in a fairly quiet mode (but not
   totally silent).  However, sometimes you or other kernel developers need
   to see compile, link, or other commands exactly as they are executed.
   For this, use "verbose" build mode.  This is done by inserting
   "V=1" in the "make" command.  E.g.:

	make V=1 all

   To have the build system also tell the reason for the rebuild of each
   target, use "V=2".  The default is "V=0".

 - Keep a backup kernel handy in case something goes wrong.  This is 
   especially true for the development releases, since each new release
   contains new code which has not been debugged.  Make sure you keep a
   backup of the modules corresponding to that kernel, as well.  If you
   are installing a new kernel with the same version number as your
   working kernel, make a backup of your modules directory before you
   do a "make modules_install".
   Alternatively, before compiling, use the kernel config option
   "LOCALVERSION" to append a unique suffix to the regular kernel version.
   LOCALVERSION can be set in the "General Setup" menu.

 - In order to boot your new kernel, you'll need to copy the kernel
   image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
   to the place where your regular bootable kernel is found. 

 - Booting a kernel directly from a floppy without the assistance of a
   bootloader such as LILO, is no longer supported.

   If you boot Linux from the hard drive, chances are you use LILO which
   uses the kernel image as specified in the file /etc/lilo.conf.  The
   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
   /boot/bzImage.  To use the new kernel, save a copy of the old image
   and copy the new image over the old one.  Then, you MUST RERUN LILO
   to update the loading map!! If you don't, you won't be able to boot
   the new kernel image.

   Reinstalling LILO is usually a matter of running /sbin/lilo. 
   You may wish to edit /etc/lilo.conf to specify an entry for your
   old kernel image (say, /vmlinux.old) in case the new one does not
   work.  See the LILO docs for more information. 

   After reinstalling LILO, you should be all set.  Shutdown the system,
   reboot, and enjoy!

   If you ever need to change the default root device, video mode,
   ramdisk size, etc.  in the kernel image, use the 'rdev' program (or
   alternatively the LILO boot options when appropriate).  No need to
   recompile the kernel to change these parameters. 

 - Reboot with the new kernel and enjoy. 

IF SOMETHING GOES WRONG:

 - If you have problems that seem to be due to kernel bugs, please check
   the file MAINTAINERS to see if there is a particular person associated
   with the part of the kernel that you are having trouble with. If there
   isn't anyone listed there, then the second best thing is to mail
   them to me ([email protected]), and possibly to any other
   relevant mailing-list or to the newsgroup.

 - In all bug-reports, *please* tell what kernel you are talking about,
   how to duplicate the problem, and what your setup is (use your common
   sense).  If the problem is new, tell me so, and if the problem is
   old, please try to tell me when you first noticed it.

 - If the bug results in a message like

	unable to handle kernel paging request at address C0000010
	Oops: 0002
	EIP:   0010:XXXXXXXX
	eax: xxxxxxxx   ebx: xxxxxxxx   ecx: xxxxxxxx   edx: xxxxxxxx
	esi: xxxxxxxx   edi: xxxxxxxx   ebp: xxxxxxxx
	ds: xxxx  es: xxxx  fs: xxxx  gs: xxxx
	Pid: xx, process nr: xx
	xx xx xx xx xx xx xx xx xx xx

   or similar kernel debugging information on your screen or in your
   system log, please duplicate it *exactly*.  The dump may look
   incomprehensible to you, but it does contain information that may
   help debugging the problem.  The text above the dump is also
   important: it tells something about why the kernel dumped code (in
   the above example it's due to a bad kernel pointer). More information
   on making sense of the dump is in Documentation/oops-tracing.txt

 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
   as is, otherwise you will have to use the "ksymoops" program to make
   sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
   This utility can be downloaded from
   ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
   Alternately you can do the dump lookup by hand:

 - In debugging dumps like the above, it helps enormously if you can
   look up what the EIP value means.  The hex value as such doesn't help
   me or anybody else very much: it will depend on your particular
   kernel setup.  What you should do is take the hex value from the EIP
   line (ignore the "0010:"), and look it up in the kernel namelist to
   see which kernel function contains the offending address.

   To find out the kernel function name, you'll need to find the system
   binary associated with the kernel that exhibited the symptom.  This is
   the file 'linux/vmlinux'.  To extract the namelist and match it against
   the EIP from the kernel crash, do:

		nm vmlinux | sort | less

   This will give you a list of kernel addresses sorted in ascending
   order, from which it is simple to find the function that contains the
   offending address.  Note that the address given by the kernel
   debugging messages will not necessarily match exactly with the
   function addresses (in fact, that is very unlikely), so you can't
   just 'grep' the list: the list will, however, give you the starting
   point of each kernel function, so by looking for the function that
   has a starting address lower than the one you are searching for but
   is followed by a function with a higher address you will find the one
   you want.  In fact, it may be a good idea to include a bit of
   "context" in your problem report, giving a few lines around the
   interesting one. 

   If you for some reason cannot do the above (you have a pre-compiled
   kernel image or similar), telling me as much about your setup as
   possible will help.  Please read the REPORTING-BUGS document for details.

 - Alternately, you can use gdb on a running kernel. (read-only; i.e. you
   cannot change values or set break points.) To do this, first compile the
   kernel with -g; edit arch/i386/Makefile appropriately, then do a "make
   clean". You'll also need to enable CONFIG_PROC_FS (via "make config").

   After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
   You can now use all the usual gdb commands. The command to look up the
   point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes
   with the EIP value.)

   gdb'ing a non-running kernel currently fails because gdb (wrongly)
   disregards the starting offset for which the kernel is compiled.

meta-sunxi's People

Contributors

Stargazers

Watchers

Forkers

vonfritz aapash kristofrobot raoulh chenbd rehivetech koenkooi guessyet peolsson dtrimaille saskatoontechworks grilledcheesesandwich xleng rorei dnmeid dannygto net147 lukas2511 vishnupatekar sebastianwendel mixtile webin xxl007 mcherifioss whirm jlucius solderzzc soderstrom-rikard rofehr twoerner embedlynx bladegroup tizenteam liuxincheng tylerwhall bojczmac stephanroslen prajoshpremdas gizero jhedev zzeroo pemdp linhdnguyen likewise jamespettigrew xpete amirhammad anr2me rahul012345 kynetics scrawford916 fdlg shaunmulligan icgilca hunterhu elecboy ad-aleksandrov nickbetteridge kgolding nandra anguslees madscientist42 xevoinc maxpayne86 niurenyige leon-anavi zavorka thewhoo dronsv hitech95 13824125580 mirzak 3mdeb neutis hwuethrich macpijan floion nhewitt1 hizukiayaka stephensorriaux aragua konsulko mwohlert mdevries86 ganeshhalthota lycheepi hvraven fefr chinhpc voloviq bpi-sinovoip egladman cz7asm stefanofiorentino kedder colrack chavdar75 saycv gagath madivak

meta-sunxi's Issues

Support for orange-pi-zero

The orange-pi-zero board (H2+) is not yet supported.

With the orange-pi-one conf, the board can't boot.
Did you plan to support this board ?

meta-sunxi / recipes-graphics / libgles / sunxi-mali_git.bb SRC_URI="gitsm://???

The protocol gitsm does not seem to work
SRC_URI = "gitsm://github.com/linux-sunxi/sunxi-mali.git"
i replaced it by the protocol git and now it works
SRC_URI = "git://github.com/linux-sunxi/sunxi-mali.git"
could you explain me what is the different between gitsm and git ?
Thank you !

libdri2: missing dri2proto dependency

I got following error when building libdri2:

DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 4
make  all-recursive
make[1]: Entering directory `/home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/libdri2/git-2/git'
Making all in src
make[2]: Entering directory `/home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/libdri2/git-2/git/src'
../arm-oe-linux-gnueabi-libtool  --tag=CC   --mode=compile arm-oe-linux-gnueabi-gcc  -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 --sysroot=/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2 -std=gnu99 -DHAVE_CONFIG_H -I. -I..    -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -I/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2/usr/include/libdrm  -I../include -DMALLOC_0_RETURNS_NULL -O2 -pipe -g -feliminate-unused-debug-types -c -o dri2.lo dri2.c
arm-oe-linux-gnueabi-libtool: compile:  arm-oe-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 --sysroot=/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2 -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -I/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2/usr/include/libdrm -I../include -DMALLOC_0_RETURNS_NULL -O2 -pipe -g -feliminate-unused-debug-types -c dri2.c  -fPIC -DPIC -o .libs/dri2.o
dri2.c:43:38: fatal error: X11/extensions/dri2proto.h: No such file or directory
 #include <X11/extensions/dri2proto.h>
                                      ^
compilation terminated.
make[2]: *** [dri2.lo] Error 1
make[2]: Leaving directory `/home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/libdri2/git-2/git/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/libdri2/git-2/git'
make: *** [all] Error 2
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_compile (log file is located at /home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/libdri2/git-2/temp/log.do_compile.23784)

This seems a missing dependency in libdri2_git.bb - adding dri2proto fixes this:

DEPENDS = "dri2proto libdrm libxext xextproto libxfixes"

I'll launch a pull request that fixes this later, but wanted to document this already.

Again 'oldconfig' trouble

Hello.
I have trouble (#79) when i try build system for my cubie 1.

local.conf

BB_NUMBER_THREADS ?= "2"
PARALLEL_MAKE ?= "-j 2"
MACHINE ?= "cubieboard"

bblayers.conf

LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/bai/embedded/poky/meta \
  /home/bai/embedded/poky/meta-yocto \
  /home/bai/embedded/poky/meta-yocto-bsp \
  /home/bai/embedded/poky/meta-sunxi \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /home/bai/embedded/poky/meta \
  /home/bai/embedded/poky/meta-yocto \
  "

Truble:

bai@ubuntu-cons:~/embedded/poky/cubieboard$ bitbake core-image-minimal
Loading cache: 100% |##################################################################################################################| ETA:  00:00:00
Loaded 1301 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.26.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "cubieboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.8"
TUNE_FEATURES     = "arm armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp    = "fido:08f9fbbc97909698b56200aa9be5fe50b99a44b2"
meta-sunxi        = "master:9ac263ebab41ea5229d4c74ff837ae6a623536b9"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_configure (log file is located at /home/bai/embedded/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/4.1.3-r0/temp/log.do_configure.20650)
ERROR: Logfile of failure stored in: /home/bai/embedded/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/4.1.3-r0/temp/log.do_configure.20650
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make -C /home/bai/embedded/poky/cubieboard/tmp/work-shared/cubieboard/kernel-source O=/home/bai/embedded/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/4.1.3-r0/build oldconfig
| make: Entering directory `/home/bai/embedded/poky/cubieboard/tmp/work-shared/cubieboard/kernel-source'
| make: *** No rule to make target `oldconfig'.  Stop.
| make: Leaving directory `/home/bai/embedded/poky/cubieboard/tmp/work-shared/cubieboard/kernel-source'
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/bai/embedded/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/4.1.3-r0/temp/log.do_configure.20650)
ERROR: Task 74 (/home/bai/embedded/poky/meta-sunxi/recipes-kernel/linux/linux_4.1.3.bb, do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1035 tasks of which 1033 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /home/bai/embedded/poky/meta-sunxi/recipes-kernel/linux/linux_4.1.3.bb, do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Folder "/home/bai/embedded/poky/cubieboard/tmp/work-shared/cubieboard/kernel-source" is empty.
Kernel folder isn't empty:

bai@ubuntu-cons:~/embedded/poky/cubieboard$ ls -la /home/bai/embedded/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/4.1.3-r0/
total 40
drwxrwxr-x  5 bai bai  4096 Aug 14 16:49 .
drwxrwxr-x  3 bai bai  4096 Aug 14 16:47 ..
drwxr-xr-x  2 bai bai  4096 Aug 14 17:07 build
-rw-r--r--  1 bai bai 17866 Aug 14 16:49 defconfig
drwxr-xr-x 23 bai bai  4096 Jul 21 20:10 linux-4.1.3
drwxrwxr-x  2 bai bai  4096 Aug 14 18:16 temp

Folder "/home/bai/embedded/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/4.1.3-r0/build" contain ".config".
File "linux.inc" same as in meta-oe.

cubieboard2 - core-image-base generates corrupt SD image

Hi,

I upgraded my openembedded-core, bitbake, meta-openembedded and meta-sunxi repositories, and now I am unable to build a valid SD image for cubieboard2.

I should point out that it has been a few weeks since I last generated an SD image - so I dont know when exactly this broke.

Also note that I get this even when starting from a fresh build directory.

This is my build configuration:

kristof@test:~/OE/build$ bitbake core-image-base
Loading cache: 100% |###########################################| ETA:  00:00:00
Loaded 1792 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 3.4.61 of linux-libc-headers not available (for item linux-libc-headers)
NOTE: versions of linux-libc-headers available: 3.10
NOTE: preferred version 3.4.61 of linux-libc-headers not available (for item linux-libc-headers-dev)
NOTE: versions of linux-libc-headers available: 3.10

Build Configuration:
BB_VERSION        = "1.21.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-13.10"
TARGET_SYS        = "arm-oe-linux-gnueabi"
MACHINE           = "cubieboard2"
DISTRO            = "nodistro"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta              = "master:82c773e88aaefd9321481ad297554d5b4a3ae0b2"
meta-oe           
meta-networking   = "master:56dde5189f20d3507cad39814b833be7626067a4"
meta-sunxi        = "master:1ebcb0778fade0175f18a2780e8f355f8dca8139"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 1956 tasks of which 1956 didn't need to be rerun and all succeeded.

That seems to work fine, however, when I try to boot the image, I get a kernel panic.

Moreover, if I mount the generated SD image system, I see that it indeed seems corrupted:

kristof@test:~/OE/images$ sudo kpartx -a -v core-image-base-cubieboard2.sunxi-sdimg
add map loop0p1 (252:0): 0 40960 linear /dev/loop0 4096
add map loop0p2 (252:1): 0 208896 linear /dev/loop0 45056
kristof@test:~/OE/images$ sudo mount /dev/mapper/loop0p2 /mnt 
kristof@test:~/OE/images$ ls /mnt
bin  boot  dev  lib  lost+found  media  mnt  proc  tmp  usr  var
kristof@test:~/OE/images$ sudo umount /mnt
kristof@test:~/OE/images$ sudo mount /dev/mapper/loop0p1 /mnt
kristof@test:~/OE/images$ ls /mnt
image-version-info  script.bin  uImage

As you can see, the /etc, /home, /run, /sbin and sys directories are missing.

This is strange, as they are present in the *.ext file:

kristof@test:~/OE/images$ sudo mount -o loop core-image-base-cubieboard2.ext3 /mnt
kristof@test:~/OE/images$ ls /mnt
bin  boot  dev  etc  home  lib  lost+found  media  mnt  proc  run  sbin  sys  tmp  usr  var

and also the *.tar.gz seems fine:

kristof@test:~/OE/images$ tar -ztf core-image-base-cubieboard2.tar.gz 
./
./boot/
./boot/uImage
./boot/uImage-3.4.79
./mnt/
./mnt/.psplash/
[...]
./etc/rc2.d/S01networking
./etc/rc2.d/S20hwclock.sh
./etc/rc2.d/S64neard
./etc/rc2.d/S02dbus-1
./etc/rc2.d/S99stop-bootlogd
./etc/rc2.d/S15mountnfs.sh
./etc/rc2.d/S20apmd
./etc/rc2.d/S99rmnologin.sh
./run/
./sys/

Any idea what could be wrong? Or how I could further debug this?
Can others reproduce this issue?

Thanks!

Kristof

Migrate to Yocto Linux Kernel

I think it would be a good idea to migrate to using Yocto Linux Kernel recipes - to avoid issues like #79

See http://www.yoctoproject.org/docs/1.7.1/kernel-dev/kernel-dev.html:

The Yocto Project also provides a powerful set of kernel tools for managing Linux kernel sources and configuration data. You can use these tools to make a single configuration change, apply multiple patches, or work with your own kernel sources. [...]

If you do not maintain your own kernel sources and need to make only minimal changes to the sources, the released recipes provide a vetted base upon which to layer your changes. Doing so allows you to benefit from the continual kernel integration and testing performed during development of the Yocto Project.

I think meta-sunxi is in this case?

If, instead, you have a very specific Linux kernel source tree and are unable to align with one of the official linux-yocto recipes, an alternative exists by which you can use the Yocto Project Linux kernel tools with your own kernel sources.

Or are we in this case?

mali driver x11 problem

Hi,
I try to build an image for bananaPro withot x11 and wayland support.But I get following error during mali test binary compilation

make: Leaving directory '/home/yusuf/yocto/poky/bananaProHf/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git/include'
make -C test test
make[1]: Entering directory '/home/yusuf/yocto/poky/bananaProHf/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git/test'
arm-poky-linux-gnueabi-gcc -march=armv7-a -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 --sysroot=/home/yusuf/yocto/poky/bananaProHf/tmp/sysroots/bananapro -O2 -pipe -g -feliminate-unused-debug-types -I../include -L../../image/usr/lib -o test test.c -lEGL -lGLESv2 -lX11
In file included from ../include/EGL/egl.h:36:0,
from test.c:32:
../include/EGL/eglplatform.h:89:22: fatal error: X11/Xlib.h: No such file or directory
compilation terminated.
Makefile:8: recipe for target 'test' failed

When I view 0001-fix-test-build.patch file,I see following lines

test: ../config.mk test.c

-$(CC) $(CFLAGS) -o $@ test.c -lEGL -lGLESv2

+$(CC) $(CFLAGS) -I../include -L../../image/usr/lib -o $@ test.c -lEGL -lGLESv2 -lX11

Since the image doesn't support X11, I assumed the X11 libraries shouldn't be included. Isn't that true?
How can I solve this problem?

Linux: very slow fetching of mainline kernel - migrate from git to tar.xz?

I am encountering very slow fetch times of the mainline kernel from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git (see https://github.com/linux-sunxi/meta-sunxi/blob/master/recipes-kernel/linux/linux_4.1.bb)

Is there any reason we don't just fetch the compressed tar.xz package from https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.1.2.tar.xz? That seems to be a lot faster in my case.

dtb file is missing from sdimage

test with cubietruck, core-image-base, build without any problem. but after flash the sdimage to sdcard and try to boot, the image can't boot, and seems the dtb file is missing from boot dir.
after manually copy uImage-sun7i-a20-cubietruck.dtb to boot dir and named sun7i-a20-cubietruck.dtb, the image can boot now.
i also checked core-image-base-cubietruck-20160607130700.rootfs.tar.gz and boot dir contains the dtb file

pyA20 recipe is not working

I get this error when i try to create an image with pyA20 on krogoth branch.
Tested with olinuxino_a20 and olinuxino_a20som.

ERROR: image-1.0-r3 do_rootfs: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:

File: 'exec_python_func() autogenerated', lineno: 2, function:
0001:
*** 0002:license_create_manifest(d)
0003:
File: '/home/username/Projects/build/../poky/meta/classes/license.bbclass', lineno: 48, function: license_create_manifest
0044: pkg_dic = {}
0045: for pkg in sorted(image_list_installed_packages(d)):
0046: pkg_info = os.path.join(d.getVar('PKGDATA_DIR', True),
0047: 'runtime-reverse', pkg)
*** 0048: pkg_name = os.path.basename(os.readlink(pkg_info))
0049:
0050: pkg_dic[pkg_name] = oe.packagedata.read_pkgdatafile(pkg_info)
0051: if not "LICENSE" in pkg_dic[pkg_name].keys():
0052: pkg_lic_name = "LICENSE_" + pkg_name
Exception: OSError: [Errno 2] No such file or directory: '/home/username/Projects/build/tmp/sysroots/olinuxino-a20som/pkgdata/runtime-reverse/pya20'

ERROR: image-1.0-r3 do_rootfs: Function failed: license_create_manifest
ERROR: Logfile of failure stored in: /home/username/Projects/build/tmp/work/olinuxino_a20som-poky-linux-gnueabi/image/1.0-r3/temp/log.do_rootfs.16867
ERROR: Task 9 (/home/username/Projects/build/../meta-private/recipes-private/images/image.bb, do_rootfs) failed with exit code '1'

No recipes available for /poky/meta-sunxi/recipes-graphics/tslib/tslib_1.1.bbappend

What does this mean?I'm using poky-morty.
Any help?

Cannot build system for cubieboard at yocto

I tried build the system for cubieboard in yocto system. But I did not succeed.
I described my troubles in google groups: https://groups.google.com/forum/#!category-topic/cubieboard/other/EI5sV6_gaj0
Steps for reproduce.

Downolad yocto

bai@lin-o-book:/_DATA/_embedded/yocto$ pwd
/_DATA/_embedded/yocto
bai@lin-o-book:/_DATA/_embedded/yocto$ git clone git://git.yoctoproject.org/poky
Cloning into 'poky'...
remote: Counting objects: 216222, done.
remote: Compressing objects: 100% (54509/54509), done.
remote: Total 216222 (delta 157393), reused 215669 (delta 156845)
Receiving objects: 100% (216222/216222), 98.24 MiB | 87.00 KiB/s, done.
Resolving deltas: 100% (157393/157393), done.
Checking connectivity... done
bai@lin-o-book:/_DATA/_embedded/yocto$

Download meta-sunxi

bai@lin-o-book:/_DATA/_embedded/yocto/poky$ git clone https://github.com/linux-sunxi/meta-sunxi.git
Cloning into 'meta-sunxi'...
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
remote: Counting objects: 739, done.
remote: Compressing objects: 100% (414/414), done.
remote: Total 739 (delta 249), reused 690 (delta 218)
Receiving objects: 100% (739/739), 347.56 KiB | 192.00 KiB/s, done.
Resolving deltas: 100% (249/249), done.
Checking connectivity... done
bai@lin-o-book:/_DATA/_embedded/yocto/poky$

Source create

bai@lin-o-book:/_DATA/_embedded/yocto/poky$ source oe-init-build-env cubieboard
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to use a 
different MACHINE (target hardware) or enable parallel build options to take 
advantage of multiple cores for example. See the file for more information as 
common configuration options are commented.

The Yocto Project has extensive documentation about OE including a reference manual
which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/

You had no conf/bblayers.conf file. The configuration file has been created for
you with some default values. To add additional metadata layers into your
configuration please add entries to this file.

The Yocto Project has extensive documentation about OE including a reference manual
which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/



### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    adt-installer
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
bai@lin-o-book:/_DATA/_embedded/yocto/poky/cubieboard$

Edit conf/local.conf

BB_NUMBER_THREADS ?= "4"
PARALLEL_MAKE ?= "-j 4"
MACHINE ?= "cubieboard"

Edit conf/bblayers.conf

BBLAYERS ?= " \
  /_DATA/_embedded/yocto/poky/meta \
  /_DATA/_embedded/yocto/poky/meta-yocto \
  /_DATA/_embedded/yocto/poky/meta-yocto-bsp \
  /_DATA/_embedded/yocto/poky/meta-sunxi \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /_DATA/_embedded/yocto/poky/meta \
  /_DATA/_embedded/yocto/poky/meta-yocto \
  /_DATA/_embedded/yocto/poky/meta-sunxi \
  "

Run bitbake (Becouse Tested with core-image-base. I tried in this case.)

bai@lin-o-book:/_DATA/_embedded/yocto/poky/cubieboard$ bitbake core-image-base
Parsing recipes: 100% |#########################################################################################################################################################| Time: 00:00:59
Parsing of 862 .bb files complete (0 cached, 862 parsed). 1215 targets, 55 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 3.4.61 of linux-libc-headers not available (for item linux-libc-headers)
NOTE: versions of linux-libc-headers available: 3.10
NOTE: preferred version 3.4.61 of linux-libc-headers not available (for item linux-libc-headers-dev)
NOTE: versions of linux-libc-headers available: 3.10

Build Configuration:
BB_VERSION        = "1.21.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-13.10"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "cubieboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.5+snapshot-20131222"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta              
meta-yocto        
meta-yocto-bsp    = "master:85ac39431a549e0e6a94aa8cba6e8428a8a8758d"
meta-sunxi        = "master:92d1408c46c50563246a642f8d7b0b4edba77e64"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks

Error?

WARNING: Failed to fetch URL ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://sources.redhat.com/pub/docbook-tools/new-trials/SOURCES/docbook-utils-0.6.14.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL http://pkg-shadow.alioth.debian.org/releases/shadow-4.1.4.3.tar.bz2, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.uni-erlangen.de/pub/Linux/LOCAL/dosfstools/dosfstools-2.11.src.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.debian.org/debian/pool/main/d/dpkg/dpkg_1.17.4.tar.xz, attempting MIRRORS if available
WARNING: QA Issue: sqlite3-native: configure was passed unrecognised options: --enable-tempstore
WARNING: QA Issue: python-native: configure was passed unrecognised options: --without-cxx --with-cyclic-gc
WARNING: QA Issue: dpkg-native: configure was passed unrecognised options: --with-bz2lib --with-start-stop-daemon --without-dselect --without-static-progs --without-sgml-doc
WARNING: QA Issue: libtool-cross: configure was passed unrecognised options: --with-sysroot
WARNING: QA Issue: alsa-lib: configure was passed unrecognised options: --with-cards --with-oss
WARNING: QA Issue: python: configure was passed unrecognised options: --without-cxx --with-cyclic-gc
WARNING: QA Issue: flac: configure was passed unrecognised options: --disable-id3libtest --without-id3lib
WARNING: QA Issue: bluez-hcidump: configure was passed unrecognised options: --with-bluez-includes --with-bluez-libs
ERROR: QA Issue: linux: Files/directories were installed but not shipped
  /usr/src/debug
  /usr/src/debug/linux
  /usr/src/debug/linux/3.4.67-14
  /usr/src/debug/linux/3.4.67-14/git
  /usr/src/debug/linux/3.4.67-14/git/include
  /usr/src/debug/linux/3.4.67-14/git/arch                                                                                                                                                       
  /usr/src/debug/linux/3.4.67-14/git/include/linux                                                                                                                                              
  /usr/src/debug/linux/3.4.67-14/git/include/asm-generic                                                                                                                                        
  /usr/src/debug/linux/3.4.67-14/git/include/linux/printk.h                                                                                                                                     
  /usr/src/debug/linux/3.4.67-14/git/include/linux/kernel.h                                                                                                                                     
  /usr/src/debug/linux/3.4.67-14/git/include/linux/power                                                                                                                                        
  /usr/src/debug/linux/3.4.67-14/git/include/linux/power/aw_pm.h                                                                                                                                
  /usr/src/debug/linux/3.4.67-14/git/include/asm-generic/int-ll64.h                                                                                                                             
  /usr/src/debug/linux/3.4.67-14/git/arch/arm                                                                                                                                                   
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun4i                                                                                                                                        
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/include                                                                                                                                           
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi                                                                                                                                        
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun4i/include                                                                                                                                
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun4i/include/mach                                                                                                                           
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun4i/include/mach/ccmu_regs.h                                                                                                               
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/include/asm                                                                                                                                       
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/include/asm/hwcap.h                                                                                                                               
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm                                                                                                                                     
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/include                                                                                                                                
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_ir.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_power.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_ir.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/dram_init.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_usb.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_tmr.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/dram.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_twi.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_int.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/common.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_clock.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_clock.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_power.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_key.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_int.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_usb.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_tmr.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_delay.S
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_i.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_key.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/stack.S
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/standby_twi.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/common.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/pm/standby/dram_i.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/include/plat
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/plat-sunxi/include/plat/dram.h
ERROR: QA Issue: No GNU_HASH in the elf binary: '/_DATA/_embedded/yocto/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/3.4.67-14/packages-split/kernel-dev/usr/src/kernel/modules/wifi/bcm40181/apps/epi_ttcp'
ERROR: QA Issue: No GNU_HASH in the elf binary: '/_DATA/_embedded/yocto/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/3.4.67-14/packages-split/kernel-dev/usr/src/kernel/modules/wifi/usi-bcm4329/v4.218.248.15/apps/epi_ttcp'
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /_DATA/_embedded/yocto/poky/cubieboard/tmp/work/cubieboard-poky-linux-gnueabi/linux/3.4.67-14/temp/log.do_package.32402
ERROR: Task 82 (/_DATA/_embedded/yocto/poky/meta-sunxi/recipes-kernel/linux/linux_3.4.bb, do_package) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2333 tasks of which 1367 didn't need to be rerun and 1 failed.
No currently running tasks (2333 of 2345)

Summary: 1 task failed:
  /_DATA/_embedded/yocto/poky/meta-sunxi/recipes-kernel/linux/linux_3.4.bb, do_package
Summary: There were 5 WARNING messages shown.
Summary: There were 5 ERROR messages shown, returning a non-zero exit code.
bai@lin-o-book:/_DATA/_embedded/yocto/poky/cubieboard$

What can i do?

Yocto Project 2.0 Jethro

Hi,

When do you plan to add a branch compatible with Yocto Project 2.0 Jethro?

Best regards, Leon

Cannot build with dizzy

Trying to use your layer with Yocto 1.7, default configuration, default image (core-image-sato), MACHINE= "olinuxino-a20".

Result: fails building libdri2.

I am almost sure that I succeeded when I tried a similar thing (for cubieboard) about one or two months ago, that must have been with Yocto 1.6.

Log:

| checking if arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/bspace/yocto/poky/build-a20/tmp/sysroots/olinuxino-a20 -std=gnu99 supports -Werror=address... yes
| checking if arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/bspace/yocto/poky/build-a20/tmp/sysroots/olinuxino-a20 -std=gnu99 supports -Werror=int-to-pointer-cast... yes
| checking if arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/bspace/yocto/poky/build-a20/tmp/sysroots/olinuxino-a20 -std=gnu99 supports -Werror=pointer-to-int-cast... yes
| checking if arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/bspace/yocto/poky/build-a20/tmp/sysroots/olinuxino-a20 -std=gnu99 supports -pedantic... yes
| checking if arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/bspace/yocto/poky/build-a20/tmp/sysroots/olinuxino-a20 -std=gnu99 supports -Werror... yes
| checking if arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/bspace/yocto/poky/build-a20/tmp/sysroots/olinuxino-a20 -std=gnu99 supports -Werror=attributes... yes
| /bspace/yocto/poky/build-a20/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libdri2/1_1.0.0+gitAUTOINC+4f1eef3183-r0/git/configure: line 17541: --print-errors: command not found
| checking whether make supports nested variables... (cached) yes
| checking whether malloc(0) returns NULL... (cached) yes
| /bspace/yocto/poky/build-a20/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libdri2/1_1.0.0+gitAUTOINC+4f1eef3183-r0/git/configure: line 17751: syntax error near unexpected token DRI2,' | /bspace/yocto/poky/build-a20/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libdri2/1_1.0.0+gitAUTOINC+4f1eef3183-r0/git/configure: line 17751:PKG_CHECK_MODULES(DRI2, x11 xext xextproto libdrm)'
| Configure failed. The contents of all config.log files follows to aid debugging
| ERROR: oe_runconf failed
| WARNING: /bspace/yocto/poky/build-a20/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libdri2/1_1.0.0+gitAUTOINC+4f1eef3183-r0/temp/run.do_configure.9345:1 exit 1 from
| exit 1
| ERROR: Function failed: do_configure (log file is located at /bspace/yocto/poky/build-a20/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libdri2/1_1.0.0+gitAUTOINC+4f1eef3183-r0/temp/log.do_configure.9345)
ERROR: Task 4370 (/bspace/yocto/poky/meta-sunxi/recipes-graphics/xorg-xserver/libdri2_git.bb, do_configure) failed with exit code '1'

Function failed: do_image_sunxi_sdimg

I keep getting the error below. The sunxi-sdimg is not even created. It works without the meta-sunxi.

bitbake core-image-base
WARNING: Host distribution "Ubuntu-16.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Parsing recipes: 100% |######################################################################################################################################################################| Time: 00:00:24
Parsing of 879 .bb files complete (0 cached, 879 parsed). 1311 targets, 67 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.30.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-16.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "olinuxino-a20"
DISTRO = "poky"
DISTRO_VERSION = "2.1.1"
TUNE_FEATURES = "arm armv7ve vfp neon vfpv4 callconvention-hard cortexa7"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "krogoth:e93596fe74927e2e2f4dd7f671994ccb9744cff8"
meta-sunxi = "master:4ab93061c2f0e22cc91cfd22e31200de92b3eff5"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.0.1/x86_64-nativesdk-libc.tar.bz2;sha256sum=acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8
NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-base-1.0-r0 do_image_sunxi_sdimg: Function failed: do_image_sunxi_sdimg (log file is located at /home/user/yocto/poky/build/tmp/work/olinuxino_a20-poky-linux-gnueabi/core-image-base/1.0-r0/temp/log.do_image_sunxi_sdimg.6889)
ERROR: Logfile of failure stored in: /home/user/yocto/poky/build/tmp/work/olinuxino_a20-poky-linux-gnueabi/core-image-base/1.0-r0/temp/log.do_image_sunxi_sdimg.6889
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_sunxi_sdimg
| dd: failed to open '/core-image-base-olinuxino-a20-20161011145937.rootfs.sunxi-sdimg': Permission denied
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_sunxi_sdimg (log file is located at /home/user/yocto/poky/build/tmp/work/olinuxino_a20-poky-linux-gnueabi/core-image-base/1.0-r0/temp/log.do_image_sunxi_sdimg.6889)
ERROR: Task 17 (/home/user/yocto/poky/meta/recipes-core/images/core-image-base.bb, do_image_sunxi_sdimg) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2504 tasks of which 8 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
/home/user/yocto/poky/meta/recipes-core/images/core-image-base.bb, do_image_sunxi_sdimg
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

mainline 4.1 kernel (as long as 4.4) are broken regarding input devices

mainline 4.1 kernel (as long as 4.4) are broken regarding input devices as defconfig doesn't
contain CONFIG_INPUT_EVDEV which prevents /dev/input/eventX creation
as latest udev doesn't create device nodes and kernel doesn't pick up evdev (and keyboard + mouse are disabled too). dition of CONFIG_INPUT_EVDEV is enough to make X11/weston work with current
openembedded-core/systemd

Yocto Cubieboard2 core-image-sato with tools sdk and packages password??

I just did a clean build of Core-image-sato, this time I enabled debian packages and tools-sdk in my local.conf
Weird enough, the image loads with an enabled password. Anybody knows what the default password could be?

sunxi-mali: --disable-static: not found

sunxi-mali configure error, the following is the error log:
DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
/home/chen/linux/linux-sunxi/yocto/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/sunxi-mali/git-r0/temp/run.do_configure.6832: 103: /home/chen/linux/linux-sunxi/yocto/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/sunxi-mali/git-r0/temp/run.do_configure.6832: --disable-static: not found
WARNING: exit code 127 from a shell command.
ERROR: Function failed: do_configure (log file is located at /home/chen/linux/linux-sunxi/yocto/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/sunxi-mali/git-r0/temp/log.do_configure.6832)

dd: failed to open '/core-image-minimal-cubieboard2-20170117143941.rootfs.sunxi-sdimg': Permission denied

I am building an image for the cubieboard2 and it has not been successful so far. The do rootfs function fails and the dd if="" command fails in the sunxi-sdimg script.Here is my console output.

ngigijoe@ngigijoe-HP-2000-Notebook-PC:~/src/git/poky/build$ bitbake core-image-minimal
WARNING: Host distribution "Ubuntu-16.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |###############################################################################################################################| ETA: 00:00:00
Loaded 1346 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.28.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-16.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "cubieboard2"
DISTRO = "poky"
DISTRO_VERSION = "2.0.3"
TUNE_FEATURES = "arm armv7a vfp neon"
TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp = "jethro:e08994ce953ff5ab49b260e7763a40bfad4285ca"
meta-sunxi = "master:7f88e6c78e7014960654c8f4b3bb0c4e188f0f43"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Error: The image creation script '/home/ngigijoe/src/git/poky/build/tmp/work/cubieboard2-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.sunxi-sdimg' returned 1:
dd: failed to open '/core-image-minimal-cubieboard2-20170117143941.rootfs.sunxi-sdimg': Permission denied
WARNING: exit code 1 from a shell command.

ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/ngigijoe/src/git/poky/build/tmp/work/cubieboard2-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.10750
ERROR: Task 7 (/home/ngigijoe/src/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2119 tasks of which 2118 didn't need to be rerun and 1 failed.
No currently running tasks (2118 of 2123)

Summary: 1 task failed:
/home/ngigijoe/src/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

How to get cubietruck with Qt5

Folks,

I'm trying to get cubietruck and qt5 with mali support.

Basically we have to scenarios:

X11 with mali accelerated
Framebuffer with mali accelerated

I couldn't get none of these working. Both tells me error with EGL.

Anyone ever get cubietruck with qt5 and accelerated HW?

Yocto Cubieboard2: no package provides libUMP.so

Hello,

I'm trying to build yocto(poky-dora-10.0.1) with sunxi layer. Here is my configuration:

BB_VERSION        = "1.20.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-13.10"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "cubieboard2"
DISTRO            = "poky"
DISTRO_VERSION    = "1.5.1"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta              
meta-yocto        
meta-yocto-bsp    = "<unknown>:<unknown>"
meta-oe           = "dora:40e0f371f3eb1628655c484feac0cebf810737b4"
meta-sunxi        = "master:1ebcb0778fade0175f18a2780e8f355f8dca8139"

When I'm trying to bake core-image-sato:

| Note: to be installed:  packagegroup-core-ssh-dropbear@all packagegroup-core-x11-sato-games@cubieboard2 packagegroup-core-x11-base@all smartpm@armv7a_vfp_neon psplash@armv7a_vfp_neon opencv@armv7a_vfp_neon packagegroup-core-boot@cubieboard2 packagegroup-base-extended@cubieboard2 rpm@armv7a_vfp_neon packagegroup-core-x11-sato@cubieboard2 locale-base-en-us@armv7a_vfp_neon locale-base-en-gb@armv7a_vfp_neon
| Loading cache...
| Updating cache...               ######################################## [100%]
| 
| Computing transaction...error: Can't install xf86-video-fbturbo-3:0.3.1+git0+eed17d5586-r0@armv7a_vfp_neon: no package provides libUMP.so

Thanks!

Improve performance by changing default machine tuning options

Note: I am focusing on Cubieboard2 in this post, as that is the board I own and can test on, but this should be relevant to other boards as well

Currently our cubieboard2 machine.conf file [1] falls back on the default tuning option specified in arch-armv7a.inc [2]:

DEFAULTTUNE ?= "armv7a-neon"

This boils down to the following compiler options:

-march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon

That is really the lowest performance option, and cubieboard2 is capable of more than that.
Specifically, it supports NEONv2, VFPv4 and Thumb-2 (see [3] and [4] ) - but the default tuning file does not take advantage of that.

I'd propose to set the default tune to something that supports all the capabilities of the Allwinner A20 chip, i.e.:

DEFAULTTUNE = "cortexa7thf-neon"

resulting in

-march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a7

Note that this still does not take advantage of the NEONv2/VFPv4 capabilities of the Allwinner A20 - for that we'd need -mfpu=neon-vfpv4 [5]. I am currently using an ugly hack to force this compile option in my builds, and opened a request upstream to add this ([6]).

I'll try to run some benchmarks comparing the default with the proposed tuning options above, to put some data behind this, and get an idea of how big the difference is really.

In the meantime, all comments welcome.

Thanks!

Kristof

[1] https://github.com/linux-sunxi/meta-sunxi/blob/master/conf/machine/cubieboard2.conf
[2] https://github.com/openembedded/oe-core/blob/master/meta/conf/machine/include/tune-cortexa7.inc
[3] http://linux-sunxi.org/Allwinner_SoC_Family
[4] http://wits-hep.blogspot.fr/2013/12/fftw-benchmarks-on-cortex-a7.html
[5] http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
[6] https://bugzilla.yoctoproject.org/show_bug.cgi?id=5710

daisy branch

I tested latest meta-sunxi with angstrom-v2014.06-yocto1.6 branch and boot-tested the generated console-image on olinuxino a20.

If it's ok i can create and push the daisy branch based on current master.

recipes-kernel/linux/linux_3.4.bb: clean-up kernel modules

Hi all,

I am not a big fan of the current way to specify kernel-modules in linux_3.4.bb [1]:

        file://screen.conf \        
        file://spdif.conf \
        file://sata.conf \
        file://wifi.conf \
[...]
do_install_append () {
install -d ${D}${sysconfdir}/modules-load.d
install -m 0755 ${WORKDIR}/spdif.conf ${D}${sysconfdir}/modules-load.d/screen.conf
install -m 0755 ${WORKDIR}/spdif.conf ${D}${sysconfdir}/modules-load.d/spdif.conf
install -m 0755 ${WORKDIR}/sata.conf ${D}${sysconfdir}/modules-load.d/sata.conf
install -m 0755 ${WORKDIR}/wifi.conf ${D}${sysconfdir}/modules-load.d/wifi.conf
}

I believe the linux_3.4.bb file should be as minimal/generic as possible, with any kernel modules being added in the appropriate machine.conf file [2] rather than in this generic file, where it will impact all machine configurations.

As an example of how this would work, see
https://github.com/KristofRobot/meta-allwinner/blob/cubieboard2-custom/recipes-kernel/linux/linux_3.4.bb
and
https://github.com/KristofRobot/meta-allwinner/blob/cubieboard2-custom/conf/machine/cubieboard2.conf

Specifically, you can see that the kernel-modules have been moved to the cubieboard2.conf file:

MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS = "\
 kernel-module-sunxi-emac \
 kernel-module-rt2800usb \
 "

#autoload ethernet module at boot
module_autoload_sunxi_emac = "sunxi_emac"
module_autoload_rt2800usb = "rt2800usb"

I can pull a request with a cleaned linux_3.4.bb, but as this is quite a major change, I wanted to discuss this here first.

Thoughts?

Thanks,

Kristof

[1] https://github.com/linux-sunxi/meta-sunxi/blob/master/recipes-kernel/linux/linux_3.4.bb
[2] https://github.com/linux-sunxi/meta-sunxi/tree/master/conf/machine

MACHINE configs set DISTRO policy

The machines in meta-sunxi include https://github.com/linux-sunxi/meta-sunxi/blob/master/conf/machine/include/sunxi-mali.inc which sets DISTRO policy.

Even when ignoring that, an OE build should never install a big blob of binary without explicitly telling the user, especially binaries where redistribution wasn't allowed in past versions.

What I'd like to propose is:

Remove the include from the MACHINE.configs
Tag the machines with a mali gpu with 'mali' in MACHINE_FEATURES, e.g. 'mali200'
Add something like https://github.com/96boards/meta-rpb/blob/master/conf/distro/include/mali.inc to meta-sunxi, located in conf/distro/include
Describe in the README how to include said .inc and what the license terms are

This would be a big step into making mali behave the same between BSPs. If not that, it makes this BSP more well behaved for not stepping on DISTRO settings.

Keyboard and Mouse not working after building core-image-sato for cubieboard2

I successfully built core-image-sato for cubieboard2. It boots perfectly, the Xorg server even launches the desktop. The only problem is I can't get the mouse and keyboard to work. Any help is highly welcome. I have been using the jethro branch.Below is the output I get from:
/var/log/Xorg.0.log

X.Org X Server 1.17.2
Release Date: 2015-06-16
[3132137.737] X Protocol Version 11, Revision 0
[3132137.737] Build Operating System: Linux 4.4.0-59-generic x86_64
[3132137.737] Current Operating System: Linux cubieboard2 4.1.15 #1 SMP Thu Jan
[3132137.737] Kernel command line: console=ttyS0,115200 console=tty1 root=/dev/m
[3132137.737] Build Date: 19 January 2017 07:33:48PM
[3132137.737]
[3132137.737] Current version of pixman: 0.32.6
[3132137.737] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[3132137.737] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[3132137.738] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 20 07:04:14 20
[3132137.778] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[3132137.798] (==) No Layout section. Using the first Screen section.
[3132137.798] (==) No screen section available. Using defaults.
[3132137.798] () |-->Screen "Default Screen Section" (0)
[3132137.798] () | |-->Monitor ""
[3132137.799] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[3132137.799] () | |-->Device "Allwinner A10/A13 FBDEV"
[3132137.799] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[3132137.799] (==) Automatically adding devices
[3132137.799] (==) Automatically enabling devices
[3132137.799] (==) Automatically adding GPU devices
[3132137.802] (WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
[3132137.802] Entry deleted from font path.
[3132137.802] (WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
[3132137.803] Entry deleted from font path.
[3132137.803] (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
[3132137.803] Entry deleted from font path.
[3132137.803] (WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
[3132137.803] Entry deleted from font path.
[3132137.803] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[3132137.803] Entry deleted from font path.
[3132137.803] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[3132137.803] Entry deleted from font path.
[3132137.803] (==) FontPath set to:

[3132137.803] (==) ModulePath set to "/usr/lib/xorg/modules"
[3132137.803] (II) The server relies on udev to provide the list of input device
[3132137.803] (==) ModulePath set to "/usr/lib/xorg/modules"
[3132137.803] (II) The server relies on udev to provide the list of input device
If no devices become available, reconfigure udev or disable AutoAddDevic
[3132137.803] (II) Loader magic: 0x1bfa80
[3132137.803] (II) Module ABI versions:
[3132137.803] X.Org ANSI C Emulation: 0.4
[3132137.803] X.Org Video Driver: 19.0
[3132137.803] X.Org XInput driver : 21.0
[3132137.803] X.Org Server Extension : 9.0
[3132137.804] (II) no primary bus or device found
[3132137.806] (II) LoadModule: "glx"
[3132137.813] (WW) Warning, couldn't open module glx
[3132137.813] (II) UnloadModule: "glx"
[3132137.813] (II) Unloading glx
[3132137.813] (EE) Failed to load module "glx" (module does not exist, 0)
[3132137.813] (II) LoadModule: "fbturbo"
[3132137.813] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[3132137.823] (II) Module fbturbo: vendor="X.Org Foundation"
[3132137.823] compiled for 1.17.2, module version = 0.5.1
[3132137.823] Module class: X.Org Video Driver
[3132137.823] ABI class: X.Org Video Driver, version 19.0
[3132137.823] (II) FBTURBO: driver for framebuffer: fbturbo
[3132137.824] (--) using VT number 3

[3132137.922] (WW) Falling back to old probe method for fbturbo
[3132137.923] (II) Loading sub module "fbdevhw"
[3132137.923] (II) LoadModule: "fbdevhw"
[3132137.923] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[3132137.928] (II) Module fbdevhw: vendor="X.Org Foundation"
[3132137.928] compiled for 1.17.2, module version = 0.0.2
[3132137.928] ABI class: X.Org Video Driver, version 19.0
[3132137.928] (II) FBTURBO(0): using /dev/fb0
[3132137.928] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card suppor
[3132137.929] (II) FBTURBO(0): Creating default Display subsection in Screen sec
"Default Screen Section" for depth/fbbpp 24/32
[3132137.929] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[3132137.929] (==) FBTURBO(0): RGB weight 888
[3132137.929] (==) FBTURBO(0): Default visual is TrueColor
[3132137.929] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[3132137.929] (II) FBTURBO(0): hardware: simple (video memory: 5120kB)
[3132137.929] () FBTURBO(0): Option "fbdev" "/dev/fb0"
[3132137.929] () FBTURBO(0): Option "SwapbuffersWait" "false"
[3132137.930] (II) FBTURBO(0): processor: ARM Cortex-A7
[3132137.930] (II) FBTURBO(0): checking modes against framebuffer device...
[3132137.930] (II) FBTURBO(0): checking modes against monitor...
[3132137.930] (II) FBTURBO(0): checking modes against monitor...
[3132137.930] (--) FBTURBO(0): Virtual size is 1280x1024 (pitch 1280)
[3132137.930] (**) FBTURBO(0): Built-in mode "current"
[3132137.930] (==) FBTURBO(0): DPI set to (96, 96)
[3132137.930] (II) Loading sub module "fb"
[3132137.930] (II) LoadModule: "fb"
[3132137.930] (II) Loading /usr/lib/xorg/modules/libfb.so
[3132137.938] (II) Module fb: vendor="X.Org Foundation"
[3132137.938] compiled for 1.17.2, module version = 1.0.0
[3132137.938] ABI class: X.Org ANSI C Emulation, version 0.4
[3132137.938] (==) Depth 24 pixmap format is 32 bpp
[3132137.939] (EE) FBTURBO(0): FBIOBLANK: Invalid argument
[3132137.960] (II) FBTURBO(0): using backing store heuristics
[3132137.967] (II) FBTURBO(0): can't load 'g2d_23' kernel module
[3132137.967] (II) FBTURBO(0): failed to enable the use of sunxi display control
[3132137.967] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp a
[3132137.968] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
[3132137.968] (II) FBTURBO(0): enabled VFP/NEON optimizations
[3132137.968] (==) FBTURBO(0): Backing store enabled
[3132137.969] (==) FBTURBO(0): DPMS enabled
[3132137.969] (II) FBTURBO(0): failed to enable hardware cursor
[3132137.984] (II) FBTURBO(0): can't load 'mali' kernel module
[3132137.992] (II) FBTURBO(0): can't load 'mali_drm' kernel module
[3132137.992] (II) FBTURBO(0): can't load 'mali_drm' kernel module
[3132138.000] (II) FBTURBO(0): can't load 'sunxi_cedar_mod' kernel module
[3132138.000] (II) Loading sub module "dri2"
[3132138.000] (II) LoadModule: "dri2"
[3132138.000] (II) Module "dri2" already built-in
[3132138.399] SunxiMaliDRI2_Init: drmOpen failed!
[3132138.400] (II) FBTURBO(0): failed to enable DRI2 integration for Mali GPU
[3132138.400] (==) RandR enabled
[3132138.759] (EE) FBTURBO(0): FBIOBLANK: Invalid argument
[3132738.774] (EE) FBTURBO(0): FBIOBLANK: Invalid argument
[3132738.774] (EE) FBTURBO(0): FBIOBLANK: Invalid argument
[3132738.807] (EE) FBTURBO(0): FBIOBLANK: Invalid argument

Image build fails for some machines due to missing/wrong fex support

'meleg' and 'olinuxino-a10' fail for me due to the fex stuff failing to build. With a recent u-boot and mainline being the default, do we still need to build the fex stuff by default?

orange-pi-one build fails on morty

I'm experiencing a similar issue, trying to build the "orange-pi-one":

bitbake core-image-minimal
Parsing recipes: 100% |###############################################################################| Time: 0:00:33
Parsing of 878 .bb files complete (0 cached, 878 parsed). 1334 targets, 76 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-16.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "orange-pi-one"
DISTRO = "poky"
DISTRO_VERSION = "2.2.1"
TUNE_FEATURES = "arm armv7ve vfp neon vfpv4 callconvention-hard cortexa7"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "morty:6a1f33cc40bfac33cf030fe41e1a8efd1e5fad6f"
meta-sunxi = "morty:1848d697ad2c57eebaef7c9826fe9f0e9f55f091"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca
--2017-03-05 21:24:33-- http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2
Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.20.127
Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2473216 (2.4M) [application/octet-stream]
Saving to: ‘/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2’

2017-03-05 21:24:35 (1.39 MB/s) - ‘/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2’ saved [2473216/2473216]

Initialising tasks: 100% |############################################################################| Time: 0:00:04
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: xz-native-5.2.2-r0 do_fetch: Failed to fetch URL http://tukaani.org/xz/xz-5.2.2.tar.gz, attempting MIRRORS if available
WARNING: libpng-native-1.6.24-r0 do_fetch: Failed to fetch URL http://distfiles.gentoo.org/distfiles/libpng-1.6.24.tar.xz, attempting MIRRORS if available
ERROR: core-image-minimal-1.0-r0 do_image_sunxi_sdimg: Function failed: do_image_sunxi_sdimg (log file is located at /home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/work/orange_pi_one-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_sunxi_sdimg.32003)
ERROR: Logfile of failure stored in: /home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/work/orange_pi_one-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_sunxi_sdimg.32003
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_sunxi_sdimg
| 0+0 records in
| 0+0 records out
| 0 bytes copied, 0.000109502 s, 0.0 kB/s
| Model: (file)
| Disk /home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/work/orange_pi_one-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-orange-pi-one-20170305202432.rootfs.sunxi-sdimg: 35.7MB
| Sector size (logical/physical): 512B/512B
| Partition Table: msdos
| Disk Flags:
|
| Number Start End Size Type File system Flags
| 1 2097kB 23.1MB 21.0MB primary boot, lba
| 2 23.1MB 33.6MB 10.5MB primary
|
| mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
| mkfs.fat 4.0 (2016-05-06)
| Total number of sectors (40960) not a multiple of sectors per track (63)!
| Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
| Total number of sectors (40960) not a multiple of sectors per track (63)!
| Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
| Total number of sectors (40960) not a multiple of sectors per track (63)!
| Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
| Copying image-version-info
| 10+0 records in
| 10+0 records out
| 20971520 bytes (21 MB, 20 MiB) copied, 0.0154594 s, 1.4 GB/s
| 0+1 records in
| 0+1 records out
| 10485760 bytes (10 MB, 10 MiB) copied, 0.0117678 s, 891 MB/s
| dd: failed to open '/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/deploy/images/orange-pi-one/u-boot-sunxi-with-spl.bin': No such file or directory
| WARNING: /home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/work/orange_pi_one-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_sunxi_sdimg.32003:1 exit 1 from 'dd if=/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/deploy/images/orange-pi-one/u-boot-sunxi-with-spl.bin of=/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/work/orange_pi_one-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-orange-pi-one-20170305202432.rootfs.sunxi-sdimg bs=1024 seek=8 conv=notrunc'
| ERROR: Function failed: do_image_sunxi_sdimg (log file is located at /home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/build-sunxi-orange-pi-one/tmp/work/orange_pi_one-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_sunxi_sdimg.32003)
ERROR: Task (/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/meta/recipes-core/images/core-image-minimal.bb:do_image_sunxi_sdimg) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1838 tasks of which 6 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/ciprian/work/f-elec/trainig/yocto/yocto-labs/poky-morty/meta/recipes-core/images/core-image-minimal.bb:do_image_sunxi_sdimg
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Looks like the u-boot-sunxi-with-spl.bin was not installed in the expected location.
Anyone experienced this before ?

Thanks

make: *** No rule to make target `A20-OLinuXino-Lime2_config'. Stop.

When compiling an image for Olimex Lime2, I have this error :

ERROR: Function failed: do_compile (log file is located at /home/user/yocto2/build/olimex/output/work/olinuxino_a20lime2-poky-linux-gnueabi/u-boot/1_v2014.04+gitAUTOINC+ea1ac32bf7-r0/temp/log.do_compile.29222)
ERROR: Logfile of failure stored in: /home/user/yocto2/build/olimex/output/work/olinuxino_a20lime2-poky-linux-gnueabi/u-boot/1_v2014.04+gitAUTOINC+ea1ac32bf7-r0/temp/log.do_compile.29222
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 16 CROSS_COMPILE=arm-poky-linux-gnueabi- CC=arm-poky-linux-gnueabi-gcc  --sysroot=/home/user/yocto2/build/olimex/output/sysroots/olinuxino-a20lime2 A20-OLinuXino-Lime2_config
| make: *** No rule to make target `A20-OLinuXino-Lime2_config'.  Stop.
| make: *** [A20-OLinuXino-Lime2_config] Error 1
| ERROR: oe_runmake failed
| WARNING: /home/user/yocto2/build/olimex/output/work/olinuxino_a20lime2-poky-linux-gnueabi/u-boot/1_v2014.04+gitAUTOINC+ea1ac32bf7-r0/temp/run.do_compile.29222:1 exit 1 from
|   exit 1
| ERROR: Function failed: do_compile (log file is located at /home/user/yocto2/build/olimex/output/work/olinuxino_a20lime2-poky-linux-gnueabi/u-boot/1_v2014.04+gitAUTOINC+ea1ac32bf7-r0/temp/log.do_compile.29222)
ERROR: Task 262 (/home/user/yocto2/layers-externes/meta-sunxi/recipes-bsp/u-boot/u-boot_git.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5001 tasks of which 4998 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
/home/user/yocto2/layers-externes/meta-sunxi/recipes-bsp/u-boot/u-boot_git.bb, do_compile

I use poky and openembedded up to date.

I have made it work by editing meta-sunxi/conf/machine/olinuxino-a20lime2.conf and putting UBOOT_MACHINE = "A20-OLinuXino-Lime_config", but I don't really like this solution...

meta-sunxi/conf/machine/olinuxino-a20.conf - wrong UBOOT_MACHINE name

In the master branch in the file:

meta-sunxi/conf/machine/olinuxino-a20.conf

The UBOOT_MACHINE name is incorrect.

It is currently:

UBOOT_MACHINE = "A20-OLinuXino-Micro_config"

But must be:

UBOOT_MACHINE = "A20-OLinuXino_MICRO_defconfig"

Machine and Submachine

Hi,
Today we add a new machine for each card we want to support. So we get a lot of code duplication.
What i would like, is to use only one machine : sunxi so we can have the same defconfig, for the kernel for example. But we also need the diffentiation between machine, so it could be interresting to create a new variable SUBMACHINE which could be cubieboard, cubieboard2, mele, ... With this SUBMACHINE we could configure uboot with the right config, and install the right fex on the sdcard.

I think it will permit to save a lot of code.
What you think about it ?

build failed of sunxi-mali_git.bb for meta-ivi and meta-sunxi

can some please guide me how to fix this problem?
i want to build a genivi baseline for sunxi A20 board.
log as follows:
bitbake gemini-image
Loading cache: 100% |###########################################################################################################| ETA: 00:00:00
Loaded 1219 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 3.4.61 of linux-libc-headers not available (for item linux-libc-headers)
NOTE: versions of linux-libc-headers available: 3.10
NOTE: preferred version 3.4.61 of linux-libc-headers not available (for item linux-libc-headers-dev)
NOTE: versions of linux-libc-headers available: 3.10

Build Configuration:
BB_VERSION = "1.20.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "cubieboard2"
DISTRO = "poky-ivi-systemd"
DISTRO_VERSION = "5.0.1"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp = "dora:53d2563ff13fcec74d4250bef5419e36169e55cc"
meta-ivi = "5.0:efeb671d2ec3b07c2136af57b5e117ae6a19bd5a"
meta-sunxi = "master:db3d191f284c7c6d00a9c6329fe6075229340c0e"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 1, output:
fatal: Could not switch to '/home/chenbd/genivi-baseline/yocto/build/downloads/git2/github.com.linux-sunxi.sunxi-mali.git.tmp/lib': No such file or directory
Unable to fetch in submodule path 'lib/mali'

ERROR: Logfile of failure stored in: /home/chenbd/genivi-baseline/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/temp/log.do_unpack.10480
Log data follows:
| DEBUG: Executing python function do_unpack
| DEBUG: Executing python function base_do_unpack
| DEBUG: Running export SSH_AGENT_PID="1933"; export SSH_AUTH_SOCK="/tmp/keyring-ZZD4cX/ssh"; export PATH="/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/cubieboard2/usr/bin/crossscripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux//bin:/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/poky/bitbake/bin:/home/chenbd/bin:/home/chenbd/android-sdk-linux/tools:/home/chenbd/android-sdk-linux/platform-tools:/home/chenbd/android-studio/bin:/home/chenbd/my-android-toolchain/bin:/home/chenbd/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/sunJVM/JDK/jdk1.6.0_33/bin"; export HOME="/home/chenbd"; git clone -s -n /home/chenbd/genivi-baseline/yocto/build/downloads/git2/github.com.linux-sunxi.sunxi-mali.git/ /home/chenbd/genivi-baseline/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git/
| DEBUG: Running export SSH_AGENT_PID="1933"; export SSH_AUTH_SOCK="/tmp/keyring-ZZD4cX/ssh"; export PATH="/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/cubieboard2/usr/bin/crossscripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux//bin:/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/poky/bitbake/bin:/home/chenbd/bin:/home/chenbd/android-sdk-linux/tools:/home/chenbd/android-sdk-linux/platform-tools:/home/chenbd/android-studio/bin:/home/chenbd/my-android-toolchain/bin:/home/chenbd/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/sunJVM/JDK/jdk1.6.0_33/bin"; export HOME="/home/chenbd"; git checkout 0809383f9d3ee2575da52262a639ddd6464a641f
| DEBUG: Running export SSH_AGENT_PID="1933"; export SSH_AUTH_SOCK="/tmp/keyring-ZZD4cX/ssh"; export PATH="/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/cubieboard2/usr/bin/crossscripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux//bin:/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/poky/bitbake/bin:/home/chenbd/bin:/home/chenbd/android-sdk-linux/tools:/home/chenbd/android-sdk-linux/platform-tools:/home/chenbd/android-studio/bin:/home/chenbd/my-android-toolchain/bin:/home/chenbd/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/sunJVM/JDK/jdk1.6.0_33/bin"; export HOME="/home/chenbd"; git show 0809383f9d3ee2575da52262a639ddd6464a641f:.gitmodules
| DEBUG: Running export SSH_AGENT_PID="1933"; export SSH_AUTH_SOCK="/tmp/keyring-ZZD4cX/ssh"; export PATH="/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/cubieboard2/usr/bin/crossscripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux//bin:/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/poky/bitbake/bin:/home/chenbd/bin:/home/chenbd/android-sdk-linux/tools:/home/chenbd/android-sdk-linux/platform-tools:/home/chenbd/android-studio/bin:/home/chenbd/my-android-toolchain/bin:/home/chenbd/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/sunJVM/JDK/jdk1.6.0_33/bin"; export HOME="/home/chenbd"; cp -r /home/chenbd/genivi-baseline/yocto/build/downloads/git2/github.com.linux-sunxi.sunxi-mali.git/modules /home/chenbd/genivi-baseline/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git//.git/
| DEBUG: Running export SSH_AGENT_PID="1933"; export SSH_AUTH_SOCK="/tmp/keyring-ZZD4cX/ssh"; export PATH="/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/cubieboard2/usr/bin/crossscripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux//bin:/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/poky/bitbake/bin:/home/chenbd/bin:/home/chenbd/android-sdk-linux/tools:/home/chenbd/android-sdk-linux/platform-tools:/home/chenbd/android-studio/bin:/home/chenbd/my-android-toolchain/bin:/home/chenbd/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/sunJVM/JDK/jdk1.6.0_33/bin"; export HOME="/home/chenbd"; git submodule init
| DEBUG: Running export SSH_AGENT_PID="1933"; export SSH_AUTH_SOCK="/tmp/keyring-ZZD4cX/ssh"; export PATH="/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/cubieboard2/usr/bin/crossscripts:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/usr/bin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux/sbin:/home/chenbd/genivi-baseline/yocto/build/tmp/sysroots/x86_64-linux//bin:/home/chenbd/genivi-baseline/yocto/poky/scripts:/home/chenbd/genivi-baseline/yocto/poky/bitbake/bin:/home/chenbd/bin:/home/chenbd/android-sdk-linux/tools:/home/chenbd/android-sdk-linux/platform-tools:/home/chenbd/android-studio/bin:/home/chenbd/my-android-toolchain/bin:/home/chenbd/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/sunJVM/JDK/jdk1.6.0_33/bin"; export HOME="/home/chenbd"; git submodule update
| DEBUG: Python function base_do_unpack finished
| DEBUG: Python function do_unpack finished
| ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 1, output:
| fatal: Could not switch to '/home/chenbd/genivi-baseline/yocto/build/downloads/git2/github.com.linux-sunxi.sunxi-mali.git.tmp/lib': No such file or directory
| Unable to fetch in submodule path 'lib/mali'
|
ERROR: Task 2325 (/home/chenbd/genivi-baseline/yocto/meta-sunxi/recipes-graphics/libgles/sunxi-mali_git.bb, do_unpack) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2187 tasks of which 2181 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
/home/chenbd/genivi-baseline/yocto/meta-sunxi/recipes-graphics/libgles/sunxi-mali_git.bb, do_unpack
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

How to get a working X11 image on Cubietruck

Folks,

I'm using both yocto and meta-sunxi on dora branch.
I've built a core-image-x11 but xorg fails to initialize.
I've added xf86-video-fbturbo on the image.

Here is my Xorg.0.log file:
[4233974.387]
X.Org X Server 1.14.0
Release Date: 2013-03-05
[4233974.387] X Protocol Version 11, Revision 0
[4233974.387] Build Operating System: Linux 3.5.0-27-generic x86_64
[4233974.387] Current Operating System: Linux cubietruck 3.4.79 #1 SMP PREEMPT Wed May 14 11:07:22 BRT 2014 armv7l
[4233974.387] Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait loglevel=8 panic=10
[4233974.388] Build Date: 14 May 2014 03:45:20PM
[4233974.388]
[4233974.388] Current version of pixman: 0.30.2
[4233974.388] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[4233974.388] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
4233974.388 Log file: "/var/log/Xorg.0.log", Time: Wed May 14 20:12:25 2014
4233974.399 Using system config directory "/usr/share/X11/xorg.conf.d"
4233974.401 No Layout section. Using the first Screen section.
4233974.401 No screen section available. Using defaults.
4233974.401 |-->Screen "Default Screen Section" (0)
4233974.401 | |-->Monitor ""
4233974.409 No device specified for screen "Default Screen Section".
Using the first device section listed.
4233974.409 | |-->Device "Allwinner A10/A13 FBDEV"
4233974.409 No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
4233974.410 Automatically adding devices
4233974.410 Automatically enabling devices
4233974.410 Automatically adding GPU devices
4233974.412 The directory "/usr/share/fonts/X11/misc/" does not exist.
[4233974.412] Entry deleted from font path.
4233974.412 The directory "/usr/share/fonts/X11/TTF/" does not exist.
[4233974.412] Entry deleted from font path.
4233974.412 The directory "/usr/share/fonts/X11/OTF/" does not exist.
[4233974.412] Entry deleted from font path.
4233974.412 The directory "/usr/share/fonts/X11/Type1/" does not exist.
[4233974.412] Entry deleted from font path.
4233974.412 The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[4233974.412] Entry deleted from font path.
4233974.412 The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[4233974.413] Entry deleted from font path.
4233974.413 FontPath set to:

4233974.413 ModulePath set to "/usr/lib/xorg/modules"
4233974.413 The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
4233974.414 Loader magic: 0x1a6848
4233974.414 Module ABI versions:
[4233974.414] X.Org ANSI C Emulation: 0.4
[4233974.414] X.Org Video Driver: 14.1
[4233974.414] X.Org XInput driver : 19.1
[4233974.414] X.Org Server Extension : 7.0
4233974.416 config/udev: Adding drm device (/dev/dri/card0)
4233974.416 config/udev: Adding drm device (/dev/dri/card1)
[4233974.419] Initializing built-in extension Generic Event Extension
[4233974.419] Initializing built-in extension SHAPE
[4233974.419] Initializing built-in extension MIT-SHM
[4233974.419] Initializing built-in extension XInputExtension
[4233974.419] Initializing built-in extension XTEST
[4233974.419] Initializing built-in extension BIG-REQUESTS
[4233974.419] Initializing built-in extension SYNC
[4233974.419] Initializing built-in extension XKEYBOARD
[4233974.419] Initializing built-in extension XC-MISC
[4233974.419] Initializing built-in extension XFIXES
[4233974.419] Initializing built-in extension RENDER
[4233974.419] Initializing built-in extension RANDR
[4233974.419] Initializing built-in extension COMPOSITE
[4233974.420] Initializing built-in extension DAMAGE
[4233974.420] Initializing built-in extension MIT-SCREEN-SAVER
[4233974.420] Initializing built-in extension DOUBLE-BUFFER
[4233974.420] Initializing built-in extension DPMS
[4233974.420] Initializing built-in extension X-Resource
[4233974.420] Initializing built-in extension XVideo
[4233974.420] Initializing built-in extension XVideo-MotionCompensation
[4233974.420] Initializing built-in extension XFree86-VidModeExtension
[4233974.420] Initializing built-in extension XFree86-DGA
[4233974.420] Initializing built-in extension XFree86-DRI
[4233974.420] Initializing built-in extension DRI2
4233974.420 LoadModule: "glx"
4233974.427 Warning, couldn't open module glx
4233974.427 UnloadModule: "glx"
4233974.427 Unloading glx
4233974.427 Failed to load module "glx" (module does not exist, 0)
4233974.427 LoadModule: "fbturbo"
4233974.427 Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
4233974.435 Failed to load /usr/lib/xorg/modules/drivers/fbturbo_drv.so: /MY_BUILD_SYSROOT_PATH/usr/lib/libUMP.so: cannot open shared object file: No such file or directory
4233974.435 UnloadModule: "fbturbo"
4233974.435 Unloading fbturbo
4233974.435 Failed to load module "fbturbo" (loader failed, 7)
4233974.435 No drivers available.
[4233974.436]
Fatal server error:
[4233974.436] no screens found
4233974.436
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
4233974.436 Please also check the log file at "/var/log/Xorg.0.log" for additional information.
4233974.436
[4233974.436] Server terminated with error (1). Closing log file.

Note that fbturbo_drv.so is tryng to load libUMP.so from my build sysroot path.

weird dependency problems

We have sunxi-mali and libump recipes, both of which generate libUMP.so.3 and libUMP.so.
Which one is relevant?

Commit "4240612 Use SOC_FAMILY to avoid the long list..." breaks u-boot on the cubieboard 2.

It gets into a bootloop:

U-Boot SPL 2015.07-rc2-gdfc8bb1 (Jun 25 2015 - 19:04:45)
DRAM:Timeout initialising DRAM

resetting ...

U-Boot SPL 2015.07-rc2-gdfc8bb1 (Jun 25 2015 - 19:04:45)
DRAM:Timeout initialising DRAM

resetting ...

linux: do_configure fails - no rule to make target 'oldconfig'

When building against the newest openembedded master, the below failure
occurs.

DEBUG: Executing shell function do_configure
NOTE: make oldconfig
make: *** No rule to make target `oldconfig'.  Stop.
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_configure

Apparently this is already fixed in meta-raspberrypi, see djwillis/meta-raspberrypi@1eda7e8

We should do something similar.

Problems with sunxi-mail on current master

I am trying to compile my layer with meta-sunxi on current master (which will be Yocto 2.0). I got many build errors complaining about missing EGL, which is fixed by my current pull request, but I still get an error when bitbaking sunxi-mali:

ERROR: runstrip: ''arm-poky-linux-gnueabi-strip' --remove-section=.comment --remove-section=.note --strip-unneeded '/home/jens/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/sysroot-destdir/usr/lib/libMali.so.3'' strip command failed with 1 (arm-poky-linux-gnueabi-strip: /home/jens/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/sysroot-destdir/usr/lib/stpvDXfe: Not enough room for program headers, try linking with -N
arm-poky-linux-gnueabi-strip:/home/jens/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/sysroot-destdir/usr/lib/stpvDXfe[.note.gnu.build-id]: Bad value
)

The recipe already contains
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"
which should skip the most split actions. I am not getting this error on current yocto fido. Any ideas?

Cubietruck with Qt5

I'm having compile errors for qtbase using the following configs on local.conf:
DEFAULTTUNE = "cortexa7hf-neon-vfpv4"
DISTRO_FEATURES_append = " opengl x11"
PACKAGECONFIG_append_pn-qtbase = " linuxfb gles2 xcb"

If I remove PACKAGECONFIG line everything is compile but Qt5_CinematicExperience isn't launched complaining about missing xcb plugin.

I'm using yocto and meta-sunxi on dora and meta-qt5 on master.

Have anyone successfully gotten qt5 with mali support up and running?

Am I missing something?

linux: QA issues

When bitbaking core-image-minimal with cubieboard2, I get the following QA issues:

WARNING: QA Issue: linux: Files/directories were installed but not shipped
  /usr/src/debug
  /usr/src/debug/linux
  /usr/src/debug/linux/3.4.67-14
  /usr/src/debug/linux/3.4.67-14/git
  /usr/src/debug/linux/3.4.67-14/git/include
  /usr/src/debug/linux/3.4.67-14/git/arch
  /usr/src/debug/linux/3.4.67-14/git/include/linux
  /usr/src/debug/linux/3.4.67-14/git/include/linux/printk.h
  /usr/src/debug/linux/3.4.67-14/git/include/linux/kernel.h
  /usr/src/debug/linux/3.4.67-14/git/include/linux/power
  /usr/src/debug/linux/3.4.67-14/git/include/linux/power/aw_pm.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/include
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/include/asm
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/include/asm/hwcap.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/include
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/include/mach
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/include/mach/ccmu.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/mem_tmr.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/mem_timing.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/pm_types.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/pm_debug.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/mem_divlibc.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/pm.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/dram.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_power.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_usb.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_printk.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_twi.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_timing.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_tmr.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_divlib.S
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_delay.S
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_mmu_pc_asm.S
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_ir.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_key.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_delay.S
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_int.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_divlibc.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_key.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/dram_init.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_serial.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_power.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_clock.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/common.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_clock.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/common.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/pm_debug.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/mem_int.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_usb.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_ir.h
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_twi.c
  /usr/src/debug/linux/3.4.67-14/git/arch/arm/mach-sun7i/pm/standby/standby_tmr.c

and

WARNING: QA Issue: No GNU_HASH in the elf binary: '/home/kristof/OE/oe-core/build/tmp-eglibc/work/cubieboard2-oe-linux-gnueabi/linux/3.4.67-14/packages-split/kernel-dev/usr/src/kernel/modules/wifi/usi-bcm4329/v4.218.248.15/apps/epi_ttcp'
WARNING: QA Issue: No GNU_HASH in the elf binary: '/home/kristof/OE/oe-core/build/tmp-eglibc/work/cubieboard2-oe-linux-gnueabi/linux/3.4.67-14/packages-split/kernel-dev/usr/src/kernel/modules/wifi/bcm40181/apps/epi_ttcp'

Although these are just "warnings", I think it would be better if these would be solved (preferred) or supressed using INSANE_SKIP (otherwise).

In fact, if possible, I'd like to take the opportunity to also review the current skip line:

INSANE_SKIP_kernel-dev = "debug-files debug-deps arch"

Thoughts on how to do so?

Socarch definition missing?

In sunxi.inc the following definition is done:

Sub-architecture support

MACHINE_SOCARCH_SUFFIX ?= ""
MACHINE_SOCARCH_SUFFIX_sun4i = "-sun4i"

does it not need to define the other sufixes as well?

e.g.
MACHINE_SOCARCH_SUFFIX_sun5i = "-sun5i"
MACHINE_SOCARCH_SUFFIX_sun7i = "-sun7i"

uImage: no such file or directory

Image creation fails with latest openembedded master:

ERROR: Error: The image creation script '/home/kristof/OE/build/tmp-glibc/work/cubieboard2-oe-linux-gnueabi/core-image-frobo/1.0-r0/temp/create_image.sunxi-sdimg' returned 1:
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.3093e-05 s, 0.0 kB/s
Model:  (file)
Disk /home/kristof/OE/build/tmp-glibc/deploy/images/cubieboard2/core-image-frobo-cubieboard2-20150201115239.rootfs.sunxi-sdimg: 979MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      2097kB  23.1MB  21.0MB  primary               boot, lba
 2      23.1MB  977MB   954MB   primary

mkfs.vfat 2.11 (12 Mar 2005)
/home/kristof/OE/build/tmp-glibc/sysroots/cubieboard2/usr/src/kernel/uImage: No such file or directory
WARNING: exit code 1 from a shell command.

ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/kristof/OE/build/tmp-glibc/work/cubieboard2-oe-linux-gnueabi/core-image-frobo/1.0-r0/temp/log.do_rootfs.6054
NOTE: recipe core-image-frobo-1.0-r0: task do_rootfs: Failed
ERROR: Task 7 (/home/kristof/OE/meta-frobo/recipes-images/frobo/core-image-frobo.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6370 tasks of which 6369 didn't need to be rerun and 1 failed.

Why complex kernel config again?

Is it now ok to add kernel config options again? When I added the kernel recipe for 4.x I had a complex config with many options enabled which I removed again:

ebutera -
"please as @whirm said it's better to just use the sunxi_defconfig instead of adding those files, it's much easier to maintain"

If it´s ok, I´ll add back a few options myself.

Custom dts in yocto

Hello,
i tried build system without rtc (in cubieboard isn't active on board), and in previously versions i used a small script for sys which add i2c rtc ds1307 device as rtc and it work fine. But in current version have embedded rtc driver and i can not use external rtc device, because internal rtc is in priority for hwclock. And i want add some new devices through IO ports. For u-boot i created own repo and link to it with new commit id and this solution work fine (i see my dtb inspl file), but kernel rewrite all dts's and i can not use this hook. What is correct way to use custom dts in meta-sunxi. Google hasn't this info. Thank you.

Cubietruck - fail to bring-up eth0

This is my build configuration:

Yocto on dora
meta-sunxi on dora
DEFAULTTUNE = "cortexa7hf-neon-vfpv4" (cherry-pick vfpv4 support)
core-image-minimal and core-image-base

When I try a ifup eth0 I get this message:

ifconfig: SIOCGIFFLAGS: No such device

cgroup patch fails with newer sunxi kernel

Trying to update the meta-sunxi kernel, the patch 0001-cgroup-add-xattr-support-sunxi.patch fails because of a conflict. The conflicting part of the patch is:

@@ -3921,51 +4244,63 @@ static int cgroup_has_css_refs(struct cgroup *cgrp)

which conflicts with

linux-sunxi/linux-sunxi@b519f21

I don´t know which is the best solution to solve this:

Remove CGroup Patch
Remove conflicting patch
Resolv conflict

Just resolving the conflicting lines would be easy, but I am not sure about the implications in the code. Maybe somebody with better C and kernel knowledge can tell me what the best option is?

Add support for Olinuxino A10 Lime

Would it be possible to add support for Olinuxino A10 Lime? I've manually tried to hack it in, but I didn't succeed very well..

Besides the obvious changes needed in config files, some of the git revisions for u-boot, linux-sunxi, fex etc. might need to be updated.

I did manage to add it manually and get it to compile properly, but I couldn't get it to boot on the device.

sdcard_image-sunxi: race condition

Hi,

There seems to be a race condition in sdcard_image-sunxi.bbclass [1].

Analysis
When I build an image using BB_NUMBER_THREADS = 2, I get the error:

/home/kristof/OE/oe-core/build/tmp-eglibc/deploy/images/cubieboard2/uImage-cubieboard2.bin: No such file or directory
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_rootfs (log file is located at /home/kristof/OE/oe-core/build/tmp-eglibc/work/cubieboard2-oe-linux-gnueabi/core-image-base-ssh/1.0-r0/temp/log.do_rootfs.30047)

Looking at the code in sdcard_image-sunxi.bbclass, I believe this is due to a race condition between virtual/kernel:do_deploy and image_types:do_rootfs.

Specifically, image_types:do_rootfs depends on virtual/kernel:do_populate_sysroot as IMAGE_DEPENDS_sunxi-sdimg is translated into dependencies as follows, by image_types.bbclass [2]:

def imagetypes_getdepends(d):
    [...]
    for dep in deps:
        depstr += " " + dep + ":do_populate_sysroot"
    return depstr

However, ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${MACHINE}.bin is only written away during virtual/kernel:do_deploy by kernel.bbclass [3]:

kernel_do_deploy() {
        install -m 0644 ${KERNEL_OUTPUT} ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
 [...]

        ln -sf ${KERNEL_IMAGE_BASE_NAME}.bin ${DEPLOYDIR}/${KERNEL_IMAGE_SYMLINK_NAME}.bin

Hence the race condition.

Note that there is also a dependency on sunxi-board-fex:do_deploy through following code:

       if [ -e "${DEPLOY_DIR_IMAGE}/fex.bin" ]
        then
                mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/fex.bin ::script.bin
        fi

and in sunxi-board-fex.bb

do_deploy() {
    install -m 0644 ${B}/${SUNXI_FEX_BIN_IMAGE} ${DEPLOYDIR}/
    cd ${DEPLOYDIR}
    ln -sf ${SUNXI_FEX_BIN_IMAGE} ${SUNXI_FEX_BIN_IMAGE_SYMLINK}
    ln -sf ${SUNXI_FEX_BIN_IMAGE} ${SUNXI_FEX_BIN_IMAGE_SYMLINK_SIMPLE}
}

However, in practice, I believe this is highly unlikely to manifest itself as a race condition, as u-boot depends on sunxi-board-fex as well, and while u-boot is 'baking', there is plenty of time for sunxi-board-fex to finish do_deploy. Nevertheless, something we might want to fix as well.

Solution
I see two ways to solve the dependency on virtual/kernel:do_deploy:

(1) Use STAGING_DIR rather than DEPLOYDIR
Do not depend on files in DEPLOYDIR, but use files from STAGING_DIR instead, i.e. (not tested yet)

mcopy -i ${WORKDIR}/boot.img -s ${STAGING_DIR_HOST}/usr/src/kernel//${KERNEL_IMAGETYPE} ::uImage

(2) Create the right dependency
As far as I understand, I should be able to do this by adding following line in sdcard_image-sunxi.bbclass:

do_rootfs[depends] += "virtual/kernel:do_deploy"

However, that does not seem to work, although I do not understand why.

I actually prefer the second solution, as it seems more elegant - if it would work.

Anyone have any idea how to make that option work?
Or a preference for solution (1)?
Or another solution?

[1] https://github.com/linux-sunxi/meta-sunxi/blob/master/classes/sdcard_image-sunxi.bbclass
[2] https://github.com/openembedded/oe-core/blob/master/meta/classes/image_types.bbclass
[3] https://github.com/openembedded/oe-core/blob/master/meta/classes/kernel.bbclass

ata1: link is slow to respond, please be patient (ready=0)

Hello.
I have build yocto sdimage and test it on my Cubieboard. When i plugged 2.5" hdd Toshiba MK2565GSX to the cubie i got error messages at boot:

U-Boot SPL 2015.07-g33711bd (Aug 24 2015 - 22:03:48)
DRAM: 1024 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2


U-Boot 2015.07-g33711bd (Aug 24 2015 - 22:03:48 +0300) Allwinner Technology

CPU:   Allwinner A10 (SUN4I)
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
SCSI:  SUNXI SCSI INIT
Target spinup took 0 ms.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst 
Can not start port 0

Then boot process:

Net:   eth0: ethernet@01c0b000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
reading /boot.scr
499 bytes read in 17 ms (28.3 KiB/s)
## Executing script at 43100000
reading sun4i-a10-cubieboard.dtb
21420 bytes read in 31 ms (673.8 KiB/s)
reading zImage
** Unable to read file zImage **
reading boot/zImage
** Unable to read file boot/zImage **
reading uImage
3273048 bytes read in 261 ms (12 MiB/s)
Bad Linux ARM zImage magic!
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux-4.1.3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3272984 Bytes = 3.1 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Kernel Image ... OK
   Loading Device Tree to 4eff7000, end 4efff3ab ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 4.1.3 (bai@bai-desktop) (gcc version 4.9.2 (GCC) ) #1 SMP Mon Aug 24 21:46:00 MSK 2015
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Cubietech Cubieboard
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] PERCPU: Embedded 11 pages/cpu @eefd8000 s16384 r8192 d20480 u45056
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260624
[    0.000000] Kernel command line: console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootwait panic=10
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1032804K/1048576K available (4532K kernel code, 196K rwdata, 1348K rodata, 260K init, 244K bss, 15772K reserved, 0K cma-reserved, 270336K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc05c65c0   (5882 kB)
[    0.000000]       .init : 0xc05c7000 - 0xc0608000   ( 260 kB)
[    0.000000]       .data : 0xc0608000 - 0xc06390a0   ( 197 kB)
[    0.000000]        .bss : 0xc063c000 - 0xc0679234   ( 245 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000017] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000039] clocksource timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000282] Console: colour dummy device 80x30
[    0.000682] console [tty1] enabled
[    0.000715] Calibrating delay loop... 1001.88 BogoMIPS (lpj=5009408)
[    0.040095] pid_max: default: 32768 minimum: 301
[    0.040203] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.040231] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.040791] Initializing cgroup subsys net_cls
[    0.040856] CPU: Testing write buffer coherency: ok
[    0.041106] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.041191] Setting up static identity map for 0x40008280 - 0x400082d8
[    0.042093] Brought up 1 CPUs
[    0.042127] SMP: Total of 1 processors activated (1001.88 BogoMIPS).
[    0.042148] CPU: All CPU(s) started in SVC mode.
[    0.042600] devtmpfs: initialized
[    0.048213] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.048572] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.048911] pinctrl core: initialized pinctrl subsystem
[    0.049785] NET: Registered protocol family 16
[    0.050315] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.050760] cpuidle: using governor ladder
[    0.050792] cpuidle: using governor menu
[    0.054828] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.061712] reg-fixed-voltage ahci-5v: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/ahci_pwr_pin@0, deferring probe
[    0.061794] reg-fixed-voltage usb1-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb1_vbus_pin@0, deferring probe
[    0.061850] reg-fixed-voltage usb2-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb2_vbus_pin@0, deferring probe
[    0.062950] SCSI subsystem initialized
[    0.063477] usbcore: registered new interface driver usbfs
[    0.063558] usbcore: registered new interface driver hub
[    0.063628] usbcore: registered new device driver usb
[    0.063768] pps_core: LinuxPPS API ver. 1 registered
[    0.063788] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[    0.063841] PTP clock support registered
[    0.064783] Switched to clocksource timer
[    0.074562] NET: Registered protocol family 2
[    0.075248] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.075348] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.075471] TCP: Hash tables configured (established 8192 bind 8192)
[    0.075573] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.075618] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.075779] NET: Registered protocol family 1
[    0.076158] RPC: Registered named UNIX socket transport module.
[    0.076190] RPC: Registered udp transport module.
[    0.076209] RPC: Registered tcp transport module.
[    0.076228] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.079036] futex hash table entries: 256 (order: 2, 16384 bytes)
[    0.089803] NFS: Registering the id_resolver key type
[    0.089893] Key type id_resolver registered
[    0.089914] Key type id_legacy registered
[    0.091071] bounce: pool size: 64 pages
[    0.091311] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.091359] io scheduler noop registered
[    0.091385] io scheduler deadline registered
[    0.091434] io scheduler cfq registered (default)
[    0.093688] sun4i-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[    0.151042] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    0.154061] console [ttyS0] disabled
[    0.174177] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 30, base_baud = 1500000) is a U6_16550A
[    0.713789] console [ttyS0] enabled
[    0.719520] 1c0b080.mdio supply phy not found, using dummy regulator
[    0.726141] libphy: sun4i_mii_bus: probed
[    0.767646] sun4i-emac 1c0b000.ethernet: eth0: at f009a000, IRQ 19 MAC: 02:41:08:81:48:e9
[    0.776257] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.782805] ehci-platform: EHCI generic platform driver
[    0.788329] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.794537] ohci-platform: OHCI generic platform driver
[    0.800902] sunxi-rtc 1c20d00.rtc: rtc core: registered rtc-sunxi as rtc0
[    0.807757] sunxi-rtc 1c20d00.rtc: RTC enabled
[    0.812278] i2c /dev entries driver
[    0.816589] axp20x 0-0034: AXP20x variant AXP209 found
[    0.829183] input: axp20x-pek as /devices/platform/soc@01c00000/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input0
[    0.842440] axp20x 0-0034: AXP20X driver loaded
[    0.848106] sunxi-wdt 1c20c90.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[    0.856573] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found
[    0.862495] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[    0.904927] sunxi-mmc 1c0f000.mmc: base:0xf00a6000 irq:20
[    0.911086] ledtrig-cpu: registered to indicate activity on CPUs
[    0.917830] usbcore: registered new interface driver usbhid
[    0.923417] usbhid: USB HID core driver
[    0.928002] NET: Registered protocol family 17
[    0.932567] Key type dns_resolver registered
[    0.937673] Registering SWP/SWPB emulation handler
[    0.943230] registered taskstats version 1
[    0.981930] mmc0: host does not support reading read-only switch, assuming write-enable
[    0.992185] mmc0: new high speed SDHC card at address e624
[    0.998111] mmcblk0: mmc0:e624 SU04G 3.69 GiB 
[    1.003775]  mmcblk0: p1 p2
[    1.014848] ahci-sunxi 1c18000.sata: controller can't do PMP, turning off CAP_PMP
[    1.022388] ahci-sunxi 1c18000.sata: SSS flag set, parallel bus scan disabled
[    1.029577] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
[    1.038575] ahci-sunxi 1c18000.sata: flags: ncq sntf stag pm led clo only pio slum part ccc 
[    1.048014] scsi host0: ahci-sunxi
[    1.051820] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 23
[    1.060113] ehci-platform 1c14000.usb: EHCI Host Controller
[    1.065766] ehci-platform 1c14000.usb: new USB bus registered, assigned bus number 1
[    1.073640] ehci-platform 1c14000.usb: irq 21, io mem 0x01c14000
[    1.094791] ehci-platform 1c14000.usb: USB 2.0 started, EHCI 1.00
[    1.101735] hub 1-0:1.0: USB hub found
[    1.105602] hub 1-0:1.0: 1 port detected
[    1.110132] ehci-platform 1c1c000.usb: EHCI Host Controller
[    1.115802] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[    1.123683] ehci-platform 1c1c000.usb: irq 24, io mem 0x01c1c000
[    1.144773] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[    1.151646] hub 2-0:1.0: USB hub found
[    1.155503] hub 2-0:1.0: 1 port detected
[    1.160021] ohci-platform 1c14400.usb: Generic Platform OHCI controller
[    1.166724] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3
[    1.174605] ohci-platform 1c14400.usb: irq 22, io mem 0x01c14400
[    1.239522] hub 3-0:1.0: USB hub found
[    1.243335] hub 3-0:1.0: 1 port detected
[    1.247906] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[    1.254556] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4
[    1.262490] ohci-platform 1c1c400.usb: irq 25, io mem 0x01c1c400
[    1.329552] hub 4-0:1.0: USB hub found
[    1.333359] hub 4-0:1.0: 1 port detected
[    1.337754] sunxi-rtc 1c20d00.rtc: setting system clock to 2010-01-01 00:00:26 UTC (1262304026)
[    1.351424] ldo4: disabling
[    1.354452] ldo3: disabling
[    1.357497] vcc5v0: disabling
[    1.360481] vcc3v0: disabling
[    6.464776] ata1: link is slow to respond, please be patient (ready=0)
[   11.084772] ata1: COMRESET failed (errno=-16)
[   16.554769] ata1: link is slow to respond, please be patient (ready=0)
[   21.114769] ata1: COMRESET failed (errno=-16)
[   21.484777] ata1: SATA link down (SStatus 0 SControl 300)
[   21.491474] EXT4-fs (mmcblk0p2): mounting ext3 file system using the ext4 subsystem
[   21.499908] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[   21.507274] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[   21.514794] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
[   21.522214] ata1: irq_stat 0x00400040, connection status changed
[   21.528251] ata1: SError: { RecovComm PHYRdyChg CommWake DevExch }
[   21.534459] ata1: hard resetting link
[   21.570548] EXT4-fs (mmcblk0p2): recovery complete
[   21.577371] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   21.585547] VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
[   21.593037] devtmpfs: mounted
[   21.596390] Freeing unused kernel memory: 260K (c05c7000 - c0608000)
[   22.033100] udevd[98]: starting version 182
[   22.174668] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
[   22.281143] random: dd urandom read with 42 bits of entropy available
[   23.884782] ata1: COMRESET failed (errno=-32)
[   23.889173] ata1: reset failed (errno=-32), retrying in 8 secs
[   31.534784] ata1: limiting SATA link speed to 1.5 Gbps
[   31.539950] ata1: hard resetting link

Poky (Yocto Project Reference Distro) 1.8 cubieboard /dev/ttyS0

And at end again error messages:

cubieboard login: [   33.804780] ata1: COMRESET failed (errno=-32)
[   33.809170] ata1: reset failed (errno=-32), retrying in 8 secs
[   41.544786] ata1: hard resetting link
[   43.934774] ata1: COMRESET failed (errno=-32)
[   43.939158] ata1: reset failed (errno=-32), retrying in 33 secs
[   76.554788] ata1: hard resetting link
[   78.984776] ata1: COMRESET failed (errno=-32)
[   78.989183] ata1: reset failed, giving up
[   78.993218] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4050202 action 0xe frozen t4
[   79.000924] ata1: irq_stat 0x00400040, connection status changed
[   79.006958] ata1: SError: { RecovComm Persist PHYRdyChg CommWake DevExch }
[   79.013858] ata1: hard resetting link
[   81.444776] ata1: COMRESET failed (errno=-32)
[   81.449164] ata1: reset failed (errno=-32), retrying in 8 secs
[   89.014781] ata1: limiting SATA link speed to 1.5 Gbps
[   89.019946] ata1: hard resetting link
[   91.324779] ata1: COMRESET failed (errno=-32)
[   91.329178] ata1: reset failed (errno=-32), retrying in 8 secs
[   99.024782] ata1: hard resetting link
[  101.294773] ata1: COMRESET failed (errno=-32)
[  101.299154] ata1: reset failed (errno=-32), retrying in 33 secs
[  107.044781] random: nonblocking pool is initialized
[  134.034789] ata1: hard resetting link
[  136.504775] ata1: COMRESET failed (errno=-32)
[  136.509179] ata1: reset failed, giving up
[  136.513215] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4050202 action 0xe frozen t3
[  136.520924] ata1: irq_stat 0x00400040, connection status changed
[  136.526962] ata1: SError: { RecovComm Persist PHYRdyChg CommWake DevExch }
[  136.533862] ata1: hard resetting link
[  138.964777] ata1: COMRESET failed (errno=-32)
[  138.969159] ata1: reset failed (errno=-32), retrying in 8 secs
[  146.534783] ata1: limiting SATA link speed to 1.5 Gbps
[  146.539950] ata1: hard resetting link
[  148.844780] ata1: COMRESET failed (errno=-32)
[  148.849180] ata1: reset failed (errno=-32), retrying in 8 secs

Maybe i doing something incorrect?

glmark2 not building - egl not found - potentially sunxi-mali related

When trying to bitbake glmark2 on a cubieboard2, I get following error, which is potentially sunxi-mali related.

DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
Setting top to                           : /home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/glmark2/2012.12-r0/glmark2-2012.12 
Setting out to                           : /home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/glmark2/2012.12-r0/glmark2-2012.12/build 
Checking for 'gcc' (c compiler)          : arm-oe-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 --sysroot=/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2 
Checking for 'g++' (c++ compiler)        : arm-oe-linux-gnueabi-g++ -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7 --sysroot=/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2 
Checking for header stdlib.h             : yes 
Checking for header string.h             : yes 
Checking for header unistd.h             : yes 
Checking for header stdint.h             : yes 
Checking for header stdio.h              : yes 
Checking for header jpeglib.h            : yes 
Checking for library m                   : yes 
Checking for library jpeg                : yes 
Checking for function memset             : yes 
Checking for function sqrt               : yes 
Checking for program pkg-config          : /home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/pkg-config 
Checking for 'libpng12'                  : yes 
Checking for 'x11'                       : yes 
Checking for 'gl'                        : yes 
Checking for 'egl'                       : not found 
The configuration failed
(complete log in /home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/glmark2/2012.12-r0/glmark2-2012.12/build/config.log)
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_configure (log file is located at /home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/glmark2/2012.12-r0/temp/log.do_configure.26995)

cat cat /home/kristof/OE/oe-core/build/tmp-eglibc/work/cortexa7hf-vfp-neon-oe-linux-gnueabi/glmark2/2012.12-r0/glmark2-2012.12/build/config.log:

[...]
Checking for 'gl'
['/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/pkg-config', 'gl', '--cflags', '--libs']
out: -DMESA_EGL_NO_X11_HEADERS -I/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/cubieboard2/usr/include/libdrm -lGL 

yes
----------------------------------------
Checking for 'egl'
['/home/kristof/OE/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/pkg-config', 'egl', '--cflags', '--libs']
err: Package egl was not found in the pkg-config search path.
Perhaps you should add the directory containing `egl.pc'
to the PKG_CONFIG_PATH environment variable
No package 'egl' found

not found

I believe this is some error in the machine file, and more specifically in the sunxi-mali recipe [1], as that should provide egl:

PROVIDES = "virtual/libgles1 virtual/libgles2 virtual/egl"

Are others able to reproduce this as well? Any ideas on how to fix this?

Thanks!

Kristof

[1] https://github.com/linux-sunxi/meta-sunxi/blob/master/recipes-graphics/libgles/sunxi-mali_git.bb

yocto build failed at sunxi-mali git-r0

Hello does someone can help me

i want to build the qt demo recipe from the yocto project just for testing on the cubieboard1 (with the A10) but i've allways get build errors with the sunxi mali repository
the first errors i could resolve using the walkaround from issue #19
just copying all the files from the master branch into the folder but then i've got another error here is the log :

DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
rm -f config.mk
make config.mk
make[1]: Entering directory /home/philipp/poky-dora-10.0.0/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git' make -f Makefile.config ABI="armhf" (Provided) VERSION="r3p0" (Provided) EGL_TYPE="x11" (Provided) make[2]: Entering directory/home/philipp/poky-dora-10.0.0/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git'
Makefile.config:85: *** No Mali libs exist for r3p0, armhf, x11. Stop.
make[2]: Leaving directory /home/philipp/poky-dora-10.0.0/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git' make[1]: *** [config.mk] Error 2 make[1]: Leaving directory/home/philipp/poky-dora-10.0.0/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/git'
make: *** [config] Error 2
WARNING: exit code 2 from a shell command.
ERROR: Function failed: do_configure (log file is located at /home/philipp/poky-dora-10.0.0/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sunxi-mali/git-r0/temp/log.do_configure.12679)

maybe someone has a fix for this ?

linux-sunxi / meta-sunxi Goto Github PK

meta-sunxi's Introduction

meta-sunxi's People

Contributors

Stargazers

Watchers

Forkers

meta-sunxi's Issues

Sub-architecture support

Recommend Projects

Recommend Topics

Recommend Org