All of lore.kernel.org
 help / color / mirror / Atom feed
From: soraberri <421246@posta.unizar.es>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: hcidump iconsistent byte ordering?
Date: Mon, 24 Jan 2005 17:36:41 +0100	[thread overview]
Message-ID: <ct387l$p85$1@sea.gmane.org> (raw)
In-Reply-To: <1106581698.8058.47.camel@pegasus>

Hi Marcel,

Ok, the opcode is encoded in two fields:
OGF Range (6 bits): 0x00-0x3F
OCF Range (10 bits): 0x0000-0x03FF

and hcidump writes these two fields (0x01|0x0001) for the inquiry 
command, which in binary form it is

	0000 0100 0000 0001

and corresponds to 0x0401, which is shown as 01 04 by hcidump...

all rigth, I was thinking of 0x01 as 8 bits instead of 6.

thanks Marcel!

Regards

Luis Peiro


Marcel Holtmann wrote:
> Hi Luis,
> 
> 
>>let's say I want to decipher the first two HCI events from the "hcitool 
>>inq" dump:
>>< HCI Command: Inquiry (0x01|0x0001) plen 5
>>   33 8B 9E 08 64
>> > HCI Event: Command Status (0x0f) plen 4
>>   00 01 01 04
>>
>>Easily, the first one is the Inquiry command. Its command parameters are 
>>specified (Bluetooth Specification 1.1) in this order: LAP, 
>>Inquiry_Length, Num_Responses; so from the hcidump output we have:
>>
>>	LAP: 0x9E8B33 (general inquiry LAP)
>>	Inquiry_Length: 0x08
>>	Num_Responses: 0x64
>>
>>so far so good; it makes sense, but how about the command status event? 
>>the order of its event parameters from the specification is: Status, 
>>Num_HCI_Command_Packets, Command_Opcode. So following the same procedure 
>>  as before I would get:
>>	
>>	Status: 0x00
>>	Num_HCI_Command_Packets: 0x01
>>	Command_Opcode: 0x0401
>>
>>but this doesn't make sense because Command_Opcode should be 0x0001 
>>(Inquiry command). These bytes are now located as the two first bytes of 
>>the output, and the reading order is different from that of LAP's order 
>>in the Inquiry Command.
>>
>>So, I'm asking, how must I read hcidump output in order to agree with 
>>the specification?
> 
> 
> the command opcode consists of OGF and OCF. Look at the specification on
> how to encode them into the command opcode.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-01-24 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 14:31 [Bluez-devel] hcidump iconsistent byte ordering? soraberri
2005-01-24 15:48 ` Marcel Holtmann
2005-01-24 16:36   ` soraberri [this message]

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='ct387l$p85$1@sea.gmane.org' \
    --to=421246@posta.unizar.es \
    --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.