On 26 Nov 2004 at 1:33, P Witte wrote: (...) > On the Open call the PFF device driver's primary functions are > decode the name > check the details > set up and configure a channel definition block
yes, indeed! > If all of the above are ok then, on exiting, > set the calling job's program counter to a subroutine that > starts an independent job that opens any channels and > keeps things moving, ie a Driver JOB, > and then > returns to the calling job, where it left off, with a channel ID. This poses a certain number of problems, not alone that of not knowing at all where the calling job's PC lies. After all, by the time your (my) device driver open routine is called, there are so many things on the stack including return addresses within the IOSS (the very first one, for example, is one), that I would be very hesitant to say "ok, this is the job's routine address and I'll change that". Wolfgang > The Driver Job could then set up the appropriate Filter Program for that > protocol (is this really needed?) I don't belive it, but Rich does. (...) Wolfgang ---------------------------------------- www.scp-paulet-lenerz.com _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
