From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] ttyS0 problem
Date: Mon, 10 Oct 2005 05:19:15 +0200 [thread overview]
Message-ID: <1128914355.19569.33.camel@blade> (raw)
In-Reply-To: <1128909236.2417.20.camel@localhost.localdomain>
Hi David,
> > What commands do you wanna send?
> The command is HCI_GO_TO_SLEEP_IND(0x30) which is only one byte. It is a
> vendor specific command used to ask the BT device to go to sleep. If BT
> device receives the command, maybe it would response
> HCILL_GO_TO_SLEEP_ACK(0x31) command to the host.
do you have the specification of these vendor commands? Is this command
according to the HCI specification or is it an extension of the H:4
transport protocol?
> > after step 1, you must use the HCI raw socket to send commands
>
> Is this means we cannot write command to ttyS0 directly through write()
> function?
After calling hciattach the kernel takes over the serial port via the
line discipline and the reads and writes are useless.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-10 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1128906830.2417.1.camel@localhost.localdomain>
2005-10-10 1:53 ` [Bluez-devel] ttyS0 problem david
2005-10-10 3:19 ` Marcel Holtmann [this message]
[not found] <1129010637.2346.1.camel@localhost.localdomain>
2005-10-11 6:39 ` david
2005-10-09 16:38 davidgchen
2005-10-09 16:45 ` 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=1128914355.19569.33.camel@blade \
--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;
as well as URLs for NNTP newsgroup(s).