2006-08-01 15:13:53

by Peter Wippich

[permalink] [raw]
Subject: [Bluez-devel] Patch for rfcomm tty server ports

_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel


Attachments:
rfcomm_tty.patch (11.36 kB)
(No filename) (348.00 B)
(No filename) (164.00 B)
Download all attachments

2006-08-02 11:01:09

by Peter Wippich

[permalink] [raw]
Subject: Re: [Bluez-devel] Patch for rfcomm tty server ports


Hi Marcel,

On Wed, 2 Aug 2006, Marcel Holtmann wrote:

> the idea of using BDADDR_ANY is kinda nice, but the use of another
> kernel thread for the listen RFCOMM socket within the RFCOMM module is
> not good. We need to integrate all the processing for the server state
> in the DLC itself.

I partially agree with you. The solution with the kernel thread is somehow
"quick 'n dirty". The problem was that I got only a limited time to get
this working and did not want to break anything. Currently, only a socket
can wait for an incomming connection. It would be nicer if we can put this
into the DLC itself, but this would require some more internal changes
with a high risk of messing thinks up.

> I am not gonna working on this, but I am supporting it and happy to
> review any patches.
Thank you.
When my understanding of the internals gets better I'll try to work
something out.

Regards,

Peter


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

2006-08-02 03:09:11

by Marcel Holtmann

[permalink] [raw]
Subject: Re: [Bluez-devel] Patch for rfcomm tty server ports

Hi Peter,

> this patch allows the use of tty server ports. If a rfcomm tty port
> is bound to BDADDR_ANY e.g. :
>
> rfcomm bind /dev/rfcomm0 00:00:00:00:00:00 1
>
> it will start listening on the channel supplied once opened (and will
> stop listening when the port is closed...). This allows rfcomm ttys in
> server mode without the need for an additional user space daemon.

the idea of using BDADDR_ANY is kinda nice, but the use of another
kernel thread for the listen RFCOMM socket within the RFCOMM module is
not good. We need to integrate all the processing for the server state
in the DLC itself.

I am not gonna working on this, but I am supporting it and happy to
review any patches.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel