From: Sebastien HENRIO <sebastien.henrio@parrot.fr>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] a2play and Toshiba SR-1 Bluetooth Headset
Date: Fri, 26 Nov 2004 10:00:12 +0100 [thread overview]
Message-ID: <41A6F09C.5000801@parrot.fr> (raw)
In-Reply-To: <1101442380.6465.77.camel@pegasus>
Hi,
Marcel Holtmann wrote:
> Hi Henryk,
>=20
>=20
>>>For me it is not clear if we have to set them, ignore them or what to
>>>do with them. Do we have to insert the content protection header in
>>>the media payload if these capability is present?
>>
>>Obviously we may only insert the content protection header if we reques=
t
>>content protection during set configuration. However, I don't remember
>>any document requiring us to do that. I think Content protection is
>>completely optional and we would only use that if we were a paranoid
>>Sony device that believed everybody else on the planet was after us to
>>steal our music.
>=20
>=20
> actually for me it is not clear if we have to insert that header (even
> with no content protection information) when the capabilities shows tha=
t
> record. Maybe I missed something in the specification.
In fact you have to insert the content protection header only if you=20
want to use it.
This capablity is optional, so you can skip it during the stream=20
configuration process.
Best Regards
S=E9bastien
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-26 9:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 9:11 [Bluez-devel] a2play and Toshiba SR-1 Bluetooth Headset Alain Volmat
2004-11-25 10:25 ` Henryk Plötz
2004-11-25 10:56 ` Alain Volmat
2004-11-25 12:17 ` Marcel Holtmann
2004-11-26 3:40 ` Marcel Holtmann
2004-11-26 3:56 ` Henryk Plötz
2004-11-26 4:12 ` Marcel Holtmann
2004-11-26 9:00 ` Sebastien HENRIO [this message]
2004-11-26 17:29 ` Marcel Holtmann
2004-11-27 1:04 ` Henryk Plötz
2004-11-27 3:09 ` Marcel Holtmann
2004-11-26 4:11 ` Alain Volmat
2004-11-26 4:27 ` Alain Volmat
2004-11-26 4:41 ` Marcel Holtmann
2004-11-26 4:57 ` Alain Volmat
2004-11-26 4:29 ` Marcel Holtmann
2004-11-26 4:54 ` Alain Volmat
2004-11-26 8:32 ` Brad Midgley
2004-11-26 8:07 ` Brad Midgley
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=41A6F09C.5000801@parrot.fr \
--to=sebastien.henrio@parrot.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.