From: Mayank Batra <mayankbatra@yahoo.co.in>
To: BLUEZ DEVELOPERS LIST <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] A small query
Date: Tue, 3 May 2005 14:09:09 +0100 (BST) [thread overview]
Message-ID: <20050503130909.22723.qmail@web8302.mail.in.yahoo.com> (raw)
Guys,
Does it matter whether I declare packet_type before or
after message_type. I am not sure, but if I declare it
before somehow, the hcidump on the a2recv side is not
correct.
I mean, there is something wrong in the hcidump. It
considers the commands as 'Cont' command and this is
when the source sends me a disconnect without
hesitation.
What I want to say is that if I declare packet_type
after message_type, then both the source's and sink's
dump are ok.
struct avdtp_header {
uint8_t packet_type:2;
uint8_t message_type:2;
uint8_t transaction_label:4;
uint8_t signal_id:6;
uint8_t rfa0:2;
} __attribute__ ((packed));
Mayank
________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-05-03 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 13:09 Mayank Batra [this message]
2005-05-03 15:38 ` [Bluez-devel] A small query Marcel Holtmann
2005-05-05 12:29 ` Mayank Batra
2005-05-05 13:13 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-05-08 12:44 Mayank Batra
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=20050503130909.22723.qmail@web8302.mail.in.yahoo.com \
--to=mayankbatra@yahoo.co.in \
--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