View | Details | Raw Unified | Return to bug 42715
Collapse All | Expand All

(-)usenix-devsummit.sgml (-14 / +17 lines)
Lines 50-57 Stokely</a>.</p> Link Here
50
<p>Committers in person:</p>
50
<p>Committers in person:</p>
51
<ul>
51
<ul>
52
  <li>Robert Watson (rwatson)</li>
52
  <li>Robert Watson (rwatson)</li>
53
  <li>Julian Elischer(julian)</li>
53
  <li>Julian Elischer (julian)</li>
54
  <li>John Baldwin(jhb)</li>
54
  <li>John Baldwin (jhb)</li>
55
  <li>Matt Dillon (dillon)</li>
55
  <li>Matt Dillon (dillon)</li>
56
  <li>David O'Brien (obrien)</li>
56
  <li>David O'Brien (obrien)</li>
57
  <li>Jeffery Hsu (hsu)</li>
57
  <li>Jeffery Hsu (hsu)</li>
Lines 258-264 for 5.0.</p> Link Here
258
<p><strong class="speaker">jhb</strong> : The big thing for 5.0 is to
258
<p><strong class="speaker">jhb</strong> : The big thing for 5.0 is to
259
get the network stack out from under Giant.</p>
259
get the network stack out from under Giant.</p>
260
260
261
<p><strong class="speaker">jhb</strong> : Jefferey Xu and Jennifer Ying
261
<p><strong class="speaker">jhb</strong> : Jefferey Hsu and Jennifer Yang
262
were here to talk about this.  They have the PCBs checked in now.</p>
262
were here to talk about this.  They have the PCBs checked in now.</p>
263
263
264
<p><strong class="speaker">jennifer</strong> : Interface Queues and SynCache
264
<p><strong class="speaker">jennifer</strong> : Interface Queues and SynCache
Lines 304-310 there could be a flag to just say "don't Link Here
304
would help with issues such as the socket code assuming memory is type
304
would help with issues such as the socket code assuming memory is type
305
stable.</p>
305
stable.</p>
306
306
307
<p>Over to alc on the VM system.  Nothing to say.</p>
307
<p>Over to Alan Cox on the VM system.</p>
308
309
<p><strong class="speaker">alc</strong> : Nothing to say.</strong></p>
308
310
309
<p><strong class="speaker">bmilekic</strong> : As much as I might get hated
311
<p><strong class="speaker">bmilekic</strong> : As much as I might get hated
310
for this.  Will preemption stuff go in by 5.0?</p>
312
for this.  Will preemption stuff go in by 5.0?</p>
Lines 610-616 first.</p> Link Here
610
612
611
</div>
613
</div>
612
614
613
<h3>Adillon64</h3>
615
<h3>AMD64</h3>
614
616
615
<div class="discussion">
617
<div class="discussion">
616
618
Lines 618-624 first.</p> Link Here
618
simulator problems.</p>
620
simulator problems.</p>
619
621
620
<p><strong class="speaker">obrien</strong> : The issues are about legal
622
<p><strong class="speaker">obrien</strong> : The issues are about legal
621
and NDA.  Adillon decided on <a href="http://www.freebsdmall.com">FreeBSD
623
and NDA.  AMD decided on <a href="http://www.freebsdmall.com">FreeBSD
622
Mall</a> as the NDA person.  I have not had a working simulator since
624
Mall</a> as the NDA person.  I have not had a working simulator since
623
September.</p>
625
September.</p>
624
626
Lines 635-641 Should we discuss that at another date?< Link Here
635
637
636
</div>
638
</div>
637
639
638
<h3>MIps</h3>
640
<h3>MIPs</h3>
639
641
640
<div class="discussion">
642
<div class="discussion">
641
643
Lines 717-723 out. Polished 4.2. We need to start ma Link Here
717
November is still the date we're shooting for.  We're going to do a
719
November is still the date we're shooting for.  We're going to do a
718
4.7 and a 4.8.  DP3?</p>
720
4.7 and a 4.8.  DP3?</p>
719
721
720
<p>***GET samIDE FROM MURRAY***</p>
722
<p>***GET SLIDE FROM MURRAY***</p>
721
723
722
<div class="discussion">
724
<div class="discussion">
723
725
Lines 867-881 is wrong but this is what I heard)?</p> Link Here
867
5.0 thing.</p>
869
5.0 thing.</p>
868
870
869
<p><strong class="speaker">warner</strong> : Problems with interrupt
871
<p><strong class="speaker">warner</strong> : Problems with interrupt
870
routing in alcPCI?</p>
872
routing in ACPI?</p>
871
873
872
<p><strong class="speaker">takawata</strong> : Cannot handle PCI PCI
874
<p><strong class="speaker">takawata</strong> : Cannot handle
873
interrupt routing.  Many 802.11x have this problem.</p>
875
PCI&lt;-&gt;PCI interrupt routing.  Many 802.11x have this problem.</p>
874
876
875
<p><strong class="speaker">julian</strong> : Is it a problem from Intel?</p>
877
<p><strong class="speaker">julian</strong> : Is it a problem from Intel?</p>
876
878
877
<p><strong class="speaker">takawata</strong> : This is not an Intel
879
<p><strong class="speaker">takawata</strong> : This is not an Intel
878
problem but a problem on our side.  PCI PCI routing code should be
880
problem but a problem on our side.  PCI&lt;-&gt;PCI routing code should be
879
added.  New code is necessary.</p>
881
added.  New code is necessary.</p>
880
882
881
<pre>
883
<pre>
Lines 888-894 GEOM TrustedBSD Malc BusDMA Newbus SM Link Here
888
C++		Cardbus		libwhisk/sysinstall	KOBJ? (no!)
890
C++		Cardbus		libwhisk/sysinstall	KOBJ? (no!)
889
				sparc64
891
				sparc64
890
892
891
Perl Removal	alcPI		Alpha SMP Stability	Pkgs for
893
Perl Removal	ACPI		Alpha SMP Stability	Pkgs for
892
							sparc64, IA64
894
							sparc64, IA64
893
895
894
devd		PCI intr route	document hints		release docs
896
devd		PCI intr route	document hints		release docs
Lines 1016-1022 Prefer the former.</p> Link Here
1016
<p><strong class="speaker">rwatson</strong> : Perhaps we need to create a
1018
<p><strong class="speaker">rwatson</strong> : Perhaps we need to create a
1017
FreeBSD 5 syscall vector.  Could be a new ABI.</p>
1019
FreeBSD 5 syscall vector.  Could be a new ABI.</p>
1018
1020
1019
<p><strong class="speaker">julian</strong> : Aren't there enough other numbers?</p>
1021
<p><strong class="speaker">julian</strong> : Aren't there enough other
1022
numbers?</p>
1020
1023
1021
<p><strong class="speaker">rwatson</strong> : That's one way to look at it
1024
<p><strong class="speaker">rwatson</strong> : That's one way to look at it
1022
and other platforms have done that?  Is that too heavy weight?</p>
1025
and other platforms have done that?  Is that too heavy weight?</p>

Return to bug 42715