Date: Thu, 12 Sep 2002 22:10:08 +0100 (BST) From: Dominic Marks <dominic_marks@btinternet.com> To: freebsd-gnats-submit@FreeBSD.org Cc: jim@FreeBSD.org, keramida@FreeBSD.org, blackend@FreeBSD.org Subject: docs/42715: More fixups to USENIX Summit document Message-ID: <20020912211008.AE069526@host217-41-12-204.in-addr.btopenworld.com>
next in thread | raw e-mail | index | archive | help
>Number: 42715 >Category: docs >Synopsis: More fixups to USENIX Summit document >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Sep 12 14:10:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Dominic Marks >Release: FreeBSD 4.7-PRERELEASE i386 >Organization: National Physical Laboratory, UK >Environment: System: FreeBSD gallium 4.7-PRERELEASE FreeBSD 4.7-PRERELEASE #8: Sun Sep 8 21:32:35 BST 2002 dom@gallium:/usr/obj/usr/src/sys/NIFTY i386 >Description: Correct some more naming problems: Jeffrey Xu -> Jeffrey Hsu Jennifer Ying -> Jennifer Yang MIps -> MIPs (I believe this is the common usage ?) A number of problems I introduced in my previous PR. Mass replace considered evil: Adillion64 -> AMD64 alcPCI -> ACPI samIDE -> SLIDE A few changes which make things clearer, rather than saying: "PCI PCI" when talking about ACPI, which can look like a typo, I've used: "PCI<->PCI". A few whitespace fixes while I'm here, plus wrapping a very long line. Put doc as category this time since Jim reccomended it. Who will win the CC'ed committer race? :-) >How-To-Repeat: NA. >Fix: Index: usenix-devsummit.sgml =================================================================== RCS file: /media/cvs/freebsd/www/en/events/2002/usenix-devsummit.sgml,v retrieving revision 1.6 diff -u -3 -p -r1.6 usenix-devsummit.sgml --- usenix-devsummit.sgml 10 Sep 2002 22:42:21 -0000 1.6 +++ usenix-devsummit.sgml 12 Sep 2002 21:02:13 -0000 @@ -50,8 +50,8 @@ Stokely</a>.</p> <p>Committers in person:</p> <ul> <li>Robert Watson (rwatson)</li> - <li>Julian Elischer(julian)</li> - <li>John Baldwin(jhb)</li> + <li>Julian Elischer (julian)</li> + <li>John Baldwin (jhb)</li> <li>Matt Dillon (dillon)</li> <li>David O'Brien (obrien)</li> <li>Jeffery Hsu (hsu)</li> @@ -258,7 +258,7 @@ for 5.0.</p> <p><strong class="speaker">jhb</strong> : The big thing for 5.0 is to get the network stack out from under Giant.</p> -<p><strong class="speaker">jhb</strong> : Jefferey Xu and Jennifer Ying +<p><strong class="speaker">jhb</strong> : Jefferey Hsu and Jennifer Yang were here to talk about this. They have the PCBs checked in now.</p> <p><strong class="speaker">jennifer</strong> : Interface Queues and SynCache @@ -304,7 +304,9 @@ there could be a flag to just say "don't would help with issues such as the socket code assuming memory is type stable.</p> -<p>Over to alc on the VM system. Nothing to say.</p> +<p>Over to Alan Cox on the VM system.</p> + +<p><strong class="speaker">alc</strong> : Nothing to say.</strong></p> <p><strong class="speaker">bmilekic</strong> : As much as I might get hated for this. Will preemption stuff go in by 5.0?</p> @@ -610,7 +612,7 @@ first.</p> </div> -<h3>Adillon64</h3> +<h3>AMD64</h3> <div class="discussion"> @@ -618,7 +620,7 @@ first.</p> simulator problems.</p> <p><strong class="speaker">obrien</strong> : The issues are about legal -and NDA. Adillon decided on <a href="http://www.freebsdmall.com">FreeBSD +and NDA. AMD decided on <a href="http://www.freebsdmall.com">FreeBSD Mall</a> as the NDA person. I have not had a working simulator since September.</p> @@ -635,7 +637,7 @@ Should we discuss that at another date?< </div> -<h3>MIps</h3> +<h3>MIPs</h3> <div class="discussion"> @@ -717,7 +719,7 @@ out. Polished 4.2. We need to start ma November is still the date we're shooting for. We're going to do a 4.7 and a 4.8. DP3?</p> -<p>***GET samIDE FROM MURRAY***</p> +<p>***GET SLIDE FROM MURRAY***</p> <div class="discussion"> @@ -867,15 +869,15 @@ is wrong but this is what I heard)?</p> 5.0 thing.</p> <p><strong class="speaker">warner</strong> : Problems with interrupt -routing in alcPCI?</p> +routing in ACPI?</p> -<p><strong class="speaker">takawata</strong> : Cannot handle PCI PCI -interrupt routing. Many 802.11x have this problem.</p> +<p><strong class="speaker">takawata</strong> : Cannot handle +PCI<->PCI interrupt routing. Many 802.11x have this problem.</p> <p><strong class="speaker">julian</strong> : Is it a problem from Intel?</p> <p><strong class="speaker">takawata</strong> : This is not an Intel -problem but a problem on our side. PCI PCI routing code should be +problem but a problem on our side. PCI<->PCI routing code should be added. New code is necessary.</p> <pre> @@ -888,7 +890,7 @@ GEOM TrustedBSD Malc BusDMA Newbus SM C++ Cardbus libwhisk/sysinstall KOBJ? (no!) sparc64 -Perl Removal alcPI Alpha SMP Stability Pkgs for +Perl Removal ACPI Alpha SMP Stability Pkgs for sparc64, IA64 devd PCI intr route document hints release docs @@ -1016,7 +1018,8 @@ Prefer the former.</p> <p><strong class="speaker">rwatson</strong> : Perhaps we need to create a FreeBSD 5 syscall vector. Could be a new ABI.</p> -<p><strong class="speaker">julian</strong> : Aren't there enough other numbers?</p> +<p><strong class="speaker">julian</strong> : Aren't there enough other +numbers?</p> <p><strong class="speaker">rwatson</strong> : That's one way to look at it and other platforms have done that? Is that too heavy weight?</p> >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020912211008.AE069526>