From: Alain Volmat <avolmat@src.ricoh.co.jp>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] where is rfcomm source code?
Date: Fri, 11 Mar 2005 15:08:32 +0900 [thread overview]
Message-ID: <20050311060832.GB15644@snoopy.src.ricoh.co.jp> (raw)
In-Reply-To: <310520066.16529@bjut.edu.cn>
bluez-kernel-2.2 is a very old thing.
rfcomm layer source code is inside the linux kernel.
alain
* =E9=83=AD=E7=91=9E [Fri, 11 Mar 2005 at 13:47 +0800]
<quote>
> I have read the RFCOMM protocol of Bluetooth Specification,and want to=
read the
> source code of the rfcomm in Bluez,but I don't find it in the bluez-ke=
rnel-2.2
> packet.Where is it?=20
>=20
> thanks in advance.
>=20
> =20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> 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=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
</quote>
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-11 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 5:47 [Bluez-users] where is rfcomm source code? 郭瑞
2005-03-11 6:07 ` Marcel Holtmann
2005-03-11 6:08 ` Alain Volmat [this message]
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=20050311060832.GB15644@snoopy.src.ricoh.co.jp \
--to=avolmat@src.ricoh.co.jp \
--cc=bluez-users@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