From: Marcel Holtmann <marcel@holtmann.org>
To: zubiwat <zubiwat@poczta.onet.pl>
Cc: devel Bluetooth <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BT Initialization
Date: Sat, 27 Mar 2004 19:44:23 +0100 [thread overview]
Message-ID: <1080413063.2281.59.camel@pegasus> (raw)
In-Reply-To: <009401c4142a$b06be720$fcca010a@lysydziadek>
Hi Maciej,
> I'm setting CSR BT device using code from blueZ hciattach.c
> and after this when I'm trying to send some commands I get only this:
> 04 FF 13 C2 01 00 09 00 02 00 02 68 00 00 BF 0E 00 00 00 00 00 00
> I get this even when I'm not sending anything. I looked for this event
> into specification and couldn't find it.
> I think that I have to send some command to set BT up and then it will
> listen to my other commands like reading BT ADDR.
> If someone could send me a code how to set up BT device and read
> BT ADDR for example I would be greatfull.
this is a vendor specific event and if you had looked into the BlueZ
source you would have seen that we send as first command the read local
supported features HCI command. Actually my question is what kind of
code do you wanna to see, because the complete BlueZ stack is open
source.
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
next prev parent reply other threads:[~2004-03-27 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 18:38 [Bluez-devel] BT Initialization zubiwat
2004-03-27 18:44 ` Marcel Holtmann [this message]
[not found] ` <00a401c41436$58423520$fcca010a@lysydziadek>
2004-03-27 20:20 ` Marcel Holtmann
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=1080413063.2281.59.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox