various processor architectures.
various processor architectures.
I have been trying to find a guide to the various processor architectures such as x86, arm, mips, pps, etc. discribing the pros and cons, generel differenses and such.
Sadly i havent had much luck with it, so i was thinking if anyone here would know of any such recourses.
I know its not the first time i have been posting about this subject, but i think its about time i get an indept understanding of it.
Sadly i havent had much luck with it, so i was thinking if anyone here would know of any such recourses.
I know its not the first time i have been posting about this subject, but i think its about time i get an indept understanding of it.
This was supposed to be a cool signature...
- Brynet-Inc
- Member
- Posts: 2426
- Joined: Tue Oct 17, 2006 9:29 pm
- Libera.chat IRC: brynet
- Location: Canada
- Contact:
- Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Well, there are two things to consider:
The processor architecture - you have CISC and RISC systems. RISC systems are on average faster than CISC systems, but are more difficult to program in raw assembly. Of course, difficulty is a subjective term. The AVR instruction set is not difficult at all while PA is one big mess.
You might want to consider address size as part of the equation - you have everything from 8-bit to 64-bit systems (I wouldn't be amazed if it were even 128-bit already)
Second, the system architecture, i.e. everything around the processor. These define the system more than the CPU - you can just recompile your program to a different processor, but the hardware present dictates what is actually possible.
CISC architectures: x86, 68k, 6502, etc
RISC architectures: AVR, ARM, MIPS, SuperH, HPPA, etc
The processor architecture - you have CISC and RISC systems. RISC systems are on average faster than CISC systems, but are more difficult to program in raw assembly. Of course, difficulty is a subjective term. The AVR instruction set is not difficult at all while PA is one big mess.
You might want to consider address size as part of the equation - you have everything from 8-bit to 64-bit systems (I wouldn't be amazed if it were even 128-bit already)
Second, the system architecture, i.e. everything around the processor. These define the system more than the CPU - you can just recompile your program to a different processor, but the hardware present dictates what is actually possible.
CISC architectures: x86, 68k, 6502, etc
RISC architectures: AVR, ARM, MIPS, SuperH, HPPA, etc
I dont think there can be any doubt, atleast now, that it is risc im most interested in, but still there are alot of different cpus "system architectures".
I am really only interested in a workhorse, fx. no graphics (that cant be spelled right), keyboard, mouse, etc. will be needed.
I will need a cpu of course, and memory and an interface, preferably a lan port. Some storage will allso be needed.
But it is the cpu which i find interesting as it will be doing most of the work.
I am really only interested in a workhorse, fx. no graphics (that cant be spelled right), keyboard, mouse, etc. will be needed.
I will need a cpu of course, and memory and an interface, preferably a lan port. Some storage will allso be needed.
But it is the cpu which i find interesting as it will be doing most of the work.
This was supposed to be a cool signature...
1. They are cheap and readily available, almost every mobile device uses one.
2. It has a linux port, so development is a little easier.
3. Loads of other people are using it (including pcmattman) so they can help you, whereas with PPC et al. you're a little on your own.
4. The instruction set is very nice.
2. It has a linux port, so development is a little easier.
3. Loads of other people are using it (including pcmattman) so they can help you, whereas with PPC et al. you're a little on your own.
4. The instruction set is very nice.
They may be cheap, but i havent really been able to find anything remotely usefull anywhere, enless i want to bye bundles of 1000. (of course i cant affort that )JamesM wrote:1. They are cheap and readily available, almost every mobile device uses one.
I not quite sure what a linux port is.JamesM wrote:2. It has a linux port, so development is a little easier.
Yes, we have been talking about this in an earlier threath (never can remember how to spell that), and of course it is allways nice to know where help is, but i dont think any of them is interested in teaching me from scratch how things work and i havent been able to find much on the net, not anything usefull that is.JamesM wrote:3. Loads of other people are using it (including pcmattman) so they can help you, whereas with PPC et al. you're a little on your own.
On that we can agree (i think)JamesM wrote:4. The instruction set is very nice.
This was supposed to be a cool signature...
- Brynet-Inc
- Member
- Posts: 2426
- Joined: Tue Oct 17, 2006 9:29 pm
- Libera.chat IRC: brynet
- Location: Canada
- Contact:
You don't know what "port" means or "Linux" ?Zacariaz wrote:I not quite sure what a linux port is.JamesM wrote:2. It has a linux port, so development is a little easier.
Porting software means.. adapting your code for a new operating system/architecture.
Thus he means, There is a native port of Linux to ARM.. NetBSD/OpenBSD as well
When I'm drunk, I usually can't communicate at all.Zacariaz wrote:Thats what happens when not comunicating in your native langage. Sometimes it allso happen in my native language, but mostly when im drunk
As for the "bundle of 1000", that's life for you. The way you can buy x86 CPUs single-piece is somewhat special, virtually any other CPU is build in bundles to companies building appliances with them (including the PPC, which caused the Amiga market no little headache as 1000 CPUs is quite a bit there).
Every good solution is obvious once you've found it.