Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Serial port expansion
Message-ID: <22472@ucbvax.BERKELEY.EDU>
Date: 9 Jan 88 09:08:07 GMT
References: <197@imagine.PAWL.RPI.EDU> <4918@well.UUCP> <22440@ucbvax.BERKELEY.EDU> <3113@cbmvax.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Lines: 25

In article <3113@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
>In article <> bryce@hoser.berkeley.edu (Bryce Nesbitt) writes:
>>
>>Or not at all.  Recall that OpenDevice() fills in the io_Device field with
>>the device pointer....
>
>What about the CloseDevice() ?
>Seems like you'll need some additional magic then.

I'll give that a hesitent "Don't think so".  I'm assuming CloseDevice()
looks at io_Device and fires off a Close to the proper device.  The device
would decrement the count and perhaphs become expungeable.

We already HAVE to have a way of finding the device on OpenDevice(),
so no problem there.


I bounced on an attempt at disassembling CloseDevice().  It has some funky
ram patch that looks to be either setting up a frame pointer or a Global
Vector.  Ick!

|\ /|  . Ack! (NAK, SOH, EOT)
{o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (or try "cogsci")
 (")
  U	"Your theory is crazy... but not crazy enought to be true." -Niels Bohr