From: Marcel Holtmann <marcel@holtmann.org>
To: Mauro Tortonesi <mtortonesi@ing.unife.it>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] l2cap xfer fails
Date: Wed, 28 Jan 2004 12:22:40 +0100 [thread overview]
Message-ID: <1075288960.12766.66.camel@pegasus> (raw)
In-Reply-To: <200401281200.07012.mtortonesi@ing.unife.it>
Hi Mauro,
> what i wanted to say is that i can transfer (over L2CAP) data from console,
> but transfer of files redirected to stdin always fails. perhaps i am doing
> something wrong? such as calling write(2) over L2CAP sockets with buffers
> larger that 762 bytes?
I haven't checked the nc6 Bluetooth support so far, but the L2CAP is a
SOCK_SEQPACKET and it has an in and an out MTU. The default MTU is 672
and this means if you send data with a larger buffer, the write() will
fail.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-01-28 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 10:35 [Bluez-devel] l2cap xfer fails Mauro Tortonesi
2004-01-28 11:00 ` Mauro Tortonesi
2004-01-28 11:17 ` Mauro Tortonesi
2004-01-28 11:22 ` Marcel Holtmann [this message]
2004-01-28 11:36 ` Mauro Tortonesi
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=1075288960.12766.66.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=mtortonesi@ing.unife.it \
/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