All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: zubiwat <zubiwat@poczta.onet.pl>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Strange answer from HCI
Date: Fri, 26 Mar 2004 00:47:14 +0100	[thread overview]
Message-ID: <1080258434.2283.52.camel@pegasus> (raw)
In-Reply-To: <000a01c41299$f48241d0$fcca010a@lysydziadek>

Hi Maciej,

> I'm programming a microchip to work with BT and when I send some bits
> I get in the answer sth like this: 04 10 01 FE.
> If someone knows what it means I would be greatfull for some help.
> How to set parameteres like pscan or read BD ADDR by sending bits to
> BT dongle. Does any one knows what bits are coresponding to what
> commends while setting parameteres of BT because I know bits for
> transmition from Specification.

it is all in the Bluetooth HCI specification. You should really read and
understand it. Your bytes mean

	HCI event, hardware error, error code 0xfe

The error codes are vendor specific, so I don't know what 0xfe means.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-03-25 23:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 18:49 [Bluez-devel] Strange answer from HCI zubiwat
2004-03-25 23:47 ` Marcel Holtmann [this message]
2004-03-26 11:43   ` Steven Singer

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=1080258434.2283.52.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=zubiwat@poczta.onet.pl \
    /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.