/repo: paste/paste.19994 comparison

comparison paste/paste.19994 @ 728:efefb961267a

<itidus21> pastelogs z80

author	HackBot
date	Tue, 02 Oct 2012 11:00:12 +0000
parents
children

comparison

equal deleted inserted replaced

-:cb9f84a972e1
+:efefb961267a
+2003-10-21.txt:00:59:59: <andreou> calamari_ eh, ticalc question... are they z80 based or 68k-based?
+2003-10-21.txt:01:00:35: <lament> andreou: models up to 86 are z80
+2004-02-11.txt:00:15:57: <mooz-> fizzie; z80 asm...
+2004-05-27.txt:21:54:46: <mooz-> z80 is nice
+2004-05-27.txt:21:56:46: <lament> i dunno about z80 being nice
+2004-05-27.txt:21:57:28: <lament> it would certainly be cool to hack together some custom hardware using a z80 as the brain
+2004-05-27.txt:21:58:03: <fizzie> z80 felt definitely nicer to write for than for example 6502. not that I'd have done much with either.
+2004-05-27.txt:21:58:49: <fizzie> I have seven z80 cpus somewhere here, in case I ever felt like that. 'yleiselektroniikka' sold those for something like 0.50e/piece.
+2004-05-27.txt:21:58:57: <lament> the most i have done in z80 was a program that converted a (hardcoded) number into a string like "three thousand eleven hundred fity one"
+2004-05-27.txt:21:59:43: <fizzie> my biggest z80 program is the md5 algo and OTP-key-calculator.
+2004-05-27.txt:22:00:45: <fizzie> anyway, building custom stuff with a z80 is significantly harder than with pic-like chips. z80 cpu needs external memory and a set of supportive chips.
+2004-05-27.txt:22:02:29: <fizzie> lament; no, but I have the z80 book from zilog somewhere, and after looking at it I indefinitely postponed any z80-based electronic-building-projects.
+2004-05-30.txt:20:47:21: <fizzie> I'd need to write a z80-based-device emulator for the arm/symbian/series60. :p
+2004-07-26.txt:21:52:13: <fizzie> I was supposed to write a symbianos z80-device emulator so that a friend could participate in the 'mobile demo' category, since they've banned calculators now.
+2004-07-26.txt:21:56:26: <fizzie> a 128x64 black-and-white lcd (so slow that you can do greyscale-by-flicker) and a.. was it a 6MHz z80?
+2004-07-26.txt:22:05:39: <fizzie> and the z80 instruction set at least marginally makes sense.
+2004-12-26.txt:12:54:05: <fizzie> (Oh, and the operating system for our "hey, I'll write an emulator for a (zilog-z80-based) hardware device that doesn't actually exist" thing was supposed to use befunge in the startup scripts.)
+2005-03-05.txt:22:02:02: <{^Raven^}> z80 machine code for humans, arm the dabhand guide, 6502 assembly routines (600pages)
+2005-08-17.txt:22:30:45: <pgimeno> then it's pretty much the same as Z80, except the Z80 has some prefixes to extend the instruction set
+2005-08-17.txt:22:31:08: <jix> pgimeno: but z80 has not 16 16bit registers
+2005-08-17.txt:22:31:43: <jix> and the z80 can't use ANY of them as IP
+2005-08-17.txt:22:32:33: <jix> and the z80 isn't in the voyager (satellite )
+2005-08-17.txt:22:52:44: <pgimeno> btw, in Z80 they're jr (relative), jp (absolute)
+2005-08-17.txt:22:53:34: <pgimeno> the Z80 has no SEX but has STI which is an ultra-high level instruction (that's what is left when you take the 'E' out of 'SETI')
+2005-08-17.txt:22:56:26: <pgimeno> in Z80? load, increment
+2005-08-17.txt:22:56:28: <int-e> jix, z80, load index register.
+2005-08-17.txt:23:01:20: <pgimeno> I can still type Z80 code in decimal in DATA lines but I can't remember the damn 486+ instruction set
+2005-08-18.txt:00:46:55: <pgimeno> that's Z80ish too
+2005-08-18.txt:23:25:02: <jix> z80
+2005-09-10.txt:14:03:37: <pgimeno> the ZX Spectrum (a Z80-based micro) took CR as end-of-line too
+2005-12-07.txt:13:57:09: <jix> some z80 game-device
+2005-12-07.txt:13:59:34: <jix> and i know how the z80 works by viewing offical and inoffical z80 documentation
+2005-12-09.txt:20:16:38: <jix> but now i'm writing a z80 emulator
+2005-12-09.txt:20:21:45: <fizzie> I've started to write two z80 emulators already. :p
+2005-12-09.txt:20:22:10: <fizzie> (Neither one got very far - although I think both times I had the z80 cpu part semi-done.)
+2005-12-09.txt:20:24:43: <nooga> i see that z80 is quite popular
+2005-12-09.txt:20:39:20: <fizzie> I used to have a Z80 datasheet/manual here, too. Although as I didn't bother emulating the timing issues, any old opcode list would've been as good.
+2005-12-09.txt:20:40:04: <jix> i use z80-documentated.pdf
+2006-04-30.txt:21:50:35: <int-e> not really. I've seen MIPS (and coded a bit on the strange simulated machine that SPIM provides), and I've done a bit of Z80 assembly ages ago.
+2006-06-05.txt:22:59:07: <jix> <insert some incompatible buggy z80 clone that was only produced once as a prototype> inline assembler in ruby is portable isn't it?
+2006-10-13.txt:23:35:02: <RodgerTheGreat> even better- it's Z80-based, and I have POKE and CALL!
+2006-10-13.txt:23:44:25: <RodgerTheGreat> first: memory map. then, I'll see about the serial interface, and then I'll take a crack at coding a proper BF environment in Z80 asm.
+2006-11-04.txt:01:21:00: <Razor-X> Well, x86 is a lot better than the z80 ASM on TI.
+2006-11-04.txt:01:21:10: <ihope> z80, eh?
+2006-11-23.txt:02:13:12: <GreaseMonkey> erm, i'm familiar with Z80 machine code
+2006-11-23.txt:19:55:09: <GreaseMonkey> however, in Z80 ASM: PUSH hl; PUSH af; POP hl; LD l,00h; PUSH hl; POP af; POP hl;
+2006-12-24.txt:00:19:02: <fizzie> http://juho.vaha-herttua.fi/Zilog.Z8000.1979.102646293.pdf
+2006-12-24.txt:00:25:55: <fizzie> Well, it's a little white lie. At least according to my reading of the Z8000 specification book.
+2007-02-26.txt:02:29:10: <fizzie> >>> 'ABC' < 'C' < 'Pascal' < 'Python' < 'Scheme' < 'Zilog Z80 assembler'
+2007-03-31.txt:04:14:46: <Figs> Z80?
+2007-03-31.txt:04:21:56: <Figs> http://en.wikipedia.org/wiki/Z80#Instruction_set_and_encoding
+2007-09-10.txt:17:23:05: <fizzie> Well, you can write z80 assembler for it; there's no need to use the silly TI-BASIC.
+2007-11-03.txt:01:42:55: <cpressey> if cheap, i'd go with a Z80 cpu and maybe wire it up after i've had a few, to make it interesting
+2008-02-07.txt:01:38:56: <ehird`> olsner: z80
+2008-11-13.txt:01:58:52: -!- z8000_ has joined #esoteric.
+2008-11-13.txt:01:59:11: -!- z8000_ has parted #esoteric (?).
+2009-01-11.txt:16:21:44: <fizzie> Z80 instruction set calls it "DAA" (decimal adjust accumulator) which makes more sensity.
+2009-03-05.txt:17:28:38: <impomatic> I prefer Z80
+2009-03-05.txt:17:33:08: <impomatic> I have about 40 old computers lying around. Several Z80 computer (z80, amstrad, msx) a few 6502, 6809 machines, one 8085 and others I haven't got a clue about.
+2009-03-06.txt:13:54:50: <fizzie> ineiros: Hmm, maybe? I don't have a screenshot of it, just the z80 source code where the picture is given with .db pseudo-instructions.
+2009-03-13.txt:23:47:20: <comex> you have to type in z80 opcodes as hex
+2009-03-13.txt:23:47:53: <comex> I have a packet with a list of z80 opcodes
+2009-03-15.txt:23:35:10: <fizzie> I requested Zilog's Z80 databook once, in a physical format; and it was actually pretty useful when writing some TI-86 code. I gave it away as a gift, though.
+2009-04-08.txt:22:11:29: <fizzie> MY C128 HAS A DUAL-CPU MOS-8502/ZILOG-Z80 ARCHITECTURE WITH A TURBO MODE OF 2 MEGAHERTZ AVAILABLE IF YOU DON'T MIND THE FACT THAT THE VIDEO CHIPSET DOESN'T RUN THAT FAST
+2009-04-09.txt:21:17:26: <fizzie> Z80 has even more BCD instructions, and they're very much used by the TI calculators, since the TI float format is a BCD one.
+2009-05-12.txt:20:14:05: <fizzie> Z80 gpg-error.h has "GPG_ERR_EIEIO = GPG_ERR_SYSTEM_ERROR | 44"; I'm not quite sure what it's used for.
+2009-05-12.txt:20:14:24: <fizzie> Er, not Z80 gpg-error.h; the usual gpg-error.h
+2009-05-13.txt:23:02:23: <fizzie> And speaking of SMP, the C128 *also* has a 2 MHz Z80 processor (for CP/M mode)... though for hardwarey reasons you can't run the 8502 (6510 + the 2 MHz mode) and the Z80 simultaneously.
+2009-05-13.txt:23:04:01: <fizzie> "A possibly unique feature of the C128 among CP/M systems was that some of the low-level BIOS services were executed by the 8502 chip instead of the Z80. The latter transferred control to the 8502 after having placed the pertinent parameter values in designated memory locations. The Z80 then turned itself off, being awoken by the 8502 at completion of the BIOS routine, with status value(s) available in RAM for inspection." Heh, freaky.
+2009-05-13.txt:23:04:23: <pikhq> A Z80 and an ARM7.
+2009-05-13.txt:23:05:09: <fizzie> Too bad they dropped GB compatibility from the DS; it would've had ARM9+ARM7+Z80 then.
+2009-05-19.txt:20:35:09: <ehird> http://upload.wikimedia.org/wikipedia/commons/d/d1/Computerplatine_Wire-wrap_backplane_detail_Z80_Doppel-Europa-Format_1977.jpg
+2009-09-12.txt:10:48:22: <fizzie> Deewiant: Yes, well, modern architectures are confusing. I was talking more about 6502 and z80 assembly, where you can just count cycles, and everything's very obvious.
+2009-09-25.txt:13:00:43: <fizzie> Personally I rather like Z80 more. At least it does 16-bit operations natively (you can pair up some of the 8-bit registers), and it's got a lot more registers; A, B, C, D, E, H, L compared to A, X, Y in the 6502.
+2009-09-25.txt:13:02:15: <fizzie> The Z80 was there mostly for CP/M compatibility.
+2009-09-25.txt:13:02:17: <ehird> c64 demos run on the 6502, OS code runs on the Z80 watching it...
+2009-09-25.txt:13:08:12: <fizzie> Sharing the memory bus with the VIC-II already halves the (theoretically 4 MHz) clock speed of the Z80; people did complain about the CP/M running slowly because of that.
+2009-09-25.txt:13:09:58: <fizzie> A 2 MHz Z80 is (according to a rough estimate) equivalent to a 0.5 MHz 8502 (the 6502 clone in C128), since the latter does some pipelining.
+2009-09-25.txt:13:10:18: <fizzie> "Because of the pipelined architecture of the 8502, a 1 MHz 8502 is approximately comparable in speed with a 4 MHz Z80. However, on the C128, the Z80 only runs at 4 MHz half the time giving an effective clock speed of 2 MHz. This means that the Z80 is only about half as fast as the 8502 (only about a fourth as fast when the 8502 is in 2 MHz mode)."
+2009-09-25.txt:13:12:06: <fizzie> Some of the C128 BIOS routines run on the 8502 even in CP/M mode; the Z80 writes arguments to some predefined memory location, wakes up the 8502 and halts; then the 8502 does the work, writes return values to memory, and wakes up the Z80 again.
+2009-09-25.txt:13:16:36: <fizzie> With no memory protection, shared interrupts with no routing, it will probably shit all over everything in any case, even if you could get the Z80 running too. (And the bus cycles lost to the Z80 would probably mess up all timing-related stuff in the demo.)
+2009-09-25.txt:13:18:18: <fizzie> Still, while you're doing to necessary hardware hacking to get both CPUs running, you could add a kilobyte or so of Z80-only RAM and some sort of programmable logic chip to route interrupt lines; using that (and the C128 memory banking C64 demos probably don't expect) you might even get something done.
+2009-10-01.txt:20:38:04: <impomatic> There's a 25MHz Z80 upgrade available for the Speccy, and a 4MB memory board
+2009-10-01.txt:20:41:20: <ehird> The C64 with 64KiB can run a full graphical multitasking OS with a web browser (Contiki), and it only has a 1.02MHz 6510 (or 0.985MHz in PAL regions), so I'm sure a Z80 at 3.5MHz with 48KiB of RAM can handle it.
+2009-10-07.txt:20:45:13: <fizzie> I don't suppose any of those methods would create something I could easily extract specific bytes from, with the added restrictions that (1) they shouldn't really use more than a kilobyte or two of working memory, (2) the code shouldn't take much more space than my 150-byte deflate decoder, and (3) it would be something I could cobble together with my very shaky z80 asm skills in a day or two?
+2009-10-07.txt:23:49:12: <fizzie> What I like about LZ77 is that it pretty elegantly includes also run-length-encoding as a special case (with a length > 1 and distance = 1 pair); that makes a difference because I got bored of Z80 assembly and did line-wrapping with Perl, padding things with spaces so that they wrap properly in the message area.
+2009-10-17.txt:03:16:11: <zzo38> One day, in order to learn how to build a computer, I will try to make a computer with z80-based, and a On-Screen-Display chip, a few buttons on the front, keyboard connect, audio, and external memory.
+2009-10-17.txt:04:39:14: <Warrigal> TI graphing calculators use z80-type processors, don't they?
+2009-10-23.txt:07:18:19: <zzo38> I have written Forth systems, I can probably do it with assembly language or machine-codes, too. Which is, I do plan to do so one day, to build a simple computer with Z80 and Forth, and a OSD chip.
+2009-11-01.txt:05:10:51: <madbrain> like, afaik, one reason the z80 was popular was that it handled ram refresh for you
+2010-02-11.txt:22:24:13: <fizzie> I'm sure 6502 isn't the only one who calls it that; the corresponding register is called PC for Z80 too, for example.
+2010-02-25.txt:06:28:48: <amca> I think I have a TI84 which was an upgrade to the TI83 and runs on a z80
+2010-03-26.txt:22:32:40: <AnMaster> while the other are Z80
+2010-04-21.txt:11:01:36: <fizzie> Rugxulo: Do you know of the TI-86 calculator one that's done in z80 assembly? It's very nice; has a debugger and all if I recall correctly.
+2010-05-09.txt:17:07:57: <alise> I was personally thinking Z80, since I've never seen or written Z80 code, seems interesting; but perhaps a bit too low powered.
+2010-05-09.txt:17:09:29: <alise> z80 is post-8088
+2010-05-09.txt:17:11:23: <nooga> + you're wrong alise: 8088 was released in 79 and Z80 was 8080 compatible processor introdouced in 76
+2010-05-15.txt:03:04:53: <gm|lap> yay z80 still rocks
+2010-05-15.txt:03:07:16: <gm|lap> not a z80 entry in sight :/
+2010-06-17.txt:21:38:19: <cpressey> Phantom_Hoover: Speaking of processors, remember that thing about RAM not being zero'ed on startup, we talked about yesterday?  Well, a similar thing applies to CPU's.  If you turn on power to a chip like a Z80 "too quickly", it starts up in a random, confused state...
+2010-06-20.txt:23:19:09: <fizzie> I've always felt the -89's use of a 68k processor (instead of the Z80) somehow cheatingy.
+2010-06-24.txt:22:16:05: <fizzie> cpressey: Speaking of multicore-6502's, would you classify the C128 as a dual-processor computer? It's got the 8502 (a 6510-derivative) and the Z80 both, but only one of them can be active at a time.
+2010-06-27.txt:10:54:33: <fizzie> Getting back to the 6502 thread, I seem to recall that TI made a beefed-up Z80 model quasi-recently.
+2010-06-27.txt:10:56:22: <fizzie> "The eZ80 (like the Z380) is binary compatible with the Z80 and Z180, but almost four times as fast as the original Z80 chip at the same clock frequency. Available at up to 50 MHz[1]  (2004), the performance is comparable to a Z80 clocked at 200 MHz if fast memory is used --"
+2010-07-26.txt:17:21:42: <fizzie> Every environment seems to have its own way of denoting numbers, anyway. Z80 assemblers (and many others like that) use $f00 as a hex prefix, and #01101 for binary-number prefix.
+2010-08-10.txt:13:01:59: <fizzie> I'm not sure what Z80 is; the general-purpose regs are 8-bit (A, B, C, D, E, H, L), but the instruction set also has some (but not as many as 8-bit) 16-bit arithmetic opcodes that treat the registers as pairs BC, DE, HL. And the memory-indexing registers IX and IY are 16-bit only (unless you count undocumented opcodes), as are addresses.
+2010-08-10.txt:13:03:00: <fizzie> Wikipedia categorizes Z80 as "an 8-bit microprocessor", still.
+2010-08-10.txt:13:07:06: <fizzie> That's a bit vague too, and you could start arguing the Z80 as a 16-bit CPU on that basis.
+2010-08-10.txt:13:31:38: <fizzie> There's also the 16-bit Z80 thing, but only if you want to put Z80 into the 8-bit camp. (I guess most people would put it there, though.)
+2010-08-10.txt:13:32:09: <Phantom_Hoover> How does the Z80 do 16-bit stuff
+2010-08-10.txt:13:49:22: <fizzie> Aaaanyway, back to the original issue, something I was going to add: Z80 also does 16-bit memory loads and stores to/from the register pairs, and the stack ops (push, pop) only work with 16-bit quantities.
+2010-08-10.txt:13:52:11: <fizzie> Right, well, in that sense Z80 would be a badly limited sort of 16-bit CPU.
+2010-08-31.txt:19:39:31: <cpressey> alise: Well, depends on the arch, I suppose.  6502 > Z80 > Forth > 68000, maybe.
+2010-08-31.txt:19:39:51: <cpressey> Actually, I don't know about Z80.  Never got into it much.
+2010-09-04.txt:19:59:54: <alise> No. ARM and Z80 don't tell you what the computer should look like either.
+2010-09-05.txt:21:49:56: <madbrain2> something like the z80 that has 8bit data bus with 16bit address registers
+2010-09-05.txt:21:53:32: <madbrain2> so mostly x86, looked a bit at ARM, z80...
+2010-09-05.txt:21:54:10: <cpressey> Z80 is a great piece of hardware (easy to build a computer around) but I really don't like the instruction set.
+2010-09-05.txt:21:56:34: <fizzie> cpressey: Z80 feels a bit arbitrary to me. But I can't help liking the register pairing to form BC, DE, HL out of B, C, D, E, H, L.
+2010-10-29.txt:23:02:35: <fizzie> I write 0xf00 in nasm, $f00 in z80asm/ca65 and "10h" for the x86 "int 10h" instruction, nowhere else.
+2010-11-01.txt:23:37:08: <cpressey> I once designed a protected memory system for the Z80 (in hardware)
+2010-11-01.txt:23:41:12: <cpressey> elliott: yes.  also considering there is an "enhanced Z80" out there somewhere which basically does all this in a chip :)
+2010-11-02.txt:00:13:05: <cpressey> (the "Enhanced Z80", ftr, is: http://en.wikipedia.org/wiki/Zilog_Z80000)
+2010-11-02.txt:00:13:47: <cpressey> Hm, not Z80-compatible, though.
+2010-11-02.txt:00:14:03: <fizzie> There's the eZ80, too.
+2010-11-02.txt:00:28:14: <cpressey> Unlike the Z80,000, I can actually find units of Z180 for sale.
+2011-01-04.txt:01:40:58: <pikhq> (16 MHz ARM, 4/8 MHz GB-Z80, *no fucking crazy PPU*, and NO SPECIAL CHIPS. AT ALL.)
+2011-01-04.txt:01:53:26: <pikhq> The GBA uses the GB-Z80 for some sound effects.
+2011-01-04.txt:01:56:22: <pikhq> Also a GB-Z80!
+2011-01-04.txt:02:24:10: <pikhq> cheater99: And the Gameboy is "just" an ARM7 and a GB-Z80.
+2011-01-04.txt:02:24:30: <pikhq> The Gameboy is just a GB-Z80.
+2011-02-05.txt:03:44:01: <Tabarnaco> hey guys how about that z80 assembly~~~~~~
+2011-02-05.txt:03:49:48: <elliott> Tabarnaco: Isn't Z80 relatively *non*-esoteric as CPU architectures go? :)
+2011-02-05.txt:03:50:02: <Tabarnaco> as far as i know there's no assembly or z80 channel
+2011-02-05.txt:03:50:27: <elliott> There's almost certainly some kind of assembly channel; Z80 maybe not on freenode but definitely elsewhere.
+2011-02-05.txt:03:50:47: <Tabarnaco> well i checked z80 and it doesn't exist so i don't want to browse through the list of channels
+2011-02-05.txt:03:56:23: <elliott> Tabarnaco: well I don't know Z80, so I'm going back to my Haskell :P
+2011-02-05.txt:04:00:40: <Tabarnaco> well since nobody seems to know z80 assembly in the first place i don't see the point of it...
+2011-02-06.txt:21:53:34: -!- impomatic has quit (Quit: http://shiar.nl/calc/z80/optimize).
+2011-02-07.txt:06:50:06: <quintopia> z80 also seems to result in small bytecodes for a lot of things :P
+2011-02-12.txt:16:53:36: <fizzie> Z80 binaries, since that seems to be the thing people spend large amount of time golfing, too.
+2011-03-13.txt:18:41:13: -!- iconmaster has quit (Quit: installing a z80 emulator.... My FAV ML!).
+2011-03-13.txt:18:45:03: <elliott> Yes. Z80 is a dialect of ML.
+2011-03-13.txt:18:45:04: <ais523> well, ML and z80 machine language are both pretty clean languages
+2011-03-22.txt:04:30:22: <pikhq> Say, a z80.
+2011-03-22.txt:04:31:19: <Gregor> Does that matter? The Z80 isn't more /stable/ than, say, a commodity x86, and you can never replace the processor anyway.
+2011-03-31.txt:11:24:54: <impomatic> Not possible with 8086.  Maybe with Z80.
+2011-05-24.txt:08:58:24: <zzo38> In fact, sometimes vi or z80 is the shortest solution, shorter than the GolfScript and FlogScript codes.
+2011-05-24.txt:08:58:33: <Patashu> isn't z80 assembly?
+2011-06-11.txt:18:54:58: <zzo38> 0x00 is NOP in z80, though, I think.
+2011-06-11.txt:18:58:52: <twice11> Isn't on Z80 the typical NOP encoding one of 0x40/0x49/0x52/0x5B/0x64/0x6D/0x76/0x7F?
+2011-06-11.txt:18:59:14: <elliott> Z80, hoggin' all the nops
+2011-06-11.txt:18:59:44: <twice11> Those are LD A,A; LD B,B and so on Z80
+2011-07-09.txt:06:14:33: <fizzie> And Z80 has a rather silly nybble-rotating operation, RRD. I think it might be intended for doing things on BCD values.
+2011-08-15.txt:20:43:08: <fizzie> I once requested the Z80 CPU datasheets from Zilog, and they mailed those all the way to Finland for free. It was a heartwarming gesture. Especially since I didn't really-really need those for anything. (Half of the book is just timing diagrams.)
+2011-08-21.txt:14:05:06: <fizzie> One 6502-or-Z80-I-forget-which C compiler supported an 8-bit float format, I think.
+2011-09-26.txt:10:07:25: <fizzie> For some reason I have a terrible urge to write something in assenbler; maybe for Z80 or x86-realmode or ARM or something. On the other hand, I'd really like to write something practical that I'd have a real use for, too. These two goals are not proving to be very easily combined.
+2011-11-12.txt:23:25:55: <QuickDirtyOS> Z80 was similar, but not as simple as 8080
+2011-11-12.txt:23:36:15: <QuickDirtyOS> actually Z80 is very mainstream (my bad luck?)
+2011-11-17.txt:05:15:55: <elliott> Gregor: Z80?
+2011-11-17.txt:05:16:24: <elliott> Gregor: But yeah, Z80 is a good 'un.
+2011-11-17.txt:05:17:02: <elliott> Gregor: Z80 has 32-bit addressing, I'm pretty sure.
+2011-11-17.txt:05:18:01: <elliott> Gregor: SIMH emulates a Z80: "SIMH emulates MITS Altair 8800 computer with Intel 8080, Zilog Z80 or Intel 8086 processors."
+2011-11-17.txt:14:42:35: <fizzie> How about z80? I think TI still makes e.g. the TI-84+ calculator based on that, so it's not "really old". Of course it's not 32-bit, and the computerness is arguable.
+2011-11-17.txt:14:43:05: <elliott> fizzie: I told Gregor Z80, he said waaah address space.
+2011-11-17.txt:14:43:38: <fizzie> Z80 address space is 64K though.
+2011-11-17.txt:14:43:46: <fizzie> eZ80 goes up to 16M.
+2011-11-17.txt:14:45:51: <elliott> So eZ80 will work!
+2011-11-17.txt:14:47:32: <fizzie> I'm not sure what C compilers there are for eZ80, though, other than Zilog's own best-name-ever "eZ80ZDS0100ZCC" compiler.
+2011-11-17.txt:14:47:52: <elliott> eZ80ZDS0100ZCC might just be the best name for a compiler, ever.
+2011-11-17.txt:14:48:17: <elliott> fizzie: HOW IS IT ACTUALLY CALLED eZ80ZDS0100ZCC
+2011-11-17.txt:14:49:24: <elliott> <fizzie> I'm not sure what C compilers there are for eZ80, though, other than Zilog's own best-name-ever "eZ80ZDS0100ZCC" compiler.
+2011-11-17.txt:14:50:04: <fizzie> Admittedly the prose only refers to it as "eZ80 C-Compiler", but that's more of a description than a name. I guess it's a matter of semantics.
+2011-11-17.txt:14:51:06: <elliott> "Oh, little old eZ80ZDS0100ZCC's broken again..."
+2011-12-10.txt:03:47:55: <Deathly> z80?
+2011-12-10.txt:03:48:22: <zzo38> I have written a GameBoy game once, it is similar to Z80 but not quite
+2012-01-28.txt:21:25:21: <fizzie> There's a quasi-popular/simple "install a switch that overclocks the Z80 from 6 MHz to K MHz" mod for the 86. (I don't quite recall what K is; and it eats batteries faster + not all things work right when overclocked.)
+2012-06-29.txt:12:40:33: <fizzie> The Z80 does not exactly have an FPU. And those cost big bucks.
+2012-06-29.txt:19:37:24: <fizzie> Hey, I have another piece of trivia that I recently came across again. Z80 has the usual arithmetic left shift (SLA, shifts zeroes in), arithmetic right shift (SRA, duplicates the sign bit) and logical right shift (SRL, shifts zeroes in again) instructions. *But*, if you look at the opcodes, there's a hole in where you'd logically have SLL, the logical left shift. And if you go and use it, ...
+2012-07-07.txt:00:49:20: <adu> but if you need some z80 docs, I think I have some backups of a webcrawl about 10 years ago
+2012-07-07.txt:00:49:33: <soundnfury> adu: nah, I've got all the z80 knowledge I need...
+2012-07-09.txt:08:27:09: <fizzie> Could be a slightly different busy loop on ARM. Modern processors are so weird anyway, you can't just sum up cycles/instruction like you mostly could on, say, a Z80.
+2012-07-09.txt:20:24:46: <soundnfury> next time someone posts a Haskell code snippet, I'll post some Z80 m/c
+2012-07-09.txt:20:25:05: <zzo38> OK post some Z80 m/c if you have something to write about it
+2012-07-10.txt:00:10:56: <zzo38> soundnfury: You said you are going to post a Z80 code if someone posts a Haskell code in here? (Or, something like that)
+2012-07-10.txt:00:13:59: <zzo38> Is this Z80 code a part of some program? And, what is LDIR for?
+2012-07-10.txt:00:14:30: <soundnfury> That Z80 code will fill all of RAM with the value in the Accumulator (A)
+2012-07-10.txt:00:17:27: <zzo38> I have once wrote a program for GameBoy, which is not Z80 although it is similar to Z80.
+2012-07-10.txt:00:21:47: <soundnfury> The hardest Z80 opcode to emulate is probably DAA
+2012-07-10.txt:08:46:42: <fizzie> I'll propose the C128 as a compromise, it has a Z80 in it too. :p
+2012-07-10.txt:08:48:55: <itidus21> one time i was poking around in some store, and for a few $ each i got a book about 8085 and a book about z80 next to each other
+2012-07-12.txt:09:07:52: <soundnfury> nortti: I'm afraid I was asleep when you asked your question last night.  The answer is Z80 asm.
+2012-07-12.txt:10:19:32: <soundnfury> then I'll reimplement it into Z80
+2012-07-13.txt:01:51:49: <soundnfury> I think for low-end applications the Z80 still gets used as a microcontroller
+2012-07-15.txt:05:23:27: <zzo38> Can you include Z80 or 6502 codes?
+2012-07-23.txt:13:38:07: * soundnfury 's favourite chip is Z80
+2012-07-23.txt:13:39:04: <AnotherTest> TI83 has a Z80 processor I think
+2012-07-23.txt:13:39:53: <soundnfury> the Z80 does not have onboard memory (except for general purpose registers) - it's a CPU, not a microcontroller
+2012-07-23.txt:13:41:12: <nortti> soundnfury: are there any new z80 processors produced?
+2012-07-23.txt:13:43:11: <nortti> oh. well that sounds good. I might build computer around z80
+2012-07-23.txt:13:44:05: <soundnfury> there also exist, btw, binary-compatible updated versions, the Z380 and eZ80
+2012-07-23.txt:13:44:28: <fizzie> The eZ80 is fancily kinda-sorta 24-bit.
+2012-07-23.txt:13:46:08: <soundnfury> Vorpal: the R register (8 bits) can be set with LD R,A.  On every opcode fetch, while the instruction is being decoded, the Z80 pulls /MREQ and /RFSH low (but not /RD or /WR), places {I,R} on the address bus, and increments R (except that the high bit of R is not changed)
+2012-07-23.txt:13:51:19: <soundnfury> Vorpal: a new Z80 is typically clocked at 20MHz these days
+2012-07-23.txt:13:55:31: <Vorpal> so Z80 is almost 40 years old then
+2012-07-23.txt:13:56:48: <Phantom_Hoover> You haven't heard of the Z80?
+2012-07-23.txt:13:57:29: <fizzie> "ZiLOG Application Notes are available describing how the Z80 CPU is interfaced with most popular dynamic RAM", to quote the manual. You could look at those.
+2012-07-24.txt:21:08:06: <zzo38> Can they make a patch to compile Haskell codes to: MMIX, Z-machine, Glulx, Java, Z80, Famicom, brainfuck, CLC-INTERCAL, Csound, and hardware.
+2012-08-04.txt:21:01:45: <impomatic> FreeFull: I haven't implemented an interpreter yet.  There are a online in Pascal, C and Z80 asm.
+2012-08-15.txt:09:59:48: <fizzie> But I suppose no GBA-native game actually used the Z80 for anything? I don't know.
+2012-09-09.txt:05:38:39: <soundnfury> heh, the Z80 doesn't have a decimal mode.  It just has N and H flags and a magic "DAA" instruction
+2012-09-15.txt:02:12:55: <madbr> 86 is kinda half way between a z80 and an ARM
+2012-10-02.txt:10:47:05: <barts> has anyone here tried programming the Z80 or one of its derivatives?
+2012-10-02.txt:10:59:04: <itidus21> `pastelogs z80
+2012-10-02.txt:11:00:02: <itidus21> `pastelogs z80

Mercurial > repo

comparison paste/paste.19994 @ 728:efefb961267a