FF7/Kernel/Memory management - Revision history

BukTop: /* VRAM management */

2019-07-12T22:57:08Z

‎VRAM management

BukTop: 22 revisions imported

2019-05-23T02:19:29Z

22 revisions imported

my_wiki>BukTop: 19 revisions imported

2018-04-04T09:34:50Z

19 revisions imported

my_wiki>BukTop at 02:24, 24 March 2018

2018-03-24T02:24:45Z

my_wiki>BukTop: Created page with "== RAM management == No matter what module is banked into memory, there is a section of memory 4,340 bytes long (0x10F4 bytes) that is reserved for all the variables for th..."

2018-03-24T02:21:55Z

Created page with "== RAM management == No matter what module is banked into memory, there is a section of memory 4,340 bytes long (0x10F4 bytes) that is reserved for all the variables for th..."

my_wiki>Lasyan3@hotmail.com: /* RAM management */

2011-06-18T09:28:26Z

‎RAM management

my_wiki>Synergy Blades: /* Spelling */

2005-03-20T23:04:31Z

‎Spelling

my_wiki>Synergy Blades: /* Spelling */

2005-03-20T23:02:13Z

‎Spelling

my_wiki>Synergy Blades at 23:19, 10 March 2005

2005-03-10T23:19:10Z

my_wiki>Synergy Blades: /* Table converted */

2005-03-10T23:18:41Z

‎Table converted

Show changes

@@ Line 64: / Line 64: @@
 <br /> The following is a typical state of VRAM during game play.
-[[File:Gears_img_3.jpg]]
+[[File:Gears img 3.jpg|thumb]]
 The two game screens on the left side are the video buffer and the back buffer. The patchwork of graphics on the top right are the field graphics for that scene. The bottom row consists of cached graphics and special effects and on right semi-permanent and permanent textures for the game.
@@ Line 70: / Line 70: @@
 <br /> The following is a schematic representation of VRAM and all it's texture boundaries.
-[[File:Gears_img_4.jpg]]
+[[File:Gears img 4.jpg|thumb]]
 Here the sections of VRAM are much more visible. The large cyan areas are the video frame buffers. The PSX uses a standard double page buffer to animate the game. The blank areas above and below the frame buffers are blank to allow for a correct V-sync. The dark blue areas to the right of the frame buffers are when the game plays 24 bit movies. This requires a slightly larger display and the first two texture caches are overwritten. During times in the game where no movies can take place, such as Battle, textures are commonly placed here.

@@ Line 64: / Line 64: @@
 <br /> The following is a typical state of VRAM during game play.
-[[File:Gears_img_3.jpg|[[Image:Gears_img_3.jpg|Gears img 3.jpg]]]]
+[[File:Gears_img_3.jpg]]
 The two game screens on the left side are the video buffer and the back buffer. The patchwork of graphics on the top right are the field graphics for that scene. The bottom row consists of cached graphics and special effects and on right semi-permanent and permanent textures for the game.
@@ Line 70: / Line 70: @@
 <br /> The following is a schematic representation of VRAM and all it's texture boundaries.
-[[File:Gears_img_4.jpg|[[Image:Gears_img_4.jpg|Gears img 4.jpg]]]]
+[[File:Gears_img_4.jpg]]
 Here the sections of VRAM are much more visible. The large cyan areas are the video frame buffers. The PSX uses a standard double page buffer to animate the game. The blank areas above and below the frame buffers are blank to allow for a correct V-sync. The dark blue areas to the right of the frame buffers are when the game plays 24 bit movies. This requires a slightly larger display and the first two texture caches are overwritten. During times in the game where no movies can take place, such as Battle, textures are commonly placed here.

@@ Line 1: / Line 1: @@
-== RAM management ==
+==  RAM management  ==
 No matter what module is banked into memory, there is a section of memory 4,340 bytes long (0x10F4 bytes) that is reserved for all the variables for the entire game. This entire image is called the "[[FF7/Savemap|Savemap]]". When it's time to save a game, this section of memory is copied to non-volatile ram, such as a hard disk or memory card.
-Within the [[FF7/Savemap|Savemap]] there are 5 banks of memory that are directly accessible by the [[FF7/Field script|field scripting language]]. These can either be accessed 8 bits or 16 bits at a time depending on the field command argument. The following table is basic memory map of the banks and how they relate to the [[FF7/Savemap|Savemap]]. There is also an allocation for 256 bytes for temporary field variables. These are not used between field files and are not saved.
+Within the [[FF7/Savemap|Savemap]] there are 5 banks of memory that are directly accessible by the [[FF7/Field_script|field scripting language]]. These can either be accessed 8 bits or 16 bits at a time depending on the field command argument. The following table is basic memory map of the banks and how they relate to the [[FF7/Savemap|Savemap]]. There is also an allocation for 256 bytes for temporary field variables. These are not used between field files and are not saved.
-{| border="0" cellpadding="3" cellspacing="1" style="background: rgb(0,0,0)" align="center"
+{| class="wikitable"
-!style="background:rgb(204,204,204); width:80px;" align="center" | Offset
+! style="background: rgb(204,204,204); width: 80px" align="center" | Offset
-!style="background:rgb(204,204,204); width:80px;" align="center" | 8 Bit Field Bank
+! style="background: rgb(204,204,204); width: 80px" align="center" | 8 Bit Field Bank
-!style="background:rgb(204,204,204); width:100px;" align="center" | 16 Bit Filed Bank
+! style="background: rgb(204,204,204); width: 100px" align="center" | 16 Bit Filed Bank
-!style="background:rgb(204,204,204); width:250px;" align="center" | Description
+! style="background: rgb(204,204,204); width: 250px" align="center" | Description
 |-
-|style="background:rgb(255,255,255);" | 0x0000
+| 0x0000
-|style="background:rgb(255,255,255);" align="center" | N/A
+| style="background: rgb(255,255,255)" align="center" | N/A
-|style="background:rgb(255,255,255);" align="center" | N/A
+| style="background: rgb(255,255,255)" align="center" | N/A
-|style="background:rgb(255,255,255);" | Beginning of [[FF7/Savemap|Savemap]]
 |-
-|style="background:rgb(152,204,255);" | 0x0BA4
+| style="background: rgb(152,204,255)" | 0x0BA4
-|style="background:rgb(152,204,255);" align="center" | 0x1
+| style="background: rgb(152,204,255)" align="center" | 0x1
-|style="background:rgb(152,204,255);" align="center" | 0x2
+| style="background: rgb(152,204,255)" align="center" | 0x2
-|style="background:rgb(152,204,255);" | Field Script Bank 1
+| style="background: rgb(152,204,255)" | Field Script Bank 1
 |-
-|style="background:rgb(152,204,255);" | 0x0CA4
+| style="background: rgb(152,204,255)" | 0x0CA4
-|style="background:rgb(152,204,255);" align="center" | 0x3
+| style="background: rgb(152,204,255)" align="center" | 0x3
-|style="background:rgb(152,204,255);" align="center" | 0x4
+| style="background: rgb(152,204,255)" align="center" | 0x4
-|style="background:rgb(152,204,255);" | Field Script Bank 2
+| style="background: rgb(152,204,255)" | Field Script Bank 2
 |-
-|style="background:rgb(152,204,255);" | 0x0DA4
+| style="background: rgb(152,204,255)" | 0x0DA4
-|style="background:rgb(152,204,255);" align="center" | 0xB
+| style="background: rgb(152,204,255)" align="center" | 0xB
-|style="background:rgb(152,204,255);" align="center" | 0xC
+| style="background: rgb(152,204,255)" align="center" | 0xC
-|style="background:rgb(152,204,255);" | Field Script Bank 3
+| style="background: rgb(152,204,255)" | Field Script Bank 3
 |-
-|style="background:rgb(152,204,255);" | 0x0EA4
+| style="background: rgb(152,204,255)" | 0x0EA4
-|style="background:rgb(152,204,255);" align="center" | 0xD
+| style="background: rgb(152,204,255)" align="center" | 0xD
-|style="background:rgb(152,204,255);" align="center" | 0xE
+| style="background: rgb(152,204,255)" align="center" | 0xE
-|style="background:rgb(152,204,255);" | Field Script Bank 4
+| style="background: rgb(152,204,255)" | Field Script Bank 4
 |-
-|style="background:rgb(152,204,255);" | 0x0FA4
+| style="background: rgb(152,204,255)" | 0x0FA4
-|style="background:rgb(152,204,255);" align="center" | 0xF
+| style="background: rgb(152,204,255)" align="center" | 0xF
-|style="background:rgb(152,204,255);" align="center" | 0x7
+| style="background: rgb(152,204,255)" align="center" | 0x7
-|style="background:rgb(152,204,255);" | Field Script Bank 5
+| style="background: rgb(152,204,255)" | Field Script Bank 5
 |-
-|style="background:rgb(255,255,255);" | 0x10F4
+| 0x10F4
-|style="background:rgb(255,255,255);" align="center" | N/A
+| style="background: rgb(255,255,255)" align="center" | N/A
-|style="background:rgb(255,255,255);" align="center" | N/A
+| style="background: rgb(255,255,255)" align="center" | N/A
-|style="background:rgb(255,255,255);" | End of [[FF7/Savemap|Savemap]]
 |}
-{| border="0" cellpadding="3" cellspacing="1" style="background: rgb(0,0,0)" align="center"
-|style="background:rgb(255,255,255); width:80px;" | N/A
+{| class="wikitable"
-|style="background:rgb(255,255,255); width:80px;" align="center" | 0x5
+| style="background: rgb(255,255,255); width: 80px" | N/A
-|style="background:rgb(255,255,255); width:100px;" align="center" | 0x6
+| style="background: rgb(255,255,255); width: 80px" align="center" | 0x5
-|style="background:rgb(255,255,255); width:250px;" | Temporary field variables (256 bytes)
+| style="background: rgb(255,255,255); width: 100px" align="center" | 0x6
 |}
-== VRAM management ==
+==  VRAM management  ==
 The kernel is in charge of allocating, caching, and displaying in Video RAM. In the case of the PSX, port, the Playstation only has 1 megabyte of VRAM which makes this task a little complex. This is alleviated somewhat by using the PSX's VRAM caching system.
 The PSX video memory can best be seen as a rectangular "surface" made up of 2048x512 pixels. A slight caveat to this model is that the PSX can hold multiple color depths in VRAM at the same time. To make the VRAM a little easier to visualize, This document represents VRAM as a 1024x512 matrix to allow for some color depth in either direction and to minimize some extreme skewing of the video buffers.
-The following is a typical state of VRAM during game play.
+<br /> The following is a typical state of VRAM during game play.
-[[Image:Gears_img_3.jpg]]
+[[File:Gears_img_3.jpg|[[Image:Gears_img_3.jpg|Gears img 3.jpg]]]]
 The two game screens on the left side are the video buffer and the back buffer. The patchwork of graphics on the top right are the field graphics for that scene. The bottom row consists of cached graphics and special effects and on right semi-permanent and permanent textures for the game.
-The following is a schematic representation of VRAM and all it's texture boundaries.
+[[File:Gears_img_4.jpg|[[Image:Gears_img_4.jpg|Gears img 4.jpg]]]]
 Here the sections of VRAM are much more visible. The large cyan areas are the video frame buffers. The PSX uses a standard double page buffer to animate the game. The blank areas above and below the frame buffers are blank to allow for a correct V-sync. The dark blue areas to the right of the frame buffers are when the game plays 24 bit movies. This requires a slightly larger display and the first two texture caches are overwritten. During times in the game where no movies can take place, such as Battle, textures are commonly placed here.
@@ Line 79: / Line 80: @@
 All the blank rectangles are the texture cache boundaries. In order of volatility, the top two rows of cache space are overwritten from left to right, and then the bottom rows are overwritten. The textures on the bottom right are barely overwritten except for key places.
 One of the big rules on PSX development is that direct hardware access is a prohibited. Everything must go through the BIOS or the program will risk being incompatible with later systems. This means not only from PSX to PS2, but also all the trivial hardware revisions as well. This creates a problem for the kernel. During module transitions (for example, going from "Map" to "Battle"), the engine actually "preloads" the next module while the current one is still executing. This loading of data can't be done with a simple open() or read() BIOS syscall. Whenever you enter the BIOS, the rest of the system comes to a screeching halt until it is exited.
 This problem is solved by the FF7 actually controlling the CD-ROM access itself though faster, low-level BIOS calls. The kernel can only load 8 kilobytes at a time in this "quick mode" In this mode the kernel also only references files by what sector of the CD-ROM the data is located on, not by filename.

@@ Line 37: / Line 37: @@
 |-
 |style="background:rgb(152,204,255);" | 0x0FA4
 |style="background:rgb(152,204,255);" align="center" | 0x7
 |style="background:rgb(152,204,255);" | Field Script Bank 5
 |-
@@ Line 52: / Line 52: @@
 |style="background:rgb(255,255,255); width:250px;" | Temporary field variables (256 bytes)
 |}
 == VRAM management ==

@@ Line 82: / Line 82: @@
 == PSX CD-ROM management ==
-One of the big rules on PSX development is direct hardware access is a prohibited. Everything must go through the BIOS or the program will risk being incompatible with later systems. This means not only the from PSX to PS2, but also all the trivial hardware revisions as well. This creates a problem for the kernel. During module transitions, (For example, going from "Map" to "Battle"), the engine actually "preloads" the next module while the current one is still executing. This loading of data can't be done with a simple open() or read() BIOS syscall. Whenever you enter the BIOS, the rest of the system comes to a screeching halt until it is exited.
+One of the big rules on PSX development is that direct hardware access is a prohibited. Everything must go through the BIOS or the program will risk being incompatible with later systems. This means not only from PSX to PS2, but also all the trivial hardware revisions as well. This creates a problem for the kernel. During module transitions (for example, going from "Map" to "Battle"), the engine actually "preloads" the next module while the current one is still executing. This loading of data can't be done with a simple open() or read() BIOS syscall. Whenever you enter the BIOS, the rest of the system comes to a screeching halt until it is exited.
 This problem is solved by the FF7 actually controlling the CD-ROM access itself though faster, low-level BIOS calls. The kernel can only load 8 kilobytes at a time in this "quick mode" In this mode the kernel also only references files by what sector of the CD-ROM the data is located on, not by filename.

← Older revision	Revision as of 02:19, 23 May 2019
(No difference)

← Older revision	Revision as of 09:34, 4 April 2018
(No difference)

@@ Line 56: / Line 56: @@
 == VRAM management ==
-The kernel is in charge of allocating, caching, and displaying in Video RAM. The the case if the PSX, port, the Playstation only has 1 megabyte of VRAM which makes this task a little complex. This is alleviated somewhat by using the PSX's VRAM caching system.
+The kernel is in charge of allocating, caching, and displaying in Video RAM. In the case of the PSX, port, the Playstation only has 1 megabyte of VRAM which makes this task a little complex. This is alleviated somewhat by using the PSX's VRAM caching system.
 The PSX video memory can best be seen as a rectangular "surface" made up of 2048x512 pixels. A slight caveat to this model is that the PSX can hold multiple color depths in VRAM at the same time. To make the VRAM a little easier to visualize, This document represents VRAM as a 1024x512 matrix to allow for some color depth in either direction and to minimize some extreme skewing of the video buffers.
@@ Line 74: / Line 74: @@
 Here the sections of VRAM are much more visible. The large cyan areas are the video frame buffers. The PSX uses a standard double page buffer to animate the game. The blank areas above and below the frame buffers are blank to allow for a correct V-sync. The dark blue areas to the right of the frame buffers are when the game plays 24 bit movies. This requires a slightly larger display and the first two texture caches are overwritten. During times in the game where no movies can take place, such as Battle, textures are commonly placed here.
-The magenta area under the video buffers is the Color Look Up Tables (CLUT). This is where the texture palettes are stored. This is also allows the PSX to display multiple color depths at the same time. The red area to the right is extra CLUT space when it is needed and there are no textures cached there.
+The magenta area under the video buffers is the Color Look Up Tables (CLUT). This is where the texture palettes are stored. This also allows the PSX to display multiple color depths at the same time. The red area to the right is extra CLUT space when it is needed and there are no textures cached there.
 The green area on the right is the permanent menu textures and the yellow is where the menu font is located.