Hi Hendrik, > > I want that BtOBEX* API calls always available and we should just define > > bdaddr_t if it is not defined by a previous include. > > So you have 2 options. Either release as is because it is not a > regression, or delay until fixed. > I can spend some time on it this weekend but I'll have no internet > connection, so I can submit that earliest monday evening (if ready at > that time).
since we are breaking the API now anyway, we can just redo the Bluetooth interface a little bit. For example just using const char *addr or something alike. > BTW: I tried using the USB gadget thing in Linux-2.6.29. That > interface is definitely only partly usable because you cannot get > notification when the USB master is (dis-)connected. Any idea? Never tried it. Regards Marcel ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
