[Info-vax] VMS terminal port/class doc... no it's not...

[VAXman- at SendSpamHere.ORG]

In article <4ce33fc5$0$2163$c3e8da3$9deca2c3 at news.astraweb.com>, JF Mezei <jfmezei.spamnot at vaxination.ca> writes:
>VAXman- @SendSpamHere.ORG wrote:
>>   The interface for terminal class drivers on OpenVMS I64 is a call-based
>>   interface. This is a significant difference from the JSB-based interface
>>   on OpenVMS Alpha that uses registers to pass arguments. 

Don't read too much into my query.



>It was explained to be that for that IA64 thing, VMS engineering decided
>to use an Intel provided image header format to allow the re-use of
>linker code provided by Intel.

VMS device drivers are still VMS device drivers.



>Does this mean that a rework of drivers for IA64 was done in the same
>spirit to allow easier re-use of driver code provided by Intel and/or
>Microsoft for various devices ?

No!



>Or was the difference in system architecture such that a total rework of
>driver interfaces was required even if fully developped for VMS without
>"insipiratrion" from drivers provided by other companies ?
>
>
>Theoretically speaking, could the philosophy use for IA64 driver
>interfaces be ported to Alpha (for compatibility purposes etc), or are
>architectural differences significant enough that tghe philosophy used
>for IA64 drivers just wouldn't apply well on Alpha ?

The change, documented in the manual I requested a link for, makes the
terminal class and port interface routines CALLable routine instead of
the former JSBed-to routines.
-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.