--> ap/xxxxx

* __

link to interface and society slides: 12:54 (2006.11.06:1)

http://www.1010.co.uk/xx_interface_slide1.html

16:02 (2006.11.02:1)

To work into above (below):

1) White rabbit economies

2) faked data sheet. holes in the (op code) map

3) OS -> CPU linkage. OS as a social and economic motif

where we can specify that invisible interface which is the operating system.

terms of:

4) (machine) cycles and circles - comparative slide (1) with Gravity's Rainbow mandala

5) ending with forest light slide

exactly a question of interior and exterior - of a hiding.

Notes from transparencies:

trajectory - elaboration of a data sheet, reverse engineering - zoom out (above/below) from interior to film studio to forest - flip/mirror side of kopf and perhaps Salo

trajectory of inside/outside - a journey outwards (but where we imply economy)

a trajectory through the rings - from inside out or from outside in, rings of protection, circles of hell

operating system - kernel and user space.

? the circle within this trajectory

arriving back where we started within an embedding (parallel tracks). - the film that is Gravity's Rainbow ends with the contemporary (to its writing) crash into the movie theatre (the mirror/flip side of Edison's black maria studio - a quotation/exhibition/execution of that which was scripted so long ago). film studio CPU is thus at the centre.

arriving back within an embedding which is endophysical. the CPU disappears or is erased to become the world. that is the circle end

CPU and world as interface

1) code and hardware (interface). the (Chateau) Silling CPU. designation of interpreter, compiler and questions also of microcode and micro-assembler. code commentary from xxxxx introduction:

Sadean life/live coding, with reference to clear systematics, is of an extreme order, existing in obvious relation to Stewart Home and Florian Cramer's pornographic coding. By way of equally systematic artist Pierre Klossowski we can begin to decode Sade's writing in essential relation to the executable:

The description Sade gives of his own experience in the characters he created covers a twofold experimentation: (1) that of the representation of the sensuous in an aberrant act; (2) that of the described representation.

[Pierre Klossowski. Sade My Neighbour. Quartet books 1992 page 17]

Sade's text is not "purely descriptive" but rather functions as quine-like source code for an interpreter. Again we're near to the closed circuit of expanded hardware - an interiority of code in Klossowski's terms referenced as a bloody Cyclops eye otherwise known as the bedroom. Sade as the primal "coder in the boudoir."

This is made evident in Salo. The frame. The whore/storytellers relating of an aberration interpreted by the machinery (CPU) of the libertines; rendered executable and electric within that circuitry.

A spoken source code, grey as celluloid, lingers within the irreversible miasmic air of the chateau. Even the code comments are there:

Do we read Sade as we read Laclos, Stendhal, Balzac? Clearly not! We would not look to the bottom of the pages of Splendours and Miseries of the Courtesans [ital] for notes that would give prescriptive formulas and recipes for procedures to follow or ways to act in the bedchamber. We do find here and there this sort of pragmatic note at the bottom of the pages of Juliette [ital]... These pragmatic notes belong to the exercise of purest irony.

[Pierre Klossowski. Sade My Neighbour. Quartet books 1992 page 42]

In this code walk through (low level to high level or in reverse to action) we are one step away from execution; the next paragraph. The ambiguity of live/life coding presents a similar exercise in irony/cynicism. Life as code, as dictation. The machine (for living - a house or a body) only does that which it has been instructed to do. Alternatively living coding at the command line; that horizontal prompt proving a horizon for contemplation. Just as Klossowski quite rightly states that such an exercise in the "purest irony," our code comments, would not function is such notes did not achieve "real pragmatic use." They must be capable of being rendered executable, of indicating an outside which is "not at all the interior of the 'bedroom'..." where one would code.

The whores function as a prime example of Sadean life coders and also engage economy. Execution is quite literally the final dance, the two hopeful boys embrace at the close of the film cut across the tubular torture garden at the end of the telescope or kaleidoscope screwing down the Cyclops iris of the film camera. The pinnacle of an always-fictional snuff movie as a sexual reflexivity in the seedy primal location of Edison's Black Maria or Kinetographic theatre. The apparatus here is also in the circuit; perfect end credits of a stopped down lens sequence. A circuit which could be readily coaxed to embrace a particular director's death.

What gives Sade's text its disturbing originality is that through him this outside comes to be commented on as something produced within thought.

[Pierre Klossowski. Sade My Neighbour. Quartet books 1992 page 42]

Full circle. This is the other half of the two rainbow portions left and right forming the loop (antenna); an active circuit articulated by the changes in digital circuitry itself which are effected by the instructions. A setting of switches in strict notated time; a transition from 24 fps to 2.7 GHz, TTL or CMOS modulation within an economy, a system of production impacted by the very wavelength of light. The following can well be compared with Pynchon's electromysticism closing the work:

[possibly as closing forest slide]

... first a series of tales, discourses, then a series of tableaux that slyly invite the reader to see outside what does not seem to lie in the text - whereas nothing is visible anywhere except in the text. His work then is like the vast layout of an urban showroom in the heart of the city, one with the city, where without noticing it one passes from the objects exhibited to objects that exhibit themselves fortuitously without being exhibitable. At length one recognises that it is to these that the corridors of the exhibition lead.

[Pierre Klossowski. Sade My Neighbour. Quartet books 1992 page 42]

2) Seasonal, tabulated program of de Sade (les reglements). Salo making evident quotation. (120 days) Four nobles are isolated in the Chateau Silling for 4 months - November, December, January, February.

4 whores/storytellers/life coders

Salo/chateau as the interior of the CPU

3) KEZVH (p361 Gravity's Rainbow Picador). Klar, Entluftung, Zundstufe, Vorstufe, Hauptstufe (main stage)

In the sky over the Alexanderplatz he has seen Oberst Enzian's KEZVH mandala (p446)

circular design of GR

Dante's inferno. Salo/de Sade - circle of manias, circle of shit, circle of blood. circular mechanism of the black maria. Rings of privilege within the CPU.

Beyond the Zero (GR opening)

4) 6809 Byte design 3 parter: SYNC - allows external hardware to be synchronised

5) A map of the TMS-9900 CPU: with 2 to power of 15.95 legal instructions.

table:

instruction opcode operand operation addressing mode

or:

classsubclassmnemonicoctal op codefull namedescription

6809 classes such as Math, Move, Clear, Branch

I/O as class: subclasses here: Multi-digit, Single-digit and Flags

6) Dotted lines surround the black diagram, a symbolic description; dotted lines mark the cut, the interface between exterior and interior

7) exterior- pin functions and pin assignments

interior idealised - the block diagram

the exo-CPU

8) Features of the Silling/Dee CPU:

x___

further on instruction sets:

Alice stack, off with her head

atrocity exhibition

cpu as chateau

one bit world cyclops instruction

instructions named after four life coders of de Sade:

La Duclos, La Champville, La Martaine, La Desgranges

For Interface and Society presentation: 17:23 (2006.11.01:1)

Opening slide as forest with script (from Byte July 1978. A Short History of Computing):

A few weeks ago a master's degree candidate in computer science confided, with an embarrassed laugh, that he had never seen a computer. His experience with the machine of his chosen vocation had consisted entirely of submitting punched cards through a hole in the wall and later getting the results the same way.

Further notes from other Byte magazines (particularly of interest: A Microprocessor for the Revolution Jan, Feb, Mar 1979 on the design of the 6809 microprocessor):

1] The large computer, being a very expensive resource, quickly justified the capital required to investigate optimum use of that resource. Among the principle results of these projects was the development of batch mode multiprocessing. The computer itself would save up the various tasks it had to do then change from one to the other at computer speeds. This minimised the wasted time between jobs and spawned the concept of an operating system (itals).

2] GOTOlocks and the Three Sorts. Gwen Hadley. Byte Jan 1979

3] Filling 6800 Op Code Holes:

Table 1:

A table of "holes" in the 6800 op code space. Analysing the holes involves tabulating the effect of each instruction on the condition code register, computing the number of machine cycles, and most importantly, finding suitable applications for these instructions.

Tabulated as Instruction Length, Hex Code, Label, Commentary

Hole are nonimplemented op codes in data chart

concludes with:

It would be interesting to find out if all 6800s follow the patterns in my table, or if the results are specific to my individual unit. (ie. unshared as officially undocumented - they may just be an anomaly).

further:

What is position independent code?

In computing, position-independent code (PIC) or position-independent executable (PIE) is machine instruction code that executes properly regardless of where in memory it resides. PIC is commonly used for shared libraries, so that the same library code can be loaded in a location in each program address space where it won't overlap any other uses of memory (for example, other shared libraries). PIC was also used on older computer systems lacking an MMU, so that the operating system could keep applications away from each other even within the single address space of a MMU-less system.

Position-independent code can be copied to any memory location without modification and executed, unlike relocatable code, which requires special processing by a link editor or program loader to make it suitable for execution at a given location. Code must generally be written or compiled in a special fashion in order to be position independent. Instructions that refer to specific memory addresses, such as absolute branches, must be replaced with equivalent program counter relative instructions. The extra indirection may cause PIC code to be less efficient, although modern processors are designed to ameliorate this.

http://en.wikipedia.org/wiki/Position_independent_code

x____

An economy of design and implementation/white rabbit economies of the physical as a thematic.

CPU (and its double) as tied into the OS. An unwritten history of this entry of the OS, a story of protected modes, privilege, segmentation, of rings, by way also of system calls and interrupts - the economic OS enters into and dictates economies of hardware and of the physical

System calls often use a special CPU instruction which causes the processor to transfer control to more privileged code, as previously specified by the more privileged code. This allows the more privileged code to specify where it will be entered as well as important processor state at the time of entry.

Economic interdependency of OS and CPU.

x86: four rings starting at ring 0 (can do anything).

also virtualisation: ring -1

Rings (circles of hell):

In computer science hierarchical protection domains, often called protection rings, is a mechanism to protect data and functionality from faults (fault tolerance) and malicious behaviour (computer security). This approach is diametrically opposite to that of capability-based security.

esp:

http://en.wikipedia.org/wiki/Kernel_mode#Interoperation_between_cpu_and_OS_levels_of_abstraction

links:

http://rr0d.droids-corp.org/ ___ Ring 0 OS independent x86 debugger

http://www.homebrewcpu.com/links.htm

http://incolor.inebraska.com/bill_r/elf/html/elf-1-33.htm ___>

Build The COSMAC "ELF" A Low-Cost Experimenter's Microcomputer Part 1

Progressive zoom out from the black CPU (lens zoom visible or tracking 11:08 (2006.10.24:1 research#101 interface_and_society_notes#5)

obviously still within the black maria film studio which is itself within the forest):

Zoom out follows a trajectory from:

a) CPU interior. - Salo opening bibliography

b) CPU pin outs/data sheet - interface

c) CPU exterior within/at centre of the film studio (as in framed image below)

d) Salo + Welt am Draht KOPF quotation transitions

also note our own MICRO-ASSEMBLER and compression-technology-led permuted films

From: 18:08 (2006.10.23:2 research#100 interface_and_society_notes#4)

W.K.L and Antonia Dickson: History of the Kinetograph (facsimile 2000 MOMA NYC):

p20: regarding the Kinetographic theatre or black maria:

[quote]

As we peer into the illusive depths we seem transported to one of those cheerful banqueting halls of old, where the feudal chief made merry with human terrors, draping the walls with portentious black, and thoughtfully providing a set of coffins for the accommodation of his guests. And what is this mysterious cell at the other extremity, sharply outlined against the dazzling radiance of the middle ground and steeped in an angry crimson hue? Are these inquisatorial dungeons, and is that lurid glare the advance guard of the awful Question? Is that gentle persuasive in process of administration, and do these half-guessed recesses conceal the hellish paraphernalia of rack and screw, glowing iron and crushed stone? Has the doom of ages overtaken our wizard at last, and is he expiating, with twisted limb and scorching flesh, the treasures of his unlawful wisdom? Ah, me! that the prosaic truth must be told. No dungeons are these, thrilling with awful possibilities, but simply a building for the better "taking" of kinetographic subjects.

xx___ 17:51 (2006.10.23:1 research#99 interface_and_society_notes#3)

The CPU is a highly interiorised existent device/structure in the world. The interior is unknown - interface is presented both by way of assigned pins (labelled by numbers/assignments and control, I/O or time driven functions) and the literature on construct of the data sheet which presents this annotation - to some degree often incorporating purely theoretical rather than practical information. The product unknown to the manufacturer returns conjecture. There is a relation to measurement and exploration by way of reverse engineering.

[CPU image. the black box. data sheet Zilog Z80. machinery of reverse engineering]

To extrapolate from such a (fictional) view of the CPU (in the world) towards the world/existent (and thus the arena of life coding: the darkened theatre and its double) implies an interiority which is rationality (a machine) with pin-outs extending deep into the black forest of an outside. It's a necessary exchange - expansion of CPU/machine interiority implies a sadistic or cruel rationality (contained) of the machinic. The CPU is (always) a rabbit hole within this forest which accommodates another extrapolated CPU - Edison's Black Maria. A film studio with a constrained or reduced instruction set which well allows for viral reproduction and thus execution. This studio, in the forest, precisely mimes interiority. The encoding of the instruction set permutation, the program, which equally implies circular motion by way of both vertical sprocket-led motion (reproduction) and a horizontal rotation of the studio itself repeating the world's motion in attempting to track the light of the sun, a telescope's motion; this encoding is equally used within the first hardwired CPU of Konrad Zuse - a hardwired arithmetic unit implying circuit selection parallels the permutational (editing) possibilities of that life coding demonstrative double which is cinema.

ref also:

http://irb.cs.tu-berlin.de/~zuse/Konrad_Zuse/Neumann_vs_Zuse.html

John von Neumann's Computer Concepts versus Konrad Zuse's Ideas and the Machines Z1 and Z3

[Klossowski image/Salo bibliography-ending wrapped in as image and text. Black Maria interior shot. shot. Edison text p. 20+ Dickson's history transcribed below]

Extrapolating further on this tracking (out) trajectory from CPU to Black Maria studio (a mobile police cell) to world/existent and maintaining a relation to containment (prison of language and rationalism), leads both to a permutational filmic construct arrived at when film, like all software, turns in on itself, eats its own promiscuous tail, in compiling or interpreting harmless, passive data as world-active code - an everyday operation which allows for an interface between high level expressive language (comments are nevertheless discarded) and the machinic: machine code exactly as it is termed.

[?. an interpreter in hardware - Lisp transcription]

This film: Rainer Werner Fassbinder's Welt am Draht. Thus a series of ever expanding containers, Searle's Chinese room embeddings. leading both to the Kopf embeddings within Fassbinder's two part magnum opus, and equally to the question of interface. The clue that such a world reverse engineering, this mock turtle science, is on the right paranoiac or conspiratorial track revealed through further empirical evidence or coincidence. Fassbinder's Welt Am Draht (describe) is based on a novel, Simulacron-3, by Daniel F. Galouye in 1964, which is well referenced at the beginning of Otto Roessler's first manifesto for a new kind of science: Endophysics (1992) , or precisely science or physics from WITHIN. Equally the question of a "world as interface" - a thought movement made possible by the use of computers and the descriptive active means of programming languages to model the wonderland world: embedding a world for an equally embeddable observer (the Kopf). A science born of a science fiction which further following the conspiratorial track is further related (in 1970) by Konrad Zuse in his essay Rechnende Raum, or Calculating space/room. The circuit is complete but the question remains of observer interiority - access to a falsified data sheet for a cruel world or rabbit hole CPU. [expand on Endophysics and the observer]

[Welt am Draht images. Tower of Babel and Breugel CPU]

Brief post-xxxxx_at_piksel notes: 13:19 (2006.10.19:2 xxxxx_at_piksel_notes#48 interface_and_society_notes#2 research#97)

1] Slide 0: All hardware is necessarily closed, black boxed - another exposure (potentially falsified) by way of the data sheet enumerating instruction set, pin outs and exposed physical characteristics. A potential for reverse engineering of CPU, black box, brain or world (that process outlined).

2] From day one:

a) Reversibility, Augustine, Poincare', Friedkin

b) Tragedy and arithmetic.

c) Rationalism and the container/frame (an interiority: incompleteness, inside - first person). By way of endophysics (inside) an investigation of computer science and interiority: that computational technologies (hardware and software) enable a new thinking of the interior (enabling the science of endophysics). Thus:

(computer) hardware as a theatre of interiority along the hard/soft line of execution

d) Economies: a white rabbit economy within the CPU (for Oslo also below). The transfromation from notebook to white rabbit as computationally too expensive in terms of complexity and thus entropy. Equally an entropic world economy as outlined within Kekule'/Pynchon quote.

refs: Anaxagoras fragments, Leibniz-Clarke correspondence

e) xxxxx defined now as the active construction of a non-subject space (paradise) through noise

3] Towards Oslo: specification of a CPU:

a) Edison black maria(h) exterior CPU model. (The instruction set is cinema). Interior stills (Salo stills, exposure). Model and flattened studio. Revolving studio platform and sun opening (a hole).

b) JDM. John Dee Machines - monadic CPU, autumnal CPU (rabbit holes moss and web covered, forest, mushrooms).

sleep CPU instruction (kill cell). time machine and Alice functions. autumnal pinouts (I/O leaf indication), contained experience and sample lige coding manual for machinery...

sources:

Pieter Breugel the Elder: Tower of Babel, Allegory of Autumn (the younger?), Flemish Proverbs

For reference: 12:12 (2006.10.19:1 fpga#20 tech_notes#294 interface_and_society_notes#1)

XSTEND and own FPGA expansion board pin details:

own interface:

8 IN 8 OUT (IN into voltage divider and both by way of 74hc245 transceiver

TOP (4 pin VGA interface)

1: GND

2: 5V

3: VSYNC

4: HSYNC

FPGA XSTEND: ref to FPGA pins (xsa-200/xsa-3s1000):

VERTICAL LINE FROM TOP:

0-7: IN

0: A5/F15

1: F14/P12

2: P9/J1

3: R9/H1

4: T9/H3

5: T7/G2

6: B9/K15

7: A9/K16

0-7: OUT

0: M7/E2

1: R6/E1

2: N7/F3

3: P7/F2

4: R7/G4

5: T14/G3

6: P8/G1

7: T8/H4

(both above as bi-directional I/O ports - extra 16 IN should be available)

0-7: MISC

1: GND

2: 5V

3: VSYNC

4: HYSNC