I've been going around with Jorge for a couple of days with this. He
doesn't see the error but I do using make 4.0. I have spoken with
Vishal and he sees this error with make 3.81, and tells me Fathi sees
this error in local builds. Is anyone else seeing the following?
When I build this branch locally, I get the following error:
/media/scottb/linaro/hikey/source/linux/drivers/gpu/arm/utgard/Kbuild:37:
*** DMA-BUF is incompatible with non-GPL license. Stop.
/media/scottb/linaro/hikey/source/linux/scripts/Makefile.build:416:
recipe for target 'drivers/gpu/arm/utgard' failed
make[4]: *** [drivers/gpu/arm/utgard] Error 2
/media/scottb/linaro/hikey/source/linux/scripts/Makefile.build:416:
recipe for target 'drivers/gpu/arm' failed
make[3]: *** [drivers/gpu/arm] Error 2
/media/scottb/linaro/hikey/source/linux/scripts/Makefile.build:416:
recipe for target 'drivers/gpu' failed
make[2]: *** [drivers/gpu] Error 2
/media/scottb/linaro/hikey/source/linux/Makefile:957: recipe for
target 'drivers' failed
make[1]: *** [drivers] Error 2
make[1]: Leaving directory
'/media/scottb/linaro/kernel/output/kernel-hikey-mali'
Makefile:145: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
This error is from: drivers/gpu/arm/utgard/Kbuild
The above makefile has the following script in it:
# For customer releases the Linux Device Drivers will be provided as
ARM proprietary and GPL releases:
# The ARM proprietary product will only include the
license/proprietary directory
# The GPL product will only include the license/gpl directory
ifeq ($(wildcard $(src)/linux/license/gpl/*),)
ccflags-y += -I$(src)/linux/license/proprietary
ifeq ($(CONFIG_MALI400_PROFILING),y)
$(error Profiling is incompatible with non-GPL license)
endif
ifeq ($(CONFIG_PM_RUNTIME),y)
$(error Runtime PM is incompatible with non-GPL license)
endif
ifeq ($(CONFIG_DMA_SHARED_BUFFER),y)
$(error DMA-BUF is incompatible with non-GPL license)
endif
$(error Linux Device integration is incompatible with non-GPL license)
else
ccflags-y += -I$(src)/linux/license/gpl
endif
The condition is failing:
ifeq ($(wildcard $(src)/linux/license/gpl/*),)
$(src) is "drivers/gpu/arm/utgard"
drivers/gpu/arm/utgard/linux/license/gpl contains file mali_kernel_license.h
wildcard $(src)/linux/license/gpl/* should return
"mali_kernel_license.h" but actually returns ""
hence the code assumes we are using a proprietary license, and dies
because we are using DMA_BUF.
Anyone have any thoughts?
Since we know we are using GPL code, an easy workaround is to comment
out all the code, except for:
ccflags-y += -I$(src)/linux/license/gpl
Scott
--
Scott Bambrough
Technical Director, Member Services
Linaro
This patch uses the correct API to report the arm64 topology to the
scheduler.
arch/arm64/kernel/topology.c | 56 ++++++++++++++++++++++----------------------
1 file changed, 28 insertions(+), 28 deletions(-)
This series is to polish pinumx setting in dts so that can easily
maintain and add items as needed.
In the old code, it sets pinmux for every pin one by one; so one
patch will group pinmux setting according to pins binding to device
modules, which can be easily maintain compare to old implementation.
Also polish pinmux's gpio range with more readable format.
Leo Yan (2):
dts: hi6220: use readable setting for gpio range
dts: hikey: set pinmux base on module
arch/arm64/boot/dts/hi6220-hikey.dts | 136 +-
arch/arm64/boot/dts/hi6220.dtsi | 77 +-
arch/arm64/boot/dts/hikey-pinctrl.dtsi | 3228 ++++++--------------------------
3 files changed, 589 insertions(+), 2852 deletions(-)
--
1.9.1
Hi,
After upgrading UEFI with fastboot.efi:
NOTICE: BL1: Built : 08:51:46, Apr 7 2015
...
NOTICE: BL2: Built : 13:51:24, Apr 16 2015
So the BL1 is now out of sync with rest. I tried updating fastboot1
partition without success:
fastboot flash fastboot1 l-loader.bin
..
FAILED (remote: No such partition.)
Is the only way to update BL1 via hisi-idt.py and jumper?
Riku
Hi,
I have setup a hikey build using angstrom-next:
$ git clone git://github.com/angstrom-distribution/setup-scripts.git
$ cd setup-scripts
$ git checkout next
$ MACHINE=hikey ./oebb.sh config hikey
$ source environment-angstrom
$ bitbake-layers add-layer <path to angstrom's meta-96boards>
$ bitbake console-image
While building the kernel (linux-hikey_3.18) my build fails with:
/home/trevor/devel/yocto/hikey/board1/angstrom/next/build/tmp-glibc/work-shared/hikey/kernel-source/drivers/gpu/arm/utgard/Kbuild:37:
*** DMA-BUF is incompatible with non-GPL license. Stop.
make[5]: *** [drivers/gpu/arm/utgard] Error 2
make[4]: *** [drivers/gpu/arm] Error 2
make[3]: *** [drivers/gpu] Error 2
make[2]: *** [drivers] Error 2
make[2]: *** Waiting for unfinished jobs....
Any thoughts on why this might be happening?
Thanks and best regards,
Trevor
The following statement doesn't have consistent behaviour on all machines:
$(wildcard $(src)/linux/license/gpl/*)
On some it actually returns the name of the GPL header file, on others it is a blank string.
Since the driver is in-tree, we can assume GPL compliance.
---
drivers/gpu/arm/utgard/Kbuild | 19 ++-----------------
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/drivers/gpu/arm/utgard/Kbuild b/drivers/gpu/arm/utgard/Kbuild
index 78f5f32..f586f8d 100644
--- a/drivers/gpu/arm/utgard/Kbuild
+++ b/drivers/gpu/arm/utgard/Kbuild
@@ -23,23 +23,8 @@ MALI_UPPER_HALF_SCHEDULING ?= 1
MALI_ENABLE_CPU_CYCLES ?= 0
# For customer releases the Linux Device Drivers will be provided as ARM proprietary and GPL releases:
-# The ARM proprietary product will only include the license/proprietary directory
-# The GPL product will only include the license/gpl directory
-ifeq ($(wildcard $(src)/linux/license/gpl/*),)
- ccflags-y += -I$(src)/linux/license/proprietary
- ifeq ($(CONFIG_MALI400_PROFILING),y)
- $(error Profiling is incompatible with non-GPL license)
- endif
- ifeq ($(CONFIG_PM_RUNTIME),y)
- $(error Runtime PM is incompatible with non-GPL license)
- endif
- ifeq ($(CONFIG_DMA_SHARED_BUFFER),y)
- $(error DMA-BUF is incompatible with non-GPL license)
- endif
- $(error Linux Device integration is incompatible with non-GPL license)
-else
- ccflags-y += -I$(src)/linux/license/gpl
-endif
+# The in-tree driver will only use the GPL releases.
+ccflags-y += -I$(src)/linux/license/gpl
ifeq ($(USING_GPU_UTILIZATION), 1)
ifeq ($(USING_DVFS), 1)
--
2.1.0
Hi all,
Now NVME feature is enabled in UEFI. The variable could be saved in
eMMC, although there's one issue on it. And this feature is merged
into UEFI in github of 96boards. You can test it now.
If you only create a new variable in UEFI, it works well.
If you update the variable with multiple times (more than two),
sometimes you'll fail to find the variable after reboot. In this case,
we have to reflush the NVME parition in eMMC. Up to now, it's the only
one workaround. I'll continue to investigate this issue.
When we check the eMMC device, we could find the variable are already
flushed into eMMC. Old variables are marked deleted state (0x3d)
already. And new variable is marked as added state (0x3f).
Best Regards
Haojian
