Hi,
Am 29.01.2009 um 17:22 schrieb Alex Kanavin:
> Actually I agree with you - Marcel is unresponsive lately, and if he's
> too busy with bluez or whatever, he should hand openobex over to
> Hendrik or Christian if either agrees. IMO :)
That is an issue for quite some time now. Personally, I sti
2009/1/29 Bastien Nocera :
> And a few calls to ods_usbobex_free_interfaces() were missing as well.
OBEX_Cleanup does the same thing though.
>> > I've changed the code to not use the same structures as openobex does
>> > internally, to avoid such confusion.
>>
>> Aah, now I see how this works. I'
On Thu, 2009-01-29 at 17:53 +0200, Alex Kanavin wrote:
> 2009/1/29 Bastien Nocera :
> >> > Using the same code as openobex for the device discovery, and fixing a
> >> > few memleaks in the process.
>
> Could you point them out?
In the obex-data-server code?
that one:
- info = g_hash_table_
Alex Kanavin wrote
> HOWEVER,
> libusb 1.0 has just been released. It has a much nicer looking API,
> and part of that API allows getting bus and device numbers:
> http://libusb.sourceforge.net/api-1.0/group__dev.html
> I will write a patch that ports OpenOBEX to libusb 1.0, and adds those
> proper
2009/1/29 Bastien Nocera :
>> > Using the same code as openobex for the device discovery, and fixing a
>> > few memleaks in the process.
Could you point them out?
> I've changed the code to not use the same structures as openobex does
> internally, to avoid such confusion.
Aah, now I see how thi
On Thu, 2009-01-29 at 13:55 +0200, Alex Kanavin wrote:
> 2009/1/29 Bastien Nocera :
> > Using the same code as openobex for the device discovery, and fixing a
> > few memleaks in the process.
> >
> > Patch for obex-data-server attached.
>
> Quite a hack:
>
> +/* Information about a USB OBEX inter
2009/1/29 Bastien Nocera :
> Using the same code as openobex for the device discovery, and fixing a
> few memleaks in the process.
>
> Patch for obex-data-server attached.
Quite a hack:
+/* Information about a USB OBEX interface present on the system */
+struct obex_usb_intf_transport_t {
You co
On Thu, 2009-01-29 at 00:17 +0100, Tadas Dailyda wrote:
> It is also possible to just fork USB interface discovery code from
> openobex to ods. That way we wouldn't break openobex API and ods
> wouldn't have to depend on very recent openobex version (furthermore,
> nobody knows when it would be re
2009/1/29 Hendrik Sattler :
>> Well, openobex needs to be ported to libusb 1.x anyway, where those
>> properties are absent.
>
> Is is possible to add support both both, e.g. with a #ifdef? And both
> being ABI-compatible?
> I don't want to be force to upgrade to a recent libusb version to be
> abl
Alex Kanavin schrieb:
> 2009/1/29 Bastien Nocera :
>> They don't only work on Linux. They also work on BSDs, and MacOS X (at
>> least). It's what libgphoto2 uses, and I believe it works on much more
>> than just Linux.
>
> Well, openobex needs to be ported to libusb 1.x anyway, where those
> prope
10 matches
Mail list logo
