linux-kernel - Re: [PATCH] Route kbd LEDs through the generic LEDs layer (5th version)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100321211653.GS12469@const.famille.thibault.fr>
Date:	Sun, 21 Mar 2010 22:16:53 +0100
From:	Samuel Thibault <samuel.thibault@...-lyon.org>
To:	Pavel Machek <pavel@....cz>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	alan@...rguk.ukuu.org.uk, mgarski@...t.pl,
	linux-input@...r.kernel.org, Vojtech Pavlik <vojtech@...e.cz>,
	Richard Purdie <rpurdie@...ys.net>
Subject: Re: [PATCH] Route kbd LEDs through the generic LEDs layer (5th version)

Pavel Machek, le Sun 21 Mar 2010 22:09:38 +0100, a écrit :
> Now, minor comments:
> 
> sometimes it uses "numl" (led name), sometimes it uses "numlock"
> trigger name.

Yes, I preferred to stick to the existing names: numl like LED_NUML, and
numlock like VC_NUMLOCK.  I don't have any opinion on this however.

> root@amd:/sys/class/leds/input5::numl# echo heartbeat > trigger
> 
> did not do the trick on my thinkpad. It still acts as numlock led. Is
> it driven by hw? input5::capsl works as expected.

If it is a laptop, it is likely, depending on the BIOS & such.
On my laptop, doing this works fine.

Samuel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/