September 2017 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] built-in modules probe order problem
by Guillaume Gardet 13 Sep '17

13 Sep '17

Hi, I am trying to fix the video output on the BeagleBoard xM (armv7) which is broken since a while. I am nearly done with the config update, but I have a last problem. The TFP410 (HDMI transmitter) has a power-down GPIO handled by another chip, the TWL4030 (module also built-in). The problem is that that TWL4030 is probed _after_ the TFP410 which results in: "tfp410 encoder0: failed to parse PD gpio". How could I probe TWL4030 _before_ the TFP410 (both modules built-in) ? Guillaume -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] built-in modules probe order problem
by Guillaume Gardet 13 Sep '17

13 Sep '17

Hi, I am trying to fix the video output on the BeagleBoard xM which is broken since a while. I am nearly done with the config update, but I have a last problem. The TFP410 (HDMI transmitter) has a power-down GPIO handled by another chip, the TWL4030 (module also built-in). The problem is that that TWL4030 is probed _after_ the TFP410 which results in: "tfp410 encoder0: failed to parse PD gpio". How could I probe TWL4030 _before_ the TFP410 (both modules built-in) ? Guillaume -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] leap 42.3 kernel 4.4.85-22 and vmware kernel modules
by Markus Koßmann 12 Sep '17

12 Sep '17

Hallo; kernel 4.4.85-22 contains some backports from newer kernel versions which break the build of vmware kernel modules. Will vmware release a version of their kernel modules, which is aware of this special case ? Or should vmware users on Leap 42.3 hack vmware kernel module sources or use another (non distribution) kernel , mightbe kernel stable ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] v4.13-rc1 module linking issue
by Andreas Färber 09 Sep '17

09 Sep '17

Hi, I'm facing an error trying to locally build a custom kernel module: make -C /lib/modules/`uname -r`/build M=$PWD make[1]: Entering directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' AR /home/andreas/lora/built-in.o CC [M] /home/andreas/lora/af_lora.o LD [M] /home/andreas/lora/lora.o CC [M] /home/andreas/lora/dev.o LD [M] /home/andreas/lora/lora-dev.o CC [M] /home/andreas/lora/sx1276.o CC [M] /home/andreas/lora/rn2483.o Building modules, stage 2. MODPOST 4 modules CC /home/andreas/lora/lora-dev.mod.o LD [M] /home/andreas/lora/lora-dev.ko ld: cannot find ./arch/arm64/kernel/ftrace-mod.o: No such file or directory make[4]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/scripts/Makefile.modpost:132: /home/andreas/lora/lora-dev.ko] Error 1 make[3]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/Makefile:1525: modules] Error 2 make[2]: *** [Makefile:145: sub-make] Error 2 make[1]: *** [Makefile:24: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' make: *** [Makefile:8: all] Error 2 If I pass KDIR=/lib/modules/4.12.*/build it builds okay. To reproduce: git clone https://github.com/afaerber/lora-modules.git cd lora-modules make It's not specific to that module of mine: make -C /lib/modules/`uname -r`/build M=$PWD make[1]: Entering directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' AR /home/andreas/netx-module/built-in.o CC [M] /home/andreas/netx-module/netx.o Building modules, stage 2. MODPOST 1 modules CC /home/andreas/netx-module/netx.mod.o LD [M] /home/andreas/netx-module/netx.ko ld: cannot find ./arch/arm64/kernel/ftrace-mod.o: No such file or directory make[4]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/scripts/Makefile.modpost:132: /home/andreas/netx-module/netx.ko] Error 1 make[3]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/Makefile:1525: modules] Error 2 make[2]: *** [Makefile:145: sub-make] Error 2 make[1]: *** [Makefile:24: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' make: *** [Makefile:8: all] Error 2 git clone https://github.com/afaerber/netx-module.git cd netx-module make On x86_64 (Leap host) lora-modules.git builds okay. armv7hl 4.13-rc1 packages haven't finished building yet for comparison. Any ideas what's going wrong here? Our config/arm64/default Kconfig? Our kernel[-default]-devel packaging? Something in the upstream kernel? Thanks, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 4

[opensuse-kernel] Frequency of Leap kernel updates
by Takashi Iwai 07 Sep '17

07 Sep '17

Hi, as we're closing to the release of Leap 42.3, I'd like to ask your opinions about the frequency of update kernel releases. For Leap 42.1 and 42.2, I've tried to pick up the update regularly, roughly once per month. For example, below is the list of kernels that have been released for Leap 42.2: 4.4.27-1 20161027 4.4.36-5 * 20161208 4.4.36-8 20161209 4.4.46-11 20170204 4.4.49-16 * 20170219 4.4.57-18.3 * 20170330 4.4.62-18.6 20170421 4.4.70-18.9 20170531 4.4.72-18.12 * 20170619 4.4.73-18.17 20170623 4.4.74-18.20 20170630 The kernels with asterisk are for security updates. My question here is whether this rhythm is ideal for users and from maintenance burden POV. Should the update be triggered more often, a la rolling release like each stable 4.4.x kernel update? Or twice per month? Or better to be less frequently? Release more often would allow catching a regression more quickly, and this would make bug hunting easier. More frequent update is no problem from my kernel branch maintainer side, too, but it'll certainly increase the load for QA. Comments? thanks, Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 19