| Age | Commit message (Collapse) | Author |
|---|
|
If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!
mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!
ok miod@, mlarkin@, deraadt@, shadchin@
|
|
after discussions with beck deraadt kettenis.
|
|
code was masking out bits which were also tested in the same expression.
Reported by cppcheck via jsg@ (Expression '(X & 0xfc) != 0x2' is always true).
Tested with Elantech Touchpad, version 3, firmware 0x250f00.
|
|
device of type PMS_STANDARD, probing during autoconf(9) is enough!.
In such case, the device can be a simple PS/2 mouse, a unsupported
touchpad or a downgraded touchpad if something bad happened. But
it is very unlikely that reprobing will improve the situation and
transform a standard mouse into a multitouch-aware touchpad ;)
This fixes the 12 seconds delay seen on various Dell laptops (E4310
and Latitude D630) when starting Xorg, reported by KÄrlis MiÄ·elsons
on bugs@.
ok stsp@, dcoppa@, shadchin@
|
|
|
|
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.
ok deraadt, kettenis
|
|
kernels:
- keyboard drivers will now tell wskbd if the keyboard layout they ask
for is a default value, or a value they are 100% sure of (either
because your kernel has a XXXKBD_LAYOUT option, or because the
driver can tell the keyboard layout, e.g. by the country code on USB
keyboards which provide it, such as Sun's)
- when attaching a keyboard with a non-default layout, the layout will
become the default layout of the mux for new keyboard attachments if
the mux doesn't have a layout set already.
- when changing the keyboard layout of a particular keyboard with an
ioctl (i.e. using kbd(8) or wsconsctl(8)), the layout will become the
default layout of the mux for new keyboard attachments.
ok mpi@
|
|
Send WSCONS_EVENT_SYNC every time you call wsmouse_input(). Used to synchronize
and separate events into packets of input data changes occurring at the same
moment in time. For example, motion of a mouse may set the DELTA_X and DELTA_Y
values for one motion, then emit a SYNC.
ok matthieu@. tested edd@, Henri Kemppainen and Alf Schlichting.
|
|
The synaptics driver now attaches to elantech v2 touchpads. It seems these
pads were always falling back to compat mode, which went unnoticed until r1.47.
Fix based on a patch submitted by Cedric Tessier:
http://marc.info/?l=openbsd-bugs&m=136904396518528&w=2
which in turn was probably based on parts of this patch:
https://launchpadlibrarian.net/73099683/elantech.patch
which updates the Linux driver code but isn't part of Torvald's Linux.
Behaviour of elantech firmware versions seems to vary quite a bit so print
the firmware version at attach time for reference in future bug reports.
Fix tested by frantisek holop and Peter J. Philipp.
ok mpi@
|
|
are still taking time to wake up. So make the pms(4) driver wait a little
longer before giving up on them. Fixes mouse after resume on my x130e TP.
ok mpi, earlier versions tested by weerd with no regressions seen
|
|
identified during attach. This prevents the driver to downgrade itself
to use the standard mouse protocol and reattach a new wsmouse child if
something bad happens when we re-query the hardware (during resume for
example).
Discussed with and ok stsp@
|
|
to wsmouse_input() when no finger are reported.
Pointed out by Maxime Villard.
|
|
pointed out by Owain G. Ainsworth
|
|
tested on an asus ux21a
ok mpi@ stsp@
|
|
for chipsets which stopped working.
ok mpi
|
|
Supported for i386 and amd64 except SMALL_KERNEL.
Based on Miod's former work on this subject.
ok mpi
|
|
by Peter J. Philipp, thanks.
|
|
touchpads support both of them and we want to pick the latter.
Reported by Peter J. Philipp, thanks.
|
|
makes it harder to pick the right protocol if a device answers to more than
one magic sequence.
Tested by many on tech@, ok shadchin@
|
|
From "Creamy" on tech@
|
|
versions. Fixes a problem reported by Peter J. Philipp where the pms driver
spits out "not in sync yet" messages after attaching to elantech v2 hardware.
Fix tested by me on v3 hardware, and by Peter on v2 hardware.
ok mpi@ shadchin@
|
|
ok mpi@ shadchin@
|
|
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.
|
|
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.
feedback from many, ok shadchin@
|
|
Also small simplify elantech part.
ok stsp@, mpi@
|
|
hardware variants. ok shadchin mikeb mpi
|
|
Fix by oga, via mikeb.
|
|
input driver to configure these touchpads properly, e.g. toggle tap-to-click,
two-finger scrolling, edge-scrolling, etc. So far these pads were working
only in PS/2 mouse compatibility mode.
Support for up to hardware version 3 has been implemented. But only version 3
has been tested so versions 1 and 2 remain disabled via #ifdef notyet until
someone tests (bugs in this code could seriously mess up the mouse and I
don't want to end up shipping such bugs in 5.3).
help and ok mpi@ shadchin@
|
|
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success
ok miod@
|
|
ok gilles@, matthieu@, mpi@, miod@, deraadt@
|
|
reported pressure is non-null. Fix the use of ALPS touchpads with recent
(>1.6) xf86-input-synaptics drivers, issue reported by janis at cieti lv.
Tested by yasuoka@ and janis, ok shadchin@
|
|
ok mpi@
|
|
which send 'interleaved' PS2 packets in between absolute ALPS packets.
Dell laptops (E6xxx and E5500 at least) have this kind of touchpad.
ok and some rework mpi@, tested okan@.
|
|
Issue reported by deraadt@
|
|
(synaptics and alps uses this for trackpoint)
ok mpi@
|
|
reported by espie@, not reported by miod@
with and ok shadchin@, ok espie@
|
|
|
|
on misc@
Similar diff tested by okan@ and Mathieu (ptr.jetable)
ok shadchin@
|
|
This also fix the "slow touchpad" problem due to the fact that some ALPS
devices respond to some Synaptics messages and stay in un half-configured
state.
Tested by Rivo Nurges, armani@, shadchin@ and matthieu@
ok shadchin@
|
|
the accuracy detection ALPS.
ok mpi@
|
|
This fixed "react strangely" when the pms driver probes
for a synaptic-compatible touchpad.
Tested and ok mpi@
|
|
ok miod@, matthieu@
|
|
|
|
ok miod@
|
|
ok krw, miod
|
|
ok krw, miod
|
|
ok krw, miod
|
|
after boot and before the first activation (wsmoused or X),
sc->protocol is not initialized, and any call ioctl lead to crash
(example 'wsconsctl -a')
thanks and ok krw@
|
|
This is to make it easier to add additional mice types in future
ok krw@, miod@, nicm@
|
|
ok miod@
|
