Free nlite sata driver software for linux

The intel-wings project is a Linux driver for the Intel Wireless Series of input devices.
Somehow, Intel managed to avoid using the USB Human Interface Device standards with their wireless gamepads.
All other USB gamepads work out-of-the-box: plug it in, and the computer knows that it has an X axis, a Y axis, and six buttons. Not Intel. Thats where intel-wings comes in.
Wireless Series?
Yes, youve seen them. Everyone hated them. The keyboards were of poor manufacturing, the mice eat batteries like theres no tomorrow, and the whole system was ridiculously expensive. They were killed off by Intel several years ago -- after hitting the shelves and getting a lukewarm reaction, manufacturing was stopped, and support was terminated 18 months after release.
All of these complaints are valid. On the other hand, when used infrequently, the mice last a few months, and work great on a glass coffee table in my living room. (A newer wireless optical mouse wouldnt work.)
The gamepads are actually pretty fun, in my opinion: you can have a whole bunch of them attached to one base station, which is great for playing old console games with friends. You can get a complete set of devices for $10 on eBay, and with Linux-based PVRs becoming increasingly common, I find my devices to be a great addition to my living room.
Note that I wouldnt recommend the mice to anyone that uses their computer on a regular basis, but its easier for navigating menus than a remote control. In my opinion, the Intel Wireless Series devices on Linux PVRs are the way to go.
Enhancements:
- Preliminary keyboard support was added.
- The Intel wireless keyboards are at least partially functional.

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.

The Advanced Linux Sound Architecture is composed of several parts. The first is a fully modularized sound driver which supports module autoloading, devfs, isapnp autoconfiguration, and gives complete access to analog audio, digital audio, control, mixer, synthesizer, DSP, MIDI, and timer components of audio hardware.
It also includes a fully-featured kernel-level sequencer, a full compatibility layer for OSS/Free applications, an object-oriented C library which covers and enhances the ALSA kernel driver functionality for applications (client/server, plugins, PCM sharing/multiplexing, PCM metering, etc.), an interactive configuration program for the driver, and some simple utilities for basic management.
Main features:
- Efficient support for all types of audio interfaces, from consumer soundcards to professional multichannel audio interfaces.
- Fully modularized sound drivers.
- SMP and thread-safe design.
- User space library (alsa-lib) to simplify application programming and provide higher level functionality.
- Support for the older OSS API, providing binary compatibility for most OSS programs.

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.

This project is to produce drivers for the Logitech Quickam Express that will run popular linux software, such as video for linux.

This site hosts the Linux driver for the QuickCam Express and other QuickCam-related and QuickCam-compatible USB web cameras. The original work was done by Georg Acher and was known as qce-ga; Jean-Frederic Clere took that driver and created the first Video4Linux (V4L) driver, enabling popular V4L applications such as Xawtv to display pictures from the webcam. Since then, a group of developers around the world have evolved the driver into its current state, adding support for new cameras and chipsets as they have become available. In the process, the driver became known as qc-usb to reflect the fact that it supports a wide variety of USB-attached QuickCam cameras, not just the QuickCam Express.

The qc-usb driver supports the following webcams:

Dexxa Webcam
Labtec Webcam (old model)
LegoCam
Logitech QuickCam Express (old model)
Logitech QuickCam Notebook (some models)
Logitech QuickCam Web

Generally, any USB camera with a USB vendor ID of 0x46d and a USB product ID of 0x840, 0x850, or 0x870 (so, 0x46d:0x840, for example), should work. You can see the USB ID using operating system utilities such as lsusb in Linux.

ATA over Ethernet driver allows the Linux kernel to use the ATA over Ethernet (AoE) network protocol.
Using AoE, a Linux system can use AoE block devices like EtherDrive (R) storage blades.
The block devices appear as local device nodes (e.g. /dev/etherd/e0.0).
Enhancements:
- The driver now handles payloads larger than 4KiB, receives large packets without extra in-memory copy, and handles I/O requests so that the user can choose between the Linux I/O schedulers.

EXAMPLE

# This is a really long synopsis, but hopefully it will give you an idea...

package MyPackage;

use Class::Driver;
use base q(Class::Driver);

our %drivers;

return 1;

sub new {
my($class, %args) = @_;
die "mime_type is required" unless($args{mime_type});
die "no driver to handle type $args{mime_type}"
unless($drivers{$args{mime_type}});
return $class->driver_load($drivers{$args{mime_type}}, %args);
}

sub driver_new {
my($class, %args) = @_;
return bless %args, $class;
}

sub driver_required { 1; }
sub driver_requied_here { 0; }

package MyPackage::avi;

use MyPackage;
use base q(MyPackage);
use Video::Info;

$MyPackage::drivers{video/x-msvideo} = avi;

return 1;

sub driver { "avi"; }

sub driver_new {
my($class, %args) = @_;
die "file is a required parameter for $args{mime_type} files"
unless($args{file});
$args{info} = Video::Info->new(-file => $args{file})
or die "Failed to create a Video::Info object for $args{file}";
return $class->SUPER::driver_new(%args);
}

sub duration {
my $self = shift;
return $args{info}->duration;
}

package MyPackage::mp3;
use base q(MyPackage);
use MP3::Info;

$MyPackage::drivers{audio/mpeg} = mp3;

## (etc...)

package main;

my $foo = MyPackage->new(file => foobar.mp3, mime_type => audio/mpeg);
print "foobar.mp3 is ", $foo->duration, " seconds long.n";

iRiver iFP is an user-space open-source driver for iRivers iFP flash portable MP3 players.
This project encourages open source driver development for iRivers iFP portable music players. Ifp-driver was started by Pavel Kriz with ifp-line, a command-line program and the first Free iFP driver. Today, the ifp-driver mailing list is a hub of discussion for iFP driver development: participants include everyone from authors of spin-off projects, to prospective owners/users.
Ifp-driver home projects:
ifp-line is the original command line utility and Midnight Commander plugin. Stable.
linux-filesystem a linux kernel module that mounts iFP devices as filesystems. Stable.
libifp a generic iFP support library. Stable.
Related projects:
user interfaces
ifpgui a kde/qt manager by Jim Campbell; uses libifp.
ifp-gnome a gnome manager by Billy Charlton; uses ifp-line.
ifp-manager a perl+gtk2 gui
giriver a python+gtk2 frontend; uses libiriver. (unmaintained)
plugins
kio_iriver KDE KIO slave by Joe Roback; uses libiriverdriver.
[unnamed] KDE KIO slave by Thomas Loeber.
libraries
libiriverdriver a C++ library driver by Joe Roback.
pyifp python bindings for libifp, by James Evans
rubyifp Ruby bindings for libifp, by Martin Schanzenbach
libifp-cil Mono/.NET bindings for libifp, by Christian Elkjaer
libiriver an older ifp library. (unmaintained)
Unless otherwise noted, projects support all iRiver iFP devices. Users have reported successfully accessing models iFP-1xx,3xx,5xx,7xx,8xx,9xx and N10. We dont anticipate difficulty supporting future models.
Enhancements:
- Release ifp-line-0.3.
- ifp.c: Change "ifp version" output for GPL compliance.
- NEWS: Fix Engrish in NEWS.
- README: Add notice for error with non-ASCII filename.
- ChangeLog: Add ChangeLog.