[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] direct l2cap access in kernel mode

  I too have an application that only needs to access the l2cap layer only 
(as far as i can tell). All i need to do is establish a connection with 
another node and transfer a very small amount of data. I am using the stack 
in usermode as that seems to be much easier and my application is not 
critical at this point. I am not an expert programmer and need something 
quick and easy to use, such as a direct function call rather then using IOCTLs.

  I have been able to use the functions:  (from the btd.c sample application)
  These functions only establish a Baseband connection. How do I continue 
if I want the remote end to send a few bytes of data to this master 
(client) that just established the connection?
  Are there any suggestions of what functions or sequence of events (based 
on the axis OpenBT stack) I could/should use? I know there are other 
functions such as l2cap_recieve_data..etc.. but which is the correct one to 
use on the master and slave?


>For my application, I need to access the l2cap layer directly; I have no 
>need for features added by RFCOMM or higher layers.  I also need to allow 
>multiple devices to access the bluetooth interface simultaneously, so I 
>will need to use the stack in kernel mode.  As it sits in cvs (as of a few 
>days ago when I last updated), the OpenBT stack does not allow direct 
>access to L2CAP when running in kernel mode.  Do you intend to add support 
>for this eventually?   When the stack was designed, what

To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com