Hi Dennis, Thanks for your prompt reply!
Yes, I've managed to get that far. I have an extension of org.osgi.service.Device that gets registered with the appropriate properties (I think) i.e. DEVICE_SERIAL etc.. It also gets unregistered when the device is disconnected...hoooray. =) Its just that when I take the next step with Device Manager, a driver and driver attachement I always have the feeling of "ok, did I get this right or what...". My first version I opened a USB channel and allocated resources for IO as part for the device registration but that didn't seem right. Now I have a re-written version where the USB driver will go through the matching and attachment process and I guess that will turn out better... Although, it would be nice to have something to verify against.... I guess that the verification comes from having the devices and drivers working in the dynamic environment i.e. coming and going attaching and releasing...I'm slowly getting there... ;) Is there something that I can use, for verification, from the Felix website? Regards Patrik > Hi Patrik, > > I don't know of a HelloWorld example that exists out there, but I've > recently donated an implementation of the device access spec to Apache > Felix. I can cook up an example for you, if you want. > > What you probably need is some kind base driver that is able to detect > (in a low-level way) that a device has appeared on the USB bus. Based > on the limited information that has then become available about the > device > a Device (in the sense of the device access spec) must then be > registered within the framework. It is then up to the device manager > to locate possible drivers that match the detected device. > > Regards, Dennis
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
