> > The same as we do /dev/audio. We reset any state that can be
>
>
> OK, maybe I'm dense, but what is the perceived failure mode here?
> Is it "someone left a page on the scanner" or is it something else?
It's that there is information remaining in the device that
can be accessed after the device has been returned to the
system and given to anothe person.
> If it is the "can't flush page table :-)" problem, what is it
> that you would expect to be done here? Not allow logout to happen
> until scan() == empty_scan_platen() or some such? or ...?
See allocate(1), deallocate(1), device_allocate(4), device_maps(4),
and I thought there was a device_clean man page that I can't find.
I expect the project team to supply whatever is necessary to
work within the device allocation framework so the device
is properly integrated therein. This may include stuff in
devfsadm(1m), mkdevalloc(1m), mkdevmaps(1m), providing
a clean script/program and so on.
This stuff has all been part of SunOS since 5.3. Until recently,
there's been very little activity in adding system components
that needed special object reuse handling.
Gary..
