From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Regarding a2recv
Date: Thu, 05 May 2005 08:40:29 -0600 [thread overview]
Message-ID: <427A305D.40808@xmission.com> (raw)
In-Reply-To: <20050505124512.53335.qmail@web8306.mail.in.yahoo.com>
Mayank,
Good job finding that error.
Sorry I was slow to figure out what you were saying and didn't get it. I
made the fix.
If you show us the output of 'cvs diff' you'll be able to make these
things clear with less effort on your part:
$ cvs diff a2dp.h
Index: a2dp.h
===================================================================
RCS file: /cvsroot/bluetooth-alsa/btsco/a2dp.h,v
retrieving revision 1.3
diff -u -b -B -w -p -r1.3 a2dp.h
--- a2dp.h 2 May 2005 16:01:19 -0000 1.3
+++ a2dp.h 5 May 2005 14:34:20 -0000
@@ -38,8 +38,8 @@ struct sbc_frame_header {
/* packet components */
struct avdtp_header {
- uint8_t packet_type:2;
uint8_t message_type:2;
+ uint8_t packet_type:2;
uint8_t transaction_label:4;
uint8_t signal_id:6;
uint8_t rfa0:2;
Brad
Mayank Batra wrote:
> Henryk,
>
> Did you try what I suggested you in my mail titled 'A
> small Query' ?
>
> That is, swap the message_type and packet_type fields
> of the structure
>
> 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));
>
> in the file a2dp.h
>
> i.e. make it look like the following:
> struct avdtp_header {
> uint8_t message_type:2;
> uint8_t packet_type:2;
> uint8_t transaction_label:4;
> uint8_t signal_id:6;
> uint8_t rfa0:2;
> } __attribute__ ((packed));
>
>
> Once you swap them, I feel that a2recv will work for
> you.
> If it doesn't work, send me a copy of the dump.
>
> Regards,
>
> 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
-------------------------------------------------------
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 prev parent reply other threads:[~2005-05-05 14:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 12:45 [Bluez-devel] Regarding a2recv Mayank Batra
2005-05-05 13:14 ` Marcel Holtmann
2005-05-05 14:40 ` Brad Midgley [this message]
2005-05-06 4:05 ` Henryk Plötz
2005-05-08 12:50 ` Mayank Batra
2005-05-08 22:54 ` Henryk Plötz
2005-05-09 0:01 ` Marcel Holtmann
2005-05-09 0:58 ` Henryk Plötz
2005-05-09 1:03 ` Marcel Holtmann
2005-05-09 1:35 ` Henryk Plötz
2005-05-09 1:44 ` Marcel Holtmann
2005-05-09 4:29 ` Brad Midgley
2005-05-09 12:48 ` Henryk Plötz
2005-05-09 12:58 ` Marcel Holtmann
2005-05-09 16:25 ` Brad Midgley
2005-05-09 4:29 ` Brad Midgley
2005-05-09 12:38 ` Henryk Plötz
2005-05-09 21:31 ` Brad Midgley
2005-05-10 7:20 ` 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=427A305D.40808@xmission.com \
--to=bmidgley@xmission.com \
--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