Nice. Note that on vxworks, you could easily set up your own device that appears under A, we already do this for diskboot in drv_self_hide. You can also look at the /tyCo/0 hook for console output. Note that you could make this driver actually eat the data and send it off over ptp (or rather buffer it and block until the PC grabs it, since the camera can't initiate data transfer) Don't know if that would be simpler than grabbing it out of memory...
vxworks documentation may be easily found with google.
I would guess that setting up a driver on DryOS is similar, but documentation is scarce I don't see an references to anything that looks like /dev/null. There is /_term and termDeviceCreate
Thx for the suggestions. Using a device with a name that passes the name check could spare the duplication of a few routines and would look elegant. But I currently barely know anything about devices ...
If you want to just prevent writing, and grab the data elsewhere, you could probably just copy the device struct from the null device.
edit:FWIW, I was unable to open /_term with open() in dryos, so maybe dryos devices are not so similar to vxworks ones.
hmmm, I see: DRV_struct = _iosDevFind("/tyCo/0", 0); in /platform/generic/main.c
Started by hiker_jon
Started by mhstgt
RAW Shooting and Processing
Started by jt256
Started by careyer
Started by esmail