Before porting to Vaxen, we built a 64 concurrent user Forth system using a 68000 and a bunch of 8 port IO cards. Nice chip.
Given that 25 years has elapsed, I can only say I used to be familiar.
Cheers
Computer Science Canada 68k |
| Author: | Epic Tissue [ Tue Jul 08, 2008 5:38 pm ] |
| Post subject: | 68k |
Just wondering, anyone familiar with the 68k? linky |
|
| Author: | btiffin [ Tue Jul 08, 2008 6:04 pm ] |
| Post subject: | RE:68k |
Before porting to Vaxen, we built a 64 concurrent user Forth system using a 68000 and a bunch of 8 port IO cards. Nice chip. Given that 25 years has elapsed, I can only say I used to be familiar.
Cheers |
|
| Author: | md [ Tue Jul 08, 2008 7:57 pm ] |
| Post subject: | RE:68k |
I'm currently taking an assembly language course that uses it. I can say it's interesting... but oh how I prefer RISC (like say... ARM or MIPS) to CISC. |
|
| Author: | jernst [ Tue Jul 08, 2008 8:42 pm ] |
| Post subject: | Re: 68k |
Im still pretty familiar with it, I took a course in it at laurier about two years ago |
|
| Author: | apomb [ Wed Jul 09, 2008 2:34 pm ] |
| Post subject: | Re: 68k |
At my first college program, i took an assembly language course in which i hooked up a logic analyzer and some input/output stuff to one of these chips, here are some pics from that project: 
 |
|
| Author: | silent1mezzo [ Wed Jul 09, 2008 7:29 pm ] |
| Post subject: | RE:68k |
I've taken a couple courses. DOn't remember much but still have the textbook lying around. |
|
| Author: | Epic Tissue [ Wed Jul 09, 2008 8:17 pm ] |
| Post subject: | RE:68k |
Out of interest, what textbook? |
|
| Author: | Tony [ Wed Jul 09, 2008 8:29 pm ] |
| Post subject: | RE:68k |
I wrote an Assember (for MIPS though, not 64K) for one of my courses. So I'm familiar with the very basics of Assembly. Though I doubt I can write anything useful, that is also significantly more optimized than something like gcc could compile for me. |
|
| Author: | rizzix [ Wed Jul 09, 2008 9:16 pm ] |
| Post subject: | RE:68k |
Something that's worthwhile knowing is creating GCC frontends if you're into language design; or creating GCC backends if you're into writing assemblers for hardware. Then just let GCC handle the optimization part for you. |
|