At 15:00 7/10/99 +0100, you wrote:
I would therefore like some pointers to texts that would give me an answer
to the following questions:
What type of API is the application code going to use? Is the UNIX system
API any use at all?
What about POSIX 1003.1b and 1003.1c ? It's supposed to be
Hi,
Recently I have become much more interested in the possibility of running
ELKS on actual embedded systems, rather than a Linux for old PCs. I have
no plans for cutting down development of Linux-8086, but would like to add
options to the kernel config to make it possible to build a system
Can anyone tell me where I can get hold of a cheap SBC with
an x86 CPU,
EPROM, RAM and a serial interface at least on?
Cheap is relative. I think cheap would be like $50 for an SBC, but I
can't find any that cheap. Currently, I'm teaching myself some of the
grounding for creating my
Alistair Riddoch wrote:
Hi,
Recently I have become much more interested in the possibility of running
ELKS on actual embedded systems, rather than a Linux for old PCs. I have
no plans for cutting down development of Linux-8086, but would like to add
options to the kernel config to make
I'm no expert here, but following are my $.02:
: What sort of features are required for this type of system? It seems to me
: that a filesystem is not all that important with no storage. Are device
: drivers, interrupt handling and memory management the types of features
: required?
On 07-Oct-99 Alistair Riddoch wrote:
I would therefore like some pointers to texts that would give me an answer
to the following questions:
I can tell what we use in our own propietary OS.
What sort of features are required for this type of system? It seems to me
that a filesystem is not
Al:
My product (a fiber-optic multiplexer) uses a 10 MHz 80186 with
1 MB RAM and 1 MB EPROM (half disabled). There are a few other
system components -- 3 SCCs (Zilog's 2-channel "Serial
Communications Controllers" -- a few ports have RS-232), one 8256
multifunction chip (which also has an
