Processor architecture - Revision history

91.153.162.47: /* PCs: x86 architecture */ typo in link

91.153.162.47 — Mon, 03 Jan 2011 07:47:08 GMT

PCs: x86 architecture: typo in link

← Older revision		Revision as of 07:47, 3 January 2011
Line 8:		Line 8:
	==PCs: x86 architecture==		==PCs: x86 architecture==

-	Most PCs are powered by processors produced by Intel or AMD that are referred to as [[:wikipedia:X86\|x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.	+	Most PCs are powered by processors produced by Intel or AMD that are referred to as [[:wikipedia:X86\|x86-compatible]]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.

	===Compiled Applications===		===Compiled Applications===

amigadave: wikify link

amigadave — Wed, 25 Aug 2010 13:35:59 GMT

wikify link

← Older revision		Revision as of 13:35, 25 August 2010
Line 1:		Line 1:
-	~~==Overview==~~
	The purpose of this page is to answer the following (reasonable) questions that come up in the community quite frequently:		The purpose of this page is to answer the following (reasonable) questions that come up in the community quite frequently:
	# Is it possible to make <some Windows application> run on Maemo?		# Is it possible to make <some Windows application> run on Maemo?
Line 8:		Line 7:

	==PCs: x86 architecture==		==PCs: x86 architecture==
-	Most PCs are powered by processors produced by Intel or AMD that are referred to as [~~http~~:~~//en.~~wikipedia~~.org/wiki/~~X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.	+
		+	Most PCs are powered by processors produced by Intel or AMD that are referred to as [[:wikipedia:X86\|x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.

	===Compiled Applications===		===Compiled Applications===

amigadave: /* Mobile devices: ARM architecture */ wikify link

amigadave — Mon, 14 Jun 2010 14:25:46 GMT

Mobile devices: ARM architecture: wikify link

← Older revision		Revision as of 14:25, 14 June 2010
Line 16:		Line 16:
	==Mobile devices: ARM architecture==		==Mobile devices: ARM architecture==

-	There is a much simpler instruction set called [~~http~~:~~//en.~~wikipedia~~.org/wiki/ARM_architecture~~ ARM] and, because of its simplicity, many mobile devices use an ARM-based processor. (Note that "simpler" does not necessarily imply "better" or "worse" for the end user: ARM processors are typically smaller and thus easier to make.) This is true of devices that run Maemo. Because the instruction set is different, most applications that will run on a PC will not directly run on maemo without recompiling. Recompiling requires the original description of the application in some human-readable computer language (the [[:wikipedia:source code\|source code]]) and this is not available for most commercial, proprietary applications (which are therefore referred to as ''closed source'').	+	There is a much simpler instruction set called [[:wikipedia:ARM architecture\|ARM]] and, because of its simplicity, many mobile devices use an ARM-based processor. (Note that "simpler" does not necessarily imply "better" or "worse" for the end user: ARM processors are typically smaller and thus easier to make.) This is true of devices that run Maemo. Because the instruction set is different, most applications that will run on a PC will not directly run on maemo without recompiling. Recompiling requires the original description of the application in some human-readable computer language (the [[:wikipedia:source code\|source code]]) and this is not available for most commercial, proprietary applications (which are therefore referred to as ''closed source'').

	==Emulation==		==Emulation==

amigadave: wikify and tidy

amigadave — Mon, 14 Jun 2010 14:24:43 GMT

wikify and tidy

← Older revision		Revision as of 14:24, 14 June 2010
Line 1:		Line 1:
-	===Overview===	+	==Overview==
	The purpose of this page is to answer the following (reasonable) questions that come up in the community quite frequently:		The purpose of this page is to answer the following (reasonable) questions that come up in the community quite frequently:
	# Is it possible to make <some Windows application> run on Maemo?		# Is it possible to make <some Windows application> run on Maemo?
Line 7:		Line 7:
	It attempts to do this by explaining about computer processor ''architecture'', and relates that to maemo software and hardware.		It attempts to do this by explaining about computer processor ''architecture'', and relates that to maemo software and hardware.

-	===PCs: x86 architecture===	+	==PCs: x86 architecture==
	Most PCs are powered by processors produced by Intel or AMD that are referred to as [http://en.wikipedia.org/wiki/X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.		Most PCs are powered by processors produced by Intel or AMD that are referred to as [http://en.wikipedia.org/wiki/X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.

	===Compiled Applications===		===Compiled Applications===
		+
	What that means is that, no matter what form the applications take, in the end they have to be presented to the CPU as x86 instructions. The most efficient applications are often the ones that are ''[[:wikipedia:Compiler\|compiled]]'' directly into a listing of these x86 instructions. For that reason, the most core parts of the operating system and the most demanding applications are usually distributed and stored as a [[:wikipedia:Executable\|binaries]] of this compiled state.		What that means is that, no matter what form the applications take, in the end they have to be presented to the CPU as x86 instructions. The most efficient applications are often the ones that are ''[[:wikipedia:Compiler\|compiled]]'' directly into a listing of these x86 instructions. For that reason, the most core parts of the operating system and the most demanding applications are usually distributed and stored as a [[:wikipedia:Executable\|binaries]] of this compiled state.

-	===Mobile devices: ARM architecture===	+	==Mobile devices: ARM architecture==
-	There is a much simpler instruction set called [http://en.wikipedia.org/wiki/ARM_architecture ARM] and, because of its simplicity, many mobile devices use an ARM-based processor. (Note that "simpler" does not necessarily imply "better" or "worse" for the end user: ARM processors are typically smaller and thus easier to make.) This is true of devices that run Maemo. Because the instruction set is different, most applications that will run on a PC will not directly run on maemo without recompiling. Recompiling requires the original description of the application in some human-readable computer language (the [[source code]]) and this is not available for most commercial, proprietary applications (which are therefore referred to as ''closed source'').	+

-	===Emulation===	+	There is a much simpler instruction set called [http://en.wikipedia.org/wiki/ARM_architecture ARM] and, because of its simplicity, many mobile devices use an ARM-based processor. (Note that "simpler" does not necessarily imply "better" or "worse" for the end user: ARM processors are typically smaller and thus easier to make.) This is true of devices that run Maemo. Because the instruction set is different, most applications that will run on a PC will not directly run on maemo without recompiling. Recompiling requires the original description of the application in some human-readable computer language (the [[:wikipedia:source code\|source code]]) and this is not available for most commercial, proprietary applications (which are therefore referred to as ''closed source'').
		+
		+	==Emulation==

	The only way to use the compiled binaries for one architecture on another architecture is through a translator. This is called an [[:wikipedia:Emulator\|emulator]]; it ''emulates'' the desired architecture for the software so that it is compatible. This can be a very inefficient process, with the emulated processor a few to tens of times slower than the native processor. In the context of the portable maemo devices with limited processing power and battery capacity, it means that emulating complex PC software is generally not practical. This is true of Microsoft's Windows operating system, and applications that run in Windows.		The only way to use the compiled binaries for one architecture on another architecture is through a translator. This is called an [[:wikipedia:Emulator\|emulator]]; it ''emulates'' the desired architecture for the software so that it is compatible. This can be a very inefficient process, with the emulated processor a few to tens of times slower than the native processor. In the context of the portable maemo devices with limited processing power and battery capacity, it means that emulating complex PC software is generally not practical. This is true of Microsoft's Windows operating system, and applications that run in Windows.
Line 22:		Line 24:
	See the [[emulators]] page for more specific details on what architectures and systems can be emulated in maemo.		See the [[emulators]] page for more specific details on what architectures and systems can be emulated in maemo.

-	===Conclusion and Relevance===	+	==Conclusion and Relevance==
		+
	What this means to you, the user, is that open standards and open source are your friend. Given enough time and enough demand, most anything that is "open" can and probably will be brought to maemo.		What this means to you, the user, is that open standards and open source are your friend. Given enough time and enough demand, most anything that is "open" can and probably will be brought to maemo.

amigadave: /* Emulation */ fix links

amigadave — Thu, 18 Mar 2010 08:25:29 GMT

Emulation: fix links

← Older revision		Revision as of 08:25, 18 March 2010
Line 18:		Line 18:
	===Emulation===		===Emulation===

-	The only way to use the compiled binaries for one architecture on another architecture is through a translator. This is called an [[emulator]]; it ''emulates'' the desired architecture for the software so that it is compatible. This can be a very inefficient process, with the emulated processor a few to tens of times slower than the native processor. In the context of the portable maemo devices with limited processing power and battery capacity, it means that emulating complex PC software is generally not practical. This is true of Microsoft's Windows operating system, and applications that run in Windows.	+	The only way to use the compiled binaries for one architecture on another architecture is through a translator. This is called an [[:wikipedia:Emulator\|emulator]]; it ''emulates'' the desired architecture for the software so that it is compatible. This can be a very inefficient process, with the emulated processor a few to tens of times slower than the native processor. In the context of the portable maemo devices with limited processing power and battery capacity, it means that emulating complex PC software is generally not practical. This is true of Microsoft's Windows operating system, and applications that run in Windows.

-	See the [[~~emulator~~]] page for more specific details on what architectures and systems can be emulated in maemo.	+	See the [[emulators]] page for more specific details on what architectures and systems can be emulated in maemo.

	===Conclusion and Relevance===		===Conclusion and Relevance===

amigadave: /* Compiled Applications */ wikipedia links

amigadave — Thu, 18 Mar 2010 08:23:23 GMT

Compiled Applications: wikipedia links

← Older revision		Revision as of 08:23, 18 March 2010
Line 11:		Line 11:

	===Compiled Applications===		===Compiled Applications===
-	What that means is that, no matter what form the applications take, in the end they have to be presented to the CPU as x86 instructions. The most efficient applications are often the ones that are ''[[compiled]]'' directly into a listing of these x86 instructions. For that reason, the most core parts of the operating system and the most demanding applications are usually distributed and stored as a [[~~binaries~~ \| ~~binary (computer readable) representation~~]] of this compiled state.	+	What that means is that, no matter what form the applications take, in the end they have to be presented to the CPU as x86 instructions. The most efficient applications are often the ones that are ''[[:wikipedia:Compiler\|compiled]]'' directly into a listing of these x86 instructions. For that reason, the most core parts of the operating system and the most demanding applications are usually distributed and stored as a [[:wikipedia:Executable\|binaries]] of this compiled state.

	===Mobile devices: ARM architecture===		===Mobile devices: ARM architecture===

amigadave: categorise

amigadave — Thu, 11 Feb 2010 15:03:18 GMT

categorise

← Older revision		Revision as of 15:03, 11 February 2010
Line 26:		Line 26:

	It also means that unless the owner of proprietary products sees value in releasing their product for maemo, it will probably never be available. Consider whether you are supporting open standards and open source when you make decisions what technology to use on projects so that you can use your maemo device most effectively.		It also means that unless the owner of proprietary products sees value in releasing their product for maemo, it will probably never be available. Consider whether you are supporting open standards and open source when you make decisions what technology to use on projects so that you can use your maemo device most effectively.
		+
		+	[[Category:Users]]
		+	[[Category:Hardware]]
		+	[[Category:Software]]

dneary at 19:40, 27 January 2010

dneary — Wed, 27 Jan 2010 19:40:16 GMT

← Older revision		Revision as of 19:40, 27 January 2010
Line 11:		Line 11:

	===Compiled Applications===		===Compiled Applications===
-	What that means is that, no matter what form the applications take, in the end they have to be presented to the CPU as x86 instructions. The most efficient applications are often the ones that are ''[[compiled]]'' directly into a listing of these x86 instructions. For that reason, the most core parts of the [[operating system]] and the most demanding [[applications]] are usually distributed and stored as a [[binaries \| binary (computer readable) representation]] of this compiled state.	+	What that means is that, no matter what form the applications take, in the end they have to be presented to the CPU as x86 instructions. The most efficient applications are often the ones that are ''[[compiled]]'' directly into a listing of these x86 instructions. For that reason, the most core parts of the operating system and the most demanding applications are usually distributed and stored as a [[binaries \| binary (computer readable) representation]] of this compiled state.

	===Mobile devices: ARM architecture===		===Mobile devices: ARM architecture===

flandry: /* PCs: x86 architecture */

flandry — Fri, 01 Jan 2010 00:02:41 GMT

PCs: x86 architecture

← Older revision		Revision as of 00:02, 1 January 2010
Line 8:		Line 8:

	===PCs: x86 architecture===		===PCs: x86 architecture===
-	Most PCs are powered by processors produced by Intel or AMD that are referred to as [http://en.wikipedia.org/wiki/X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set.	+	Most PCs are powered by processors produced by Intel or AMD that are referred to as [http://en.wikipedia.org/wiki/X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set. Software that works on one will work on another.

	===Compiled Applications===		===Compiled Applications===

flandry: State purpose of article: if it does not accomplish this purpose, please revise the article (not the purpose) so that it does.

flandry — Thu, 31 Dec 2009 23:45:13 GMT

State purpose of article: if it does not accomplish this purpose, please revise the article (not the purpose) so that it does.

← Older revision		Revision as of 23:45, 31 December 2009
Line 1:		Line 1:
		+	===Overview===
		+	The purpose of this page is to answer the following (reasonable) questions that come up in the community quite frequently:
		+	# Is it possible to make <some Windows application> run on Maemo?
		+	# Why or why not?
		+	# Why do the technologies I choose to use and support matter?
		+
		+	It attempts to do this by explaining about computer processor ''architecture'', and relates that to maemo software and hardware.
		+
	===PCs: x86 architecture===		===PCs: x86 architecture===
	Most PCs are powered by processors produced by Intel or AMD that are referred to as [http://en.wikipedia.org/wiki/X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set.		Most PCs are powered by processors produced by Intel or AMD that are referred to as [http://en.wikipedia.org/wiki/X86 x86-compatible]. Pentium to Core2, Athlon to Phenom, all of these are CPUs (Central Processing Units) compatible with the x86 instruction set.