Linux Driver Project - User contributions [en]

User:Josheratkins

2012-05-07T22:56:32Z

Tomasz Grzegurzko: Links to non-relevant external sites.

User:Tomasz Grzegurzko

2012-05-07T07:26:20Z

Tomasz Grzegurzko:

* The administrator of the linuxdriverproject.org web and related services. To report problems, please send me an email <email>tomasz89@gmail.com</email>.

Linux Driver Project:About

2012-05-07T07:25:02Z

Tomasz Grzegurzko:

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

For any problems with the mailing lists, wiki or web site, please send an email to [[User:Tomasz Grzegurzko|the administrator]].

Main Page

2012-05-07T07:16:13Z

Tomasz Grzegurzko:

Welcome to the Wiki for The Linux Driver Project.

This group is focused on creating and maintaining [[Open Source]] Linux kernel drivers for all types of devices, and maintaining community information on developments around devices. If you had previously registered in the [http://linuxdriverproject.org/legacy/foswiki old wiki], you will need to create a new account.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the [[Company Process]] page.

If you are a developer, consider joining the [[Mailing Lists]] or creating an account in the Wiki and aiding in the documentation effort.

== Frequently Asked Questions ==

We have quite a long list of [[Frequently Asked Questions]] that you might wish to peruse before asking them to the developers or on the [[Mailing Lists]].

== Mailing Lists ==

We currently have one mailing list, for all [[Developers]]. Please see the [[Mailing Lists]] page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the [[Project Status]] page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of [[Out Of Tree Drivers]], that could be cleaned up and added to the main Linux kernel tree, and one list of [[Drivers Needed]] for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by [[User:GregKH|GregKH]], and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact [[User:GregKH|GregKH]].

Linux Driver Project:About

2012-05-07T07:14:39Z

Tomasz Grzegurzko: Created page with "We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, d..."

Main Page

2012-05-07T05:24:32Z

Tomasz Grzegurzko:

Welcome to the Wiki for The Linux Driver Project.

This group is focused on creating and maintaining [[Open Source]] Linux kernel drivers for all types of devices, and maintaining community information on developments around devices. If you had previously registered in the [http://linuxdriverproject.org/legacy/foswiki old wiki], you will need to create a new account.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the [[Company Process]] page.

== Frequently Asked Questions ==

We have quite a long list of [[Frequently Asked Questions]] that you might wish to peruse before asking them to the developers or on the [[Mailing Lists]].

== Mailing Lists ==

We currently have one mailing list, for all [[Developers]]. Please see the [[Mailing Lists]] page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the [[Project Status]] page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of [[Out Of Tree Drivers]], that could be cleaned up and added to the main Linux kernel tree, and one list of [[Drivers Needed]] for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by [[User:GregKH|GregKH]], and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact [[User:GregKH|GregKH]].

Main Page

2012-05-07T04:34:14Z

Tomasz Grzegurzko:

Welcome to the Wiki for The Linux Driver Project.

This group is focused on creating and maintaining [[Open Source]] Linux kernel drivers for all types of devices, and maintaining community information on developments around devices. If you had previously registered in the [http://linuxdriverproject.org/foswiki old wiki], you will need to create a new account.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the [[Company Process]] page.

== Frequently Asked Questions ==

We have quite a long list of [[Frequently Asked Questions]] that you might wish to peruse before asking them to the developers or on the [[Mailing Lists]].

== Mailing Lists ==

We currently have one mailing list, for all [[Developers]]. Please see the [[Mailing Lists]] page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the [[Project Status]] page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of [[Out Of Tree Drivers]], that could be cleaned up and added to the main Linux kernel tree, and one list of [[Drivers Needed]] for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by [[User:GregKH|GregKH]], and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact [[User:GregKH|GregKH]].

Help:Editing

2012-05-07T04:25:04Z

Tomasz Grzegurzko:

Please see http://meta.wikimedia.org/wiki/Help:Editing

Help:Editing

2012-05-07T04:24:29Z

Tomasz Grzegurzko: Created page with "#REDIRECT [http://meta.wikimedia.org/wiki/Help:Editing]"

#REDIRECT [http://meta.wikimedia.org/wiki/Help:Editing]

User:Tomasz Grzegurzko

2012-05-07T04:14:54Z

Tomasz Grzegurzko: Created page with "* I am the administrator of the linuxdriverproject.org web and related services. * To report problems, please send me an email <email>tomasz89@gmail.com</email>."

* I am the administrator of the linuxdriverproject.org web and related services.
* To report problems, please send me an email <email>tomasz89@gmail.com</email>.

Main Page

2012-05-07T04:03:44Z

Tomasz Grzegurzko:

The Linux Driver Project is focused on creating and maintaining [[Open Source]] Linux kernel drivers for all types of devices.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the [[Company Process]] page.

== Frequently Asked Questions ==

We have quite a long list of [[Frequently Asked Questions]] that you might wish to peruse before asking them to the developers or on the [[Mailing Lists]].

== Mailing Lists ==

We currently have one mailing list, for all [[Developers]]. Please see the [[Mailing Lists]] page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the [[Project Status]] page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of [[Out Of Tree Drivers]], that could be cleaned up and added to the main Linux kernel tree, and one list of [[Drivers Needed]] for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by [[User:GregKH|GregKH]], and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact [[User:GregKH|GregKH]].

No Linux Driver Needed

2012-05-07T04:02:58Z

Tomasz Grzegurzko: Created page with "Not all devices need a Linux kernel driver in order to work properly. The following is a list of some of these types of devices. == USB devices == Most of these should not ..."

Not all devices need a Linux kernel driver in order to work properly. The following is a list of some of these types of devices.

== USB devices ==

Most of these should not need in-kernel drivers beyond those that already exist. Userspace can access USB devices via [http://libusb.sourceforge.net libusb], or soon via [http://wiki.cs.pdx.edu/usb/usbfs2.html usbfs2].

=== USB Scanners ===

These devices use [http://libusb.sourceforge.net libusb] and the [http://www.xsane.org xsane] project to access the device properly. Please contact that project if you need new devices supported.

=== USB Digital Cameras ===

For digital cameras, first check if the camera shows up as a mass storage device; if not, see [http://www.gphoto.org/ gphoto].

=== USB Media Players (music, video) ===

If the device shows up as a mass storage device, then either it finds media automatically (no driver needed) or it needs a magic media index built (userspace support needed only). If the device does not show up as a mass storage device, it can have a driver written in userspace (no kernel driver needed, often using [http://libusb.sourceforge.net libusb]). Such userspace drivers exist for e.g MTP devices (see [http://libmtp.sourceforge.net libmtp]), NOMAD devices ([http://libnjb.sourceforge.net/ libnjb]).

=== Mobile Phones ===

Mobile phones can typically present several types of interfaces, sometimes all at once. They are all already supported through kernel drivers or userspace libraries.

==== Mass storage interface ====

Kernel driver available, but occasionally device quirks need to be specified for new phones.

==== CDC ACM Modem ====

Supported by cdc_acm kernel driver.

==== OBEX filetransfer interface ====

Supported through [http://www.openobex.org libopenobex] (which is using libusb) and various frontends to that library.

==== OBEX SyncML interface ====

Supported through [http://www.opensync.org OpenSync] and libsyncml library that it includes (that in turn is using libopenobex).

==== Nokia FBUS interface also known as DKU2 interface ====

Supported by [http://www.gnokii.org] through libusb.

==== Generic serial interfaces ====

Supported by kernel drivers.

==== Windows Mobile RNDIS interface ====

Supported via rndis_host driver. Check [http://www.synce.org/index.php/Connecting_your_Windows_Mobile_2005_device_via_USB_(usb-rndis-lite) this] and [http://ohioloco.ubuntuforums.org/showpost.php?p=3588717&postcount=54 this].

== Printers ==

All Linux printer drivers are done in userspace. Contact the [http://www.linuxprinting.org Linux Printing Project] if you have a printer that you wish to get properly supported under Linux.

== Video Cards ==

A number of video cards are directly supported by the [http://www.x.org x.org] project and do not need a kernel driver. However, for some newer devices, to get properly 3d graphics support, a kernel driver is needed to help out the X side. We will be glad to help out with the kernel driver for projects like this if needed.

== GPS ==

For GPS devices, see [http://gpsd.berlios.de/ gpsd]

== Fingerprint Readers ==

These are the same as scanners mentioned above, kernel drivers are not needed. The [http://www.reactivated.net/fprint/wiki/ fprint project] supports a lot of fingerprint scanners found in consumer devices.

== Spectrometers and Colorimeters ==

These devices are used for colour calibration and profiling. A number of them are supported via the [http://www.argyllcms.com Argyll CMS project] and don't need a kernel driver.

== Winmodem devices ==

The large majority of these devices are already supported by the ALSA modem drivers, and should work just fine in the latest version of your favorite Linux distribution.

== FireWire Audio devices ==

FireWire Audio devices are handled in userspace; see the [http://www.ffado.org/ FFADO project].

== Uninterruptible Power Supplies (UPS) ==

These devices, whatever the bus used (serial, USB, network), use [http://www.networkupstools.org Network UPS Tools] project to access the device properly. Please contact that project if you need new devices supported.

Windows Mobile

2012-05-07T03:59:45Z

Tomasz Grzegurzko: Created page with "* USB support for Windows Mobile 6 Internet Sharing - Please read before deleting AGAIN. Windows Mobile 6 introduced a NEW method of internet sharing using PAND networking. ..."

* USB support for Windows Mobile 6 Internet Sharing - Please read before deleting AGAIN. Windows Mobile 6 introduced a NEW method of internet sharing using PAND networking. Linux currently supports this method using Bluetooth. It does '''NOT''' in any way shape or form support PAND via USB and that is what is being requested. The old method of bluetooth and USB DUN worked in Windows Mobile 5 but does NOT work in Windows Mobile 6.
** Where are the references to support your claim? Why does this require a new kernel driver? Accessing the internet via USB with WM6 devices is supported by rndis_host kernel driver, as confirmed by SyncE developer [http://ohioloco.ubuntuforums.org/showpost.php?p=3588717&postcount=54 here]. You can find the instructions for setting up USB connection for example [http://forum.ubuntu-fr.org/viewtopic.php?id=88530 here] - in French, but you can get an idea.
*** I stand corrected. Following the SyncE developer's instructions allowed me to connect via USB to internet sharing. It only worked using the SVN version and not the module on sourceforge. Thank you for the info.
<nowiki>
--
ohci_hcd 0000:02:02.0: wakeup
usb 3-2: new full speed USB device using ohci_hcd and address 121
usb 3-2: new device found, idVendor=0bb4, idProduct=0303
usb 3-2: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-2: Product: Generic RNDIS
usb 3-2: Manufacturer: HTC
usb 3-2: SerialNumber: ###############
usb 3-2: configuration #1 chosen from 1 choice
rndis0: register 'rndis_host' at usb-0000:02:02.0-2, RNDIS device, XX:XX:XX:XX:XX:XX
--
rndis0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2002:d036:7557:10:8200:60ff:fe0f:e800/64 Scope:Global
inet6 addr: fec0::10:8200:60ff:fe0f:e800/64 Scope:Site
inet6 addr: fe80::8200:60ff:fe0f:e800/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1460 Metric:1
RX packets:10884 errors:10759 dropped:0 overruns:0 frame:0
TX packets:8178 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13692482 (13.0 Mb) TX bytes:1147593 (1.0 Mb)
</nowiki>

Drivers Needed

2012-05-07T03:57:55Z

Tomasz Grzegurzko: Created page with "This is a list of hardware that does not have support on Linux and needs kernel drivers written for them. Note, some types of [[No Linux Dr..."

This is a list of hardware that does not have support on Linux and needs kernel drivers written for them.

Note, some types of [[No Linux Driver Needed|devices do not need Linux kernel drivers]], so please consult that list first and do not include them here.

'''If the device you are concerned about already works in Linux, but not as well as you would like it to, or with reduced functionality, please do not list it here.''' Instead, contact the author of the driver and work with them to fix the problem or add the new features. [http://bugzilla.kernel.org/ bugzilla.kernel.org] is the proper place to report such bugs and feature requests for existing drivers.

If the device you are concerned about only works with a proprietary driver, that does not count as proper Linux support; please list it here, and note the existence of the proprietary driver as it may provide useful resources for writing a Free Software driver. This includes network cards only supported by ndiswrapper and a Windows driver.

Try to keep these devices sorted by type and possibly manufacturer. The developers of the Linux Driver Project will use this list to contact the companies involved to try to create Linux drivers for them.

If there are devices with already created drivers, but the drivers are not in the kernel tree, please add them to the OutOfTreeDrivers page, do not put them on this page.

Wherever possible, please give the device product and vendor ids (for PCI and USB devices) as well as the full name the manufacturer uses.

If you do not wish to create a wiki account, just to edit this list, feel free to email [[User:GregKH|GregKH]] your requests, or send them to [[Developers]] [[Mailing Lists]].

== Storage devices ==
=== SCSI controllers ===
* Adaptec SCSI Controllers with HostRAID - HostRaid kernel module (a320raid) is closed source. Seems that there is no linux distro which supports system installation on HostRaid raid volumes. Dmraid has limited support for hostraid now. I read that dmraid was part of SLES10SP1 but I failed installation on machines with HostRaid.

=== SATA controllers ===
* Marvell 88SE6111 (found in Asus P5K SE for example). There's some code written by Marvell available for download from Asus' support page, although I'm not sure about the license.
* Marvell 6141, made by Marvell Technology Group Ltd.
* Initio 162x. Half-working driver (sata_inic162x) exists but virtually useless (LBA48 doesn't work). More info from the vendor required.
* Promise RAID controllers http://www.promise.com/support/support_eng.asp
* ALL Highpoint RocketRAID controllers(except RR3xxx/4xxx supported by driver/scsi/hptiop.c) only have binary vendor drivers, which include raid1.o raid5.o etc. for fakeraid support. Highpoint labels them Open Source, but '''MODULE_LICENSE''' is Proprietary (see http://www.highpoint-tech.com/USA/bios.htm)
* [http://linux-ata.org/driver-status.html Serial ATA (SATA) Linux hardware/driver status report] lists cards that have drivers.

=== USB Storage Devices ===
* Kingston DataTraveler Secure (AES encrypted USB flash device)
* LG Cosmo cell phone (the one sold at Brazil). It should work as a Mass Storage Device, however, current kernel driver does not work.

=== Flash media readers ===
* O2 OZ711Mx controller 1217:7110, by o2 Micro, a card reader for MMC/SD/MemoryStick(Pro), [http://mmc.drzeus.cx/wiki/Controllers/O2/OZ711Mx more info (page no longer available)]
* Toshiba TypA SD controllers (PCI ID 1179:0805) - not SDHCI compatible.
* TIFM controllers for XD and Smartmedia - Memory Stick support exists in Subversion and seems to work (provides a generic Memory Stick class for drivers to hook into) (MMC/SD functionality is believed to work while is generally faulty)
* Ricoh R5C843 xD/memorystick support (PC Card and SD currently working).
* Ricoh R5C576 SD Bus Host Adapter
* Ricoh R5C592 Memory Stick Bus Host Adapter
* Rioch Co Ltd xD-Picture Card Controller (rev 05).
* ENE CB710 - multi card reader, no driver available.
* ENE Technology Inc. - multi card reader, no driver available, for Acer Aspire Laptops.
=== Turbo memory controllers ===
* Intel turbo memory controller - Drivers not available. Intel refuses to release specs.

=== External NAS/RAID storage devices ===
These "should" not need kernel drivers, but there are some exceptions:
* Raw NAS storage like the Netgear SC 101. This performs adequately on some Windows systems, and very poorly on others, for reasons which are not obvious. The protocol is proprietary, and some details of the hardware, such as the CPU, are undocumented, so a firmware solution may not be possible. The protocol may be capable of reverse engineering, but it would be better if the manufacturer would do something about it. See also: http://code.google.com/p/sc101-nbd/
* [https://secure.wikimedia.org/wikipedia/en/wiki/Network_Direct_Attached_Storage Network Direct Attached Storage]. There is a proprietary driver at http://code.ximeta.com/

== Video for Linux devices (Input) ==
To reduce the amount of duplicates, please use [http://webcam-osx.sf.net/cameras/index.php this page] for information about the chipset/controller in your webcam.

* [http://ati.amd.com/products/theater650pro/index.html/ ATI Theater\x{2122} 650 PRO] - TV Tuner - ven_1002 / dev_4d50 - see ATITheater650Pro - Out Since 2006
* [http://ati.amd.com/products/tvwonder650/PCI/index.html/ ATI TV Wonder 650] - TV Tuner
* [http://ati.amd.com/products/tvwonderelite/features.html ATI TV Wonder Elite; 550 Pro] - TV/FM Tuner
* [http://ati.amd.com/products/tvwonderproremote/index.html ATI TV-Wonder Pro and Remote Control Support] - I think this is the 550 chipset, but I'm not too sure.
* [http://ati.amd.com/products/tvwonderdigital/index.html ATI TV-Wonder Digital Cable Tuner] with CableCard support.
* The new AMD/ATI HD capture cards listed in http://magicboxlive.blogspot.com/2007/10/amd-new-tuner-products-to-deliver-hdtv.html
* ATI All-In-Wonder (ex. 9700 Pro, X800 XT) Video Card TV-Tuner Support (better support for DVR programs like mythTV)
* [http://www.ali.com.tw/eng/about/index.htm ALi] M560x chipset webcams, as shipped in some Asus and Clevo laptops, plus many standalone webcams from Creative (e.g. [http://us.creative.com/products/product.asp?category=218&subcategory=219&product=14813 Live! Cam Voice] and [http://us.creative.com/products/product.asp?category=218&subcategory=219&product=15442 Video IM Pro]). Some progress has been made at https://sf.net/projects/m560x-driver/
* Anysee E30 C Plus USB2.0 DVB-C Receiver with Conax card reader. http://www.anysee.com/eng/product/anyseeE30CPlus.php
* ASUSTeK TV7162, Hybrid Capture Device. lspci: Multimedia controller: Philips Semiconductors Unknown device 7162 (rev 01) - Subsystem: ASUSTeK Computer Inc. Unknown device 4872, found in Fujitsu Siemens, Scaleo E Mediacenter PC.
* AVerMedia Hybrid TV card M115S (1461:e836, MiniPCI card on SONY VAIO VGN-AR21MR,SONY VAIO VGC-LA1)
* AverMedia AverTV USB2.0 (model M033) tv tuner/video&audio input device. I believe this is based on the DC1100 video chip, which may sometime be supported by http://syntekdriver.sf.net/ if the project gets somewhere.
* AVerMedia AVerTV USB2.0 PLUS (model M036)
* AVerMedia USB2.0 DVB-T A310 Minicard. Based on the Intel CE9500 DVB-T reference design. Contains a Intel CE6230 DVB-T Tuner and a MaxLinear MXL5003F Receiver Chip. Other USB Receivers based on this Design exist. At least one from GoldenBrigde.
* AVerMedia AVerTV Hybrid Volar, USB2.0 dongle - official drivers: http://www.avermedia.com/images/www.avermedia.com_EN/driver_linuxA828_x86.html - DVB works fine, analog TV doesn't. Audio is ok, but picture is pretty bad (TVtime). It feels like there is much less frames per second then it should be.
* AVerMedia AVerTV Hybrid NanoExpress. ExpressCard formfactor. Very NEW,compact tuner. Based on NXP TDA18271, NXP SAA7136E and DVB-T COFDM Intel WJCE6353. AVerMedia representatives said that they will NEVER ever think about creating linux drivers for it. Kernel 2.6.27rc6 saw some part of it, nothing works at all.
* AVerMedia AVerTV cardbus Plus (E501R) PCMCIA - Radio doesn't work, because i2c addresses aren't standard or used multiple times. Depending on which chip is enabled at that time.
* AVerMedia AVerTV Combo PCIe M780 - combines a digital ATSC tuner and a analog tuner in an inexpensive PCIe 1x low profile card. It apparently uses an nGene chip which is not yet supported.
* AVerMedia AVerTV USB MCE (M038), 07ca:1228, [http://www.avermedia.com/AVerTV/Product/ProductDetail.aspx?Id=45 product page at AVerMedia.com]
* [http://www.e3ctech.com/products.html e3C Inc EC168] based USB DVB-T receivers, for example [http://www.teknikmagasinet.se/nydb/db.pl?template_file=link_product.html&link=Produktsok&artnr=480315 this one from .ZAP] with USB ID 18b4:fffb (shows up as HID device, should be more there).
* Genius Look 320s webcam [http://www.geniusnet.co.uk/geniusOnline/online.portal?_nfpb=true&productPortlet_actionOverride=%2Fportlets%2FproductArea%2Fcategory%2FqueryPro&_windowLabel=productPortlet&productPortletproductId=488880&_pageLabel=productPage&test=portlet-action# link]
* Genius Slim 321c webcam [http://osdir.com/ml/macosx.macam.devel/2006-07/msg00031.html link]
* Logitech Trash.MainQuickCam Sphere MP
* Leadtek WinFast TV 2000/XP (rm)
* Leadtek WinFast TV USB2 Deluxe
* HP Pavilion Webcam for the dv2000 series HP laptops
* Hercules Trash.MainWebCam Deluxe
* Trust Sp@cecam 320
* Trust webcam (04f2:a128), www.trust.com/14921
* Webcam Genesys Logic: ID 05e3:0503 [http://www.genesyslogic.com/_en/product_01_1.php?id=40 link]
* There is a project to provide drivers for these Microdia webcams (0c45:xxxx and others) [http://groups.google.com/group/microdia/ here]
** Microdia webcam (0c45:608f), made by Dr. Hank (VC-R035-CD2B).
** Microdia webcam (0c45:624f), made by Microdia, found in Lenovo 3000 N100 0768-A2U.
** Microdia webcam (0c45:6260), made by Microdia, found in some Acer Aspire models.
** Microdia webcam (0c45:627b), made by Microdia, found in Thinkpad Z61t, Frontech e-cam model JIL-2217 [http://www.frontechonline.com/webcam.php?atype=webcam&&model=e-Cam%20(1.3%20MP)&&jilcode=2217 link] Basically rebranded Sonix PC webcams with VGA Sensor SN9C201 + OV7660 chips [http://rsuinux.free.fr/luxya/img-2.jpg link].
** Microdia webcam (0c45:60c0), made by Microdia, found in MSI StarCam Clip.Works with modified driver out of box. http://pamplast.com/gspca/
** Microdia webcam (0c45:8105), made by CyClops sold as a "CyClops DR100"
** Microdia webcam (0c45:6270), made by Microdia, sold separately as a generic 1.3MP webcam. [http://global.msi.com.tw/index.php?func=proddesc&prod_no=632&maincat_no=132&cat2_no=262 link]
** Sonix webcam chipset Trash.MainSN9C201 (chipset in the Microdia webcams above) and SN9C202. There is a closed-source driver [http://www.linux-projects.org/modules/mydownloads/viewcat.php?cid=7 here]
** Microdia webcam (0c45:613b). Branded as Fujitsu Siemens Computers, Webcam USB, Model No: DLV-B16. [http://www.fujitsu-siemens.com/home/products/accessories/multimedia/webcam_usb.html Product page] Now works with sn9c102, 2.6.27 (Mandriva 2009)
** Microdia webcam (0c45:6242), sold as [http://www.bigpockets.co.uk/product.php?product_id=23445 Sumvision Web Camera Panther GT 4MP] (link no longer available)
* Creative Webcam Live! Ultra: there appears to have been [http://gkall.hobby.nl/sq930x.html some work] on making this hardware work already.
* Creative Live! Cam Video IM Pro ( a similar model without the "Pro" is supported but this has a different chipset) Details on camera can be found here: [http://www.qbik.ch/usb/devices/showdev.php?id=3970] This camera uses the ALi M560x chipset, reported above.
* [http://www.ieiworld.com/en/product_IPC.asp?model=PM-1059 IEI Tech. PM-1059] MPEG-4 Audio/Video PC-104+ capture module
* Twinhan model 1027 DVB-S card. Twinhan supposedly released drivers that compile against an old kernel version. They probably need to be ported to the new DVB driver API. Links:
** http://www.linuxtv.org/pipermail/linux-dvb/2007-May/017916.html
** http://www.al7bar.tk/Forums/showthread.php?t=206806
** http://www.mail-archive.com/linux-dvb@linuxtv.org/msg22823.html
* Twinhan model 7045A DVB card. Twinhan has released windows drivers and also a hardware spec for it. The code to make it work already is in the DVB-T tree, somebody "just" needs to glue the TDA10046 frontend to the existing VP7045 backend code. Links:
** http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html
** http://www.flamingspork.com/blog/2006/09/05/twinhan-usb-dtv-dongle-not-working/
* TerraTec Cinergy 2400i DVB-T card. This is a PCIe dual tuner card, which (just like all other known PCIe DVB cards currently on the market) does not have any Linux drivers yet. Links:
** http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_2400i_DVB-T
** http://www.linuxtv.org/wiki/index.php/DVB-T_PCIe_Cards
* TerraTec Cinergy T USB XE DVB-T card. This is a USB digital tuner, with ID 0ccd:0069. This is version number 2 of this tuner, and it uses chip AF9015. Version number 1, ID 0ccd:0055, uses chip AF9005 and works under Linux
* Haupauge HVR-900h DVB/analogue usb tuner with ID 2040:6600 (v4l, tm6010 never completed) -- Main.JanSimonMoeller - 02 Dec 2009
* Hauppauge has not released Linux drivers for their HDTV video capture devices, such as [http://www.hauppauge.com/pages/support/support_hvr950.html WinTV-HVR-950] and [http://www.hauppauge.com/pages/support/support_hvr1600.html WinTV-HVR-1600]
** There is a Linux driver for the HVR-950, but there are issues getting it merged. You can try my http://www.makomk.com/hg/v4l-dvb-makomk driver (more mergable, less tested) or Markus' http://mcentral.de/hg/~mrec/v4l-dvb-experimental/ (more tested, but totally unmergable - please only use it if you have issues with v4l-dvb-makomk) -- Main.AidanThornton - 28 Oct 2007
* Hauppauge Wintv pvr usb.This card is an external tuner card that has a mpeg2 encoder inside...drivers only exist for the 2.4 kernel http://pvrusb.sf.net/
* Logitech Quickcam Notebook
* Terratec Cinergy hybrid T USB XS (USB analogue and digital tv tuner) with ID 0ccd:005e. Note that Marcus Rechberger is working on a userspace driver, which is not likely to be included in the kernel.
** There is a non-userspace driver out there; several versions of it, in fact. The least unmergable is probably my http://www.makomk.com/hg/v4l-dvb-makomk, but it's also the least tested. -- Main.AidanThornton - 28 Oct 2007
* AXIS ARTPEC-1 (Real Time Picture Encoder) ... closed-source driver included on the firmware image in Axis network cameras.
* Chicony Webcam: ID 04f2:b016 Chicony Electronics Co., Ltd, found in HP Pavilion dv2555ea (should work with the Linux UVC driver available at http://linux-uvc.berlios.de - please test and report) Thank you very much, although is not reported it works, unfortunately only for 5-10 seconds
* [http://r-engine.sf.net/ Sony R-Engine] MPEG2 encoder/decoder (0x10cf:0x2011) for VAIO laptops' Motion Eye webcam - also found in some Fujitsu laptops?
* Z-Star Webcam: ID 0ac8:307b Z-Star Microelectronics Corp.
* [http://www.kworld.com.tw/product_overview.aspx?P_ID=14 Kworld TV/FM Tuner PVR-TV PE210] - TV/FM tuner
* Z-Star Microelectronics Corp. - Sansun SN-510 Trash.MainWebCam [hv713d] - USB - ID \x{200e}0x0ac8 - 0x301b
* Z-Star Microelectronics Corp. USB2 - 0ac8:0323
* Ricoh Webcam Ry5u870: 05ca:1830, 05ca:1832, 05ca:1833, 05ca:1834, 05ca:1835, 05ca:1836, 05ca:1870, 05ca:1810. There is a working driver (http://avilella.googlepages.com/r5u870-0.10.0.tgz) but needs to be incorporated in the mainstream kernel.
* The above driver doesn't yet support Ricoh's new cameras like 05ca:1839, which is the Motion Eye included in the Sony Vaio CR, and possibly others.
* Logitech Trash.MainQuickCam Communicate STX. A very rudimentary driver for this [http://home.mag.cx/messenger/ here].
* AverMedia AverTV USB 2.0 - Integrated into several notebooks, also a standalone version available product page: http://www.avermedia.com/cgi-bin/products_tvtuner_avertvusb2.asp
* Video capture with LG GSA-5169D (advanced USB DVD burner).
* ADS-Tech Video Xpress (USBAV-191-EF) [http://www.adstech.com/products/USBAV-191-EF/intro/USBAV_191_intro.asp?pid=USBAV-191-EF]
* ADS-Tech Instant Video To-Go (RDX-160) (H.264 hardware compression accelerator) based on [http://www.mobilygen.com/] SOC which claims to have a Linux SDK. [http://www.adstech.com/products/RDX-160/intro/RDX-160_intro.asp?pid=RDX-160]
* Toshiba PCI DVB-T/Analog Hybrid Tuner
* Techwell 6800 based video capture card
* bttv driver needs to be updated for v4l2
* Adaptec Gamebridge USB devices
* Blackmagic Design [http://www.blackmagic-design.com/products/intensity/ Intensity / Intensity Pro] HDMI capture cards.
* YUAN Analog TV Tuner (Trash.MainExpressCard) (HP Analog Tuner) 1164:0601
* Shenzhen SSTR Technology CO STR-300 USB2 DVB-T TV-Tuner. The em28xx driver at http://www.makomk.com/hg/v4l-dvb-makomk now supports this, needs testing.
* Compro VideoMate H900 analog TV/FM-Tuner with real-time hardware MPEG-1/2 encoder based on Conexant CX23418 video process chip
* Medion TV/DVB-T Combo card CTX953_V.1.4.3. Works with SAA7134 and Card=96 but no audio!
* Pinnacle PCTV HD (800i) TV-Tuner Support [http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_HD_Card_(800i)]
* DVB-S TeVii S400 http://www.ruslink.info/tevii/index.php
* DVB-S TeVii S600 http://www.ruslink.info/tevii/index.php
* Konica Minolta Dimage Xg (it's WebCam mode)
* Pinnacle System Dazzle DVC150 USB2.0 MPEG-2 Encoder http://www.pinnaclesys.com/PublicSite/us/Products/Consumer+Products/Home+Video/Dazzle/Digital+Video+Creator+150.htm
* NVIDIA DualTV MCE TV tuner card http://www.nvidia.com/page/dualtvmce.html
* Pinnacle System PCTV and PCTV PRO
* Multimedia video controller: Unknown device 197d:0ecb (rev 01)
* Multimedia controller: Unknown device 1745:2010
* Vimicro Corp. USB2 Web Camera (0ac8:0323) sold as Zolid 1.3MP WEBCAM
* MediaForte SF256-PCP-R (fm801) - radio card ( chip: tea575x)
* Griffin RadioSHARK and RadioSHARK 2: USB AM/FM radio tuners. There is an abandoned userland HID-based control program (http://marius.scurtescu.com/2007/09/21/radioshark2_under_ubuntu) for each, so writing a real driver shouldn't be too difficult
* Emuzed Maui / LSI DVXPLORE, lists as Multimedia controller [0480]: C-Cube Microsystems E4? [123f:8120] (rev b1) in lspci.

== Network devices ==

=== 802.11 Wireless Network cards ===
* [http://en.wikipedia.org/wiki/IEEE_802.11 IEEE_802.11 (Wi-Fi)]
* AMD am1772 chipset
* Atheros old PCI chipsets are only supported by MadWifi/OpenHAL.
* Inprocomm IPNxxxx chips: http://osdir.com/ml/law.gpl.violations.legal/2006-01/msg00013.html
* Marvell TOPDOG USB [0846:9000] and PCI [11ab:2a02] devices.
** Proprietary drivers are available through ndiswrapper all around the net ( look for netmw245.inf (USB) or NetMW24x.inf (PCI) ), though these only work on 32-bit unix. No 64-bit drivers are available.
** See: http://ubuntuforums.org/showthread.php?t=859481 and http://bbs.archlinux.org/viewtopic.php?pid=557623
* Marvell libertas W8300 PCI.
* SiS16x chipsets : http://www.sis.com/download/ -> I gree ->Linux ->Network driver -> SiS160 WLAN controller.
* Socket Mobile Go Wi-Fi SDIO: http://www.socketmobile.com/products/embedded-wireless-communications/wireless-lan-modules/
* ParkerVision WLAN1500 [http://www.parkervision.com/]
* The Eye-Fi Card (http://www.eye.fi/) is a combined SecureDigital storage card and 802.11 network card, designed to add WiFi uploading to digital cameras.
* Broadcom SoftMAC 802.11g USB chipset, used in Linksys WUSB54GSCv2. Not supported by rndis_wlan or b43.
* STMicroelectronics STLC4370 (Nokia 770) - [http://cx3110x.garage.maemo.org/ cx3110x] is a driver for a binary-only wlan stack. No open source driver exists at this point. The STLC4550/STLC4560 (Nokia N8x0) is similar, and supported by [http://stlc45xx.garage.maemo.org/ stlc45xx] and [http://wireless.kernel.org/en/users/Drivers/p54 p54spi]

=== 802.16 Wireless Network cards ===
* [http://en.wikipedia.org/wiki/IEEE_802.16 IEEE_802.16 (WiMAX)]
* Navini Networks Ripwave PCMCIA card (both SCDMA only and PMX "pre-WiMAX" cards)

=== Controller Area Network (CAN) cards ===
[http://lwn.net/Articles/253425/ PF_CAN] is already included in the current Linux kernel but there is a lack of different device drivers.
* Softing [http://www.softing.com/home/en/industrial-automation/products/can-bus/interface-cards/can/usb.php?navanchor=3010140 CANusb]: some of the Softing CAN devices [http://www.softing.com/home/en/pdf/ia/datasheet/can-bus/CAN-Interfaces-Technical-Data-e.pdf have already a Linux driver], but the CANusb is not included in this list.
* IXXAT [http://www.ixxat.com/usb-to-can-compact-interface_en.html USB-to-CAN compact]: there is already a [http://www.ixxat.com/linux_vxworks_driver_en.html driver created by IXXAT] but it is only available with signing an NDA.
* IXXAT [http://www.ixxat.com/usb-to-can-ii-interface_en.html USB-to-CAN II]: this card is not supported by the [http://www.ixxat.com/linux_vxworks_driver_en.html driver created by IXXAT].
* Vector [http://www.vector.com/vi_cancase_xl_en.html CANcaseXL]

=== ISDN cards ===
* working opensource capi in the kernel for FRITZ!Card PCI Proprietary (.o parts) driver exists http://www.avm.de/files/cardware/fritzcrd.pci/linux/suse.93, but the are very old, and are not longer maintained
* working opensource capi in the kernel for hfc based cards (misdn sucks)
* USB Winbond W6694 Driver [http://pdfdata.datasheetsite.com/web/190788/W6694.pdf Specs] ... there is a [http://www.turbocat.net/~hselasky/isdn4bsd/sources/src/sys/i4b/layer1/ihfc2/i4b_wibusb.h BSD Driver]... would be really great and shouldn't be too hard
* LanCapi for [http://www.lancom-systems.de/index.php?i-d=&no_cache=1&L=1&send=GO LANCOM] ISDN/DSL+ISDN router products for using their ISDN functionallity over IP - manufactorer provides specs when asked for

=== Analog Modems ===
* Creative Modem Blaster *PCI* (DI5656 & DI5663)
* Motorola SM56 based Winmodems
* Conexant D110 MDC V.9x Modem unsupported
* Conexant D480 MDC V.9x Modem vendor ID 14f1 device ID 5422, also known as a hsfmodem; there are binary only drivers available from [http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php linuxant] or [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 Dell]
* Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G (ICH7 Family), SubSystem : 1028:01cc Dell Unknown device 01cc
Further information about supported and unsupported modems can be found on [http://www.linmodems.org linmodems.org]

=== ADSL ===
* RNDIS/USB to Dlink ADSL modems.
* Conexant AccessRunner ADSL PCI modem. Proprietary (.o parts) driver exists in http://patrick.spacesurfer.com/linux_conexant_pci_adsl.html , but it don't function in multi-core system. You have to compile kernel with CONFIG_SMP=off.
* Sangoma ADSL and T1/T3 cards. Mix of open and closed source available from the [http://wiki.sangoma.com/wanpipe-linux-drivers manufacturer]. Need better integration with netdev/tty stacks. There's also a F/OSS OpenBSD driver ([http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/ if_san*.{c,h}]) for Sangoma AFT T1/E1.
* ADSL controllers, such as the TI Avalanche used by Dlink 5- and 6-series ADSL routers. These run Linux but the lack of source support for this chip prevents better firmware, such as OpenWrt, being used.
* ADSL Modem HUAWEI SmartAX MT882 USB do not have drivers for kernel 2.6
* Unicorn driver for ADSL modem (USB ID 0483:0137 SGS Thomson Microelectronics). The proprietary driver http://www.bewan.com/bewan/drivers/A1012-A1006-A904-A888-A983-0.9.3.tgz doesn't compile on 2.6.24. On 2.6.22 with patches from community it compiles but works unstable. It is even not any more available on Bewan site (still on [http://www.filewatcher.com/m/A1012-A1006-A904-A888-A983-0.9.3.tgz.1176291.0.0.html filewatcher]).

=== Various network cards ===
* Olicom Token-Ring adapters do not have drivers for kernel 2.6. There is an outdated driver for kernel 2.4 on the Madge website (open source, I'm not sure if compatible with the GPL; doesn't work on SMP kernels), and FreeBSD has a contributed binary driver (with an open source wrapper).
* ZTE MF330 - GSM modem on pcmcia card. Modem is detected, but kernel should create 3 input/output ports in /dev/ (ttyUSB*). Problem is with USB drivers. Check this: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129433
* ADSL Modem HUAWEI SmartAX MT882 USB do not have drivers for kernel 2.6
* Broadcom BCM4210 based Linksys HomePNA 2.0 card have own bug drivers work only Windows driver via NdisWrapper but their not support PROMISC mode.
* Prolific USB network cable pl-2501 appears not to work with the usbnet module, at least with kernel 2.6.9. Module loads but network packets don't get through.
* Many UTMS/GPRS data cards do not work.
* Soerensen EnVision VoIP board: video capture and G.723.1 voice encoding

== Crypto ==
Hardware encryption accelerators:
* <del>[http://www.hifn.com/ HiFn crypto accelerators chipsets] (with full devs doc on [ftp://ftp.hifn.com ftp.hifn.com]). Soekris crypto accelerators has an Hifn chipsets (see http://soekris.com/vpn1401.htm ). We can also find discrete PCI cards using those chipsets. Since June 2006 (and after OpenBSD devs requested it), Hifn provide full developers specifications for their crypto chipsets (HiFn 6500, 7711, 7751, 7811, 795x, 7855), without nda nor registration, on their ftp ( ftp://ftp.hifn.com ). There's an ou-of-free, unmaintained, old driver for HiFn 7951 for [http://sf.net/projects/hifn7951/ kernels 2.2 and 2.4]. There's also an [http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/ OpenBSD driver]). Hifn people seems responsive to developers demand (search for "hifn" on openbsd-misc mailing-list archive, for instance, to get some execs emails), so they may be willing to provide hardware too.</del>
* Broadcom 5820/5821 chipsets do RSA and DSA plus Hardware RNG and some bulk symmetric crypto. Maru has drivers here [http://sourceforge.net/projects/bcm58xx] -- pci id 0x14e4 :: 5821
* cavium nitrox XL based PCI-X accelerator cards.. similar to hifn and Broadcom offerings, but high throughput. pci id 0x177d :: [1,2,3,4, etc..] see [http://www.caviumnetworks.com/acceleration_boards.htm] and [http://www.caviumnetworks.com/processor_security_nitrox.htm]
* The Freescale MPC184 and MPC190 chipsets do RSA, Diffie-Hellman, Elliptic Curve, DES, 3DES, RC4, SHA1, SHA256, MD4, MD5 and HMAC. It also has an on-board PRNG. I know of no Linux or other Open Source drivers for it. The documentation for them ([http://www.freescale.com/files/32bit/doc/ref_manual/MPC1848XXUM.pdf], [http://www.freescale.com/files/32bit/doc/ref_manual/MPC184UM.pdf] and [http://www.freescale.com/files/32bit/doc/ref_manual/MPC190UM.pdf]) appear to fully document all of the data structures and PCI calls needed to use the chip.
** MPC190 appears to be end of life. Which products use an MPC184 chip?

== Sound ==
* Various sound cards; see the [http://www.alsa-project.org/main/index.php/Matrix:Main ALSA project's Sound Card Matrix]. In particular:
** ESI Juli@ (Needs better driver. It causes kernel panics because of midi support not working and that's not the only problem.)
** Conexant CX20551
** ALSA drivers for some exotic (not PC) and ISA hardware with in-kernel OSS drivers
* FireWire devices [[No Linux Driver Needed|do not need Linux kernel drivers]]]
* Digidesign
** USB interfaces: Mbox, Mbox2, and Mbox-mini
** PCI interfaces: Project, project II, pro tools III, pro tools 24, pro tools mix(+), pro tools HD, Digi 001
** PCIe interfaces: Pro Tools HD
* USB Audio: Wireless headset Jabra BT620s doesn't work in USB-mode.
* Bluetooth handsfree support for all devices - (khandsfree is no longer active in http://bluetooth.kmobiletools.org/)
* Diasonic DVR DDR-3000 Series Digital Voice Recorder.
* E-MU Digital Audio Systems
* !HardSID [http://www.hardsid.com/:The HardSID homepage]
* Sigmatel Audio on SB450 southbridge ([http://support.gateway.com/s/Mobile/Q106/Bishop/4006148R/4006148Rsp2.shtml mobo documentation])
* Build in Plusdeck2 tape drive (not usb version) [http://www.plusdeck.com/]
* Zalman ZM-RSSC USB sound card [http://www.zalman.co.kr/eng/product/view.asp?idx=112&code=023] - I'm really just after any affordable sound card with FULL support for S/PDIF optical out. Thought I had a chance with this USB product, but no...
* Frontier Design PCI cards, including Dakota, WaveCenter/PCI.
* 5.1 support for Hercules Muse Pocket.
* Sound Blaster !SigmaTel High Definition Audio (Audigy HD) - There is no sound at all, no volume controls, nothing. There is an error that says GStreamer plugin not detected/installed
* Sondigo Sirocco (http://sondigo.com/sirocco), Wireless 5.1 Soundcard
* ESI !U46DJ Multi-chanel soundcard [http://www.esi-pro.com/viewProduct.php?pid=60]
* Philips Aurillium PSC805 [http://www.p4c.philips.com/cgi-bin/dcbint/cpindex.pl?ctn=PSC805/17&scy=US&slg=en] - usb-audio supports 2 channel looking for support for subdevices such as surround and s/pdif out
* Sweex external soundcard 5.1 with digital in/out USB 2.0 / C-Media CM6207. This card (actually a box) is more or less works using "standard" USB audio class support from ALSA, but lacks bits of functionality that either is implemented using vendor specific extensions or simply ALSA doesn't support it in it's USB driver. Documentation of the CM6207 IC can be found here: [http://erik.slagter.name/pub/6207-datasheet-1.2.pdf], this sheet doesn't seem to be freely available from C-Media but it is distributed with the Sweex box. Also it only works when fed with 4 or more channel data, 2 channel data is broken (alsa bug?).
* Panasonic RR US450 - Digital Voice Recorder (http://www2.panasonic.com/consumer-electronics/support/Audio/Portable-Audio/Recorders/model.RR-US450) Driver available only for MS Vista, none for Linux. Device comes with USB cable.

== Input devices ==
* TwinhanDTV StarBox DVB-S USB2.0 (VP7021) [http://www.twinhan.com/product_satellite_6.asp]
* 6-Degrees of Freedom Headtracker called TrackIR [http://www.naturalpoint.com/trackir/]
* 3D-controllers from [http://www.3dconnexion.com 3DConnexion.com]. They have a old motif-interface today on the Linux platform. Not very well integrated. I think it should be a kernel-module instead. A drop-in, replacement, open source driver is available from John Tsiombikas at [http://spacenav.sf.net]. The open source version works well with Space Navigator. Neither version currently provides the ability to use a 3Dconnexion controller as a general mouse replacement. Currently, programs must specifically implement calls to the SDK to use the controller.
* Apple Remote when used with an [http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/wa/RSLID?mco=31188AB7&fnode=home/shop_ipod/ipod_accessories/cables_docks&nplm=MB125G/A Apple Universal Dock] (the one with an infra-red receiver). There exists driver for this on Mac Mini and Power-/MacBooks, but not for this Dock and Remote combo.
* Novint Falcon force feedback input device (info [http://home.novint.com/products/sdk.php here])
* eBeam Whiteboard device ([http://www.e-beam.com/])
* Mimio XI Whiteboard device ([http://www.mimio.com/]) -- [http://praxis.it.usyd.edu.au/mimiolinux.tar.bz2 some initial work] (builds for kernel 2.6.17 -- 2.6.23 (+?))
* The Fujitsu P7230 Notebook has two special buttons on it, one is marked "ECO" and the other is marked "A". Neither of these buttons elicit any sort of response in X or in the Linux kernel.
* Keyboard Dell Sk-8135 Volume Knob does not function under bleeding edge distros. (info [http://ubuntuforums.org/showthread.php?t=203770], [http://www.spinics.net/lists/xorg/msg28087.html]).
* Graphic tablets other than Wacom, for example Packard Bell PB-GT-150, Genius, and Hyundai graphics tablets.
** The entire range of hand writing tables from [http://www.penpower.com.tw/brand_en/4_0product/4_1pro.html Penpower], usually for Chinese input.
* ShuttleXpress (possibly ShuttlePro as well?) control pad. Currently partially functional. 1 of 5 buttons recognized as a mouse button, each of the jog wheel directions is recognized as a mouse button as well, but behaves oddly. Wheel/knob is not recognized at all.
* Merc Zboard Gaming Keyboard (info [http://ubuntuforums.org/showthread.php?t=395841 here])
* Microsoft Natural Keyboard 4000 (Most special keys don't work at all. Zoom does not work. Keyboard crashes after reset/reboot)
* Logitech MX5000 wireless bluetooth keyboard and mouse, works OK in standard wireless, doesn't work at all in bluetooth mode, none of the special keys work, also would be nice to see the screen be of use on the keyboard.
** The keyboard repeats 10-20 characters when waking up from sleep mode (e.g. after a pause). This a hardware bug with the keyboard, but could maybe be fixed with a specialized driver?
** Some support for the keyboard LCD screen is available from [http://home.gna.org/mx5000tools/ mx5000tools], but doesn't work for all setups.
* Logitech G15 Keyboard. No GamePanel LCD- and programmable extra button Support.
* LCD and control panel for Thecus n3200, n5200 and 1U4500 NAS devices/servers. The LCD/control panel needs a kernel module and a user-space tool. There are sources for a 2.6 kernel module in Thecus GPL downloads: http://www.thecus.com/Downloads/. There are also some reverse-engineered instructions: http://wiki.chaostreff.ch/index.php/Thecus_n5200_Debian#Thecus_Kernel_Patch. As almost all Thecus products have this LCD/control panel, it would be great to persuade the company to try to push this driver upstream.
* Keyboard BTC 8193 (scroll wheel doesn't work, [http://bugzilla.kernel.org/show_bug.cgi?id=9385 kernel.org bug #9385]).
* IBM UltraNav external USB keyboard. (eg http://shop.lenovo.com/SEUILibrary/controller/e/na/LenovoPortal/en_US/catalog.workflow:item.detail?GroupID=38&Code=31P9490&current-category-id=32DC77FF9F7C48E78298CB802038DD45 ). This works fine, except that the trackpoint sensitivity cannot be accelerated. The trackpoint in an internal thinkpad keyboard works brilliantly, and can be configured thus: http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint
* Nokia SU-1B Digital Pen
* C Technologies C-Pen 10 Digital Input Pen
* Finger Print Reader AuthenTec 2810 PCI ID 08ff:2810
* [http://www.jastec.co.kr/ Jastec] touchscreens - you can get a proper serial line e.g. via usb subsystem, but the touchscreen protocol is not known to the kernel.

=== Gaming controllers ===
* Lifetec Erazer joystick
* Logitech G25 Racing Wheel (046d:c294) basics supported by USBHID, but no force feedback, clutch pedal not available
** Update: Logitech G25 Racing Wheel has three mode - basic (046d:c294), extended(046d:c299) and pro(046d:c298). clutch and H-shift work in extended mode. You can switch from basic mode to extended with [ftp://srv.l14.ru/pub/usbtool-0.1.tar.gz usbtool]
* Logitech G15 Keyboard, LCD display, multimedia keys, and M1-3 programable keys.
* Belkin Nostromo N52 Gamepad
* Logitech RumblePad 2 Vibration Feedback Gamepad. No datasheet available.
* Flight Stick 2. usb joystick and throttle by Hori originally for Playstation 2 but drivers are available for Windows XP (tested and confirmed working): [http://www.tamanegi.org/prog/hfsd/ Third party Windows XP/2000 drivers including source code](Japanese site). [http://www.hori.jp/us/contact.html Company contact info]. [http://au.gear.ign.com/articles/562/562988p1.html More info].
* Haptic devices: [http://home.novint.com/ Novint Falcon] (force feedback)
* Genius Maxfire Pandora Pro Mini [http://www.geniusnet.com/geniusOnline/online.portal?_nfpb=true&productPortlet_actionOverride=%2Fportlets%2FproductArea%2Fproduct%2FquerySection&_windowLabel=productPortlet&productPortletproductId=160250&productPortletsectionId=160252&_pageLabel=productPage&test=portlet-action link] (force feedback)

== Video Cards (X.org Output) ==
* Yes, we know all about ATI and nVidia graphic cards, please don't feel like you need to list the specific cards that are not supported, there are teams of developers working right now to address this in an open-source manner: see http://dri.freedesktop.org/wiki/Status
* SiS315/Xabre chipset family direct rendering driver
* Matrox G550 and others. Proprietary driver is available from Matrox, but TV-out feature is not supported in Linux. (Works in Windows only.) Matrox has ceased driver development for its older hardware, and has stated that it has no interest in developing TV-out for Linux. Matrox TV-out quality is extremely high in Windows and it is a shame we can't have it on Linux.
* AIGLX support for S3 Inc. SuperSavage IX/C SDR (rev 05) Driver works, but 2D only.
* Via Unichrome. Proprietary drivers exist along with OpenChrome
* 3D driver for the Prophet Kyro Series graphic cards (STMicroelectronics), there is an old proprietary driver from [http://www.imgtec.com/powerVR/insider/powervr-drivers.asp Imagination Technologies], but only for the 2.4 kernel. X.org developers are [https://bugs.freedesktop.org/show_bug.cgi?id=1652 not interested] in writing a driver unless documentation is released.
* DRI (3D) driver for various Trident chipsets (e.g. CyberBlade series). X.org "trident" driver is 2D only.
** e.g. Trident CyberBlade XPAi1 (PCI ID 1023:8820)
* [http://en.wikipedia.org/wiki/DisplayLink DisplayLink] USB Graphics devices ( [http://www.displaylink.com/shop.html multiple vendors])
* 3D driver for the SIS Series graphic cards[Silicon Integrated Systems], there is an old driver, but no 3D supported.

== Video Cards (Framebuffer) ==
* radeonfb support for the remaining unsupported pre-AVIVO radeon cards like RV410 (nobody is currently working on this according to benh)
* Framebuffer support for AVIVO radeon cards (R500 and later)
* viafb - support for Via Unichrome chipsets enabling hardware accelerated mpeg decoding

== Motherboard Chipsets ==
* Foxconn 662MX - Chipset SiS 966L - Video Problems
* Built-in VIA Technologies, Inc. UniChrome Pro IGP (rev 01) P4M800 NorthBridge Controller ASROCK Motherboard 775VM800

== Musical Instruments ==
* Access Virus TI Synthesizer (http://virus.info)
* M-Audio Keystation 49e USB midi-keyboard (Is not recognized at all, even in lsusb. This may also include other keystation models and usb midi-keyboards from M-audio) (http://www.m-audio.com/products/en_us/Keystation49e-main.html) -> works for me (tm) ... See [http://www.christian-gmeiner.info/wordpress/?p=12 this link]
* Creative Prodikeys keyboard

== Printers ==
See [http://www.linuxdriverproject.org/twiki/bin/view/Main/NoLinuxDriverNeeded#Printers this link] for why this project does not handle printer issues.

== Scanners ==
See [http://www.linuxdriverproject.org/twiki/bin/view/Main/NoLinuxDriverNeeded#USB_Scanners this link] for why this project does not generally handle scanner issues.

== Mobile Phones and Smartphones ==
See [http://www.linuxdriverproject.org/twiki/bin/view/Main/NoLinuxDriverNeeded#Mobile_Phones this link] for why this project does not generally handle mobile phone issues. However, if you are certain that some phone needs a whole new type of kernel driver, you are welcome to demonstrate this (for example with portions of lsusb -v output). [[Windows Mobile]] for example, is a solved case.

== Measurement and Automation ==
* National Instruments -- they provide a free DDK, but they would definitely benefit from mainlined Linux support
* USB Data Acquisition Boards from [http://www.datatranslation.com/products/dataacquisition/usb/default.htm Data Translation]
* It would be nice to have support for PC-based measuring instruments - I'm thinking of my TiePie HandyScope HS3 digital scope and similar items. See http://www.tiepie.nl. I'm not really a programmer, but I'm obviously more than willing to help on this.

== Imaging Devices (e.g. Cameras) ==
* Canon SDKs - Canon provides full-featured SDKs for many of their models. This allows developer to write application to interact with cameras (i.e. controlling the camera to build HDR images). It will be very beneficial to have their driver and SDK available in Linux. This is actually work in progress in the [http://www.gphoto.org/ Gphoto Project]. This is user-land and it works with a small selection of camera, not only Canon. See [http://www.gphoto.org/doc/remote/ Remote Controlling Cameras] for up-to-date information.
* Concord EyeQ 4060AF 4 megapixel digital camera - http://www.concord-camera.com This is a Chinese made digital camera. It may well have been superseded now by another model. There are some Concord models listed in various 'graphics's software such as DigiKam but not this one. It has been tried with both 2.4 and 2.6 kernels but is not even recognised as a USB mass storage device. Just this basic functionality would be good.

== PCI and PCI Express Endpoints ==
There exist a number of PCI and PCI Express ASIC chips or FPGA IP cores that implement either a PCI to local bus bridge or a full scatter/gather DMA endpoint implementation. Although these are not complete devices, the example cores or development boards do require a complementary driver. Those device examples often just DMA to/from a local device memory.
* Altera FPGA soft core and hard core PCI Express endpoint with descriptor based scatter/gather DMA example implementation.
** Altera PCI Express Megacore with the Chaining DMA application running on most Altera FPGA PCIe development boards, the Arria GX PCIe kit is one example: http://www.altera.com/products/devkits/altera/kit-arriagx.html. This has driver project number 012.
* OpenCores.org PCI Bridge to Wishbone * ...

== Uncategorized ==
* Additional keys support for ACER laptops
** Older laptops need polling
** Newer laptops (i.e. all Acer laptops from 2004 onwards, possibly from even earlier) only need their extra keys added to HAL - they do _not_ need a new driver
* Additional keys support for HP Compaq nx6125 Laptop
* ACPI Support for HP Pavillion laptops
* ACPI Support for Samsung R20 and related
* ACPI Support for Samsung R40 and related
* ACPI Support for Toshiba A100 Series Laptops
* ACPI Support for HP Compaq nc6000 Laptop
* ACPI Support for HP Compaq nx6125 Laptop
* ACPI Support for MITAC laptops (8258d model)
* ACPI Support for FSC Amilo Pa 2548 and related.
* Support for Panasonic Let's Note W5 functions (key to power-off internal USB dvd-drive; changing battery charging policy) (probably valid for all "Let's Note" serie)
* Blu-Ray and HD-DVD support. Reading appears to require a [http://sf.net/tracker/index.php?func=detail&aid=1671912&group_id=295&atid=300295 patched UDF filesystem driver] for UDF 2.5. Several sources suggest that writing requires a kernel patch in addition to support from cdrkit or dvd+rw-tools.
* Lightscribe CD/DVD labeling support. (May not need kernel support; if not, move to NoLinuxDriverNeeded. Closed-source driver for x86 only downloadable from lightscribe.com - no public specs.)
* Creative external/internal I/O Hubs (e.g. Audigy 2 ZS, Audigy 4)
* ITE Tech. Consumer Infrared Receiver CIR. Model 8704/8707/8708/8709 series. Not compatible with ITE 8705/8712F Chips for which a driver exists. May be a former SMSC Chip.
* TI OMAP platform drivers, as used in the Nokia Internet Tablets (N800, N810), and currently available in binary-only form from Nokia.
* Ageia PhysX physics accelerator card.
* Bodybugg http://www.bodybugg.com
* Thin Qemu drivers -- i.e. drivers for Linux guests that (1) are as quick as possible in the guest and (2) expose as much host functionality as possible. For instance, hardware accelerated video. Note that this is really a driver+"hardware" project where, in addition to a guest driver, a matching virtualized hardware chunk must be implemented. It would be nifty if the virtualized hardware were documented adequately to permit similar lightweight drivers to be written for non-Linux OSs (although this "requirement" is not in-scope for this forum).
* DDC's ARINC (avionics) cards. They have proprietary drivers ([http://www.ddc-web.com/Products/2/Default.aspx], select software) for Linux for the DD-42976S1 and DD-42977S1, although the 76S1 driver is circa 2004 at the latest. The drivers do appear to be mission-critical-quality.
* TI 1620 with firmware loading found on the HP TC1100 tablet and similar devices JoeBeaty - 9 Nov 2007
* TI SmartCard reader, as found in (for example) the HP NW8240, PCI ID 104C:8035
* Texas Instruments UltraMedia GemCore SmartCard reader, as found in (for example) the Dell D800, PCI ID 104C:8204 -- Main.JensJorgensen - 29 Oct 2007
* Digilent USB JTAG Programming cable (http://www.digilentinc.com/Products/Detail.cfm?Prod=JTAG-USB&Nav1=Products&Nav2=Cables). Cable has own firmware and seems to need windows only software to be able to program micro controllers. Cables can be provided.
* [http://www.passmark.com/products/usb2loopback.htm PassMark USB loopback test plugs]
* Largan Chameleon Digital Camera http://www.largan.com
* RF Kill Switch interface on some Fujitsu-Siemens devices.
* Xyron Wishblade and Xyron Wishblade Personal Media Cutter - these are based on Graphtec plotters and cutters
* SigmaDesigns REALmagic® Xcard http://www.sigmadesigns.com
* HP MDPS (Hewlett Packard Mobile Data Protection System) - An acceleration sensor, similar to IBM's HDAPS (Hard Disk Active Protection System). There has been an patch at the LKML, but it never got integrated into the Kernel due to some open issues (high CPU usage in some cases etc.). Take a look at the LKML thread for more details: [http://lkml.org/lkml/2007/8/11/60]
* lirc drivers for imon_pad remote & VFD from Silverstone LC16M (New version) USB ID ID 15c2:0036
* Windows Vista SideShow devices/displays
* Stargate ACL serial adapters - especially the ACL 16(+) (Note: these adapters are (mostly) ISA, so they might be marginally interesting.) Technical information available here; [ftp://ftp.digi.com/support/legacy/stargate/developers/] That and other info here; [ftp://ftp.digi.com/support/legacy/stargate/index.html] (Note2: the ACL 16(+) also needs firmware written for it, but the technical info covers how to.)
* Inmax USB IMT-0521 Smartcard Reader (USB ID 11c5:0521) [http://www.soft32.com/Download/Free/Inmax_USB_IMT0521_Smartcard_Reader/4-180747-1.html info]
* Pazzles Creative Cutter Inspiration - a paper cutter simialr to the Xyron Wishblade series. Used just like a printer except instead of printing paper, it cuts paper (such as shapes, fonts, etc.)

== Other lists ==
There are quite a few other lists of linux incompatible hardware.
* [http://www.leenooks.com/ Linux Incompatibility List] is a wiki.
* [http://tldp.org/HOWTO/Hardware-HOWTO/incompatible.html Linux incompatible Hardware] from the Linux Compatibility HOWTO is a bit dated.
* http://www.ubuntuhcl.org/
* http://hardware4linux.info/
* http://linux-wless.passys.nl/ this is cohomprensive list of wireless cards, saying also which are unsupported or with unknown status.
* http://www.fsf.org/resources/hw

Out Of Tree Drivers

2012-05-07T03:39:32Z

Tomasz Grzegurzko: Created page with "'''Here is a list of [http://www.opensource.org/ Open Source] (only GPL, BSD, MIT or MPL licenses accepted) Linux drivers that are already written, but are not included in the..."

'''Here is a list of [http://www.opensource.org/ Open Source] (only GPL, BSD, MIT or MPL licenses accepted) Linux drivers that are already written, but are not included in the main Linux kernel.org tree for one reason or another'''. These are all possible projects that the Linux Driver Project developers could undertake to move the driver into the main kernel tree.

'''Note:''' Please do not list closed source drivers here, or ones that contain some kind of licensing issue that prevents them from being merged into the Linux source tree due to a legal issue. If no open source driver exists for the same hardware, please add an entry on DriversNeeded if one does not already exist.

== Drivers by subsystem and type ==

=== Firewire ===
* ToDo:
** http://ieee1394.wiki.kernel.org/index.php/Out-of-tree_Kernel_Drivers
** http://ieee1394.wiki.kernel.org/index.php/To_Do#New_drivers
** http://ieee1394.wiki.kernel.org/index.php/Juju_Migration

=== Networking ===

==== Fixed Ethernet ====
* Chelsio TOE and RDMA support for the Terminator family [http://service.chelsio.com/]
** NOTE: Networking maintainers do not want support for this class of hardware in kernel!

=== Wireless 802.11 ===
* Texas Instruments' ACX100/ACX111/TNETW1450 http://acx100.sf.net/ . See http://acx100.sf.net/wiki/History#Kernel_inclusion kernel inclusion section for some background information on the previous attempt to include it in the mainline kernel, also read http://linuxwireless.org/en/users/Drivers/acx1xx
* 3Com 3CRWE62092A X-Jack PCMCIA : [[http://poldhu.sf.net]]
* [http://linuxwireless.org/en/users/Drivers/ar6k Atheros ar6k (AR6000)] http://git.openmoko.org/?p=kernel.git (try the head [http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/ar6000-2.6.31 ar6000-2.6.31] unless a newer has shown up). It might be a good idea to read the thread starting [http://www.mail-archive.com/openmoko-kernel@lists.openmoko.org/msg09979.html here] first...
* ks7010 microSD wifi card [http://projects.qi-hardware.com/index.php/p/qi-kernel/source/tree/5396a9238205f20f811ea57898980d3ca82df0b6/drivers/net/wireless/ks7010 http://projects.qi-hardware.com]
* [http://linuxwireless.org/en/users/Drivers/rtl819x Realtek r8192xx] 802.11N devices, they are in staging right now.

=== Controller Area Network (CAN, ISO 11898) ===
* pcan http://www.peak-system.com/linux/index.htm Peak-System Technik CAN interfaces (ISA, PC/104, parport, PCI, PCMCIA, USB, PC/104plus, embedded variants)
* lincan http://www.ocera.org/download/components/WP7/lincan-0.3.3.html

=== Misc ===
* iBurst mobile broadband wireless http://sf.net/projects/ibdriver http://en.wikipedia.org/wiki/Iburst
* Zaptel (DAHDI) drivers for the Digum telephony interfaces http://downloads.asterisk.org/pub/telephony/dahdi-linux/
* NDISWrapper http://ndiswrapper.sf.net/ - implements Windows kernel API and NDIS API within Linux kernel, mostly acting as a compatibility layer to be able to load proprietary windows drivers when there is no Linux driver available. Not sure if any kernel developer wants this in mainline at all, so it`s just being listed for completeness here.
* kclown_spy http://clownix.net/ This kernel module permits the display of real-time plots for bandwidth of tcp/udp connexions and for qdiscs monitoring.
* l7-filter http://l7-filter.sf.net/ Linux layer 7 packet classifier
* Pulsar ADSL card http://sf.net/projects/openadsl/
* IMQ http://www.linuximq.net/. IFB was added to mainline to provide similar functionality as IMQ but didn't go all the way thus IMQ is still being used.
* bewan-adsl - Bewan ADSL PCI & USB st driver http://www.bewan.com/
* ipp2p - netfilter module for dealing with P2P applications http://www.ipp2p.org
* arpstar - ARPStar kernel module for protection against arp poisoning http://arpstar.sf.net
* htbinit - Sets up Hierachical Token Bucket based traffic control (QoS) with iproute2 http://sf.net/projects/htbinit
* ksb - kernel SOCKS bouncer http://ksb.sf.net/
* noarp - kernel module for hiding network interfaces http://www.masarlabs.com/noarp/
* portbunny - kernel based highspeed TCP SYN port scanner http://recurity-labs.com/portbunny/
* linmodem - winmodems with Lucent Apollo (ISA) and Mars (PCI) chipsets http://linmodems.technion.ac.il/
* madwimax - user-space driver for the Samsung SWC-U200 Mobile WiMAX USB dongle http://code.google.com/p/madwimax/
* tcpcp - TCP connection passing between apps on different hosts http://tcpcp.sourceforge.net/
* wanpipe - WANPIPE S-series multi-protocol WAN and ADSL adapters http://wiki.sangoma.com/wanpipe-linux-drivers
* mpls-linux Multi Protocol Label Switching stack for the _Linux kernel_ http://sourceforge.net/apps/mediawiki/mpls-linux/index.php?title=Main_Page

== Storage ==
* Oracle ASMLib Kernel Driver http://oss.oracle.com/projects/oracleasm/

=== ATA ===
* Promise Technology RAID controllers: http://www.promise.com/support/support_eng.asp

=== Card Readers ===
* O2Micro OZ711MS1/OZ711MP1 controller, a card reader for MMC/SD/MS Pro - [http://mmc.drzeus.cx/wiki/Controllers/O2/OZ711MP1/MS1 more info, driver for pre-2.6.17-series kernel]
* sdricoh_cs mmc/sd-cardreader http://sdricohcs.sf.net/
* Neuros SD/MMC card readers (davinci.c, dm320_mmc.c, itomap2430_hsmmc.c, omap24xx_mmc.c, omap2430_hsmmc.c, etc). http://www.google.com/search?hl=en&lr=&q=+site%3Asvn.neurostechnology.com+mmc&btnG=Search
* Smart Cards readers drivers http://www.musclecard.com/sourcedrivers.html

=== SCSI ===
* Accusys SCSI raid driver http://uwsg.iu.edu/hypermail/linux/kernel/0710.2/2783.html
* ATARI SCSI (ACSI) [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=56a68a500fcab9e3a9a49ca7fbef14230ab7d144 1], [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c2bcf3b8978c291e1b7f6499475c8403a259d4d6 2] need to be ported from 2.4 kernel
* AEC-671X SCSI adapter driver (atp870u), was working in 2.4 kernel, broken in 2.6.
* ppSCSI, drivers for various parallel-port-to-SCSI chips, so your parallel-port-connected device shows up as a SCSI device. 2.6 version here: http://penguin-breeder.org/kernel/download/
* vscsihba - Virtual SCSI HBA Project http://vscsihba.aboo.org/
* cdemu-vhba - emulates SCSI HBA for cdemu http://cdemu.sourceforge.net/

=== iSCSI ===
* The '''iSCSI Enterprise Target Project''', also known as '''IET'''. As explained in the [http://sourceforge.net/apps/mediawiki/iscsitarget/index.php?title=FrequentlyAskedQuestions IET FAQ], IET is deployed as a kernel module. In contrast with the older iSCSI target IET has been forked from, patching and recompiling the kernel is not necessary in order to use IET.
* The '''iSCSI-SCST''' project. The [http://scst.sourceforge.net/ iSCSI-SCST] project is another actively maintained implementation of an iSCSI target for Linux. Compared to IET, iSCSI-SCST has a higher performance and overcomes several of the limitations of IET. For a detailed comparison of iSCSI-SCST and IET, see also http://scst.sourceforge.net/comparison.html.
* Although the kernel part of the '''Linux SCSI target framework project''' ([http://stgt.berlios.de/ stgt]) has been merged upstream in kernel 2.6.20, both the IET and the SCST projects have a considerable user base. This is because the IET and iSCSI-SCST targets have a higher throughput and lower latency than stgt. The throughput difference can be up to 50% -- see also [https://lists.berlios.de/pipermail/stgt-devel/2007-May/000662.html] or [http://groups.google.com.ph/group/open-iscsi/browse_thread/thread/7f71acbdf08339d]. The performance difference is significant because stgt has been implemented almost entirely in user space, while IET and iSCSI-SCST have been implemented in the kernel. There are no plans to reimplement the stgt iSCSI target in the kernel -- to the contrary, implementing most of it in user space was one of the design goals of the stgt project.

=== Tape ===
* [https://www14.software.ibm.com/webapp/iwm/web/pick.do?source=lstdd lin_tape driver] for IBM scsi/fc tape drives and libraries, open-source rewrite of the older proprietary IBMtape driver
* [http://lkml.org/lkml/2006/12/3/183 FTape driver], [http://lkml.org/lkml/2007/1/11/97 1], [http://web.archive.org/web/20021203052705/www.instmath.rwth-aachen.de/~heine/ftape/ 2]
* [http://www.informatik.uni-oldenburg.de/~delwi/trakker.html HP Colorado Trakker] tape driver

=== Disk encryption ===
* [http://loop-aes.sf.net/ loop-AES] (uncooperative with kernel developers)

== USB ==
* [http://svn.charonmedia.org/svn/vendor/spcp8x5/ Driver for spcp8x5 USB to serial adaptor.] Used in ACT Solutions HomePro/Zwave controller ZCU201.
* Eagle Chipset powered ASDL modem http://www.eagle-usb.org/
* PLX Tech NET 2272 USB controller [http://www.plxtech.com/files/products/net2000/software/selectiontool/NET_2272/Device-side_Software/Linux/NET_2272_Linux_2.6_Serial.htm PLX Tech NET 2272 USB Controller driver]

== Video Input ==

=== Web Cams ===
* Divio NW802 and related (various cameras, various chipsets). [http://nw802.sf.net/ SF project] very infrequently updated
* Ricoh R5U870-based Custom OEM Webcams : http://lsb.blogdns.com/ry5u870 http://marc.info/?l=linux-usb-devel&m=117803950126004
* ov511-new - adds additional decompression to the existing ov511 driver (ubuntu kernel) -- same as ov51x-jpeg? If so may not be suitable for in-kernel, see: http://www.rastageeks.org/ov51x-jpeg/index.php/Main_Page HansDeGoede is working on getting this into the mainline, decompression will go to userspace (libv4l)
* [http://www.ali.com.tw/eng/about/index.htm ALi] M5603c with ov7648 sensor webcams, as shipped in some Asus laptops, or Creative (e.g. [http://us.creative.com/products/product.asp?category=218&subcategory=219&product=14813 Live! Cam Voice] and [http://us.creative.com/products/product.asp?category=218&subcategory=219&product=15442 Video IM Pro]), probably Genuis SLIM321c. A functional driver developped as a sub-driver of GSPCAv2 (Jean-François Moine) exists at http://m560x-driver.svn.sourceforge.net/viewvc/m560x-driver/m560x/branches/m5603c-gspca/ . It needs some test or cleanup before going into gspca tree. Works for me for usb device '''0402:5603''' ALi Corp. USB 2.0 Q-tec Webcam 300 and for '''041e:4055''' Creative Technology, Ltd Live! Cam Video IM Pro. Note the ALi M5602 have nothing common with this driver and is already included in gspca tree.
=== V4L ===
* [http://marvel.sf.net/ V4L driver for Matrox Marvel G200-TV and G400-TV]
* [http://rivatv.sf.net/ RivaTV]: Enables video-in TV tuners that come with nVidia graphics cards.
* [http://www.jusst.de/hg/mantis] Video capture from Mantis based DVB cards - still considered as experimental by the driver author (Found link here: http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C)
* [http://www.linuxtv.org/v4lwiki/index.php/Trident_TM6000] The TV-Master TM6000 is an integrated Video decoder and USB bridge IC from Trident. There is an experimental patch that has several issues. Due to that, it is was not been included in tree, and doesn't compile with the latest kernels, due to the i2c changes.
* [http://gitorious.org/tw68 tw68] - V4L2 driver for Techwell TW6800 based boards

== Video Output ==
* device3dfx kernel driver for Voodoo boards svn://sf.net/projects/glide
* [http://attila.kinali.ch/mga/ mga_vid] driver for Matrox cards
* radeonfb ATOM BIOS parser and support for newer cards http://lwn.net/Articles/215965/ http://thread.gmane.org/gmane.linux.kernel/530781
* DXR3 & Hollywood plus Mpeg2 Decoder card http://dxr3.sf.net/
* radeonlcd http://fdd.com/software/radeon/

== Audio ==
* hardsid driver http://hardsid.sf.net/
* snd_bt-sco - bluetooth SCO sound driver (ubuntu kernel)

== Input Devices ==
* Acer hotkey driver http://www.cakey.de/acerhk/ (Does not work on x86-64 because it calls 32 bit protected mode BIOS routines; it can't be ported to libx86 because this can currently only make 16 bit real mode BIOS calls) (Ubuntu and Mandriva kernels)
* ATI Remote Wonder Plus http://mythtv.wbond.net/remote_wonder_plus_linux/
* Creative DXR2 http://dxr2.sf.net (only works on linux-2.4)
* Panasonic hotkey driver http://www.da-cha.jp/letsnote
* Wacom tablets [http://linuxwacom.sourceforge.net Project homepage]
* lirc http://www.lirc.org (included in Fedora kernel) and the lirc drivers for Hauppauge cards at http://ivtvdriver.org
* [http://www.jan-steinhoff.de/linux/synaptics-usb.html Synaptics USB driver] for cPad and other USB touchpads
* lmpcm_usb - Logitech mediaplay cordless mouse driver (ubuntu kernel)
* xpc rc01 remote control - http://mathema.tician.de/node/416
* Aiptek/Trust USB tablets - http://sourceforge.net/projects/aiptektablet

== Multiport Serial Devices ==
* Digi RealPort ethernet-connected multiport console/serial server [ftp://ftp1.digi.com/support/beta/linux/dgrp/ (dgrp)]
* Digi AccelePort C/X, XEM, Xr and EPC/X driver [ftp://ftp1.digi.com/support/beta/linux/dgap/ (dgap)]
* Digi AccelePort RAS and XP driver [ftp://ftp1.digi.com/support/beta/linux/dgdm/ (dgdm)]
* Digi Neo and ClassicBoard driver [ftp://ftp1.digi.com/support/beta/linux/dgnc/ (dgnc)]
* Equinox/Avocent ESP Serial Hub http://www.connectivity.avocent.com/support/download-drivers/
* Equinox/Avocent SST multiport serial http://www.connectivity.avocent.com/support/download-drivers/ - http://marc.info/?a=115098161800001&r=1&w=2 linux-kernel review

== Data acquisition / custom device control ==
* dmx4linux http://llg.cubic.org/dmx4linux/ (like midi, but for lighting)
* GPIB/IEEE488 USB Controller, model NI GPIB-USB-HS by National Instruments. http://linux-gpib.sf.net/
* linuxclc http://sf.net/projects/linuxclc/ - "This is a Linux 2.4 driver for ISA, PC-104 and serial Indramat CLC cards for SERCOS motion control."
* camac http://www.ifh.de/~ole/camac/ Wiener CC-16 ISA-CAMAC, Jorway J73A SCSI-CAMAC controllers, and a few others
* ccp http://psux1.kek.jp/~kohama/ccp/ccp.html CAMAC, TKO and Fastbus driver for Hoshin CCP-IBM(ISA) controller
* camdrv http://www.awa.tohoku.ac.jp/%7Esanshiro/kinoko/camdrv/index.html CAMAC driver for CC/7700-PCI,CC/7700-ISA,CC/7000-ISA,CCP (PCI/ISA),CCP (PCI-2703A)
* k2927/k2915/acc_unidaq http://www.elc.nias.ac.jp/~daq/software/ drivers for various KineticSystems CAMAC cards

== Hardware monitoring (a.k.a lm_sensors) ==
* TODO table: http://www.lm-sensors.org/wiki/Devices

== VME ==
* SIS1100/SIS3100 PCI to VME interface (VME is a bus architecture popular in high-end physics labs and mission-critical systems) - the existing Linux source can be found at http://www.struck.de/linux1100.htm
* [http://www.awa.tohoku.ac.jp/~sanshiro/kinoko-e/vmedrv/ vmedrv] is a device driver for Linux 2.x for the PCI-VME bus adapter Model 616/617/618/620 manufactured by SBS Technologies (Bit3).

== Test/development cards ==
* ex10 ex10_i2c ex10_spi Modules for Amfeltec eX10 PCI Extender, GPL, included on accompanying CD only.

== ACPI Support ==
* Experimental Toshiba ACPI Driver (needed for Toshset to control fan speeds, LCD brightness, etc.) http://memebeam.org/toys/ExperimentalToshibaAcpiDriver
* acer_acpi - Acer hardware control http://code.google.com/p/aceracpi
* fritzacpi - SuSE's 2.6 AVM kernel modules for fcclassic, fcpci, fcpcmcia, fcpnp, fcusb, fcusb2, fxusb_CZ, fxusb, e2220pc and e5520pc http://www.avm.de/ ftp://ftp.suse.com/pub/suse/i386/10.1/SUSE-Linux10.1-Beta3-Extra/suse/x86_64/km_fritzacpi.

== Hardware offload ==

Howler Screamer G.729 encode/decode offload card. http://www.howlertech.com/static/downloads/hfs-1.3.2.tar.gz

== Non-Driver modules outside of the kernel tree ==

== Filesystems ==
* Lustre [http://www.lustre.org]
* Read-only compressed loop blockdevice [http://debian-knoppix.alioth.debian.org/sources/ cloop]
* Reiser4 http://kernelnewbies.org/WhyReiser4IsNotIn & http://lkml.org/lkml/2006/7/28/180 & http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=668645;page=1;sb=post_latest_reply;so=ASC;mh=25;list=linux
* unionfs http://www.filesystems.org/project-unionfs.html in andrew morton`s -mm tree.
* NAND flash filesystem [http://www.yaffs.net/ YAFFS] ([http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/ cvs])
* novfs - Novell Filesystem (inside OpenSuSE kernel??)
* aufs http://aufs.sf.net/
* fusion proc filesystem - http://directfb.org/wiki/index.php/Fusion_Proc_Filesystem
* openafs - OpenAFS distributed filesystem http://www.openafs.org/
* shfs - Secure Shell File System http://shfs.sf.net/
* Redundant Array of Independent Filesystems - [ftp://ftp.fsl.cs.sunysb.edu/pub/raif/ source] see also the [http://www.filesystems.org/ papers]
** (This may not be the right category for the following)
* uloop - kernel driver for implementing loopdevice in userspace. http://aufs.cvs.sf.net/aufs/aufs/sample/uloop/00readme.txt?view=log
* dm-userspace - similar to uloop, but different, device-mapper-style implementation. http://wiki.xensource.com/xenwiki/DmUserspace
* cowloop - copy-on-write loop driver to be used on top of any other block driver. http://www.atcomputing.nl/Tools/cowloop/
* dm-bbr - Bad Block relocation target (gentoo kernel)
* cdemu - mount bin/cue cd images http://cdemu.sourceforge.net/

== Network Block Devices ==
* [http://www.drbd.org/ DRBD]
* [http://www.it.uc3m.es/~ptb/nbd/ Enhanced Network Block Device (enbd)]
* [http://sourceware.org/cluster/gnbd/ GNBD]
* [http://lpk.com.price.ru/~lelik/AoE/ vblade-kernel] for exporting blockdevices via AoE (ATA Over Ethernet)
* [http://freshmeat.net/projects/kvblade/ kvblade] ditto, but different implementation

== LSM (Linux Security Modules) ==
* Dazuko http://www.dazuko.org/
* LIDS http://www.lids.org/
* MultiADM http://jengelh.medozas.de/projects/multiadm/
* TALPA http://sf.net/projects/talpa/ Intercepts file accesses and allows userspace daemons to vet them. Part of Sophos security products. Please mind discussion thread at http://marc.info/?l=linux-kernel&m=119625408226843&w=2
** (This may not be the right category for the following)
* grsecurity, gadmin and PAX http://grsecurity.org/
* McAfee LinuxShield
* Sophos AntiVirus
* Exec Shield http://en.wikipedia.org/wiki/Exec_Shield , (included in Fedora kernel)

== Virtualization ==
* [http://en.wikipedia.org/wiki/QEMU#KQEMU kqemu] http://www.nongnu.org/qemu/download.html
* VirtualBox virtualization drivers http://www.virtualbox.org/wiki/Downloads
* various VMware drivers as part of the open-vm-tools package http://open-vm-tools.sf.net/
* Mac On Linux - http://mac-on-linux.sf.net/

== Architectures ==
* Linux/98 for PC-98 NEC arch http://linux98.sourceforge.jp/ - deleted by [http://lkml.org/lkml/2003/1/19/1 1], [http://lkml.org/lkml/2006/2/10/71 2]
* [http://www.linuxdevices.com/products/PD6574796610.html NEC Osprey board] (vr4181) [http://lkml.org/lkml/2005/8/7/57 1]
* [http://elinux.org/Linux_Tiny Linux Tiny] patchset to minimize memory footprint and enable booting on embedded and old i386 devices (maintained by Sony)
* VAX port http://linux-vax.sf.net/ http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/jbglaw/vax-linux.git;a=summary git tree
* DENX tree for various embedded architectures: http://www.denx.de/en/Software/GIT
* Tom Tom kernel ARM port and drivers http://www.tomtom.com/gpl

== Uncategorised ==
* Catweasel Advanced Floppy Controller driver http://www.soundtracker.org/raw/cwfloppy/
* Catweasel i/o device drivers... driver for the joystick/mice/keyboard parts (sid part is covered by compatible hardsid, see Audio section), see above for the floppy controller part http://llg.cubic.org/cw/
* parallel port hardware http://www-stud.ims.uni-stuttgart.de/~voegelas/pcf.html
* speakup http://www.linux-speakup.org/
* Texas Instruments UltraMedia Firmware Loader http://penguin-breeder.org/kernel
* PJB100 mp3 player http://openpjb.sf.net/ with patches for recent kernels appearing at http://tech.groups.yahoo.com/group/PJB100-mp3/
* ATOP process counters http://www.atcomputing.nl/Tools/atop/kernpatch.html
* LTTng http://ltt.polymtl.ca/
* http://rick.vanrein.org/linux/badram/ provides support for damaged RAM
* oms
* heci (ubuntu kernel)
* gc-usb (ubuntu kernel)
* rfkill (ubuntu kernel) -- already in mainline? See Documentation/rfkill.txt in the current kernel tree
* tlsup (ubuntu kernel)
* via_chrome9 (ubuntu kernel)
* fasm7400 - rf kill switch for Fujitsu Siemens Amilo M7400 laptop (ubuntu kernel)
* thinkpad_ec - thinkpad embedded controller lpc3 functions, will not be accepted upstream due to authorship issues (written by an anonymous developer). (ubuntu kernel)
* tp_smapi - thinkpad SMAPI support, will not be accepted upstream due to authorship issues (written by an anonymous developer). (ubuntu kernel)
* SGI "ProPack"
* fbcondor - framebuffer console decoration (gentoo kernel)
* airt - advanced incident response assistant tools - http://159.226.5.93/projects/airt.htm
* omnibook - HP laptop support http://sf.net/projects/omnibook
* tpctl - thinkpad system control kernel modules http://tpctl.sf.net
* usbirboy - homemade ir USB receiver http://usbirboy.sf.net/
* parapin - parallel port pin kernel module http://parapin.sf.net/
* legousb - lego mindstorms usb tower kernel driver http://legousb.sf.net/
* sysprof - system-wide profiler http://www.daimi.au.dk/~sandmann/sysprof/
* svgalib - svga graphics on the console http://www.svgalib.org/
* line6usb - usb driver for line6 PODs and the Variax workbench http://www.tanzband-scream.at/line6/
* packetcommand - driver for the em84xx dvd disc access http://www.htpc-forum.de
* em8300 - RealMagic Hollywood+/Creative DXR3 video decoder driver http://dxr3.sf.net
* em84xx - em4xx based mpeg-decoder card driver http://sf.net/projects/em84xx/
* fsam7400 - software killswitch for F-S Amilo laptops and compatibles http://zwobbl.homelinux.net
* pcfclock - driver for the parallel port radio clock sold by Conrad Electronic http://www-stud.ims.uni-stuttgart.de/~voegelas/pcf.html
* rlocate - locate implementation that is always up-to-date http://rlocate.sf.net/
* Crash Utility memory driver http://people.redhat.com/anderson/ (included in Fedora kernel)
* utrace Infrastructure for tracing and debugging user processes: http://people.redhat.com/roland/utrace/ (included in Fedora kernel)
* asus_eee - interface for access to eeepc internals (e.g. fan speed): http://code.google.com/p/eeepc-linux/
* sony - (old) kernels for Sony televisions, set top boxes and similar http://products.sel.sony.com/opensource/

PRJ012

2012-05-07T03:19:18Z

Tomasz Grzegurzko:

== Altera FPGA PCI Express core with Chaining DMA ==

=== Introduction ===

Field programmable gate arrays (FPGA) more and more often come with a PCI Express implementation, either a soft core (i.e. as programmable logic) or as a hard core (i.e. as silicon on-chip). Altera's PCI Express Megacore can be used to instantiate such a core for most FPGA's such as Cyclone II, III, Arria I, II, Stratix II, III or IV. It uses either the on-board transceivers or an external PCIe PHY chip.

The Megacore will instantiate an example end point reference design called "Chaining DMA" which includes a small on-chip memory, as well as a chaining DMA controller that fetches a descriptor table from Root Complex memory and performs the DMA copies in the table.

=== Driver ===

This Linux device driver controls the Chaining DMA application and acts as a working reference design.
* The driver has appeared in the drivers/staging area of the linux-next GIT tree.

=== Progress ===

==== To Do ====

* Implement the character device file operations, have read and write map to synchronous DMA transfers
* Implement asynchronous building of descriptor tables while the DMA engine is running.

==== Finished ====

* Very basic character device interface.

=== Boards ===

* Altera Cyclone II PCI Express "Sendero" development board called, with a Philips/NXP PX1011A x1 PHY.
* Altera's Arria GX PCIe development board, http://www.altera.com/products/devkits/altera/kit-arriagx.html
* Numerous other boards

=== PCI Express core configuration ===

* The current driver-in-development is targetting cores generated with the PCI Express Compiler version 8.1. Goal is to detect and support newer versions.
* The core can be configured as "Legacy" or "Native" PCI Express End Point. Goal is to support both options.
* BAR[0] size must be configured for 32kiB or more.
* BAR[2] size must be configured for 256 bytes or more. This is where the Root Complex (i.e. CPU) memory address of the DMA descriptor tables is written and where the DMA is initialized.
* BAR address sizes can be 32-bit or 64-bit. Goal is to properly detect and support both.
* The Device ID and Vendor ID must be unchanged, i.e. 0x???? and 0x????. You may change the Sub system vendor and device ID to your liking.

=== Documentation ===

* PCI Express Compiler User Guide 8.0, especially chapter 7 applies. http://www.altera.com/literature/ug/ug_pci_express.pdf
* AlteraForum postings, especially this thread: http://www.alteraforum.org/forum/showthread.php?t=2987&page=1
* http://www.altera.com/products/devkits/altera/kit-arriagx.html

=== DMA Header (in End Point memory BAR[2]) ===

{|
!address
!field
!DMA Read or Write
!comment
|-
|0x00
|Global Control & Number of Descriptors
|W
|-
|0x04
|Bus Address (upper) of Descriptor Table
|W
|Points to a table in Root Complex memory
|-
|0x08
|Bus Address (lower) of Descriptor Table
|W
|-
|0x0c
|Reserved & Last Descriptor Available (RCLAST)
|W
|RCLAST = 0 means descriptor #0 is ready for processing by the End Point
|-
|0x10
|Global Control & Number of Descriptors
|R
|-
|0x14
|Bus Address (upper) of Descriptor Table
|R
|-
|0x18
|Bus Address (lower) of Descriptor Table
|R
|
|-
|0x1c
|Reserved & Last Descriptor Available (RCLAST)
|R
|RCLAST = 0 means descriptor #0 is ready to be acted-upon by the End Point
|-
|}

Notes:
* The fields must be written by DWORD writes, i.e. in Linux use iowrite32().
* The fields only have write access. Reading from these address will return a PCIe error (this can hang your system!).
* Writing to the 0x0c or 0x1c location starts the corresponding DMA operation.
* Does the design support DMA read and write operation concurrently?
* The Root Complex may increment RCLAST during the DMA transfer (this is not tested yet).

=== DMA Table (in Root Complex memory) ===
Each Table starts with four 32-bits words (16 bytes) in which the DMA controller will write its progress, followed by an array of descriptors, each four 32-bits words (16 bytes) in size.

{|
!address
!field
!Access
!comment
|-
|0x00
|Reserved
|R/W
|-
|0x04
|Reserved
|R/W
|
|-
|0x08
|Reserved
|R/W
|-
|0x0c
|Reserved & Last Descriptor Completed (EPLAST)
|R/W
|-
|0x10
|Control & Transfer Length (DWORDS)
|R/W
|Descriptor #0
|-
|0x14
|End Point address
|R/W
|Descriptor #0
|-
|0x18
|Bus Address (msb) for Root Complex memory
|R/W
|Descriptor #0
|-
|0x1c
|Bus Address (lsb) for Root Complex memory
|R/W
|Descriptor #0
|-
|0x20
|Control & Transfer Length (DWORDS)
|R/W
|Descriptor #1
|-
|0x24
|End Point address
|R/W
|Descriptor #1
|-
|0x28
|Bus Address (msb) for Root Complex memory
|R/W
|Descriptor #1
|-
|0x2c
|Bus Address (lsb) for Root Complex memory
|R/W
|Descriptor #1
|-
|}

Notes:
* The total table may not exceed 4096 bytes or cross 4096 boundaries. pci_alloc_consistent(..., 4096, ...) will do that for us.
* 4096 bytes gives 255 descriptors. Suppose that each descriptor describes a 4096 byte copy, this gives 255 * 4096 is just a little less of 1 MiB per DMA operation.

== Linux Kernel API's ==

Scatterlists
* http://lwn.net/Articles/234617/
* http://lwn.net/Articles/256368/
* http://lwn.net/Articles/263343/

== Kernel configuration (Kconfig) entry ==

<nowiki>
config ALTPCIECHDMA
tristate "Altera PCI Express Chaining DMA Test Driver"
---help---
The Altera PCIe Chaining DMA test driver will perform tests against
FPGA/ASIC devices that have Altera's PCI Express core with the
Chaining DMA application generated by the Megacore.

Devices range from Cyclone II FPGA with soft PCIe IP core up to a
Stratix IV with a silicon PCIe core.

This driver controls the DMA engine by performing DMA transfers
in loop-back fashion and doing memory compares to verify the loop-
back was succesfull.

The driver acts as a test driver to verify your PCIe core. It may
be used as a basis for your custom logic.
</nowiki>

== Kernel Makefile entry ==
<nowiki>
obj-$(ALTPCIECHDMA) += altpciechdma.c
</nowiki>

PRJ012

2012-05-07T03:18:54Z

Tomasz Grzegurzko: Created page with "== Altera FPGA PCI Express core with Chaining DMA == === Introduction === Field programmable gate arrays (FPGA) more and more often come with a PCI Express implementation, e..."

== Altera FPGA PCI Express core with Chaining DMA ==

=== Introduction ===

Field programmable gate arrays (FPGA) more and more often come with a PCI Express implementation, either a soft core (i.e. as programmable logic) or as a hard core (i.e. as silicon on-chip). Altera's PCI Express Megacore can be used to instantiate such a core for most FPGA's such as Cyclone II, III, Arria I, II, Stratix II, III or IV. It uses either the on-board transceivers or an external PCIe PHY chip.

The Megacore will instantiate an example end point reference design called "Chaining DMA" which includes a small on-chip memory, as well as a chaining DMA controller that fetches a descriptor table from Root Complex memory and performs the DMA copies in the table.

=== Driver ===

This Linux device driver controls the Chaining DMA application and acts as a working reference design.
* The driver has appeared in the drivers/staging area of the linux-next GIT tree.

=== Progress ===

==== To Do ====

* Implement the character device file operations, have read and write map to synchronous DMA transfers
* Implement asynchronous building of descriptor tables while the DMA engine is running.

==== Finished ====

* Very basic character device interface.

=== Boards ===

* Altera Cyclone II PCI Express "Sendero" development board called, with a Philips/NXP PX1011A x1 PHY.
* Altera's Arria GX PCIe development board, http://www.altera.com/products/devkits/altera/kit-arriagx.html
* Numerous other boards

=== PCI Express core configuration ===

* The current driver-in-development is targetting cores generated with the PCI Express Compiler version 8.1. Goal is to detect and support newer versions.
* The core can be configured as "Legacy" or "Native" PCI Express End Point. Goal is to support both options.
* BAR[0] size must be configured for 32kiB or more.
* BAR[2] size must be configured for 256 bytes or more. This is where the Root Complex (i.e. CPU) memory address of the DMA descriptor tables is written and where the DMA is initialized.
* BAR address sizes can be 32-bit or 64-bit. Goal is to properly detect and support both.
* The Device ID and Vendor ID must be unchanged, i.e. 0x???? and 0x????. You may change the Sub system vendor and device ID to your liking.

=== Documentation ===

* PCI Express Compiler User Guide 8.0, especially chapter 7 applies. http://www.altera.com/literature/ug/ug_pci_express.pdf
* AlteraForum postings, especially this thread: http://www.alteraforum.org/forum/showthread.php?t=2987&page=1
* http://www.altera.com/products/devkits/altera/kit-arriagx.html

=== DMA Header (in End Point memory BAR[2]) ===

{|
!address
!field
!DMA Read or Write
!comment
|-
|0x00
|Global Control & Number of Descriptors
|W
|-
|0x04
|Bus Address (upper) of Descriptor Table
|W
|Points to a table in Root Complex memory
|-
|0x08
|Bus Address (lower) of Descriptor Table
|W
|-
|0x0c
|Reserved & Last Descriptor Available (RCLAST)
|W
|RCLAST = 0 means descriptor #0 is ready for processing by the End Point
|-
|0x10
|Global Control & Number of Descriptors
|R
|-
|0x14
|Bus Address (upper) of Descriptor Table
|R
|-
|0x18
|Bus Address (lower) of Descriptor Table
|R
|
|-
|0x1c
|Reserved & Last Descriptor Available (RCLAST)
|R
|RCLAST = 0 means descriptor #0 is ready to be acted-upon by the End Point
|-
|}

Notes:
* The fields must be written by DWORD writes, i.e. in Linux use iowrite32().
* The fields only have write access. Reading from these address will return a PCIe error (this can hang your system!).
* Writing to the 0x0c or 0x1c location starts the corresponding DMA operation.
* Does the design support DMA read and write operation concurrently?
* The Root Complex may increment RCLAST during the DMA transfer (this is not tested yet).

=== DMA Table (in Root Complex memory) ===
Each Table starts with four 32-bits words (16 bytes) in which the DMA controller will write its progress, followed by an array of descriptors, each four 32-bits words (16 bytes) in size.

{|
!address
!field
!Access
!comment
|-
|0x00
|Reserved
|R/W
|-
|0x04
|Reserved
|R/W
|
|-
|0x08
|Reserved
|R/W
|-
|0x0c
|Reserved & Last Descriptor Completed (EPLAST)
|R/W
|-
|0x10
|Control & Transfer Length (DWORDS)
|R/W
|Descriptor #0
|-
|0x14
|End Point address
|R/W
|Descriptor #0
|-
|0x18
|Bus Address (msb) for Root Complex memory
|R/W
|Descriptor #0
|-
|0x1c
|Bus Address (lsb) for Root Complex memory
|R/W
|Descriptor #0
|-
|0x20
|Control & Transfer Length (DWORDS)
|R/W
|Descriptor #1
|-
|0x24
|End Point address
|R/W
|Descriptor #1
|-
|0x28
|Bus Address (msb) for Root Complex memory
|R/W
|Descriptor #1
|-
|0x2c
|Bus Address (lsb) for Root Complex memory
|R/W
|Descriptor #1
|-
|}

Notes:
* The total table may not exceed 4096 bytes or cross 4096 boundaries. pci_alloc_consistent(..., 4096, ...) will do that for us.
* 4096 bytes gives 255 descriptors. Suppose that each descriptor describes a 4096 byte copy, this gives 255 * 4096 is just a little less of 1 MiB per DMA operation.

== Linux Kernel API's ===

Scatterlists
* http://lwn.net/Articles/234617/
* http://lwn.net/Articles/256368/
* http://lwn.net/Articles/263343/

== Kernel configuration (Kconfig) entry ==

<nowiki>
config ALTPCIECHDMA
tristate "Altera PCI Express Chaining DMA Test Driver"
---help---
The Altera PCIe Chaining DMA test driver will perform tests against
FPGA/ASIC devices that have Altera's PCI Express core with the
Chaining DMA application generated by the Megacore.

Devices range from Cyclone II FPGA with soft PCIe IP core up to a
Stratix IV with a silicon PCIe core.

This driver controls the DMA engine by performing DMA transfers
in loop-back fashion and doing memory compares to verify the loop-
back was succesfull.

The driver acts as a test driver to verify your PCIe core. It may
be used as a basis for your custom logic.
</nowiki>

== Kernel Makefile entry
<nowiki>
obj-$(ALTPCIECHDMA) += altpciechdma.c
</nowiki>

PRJ008

2012-05-07T02:54:01Z

Tomasz Grzegurzko: Created page with "Patch for original driver can be found at: * http://www.madingley.org/macmini/ * http://www.madingley.org/macmini/kernel/ir.patch"

Patch for original driver can be found at:
* http://www.madingley.org/macmini/
* http://www.madingley.org/macmini/kernel/ir.patch

PRJ002

2012-05-07T02:53:33Z

Tomasz Grzegurzko: Created page with "== Summary == VOIP gateway solution needs a driver. The company needs a sound type driver like the Au600 device: * http://alsa.opensrc.org/Au600 for their reference platform."

== Summary ==
VOIP gateway solution needs a driver.

The company needs a sound type driver like the Au600 device:
* http://alsa.opensrc.org/Au600
for their reference platform.

PRJ001

2012-05-07T02:52:51Z

Tomasz Grzegurzko: Created page with "== Summary == Create drivers for TI TMP401, Analog Devices AD9833, and Philips PCA9552. Some information has been received from requesting company and just putting things toge..."

== Summary ==
Create drivers for TI TMP401, Analog Devices AD9833, and Philips PCA9552. Some information has been received from requesting company and just putting things together now. They are using these ICs with an AT91SAM9261 which is an ARM926EJ-S-based 32-bit RISC microcontroller. The company is currently using a 2.6.19 kernel but will likely move to the 2.6.21 (or newer) kernel soon.

Hardware monitoring IC will follow Documentation/hwmon/sysfs-interface.

LED driver IC will follow Documentation/leds-class.txt.

== Data Sheets ==
{|
|http://focus.ti.com/docs/prod/folders/print/tmp401.html
|TI TMP401 Data Sheet
|Temperature Sensor
|-
|http://www.analog.com/UploadedFiles/Data_Sheets/AD9833.pdf
|AD9833 Data Sheet
|Programmable Waveform Generator
|-
|http://www.nxp.com/acrobat_download/datasheets/PCA9552_5.pdf
|PCA9552 Data Sheet
|16 bit LED driver
|-
|}

PRJ013

2012-05-07T02:49:47Z

Tomasz Grzegurzko: Created page with "== Summary == Developing a driver for the Zarlink Ethernet Switch(ZL50408) Functonalities required: # read/write switch configuration registers # send /receive control comma..."

== Summary ==

Developing a driver for the Zarlink Ethernet Switch(ZL50408)

Functonalities required:
# read/write switch configuration registers
# send /receive control command frames - for statistics collection, MAC address learning, aging etc.
# send/ receive Ethernet data frames

Hardware Interface:
16 bit CPU interface connected to the local bus of Host Processor

== Design ==
* Operations 1 & 2 exported using a char interfaces. say /dev/zlctrl.

Userspace applications can make use of ioctls for configuration register access and read/write system calls to send/receive control frames.
* Operation 3 exported using network driver interface. say eth1

== References ==
http://agata.pd.infn.it/LLP_Carrier/New_ATCA_Carrier_web/Appnotes_And_Reference_Designs/Zarlink_Application_Notes/ZLAN_026_AppNote_Jun06.pdf

PRJ003

2012-05-07T02:47:55Z

Tomasz Grzegurzko: Created page with "== Summary == Developing a simple driver interface for time code reader/generator PCI card and USB devices. The products have 256 byte memory footprint (I/O space similar to ..."

== Summary ==

Developing a simple driver interface for time code reader/generator PCI card and USB devices. The products have 256 byte memory footprint (I/O space similar to a PC COM port).

Required:
# Read/write into the hardware registers via API or IOCTL calls
# Handle hardware interrupt callback to pass the "time" data so it can be handled with a low latency

Project Status

2012-05-07T02:46:51Z

Tomasz Grzegurzko: Created page with "== Projects currently under development == {| !align="left" | Project ID !Project description !Developer(s) !Project Manager !Status |- |PRJ003 |USB/PCI driver for video..."

== Projects currently under development ==
{|
!align="left" | Project ID
!Project description
!Developer(s)
!Project Manager
!Status
|-
|[[PRJ003]]
|USB/PCI driver for video timestamp device
|BrandonPhilips
|GregKH
|[http://lkml.org/lkml/2009/1/27/314 patch] signed off and in GregKH's tree - should be in 2.6.29
|-
|[[PRJ004]]
|Highspeed datacapture device
|unknown
|Jaya Kumar
|under development
|-
|[[PRJ005]]
|cleanup existing USB driver
|Steve
|GregKH
|under development
|-
|[[PRJ006]]
|video digital demodulator driver
|unknown
|Max
|awaiting hardware completion
|-
|[[PRJ007]]
|tty over TCP driver
|None
|Saravana Krishnamurthy
| Failed dues to absence of time. New developers needed.
|-
|[[PRJ009]]
|firewire DVB driver
|
|
|under development
|-
|[[PRJ010]]
|1Gb network driver
|GregKH
|GregKH
|cleanups needed, basic functionality finished
|-
|[[PRJ011]]
|10Gb network driver
|GregKH
|GregKH
|cleanups needed, basic functionality finished
|-
|[[PRJ013]]
|Ethernet Switch Device Driver
|Linu Cherian, AustinMarton
|Caleb Gordon
|under development
|-
|}

== Projects completed ==
{|
!align="left" | Project ID
!Project description
!Developer(s)
!Project Manager
!Status
|-
|[[PRJ001]]
|3 i2c devices
|-
|[[PRJ002]]
|VOIP gateway driver
|unknown
|Jaya Kumar
|company changed hardware and no driver is needed
|-
|[[PRJ008]]
|macMini IR driver
|GregKH
|GregKH
|completed
|-
|[[PRJ012]]
|Altera FPGA PCIe core
|LeonWoestenberg
|LeonWoestenberg
|completed
|-
|}

[[User:GregKH]] can assign you a new project id, just ask him for one if you really want to create a new project or add an [http://www.proessay.com essay paper].

Please use wiki syntax to provide as much information as possible (links to device descriptions, vendor sites, etc.)

Status is color coded between green and red. Use red only for when there are blocking issues in the project of a magnitude warranting you flagging peoples' attention.

Developers

2012-05-07T02:28:06Z

Tomasz Grzegurzko: Created page with "Developers are essential for the success of the Linux Driver project. Their tasks are: * working with the companies to determine the proper type of driver that is needed for ..."

Developers are essential for the success of the Linux Driver project.

Their tasks are:
* working with the companies to determine the proper type of driver that is needed for the device.
* design and develop the Linux kernel driver according to the Linux Kernel coding style.
* work with the project manager to help answer any questions that the company might have.
* submit the created driver to the Linux kernel mailing lists for inclusion in the main kernel source tree.
* If possible, maintain the driver over time, answering user emails that report bugs and other problems when the driver is used.

If you wish to become a developer on this project (we can always use more), please sign up on the developer mailing list at http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Mailing Lists

2012-05-07T02:27:28Z

Tomasz Grzegurzko: Created page with "There is just one mailing list for the Linux Driver Project: == Developers == The developer mailing list is where the new projects are announced and asked for volunteers from..."

There is just one mailing list for the Linux Driver Project:

== Developers ==
The developer mailing list is where the new projects are announced and asked for volunteers from, discussions about the project either technical or procedural, and is the general location for anyone wishing to help out with the Linux Driver Project.

The list is open to non-members, but HTML is not allowed on the list to cut down on spam. Anyone is allowed to join the list if you wish to help out or ask questions.

More information on how to join the list, and to see the archives of it, can be found at: http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Frequently Asked Questions

2012-05-07T02:26:03Z

Tomasz Grzegurzko: Created page with "Q: You forgot to mention the most obvious benefit to the company, "They might sell more of their devices!" How can they turn down an offer like that? A: Good point :) Q: How..."

Q: You forgot to mention the most obvious benefit to the company, "They might sell more of their devices!" How can they turn down an offer like that?

A: Good point :)

Q: How are you going to write a GPL driver by signing an NDA? Is it going to require a binary blob or some other way of obfuscating the code?

A: No, not at all. I have written many drivers after signing NDAs with companies. They are usually signed either to keep information about the device private until it is announced at a specific date, or to just keep the actual specification documents from being released to the public directly. All code created by this NDA program is to be released under the GPL for inclusion in the main kernel tree, nothing will be obfuscated at all.

Q: This is a lame publicity stunt, Linux development has always been done this way.

A: Well, the NDA program that we have set up with The Linux Foundation is new. But yes, other than that, this is exactly how Linux kernel development has been done. But it is good to point out exactly how it all works for those who are not familiar with how it works.

Q: You are putting the people who do this kind of development for a living out of a job, stop that!

A: This is just not true at all. In fact a number of people who are consultants doing this kind of development have contacted me thanking me for bringing the issue more publicity. They know that some companies really want to pay people to do development and support in order to achieve contractual issues and have some one on the hook for providing support in ways that the community can not guarantee.

Q: Are companies really going to do this?

A: Yes, already we have received a number of serious queries from companies about producing Linux drivers for their devices. More information will be available later when details are firmed up.

Q: Can you write a driver for my [insert device name here] to get it to work? It isn't made anymore and no one has the specs for it.

A: Sorry, but this project is for devices in which we have the specification and hopefully the manufacturer's support. We don't have the time or effort that is needed to reverse engineer the device on our own, sorry.

Q: Do you need developer help for this project?

A: Yes, just drop me an email and I'll add you to the list of people who have volunteered to help out. We are always glad to accept help.

Q: Are companies actually taking you up on this offer?

A: Yes, the initial response to this was amazing, a measurable number of new Linux drivers will be created thanks to this program.

Q: What about helping to get out-of-the-tree GPL drivers into the main kernel tree?

A: A number of people have offered to help out with this in the past, and all code is welcome to Linux. But we aren't going to be pulling in code to the main kernel tree without the permission of the authors.

Q: What about Printer drivers?

A: Printer drivers live in userspace, not in the kernel. Please contact the [http://linuxprinting.org Linux Printing Project] about Linux printer drivers for specific printers and for all Linux printer issues.

Q: What about the BSDs?

A: What about them? They are free to do whatever they wish, I have no input into their development at all, sorry.

Q: What about drivers for video cards?

A: Yes, we will be glad to work on the kernel side of video drivers for Linux

Main Page

2012-05-07T02:23:52Z

Tomasz Grzegurzko:

The Linux Driver Project is focused on creating and maintaining [[Open Source]] Linux kernel drivers for all types of devices.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the [[Company Process]] page.

== Frequently Asked Questions ==

We have quite a long list of [[Frequently Asked Questions]] that you might wish to peruse before asking them to the developers or on the [[Mailing Lists]].

== Mailing Lists ==

We currently have one mailing list, for all [[Developers]]. Please see the [[Mailing Lists]] page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the [[Project Status]] page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of [[Out Of Tree Drivers]], that could be cleaned up and added to the main Linux kernel tree, and one list of [[Drivers Needed]] for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by GregKH, and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact GregKH.

Company Process

2012-05-07T02:22:55Z

Tomasz Grzegurzko: Created page with "If you wish to have Linux drivers written for your device, just follow the simple steps here: Post to the Project Managers mailing list the following information * What t..."

If you wish to have Linux drivers written for your device, just follow the simple steps here:

Post to the [[Project Managers]] mailing list the following information
* What type of device you wish to have supported.
* Summary of technical specs that you have for your device.
* If your company requires an [[wikipedia:Non-disclosure_agreement|NDA]] to be signed to get access to the specifications for this device.
* Anything else you think that the project managers will find helpful in trying to determine the amount of effort that will be needed to support this device.

The project managers will then respond with some followup questions based on your initial query and will work to assign some developers to your project.

Once the proper developers are found, you will probably be required to provide at least one sample of the device to the developer so that they can develop and test the Linux kernel driver. If you wish to pair the developers up with some of your own technical people, that has been found to be the quickest way to answer questions that come up in the normal process of development.

After the driver is developed and you verify that it works properly for you, it will be submitted to the main Linux kernel tree for inclusion in the main Linux kernel source tree that all Linux distributions base their releases on.

If you have further questions about this process, please feel free to contact [[User:GregKH|GregKH]] directly.

Open Source

2012-05-07T02:16:16Z

Tomasz Grzegurzko: Created page with "Linux kernel drivers are created under the GPL license, but dual (BSD, MIT or MPL) + GPL licenses are also accepted. If your company wishes to also have additional licenses a..."

Linux kernel drivers are created under the GPL license, but dual (BSD, MIT or MPL) + GPL licenses are also accepted.

If your company wishes to also have additional licenses applied to the code produced by this group, please contact the developers at the initial start of the project to find out if that is going to be possible.

Main Page

2012-05-04T04:55:02Z

Tomasz Grzegurzko:

The Linux Driver Project is focused on creating and maintaining [[Open Source]] Linux kernel drivers for all types of devices.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the [[Company Process]] page.

== FrequentlyAskedQuestions ==

We have quite a long list of [[FrequentlyAskedQuestions]] that you might wish to peruse before asking them to the developers or on the MailingLists.

== MailingLists ==

We currently have one mailing list, for all [[Developers]]. Please see the [[Mailing Lists]] page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the [[Project Status]] page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of [[Out Of Tree Drivers]], that could be cleaned up and added to the main Linux kernel tree, and one list of [[Drivers Needed]] for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by GregKH, and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact GregKH.

Main Page

2012-05-04T04:51:47Z

Tomasz Grzegurzko:

The Linux Driver Project is focused on creating and maintaining OpenSource Linux kernel drivers for all types of devices.

== About us ==

We are a group of Linux kernel developers (over 400 strong) that develop and maintain Linux kernel drivers. We work with the manufacturers of the specific device to specify, develop, submit to the main kernel, and maintain the kernel drivers. We are willing and able to sign NDAs with companies if they wish to keep their specifications closed, as long as we are able to create a proper GPLv2 compliant Linux kernel driver as an end result.

== Joining ==

If you are a company that wishes to have a Linux kernel driver written and maintained by this group, please go to the CompanyProcess page.

== FrequentlyAskedQuestions ==

We have quite a long list of FrequentlyAskedQuestions that you might wish to peruse before asking them to the developers or on the MailingLists.

== MailingLists ==

We currently have one mailing list, for all [[Developers]]. Please see the MailingLists page for more details.

== Current Projects ==

We have a list of currently running projects, along with some information about past projects on the ProjectStatus page.

As it seems that there are not enough companies asking us to do development for them to keep all of the developers busy, we have started to collect two lists, one list of OutOfTreeDrivers, that could be cleaned up and added to the main Linux kernel tree, and one list of DriversNeeded for hardware that does not currently work on Linux. Please contribute to these lists if you can.

== History ==

This project was started with an announcement to the Linux Kernel mailing list by GregKH, and has enabled many different manufacturers to achieve full Linux support for their devices.

== Questions? ==

If you still have questions, or do not see the answer for what you are looking for, please feel free to contact GregKH.