src/sys/dev/adb, branch release/8.1.0

MFC r199888:

2009-12-12T02:34:00Z

Add support for interpreting taps on ADB touchpads as a button click. Submitted by: Andreas Tobler

MFC 196403: Temporarily revert the new-bus locking for 8.0 release.

2009-08-20T20:23:28Z

Approved by: re (kib)

Make the newbus subsystem Giant free by adding the new newbus sxlock.

2009-08-02T14:28:40Z

The newbus lock is responsible for protecting newbus internIal structures, device states and devclass flags. It is necessary to hold it when all such datas are accessed. For the other operations, softc locking should ensure enough protection to avoid races. Newbus lock is automatically held when virtual operations on the device and bus are invoked when loading the driver or when the suspend/resume take place. For other 'spourious' operations trying to access/modify the newbus topology, newbus lock needs to be automatically acquired and dropped. For the moment Giant is also acquired in some key point (modules subsystem) in order to avoid problems before the 8.0 release as module handlers could make assumptions about it. This Giant locking should go just after the release happens. Please keep in mind that the public interface can be expanded in order to provide more support, if there are really necessities at some point and also some bugs could arise as long as the patch needs a bit of further testing. Bump __FreeBSD_version in order to reflect the newbus lock introduction. Reviewed by: ed, hps, jhb, imp, mav, scottl No answer by: ariff, thompsa, yongari Tested by: pho, G. Trematerra , Brandon Gooch Sponsored by: Yahoo! Incorporated Approved by: re (ksmith)

Use si_drv1 to hold the softc for the adb_mouse character device instead of

2009-01-29T16:18:49Z

using devclass_get_softc(). Tested by: nwhitehorn

Make adb_mouse use dev2unit() instead of minor().

2009-01-29T05:59:42Z

A real fix would be to migrate it to si_drv0 to store the softc directly, but this is the quickest way to fix it right now.

Improve the AT keyboard emulation of the ADB keyboard driver, by supporting

2009-01-08T17:47:45Z

an AT-like K_RAW mode instead of just K_CODE. This has the effect of making the arrow keys on ADB keyboards work in X11. Copied from: sunkbd(4)

Fix some nasty race conditions in the VIA-CUDA driver that ended up preventing

2008-12-06T23:26:02Z

my right mouse button and keyboard LEDs from working due to mangled configuration packets. Fixed several other races and associated problems in the main ADB stack that were exposed while fixing this.

Probe ADB miscellaneous devices (ID 7) instead of stopping at ID 6. This

2008-11-12T17:33:36Z

allows us to probe the brightness and volume control buttons on PPC Apple laptops, though there is not yet a driver to do anything useful with them.

Make the touch pad on my PowerBook G4 12" a little more usable.

2008-11-02T19:08:10Z

For an unknown reason the touch pad of my PowerBook generates button 5 events when you operate it. This causes the adb_mouse code to convert them to button 2 events, which is not what we want. Add a new flag, AMS_TOUCHPAD, which is used to distinguish the touch pad. When set, don't convert button events of unknown buttons to the last button. There are still three problems left with respect to user input: - The mouse button events are not properly processed when the touch pad isn't touched. - The arrow keys on the keyboard don't work inside X11. - The power button isn't handled by the kernel, similar to the ACPI power button on i386/amd64. Approved by: nwhitehorn

Allow a read() on /dev/ams[0-9] to be interrupted.

2008-11-01T08:07:02Z

Right now ams_read() uses cv_wait() to wait for new data to arrive on the mouse device. This means that when you run `cat /dev/ams0', it cannot be interrupted directly. After you press ^C, you first need to move the mouse before cat will quit. Make this function use cv_wait_sig(), which allows it to be interrupted directly. Reviewed by: nwhitehorn