Free synaptics touchpad driver software for linux

XOrg/XFree86 Synaptics TouchPad Driver project is a driver for the Synaptics TouchPad for XOrg/XFree86 4.x.
A Synaptics touchpad by default operates in compatibility mode by emulating a standard mouse. However, by using a dedicated driver, more advanced features of the touchpad becomes available.
Main features:
- Movement with adjustable, non-linear acceleration and speed.
- Button events through short touching of the touchpad.
- Double-Button events through double short touching of the touchpad.
- Dragging through short touching and holding down the finger on the touchpad.
- Middle and right button events on the upper and lower corner of the touchpad.
- Vertical scrolling (button four and five events) through moving the finger on the right side of the touchpad.
- The up/down button sends button four/five events.
- Horizontal scrolling (button six and seven events) through moving the finger on the lower side of the touchpad.
- The multi-buttons send button four/five events, and six/seven events for horizontal scrolling.
- Adjustable finger detection.
- Multifinger taps: two finger for middle button and three finger for right button events. (Needs hardware support. Not all models implement this feature.)
- Run-time configuration using shared memory. This means you can change parameter settings without restarting the X server.
Enhancements:
- Support for xorg 7.1 has been added.
- A couple of minor build fixes for xorg 7.0 have been made.

libsynaptics is a library intended to support all upcoming driver versions of the Xorg Synaptics Touch Pad Driver. Programs that want to access the touch pad should make use of this library and will thereby not interfere with each other.
Available parameters can be read and written and the version of the installed driver can be determined. It is still not clear whether libsynaptics will be distributed seperately or within the driver package (which seems to be the better solution to me!).
Enhancements:
A new release of libsynaptics and ksynaptics is now available. This fixes several bugs and breaks backward compatibility with earlier libsynaptics versions. This is why you will have to update both libsynaptics and ksynaptics or keep your current versions.
- new: new mouse button icons (svg based)
- fixed: syndock would run in smart mode even if disabled in ksynaptics
- new: rewrote libsynaptics 0.14.6c, an bug-fixing rewrite
- fixed: the nasty syndock crash on logout should be fixed
IMPORTANT:
- Install libsynaptics 0.14.c first!
- Since the latest libsynaptics breaks backwards compatibility, you cannot use any libsynaptics prior to 0.14.c!

QSynaptics aims to help desktop users to configure their synaptics touch pad thats commonly used in laptops.
The program uses Qt 3.2, is easy to manage and performs the basic configuration steps to use your pad more efficiently. The program is based on the X11 synaptics touch pad driver.
Main features:
- pressure sensitivity: adjust how strong you have to press your pad to create events
- tapping: adjustable tapping delay and disengageable tapping
- smart tapping: switches off mouse pad for an certain delay after an keyboard event has occured
- mouse button emulation: mapping of multifinger taps to certain mouse button
- circular scrolling: enable or disable circular scrolling and adjusting the speed, configuring sensitive edges/corners

TAP provides packet reception and transmission for user-space programs. It can be viewed as a simple Ethernet device, which instead of receiving packets from a physical medium, receives them from a user-space program and instead of sending packets via physical media, writes them to the user-space program.
When a program opens /dev/tunX or /dev/tapX, driver creates and registers corresponding net device tunX or tapX. After a program closed above devices, driver will automatically delete tunXX or tapXX device and all routes corresponding to it.
This package(http://vtun.sourceforge.net/tun) contains two simple example programs that shows you how to use tun and tap devices. Both programs work like bridge between two network interfaces. br_select.c - bridge based on select system call. br_sigio.c - bridge based on async io and SIGIO signal. However the best example is VTun http://vtun.sourceforge.net
Enhancements:
- Massive Linux driver update: 2.4.x kernel support. New cloning interface, protocol indication. Statistics counting fixes.
- Solaris driver update: Correct Ethernet header substitution.
- Configure and Makefile updates. RPM package update.
- Documentation update.

Apache LDAP vhost driver project lets you put vhost with all possible information in an LDAP database for both Apache 1.x and 2.x.

Bug report system

With the new maintainence, there is now also a bug report system at the URL http://bugs.bayour.com/ (project mod_ldap_cfg).

Schemas

A schema called mod_ldap_cfg is used.

Apache config

To setup Apache to use this module, the httpd.conf is used.

uLan Driver provides 9-bit message oriented communication protocol, which is transferred over RS-485 link.
Characters are transferred same way as for RS-232 asynchronous transfer except parity bit, which is used to distinguish between data characters and protocol control information. A physical layer consists of one twisted pair of leads and RS-485 transceivers.
Use of 9-bit character simplifies transfer of binary data and for intelligent controllers can lower the CPU load, because of the CPU need not to care about data characters send to other node. Producers of most microcontrollers for embedded applications know that and have implemented 9-bit extension in UARTs of most of todays MCUs. There is the list below to mention some of them:
- all Intel 8051 and 8096 based MCUs with UART
- members of Motorola 683xx family ( 68332, 68376, ... )
- Hitachi H8 microcontrollers
The driver is implemented as relatively independent layers and subsystems. Messages are prepared and received in the driver dedicated memory. This memory is divided into blocks with uniform size with atomic allocation routines.
When message is being stored into blocks, head of message with couple of data bytes is stored in the first allocated memory block. If all data cannot be stored in the first block, next blocks are allocated and linked together.
The message heads are linked in bidirectional linked lists of messages prepared for sending, processed messages and messages prepared for client notification. These lists or queues are main mechanism for transferring of messages between subsystems.
Link protocol is programmed as finite state automata with state stack, which state routines are executed by interrupt handler. State routine can return positive integer information, negative error notification or zero, which leads to wait for next interrupt. Information or error is used as input parameter when state routine is called.
When the state routine wants initiate transfer to another state routine it changes pointer to the actual state routine. If previous state routine returns nonzero value new routine is called immediately, in other case next interrupt invokes new state routine.
There is stack of callers of actual state routines which enables to constructs automata subsystems, which can be used in more places in main automata loop. Main purpose of this automata is to send or process messages coming in list of messages prepared for sending and if specified, move these messages onto list of messages prepared for client notification.
Received messages are put onto this list too. Subsystem is supervised by timeout handler, which can revitalize communication in case of die of other node. The interrupt and timeout handlers are fully SMP reentrant.
The automata subsystem uses pointers to chip driver routines for hardware port manipulation. This is only part dependent on used chip, today 82510, 16450 and OX16C950PCI. These routines can send and receive 9 bit character, connect to RS-485 line by the arbitration sequence, wait for specified time for character and initialize and close port.
File operation subsystem makes interface between OS kernel VFS and client message queues. It enables to prepare single or multi-frame messages and stores notifications of received or processed messages in clients private state structures. This part is heavily operating system dependent.
Enhancements:
- This release enables you to build the driver within the WDF framework for Windows.
- Updates to support the latest Linux 2.6.x kernels are included (tested to 2.6.19).
- Changes to allow stand-alone system-less build for ARM targets (LPC21xx) are included.
- The OMK has been selected as the default build.
- The "switch2std" script allows you to switch to the old build system.

Bind9 LDAP sdb driver is an attempt at an LDAP back-end for BIND 9 using the new simplified database interface "sdb". Using this you can store zones in LDAP rather than in files.

Note that when using sdb, the zones are not cached in memory, BIND will do a database lookup whenever it gets a query. If you want to store zones in LDAP but still have BIND do caching, you may be interested in the ldap2zone tool.

ATI Radeon Linux Display Drivers are proprietary Linux drivers for ATI Radeon cards.
ATI Radeon Linux Display Driver provides TV Output support for ATI graphics cards that support TV out. The ATI Proprietary Linux driver also allows for the following monitor arrangements:
- Laptop Mode (toggle between internal or external screen)
- Clone Mode (same content on both screens)
- Big Desktop (one desktop stretched across two screens)
- Dual Head (separate instances of X running on each screen)