[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANpvso4etXYFsC=0KfDayTFp-Zo+-m1xBzii0g71wq14uDF2aw@mail.gmail.com>
Date: Tue, 29 Sep 2015 15:47:10 +0100
From: Eric Curtin <ericcurtin17@...il.com>
To: Austin S Hemmelgarn <ahferroin7@...il.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Valentina Manea <valentina.manea.m@...il.com>,
Shuah Khan <shuah.kh@...sung.com>,
USB list <linux-usb@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: First kernel patch (optimization)
On 29 September 2015 at 14:51, Austin S Hemmelgarn <ahferroin7@...il.com> wrote:
> On 2015-09-26 09:28, Eric Curtin wrote:
>>
>> Hi Dimitry,
>>
>>> Is it Debian-derivative by any chance? Their capslock setup is wonky
>>> because CapsLock key does no actually set up as a CapsLock but another
>>> modifier. Also is it in X or is it on text console? Because X handles
>>> led state on its own...
>>
>>
>> I'm on Fedora 22. Yeah, you're correct X is handling this, the led does
>> not turn on at all in text console. Tried Wayland also for the first time
>> to see if it occurred there also, it does. Does this mean I should not be
>> looking at kernel code all to fix this issue and I should be looking at
>> X/Wayland?
>
> If the led doesn't turn on on the console either, then it may be worth
> looking at kernel code, but it may be in the console driver instead of the
> input layer driver.
>
I may have been incomplete earlier. The led does not turn on at all in
console. In X the led does turn on, but does not switch off correctly.
I'm looking at kernel code, still assuming I can fix it in here.
--
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/
Powered by blists - more mailing lists