From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Cc: bluez-users@lists.sf.net
Subject: Re: [Bluez-users] Problem with rfcomm!!
Date: Mon, 23 May 2005 12:09:34 +0200 [thread overview]
Message-ID: <1116842974.30044.38.camel@pegasus> (raw)
In-Reply-To: <20050521130837.51168.qmail@web42001.mail.yahoo.com>
Hi Neelam,
> I am working on a project in which I need to send character string via
> Bluetooth from Linux Box to an application running on an iPAQ.
>
> I am using Bluez on Linux for bluetooth support.
>
> And for sending the string to the iPAQ i am connecting by rfcomm and
> then just cat a text file to the rfcomm device.
>
> The commands I use are:
>
> rfcomm connect /dev/rfcomm0 <dev addr> <channel no>
>
> and the in another terminal i do:
>
> cat test.txt > /dev/rfcomm0
>
> The problem i am facing is with the number of characters my
> application receives.I have tried it on two kernels viz. 2.6.9 and
> 2.6.10........
>
> it is working perfectly fine with 2.6.9 but in case of 2.6.20 only 19
> characters are being send.......i just can't understand the
> reason........
try direct RFCOMM socket programming or use
rfcomm --raw connect ...
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&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-05-23 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 13:08 [Bluez-users] Problem with rfcomm!! neelam goyal
2005-05-23 10:09 ` Marcel Holtmann [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=1116842974.30044.38.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sf.net \
--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