From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] "Gather Write"/writev call and BlueZ driver...
Date: Sat, 30 Aug 2008 10:59:41 +0200 [thread overview]
Message-ID: <1220086781.7145.35.camel@californication> (raw)
In-Reply-To: <25BA763748F34FF6A428E1AE776B1E32@freqonedev>
Hi David,
> Not sure who to address this to (Marcel, maybe?), but does the Bluetooth
> driver support the writev call?
>
> The reason for asking is that in AVRCP+Metadata I need to implement
> fragmentation in AVCTP. Of course, I can just sling chunks of the big
> AVRCP packet into AVCTP buffers, pre-pending with the appropriate AVCTP
> header, but was wondering if there might be a more elegant solution
> (using writev to write the header, then the appropriate piece of the
> AVRCP packet).
go ahead and try it. I am not sure about writev, but in general it
should be supported since the kernel callback only expose sendmsg and
the rest it userspace API.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-08-30 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 11:06 [Bluez-devel] "Gather Write"/writev call and BlueZ driver David Stockwell
2008-08-30 8:59 ` 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=1220086781.7145.35.camel@californication \
--to=marcel@holtmann.org \
--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