This is the
talk page for discussing improvements to the
NEC V60 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find video game sources: "NEC V60" – news · newspapers · books · scholar · JSTOR · free images · free news sources · TWL · NYT · WP reference · VG/RS · VG/RL · WPVG/Talk |
![]() | A fact from NEC V60 appeared on Wikipedia's
Main Page in the
Did you know column on 12 March 2014 (
check views). The text of the entry was as follows:
| ![]() |
![]() | This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
|
The comment about the Sega Saturn should be removed because it is irrelevant and incorrect:
1. There is no evidence Sega used Model 1 as a reference for the Saturn. The Saturn architecture is entirely unlike Model 1 and bears absolutely no resemblance to it.
2. There is no evidence Sega planned to use a V60 in the Saturn. While the Saturn video hardware is a predecessor for the System 32 video hardware, the rest of the design is highly SH-2 centric (specifically the SH-2 specific SCU and a system memory architecture closely tied to the SH-2 feature set).
The comment is speculative and offers no proof to back up these claims.
130.65.11.98 ( talk) —Preceding undated comment added 05:18, 2 March 2010 (UTC).
It was probably just an announcement but [3] mentions "There was an article about the V80 in the February 13, 1989 issue of EE Times." EE Times on-line archives don't go back that far though, so it's print only. Someone not using his real name ( talk) 18:58, 14 February 2014 (UTC)
There's an article in English in a French book/proceedings [4]; it's pretty obscure though obtainable through interlibrary loan in the US. The 2011 paper is unfortunately mostly focused on V70's replacement... Someone not using his real name ( talk) 23:10, 14 February 2014 (UTC)
This structured link description is removed from the article. Instead of it, some descriptions need to be added in the article itself. Some general descriptions might be suitable for locating in other computer architecture related articles. Cafeduke ( talk) 02:52, 4 March 2018 (UTC)
"== See also =="
In NEC V60#Unix (non-real-time and real-time), it says:
NEC also developed a variant for V60/V70/V80, with a focus on a real-time operation, called Real-time UNIX RX-UX 832. It has a double-layered kernel structure, and all the kernel calls of Unix issues tasks to the real-time kernel.
Before the recent copy-editing, it said
NEC also developed a variant for V60/V70/V80 with a focus on a real-time operation called Real-time UNIX RX-UX 832. It has double layered kernel structure, and all the kernel call of Unix issues task to the real-time kernel.
but neither is clear.
The "Real-Time UNIX Operating System: RX-UX 832" paper cited as a reference doesn't say very much about the structure of the OS. A diagram shows a box labeled "The V60/V70 RTOS", with, inside that box:
Outside, and above, the "The V60/V70 RTOS" box are two sets of other boxes:
They describe the OS as being built with the "building block approach". The paragraphs under "building block approach" say that
A virtual memory management mechanism for UNIX specific demand paging and a UNIX user-interface are maintained by a Unix supervisor. On the other hand, simpler and time-dependent functions, a memory management mechanism for real address spaces and common capabilities, such as a task scheduling, are provided by a real time operating system.
They don't indicate whether the arrows that go from "Unix task"s into the "The V60/V70 RTOS" box represent straightforward system calls, message-passing calls, or some other form of control transfer. The fact that there are arrows going from "Unix task"s to the "File Systems" box suggests that not all UNIX APIs that are traditionally implemented as "system calls" are implemented as transfers of control to the Unix supervisor.
"Task" can either be used in the conventional sense of a job to perform or in the technical sense that's similar to process. In "all the kernel call of Unix issues task to the real-time kernel", it sounds as if it might be used in the first sense, although, from the diagram, some calls from "Unix task"s to "The V60/V70 RTOS" don't go through the "Real-time interface" directly to "The Real-Time Kernel" - some go either to "Unix supervisor" or "File System".
If anybody has a reference giving more details, that would be useful. Guy Harris ( talk) 08:20, 21 May 2020 (UTC)
NEC developed a variant that focuses on real-time operation, to run on V60/V70/V80. Called Real-time UNIX RX-UX 832, it has a double-layered kernel structure, with all task scheduling handled by the real-time kernel.
@ Dhtwiki: Regarding this revert: Some of the links in citations needed archive links because they are reported as live even though the cited content has been removed. (For example: http://www.chipcatalog.com/NEC/MV-4000.htm) It's useful to have the archive links there in any case, since live pages could disappear at any time, which would leave readers unable to verify or read more detail. -- Beland ( talk) 19:47, 23 December 2021 (UTC)
This is the
talk page for discussing improvements to the
NEC V60 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find video game sources: "NEC V60" – news · newspapers · books · scholar · JSTOR · free images · free news sources · TWL · NYT · WP reference · VG/RS · VG/RL · WPVG/Talk |
![]() | A fact from NEC V60 appeared on Wikipedia's
Main Page in the
Did you know column on 12 March 2014 (
check views). The text of the entry was as follows:
| ![]() |
![]() | This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||
|
The comment about the Sega Saturn should be removed because it is irrelevant and incorrect:
1. There is no evidence Sega used Model 1 as a reference for the Saturn. The Saturn architecture is entirely unlike Model 1 and bears absolutely no resemblance to it.
2. There is no evidence Sega planned to use a V60 in the Saturn. While the Saturn video hardware is a predecessor for the System 32 video hardware, the rest of the design is highly SH-2 centric (specifically the SH-2 specific SCU and a system memory architecture closely tied to the SH-2 feature set).
The comment is speculative and offers no proof to back up these claims.
130.65.11.98 ( talk) —Preceding undated comment added 05:18, 2 March 2010 (UTC).
It was probably just an announcement but [3] mentions "There was an article about the V80 in the February 13, 1989 issue of EE Times." EE Times on-line archives don't go back that far though, so it's print only. Someone not using his real name ( talk) 18:58, 14 February 2014 (UTC)
There's an article in English in a French book/proceedings [4]; it's pretty obscure though obtainable through interlibrary loan in the US. The 2011 paper is unfortunately mostly focused on V70's replacement... Someone not using his real name ( talk) 23:10, 14 February 2014 (UTC)
This structured link description is removed from the article. Instead of it, some descriptions need to be added in the article itself. Some general descriptions might be suitable for locating in other computer architecture related articles. Cafeduke ( talk) 02:52, 4 March 2018 (UTC)
"== See also =="
In NEC V60#Unix (non-real-time and real-time), it says:
NEC also developed a variant for V60/V70/V80, with a focus on a real-time operation, called Real-time UNIX RX-UX 832. It has a double-layered kernel structure, and all the kernel calls of Unix issues tasks to the real-time kernel.
Before the recent copy-editing, it said
NEC also developed a variant for V60/V70/V80 with a focus on a real-time operation called Real-time UNIX RX-UX 832. It has double layered kernel structure, and all the kernel call of Unix issues task to the real-time kernel.
but neither is clear.
The "Real-Time UNIX Operating System: RX-UX 832" paper cited as a reference doesn't say very much about the structure of the OS. A diagram shows a box labeled "The V60/V70 RTOS", with, inside that box:
Outside, and above, the "The V60/V70 RTOS" box are two sets of other boxes:
They describe the OS as being built with the "building block approach". The paragraphs under "building block approach" say that
A virtual memory management mechanism for UNIX specific demand paging and a UNIX user-interface are maintained by a Unix supervisor. On the other hand, simpler and time-dependent functions, a memory management mechanism for real address spaces and common capabilities, such as a task scheduling, are provided by a real time operating system.
They don't indicate whether the arrows that go from "Unix task"s into the "The V60/V70 RTOS" box represent straightforward system calls, message-passing calls, or some other form of control transfer. The fact that there are arrows going from "Unix task"s to the "File Systems" box suggests that not all UNIX APIs that are traditionally implemented as "system calls" are implemented as transfers of control to the Unix supervisor.
"Task" can either be used in the conventional sense of a job to perform or in the technical sense that's similar to process. In "all the kernel call of Unix issues task to the real-time kernel", it sounds as if it might be used in the first sense, although, from the diagram, some calls from "Unix task"s to "The V60/V70 RTOS" don't go through the "Real-time interface" directly to "The Real-Time Kernel" - some go either to "Unix supervisor" or "File System".
If anybody has a reference giving more details, that would be useful. Guy Harris ( talk) 08:20, 21 May 2020 (UTC)
NEC developed a variant that focuses on real-time operation, to run on V60/V70/V80. Called Real-time UNIX RX-UX 832, it has a double-layered kernel structure, with all task scheduling handled by the real-time kernel.
@ Dhtwiki: Regarding this revert: Some of the links in citations needed archive links because they are reported as live even though the cited content has been removed. (For example: http://www.chipcatalog.com/NEC/MV-4000.htm) It's useful to have the archive links there in any case, since live pages could disappear at any time, which would leave readers unable to verify or read more detail. -- Beland ( talk) 19:47, 23 December 2021 (UTC)