From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3619b2e2178d7152 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-13 05:46:34 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!uunet!psinntp!ss3!ss5!mjmeie From: mjmeie@ss5.magec.com (Mike Meier) Subject: Re: Seeking RS232/422 Implementations/Help Message-ID: Sender: usenet@ss3.magec.com Nntp-Posting-Host: ss5 Organization: Magnavox Electronics Systems Company X-Newsreader: TIN [version 1.2 PL2] References: <3jq9oi$rr7@esdmaster.dsd.northrop.com> Distribution: usa Date: Mon, 13 Mar 1995 12:59:55 GMT Date: 1995-03-13T12:59:55+00:00 List-Id: Hartsough Michael J. (hartsoug@ss22.dsd.northrop.com) wrote: : I need to implement interfaces to RS232, RS422, and 1553B buses (in Ada). Device drivers are heavily dependent on: - The hardware device being used (register structures and automated capabilities vary greatly) - The hardware environment (influences decision on polled vs. interrupt driven) - The protocol (little variation for RS232/422, but varies greatly for 1553B (e.g., various schemes for single BC, multiple BCs) - Other nuances One set of software cannot be reused without knowing many of these details. Even with a simple RS-232 interface I've had to rewrite completely when going from a Motorola to an Intel device. Perhaps you can specify more so that we can think about helping...