From: "siddhant tewari" <siddhant.tewari@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm channel and ioctl
Date: Mon, 5 Mar 2007 14:56:58 +0530 [thread overview]
Message-ID: <57c68ddc0703050126n2696b8a7h7a4d36f605e6d2cc@mail.gmail.com> (raw)
In-Reply-To: <1172921500.24446.10.camel@aeonflux.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 1399 bytes --]
Hi Marcel,
Thanks very much for the reply ... rfcomm sockets are working
perfectly .... rctest.c example really eased out the things for me.
I would like to contribute for the bluez development , if thats
possible please suggest ways in which i can do that , may be for the start i
can fix small bugs with known solution.
regards
siddhant
On 3/3/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Siddhant,
>
> > Can someone tell me about tutorial describing how rfcomm and ioct
> > work in linux and about the underlying structure in kernel.
>
> no such thing exists. However RFCOMM programming is like programming
> TCP/IP and the rctest.c and attest.c files have code examples. The ioctl
> of RFCOMM are only needed for virtual TTY devices. Check the rfcomm
> utility source code to see how they work.
>
> 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
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #1.2: Type: text/html, Size: 2094 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-03-05 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 6:45 [Bluez-devel] rfcomm channel and ioctl siddhant tewari
2007-03-03 11:31 ` Marcel Holtmann
2007-03-05 9:26 ` siddhant tewari [this message]
2007-03-05 12:50 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57c68ddc0703050126n2696b8a7h7a4d36f605e6d2cc@mail.gmail.com \
--to=siddhant.tewari@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox