Drivers Touchkit Mice & Touchpads
- Windows device driver information for Touchkit USB Controller for TouchScreen. Touchkit USB Controller for TouchScreen is a product of Technologies Inc and it provides the hopeful performance of analog resistive touch panels for four wire, five wire, and wire models. It communicates with PC system directly through RS232, PS/2 or USB connector.
- Itronix GD6000 TouchKit Touchscreen Driver 8.5.0.1032 for Windows 7 64-bit 491 downloads. Keyboard & Mouse Synaptics. Windows 7, Windows Vista, Windows XP.
Touchpad Driver free download - Synaptics TouchPad Driver 7.5.4.0.zip, Driver Booster, Driver Easy, and many more programs. Here is a step by step manual guide for TouchKit USB Controller for TouchScreen software installation process on Windows 7 / 8 / 8.1 / 10 / Vista / XP. 1 Download PBM DRIVER TOUCH.rar file for Windows 7 / 8 / 8.1 / 10 / Vista / XP, save and unpack it if needed. 2 Switch on your new mouse hardware.
A touchpad or trackpad is a pointing device featuring a tactile sensor, a specialized surface that can translate the motion and position of a user's fingers to a relative position on the operating system that is made output to the screen. Touchpads are a common feature of laptop computers as opposed to using a mouse on a desktop, and are also used as a substitute for a mouse where desk space is scarce. Because they vary in size, they can also be found on personal digital assistants (PDAs) and some portable media players. Wireless touchpads are also available as detached accessories.
Operation and function[edit]
Touchpads operate in one of several ways, including capacitive sensing and resistive touchscreen. The most common technology used in the 2010s senses the change of capacitance where a finger touches the pad. Capacitance-based touchpads will not sense the tip of a pencil or other similar ungrounded or non-conducting implements. Fingers insulated by a glove may also be problematic.
While touchpads, like touchscreens, are able to sense absolute position, resolution is limited by their size. For common use as a pointer device, the dragging motion of a finger is translated into a finer, relative motion of the cursor on the output to the display on the operating system, analogous to the handling of a mouse that is lifted and put back on a surface. Hardware buttons equivalent to a standard mouse's left and right buttons are positioned adjacent to the touchpad.
Some touchpads and associated device driver software may interpret tapping the pad as a mouse click, and a tap followed by a continuous pointing motion (a 'click-and-a-half') can indicate dragging.[1] Tactile touchpads allow for clicking and dragging by incorporating button functionality into the surface of the touchpad itself.[2][3] To select, one presses down on the touchpad instead of a physical button. To drag, instead of performing the 'click-and-a-half' technique, the user presses down while on the object, drags without releasing pressure, and lets go when done. Touchpad drivers can also allow the use of multiple fingers to emulate the other mouse buttons (commonly two-finger tapping for the center button).
Touchpads are called clickpads if it does not have physical buttons, but instead relies on 'software buttons'. Physically the whole clickpad formed a button, logically the driver interprets a click as a left or right button click depending on the placement of fingers.[4]
Some touchpads have 'hotspots', locations on the touchpad used for functionality beyond a mouse. For example, on certain touchpads, moving the finger along an edge of the touch pad will act as a scroll wheel, controlling the scrollbar and scrolling the window that has the focus, vertically or horizontally. Many touchpads use two-finger dragging for scrolling. Also, some touchpad drivers support tap zones, regions where a tap will execute a function, for example, pausing a media player or launching an application. All of these functions are implemented in the touchpad device driver software, and can be disabled.
History[edit]
By 1982, Apollo desktop computers were equipped with a touchpad on the right side of the keyboard.[5] Introduced a year later, in 1983, the first battery powered clamshell laptop, the Gavilan SC included a touchpad, which was mounted above its keyboard, rather than below, which became the norm.
In 1989 a touchpad was developed for Psion's MC 200/400/600/WORD Series .[6] Laptops with touchpads were then launched by Olivetti and Triumph-Adler in 1992.[7]Cirque introduced the first widely available touchpad, branded as GlidePoint, in 1994.[8]Apple introduced touchpads to the modern laptop in the PowerBook series in 1994, using Cirque's GlidePoint technology;[9] later PowerBooks and MacBooks would use Apple-developed trackpads. Another early adopter of the GlidePoint pointing device was Sharp.[8] Later, Synaptics introduced their touchpad into the marketplace, branded the TouchPad. Epson was an early adopter of this product.[8]
As touchpads began to be introduced in laptops in the 1990s, there was often confusion as to what the product should be called. No consistent term was used, and references varied, such as: glidepoint, touch sensitive input device, touchpad, trackpad, and pointing device.[10][11][12]
Users were often presented the option to purchase a pointing stick, touchpad, or trackball. Combinations of the devices were common, though touchpads and trackballs were rarely included together.[13] Since the early 2000s, touchpads have become the dominant laptop pointing device as most laptops produced during this period beyond include only touchpads, displacing the pointing stick.
Use in devices[edit]
Touchkit Exe
Touchpads are primarily used in self-contained portable laptop computers and do not require a flat surface near the machine. The touchpad is close to the keyboard, and only very short finger movements are required to move the cursor across the display screen; while advantageous, this also makes it possible for a user's palm or wrist to move the mouse cursor accidentally while typing. Touchpads also exist for desktop computers as an external peripheral, albeit rarely seen. Touchpads are sometimes integrated in some desktop computer keyboards, particularly keyboards oriented for HTPC use.
One-dimensional touchpads are the primary control interface for menu navigation on iPod Classic portable music players and additional input metod on some Wacom digitizer tablets, where they are referred to as 'click wheels', since they only sense motion along one axis, which is wrapped around like a wheel. Creative Labs also uses a touchpad for their Zen line of MP3 players, beginning with the Zen Touch. The second-generation MicrosoftZune product line (the Zune 80/120 and Zune 4/8) uses touch for the Zune Pad.
Apple's PowerBook 500 series was its first laptop to carry such a device,[14] which Apple refers to as a 'trackpad'. When introduced in May 1994, it replaced the trackball of previous PowerBook models. In late 2008 Apple's revisions of the MacBook and MacBook Pro incorporated a 'Tactile Touchpad' design with button functionality incorporated into the tracking surface.[2][3][15] Beginning in the second generation of MacBook Pro, the entire touchpad surface acts as a clickable button.[16]
Laptops today feature multitouch touchpads that can sense in some cases up to five fingers simultaneously, providing more options for input, such as the ability to bring up the context menu by tapping two fingers, dragging two fingers for scrolling, or gestures for zoom in/out or rotate. The touchpads with physical buttons now are only hi-end businessprofessional laptops option.
Drivers thomson network & wireless cards login. Psion's MC 200/400/600/WORD Series,[6] introduced in 1989, came with a new mouse-replacing input device similar to a touchpad,[17] although more closely resembling a graphics tablet, as the cursor was positioned by clicking on a specific point on the pad, instead of moving it in the direction of a stroke.
Theory of operation[edit]
There are two principal means by which touchpads work.[citation needed] In the matrix approach, a series of conductors are arranged in an array of parallel lines in two layers, separated by an insulator and crossing each other at right angles to form a grid. A high frequency signal is applied sequentially between pairs in this two-dimensional grid array. The current that passes between the nodes is proportional to the capacitance. When a virtual ground, such as a finger, is placed over one of the intersections between the conductive layer some of the electrical field is shunted to this ground point, resulting in a change in the apparent capacitance at that location. This method received U.S. Patent 5,305,017 awarded to George Gerpheide in April 1994.
The capacitive shunt method, described in an application note by Analog Devices (not to be confused with analog devices),[18] senses the change in capacitance between a transmitter and receiver that are on opposite sides of the sensor. The transmitter creates an electric field which oscillates at 200–300 kHz. If a ground point, such as the finger, is placed between the transmitter and receiver, some of the field lines are shunted away, decreasing the apparent capacitance. Trackpads such as those found in some Blackberry smartphones work optically, like an optical computer mouse.
Manufacturing[edit]
Major manufacturers include:
- Elan Microelectronics
See also[edit]
| Wikimedia Commons has media related to Touchpads. |
References[edit]
- ^'Tap and drag'. Apple.com.
- ^ ab'The Tactile Touchpad'. sigchi.com.
- ^ ab'A Comparison of Three Selection Techniques for Touchpads'(PDF). yorku.ca.
- ^'Libinput documentation, Clickpad software button behavior'. wayland.freedesktop.org.
- ^Getting Started With Your DOMAIN System. Apollo Computer. 1983.
- ^ ab'GUIdebook Psion MC Series brochure'. guidebookgallery.org.
- ^Olivetti S20, D33 and identically Triumph-Adler Walkstation 386, Walkstation 386SX
- ^ abcDiehl, Stanford; Lennon, Anthony J.; McDonough, John (Oct 1995). 'Touchpads to Navigate By'. Byte. No. October 1995. Green Publishing. p. 150. ISSN0360-5280.
- ^Thryft, Ann R. 'More Than a Mouse,' Computer Product Development, EBN Extra, November 14, 1994, pp. E16 – E20
- ^'A WinBook for the Fussy'. Windows Magazine. No. Dec 95. 1995. p. 105.
- ^'Sharp Unveils Line of Notebooks'. Westchester County Business Journal. Westchester County Business Journal (November 20, 1995). 1995.
- ^Malloy, Rich; Crabb, Don (October 1995). 'Power Packed Power Books'. Mobile Office. New York, NY (October 1995): 44–52.
- ^Jerome, Marty (1995). 'Lightweight, Low-Cost Challenger'. PC Computing. PC Computing (December 1995): 96.
- ^'Blackbird: The PowerBook 500 Series'. Low End Mac. 1994-05-16. Retrieved 2017-07-09.
- ^'MacBook design'. Apple.com.
- ^Ackerman, Dan (June 10, 2009). 'Apple MacBook Pro Summer 2009 (Core 2 Duo 2.26 GHz, 2GB RAM, 160GB HDD, Nvidia GeForce 9400M, 13-inch)'. CNET. Retrieved April 11, 2010.
- ^'GUIdebook Psion MC Series brochure, page 4'. guidebookgallery.org.
- ^'Analog Devices' Capacitive Shunt Method'(PDF). analog.com.
External links[edit]
| Look up touchpad, trackpad, or touchscreen in Wiktionary, the free dictionary. |
- Notes on the History of Pen-based Computing on YouTube
> Hi,
>
> based on the touchkit USB and livebook PS/2 touchscreen driver,
> I made a driver for the touchkit PS/2 version. The work is based upon
> kernel 2.6.13.2 .
>
> The egalax touchsreen controller (PS/2 or USB version) is used
> in this 7' device:
> http://www.cartft.com/catalog/il/449
>
> Currently I'm using the PS/2 version in a DirectFB enviroment.
> http://www.directfb.org/
> http://mail.directfb.org/pipermail/directfb-dev/2005-September/000705.html
> http://mail.directfb.org/pipermail/directfb-dev/2005-September/000706.html
>
>
> Could you please have a look at it and tell my your comments on
> what would be additional required to get it included into kernel tree.
Hi Stefan,
first if you want people to review your code please don't send such small
patches in compressed form. In general patch looks good, but see comments
below.
> diff -uprN linux-2.6.13.2.vanilla/drivers/input/mouse/Makefile linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/Makefile
> --- linux-2.6.13.2.vanilla/drivers/input/mouse/Makefile 2005-09-17 03:02:12.000000000 +0200
> +++ linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/Makefile 2005-09-23 18:09:08.000000000 +0200
> @@ -15,4 +15,4 @@ obj-$(CONFIG_MOUSE_SERIAL) += sermouse.o
> obj-$(CONFIG_MOUSE_HIL) += hil_ptr.o
> obj-$(CONFIG_MOUSE_VSXXXAA) += vsxxxaa.o
>
> -psmouse-objs := psmouse-base.o alps.o logips2pp.o synaptics.o lifebook.o
> +psmouse-objs := psmouse-base.o alps.o logips2pp.o synaptics.o lifebook.o touchkit_ps2.o
> diff -uprN linux-2.6.13.2.vanilla/drivers/input/mouse/psmouse-base.c linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/psmouse-base.c
> --- linux-2.6.13.2.vanilla/drivers/input/mouse/psmouse-base.c 2005-09-17 03:02:12.000000000 +0200
> +++ linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/psmouse-base.c 2005-09-23 19:10:42.000000000 +0200
> @@ -25,6 +25,7 @@
> #include 'logips2pp.h'
> #include 'alps.h'
> #include 'lifebook.h'
> +#include 'touchkit_ps2.h'
>
> #define DRIVER_DESC 'PS/2 mouse driver'
>
> @@ -456,6 +457,13 @@ static int psmouse_extensions(struct psm
> }
> }
>
> + if (touchkit_ps2_detect(psmouse, set_properties) 0) {
> + if (max_proto > PSMOUSE_IMEX) {
> + if (!set_properties || touchkit_ps2_init(psmouse) 0)
> + return PSMOUSE_TOUCHKIT_PS2;
> + }
> + }
> +
> /*
> * Try Kensington ThinkingMouse (we try first, because synaptics probe
> * upsets the thinkingmouse).
> @@ -518,6 +526,10 @@ static int psmouse_extensions(struct psm
>
> if (max_proto >= PSMOUSE_IMPS && intellimouse_detect(psmouse, set_properties) 0)
> return PSMOUSE_IMPS;
> +#if 0
> + if (max_proto >= PSMOUSE_TOUCHKIT_PS2 && touchkit_ps2_detect(psmouse, set_properties) 0)
> + return PSMOUSE_TOUCHKIT_PS2;
> +#endif
Hmm, is this part really needed ?
>
> /*
> * Okay, all failed, we have a standard mouse here. The number of the buttons
> @@ -600,6 +612,13 @@ static struct psmouse_protocol psmouse_p
> .init = lifebook_init,
> },
> {
> + .type = PSMOUSE_TOUCHKIT_PS2,
> + .name = 'touchkitPS/2',
> + .alias = 'touchkit',
> + .detect = touchkit_ps2_detect,
> + .init = touchkit_ps2_init,
> + },
> + {
> .type = PSMOUSE_AUTO,
> .name = 'auto',
> .alias = 'any',
> diff -uprN linux-2.6.13.2.vanilla/drivers/input/mouse/psmouse.h linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/psmouse.h
> --- linux-2.6.13.2.vanilla/drivers/input/mouse/psmouse.h 2005-09-17 03:02:12.000000000 +0200
> +++ linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/psmouse.h 2005-09-23 17:46:38.000000000 +0200
> @@ -78,6 +78,7 @@ enum psmouse_type {
> PSMOUSE_SYNAPTICS,
> PSMOUSE_ALPS,
> PSMOUSE_LIFEBOOK,
> + PSMOUSE_TOUCHKIT_PS2,
> PSMOUSE_AUTO /* This one should always be last */
> };
>
> diff -uprN linux-2.6.13.2.vanilla/drivers/input/mouse/touchkit_ps2.c linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/touchkit_ps2.c
> --- linux-2.6.13.2.vanilla/drivers/input/mouse/touchkit_ps2.c 1970-01-01 01:00:00.000000000 +0100
> +++ linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/touchkit_ps2.c 2005-09-25 12:23:58.000000000 +0200
> @@ -0,0 +1,180 @@
> +/* ----------------------------------------------------------------------------
> + * touchkit_ps2.c -- Driver for eGalax TouchKit PS/2 Touchscreens
> + *
> + * Copyright (C) 2005 by Stefan Lucke
> + * Copyright (C) 2004 by Daniel Ritz
> + * Copyright (C) by Todd E. Johnson (mtouchusb.c)
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License as
> + * published by the Free Software Foundation; either version 2 of the
> + * License, or (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful, but
> + * WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
> + *
> + * Based upon touchkitusb.c
> + *
> + * Vendor documentation is available in support section of:
> + * http://www.egalax.com.tw/
> + *
> + */
> +
> +#include <linux/config.h>
> +#include <linux/kernel.h>
> +#include <linux/slab.h>
> +
> +#include <linux/input.h>
> +#include <linux/serio.h>
> +#include <linux/libps2.h>
> +#include <linux/dmi.h>
> +
> +#include 'psmouse.h'
> +#include 'touchkit_ps2.h'
> +
> +
> +#if !defined(DEBUG) && defined(CONFIG_USB_DEBUG)
> +#define DEBUG
> +#endif
Unused ?
> +
> +#define TOUCHKIT_MIN_XC 0x0
> +#define TOUCHKIT_MAX_XC 0x07ff
> +#define TOUCHKIT_XC_FUZZ 0x0
> +#define TOUCHKIT_XC_FLAT 0x0
> +#define TOUCHKIT_MIN_YC 0x0
> +#define TOUCHKIT_MAX_YC 0x07ff
> +#define TOUCHKIT_YC_FUZZ 0x0
> +#define TOUCHKIT_YC_FLAT 0x0
> +#define TOUCHKIT_REPORT_DATA_SIZE 8
> +
> +#define TOUCHKIT_DOWN 0x01
> +#define TOUCHKIT_POINT_TOUCH 0x81
> +#define TOUCHKIT_POINT_NOTOUCH 0x80
> +
> +#define TOUCHKIT_GET_TOUCHED(dat) ((((dat)[0]) & TOUCHKIT_DOWN) ? 1 : 0)
> +#define TOUCHKIT_GET_X(dat) (((dat)[1] << 7) | (dat)[2])
> +#define TOUCHKIT_GET_Y(dat) (((dat)[3] << 7) | (dat)[4])
> +
> +#define DRIVER_VERSION 'v0.1'
> +#define DRIVER_AUTHOR 'Stefan Lucke <ste..@lucke.in-berlin.de>'
> +#define DRIVER_DESC 'eGalax TouchKit PS/2 Touchscreen Driver'
> +
> +static int xyswap = 0;
> +module_param(xyswap, bool, 0644);
> +MODULE_PARM_DESC(xyswap, 'If set X and Y axes are swapped.');
> +
> +static int xinvert = 0;
> +module_param(xinvert, bool, 0644);
> +MODULE_PARM_DESC(xinvert, 'Invert direction of x axis.');
> +
> +static int yinvert = 0;
> +module_param(yinvert, bool, 0644);
> +MODULE_PARM_DESC(yinvert, 'Invert direction of y axis.');
> +
> +static int xfuzz = 0;
> +module_param(xfuzz, uint, 0644);
> +MODULE_PARM_DESC(xinvert, 'Fuzz value for x axis.');
> +
> +static int yfuzz = 0;
> +module_param(yfuzz, uint, 0644);
> +MODULE_PARM_DESC(yfuzz, 'Fuzz value for y axis.');
> +
> +static int smartpad = 0;
> +module_param(smartpad, bool, 0644);
> +MODULE_PARM_DESC(smartpad, 'Act as a smartpad device.');
> +
> +static int mouse = 0;
> +module_param(mouse, bool, 0644);
> +MODULE_PARM_DESC(mouse, 'Report mouse button');
> +
> +static psmouse_ret_t touchkit_ps2_process_byte(struct psmouse *psmouse, struct pt_regs *regs)
> +{
> + unsigned char *packet = psmouse->packet;
> + struct input_dev *dev = &psmouse->dev;
> + int x,y;
Strange formating, why two tabs ?
> +
> + if (psmouse->pktcnt != 5)
> + return PSMOUSE_GOOD_DATA;
> +
> + input_regs(dev, regs);
> +
> + if (xyswap) {
> + y = TOUCHKIT_GET_X(packet);
> + x = TOUCHKIT_GET_Y(packet);
> + } else {
> + x = TOUCHKIT_GET_X(packet);
> + y = TOUCHKIT_GET_Y(packet);
> + }
> +
> + y = (yinvert) ? TOUCHKIT_MAX_YC - y : y;
> + x = (xinvert) ? TOUCHKIT_MAX_XC - x : x;
> +
> + input_report_key(dev,
> + (mouse) ? BTN_MOUSE : BTN_TOUCH,
> + TOUCHKIT_GET_TOUCHED(packet));
> +
> + if (smartpad)
> + input_report_key(dev, BTN_TOOL_FINGER, 1);
> +
> + input_report_abs(dev, ABS_X, x);
> + input_report_abs(dev, ABS_Y, y);
> +
> + input_sync(dev);
> +
> + return PSMOUSE_FULL_PACKET;
> +}
> +
> +int touchkit_ps2_detect(struct psmouse *psmouse, int set_properties)
> +{
> + unsigned char param[3];
Two tabs again.
> +
> + if (set_properties) {
> + psmouse->vendor = 'eGalax';
> + psmouse->name = 'Touchscreen';
> + }
AFAIK this should be done after device is really detected.
> +
> + param[0] = 1;
> + param[1] = 'A';
> +
> + if (ps2_command(&psmouse->ps2dev, param, (2<<12)|(3<<8)|0x0A) 0 &&
Can you add descriptive #define for (2<<12)|(3<<8)|0x0A) ? Bare magic
numbers are ugly.
> + param[0] 0x0A && param[1] 0x01 && param[2] 'A'){
> + printk(KERN_INFO 'touchkit_ps2: device detectedn');
> + return 0;
> + }
> + return -1;
Use single tab not spaces.
> +}
> +
> +int touchkit_ps2_init(struct psmouse *psmouse)
> +{
> + psmouse->dev.evbit[0] = BIT(EV_KEY) | BIT(EV_ABS);
> +
> + set_bit((mouse) ? BTN_MOUSE : BTN_TOUCH,psmouse->dev.keybit);
> + if (smartpad)
> + set_bit(BTN_TOOL_FINGER,psmouse->dev.keybit);
> +
> + psmouse->dev.absbit[0] = BIT(ABS_X) | BIT(ABS_Y);
> +
> + /* Used to Scale Compensated Data */
Same here.
> + psmouse->dev.absmin[ABS_X] = TOUCHKIT_MIN_XC;
> + psmouse->dev.absmax[ABS_X] = TOUCHKIT_MAX_XC;
> + psmouse->dev.absfuzz[ABS_X] = xfuzz;
> + psmouse->dev.absflat[ABS_X] = TOUCHKIT_XC_FLAT;
> + psmouse->dev.absmin[ABS_Y] = TOUCHKIT_MIN_YC;
> + psmouse->dev.absmax[ABS_Y] = TOUCHKIT_MAX_YC;
> + psmouse->dev.absfuzz[ABS_Y] = yfuzz;
> + psmouse->dev.absflat[ABS_Y] = TOUCHKIT_YC_FLAT;
> +
> + input_set_abs_params(&psmouse->dev, ABS_X, 0, 0x07ff, xfuzz, 0);
> + input_set_abs_params(&psmouse->dev, ABS_Y, 0, 0x07ff, yfuzz, 0);
> +
> + psmouse->protocol_handler = touchkit_ps2_process_byte;
> + psmouse->pktsize = 5;
> +
> + return 0;
> +}
> diff -uprN linux-2.6.13.2.vanilla/drivers/input/mouse/touchkit_ps2.h linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/touchkit_ps2.h
> --- linux-2.6.13.2.vanilla/drivers/input/mouse/touchkit_ps2.h 1970-01-01 01:00:00.000000000 +0100
> +++ linux-2.6.13.2.touchkit_ps2/drivers/input/mouse/touchkit_ps2.h 2005-09-24 12:34:23.000000000 +0200
> @@ -0,0 +1,18 @@
> +/* ----------------------------------------------------------------------------
> + * touchkit_ps2.h -- Driver for eGalax TouchKit PS/2 Touchscreens
> + *
> + * Copyright (C) 2005 by Stefan Lucke
> + * Copyright (c) 2005 Vojtech Pavlik
> + *
> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU General Public License version 2 as published by
> + * the Free Software Foundation.
> + */
> +
> +#ifndef _TOUCHKIT_PS2_H
> +#define _TOUCHKIT_PS2_H
> +
> +int touchkit_ps2_detect(struct psmouse *psmouse, int set_properties);
> +int touchkit_ps2_init(struct psmouse *psmouse);
> +
> +#endif
Touchkit Install
--
Andrey Panin | Linux and UNIX system administrator
pa..@donpac.ru | PGP key: wwwkeys.pgp.net
-
To unsubscribe from this list: send the line 'unsubscribe linux-kernel' in
the body of a message to majo..@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/