From: Ho Ming Shun <cyph@cyph.ath.cx>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BCM2035 over UART on the E680I
Date: Sat, 24 Sep 2005 15:28:58 +0800 [thread overview]
Message-ID: <4335003A.6000400@cyph.ath.cx> (raw)
In-Reply-To: <1127485700.5623.8.camel@localhost.localdomain>
Hi,
I just did an interesting experiment:
After the phone's native stack was initialized, I killed off all
processes. Then I did a hciattach to ttyS1, followed by "hciconfig hci0
up". The BD_ADDR still shows 00:00:00:00:00:00.
It seems that the chip can still operate with READ_BD_ADDR returning
00:00:00:00:00:00. The phone's stack though already knows the BD_ADDR
through some other means (which I have not discovered).
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-09-24 7:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 13:44 [Bluez-devel] BCM2035 over UART on the E680I Ho Ming Shun
2005-09-19 9:25 ` Oliver
2005-09-19 10:22 ` Ho Ming Shun
2005-09-19 14:50 ` Oliver
2005-09-20 11:53 ` Marcel Holtmann
2005-09-23 11:41 ` Ho Ming Shun
2005-09-23 13:53 ` Marcel Holtmann
2005-09-23 13:07 ` Ho Ming Shun
2005-09-23 14:28 ` Marcel Holtmann
2005-09-24 0:22 ` Ho Ming Shun
2005-09-24 7:28 ` Ho Ming Shun [this message]
2005-10-03 8:47 ` [Bluez-devel] [SOLVED] " Ho Ming Shun
2005-10-03 11:36 ` Marcel Holtmann
2005-10-03 11:15 ` Ho Ming Shun
2005-10-03 12:42 ` 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=4335003A.6000400@cyph.ath.cx \
--to=cyph@cyph.ath.cx \
--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).