[haiku-bluetooth] Re: [PATCH] Bluetooth Optional Package

  • From: "Oliver Ruiz Dorantes" <oliver.ruiz.dorantes@xxxxxxxxx>
  • To: haiku-bluetooth@xxxxxxxxxxxxx
  • Date: Fri, 23 May 2008 17:06:52 +0200

Hi Andreas,

Seems you haven't looked at the patch yet! ;)

hehe believe me I did, but yes you are right, seems i focused only in the
link part :)

> My patch includes all parts from Adrien that I hope are okay, namely
> src/bin/Jamfile, src/kits/Jamfile, src/servers/Jamfile and
> src/add-ons/kernel/drivers/Jamfile. I guess I should split my patch up to
> make this clearer. :)

Dont worry i dont like applying patches atomatically, will perform all step
by step

> That's necessary for developing Bluetooth applications on Haiku. (I would
> be interested in creating a C# wrapper around your C++ Bluetooth kit.)

Hmm I have not the need of it in R5. due BeIDe project most likely... fine

> Yes, that one line should not be committed together with Bluetooth. I will
> submit an improved patch later, where this will be removed.

Dont worry will apply it manually ;)

As for inaugurating the mailing list, on to sadder topics ... I have tested
> 8 different Bluetooth USB dongles, none of them were listed in bt_dev_info.
> Should I see them somewhere under /dev/busses/usb/? In your blog you mention
> using usb_dev_info but that needs some argument! I did not find a trace of
> them in the filesystem, and I'm unsure whether this is a OHCI USB problem or
> a Bluetooth problem...

Hmm yes you have to pass the device path. If the USB stack recognized your
USB device, it will be published in /dev/busses/usb/...

in my case:

$ usb_dev_info /dev/bus/usb/0/0

If your dongle is not published there, the problem is:
a) USB problem (AFAIK mmlr is going on with the work of Salvatore in OHCI i
did not know it was already usable)
b) the class device is not ok, should be 224,1,1 (AFAIR) ,in that case we
can fix the driver to recognize ur vendor and product ID

Another problem is that I actually never tried ther Stack in Haiku. I wait
for the alpha release to move all in from R5

Actually your jam build system patches are being really usefull. Therefore I
can be focusing just in code, as most of the development is being done on R5
and I use the Haiku build system to make sure, I will not need to port later
to Haiku, and just to compile.

So I am still on the way getting familiar with the build system...




Other related posts: