Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH hcidump 2/2] decode fixed channel list info rsp
Date: Tue, 25 Oct 2011 11:21:39 +0200	[thread overview]
Message-ID: <20111025092139.GC3514@fusion.localdomain> (raw)
In-Reply-To: <1319448154-8743-2-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

On Mon, Oct 24, 2011, Emeltchenko Andrei wrote:
> Decode fixed channels in information response
> 
> < ACL data: handle 1 flags 0x00 dlen 10
>     L2CAP(s): Info req: type 3
> > ACL data: handle 1 flags 0x02 dlen 20
>     L2CAP(s): Info rsp: type 3 result 0
>       Fixed channel list 0x0000000a
>         L2CAP Signalling Channel
>         AMP Manager Protocol
> ---
>  parser/l2cap.c |   23 ++++++++++++++++++++---
>  1 files changed, 20 insertions(+), 3 deletions(-)

Both patches have been applied, but I had to fix the following to use
PRIx64 instead of %llx to compile both on 32 and 64 bit architectures.

> +		printf("Fixed channel list 0x%8.8llx\n", fc_mask);

Johan

  reply	other threads:[~2011-10-25  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  9:22 [PATCH hcidump 1/2] add get_le/get_be helpers Emeltchenko Andrei
2011-10-24  9:22 ` [PATCH hcidump 2/2] decode fixed channel list info rsp Emeltchenko Andrei
2011-10-25  9:21   ` Johan Hedberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-06 13:38 [PATCH hcidump 1/2] make struct features available for others Emeltchenko Andrei
2011-10-06 13:38 ` [PATCH hcidump 2/2] decode fixed channel list info rsp Emeltchenko Andrei

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=20111025092139.GC3514@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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