os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

remove 2 dead tasks

Browse source
This commit is contained in:
Sam Leffler 2009-03-15 23:27:11 +00:00
parent f08789c7e1
commit c26c194513
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=33948
1 changed files with 1 additions and 43 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
en/projects/ideas/ideas.xml
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.112 2009/03/15 14:13:43 luigi Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.113 2009/03/15 14:36:31 luigi Exp $
</cvs:keyword>
</cvs:keywords>
@ -535,27 +535,6 @@ these buses to be a subclass of this new base class.</p>
</desc>
</idea>
<idea id="modrefcnt">
<title>Dynamic module references</title>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:sam@FreeBSD.org">Sam Leffler</a></p>
<p>Kernel modules may have dynamic references created during operation.
For example net80211 key entries reference functions in the crypto module
that implements the key's cipher. Presently there is no standard mechanism
for expressing this dependency so that module unloading is disallowed;
instead modules must track references and implement their own semantics.
This task is to define and implement a general mechanism for tracking
these references and use them in handling module unload requests.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Good knowledge of C.</li>
<li>Kernel awareness.</li>
</ul>
</desc>
</idea>
<idea id="kernel-dvb" class="soc">
<title>Kernel support for linux DVB device drivers</title>
@ -969,27 +948,6 @@ destDir parameter.</li>
</desc>
</idea>
<idea id="wi" class="soc">
<title>Update wi</title>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:sam@FreeBSD.org">Sam Leffler</a></p>
<p>Many new and useful features (e.g. crypto protocols like WPA) of the WLAN
infrastructure in the kernel are not used in wi(4). While wi(4)
cards are old and can not compete with recent wireless cards, they are still
in use in a lot of places. The goal of this item is to examine the WLAN
infrastructure and other WLAN drivers in the tree for nice features and
port/use them in the wi(4) driver.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Knowledge of C.</li>
<li>No fear of undocumented parts of the kernel.</li>
<li>One wi(4) card and one other wireless device to test against.</li>
</ul>
</desc>
</idea>
<idea id="wpa2preauth" class="soc">
<title>WPA2 preauthentication in hostapd</title>