Hello Alan,
Thank you for your cooperation. While trying to produce better debug I
found out what the problem was - the cached pointer to the USB device
was not the right one so the URB was receiving bad pointer to the device.
Thanks again for your time.
As you have spent some time to write those questions to me I feel
obligated to answer. So if you are still interested find the answers below.
The USB Bluetooth driver that is already in the kernel is not suitable
for my needs as it is not pure implementation of the HCI USB transport
layer but also provides the HCI functionality itself. I'm implementing
pure Java Bluetooth stack including the HCI layer so I need only the HCI
transport layer implementation to be native.
I know the code is ugly. As I said most of it is not mine and I just
reuse it. I've only rewritten from scratch the module "init" and "exit"
functions, "probe" and "disconnect". In addition I'm not experienced C
programmer so there may be some stupidities from my side. As a reference
for Linux USB device driver development I use mainly the "Linux Device
Drivers, Third Edition" book and some other articles published on the
http://lwn.net.
Best Regards,
George
Alan Stern wrote:
On Thu, 2 Feb 2006, George Simeonov wrote:
Hello Alan,
Thank you for you reply.
My idea of asking this question like this was just to get some
guidelines where I should look for the problem. As I'm pretty new in the
Linux USB driver development and I don't really know the internals of
the Linux USB core I needed just a direction from where to start in
order to solve my problem without bothering you with looking at my
sources. However after another day of digging into the problem without
any success I would kindly ask you to take a look at the code (please
find it attached) and I'll be very grateful if you could provide me with
the solution or at least point my attention to the right direction.
Which usb_submit_urb call is failing?
Do you have a debugging log?
Why do you have static definitions in the .h file in addition to
declarations?
Why are you writing a USB bluetooth driver when there's already one
available in the kernel?
Alan Stern
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
