From: Oliver Schmidt Date: Tue, 4 Feb 2014 21:51:39 +0000 (+0100) Subject: Updated linuxdoc sources from https://github.com/groessler/cc65/tree/gh-pages-sgml. X-Git-Tag: V2.15~181 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=c3d93d259b65c51ed5ac8e6cd58327af908c9501;p=cc65 Updated linuxdoc sources from https://github.com/groessler/cc65/tree/gh-pages-sgml. --- diff --git a/doc/apple2.sgml b/doc/apple2.sgml index fb6dda7fe..ecab5c32b 100644 --- a/doc/apple2.sgml +++ b/doc/apple2.sgml @@ -87,13 +87,13 @@ on the chosen . Linker configurations

-The ld65 linker comes with a builtin config file for the Apple ][, -which is used via builtin config file

+default config file ( Default configuration optimized for a binary program running on ProDOS 8 with BASIC.SYSTEM. A plain vanilla ProDOS 8 doesn't actually use the Language Card @@ -317,13 +317,13 @@ The names in the parentheses denote the symbols to be used for static linking of - + This driver features a resolution of 40×48 with 16 colors. The function + This driver features a resolution of 280×192 with 8 colors and two hires pages. Note that programs using this driver will have to be linked with - + Gives access to 47.5 KB RAM (190 pages of 256 bytes each) on an Extended 80-Column Text Card. @@ -359,7 +359,7 @@ The names in the parentheses denote the symbols to be used for static linking of - + Supports up to two standard analog joysticks connected to the game port of the Apple ][. @@ -370,7 +370,7 @@ The names in the parentheses denote the symbols to be used for static linking of - + Driver for the AppleMouse II Card. Searches all Apple II slots for an AppleMouse II Card compatible firmware. The default bounding box is [0..279,0..191]. @@ -391,7 +391,7 @@ The names in the parentheses denote the symbols to be used for static linking of - + Driver for the Apple II Super Serial Card. Supports up to 19200 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip transmits are not @@ -421,9 +421,8 @@ BASIC.SYSTEM) there are some limitations for DOS 3.3: Disk File I/O There's no disk file I/O support. Any attempt to use it yields an error with , - and - have no effect. + The Apple ][ has no color text mode. Therefore the functions textcolor(), + bgcolor() and bordercolor() have no effect. has no effect. + The Apple ][ has no hardware cursor. Therefore the function cursor() has + no effect.

@@ -511,15 +508,6 @@ url="ca65.html" name="assembler manual">. -Bugs/Feedback

- -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - License

This software is provided 'as-is', without any expressed or implied diff --git a/doc/apple2enh.sgml b/doc/apple2enh.sgml index 667ae9ec7..f20c187fd 100644 --- a/doc/apple2enh.sgml +++ b/doc/apple2enh.sgml @@ -87,13 +87,13 @@ on the chosen . Linker configurations

-The ld65 linker comes with a builtin config file for the enhanced Apple //e, -which is used via builtin config file

+default config file ( Default configuration optimized for a binary program running on ProDOS 8 with BASIC.SYSTEM. A plain vanilla ProDOS 8 doesn't actually use the Language Card @@ -320,13 +320,13 @@ The names in the parentheses denote the symbols to be used for static linking of - + This driver features a resolution of 40×48 with 16 colors. The function + This driver features a resolution of 280×192 with 8 colors and two hires pages. Note that programs using this driver will have to be linked with - + Gives access to 47.5 KB RAM (190 pages of 256 bytes each) on an Extended 80-Column Text Card. @@ -366,7 +366,7 @@ The names in the parentheses denote the symbols to be used for static linking of - + Supports up to two standard analog joysticks connected to the game port of the enhanced Apple //e. @@ -377,7 +377,7 @@ The names in the parentheses denote the symbols to be used for static linking of - + Driver for the AppleMouse II Card. Searches all Apple II slots for an AppleMouse II Card compatible firmware. The default bounding box is [0..279,0..191]. @@ -392,7 +392,7 @@ The names in the parentheses denote the symbols to be used for static linking of - + Driver for the Apple II Super Serial Card. Supports up to 19200 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip transmits are not @@ -422,9 +422,8 @@ BASIC.SYSTEM) there are some limitations for DOS 3.3: Disk File I/O There's no disk file I/O support. Any attempt to use it yields an error with , - and - have no effect. + textcolor(), bgcolor() and bordercolor() have no effect. has no effect. + cursor() has no effect.

@@ -517,15 +514,6 @@ url="ca65.html" name="assembler manual">. -Bugs/Feedback

- -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - License

This software is provided 'as-is', without any expressed or implied diff --git a/doc/ar65.sgml b/doc/ar65.sgml index d4e19a5c5..d35bc9987 100644 --- a/doc/ar65.sgml +++ b/doc/ar65.sgml @@ -117,14 +117,6 @@ operation does update the library. This is only a warning, the linker will ignore one of the duplicate symbols (which one is unspecified). -Bugs/Feedback

- -If you have problems using the archiver, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - Copyright

ar65 (and all cc65 binutils) are (C) Copyright 1998-2000 Ullrich von diff --git a/doc/atari.sgml b/doc/atari.sgml index 9fe75ec2a..8ec359654 100644 --- a/doc/atari.sgml +++ b/doc/atari.sgml @@ -26,6 +26,16 @@ with the cc65 C compiler. It describes the memory layout, Atari specific header files, available drivers, and any pitfalls specific to that platform. +The Atari runtime support comes in two flavors: , it is +recommended to use the . Even functions marked as "platform dependent" may be available on @@ -35,35 +45,54 @@ information. Binary format

-The standard binary output format generated by the linker for the +The Atari DOS executable file format supports more than one load block (. For the discussion here it's +sufficient to know that the first load chunk(s) do preparation work and the +main part of the program is in the last load chunk. + +The values determining the size of the main part of the program (the only load +chunk for ). -You can override this behaviour by creating your own crt0.s file and -linking it into your program. A run vector is added to the end of the -file ($02E0 <run vector>) and is calculated using -__STARTUP_LOAD__ in crt0.s. Memory layout

-The default linker script assumes that the BASIC ROM is disabled (or -the BASIC cartridge unplugged). This gives a usable memory range from -$2E00 - $BC1F. The library startup code examines the + + +The default linker config file assumes that the BASIC ROM is disabled (or +the BASIC cartridge unplugged). This gives a usable memory range of +[$2000-$BC1F]. The library startup code examines the current memory configuration, which depends on the size of the -installed memory and cartridges present, by inspecting the value in -the MEMTOP ($2E5) variable. Then the initial stack pointer, -which indicates the upper bound of memory used, is adjusted. The -default load address of $2E00 was chosen to accommodate having -a DOS loaded and a driver that resides in low memory such as the 850 -R: handler. You can override this behaviour by creating a custom +installed memory and cartridges. It does so by using the value in +the MEMTOP ($2E5) variable as highest memory address the program +can use. The initial stack pointer, which is the upper bound of +memory used by the program, is set to this value, minus an optionally +defined __RESERVED_MEMORY__ value. + +The default load address of $2000 can be changed by creating a custom linker config file or by using the "--start-addr" cl65 command line argument or the "--start-addr" or "-S" ld65 command line arguments. +Please note that the first load chunk (which checks the available memory) +will always be loaded at $2E00, regardless of the specified start +address. This address can only be changed by a custom linker config file. + Special locations: @@ -86,6 +115,135 @@ Special locations:

+ + +The startup code rearranges the memory as follows: + + +Sceen memory and display list are moved below the program start address. +The ROM is disabled, making the memory in the areas [$C000-$CFFF] +and [$D800-$FFF9] available. +Character generator data is copied from ROM to the CHARGEN location specified in the +linker config file. This is (in the default ). With the character generator at $E000, there are two upper memory +areas available, [$D800-$DFFF] and [$E400-$FFF9]. + + +With the default load address of $2400 this gives a usable memory range of +[$2400-$CFFF]. Note that the default load address for . + + +Special locations: + + +

+ +Linker configurations

+ +The ld65 linker comes with default config files for the Atari. There +are two targets for the Atari, + +default config file ( + +The default configuration is tailored to C programs. It creates files +which have a default load address of $2000. + +The files generated by this config file include the + load chunk. It can +optionally be left out, see . + + + +This config file aims to give the assembler programmer maximum +flexibility. All program segments ( + +This config file can be used to create 8K or 16K cartridges. It's suited both +for C and assembly language programs. + +By default, an 8K cartridge is generated. To create a 16K cartridge, pass the +size of the cartridge to the linker, like " + +default config file ( + +The default configuration is tailored to C programs. It creates files +which have a default load address of $2400. + +The files generated by this config file include the + load chunk. It can +optionally be left out, see . + + + +This is the same as the default config file, but it rearranges the +high memory beneath the ROM into one large block. In order for this +config file to work, the runtime library has to be recompiled with a +special define. See the file load chunk. It can +optionally be left out, see . Platform specific header files

@@ -157,48 +315,43 @@ The names in the parentheses denote the symbols to be used for static linking of Graphics drivers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + +
-

Many graphics modes require more memory than the text screen which is in effect when the program starts up. Therefore the programmer has to tell the program beforehand the memory requirements of the graphics modes the program intends to use. -This can be done by using the __RESERVED_MEMORY__ linker config -variable. The number specified there describes the number of bytes to -subtract from the top of available memory as seen from the runtime -library. This memory is then used by the screen buffer. + +On the . The numbers for the different graphics modes presented below should only be seen as a rule of thumb. Since the screen buffer memory needs @@ -251,41 +404,74 @@ the Atari ROM code. Extended memory drivers

- - - - -

+Currently there is only one extended memory driver. It manages the second 64K of a 130XE. + + + + +
Joystick drivers

- +Currently there are two joystick drivers available: - - Supports up to four standard joysticks connected to the joystick ports of - the Atari. + + + + +
+
- - Supports up to eight standard joysticks connected to a MultiJoy adapter. -

+Mouse drivers

+Currently there are five mouse drivers available: -Mouse drivers

+ + + + +
+
-Currently no drivers available (in fact, the API for loadable mouse drivers -does not exist). There is a static driver you can use. +All mouse devices connect to joystick port #0. RS232 device drivers

-Currently there are no RS232 loadable drivers available for the Atari -platform. There is a static driver you can use. +Currently there is one RS232 driver. It uses the R: device (therefore +a R: driver needs to be installed) and was tested with the 850 +interface module. + + + + + +
Limitations

+ + + +The display is cleared at program start and at program termination. This is a side +effect of relocating the display memory below the program start address. +Not all possible CIO and SIO functions are handled by the runtime stub code which banks +the ROM in and out. All functions used by the runtime library are handled, though. +The It is not compatible with DOSes or other programs using the memory below the ROM. + DIO implementation

@@ -303,6 +489,143 @@ The console I/O is speed optimized therefore support for XEP80 hardware or f80.com software is missing. Of course you may use stdio.h functions. +Technical details

+ + + +Load chunks

+ +An +"system check"

+ +The Load chunks

+ +An +"system check"

+ +When setting a graphics mode, the ROM looks at the RAMTOP location. RAMTOP +describes the amount of installed memory in pages (RAMTOP is only one byte). +The screen memory and display list are placed immediately below RAMTOP. + +Now in order to relocate the screen memory to lower memory, the startup code +puts a value into RAMTOP which causes the ROM routines to allocate the display +memory below the program start address and then it issues a ROM call to setup +the regular text mode. + +Selecting a good program load address

+ +Due to the movement of the screen memory below the program start, there are some +load addresses which are sub-optimal because they waste memory or prevent a +higher resolution graphics mode from being enabled. + +There are restrictions at which addresses screen memory (display buffer and display +list) can be placed. The display buffer cannot cross a 4K boundary and a display +list cannot cross a 1K boundary. + +The startup code takes this into account when moving the screen memory down. +If the program start address (aligned to the next lower page boundary) minus +the screen buffer size would result in a screen buffer which spans a 4K +boundary, the startup code lowers RAMTOP to this 4K boundary.&nl; +The size of the screen buffer in text mode is 960 ($3C0) bytes. So, for +example, a selected start address of $2300 would span the 4K boundary +at $2000. The startup code would adjust the RAMTOP value in such way that +the screen memory would be located just below this boundary (at $1C40). +This results in the area [$2000-$22FF] being wasted. +Additionally, the program might fail to load since the lowest address used +by the screen memory could be below MEMLO. (The lowest address used in this +example would be at $1C20, where the display list would allocated.) + +These calculations are performed by the startup code (in the first two +load chunks), but the startup code only takes the default 40x24 text mode +into account. If the program later wants to load TGI drivers which set +a more memory consuming graphics mode, the user has to pick a higher +load address. +Using higher resolution modes there is a restriction in the ROM that it +doesn't expect RAMTOP to be at arbitrary values. The Atari memory modules +came only in 8K or 16K sizes, so the ROM expects RAMTOP to only have +values in 8K steps. Therefore, when using the highest resolution modes +the program start address must be at an 8K boundary. + + +Character generator location

+ +The default Other hints

@@ -335,6 +658,9 @@ feature in the . Reserving a memory area inside a program

+(This section is primarily applicable to the Each load chunk of the executable starts with a 4 byte header which -defines its load address and size. In the following linker scripts +defines its load address and size. In the following linker config files these headers are named HEADER and SECHDR (for the MEMORY layout), and accordingly NEXEHDR and CHKHDR (for the SEGMENTS layout).

@@ -360,30 +686,34 @@ segments should go above $7FFF.

The main problem is that the EXE header generated by the cc65 runtime lib is wrong. It defines a single load chunk with the sizes/addresses -of the STARTUP, LOWCODE, INIT, CODE, RODATA, and DATA segments (the whole user -program). +of the STARTUP, LOWCODE, INIT, CODE, RODATA, and DATA segments, in +fact, the whole user program (we're disregarding the "system check" +load chunk here).

-The contents of the EXE header come from the EXEHDR segment, which is -defined in crt0.s. This cannot be changed without modifying and -recompiling the cc65 atari runtime lib. Therefore the original EXE -header must be discarded. It will be replaced by a user created -one. The discarding is done by assigning the EXEHDR segment to the -BANK memory area. The BANK memory area is discarded in the new linker -script (written to file ""). +The contents of the EXE header come from the EXEHDR and MAINHDR segments. +The EXEHDR segment just contains the $FFFF value which is required +to be the first bytes of the EXE file.&nl; +The MAINHDR are defined in in crt0.s. This cannot be changed without +modifying and recompiling the cc65 atari runtime library. Therefore +the original contents of this segment must be discarded and be +replaced by a user created one. This discarding is done by assigning the +MAINHDR segment to the (new introduced) DISCARD memory area. The DISCARD memory area is +thrown away in the new linker config file (written to file ""). +We add a new FSTHDR segment for the chunk header of the first chunk.

The user needs to create a customized linker config file which adds -new memory areas and segments to hold the new EXE header and the -header data for the second load chunk. Also an assembly source file -needs to be created which defines the contents of the new EXE header -and the second load chunk header. +new memory areas and segments to hold the new header data for the first load +chunk and the header data for the second load chunk. Also an assembly source file +needs to be created which defines the contents of the new header data +for the two load chunks.

This is an example of a modified cc65 Atari linker configuration file (split.cfg): SYMBOLS { - __STACKSIZE__ = $800; # 2K stack - __RESERVED_MEMORY__: value = $0000, weak = yes; + __STACKSIZE__: value = $800 type = weak; # 2K stack + __RESERVED_MEMORY__: value = $0000, type = weak; } FEATURES { STARTADDRESS: default = $2E00; @@ -391,18 +721,22 @@ FEATURES { MEMORY { ZP: start = $82, size = $7E, type = rw, define = yes; - HEADER: start = $0000, size = $6, file = %O; # first load chunk + HEADER: start = $0000, size = $2, file = %O; # first load chunk + + FSTHDR: start = $0000, size = $4, file = %O; # second load chunk RAMLO: start = %S, size = $4000 - %S, file = %O; - BANK: start = $4000, size = $4000, file = ""; + DISCARD: start = $4000, size = $4000, file = ""; SECHDR: start = $0000, size = $4, file = %O; # second load chunk RAM: start = $8000, size = $3C20, file = %O; # $3C20: matches upper bound $BC1F } SEGMENTS { - EXEHDR: load = BANK, type = ro; + EXEHDR: load = HEADER, type = ro; - NEXEHDR: load = HEADER, type = ro; # first load chunk + MAINHDR: load = DISCARD, type = ro; + + NEXEHDR: load = FSTHDR, type = ro; # first load chunk STARTUP: load = RAMLO, type = ro, define = yes; LOWCODE: load = RAMLO, type = ro, define = yes, optional = yes; INIT: load = RAMLO, type = ro, optional = yes; @@ -412,7 +746,6 @@ SEGMENTS { RODATA: load = RAM, type = ro, define = yes; DATA: load = RAM, type = rw, define = yes; BSS: load = RAM, type = bss, define = yes; - ZPSAVE: load = RAM, type = bss, define = yes; ZEROPAGE: load = ZP, type = zp; AUTOSTRT: load = RAM, type = ro; # defines program entry point @@ -430,12 +763,13 @@ FEATURES {

-A new memory area BANK was added which describes the reserved area. -It gets loaded with the contents of the old EXEHDR segment. But the +A new memory area DISCARD was added. +It gets loaded with the contents of the (now unused) MAINHDR segment. But the memory area isn't written to the output file. This way the contents of -the EXEHDR segment get discarded. +the MAINHDR segment get discarded.

-The newly added NEXEHDR segment defines the correct EXE header. It +The newly added NEXEHDR segment defines the correct chunk header for the +first intended load chunk. It puts the STARTUP, LOWCODE, INIT, and CODE segments, which are the segments containing only code, into load chunk #1 (RAMLO memory area).

@@ -451,7 +785,6 @@ file (split.s): .import __DATA_LOAD__, __RODATA_LOAD__, __STARTUP_LOAD__ .segment "NEXEHDR" - .word $FFFF .word __STARTUP_LOAD__ .word __CODE_LOAD__ + __CODE_SIZE__ - 1 @@ -473,8 +806,8 @@ CODE, BSS, ZPSAVE into high memory (split2.cfg): SYMBOLS { - __STACKSIZE__ = $800; # 2K stack - __RESERVED_MEMORY__: value = $0000, weak = yes; + __STACKSIZE__: value = $800 type = weak; # 2K stack + __RESERVED_MEMORY__: value = $0000, type = weak; } FEATURES { STARTADDRESS: default = $2E00; @@ -482,18 +815,22 @@ FEATURES { MEMORY { ZP: start = $82, size = $7E, type = rw, define = yes; - HEADER: start = $0000, size = $6, file = %O; # first load chunk + HEADER: start = $0000, size = $2, file = %O; # first load chunk + + FSTHDR: start = $0000, size = $4, file = %O; # second load chunk RAMLO: start = %S, size = $4000 - %S, file = %O; - BANK: start = $4000, size = $4000, file = ""; + DISCARD: start = $4000, size = $4000, file = ""; SECHDR: start = $0000, size = $4, file = %O; # second load chunk RAM: start = $8000, size = $3C20, file = %O; # $3C20: matches upper bound $BC1F } SEGMENTS { - EXEHDR: load = BANK, type = ro; # discarded old EXE header + EXEHDR: load = HEADER, type = ro; # discarded old EXE header - NEXEHDR: load = HEADER, type = ro; # first load chunk + MAINHDR: load = DISCARD, type = ro; + + NEXEHDR: load = FSTHDR, type = ro; # first load chunk RODATA: load = RAMLO, type = ro, define = yes; DATA: load = RAMLO, type = rw, define = yes; @@ -501,7 +838,6 @@ SEGMENTS { STARTUP: load = RAM, type = ro, define = yes; INIT: load = RAM, type = ro, optional = yes; CODE: load = RAM, type = ro, define = yes; - ZPSAVE: load = RAM, type = bss, define = yes; BSS: load = RAM, type = bss, define = yes; ZEROPAGE: load = ZP, type = zp; @@ -521,17 +857,16 @@ FEATURES { New contents for NEXEHDR and CHKHDR are needed (split2.s): - .import __STARTUP_LOAD__, __ZPSAVE_LOAD__, __DATA_SIZE__ + .import __STARTUP_LOAD__, __BSS_LOAD__, __DATA_SIZE__ .import __DATA_LOAD__, __RODATA_LOAD__ .segment "NEXEHDR" - .word $FFFF .word __RODATA_LOAD__ .word __DATA_LOAD__ + __DATA_SIZE__ - 1 .segment "CHKHDR" .word __STARTUP_LOAD__ - .word __ZPSAVE_LOAD__ - 1 + .word __BSS_LOAD__ - 1 Compile with @@ -542,7 +877,7 @@ cl65 -t atari -C split2.cfg -o prog.com prog.c split2.s Final note

There are two other memory areas which don't appear directly in the -linker script. They are the stack and the heap. +linker config file. They are the stack and the heap. The cc65 runtime lib places the stack location at the end of available memory. This is dynamically set from the MEMTOP system variable at @@ -556,14 +891,47 @@ common/_heap.s defines the location of the heap and atari/crt0.s defines the location of the stack by initializing sp. -Bugs/Feedback

+Upgrading from an older cc65 version

+ +If you are using a customized linker config file you might get some errors +regarding the MAINHDR segment. Like this: -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email ( or ). + +ld65: Error: Missing memory area assignment for segment `MAINHDR' + + +The old "HEADER" memory description contained six bytes: $FFFF +and the first and last memory addess of the program. For the "system +check" load chunk this had to be split into two memory assigments. The +"HEADER" now only contains the $FFFF. The main program's first +and last memory address were moved to a new segment, called "MAINHDR", +which in the new linker config file goes into its own memory area (also +called "MAINHDR").&nl;&nl; +A simple way to adapt your old linker config file is to add the +following line to the "SEGMENTS" section: + + +MAINHDR: load = HEADER, type = ro; + + + + +Getting rid of the "system check" load chunk

+ +If, for some reason, you don't want to include the "system check" load +chunk, you can do so by defining the symbol +cl65 -Wl -D__SYSTEM_CHECK__=1 + +The value you assign to License

diff --git a/doc/atmos.sgml b/doc/atmos.sgml index 8e24c92a1..82aef6c31 100644 --- a/doc/atmos.sgml +++ b/doc/atmos.sgml @@ -112,14 +112,14 @@ The names in the parentheses denote the symbols to be used for static linking of - + This driver was written by Greg King and Stefan Haubenthal. It features a resolution of 228×200 with a palette of two colors that can be chosen from the Atmos's eight colors. The driver supports a third palette-"color" that actually "flips" the pixel (it becomes the other color) that is on the screen under the graphics cursor. - + This driver was written by Stefan Haubenthal and Greg King. It features a resolution of 240×200 with black and white colors. It is the default graphics driver for the Atmos. @@ -136,7 +136,7 @@ No extended memory drivers are currently available for the Atmos. - + Supports two standard joysticks connected to the P.A.S.E. interface of the Atmos.

@@ -151,7 +151,7 @@ No mouse drivers are currently available for the Atmos. - + Driver for the Telestrat integrated serial controller and the Atmos with a serial add-on. Note that because of the peculiarities of the 6551 chip together with the @@ -224,15 +224,6 @@ feature in the . -Bugs/Feedback

- -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - License

This software is provided 'as-is', without any expressed or implied diff --git a/doc/c128.sgml b/doc/c128.sgml index 37cdd25f8..5ea44b970 100644 --- a/doc/c128.sgml +++ b/doc/c128.sgml @@ -168,13 +168,13 @@ Note: The graphics drivers for the VDC are incompatible with the extended memory drivers using the VDC memory! - + This driver was written by Maciej Witkowiak. It uses the 80 column display and features a resolution of 640*200 with two colors and an adjustable palette (that means that the two colors can be chosen out of the 16 VDC colors). - + This driver was written by Maciej Witkowiak. This driver uses the 80 column display and features a resolution of 640*480 with two colors and an adjustable palette (that means that the two colors can be chosen out of the @@ -189,17 +189,16 @@ missing on VDC and are translated to the two colors missing from VIC palette. - + A driver for the GeoRam cartridge. The driver will always assume 2048 pages of 256 bytes each. There are no checks, so if your program knows better, just go ahead. - + An extended memory driver for the RAM in page 1. The common memory area is excluded, so this driver supports 251 pages of 256 bytes each. - - + An extended memory driver for the RAM in pages 1-3. The common memory area is excluded, so this driver supports up to 731 pages of 256 bytes each. The driver can be used as a full replacement for + A driver for the RamCart 64/128 written and contributed by Maciej Witkowiak. Will test the hardware for the available RAM. - + A driver for the CBM REUs. The driver will determine from the connected REU if it supports 128KB of RAM or more. In the latter case, 256KB are assumed, but since there are no range checks, the application can use more memory if it has better knowledge about the hardware than the driver. - + A driver for the VDC memory of the C128 written and contributed by Maciej Witkowiak. Autodetects the amount of memory available (16 or 64K) and offers 64 or 256 pages of 256 bytes each. Note: This driver is incompatible with @@ -230,14 +229,14 @@ missing on VDC and are translated to the two colors missing from VIC palette. - + Driver for the Protovision 4-player adapter originally written by Groepaz for the C64 and converted for the C128 by me. See for prices and building instructions. Up to four joysticks are supported. - + Supports up to two joysticks connected to the standard joysticks port of the C128. @@ -249,14 +248,21 @@ missing on VDC and are translated to the two colors missing from VIC palette. - + Supports a standard mouse connected to port #0 of the C128. - + + Supports the Inkwell Systems lightpens, connected to port #0 of the + C128. It can read both the one-button 170-C and the two-button 184-C pens. + (It can read other lightpens and light-guns that send their button signal to + the joystick left-button pin or the paddle Y [up/down] pin.) It works on + only the 40-column screen. + + Supports a mouse emulated by a standard joystick e.g. 1350 mouse in port #1 of the C128. - + Supports a potentiometer device e.g. Koala Pad connected to port #1 of the C128. @@ -267,7 +273,7 @@ missing on VDC and are translated to the two colors missing from VIC palette. - + Driver for the SwiftLink cartridge. Supports up to 38400 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip together with the use of the NMI, transmits @@ -323,15 +329,6 @@ feature in the . -Bugs/Feedback

- -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - License

This software is provided 'as-is', without any expressed or implied diff --git a/doc/c16.sgml b/doc/c16.sgml index 110082a19..5d4a5d372 100644 --- a/doc/c16.sgml +++ b/doc/c16.sgml @@ -160,7 +160,7 @@ No graphics drivers are currently available for the C16/C116. - + A driver for the hidden RAM below the BASIC and KERNAL ROMs. Supports 125 pages with 256 bytes each if the machine is equipped with 64K of memory (a Plus/4 or a memory extended C16/116). @@ -173,7 +173,7 @@ No graphics drivers are currently available for the C16/C116. - + Supports up to two joysticks connected to the standard joysticks port of the Commodore 16/116. @@ -183,8 +183,7 @@ No graphics drivers are currently available for the C16/C116. Mouse drivers

-Currently no drivers available (in fact, the API for loadable mouse drivers -does not exist). +No mouse drivers are currently available for the C16/C116. RS232 device drivers

@@ -237,15 +236,6 @@ feature in the . -Bugs/Feedback

- -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - License

This software is provided 'as-is', without any expressed or implied diff --git a/doc/c64.sgml b/doc/c64.sgml index 2e6a37e77..a5014414c 100644 --- a/doc/c64.sgml +++ b/doc/c64.sgml @@ -65,15 +65,15 @@ Special locations: Linker configurations

-The ld65 linker comes with a builtin config file for the Commodore 64, -which is used via builtin config file

+default config file ( -The builtin configuration is tailored to C programs. It supplies the load +The default configuration is tailored to C programs. It supplies the load address and a small BASIC stub that starts the compiled program using a SYS command. @@ -210,7 +210,7 @@ the standard setup without any memory loss or need for a changed configuration. - + This driver features a resolution of 320*200 with two colors and an adjustable palette (that means that the two colors can be chosen out of a palette of the 16 C64 colors). @@ -221,45 +221,45 @@ configuration. - + A driver for the C64 256K memory expansion. This driver offers 768 pages of 256 bytes each. Written and contributed by Marco van den Heuvel. - + A driver for the Double Quick Brown Box cartridge. This driver offers 64 pages of 256 bytes each. Written and contributed by Marco van den Heuvel. - + A driver for the Berkeley Softworks GeoRam cartridge. The driver will determine the available RAM from the connected cartridge. It supports 64KB up to 2048KB of RAM. - + A driver for the ISEPIC cartridge. This driver offers just 8 pages of 256 bytes each. Written and contributed by Marco van den Heuvel. - + A driver for the hidden RAM below the I/O area and kernal ROM. Supports 48 256 byte pages. Please note that this driver is incompatible with any of the graphics drivers! - + A driver for the RamCart 64/128 written and contributed by Maciej Witkowiak. Will test the hardware for the available RAM. - + A driver for the CBM REUs. The driver will determine from the connected REU if it supports 128KB of RAM or more. In the latter case, 256KB are assumed, but since there are no range checks, the application can use more memory if it has better knowledge about the hardware than the driver. - + A driver for the VDC memory of the C128. Written and contributed by Maciej Witkowiak. Can be used if the program is running in C64 mode of the C128. Autodetects the amount of memory available (16 or 64K) and offers 64 or 256 pages of 256 bytes each. - + A driver for the C64 D2TV (the second or PAL version). This driver offers indeed 7680 pages of 256 bytes each. @@ -270,23 +270,23 @@ configuration. - + Driver for the Digital Excess & Hitmen adapter contributed by Groepaz. See on instructions how to build one. Up to four joysticks are supported. - + Driver for the Protovision 4-player adapter contributed by Groepaz. See for prices and building instructions. Up to four joysticks are supported. - + Supports up to two standard joysticks connected to the joysticks port of the C64. - + Supports one joystick emulated by the numberpad of the C128 in C64 mode, the firebutton is labeled &dquot;5&dquot; and ENTER. @@ -297,14 +297,20 @@ configuration. - + Supports a standard mouse connected to port #0 of the C64. - + + Supports the Inkwell Systems lightpens, connected to port #0 of the C64. + It can read both the one-button 170-C and the two-button 184-C pens. (It can + read other lightpens and light-guns that send their button signal to the + joystick left-button pin or the paddle Y [up/down] pin.) + + Supports a mouse emulated by a standard joystick e.g. 1350 mouse in port #1 of the C64. - + Supports a potentiometer device e.g. Koala Pad connected to port #1 of the C64. @@ -315,7 +321,7 @@ configuration. - + Driver for the SwiftLink cartridge. Supports up to 38400 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip together with the use of the NMI, transmits @@ -372,15 +378,6 @@ feature in the . -Bugs/Feedback

- -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (). - - - License

This software is provided 'as-is', without any expressed or implied diff --git a/doc/ca65.sgml b/doc/ca65.sgml index 00d72db56..c1c314a2c 100644 --- a/doc/ca65.sgml +++ b/doc/ca65.sgml @@ -112,14 +112,12 @@ Long options: --debug Debug mode --debug-info Add debug info to object file --feature name Set an emulation feature - --forget-inc-paths Forget include search paths --help Help (this text) --ignore-case Ignore case of symbols --include-dir dir Set an include directory search path --large-alignment Don't warn about large alignments --listing name Create a listing file if assembly was ok --list-bytes n Maximum number of bytes per listing line - --macpack-dir dir Set a macro package directory --memory-model model Set the memory model --pagelength n Set the page length for the listing --relax-checks Relax some checks (see docs) @@ -195,14 +193,6 @@ Here is a description of all the command line options: command for a list of emulation features. -

- -If you have problems using the assembler, if you find any bugs, or if -you're doing something interesting with the assembler, I would be glad to -hear from you. Feel free to contact me by email -(). - - - Copyright

ca65 (and all cc65 binutils) are (C) Copyright 1998-2003 Ullrich von diff --git a/doc/ca65html.sgml b/doc/ca65html.sgml index 8b26be44c..68dd2507f 100644 --- a/doc/ca65html.sgml +++ b/doc/ca65html.sgml @@ -248,15 +248,6 @@ that you have to pay for color. -Bugs/Feedback

- -If you have problems using the converter, if you find any bugs, or if you're -doing something interesting with the assembler, I would be glad to hear from -you. Feel free to contact me by email (). - - - Copyright

ca65html is (c) Copyright 2000-2007 Ullrich von Bassewitz. For its use, the diff --git a/doc/cbm510.sgml b/doc/cbm510.sgml index 0dc842bc1..75497d977 100644 --- a/doc/cbm510.sgml +++ b/doc/cbm510.sgml @@ -3,9 +3,10 @@

Commodore 510 (aka P500) specific information for cc65 -<author>Ullrich von Bassewitz, <htmlurl url="mailto:uz@cc65.org" name="uz@cc65.org"> -Stefan A. Haubenthal, <htmlurl url="mailto:polluks@sdf.lonestar.org" name="polluks@sdf.lonestar.org"> -<date>2006-05-22 +<author>Ullrich von Bassewitz, <htmlurl url="mailto:uz@cc65.org" name="uz@cc65.org">&nl; +Stefan A. Haubenthal, <htmlurl url="mailto:polluks@sdf.lonestar.org" name="polluks@sdf.lonestar.org">&nl; +<htmlurl url="mailto:greg.king5@verizon.net" name="Greg King"> +<date>2013-08-23 <abstract> An overview over the Commodore 510 runtime system as it is implemented for the @@ -184,7 +185,7 @@ No graphics drivers are currently available for the Commodore 510. <sect1>Extended memory drivers<p> <descrip> - <tag><tt/cbm510-ram.emd (cbm510_ram)/</tag> + <tag><tt/cbm510-ram.emd (cbm510_ram_emd)/</tag> A driver for the RAM in bank 1. Supports up to 255 pages with 256 bytes each. </descrip><p> @@ -194,7 +195,7 @@ No graphics drivers are currently available for the Commodore 510. <descrip> - <tag><tt/cbm510-std.joy (cbm510_stdjoy)/</tag> + <tag><tt/cbm510-std.joy (cbm510_std_joy)/</tag> Supports up to two standard joysticks connected to the joysticks port of the Commodore 510. @@ -203,14 +204,27 @@ No graphics drivers are currently available for the Commodore 510. <sect1>Mouse drivers<p> -No mouse drivers are currently available for the Commodore 510. +<descrip> + + <tag><tt/cbm510-joy.mou (cbm510_joy_mou)/</tag> + Supports a mouse that is emulated by a standard joystick, e.g. 1350 + mouse, in joystick port #2 of the CBM510. That stick's fire button acts as + the left mouse button. The fire button of a stick in joystick port #1 can + act as the right mouse button. + <tag><tt/cbm510-inkwl.mou (cbm510_inkwl_mou)/</tag> + Supports the Inkwell Systems lightpens, connected to port #1 of the CBM510. + It can read both the 170-C and one button of the 184-C pens. (It can + read other lightpens and light-guns that send their button signal to the + joystick left-button pin.) + +</descrip><p> <sect1>RS232 device drivers<p> <descrip> - <tag><tt/cbm510-std.ser (cbm510_stdser)/</tag> + <tag><tt/cbm510-std.ser (cbm510_std_ser)/</tag> Driver for the 6551 ACIA chip built into the Commodore 510. Supports up to 19200 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip transmits are not @@ -268,15 +282,6 @@ code when they are linked into a program. See the discussion of the -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/cbm610.sgml b/doc/cbm610.sgml index 5acb38a1a..a6ec4650b 100644 --- a/doc/cbm610.sgml +++ b/doc/cbm610.sgml @@ -186,7 +186,7 @@ really good:-). <sect1>Extended memory drivers<p> <descrip> - <tag><tt/cbm610-ram.emd (cbm610_ram)/</tag> + <tag><tt/cbm610-ram.emd (cbm610_ram_emd)/</tag> A driver for the RAM in bank 2. Supports up to 255 pages with 256 bytes each. </descrip><p> @@ -201,15 +201,14 @@ are no drivers for the non existing ports available. <sect1>Mouse drivers<p> -Currently no drivers available (in fact, the API for loadable mouse drivers -does not exist). +No mouse drivers are currently available for the Commodore 610. <sect1>RS232 device drivers<p> <descrip> - <tag><tt/cbm610-std.ser (cbm610_stdser)/</tag> + <tag><tt/cbm610-std.ser (cbm610_std_ser)/</tag> Driver for the 6551 ACIA chip built into the Commodore 610. Supports up to 19200 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip transmits are not @@ -267,15 +266,6 @@ code when they are linked into a program. See the discussion of the -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/cc65.sgml b/doc/cc65.sgml index bb1303909..ab7632718 100644 --- a/doc/cc65.sgml +++ b/doc/cc65.sgml @@ -88,7 +88,6 @@ Long options: --dep-target target Use this dependency target --disable-opt name Disable an optimization step --enable-opt name Enable an optimization step - --forget-inc-paths Forget include search paths --help Help (this text) --include-dir dir Set an include directory search path --list-opt-steps List all optimizer steps and exit @@ -204,13 +203,6 @@ Here is a description of all the command line options: is defined to the value "1". - <tag><tt>--forget-inc-paths</tt></tag> - - Forget the builtin include paths. This is most useful when building - customized C or runtime libraries, in which case the standard header - files should be ignored. - - <tag><tt>-g, --debug-info</tt></tag> This will cause the compiler to insert a <tt/.DEBUGINFO/ command into the @@ -344,6 +336,7 @@ Here is a description of all the command line options: <item>apple2 <item>apple2enh <item>atari + <item>atarixl <item>atmos <item>c16 (works also for the c116 with memory up to 32K) <item>c64 @@ -357,6 +350,8 @@ Here is a description of all the command line options: <item>nes <item>pet (all CBM PET systems except the 2001) <item>plus4 + <item>sim6502 + <item>sim65c02 <item>supervision <item>vic20 </itemize> @@ -514,24 +509,23 @@ Here is a description of all the command line options: The compiler will accept one C file per invocation and create a file with the same base name, but with the extension replaced by ".s". The output -file contains assembler code suitable for the use with the ca65 macro +file contains assembler code suitable for use with the ca65 macro assembler. -Include files in single quotes are searched in the following places: +Include files in quotes are searched in the following places: <enum> -<item>The current directory. -<item>The value of the environment variable <tt/CC65_INC/ if it is defined. +<item>The current file's directory. <item>Any directory added with the <tt/-I/ option on the command line. +<item>The value of the environment variable <tt/CC65_INC/ if it is defined. </enum> Include files in angle brackets are searched in the following places: <enum> -<item>A compiled in directory which is often <tt>/usr/lib/cc65/include</tt> on - Linux systems. +<item>Any directory added with the <tt/-I/ option on the command line. <item>The value of the environment variable <tt/CC65_INC/ if it is defined. <item>A subdirectory named <tt/include/ of the directory defined in the environment variable <tt/CC65_HOME/, if it is defined. -<item>Any directory added with the <tt/-I/ option on the command line. +<item>An optionally compiled-in directory. </enum> @@ -709,7 +703,7 @@ The compiler defines several macros at startup: <descrip> <tag><tt>__APPLE2__</tt></tag> - This macro is defined if the target is the Apple ][ (-t apple2). + This macro is defined if the target is the Apple ][ (-t apple2) or the enhanced Apple //e (-t apple2enh). <tag><tt>__APPLE2ENH__</tt></tag> @@ -717,8 +711,11 @@ The compiler defines several macros at startup: <tag><tt>__ATARI__</tt></tag> - This macro is defined if the target is one of the Atari computers - (400/800/130XL/800XL). + This macro is defined if the target is the Atari 400/800 (-t atari) or the Atari 800XL/130XE (-t atarixl). + + <tag><tt>__ATARIXL__</tt></tag> + + This macro is defined if the target is the Atari 800XL/130XE (-t atarixl). <tag><tt>__ATMOS__</tt></tag> @@ -726,15 +723,15 @@ The compiler defines several macros at startup: <tag><tt>__C128__</tt></tag> - This macro is defined if the target is the c128 (-t c128). + This macro is defined if the target is the Commodore 128 (-t c128). <tag><tt>__C16__</tt></tag> - This macro is defined if the target is the c16 (-t c16). + This macro is defined if the target is the Commodore 16/116 (-t c16) or the Commodore Plus/4 (-t plus4). <tag><tt>__C64__</tt></tag> - This macro is defined if the target is the c64 (-t c64). + This macro is defined if the target is the Commodore 64 (-t c64). <tag><tt>__CBM__</tt></tag> @@ -776,7 +773,15 @@ The compiler defines several macros at startup: <tag><tt>__GEOS__</tt></tag> - This macro is defined if you are compiling for the GEOS system (-t geos). + This macro is defined if you are compiling for one of the GEOS systems. + + <tag><tt>__GEOS_APPLE__</tt></tag> + + This macro is defined if you are compiling for the Apple GEOS system (-t geos-apple). + + <tag><tt>__GEOS_CBM__</tt></tag> + + This macro is defined if you are compiling for the GEOS 64/128 system (-t geos-cbm). <tag><tt>__LINE__</tt></tag> @@ -792,7 +797,7 @@ The compiler defines several macros at startup: <tag><tt>__NES__</tt></tag> - This macro is defined if the target is the NES (-t nes). + This macro is defined if the target is the Nintendo Entertainment System (-t nes). <tag><tt>__OPT__</tt></tag> @@ -816,15 +821,22 @@ The compiler defines several macros at startup: <tag><tt>__PLUS4__</tt></tag> - This macro is defined if the target is the plus/4 (-t plus4). + This macro is defined if the target is the Commodore Plus/4 (-t plus4). <tag><tt>__STDC_HOSTED__</tt></tag> This macro is expands to the integer constant 1. + <tag><tt>__SIM6502__</tt></tag> + + This macro is defined if the target is sim65 in 6502 mode (-t sim6502). + + <tag><tt>__SIM65C02__</tt></tag> + This macro is defined if the target is sim65 in 65C02 mode (-t sim65c02). + <tag><tt>__SUPERVISION__</tt></tag> - This macro is defined if the target is the supervision (-t supervision). + This macro is defined if the target is the Supervision (-t supervision). <tag><tt>__TIME__</tt></tag> @@ -833,7 +845,7 @@ The compiler defines several macros at startup: <tag><tt>__VIC20__</tt></tag> - This macro is defined if the target is the vic20 (-t vic20). + This macro is defined if the target is the Commodore VIC20 (-t vic20). </descrip> @@ -1308,15 +1320,6 @@ behavior as implementation-defined. (to be done) -<sect>Bugs/Feedback<p> - -If you have problems using the compiler, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>Copyright<p> This is the original compiler copyright: diff --git a/doc/cl65.sgml b/doc/cl65.sgml index a574049cc..2667ab555 100644 --- a/doc/cl65.sgml +++ b/doc/cl65.sgml @@ -88,7 +88,6 @@ Long options: --debug-info Add debug info --feature name Set an emulation feature --force-import sym Force an import of symbol `sym' - --forget-inc-paths Forget include search paths (compiler) --help Help (this text) --include-dir dir Set a compiler include directory path --ld-args options Pass options to the linker @@ -277,14 +276,6 @@ to do this. -<sect>Bugs/Feedback<p> - -If you have problems using the utility, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" name="uz@cc65.org">). - - - <sect>Copyright<p> cl65 (and all cc65 binutils) are (C) Copyright 1998-2004 Ullrich von diff --git a/doc/co65.sgml b/doc/co65.sgml index 126ed56fd..ea75dcf7c 100644 --- a/doc/co65.sgml +++ b/doc/co65.sgml @@ -316,15 +316,6 @@ will get an "undefined external" error for the _c64_hi symbol. -<sect>Bugs/Feedback<p> - -If you have problems using the converter, if you find any bugs, or if you're -doing something interesting with the code, I would be glad to hear from you. -Feel free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>Copyright<p> co65 is (C) Copyright 2003 Ullrich von Bassewitz. For usage of the binaries diff --git a/doc/da65.sgml b/doc/da65.sgml index 58d031eff..4dd6800d5 100644 --- a/doc/da65.sgml +++ b/doc/da65.sgml @@ -651,15 +651,6 @@ directives explained above: -<sect>Bugs/Feedback<p> - -If you have problems using the disassembler, if you find any bugs, or if -you're doing something interesting with the assembler, I would be glad to hear -from you. Feel free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>Copyright<p> da65 (and all cc65 binutils) are (C) Copyright 1998-2007 Ullrich von diff --git a/doc/index.sgml b/doc/index.sgml index e0b110ead..ef8e56327 100644 --- a/doc/index.sgml +++ b/doc/index.sgml @@ -2,12 +2,8 @@ <article> <title>cc65 Documentation Overview -<author>Ullrich von Bassewitz, <htmlurl url="mailto:uz@cc65.org" name="uz@cc65.org"> -<date>2005-8-6 - -<abstract> -Main documentation page, contains links to other available stuff. -</abstract> +<author><htmlurl url="https://github.com/oliverschmidt/cc65" name=""> +<date> <sect>Program documentation<p> @@ -60,9 +56,6 @@ Main documentation page, contains links to other available stuff. <tag><htmlurl url="coding.html" name="coding.html"></tag> Contains hints on creating the most effective code with cc65. - <tag><htmlurl url="compile.txt" name="compile.txt"></tag> - How to compile cc65 and the support tools. - <tag><htmlurl url="using-make.html" name="using-make.html"></tag> Build programs, using the GNU Make utility. @@ -159,21 +152,5 @@ Main documentation page, contains links to other available stuff. </descrip> -<sect>Miscellaneous<p> - -<descrip> - - <tag><htmlurl url="newvers.txt" name="newvers.txt"></tag> - Somewhat outdated. Lists the differences between my cc65 releases - and the original Atari version that was created by J. R. Dunning. - - <tag><htmlurl url="BUGS" name="BUGS"></tag> - Known cc65 bugs. - - <tag><htmlurl url="CREDITS" name="CREDITS"></tag> - Here is who helped with the compiler and other tools. - -</descrip> - </article> diff --git a/doc/intro.sgml b/doc/intro.sgml index c5ef7956a..1db4c0c04 100644 --- a/doc/intro.sgml +++ b/doc/intro.sgml @@ -371,12 +371,12 @@ The emulation, also, supports that method. <sect2>VICE<p> Available at <url -url="http://www.viceteam.org/">: +url="http://vice-emu.sourceforge.net/">: Emulates Commodore 64/128/VIC-20/PET/CBM II/Plus 4 computers. Supports -printers, serial port and adapters, stereo sound, disk drives and images, RAM -expansions, cartridges, ethernet connection, cycle-exact NTSC/PAL video, mice, -and joysticks. Includes monitor. Runs on MSDOS/PCDOS, Win9x/ME/NT/2000/XP, OS2, +printers, serial port and adapters, stereo sound, disk drives and images, RAM expansions, +cartridges, ethernet connection, cycle-exact NTSC/PAL video, mice, graphics tablet, +lightpens, and joysticks. Includes monitor. Runs on MSDOS/PCDOS, Win9x/ME/NT/2000/XP, OS2, BeOS x86, Acorn RISC OS, and most Unixes. Compile the tutorial with @@ -395,7 +395,7 @@ Substitute the name of a Commodore computer for that <tt/<sys>/: <item><tt/vic20/ </itemize> -Start the desired version of the emulator (CBM510 and CBM610 programs run on +Start the desired version of the emulator (CBM610 programs run on the CBM II [<tt/xcbm2/] emulator). In the Windows versions of VICE, choose <bf>File>Autoboot disk/tape diff --git a/doc/ld65.sgml b/doc/ld65.sgml index 5330a21d9..4f74b04c1 100644 --- a/doc/ld65.sgml +++ b/doc/ld65.sgml @@ -76,7 +76,6 @@ Long options: --config name Use linker config file --dbgfile name Generate debug information --define sym=val Define a symbol - --dump-config name Dump a builtin configuration --end-group End a library group --force-import sym Force an import of symbol `sym' --help Help (this text) @@ -140,7 +139,7 @@ Here is a description of all the command line options: The -o switch is used to give the name of the default output file. Depending on your output configuration, this name may NOT be used as - name for the output file. However, for the builtin configurations, this + name for the output file. However, for the default configurations, this name is used for the output file name. @@ -148,7 +147,7 @@ Here is a description of all the command line options: <tag><tt>-t sys, --target sys</tt></tag> The argument for the -t switch is the name of the target system. Since this - switch will activate a builtin configuration, it may not be used together + switch will activate a default configuration, it may not be used together with the <tt><ref id="option-C" name="-C"></tt> option. The following target systems are currently supported: @@ -158,6 +157,7 @@ Here is a description of all the command line options: <item>apple2 <item>apple2enh <item>atari + <item>atarixl <item>atmos <item>c16 (works also for the c116 with memory up to 32K) <item>c64 @@ -171,6 +171,8 @@ Here is a description of all the command line options: <item>nes <item>pet (all CBM PET systems except the 2001) <item>plus4 + <item>sim6502 + <item>sim65c02 <item>supervision <item>vic20 </itemize> @@ -252,9 +254,9 @@ Here is a description of all the command line options: <tag><tt>-S addr, --start-addr addr</tt></tag> Using -S you may define the default starting address. If and how this - address is used depends on the config file in use. For the builtin + address is used depends on the config file in use. For the default configurations, only the "none", "apple2" and "apple2enh" systems honor an - explicit start address, all other builtin config provide their own. + explicit start address, all other default configs provide their own. <tag><tt>-V, --version</tt></tag> @@ -313,56 +315,53 @@ Here is a description of all the command line options: <sect>Search paths<p> -Starting with version 2.10 there are now several search paths for files needed -by the linker: One for libraries, one for object files and one for config +Starting with version 2.10, there are now several search-path lists for files needed +by the linker: one for libraries, one for object files, and one for config files. <sect1>Library search path<p> -The library search path contains in this order: +The library search-path list contains in this order: <enum> <item>The current directory. -<item>A compiled in library path which is often <tt>/usr/lib/cc65/lib</tt> on - Linux systems. +<item>Any directory added with the <tt><ref id="option--lib-path" + name="--lib-path"></tt> option on the command line. <item>The value of the environment variable <tt/LD65_LIB/ if it is defined. <item>A subdirectory named <tt/lib/ of the directory defined in the environment variable <tt/CC65_HOME/, if it is defined. -<item>Any directory added with the <tt><ref id="option--lib-path" - name="--lib-path"></tt> option on the command line. +<item>An optionally compiled-in library path. </enum> <sect1>Object file search path<p> -The object file search path contains in this order: +The object file search-path list contains in this order: <enum> <item>The current directory. -<item>A compiled in directory which is often <tt>/usr/lib/cc65/obj</tt> on - Linux systems. +<item>Any directory added with the <tt><ref id="option--obj-path" + name="--obj-path"></tt> option on the command line. <item>The value of the environment variable <tt/LD65_OBJ/ if it is defined. <item>A subdirectory named <tt/obj/ of the directory defined in the environment variable <tt/CC65_HOME/, if it is defined. -<item>Any directory added with the <tt><ref id="option--obj-path" - name="--obj-path"></tt> option on the command line. +<item>An optionally compiled-in directory. </enum> <sect1>Config file search path<p> -The config file search path contains in this order: +The config file search-path list contains in this order: <enum> <item>The current directory. -<item>A compiled in directory which is often <tt>/usr/lib/cc65/cfg</tt> on - Linux systems. +<item>Any directory added with the <tt><ref id="option--cfg-path" + name="--cfg-path"></tt> option on the command line. <item>The value of the environment variable <tt/LD65_CFG/ if it is defined. <item>A subdirectory named <tt/cfg/ of the directory defined in the environment variable <tt/CC65_HOME/, if it is defined. -<item>Any directory added with the <tt><ref id="option--cfg-path" - name="--cfg-path"></tt> option on the command line. +<item>An optionally compiled-in directory. </enum> @@ -1025,24 +1024,6 @@ __STACKSIZE__=xxx/ on the command line. -<sect1>Builtin configurations<p> - -The builtin configurations are part of the linker source. They can be retrieved -with <tt/--dump-config/ and don't have a special format. So if you need a -special configuration, it's a good idea to start with the builtin configuration -for your system. In a first step, just replace <tt/-t target/ by <tt/-C -configfile/. Then go on and modify the config file to suit your needs. - - - -<sect1>Secondary configurations<p> - -Several machine specific binary packages are distributed together with secondary -configurations (in the cfg directory). These configurations can be used with -<tt/-C configfile/ too. - - - <sect>Special segments<p> The builtin config files do contain segments that have a special meaning for @@ -1075,15 +1056,6 @@ initialized. -<sect>Bugs/Feedback<p> - -If you have problems using the linker, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>Copyright<p> ld65 (and all cc65 binutils) are (C) Copyright 1998-2005 Ullrich von diff --git a/doc/library.sgml b/doc/library.sgml index 29a8ca063..6c2ced433 100644 --- a/doc/library.sgml +++ b/doc/library.sgml @@ -164,6 +164,7 @@ portable. conio implementations exist for the following targets: <item>apple2 <item>apple2enh <item>atari + <item>atarixl <item>atmos <item>c16 (works also for the c116 with up to 32K memory) <item>c64 @@ -187,8 +188,7 @@ which define constants for special characters and keys. For systems that have a joystick, <tt/joystick.h/ will define a subroutine to read the current value, including constants to evaluate the result of this -function. To help in writing portable code, the header file will define the -symbol <tt/__JOYSTICK__/ on systems that have a joystick. +function. @@ -201,23 +201,12 @@ the following targets: <item>apple2 <item>apple2enh <item>atari + <item>atarixl <item>c64 <item>c128 - <item>cbm510 </itemize> -The available functions are declared in <tt/mouse.h/ To help writing portable -code, the header file will define the symbol <tt/__MOUSE__/ in systems that -support a mouse. - - -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - +The available functions are declared in <tt/mouse.h/. <sect>Copyright<p> diff --git a/doc/lynx.sgml b/doc/lynx.sgml index 48c3d7d4a..f83552e50 100644 --- a/doc/lynx.sgml +++ b/doc/lynx.sgml @@ -194,7 +194,7 @@ The names in the parentheses denote the symbols to be used for static linking of <descrip> - <tag><tt/lynx-160-102-16.tgi (lynx_160_102_16)/</tag> + <tag><tt/lynx-160-102-16.tgi (lynx_160_102_16_tgi)/</tag> A TGI driver for the standard graphics mode (160×102 in 16 colors). The TGI driver is implemented as an interrupt driven dual buffering device. @@ -243,7 +243,7 @@ No extended memory drivers are currently available for the Lynx. <descrip> - <tag><tt/lynx-stdjoy.joy (lynx_stdjoy)/</tag> + <tag><tt/lynx-stdjoy.joy (lynx_stdjoy_joy)/</tag> A joystick driver for the standard buttons. </descrip><p> @@ -258,7 +258,7 @@ No mouse drivers are currently available for the Lynx. <descrip> - <tag><tt/lynx-comlynx.ser (lynx_comlynx)/</tag> + <tag><tt/lynx-comlynx.ser (lynx_comlynx_ser)/</tag> A serial driver for the ComLynx port. The ComLynx port has Tx and Rx wired together. Every byte is sent @@ -327,15 +327,6 @@ cc65 drivers require. But for the time being you can create less portable applications using these Lynx specific modules in <tt/lynx-cart-demo/. -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/nes.sgml b/doc/nes.sgml index c66b1f2ba..5d465c813 100644 --- a/doc/nes.sgml +++ b/doc/nes.sgml @@ -161,15 +161,6 @@ following functions (and a few others): -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/od65.sgml b/doc/od65.sgml index 2668b0b86..a1960109d 100644 --- a/doc/od65.sgml +++ b/doc/od65.sgml @@ -187,15 +187,6 @@ t.o: </verb></tscreen> -<sect>Bugs/Feedback<p> - -If you have problems using the converter, if you find any bugs, or if you're -doing something interesting with the code, I would be glad to hear from you. -Feel free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>Copyright<p> od65 is (C) Copyright 2000-2009, Ullrich von Bassewitz. For usage of the diff --git a/doc/pet.sgml b/doc/pet.sgml index 35e794db5..6d816ad77 100644 --- a/doc/pet.sgml +++ b/doc/pet.sgml @@ -150,13 +150,13 @@ No extended memory drivers are currently available for the PET. <descrip> - <tag><tt/pet-ptvjoy.joy (pet_ptvjoy)/</tag> + <tag><tt/pet-ptvjoy.joy (pet_ptvjoy_joy)/</tag> Driver for the Protovision 4-player adapter contributed by Groepaz. See <htmlurl url="http://www.protovision-online.de/hardw/hardwstart.htm" name="http://www.protovision-online.de/hardw/hardwstart.htm"> for prices and building instructions. Up to two joysticks are supported. - <tag><tt/pet-stdjoy.joy (pet_stdjoy)/</tag> + <tag><tt/pet-stdjoy.joy (pet_stdjoy_joy)/</tag> Driver for the standard PET userport joystick. </descrip><p> @@ -228,15 +228,6 @@ the following code: </verb></tscreen> -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/plus4.sgml b/doc/plus4.sgml index eefb85e21..a16eef9d3 100644 --- a/doc/plus4.sgml +++ b/doc/plus4.sgml @@ -163,7 +163,7 @@ No extended memory drivers are currently available for the Plus/4. <descrip> - <tag><tt/plus4-stdjoy.joy (plus4_stdjoy)/</tag> + <tag><tt/plus4-stdjoy.joy (plus4_stdjoy_joy)/</tag> Supports up to two joysticks connected to the standard joysticks port of the Plus/4. @@ -172,15 +172,14 @@ No extended memory drivers are currently available for the Plus/4. <sect1>Mouse drivers<p> -Currently no drivers available (in fact, the API for loadable mouse drivers -does not exist). +No mouse drivers are currently available for the Plus/4. <sect1>RS232 device drivers<p> <descrip> - <tag><tt/plus4-stdser.ser (plus4_stdser)/</tag> + <tag><tt/plus4-stdser.ser (plus4_stdser_ser)/</tag> Driver for the 6551 ACIA chip built into the Plus/4. Supports up to 19200 baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note that because of the peculiarities of the 6551 chip transmits are not @@ -237,15 +236,6 @@ feature in the <htmlurl url="ca65.html" name="assembler manual">. -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/sp65.sgml b/doc/sp65.sgml index 32dead645..3cf749e20 100644 --- a/doc/sp65.sgml +++ b/doc/sp65.sgml @@ -382,15 +382,6 @@ Possible attributes for this format are: -<sect>Bugs/Feedback<p> - -If you have problems using the assembler, if you find any bugs, or if -you're doing something interesting with the assembler, I would be glad to -hear from you. Feel free to contact me by email -(<htmlurl url="mailto:uz@cc65.org" name="uz@cc65.org">). - - - <sect>Copyright<p> sp65 (and all cc65 binutils) are (C) Copyright 1998-2012 Ullrich von Bassewitz diff --git a/doc/supervision.sgml b/doc/supervision.sgml index 504ba5194..0aa990ac5 100644 --- a/doc/supervision.sgml +++ b/doc/supervision.sgml @@ -146,15 +146,6 @@ following functions (and a few others): -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied diff --git a/doc/vic20.sgml b/doc/vic20.sgml index 1227ee667..562ea002a 100644 --- a/doc/vic20.sgml +++ b/doc/vic20.sgml @@ -153,10 +153,10 @@ No extended memory drivers are currently available for the VIC20. <descrip> - <tag><tt/vic20-stdjoy.joy (vic20_stdjoy)/</tag> + <tag><tt/vic20-stdjoy.joy (vic20_stdjoy_joy)/</tag> Supports one standard joystick connected to the joysticks port of the VIC20. - <tag><tt/vic20-ptvjoy.joy (vic20_ptvjoy)/</tag> + <tag><tt/vic20-ptvjoy.joy (vic20_ptvjoy_joy)/</tag> Driver for the Protovision 4-player adapter contributed by Groepaz. See <htmlurl url="http://www.protovision-online.de/hardw/hardwstart.htm" name="http://www.protovision-online.de/hardw/hardwstart.htm"> for prices and @@ -219,7 +219,7 @@ code: <tscreen><verb> /* Check for the existence of RAM */ - if (PEEK(0xA000) == POKE(0xA000, PEEK(0xA000)+1)) {<br> + if (PEEK(0xA000) == POKE(0xA000, PEEK(0xA000)+1)) { /* Add it to the heap */ _heapadd ((void *) 0xA000, 0x2000); } @@ -236,15 +236,6 @@ feature in the <htmlurl url="ca65.html" name="assembler manual">. -<sect>Bugs/Feedback<p> - -If you have problems using the library, if you find any bugs, or if you're -doing something interesting with it, I would be glad to hear from you. Feel -free to contact me by email (<htmlurl url="mailto:uz@cc65.org" -name="uz@cc65.org">). - - - <sect>License<p> This software is provided 'as-is', without any expressed or implied