From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] A small query
Date: Thu, 05 May 2005 15:13:06 +0200 [thread overview]
Message-ID: <1115298786.8496.153.camel@pegasus> (raw)
In-Reply-To: <20050505122914.45406.qmail@web8303.mail.in.yahoo.com>
Hi Mayank,
> > > 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.
>
> I did not mean that hcidump is not functioning
> correctly, I meant that maybe we have not declared the
> structure correctly.
don't put too much trust on hcidump. It must not always be right and I
had some situations where I trusted it too much.
> Swapping message_type and packet_type makes no
> difference to a2play but it makes a lot of difference
> to a2recv.
Why can this be? Doesn't a2play uses message_type and packet_type at
all?
Regards
Marcel
-------------------------------------------------------
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 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 13:09 [Bluez-devel] A small query Mayank Batra
2005-05-03 15:38 ` Marcel Holtmann
2005-05-05 12:29 ` Mayank Batra
2005-05-05 13:13 ` Marcel Holtmann [this message]
-- 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=1115298786.8496.153.camel@pegasus \
--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