Bill Sommerfeld wrote: > On Wed, 2008-03-12 at 18:11 -0800, Gary Winiger wrote: >> The "device clean" program (or the device driver) >> resets the device to defaults so no one accessing the device at >> a later time can read out device parameters, such as scanning >> density -- I'm hypothzing here -- at a later time. > > So, you have *finally* identified something specific and actionable that > could possibly be investigated by the project team.
I think there are two things here - this is only one... > The whole "scanner as removable media" thing was a total distraction/red > herring. Nope - there was also > runs the "device clean" program. This instructs the user > to remove any documents from the device and acknowledge they > have done so. This is the removable media piece :-) > Perhaps we could use some future project to extend device allocation to > cope with devices accessed through libusb/ugen a We already have an architecture for removable media on USB flash and disk devices that uses HAL. It seems that there is an architectural hole here for "other USB devices that may have persistent state"; without fixing that hole, certain configurations of Solaris (TX etc) won't pass evaluation. Since we already have the approved architectures in place to enable SolarisTX and other "evaluated" configs, it shouldn't be the "device allocation" or "Solaris TX" teams jobs to keep on fixing the new stuff being dumped into OpenSolaris... IMO, the four teams (TX, device allocation, usb and sane) need to go off, butt heads and otherwise figure out what needs to happen. We can't (and shouldn't) invent that architecture here on this alias. -John
