Re: Re: [Bluez-users] Can anybody help plz?

Re: Re: [Bluez-users] Can anybody help plz?

[vaishali paisal]

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

Hello there,

Thanks for the information.And i can now find out the ioctl intearction stuff .But I think that RFCOMM layer is implemented as a kernel module .So it should use the same EXPORT_SYMBOL() concept to communicate with l2cap,why sockets?????
Is there any other way in which the kernel modules can interact among themselves?

Regards
vaishali  


On Tue, 05 Apr 2005 Marcel Holtmann wrote :
>Hi,
>
> > I have a small problem in understanding the blueZ source code for
> > kernel 2.6.11.I am unable to find out exactly how the kernel
> > implementations of the l2cap layer,hcilayer and rfcomm layer are
> > interacting amongst themselves ?As well as how they interact with the
> > user space libraries?
> >
> > I have seen some functions in l2cap.c calling functions from
> > hci_core.c which have been put as EXPORT_SYMBOL() in hci_core.c.
> > Is it the way they are communicating or am i missing something?
>
>the module interaction is done by the exported symbols as you already
>realized. The upper layer modules like RFCOMM, BNEP etc. are using the
>L2CAP socket interface inside the kernel. All userspace tools are using
>the ioctls and the socket interfaces.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Bluez-users mailing list
>Bluez-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-users

[-- Attachment #2: Type: text/html, Size: 2267 bytes --]