(06-09-2016, 02:08 AM)Artyom Wrote: [ -> ] (06-09-2016, 12:22 AM)umiddelb Wrote: [ -> ] (05-29-2016, 02:35 AM)Artyom Wrote: [ -> ]. Hi again. Аs I said earlier we need new kernel. As far as I understand we need kernel version 3.18.11. Additionally, you can read here:
https://patches.linaro.org/patch/47092/
https://patches.linaro.org/patch/47646/
Hm, I wouldn't go for the 3.18 kernel since a mainline kernel (4.7) is about to be issued in the next couple of weeks.
Read links. And tell me what you think.
As i undestand in the nex few week we have new kernel (4.7) with Pine64 support? I am right?
(06-09-2016, 07:49 AM)Artyom Wrote: [ -> ] (06-09-2016, 02:08 AM)Artyom Wrote: [ -> ] (06-09-2016, 12:22 AM)umiddelb Wrote: [ -> ] (05-29-2016, 02:35 AM)Artyom Wrote: [ -> ]. Hi again. Аs I said earlier we need new kernel. As far as I understand we need kernel version 3.18.11. Additionally, you can read here:
https://patches.linaro.org/patch/47092/
https://patches.linaro.org/patch/47646/
Hm, I wouldn't go for the 3.18 kernel since a mainline kernel (4.7) is about to be issued in the next couple of weeks.
Read links. And tell me what you think.
As i undestand in the nex few week we have new kernel (4.7) with Pine64 support? I am right?
Sunxi developers currently work hard on the mainline kernel development. For the status, you can check on Sunxi site or participate if you interest to contribute. Kudos to Sunxi community.
(06-09-2016, 07:30 PM)tllim Wrote: [ -> ] (06-09-2016, 07:49 AM)Artyom Wrote: [ -> ] (06-09-2016, 02:08 AM)Artyom Wrote: [ -> ] (06-09-2016, 12:22 AM)umiddelb Wrote: [ -> ] (05-29-2016, 02:35 AM)Artyom Wrote: [ -> ]. Hi again. Аs I said earlier we need new kernel. As far as I understand we need kernel version 3.18.11. Additionally, you can read here:
https://patches.linaro.org/patch/47092/
https://patches.linaro.org/patch/47646/
Hm, I wouldn't go for the 3.18 kernel since a mainline kernel (4.7) is about to be issued in the next couple of weeks.
Read links. And tell me what you think.
As i undestand in the nex few week we have new kernel (4.7) with Pine64 support? I am right?
Sunxi developers currently work hard on the mainline kernel development. For the status, you can check on Sunxi site or participate if you interest to contribute. Kudos to Sunxi community.
Hi TLLIM. Please post link.
Hi
,
since we have a more or less working 4.9 mainline kernel, I was able to apply the latest PREEMPT_RT patches against 4.9.6.
You will find the kernel sources
here and a ready to extract kernel image
here. If you want to modify some of the kernel configuration parameters, I can give you some advice how to do this and how to build a kernel on your own Pine64.
Cheers
Uli
Hi,
I'm wanting to build a rt system for digital audio (squeezebox) using a pine64+ (2GB) running Armbian base system.
I've been trying to apply the
https://www.kernel.org/pub/linux/kernel/...s/rt/3.10/
patch-3.10.104-rt117 patch set on the Armbian 3.10.104 source tree, following the procedure outlined in the developer guide.
https://docs.armbian.com/Developer-Guide...eparation/
The patches are applied successfully, but I am facing a number of problems with the build.
There were failures in various IP tunnelling modules, which I have simply removed from the config, as I don't need them, but now I'm struggling with:
Code:
MODPOST vmlinux.o │
│ WARNING: modpost: Found 2 section mismatch(es). │
│ To see full details build your kernel with: │
│ 'make CONFIG_DEBUG_SECTION_MISMATCH=y' │
│ GEN .version │
│ CHK include/generated/compile.h │
│ UPD include/generated/compile.h │
│ CC init/version.o │
│ LD init/built-in.o │
│ drivers/built-in.o: In function `mbus_pmu_remove': │
│ arisc_dram_crc.c:(.text+0x1d38): undefined reference to `hwmon_device_unregister' │
│ arisc_dram_crc.c:(.text+0x1d38): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `hwmon_device_unregister' │
│ drivers/built-in.o: In function `mbus_pmu_probe':
Can anyone suggest how to fix it?
I want to stay with 3.10.104 as vanilla doesn't support the LCD interface (which I need for the touch screen).
BR.
--Marius--
(02-08-2017, 03:06 AM)Learnincurve Wrote: [ -> ]Hi,
I'm wanting to build a rt system for digital audio (squeezebox) using a pine64+ (2GB) running Armbian base system.
I've been trying to apply the https://www.kernel.org/pub/linux/kernel/...s/rt/3.10/
patch-3.10.104-rt117 patch set on the Armbian 3.10.104 source tree, following the procedure outlined in the developer guide.
https://docs.armbian.com/Developer-Guide...eparation/
The patches are applied successfully, but I am facing a number of problems with the build.
There were failures in various IP tunnelling modules, which I have simply removed from the config, as I don't need them, but now I'm struggling with:
Code:
MODPOST vmlinux.o │
│ WARNING: modpost: Found 2 section mismatch(es). │
│ To see full details build your kernel with: │
│ 'make CONFIG_DEBUG_SECTION_MISMATCH=y' │
│ GEN .version │
│ CHK include/generated/compile.h │
│ UPD include/generated/compile.h │
│ CC init/version.o │
│ LD init/built-in.o │
│ drivers/built-in.o: In function `mbus_pmu_remove': │
│ arisc_dram_crc.c:(.text+0x1d38): undefined reference to `hwmon_device_unregister' │
│ arisc_dram_crc.c:(.text+0x1d38): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `hwmon_device_unregister' │
│ drivers/built-in.o: In function `mbus_pmu_probe':
Can anyone suggest how to fix it?
I want to stay with 3.10.104 as vanilla doesn't support the LCD interface (which I need for the touch screen).
BR.
--Marius--
You may try to enable CONFIG_HWMON=y in your config.
Cheers
Uli
Thanks umiddelb!
Compilation goes through now, with CONFIG_HWMON compiled in, rather than as a loadable module.
