Thanks a lot. After apw's comment on IRC I expected something in the
next weeks :-)
I can just tell you it boots and seems to work. When I tried to manually
build my hw-support-dkms against the kernel I got:
LANG=C ./r
+ pwd
+ make -C /usr/src/linux-headers-4.4.0-112-generic M=/home/glg/mod
make: Entering directory `/usr/src/linux-headers-4.4.0-112-generic'
Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
-fstack-protector-strong not supported by compiler
CC [M] /home/glg/mod/fujitsu-laptop.o
gcc: error: unrecognized command line option '-fstack-protector-strong'
make[1]: *** [/home/glg/mod/fujitsu-laptop.o] Error 1
make: *** [_module_/home/glg/mod] Error 2
make: Leaving directory `/usr/src/linux-headers-4.4.0-112-generic'
So I guess this kernel was build on Xenial, which I don't have
installed. I have Trusty and Bionic, which has the upstream patch
included.
But generally it looks ok'ish, as rfkill-any shows up:
$ cat /sys/class/leds/input2\:\:capslock/trigger
none rfkill-any kbd-scrolllock kbd-numlock [kbd-capslock] kbd-kanalock
kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock
kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full
CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0
cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc
phy0radio
For a test I used the the caspslock led and manually set the soft
rfkill, which triggers the led correctly:
$ echo "rfkill-any" | sudo tee /sys/class/leds/input2\:\:capslock/trigger
rfkill-any
$ cat /sys/class/leds/input2\:\:capslock/trigger
none [rfkill-any] kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock
kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock
kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full
CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0
cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc
phy0radio
=> capslock led is on
$ sudo rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
$ sudo rfkill block 0
$ sudo rfkill block 1
=> capslock led is off
I tried all combinations of block and unblock.
No stacks in the dmesg.
So I guess it works as expected.
If you can provide a Trusty based kernel, I'll test it tomorrow.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745130
Title:
Support rfkill-any led trigger for Fujitsu u727
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based
on Skylake hardware.
It has a single rfkill button and a single LED for wlan and bluetooth. Both
device driver currently provide a single rfkill trigger, so the led could just
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led
trigger to correctly handle the led with multiple rfkill devices. That was
added by one of the fujitsu-laptop maintainers and the driver sets it as the
default trigger.
commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
Author: Michał Kępień <[email protected]>
Date: Fri Jan 6 07:07:47 2017 +0100
rfkill: Add rfkill-any LED trigger
Normally I would simply patch the affected modules using DKMS, like the
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW
without messing with the kernel packages.
I'm currently waiting for some reviews, like
https://www.spinics.net/lists/platform-driver-x86/msg14606.html
But the rfkill support is compiled in, so I can't patch it using DKMS.
So my first proposed fix would be to include a backport of this patch.
Alternatively rfkill can be compiled as a module, so I can patch it
and provide an updated module.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-111-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Wed Jan 24 10:48:28 2018
SourcePackage: linux-lts-xenial
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
