src/sys/dev/atkbdc, branch releng/7.3

MFC r191164

2009-04-20T16:55:48Z

Prevent atkbd(4) interrupt handler from calling keyboard callback function when polled mode is enabled. This should help with duplicated/missing characters problem at mountroot, geli, etc. prompts on multi CPU systems while kbdmux(4) is enabled. Tested by: Tobias Grosser Tested by: Fabian Keil Approved by: re (kib)

Merge 189870

2009-03-19T07:40:41Z

Teach psm about O_ASYNC This makes Xorg happy if you aren't using moused.

MFC r179474:

2008-06-08T09:06:45Z

Try to detect a Synaptics touchpad before IntelliMouse. Some touchpads will pretend to be IntelliMouse (which have a few more features than generic mice) causing the IntelliMouse probe to work and the Synaptics code never to be called. This should not break "real" IntelliMouse because the Synaptics detection code is fairly specific. PR: kern/120833 Submitted by: Eygene Ryabinkin

MFC: 1.95, 1.96

2008-04-15T17:41:52Z

- Add write(2) support for psm(4) in native operation level. Now arbitrary commands can be written to /dev/psm%d and status can be read back from it. - Clean up and fix style(9) nits.

MFC:

2008-04-01T08:05:30Z

Some PS/2 mice (at least the A4Tech X-7xx) need to be set to Intelli mode first before they can be set to Explorer mode. PR: kern/118578 Submitted by: Andriy Gapon (I added some comments) Reviewed by: philip

Initialize mouse resolution to zero if converting from

2007-06-17T04:32:18Z

OLD to NEW.

o break newbus api: add a new argument of type driver_filter_t to

2007-02-23T12:19:07Z

bus_setup_intr() o add an int return code to all fast handlers o retire INTR_FAST/IH_FAST For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current Reviewed by: many Approved by: re@

Synaptics TouchPad seems to go back to Relative Mode after the call

2007-02-04T12:47:52Z

to set_controller_command_byte() call; by issueing a Read Mode Byte command, the touchpad is in Absolute Mode again. This problem occursed at least on Asus V6V laptops.

Spell "Kensington Thinking Mouse" correctly.

2006-12-18T18:48:28Z

Fix LEDs not working when atkbd is an active keyboard and the physical

2006-10-25T13:35:42Z

keyboard is attached only after the system has already booted. If USB keyboard is also present, and there's no kbdmux(4), the problem has been hiding itself because as soon as we get to multi-user, the USB keyboard becomes an active keyboard (see devd.conf), thus marking atkbd inactive and letting the old code initialize the keyboard. With kbdmux(4), or if there's no USB keyboard, the atkbd keyboard is always active, whether it's physically attached or not, thus it never initialized itself properly on a physical attach. To fix this, move block that initialized the keyboard on attach upper so it doesn't depend on the (KBD_IS_ACTIVE(kbd) && KBD_IS_BUSY(kbd)) condition. Also move KBD_FOUND_DEVICE() a few lines upper so that KDSETLED and KDSETREPEAT that follow it propagate to the controller. MFC after: 3 days