Now the HPS's stack is in the tree, the "Improving the USB stack in FreeBSD"

is OBE.
This commit is contained in:
Brooks Davis 2009-03-06 04:33:53 +00:00
parent 4bb0265bea
commit 79a50cf940
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=33910

View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.90 2008/11/02 22:48:28 versus Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.91 2009/03/05 18:51:31 danger Exp $
</cvs:keyword>
</cvs:keywords>
@ -739,48 +739,6 @@ href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html">here</a>.</p>
screen.</p></desc>
</idea>
<idea id="usb-update">
<title>Improving the USB stack in FreeBSD</title>
<desc>
<p><strong>Technical contact</strong>: <a href="mailto:luigi@FreeBSD.org">Luigi Rizzo</a></p>
<p>The USB stack in FreeBSD suffers from a few problems, including
lack of functionality (e.g. isochronous support for USB2 devices),
lack of documentation (most of the code is undocumented and
derives from other BSD implementations), lack of support (there
is not, to our knowledge, active development of the stack),
and the fact that it is still running under the Giant lock.</p>
<p>There is an alternate USB stack under development but it also
suffers from its own share of problems: while it supports
isochronous transfers for USB2 and does not run under Giant, it is
also almost completely undocumented, and it exports a different API
from the current one, which in turn causes portability problems for
device drivers that run on top of USB. Additionally, it is not in
widespread use.</p>
<p>The goal of this project is to improve the FreeBSD stack in one
of the following ways:</p>
<ul>
<li>Add documentation and isochronous USB2 transfers to the existing
driver. Documentation also includes a detailed description of the
locking requirements to ease the move to a different locking
architecture;</li>
<li>Add documentation and a compatibility layer to the 'new' usb
stack, and verify that the basic functionality is preserved for
widely used drivers (umass, mouse, keyboard, etc.).
This work will likely require some debugging of the new code
which we expect to be less tested than the existing one, and so
more prone to undetected bugs.</li>
</ul>
<p>The production of suitable documentation in the source is a key
requirement of the project.</p>
</desc>
</idea>
<idea id="pcihotplug">
<title>PCI-Hotplug support</title>