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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,fd3c44bd8f938354
X-Google-Attributes: gid103376,public
From: tmoran@bix.com
Subject: Re: Parallel port
Date: 2000/03/06
Message-ID: <FITw4.4090$w9.85382@news.pacbell.net>#1/1
X-Deja-AN: 593927809
References: <8a0gkf$pv8$1@nnrp1.deja.com>
X-Complaints-To: abuse@pacbell.net
X-Trace: news.pacbell.net 952371109 206.170.2.164 (Mon,
 06 Mar 2000 11:31:49 PST)
Organization: SBC Internet Services
NNTP-Posting-Date: Mon, 06 Mar 2000 11:31:49 PST
Newsgroups: comp.lang.ada
Date: 2000-03-06T00:00:00+00:00
List-Id: <comp.lang.ada>

>This is really an OS question, not an Ada question.
  Agreed that Microsoft's latest computers don't allow such access
by user programs directly to the underlying Intel computers.  But
even if the program does have such access, the relevant IO ports
would be in the IO address space, not the memory address space.  So
  for Reg_1'address use To_Address(16#378#);
will do the wrong thing.  Something like
  Vendor_Specific_IO_Library.Output(port=>16#378#, data=>data_value);
would be necessary instead.