blob: e0835adecd066185e516064e31f144019076ddad (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
|
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/4.9R/todo.sgml,v 1.10 2005/10/04 06:52:22 murray Exp $">
<!ENTITY local.rel "4.9">
<!ENTITY title "FreeBSD &local.rel; Open Issues">
<!ENTITY % navinclude.download "INCLUDE">
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
]>
<html>
&header;
<h1>Open Issues</h1>
<p>This is a list of open issues that need to be resolved for FreeBSD
&local.rel;. If you have any updates for this list, please e-mail
re@FreeBSD.org.</p>
<p>As many of these open issues involve merging bus_dma driver changes
from -CURRENT, the <a
href="&base;/projects/busdma/index.html">busdma</a> project page is
also useful.</p>
<h3>Must Resolve Issues for &local.rel;-RC3</h3>
<table class="tblbasic">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>FireWire load failure bug.</td>
<td>Done</td>
<td>matusita@</td>
<td>Reported on <tt>stable@</tt>. Did this ever work after the initial firewire commit to drivers.conf in April? If not, is there any reason to not just back out that commit and not have firewire supported during the install?</td>
</tr>
</table>
<h3>Must Resolve Issues for &local.rel;-RELEASE</h3>
<table class="tblbasic">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>if_dc tested/merged to work with PAE in 4.x</td>
<td>--</td>
<td>luoqi</td>
<td></td>
</tr>
<tr>
<td>busdma infrastructure merges</td>
<td>--</td>
<td>scottl</td>
<td>It's unclear if further bus_dma infrastructure changes need to be merged?</td>
</tr>
<tr>
<td>if_xl</td>
<td>Done</td>
<td>silby</td>
<td></td>
</tr>
<tr>
<td>RAID drivers tested/merged to work with PAE in 4.x</td>
<td>--</td>
<td>scottl</td>
<td></td>
</tr>
<tr>
<td>ACPI merged as optional component</td>
<td>In progress</td>
<td>&a.jhb;</td>
<td>ACPI will be provided as an optional component, turned off by
default.</td>
</tr>
</table>
<h3>Desired Features for &local.rel;-RELEASE</h3>
<table class="tblbasic">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>USB updated to work with PAE</td>
<td>In progress</td>
<td>jmg, joe, luoqi</td>
<td>USB does not currently work with PAE enabled.</td>
</tr>
<tr>
<td><tt>twe</tt> updated for bus_dma/PAE</td>
<td>--</td>
<td>ps</td>
<td>The 3ware <tt>twe</tt> driver needs to be updated for use with PAE in 4.X.</td>
</tr>
<tr>
<td><tt>ciss</tt> updated for bus_dma/PAE</td>
<td>--</td>
<td>ps</td>
<td>The <tt>ciss</tt> driver needs to be updated for use with PAE in 4.X.</td>
</tr>
</table>
<h3>Documentation items that must be resolved for &local.rel;</h3>
<table class="tblbasic">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>ACPI</td>
<td>Done</td>
<td>Murray</td>
<td>Handbook should be updated to note that ACPI can be enabled on
4.9 systems.</td>
</tr>
<tr>
<td>PAE</td>
<td>Done</td>
<td>Murray</td>
<td>Handbook should be updated to explain the basic PAE functionality.</td>
</tr>
</table>
<h3>Testing focuses for &local.rel;</h3>
<table class="tblbasic">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>PAE testing</td>
<td>--</td>
<td>More testing should be done with PAE systems to test device
compatibility and performance. In particular, active systems
with 12 gig of ram or more should be thoroughly tested to make
sure the various memory allocation algorithms in the kernel
still scale properly. There were reports of users running out of
KVA space in -CURRENT with large memory machines.</td>
</tr>
</table>
&footer;
</body>
</html>
|