[Letux-kernel] compile problems

H. Nikolaus Schaller hns at goldelico.com
Tue Jul 24 08:28:00 CEST 2018


Hi Andreas,

> Am 24.07.2018 um 07:29 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> On Mon, 23 Jul 2018 10:02:47 +0200
> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
> 
>> Hi Andreas,
>> I now have merged & built letux-4.18-rc6 (not yet pushed).
>> 
>>> Am 23.07.2018 um 07:47 schrieb Andreas Kemnade <andreas at kemnade.info>:
>>> 
>>> On Sun, 22 Jul 2018 22:17:05 +0200
>>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>>> 
>>> 
>>>>> [    9.171325] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>>>>> [    9.178253] [drm] No driver support for vblank timestamp query.
>>>>> [    9.198577] omapdrm omapdrm.0: Tiled buffers require DMM
>>>>> [    9.207733] fbcon_init: detected unhandled fb_set_par error, error code -16
>>> 
>>> = display problems!
>>>>> [    9.207733] Console: switching to colour frame buffer device 60x40
>>>>> [    9.227874] omapdrm omapdrm.0: fb0: omapdrm frame buffer device
>> 
>> Haven't seen this:
>> 
> At least it is not always there with the rc6.
> 
>> [    7.691253] wwan_on_off_set_power: state 1
>> [    7.695892] wwan_on_off_set_power: done
>> [    7.764709] wwan_on_off_probe: successfully probed
>> [    8.408447] omapdrm omapdrm.0: DMM not available, disable DMM support
>> [    8.460174] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> [    8.502227] [drm] No driver support for vblank timestamp query.
>> [    8.508758] omapdrm omapdrm.0: Tiled buffers require DMM
>> [    8.615325] Console: switching to colour frame buffer device 60x40
>> [    8.691711] omapdrm omapdrm.0: fb0: omapdrm frame buffer device
>> [    8.716918] cfg80211: Loading compiled-in X.509 certificates for regulatory database
>> [    8.726501] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0
>> [    8.767608] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>> [    8.785064] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
>> [    8.796966] cfg80211: failed to load regulatory.db
>> 
>>>>> [    9.234252] ---[ end trace 8c96d4db1da6a489 ]---
>>>>> [    9.262847] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0
>>>>> [    9.418731] cfg80211: Loading compiled-in X.509 certificates for regulatory database
>>>>> [    9.486663] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>>>>> [    9.543640] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
>>>>> [    9.571105] cfg80211: failed to load regulatory.db
>> 
>> And I haven't seen the iio related error. Maybe something spurious or
>> is it repeatable for you? Then it could be an effect based on different
>> boot procedure (assuming you boot through serial/usb - I did boot from
>> U-Boot with Josuas and your DFU fixes in NAND and kernel on µSD).
>> 
> My X setup tries to talk with the accelerometer but then ignores it. Maybe that is different
> 
> [   246.821] (II) config/udev: Adding input device accelerometer-iio-input-bridge (/dev/input/event6)
> [   246.821] (II) No input driver specified, ignoring this device.
> [   246.821] (II) This device may have been added with another device file.
> [   246.822] (II) config/udev: Adding input device accelerometer-iio-input-bridge (/dev/input/js0)
> [   246.822] (II) No input driver specified, ignoring this device.
> [   246.822] (II) This device may have been added with another device
> file.
> 
> Maybe that is not the case in your setup. xxd /dev/input/event6 (or wherever the bridge is) spits out
> data in earlier kernels but not in 4.18-rc6.

For me it works:

root at letux:~# evtest /dev/input/event3
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "accelerometer-iio-input-bridge"
Supported events:
  Event type 0 (EV_SYN)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value     16
      Min     -511
      Max      511
    Event code 1 (ABS_Y)
      Value     -1
      Min     -511
      Max      511
    Event code 2 (ABS_Z)
      Value    246
      Min     -511
      Max      511
Properties:
Testing ... (interrupt to exit)
Event: time 1532413320.083504, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1532413320.083504, -------------- EV_SYN ------------
Event: time 1532413320.194400, type 3 (EV_ABS), code 0 (ABS_X), value 28
Event: time 1532413320.194400, type 3 (EV_ABS), code 1 (ABS_Y), value 2
Event: time 1532413320.194400, type 3 (EV_ABS), code 2 (ABS_Z), value 243
Event: time 1532413320.194400, -------------- EV_SYN ------------
Event: time 1532413320.304318, type 3 (EV_ABS), code 0 (ABS_X), value 27
Event: time 1532413320.304318, type 3 (EV_ABS), code 2 (ABS_Z), value 242
Event: time 1532413320.304318, -------------- EV_SYN ------------
Event: time 1532413320.413718, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 1532413320.413718, type 3 (EV_ABS), code 2 (ABS_Z), value 241
Event: time 1532413320.413718, -------------- EV_SYN ------------
Event: time 1532413320.963586, type 3 (EV_ABS), code 2 (ABS_Z), value 240
Event: time 1532413320.963586, -------------- EV_SYN ------------
Event: time 1532413321.072619, type 3 (EV_ABS), code 2 (ABS_Z), value 241
Event: time 1532413321.072619, -------------- EV_SYN ------------
Event: time 1532413321.182996, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1532413321.182996, -------------- EV_SYN ------------
Event: time 1532413321.294349, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 1532413321.294349, -------------- EV_SYN ------------
Event: time 1532413321.403687, type 3 (EV_ABS), code 0 (ABS_X), value 28
Event: time 1532413321.403687, -------------- EV_SYN ------------
Event: time 1532413321.623738, type 3 (EV_ABS), code 0 (ABS_X), value 27
Event: time 1532413321.623738, type 3 (EV_ABS), code 2 (ABS_Z), value 240
Event: time 1532413321.623738, -------------- EV_SYN ------------
Event: time 1532413321.734023, type 3 (EV_ABS), code 0 (ABS_X), value 28
Event: time 1532413321.734023, type 3 (EV_ABS), code 2 (ABS_Z), value 241
Event: time 1532413321.734023, -------------- EV_SYN ------------
Event: time 1532413321.843331, type 3 (EV_ABS), code 0 (ABS_X), value 27
Event: time 1532413321.843331, type 3 (EV_ABS), code 2 (ABS_Z), value 240
Event: time 1532413321.843331, -------------- EV_SYN ------------
^C
root at letux:~# uname -a
Linux letux 4.18.0-rc6-letux+ #2551 SMP PREEMPT Mon Jul 23 08:05:46 CEST 2018 armv7l GNU/Linuxroot at letux:~# dmesg|fgrep input
[    3.208038] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    3.216705] input: gpio-keys-wwan-wakeup as /devices/platform/gpio-keys-wwan-wakeup/input/input1
[    3.237121] input: antenna-detect as /devices/platform/antenna-detect/input/input2
[   10.392486] input: twl4030_pwrbutton as /devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl at 48:pwrbutton/input/input3
[   10.425750] input: twl4030:vibrator as /devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl at 48:audio/twl4030-vibra/input/input4
[   10.461761] input: accelerometer-iio-input-bridge as /devices/virtual/input/input5
[   10.683471] input: TSC2007 Touchscreen as /devices/platform/68000000.ocp/48072000.i2c/i2c-1/1-0048/input/input6
root at letux:~#

But that doesn't solve your problem. It looks as if the kernel is generally
not running stable on your device and showing spurious bugs. Either in bitmap
console, or here in iio.

Could you please try my compiled binary to exclude a compiler issue?

http://download.goldelico.com/letux-kernel/letux-4.18-rc6/

BR,
Nikolaus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.goldelico.com/pipermail/letux-kernel/attachments/20180724/80cbf242/attachment-0001.asc>


More information about the Letux-kernel mailing list