Hi

I updated OpenOBEX in FreeBSD port collection
(http://www.freshports.org/comms/openobex/) and while updating found 2
minor bugs.

First one is just incomplete define set for freebsd, patch is

diff -ur lib/bluez_compat.h work.2/openobex-1.4/lib/bluez_compat.h
--- lib/bluez_compat.h  2008-11-07 14:36:09.000000000 +0200
+++ lib/bluez_compat.h  2008-11-19 02:34:53.000000000 +0200
@@ -53,6 +53,8 @@
#define rc_family   rfcomm_family
#define rc_bdaddr   rfcomm_bdaddr
#define rc_channel  rfcomm_channel
+#define BDADDR_ANY  NG_HCI_BDADDR_ANY
+#define BTPROTO_RFCOMM BLUETOOTH_PROTO_RFCOMM

#elif defined(HAVE_BLUETOOTH_NETBSD)
#include <bluetooth.h>

without it compilation will fail.

And another diff is a bit more complicated. While trying to compile with
libusb to enable usb obex with my mobile (nokia 3500C) I found that usb
is not working in FreeBSD-openobex. I am not guru in libusb programming,
but IMHO usbobex.c is a bit wrong. Why we have 2 usb_open() calls on the
same device? it fail on FreeBSD. IMHO it is a wrong way, because i found
no references about such usage. After removing most of the code related
with second call and so called "control connection" i was able to use my
mobile in USB mode. Also i added usb_clear_halt() on disconnect, because
without this i was not able to use obex-usb second time without
replugging. Currently i have no USB cord to test if if cause regressions
on Linux, but i`ll be able to do this soon.

http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/comms/openobex/files/patch-usb



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users

Reply via email to