home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.dcom.lans.misc:715 comp.realtime:1039
- Path: sparky!uunet!nevada.edu!jimi!equinox!pyramid!essary
- From: essary@pyramid.unr.edu (Bill Essary)
- Newsgroups: comp.dcom.lans.misc,comp.realtime
- Subject: Arcnet for an Embedded system
- Keywords: arcnet
- Message-ID: <4403@equinox.unr.edu>
- Date: 3 Sep 92 05:56:37 GMT
- References: <gregh.714841186@cserver> <#ncnf7=@quantum.on.ca> <8ycnr9+@quantum.on.ca> <1992Aug27.210159.20200@sbcs.sunysb.edu>
- Sender: news@equinox.unr.edu
- Reply-To: essary@pyramid.unr.edu (Bill Essary)
- Followup-To: comp.dcom.lans.misc
- Organization: University of Nevada, Reno
- Lines: 14
-
- >In article <#ncnf7=@quantum.on.ca> danh@quantum.on.ca (Dan Hildebrand)
- >writes:
- >>Why not drop an Arcnet chip onto your embedded system ? The component cost
- >>is very low ...
-
- We have just settled on Arcnet for our system (386, 8050 and Siemens 166
- processor mix. Has anyone seen an OSI type (well defined physical, network
- and transport layer) protocol stack written to a small realtime kernel
- interface? We have an in-house kernel and would love to port rather
- than write the network. Actually, writing the network would be fun,
- but... time.
-
-
- Bill Essary
-