10/09/2008 11:50 AM
Character Devices DDK - termination
I am attempting to write a new <io-char library based> character device manager.
It seems as if there is no support at all in the io-char library, or in any of the sample source (that I have seen) for
any kind of graceful termination.
If you are working directly with hardware, this may or may not be an issue.
However, I am working with a driver that actually communicates with another resource manager to perform the character I/
It would be extremely helpful to have some kind of support for graceful termination so that some intelligent clean-up
could be done regarding resources (and states) left hanging.
There are probably any number of ways around this as I have the ability to request (or make) changes to the resource
manager at the other end if I have to. But that might not be the cleanest of fixes, as this resource manager is not
written exclusively for the benefit of the character device driver.
I could add the code for termination support to the io-char source code that is part of the kit, but I am unsure of the
(possibly enormous) ramifications of doing this kind of thing.
One that pops to mind almost immediately is that I would then have to sync my changes to any new versions of this DDK.
Another is the possible infraction against the copyright held by QSS.
Are there any constructive thoughts on how I could proceed?