So Sup Forums, Z80 or 6502?
(Intel/motorola shitters do not apply)
So Sup Forums, Z80 or 6502?
Other urls found in this thread:
media.ccc.de
pastebin.com
twitter.com
Z80 of course
>So Sup Forums, Z80 or 6502?
Z80 was a better version of a 8080
6502 was literally a retarded 6800
The 6502 had the massive advantage of price.
25 dollars vs 150+ you paid on the 6800 or 8080
6502 was originally intended for use in appliances. Hence the simplified design and scarcity of registers.
However, it overlapped consecutive instructions so processing was streamlined.
OSI, SYM, AIM, and KIM were the first kitsets to use the much cheaper 6502. Then came Apple, CBM and Atari.
The 6800 was a speed devil like the 6502?
Depends on your application. What do you need it for?
6502 cause muh Nintendo.
>(Intel/motorola shitters do not apply)
>Z80
>literary a 8080 improvement
what?
>Z80 was a better version of a 8080
>of a 8080
not THE 8080? but a 8080?
then which 8080?
nintendo also used a z80 clone in the gameboy didn't they
>what is the GB/GBC
Z80, no doubt. Intel tried to copy them and that's what we're stuck with.
I just realized Faggin was the Keller of his time.
They used the Z80 10 years after they used the 6502.
The gameboy don't use a Z80, but more of a 8080 clone with some Z80 instructions, but none of the fun ones like the mass data transfer or second register page.
>Intel tried to copy them and that's what we're stuck with.
What?
Zilog Z80 was an improvement on the Intel 8080, it's team had actual ex-Intel employees behind it.
Intel 8086/88 is what we are "stuck with", it's development started before the Zilog Z80 was even out.
>literally rebdit: the thread
This guy has an extensive overview of the Gameboy CPU: media.ccc.de
Interesting.
I'm actually programming for the gameboy for fun, and i do end bumping into several "the Z80 could do that better".
>15* filename
>calling anyone Reddit
Okay, friendo.
all of my meme pictures were deleted :(
Yeah, I don't know what I was thinking when I wrote that post.
This reminds me of the absurd things GCC 2 did with the N64. Overlong li, branches to delay slots, you name it.
If it works...
This shit is not acceptable
lui at, 0xA430
ori at, 0x0000
and this is just hell
sltiu at, t0, t1
beqlz at, 1f
2:
addiu t1, 1
It's just the N64 mips or it fucks up like this on any MIPS?
not OP but I'm planning on building a z80 computer, anyone have advice? planning on powering it from usb if I can.
Study well the thing, don't forget to decouple the power of all your chips, and enjoy the auto memory refresh if you can.
yeah i've been doing my research (won't even have the time to actually build it for a while anyways). reading Build Your Own Z80 and a lot of build logs mainly.
Then it will most likely be fine, unless you try to make everything on a breadboard and the noise fucks you over.
alright, thanks man. will post about progress when i start
Good luck.
So people prefer a TI-83 (Z80) over a Commodore 64 or a Nintendo NES (6502)?
For me it's the Z80a
Any MIPS, I'd assume, since this was basically straight to binary.
This is the "boot sector" of SM64: pastebin.com
It's hand-compiled, and it's even worse than GCC output. Everything below L00000778 is from an unknown internal SGI library.
Are you sure it is actually worse or "dodging hardware bullets"?