[Coco] Level3 and Drivewire may not work

[Aaron Wolfe]

On Wed, Dec 17, 2014 at 10:21 AM, Robert Gault <robert.gault at att.net> wrote:
> Bill Pierce via Coco wrote:
>>
>>
>> Bill & Robert, have you tried putting all the dw modules in the sys
>> memory? That way they have access to both rbf and scf. I've also wondered
>> about the clock issue. Clock is one of the L3 modules and "I think" dw4
>> relies on it's clock. Can you run dw4 with a different clock other than
>> clock_dw?
>>
>>
>> Bill Pierce
>> "Today is a good day... I woke up" - Ritchie Havens
>
>
> Drivewire does not care which of the clock modules is being used. On my real
> Coco3, I use clock_soft and my own program to read the SmartWatch which is
> in an RS-232 pak.
>

The goal is that DW doesn't care what combination of clock, RBF, and
SCF pseudo devices are used.  You should be able to use only one or
all three or whatever mix you like.  That may or may not be true in
practice, but if it doesn't hold true then there is a bug or design
mistake and we should be able to fix that. In other words, there is no
intentional dependency between clock, RBF, and SCF functionality in
DriveWire.

There is a common dependency that all of the device types share.  That
is the dwio module which provides the low level io used by all of the
SCF, RBF, and clock functionality.  This module should probably be
loaded in a common area in level 3 so that it is available no matter
which file manager is mapped in.  If that is impossible, it could be
loaded into each file manager's space theoretically.  Having multiple
dwio modules may trigger some problem since it hasn't been tried
before, but it should be doable given that any bugs are corrected.
Again, conceptually it's OK.