• Aucun résultat trouvé

XEROX Inter-Office MenlOranduJll

N/A
N/A
Protected

Academic year: 2022

Partager "XEROX Inter-Office MenlOranduJll"

Copied!
3
0
0

Texte intégral

(1)

Inter-Office MenlOranduJll

To

Pilot Design Spec Contributors

From

Dave Redell

Subject

Results of second meeting on the Design Spec.

XEROX

Filed on: <Redell>PilotDS3.memo

Date

January 10, 1978

Location

Palo Alto

Organization

SDD/SD

Our second meeting on January 5 assessed the progress so far and established new goals for getting the various sections submitted for integration. Some modifications to the Table of Contents were adopted and several authorship assignments were revised:

20 January: Sections submitted for integration into first draft.

31

January: First draft of integrated document distributed.

Some modifications to the Table of Contents were adopted and several authorship assignments were revised.

5.0 Internal Interfaces (6.0 Algorithms and Databases)

5.1

5.2

Low-level Mesa support.

To be converted from a subset of the OIS Mesa Functional Spec, in conjunction with Mesa group.

Input/Output Control System

Current draft complete and available for review; comments solicited.

5.3 Input/Output Drivers Disks: rigid

&

local floppy

Current draft complete and available for review; comments solicited.

. X-wire

&

sockets

Exists as notes plus a prototype implementation; a prose description being written.

RS232

Current draft complete and available for review; com ments sol icited.

[Lauer]

[Jarvis] .

[Jarvis]

[Dalal]

[Schwartz]

(2)

. Results of seeond meeting on the Design Spee

5.4

5.5

. 5.6

5.7

5.8

5.9

Tapes: cassette & 9-track Magnetic cards

Printer

Display /keyboard/mouse Data Line Scanner Serial-Interrace

The six items above are all "in limbo", pending clarification of requirements; Pitts will keep an eye on them.

Dynamic Firmware Loading Facility

Meetings with Peter Deutsch and others have raised questions of generality vs.

simplicity; these should be resolved soon.

and the resulting compromise documented.

File Page Transfer Facility

Very little has' been written here; Steve Purcell and Paul McJones will help with the file sections. and one of them may asume primary responsibility.

Virtual Memory Swapper

. Substantial fragments of this section exist;

the issues seem clear enough to proceed with a full draft. (NOTE: the Relocated Memory Manager. formerly section 5.1.

has been subsumed by the swapper.)

File Manager

Nothing has been written here; Steve Purcell and Paul McJones will help with the file sections, and one of them may asume primary responsibility.

Virtual Memory Manager

Substantial fragments of this section exist;

the issues seem clear enough to proceed with a full draft.

Streams

Most of the design exists as a collection of memos; conversion to design-spec format is under way.

5.10 Clocks & timers

5.1 J

This section in somewhat in limbo due to lack of clear requirements; Hugh will keep an eye on it.

Software/ Firmware

Bootload and I nitia lization

This section is somewhat in limbo due to lack of clear requirements; Hugh will keep an eye on it.

[Jarvis]

[Jarvis]

[Jarvis]

[Jarvis]

[Jarvis]

[J.arvis]

[Hankins]

. [Redell]

[MeJones]

[Redell]

[MeJones]

[Lauer]

[Lauer]

[Hankins]

2

(3)

Results of second meeting on the Design Spec

5.12 'Install' Facility

This section is a complete unknown; no one currently has responsibility for it.

5.13 Hardware Roll Can

The roll-call is essentially part of IOCS initialization; not all details are clear. but Pitts will think about it.

5.14 Error Logging

& Auto-reboot

This section is somewhat in limbo due to lack of clear requirements; Bill will keep an eye on it for now.

3

[!lnassigned]

[Jarvis]

[Lynch?]

Références

Documents relatifs

(This step employs the Pup Microcode Boot protocol, which is also used for booting DOs and is documented in [Maxc]&lt;Pup)EtherBoot.press.) Finally, Initial calls

Two button pushes will cause the baseboard to force the current microcode through its boot sequence (warm boot).. The hot and wann boot sequences leave the

drawer, for example (rather than deleting the drawer itself, whatever that would mean) but deleting everything is seldom useful. Perhaps they are all necessary,

The value of a program or pointer variable is a pointer to an existing global frame. All interface records in the new frame are assigned copies of the

lists the name of the current module and its corresponding global frame address (and instance name if one exists) followed by the name of the current

(This allows all of the configuration's global frames to be allocated compactly, without breakage.) If the modules require a specific initialization sequence, the

Thus each volume contains a volume file map, whose primary purpose is to map filelD into volume page number (physical storage address) for each file residing on

Implementing the 64K-based memory system, using the 4Kx4 control store chips, and removing the RS232C and Raven controllers, still does not allow the Options