From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: linux-input@vger.kernel.org
Cc: nikola.ciprich@linuxbox.cz, dmitry.torokhov@gmail.com
Subject: 4.10 regression: d79e141c1c6ea7cb70c169971d522b88c8d5b419 breaks PS/2 barcode readers
Date: Sat, 10 Feb 2018 19:04:11 +0100 [thread overview]
Message-ID: <20180210180411.GC16967@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Hi,
after switching to 4.14 from 4.4 we noticed LS2208 PS/2 barcode stopped
working for us (on Lenovo desktops equipped with USB keyboards). If I plug
PS/2 keyboard, reader works.. (it's cable works as PS/2 splitter).
Digging deeper into this, I noticed kernel stopped probing PS/2 ports directly,
which seems to be caused by d79e141c1c6ea7cb70c169971d522b88c8d5b419,
reverting
+ if (x86_platform.legacy.i8042 !=
+ X86_LEGACY_I8042_EXPECTED_PRESENT)
+ return -ENODEV;
part makes reader working again (without PS/2 keyboard plugged), as well
as using i8042.nopnp.
My question is, what might best solution for that be? Could this be
solved by some quirk? I haven't found any similar to get some idea..
If I could provide some more details, please let me know..
BR
nik
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 00 Ostrava
tel.: +420 591 166 214
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2018-02-10 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180210180411.GC16967@localhost.localdomain \
--to=nikola.ciprich@linuxbox.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).