From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: Chad Page <cpage@silcom.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: Future of ELKS
Date: Sat, 29 May 2004 12:58:37 -0400 [thread overview]
Message-ID: <00af01c4459e$304516c0$6401a8c0@who5> (raw)
In-Reply-To: Pine.GSO.3.96.1040520203121.26300A-100000@beach.silcom.com
Hello from Gregg C Levine
Nice to see this list is still alive and kicking.
First off all, the 6502 processor is still alive and sqawking. I won't quote
the site name for it, since it will be given later in the thread.
And second, what's the satus of the ELKS code stored on the PlanetMirror
mirror? Or for that matter somewhere on the MIT server? Or even the Germany
Linux Labs site?
But a question does hit me, Chad, if your the same person who's early work
was last seen on the MIT server, what is the status of it? This is the not
really Linux, and certainly not ELKS stuff, from the period that started
when Linus started Linux.
Gregg C Levine obiwanthejediknight atsign att dot net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "Chad Page" <cpage@silcom.com>
To: "Stefan de Konink" <skinkie@xs4all.nl>
Cc: "David Given" <dg@cowlark.com>; <linux-8086@vger.kernel.org>
Sent: Thursday, May 20, 2004 11:39 PM
Subject: Re: Future of ELKS
>
> On Fri, 21 May 2004, Stefan de Konink wrote:
>
> > > > Hey, someone know if a 8086 is fast enough run emulators for those
old
> > > > 8-bit game consoles? 8)
> > >
> > > Nah. A 4.77MHz 8086 does not get a lot of work done. Say you want to
> > > emulate a 2MHz 6502, such as the BBC Micro... this means you have
about
> > > two and a half cycles to emulate each 6502 cycle. Just not possible.
>
> Yup... the memory access speed is *much* slower for instance.
> When I was working on ELKS little tweaks which wouldn't be noticable on
> even the Pentiums of the day - let alone today's HW - were *very*
> noticable on the PC.
>
> > Totally offtopic but I would like to know it. What if an entiere program
> > gets preprocessed, lets say optimized to run on a 8086. So a program
reads
> > binary, disassembles, rewrites to 8086 code, reassembles and run.
> > Or am I talking garbage :S (I thought emulators did a JIT thing...)
>
> qemu does that on the fly - it usually outputs about 10
> instructions per emulated one, in my experience. J. Meyer has stated that
> an 2ghz Athlon 64 runs at about the speed of a 200mhz ppc in qemu, for
> example. Might be possible to get a better code ratio against an 8-bit
> system - Intel had direct code converters from 8080 code, but even then it
> might be tricky. But you would also have to emulate the graphics
> hardware, which challenges faster systems quite a bit!
>
> It'd be interesting to emulate a high-density p-code system on an
> 8086 to fit more code into ELKS, but it'd likely be too slow in practical
> use.
>
> - Chad
>
> > Btw. If a mirror of the hacked elks code is needed, please give a shout.
> >
> >
> > Stefan
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-05-29 16:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 20:55 Future of ELKS Miguel Bolanos
2004-05-20 3:39 ` I'm in Void
2004-05-20 14:47 ` Miguel Bolanos
2004-05-20 11:42 ` Javier Sedano
2004-05-20 15:15 ` Miguel Bolanos
2004-05-20 15:37 ` Eduardo Pereira Habkost
2004-05-20 16:06 ` Andrey Romanenko
2004-05-21 5:51 ` Dan Olson
2004-05-20 17:30 ` Javier Sedano
2004-05-21 8:32 ` Gábor Lénárt
2004-05-21 14:15 ` Jody
2004-05-24 9:29 ` Gábor Lénárt
2004-05-24 18:20 ` Alan Cox
2004-05-20 23:43 ` David Given
2004-05-21 1:04 ` Stefan de Konink
2004-05-21 3:39 ` Chad Page
2004-05-29 16:58 ` Gregg C Levine [this message]
2004-05-21 5:55 ` Dan Olson
2004-05-21 6:08 ` Jody
2004-05-21 13:24 ` Eduardo Pereira Habkost
2004-05-21 16:30 ` David Given
2004-05-21 16:59 ` Michael McConnell
2004-05-22 12:12 ` David Given
2004-05-22 17:29 ` Chad Page
2004-05-21 18:38 ` Jody
2004-05-22 8:53 ` jb1
2004-05-22 17:00 ` Chad Page
2004-05-24 9:42 ` Gábor Lénárt
2004-05-20 16:54 ` Javier Sedano
2004-05-21 5:50 ` Dan Olson
2004-05-21 9:08 ` Arnaldo Carvalho de Melo
2004-05-21 10:24 ` Alan Cox
2004-05-24 12:20 ` Gábor Lénárt
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:40 Pat Gilliland
2004-05-21 17:53 ` Miguel Bolanos
2004-05-20 20:18 Tommy McCabe
2004-05-24 13:17 BODRATO Stefano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00af01c4459e$304516c0$6401a8c0@who5' \
--to=obiwanthejediknight@worldnet.att.net \
--cc=cpage@silcom.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox