Open GoogleCodeExporter opened 8 years ago
The current order is a result of supporting t he CC256x chipsets, where a large
init script (10-60 kB) has to be sent to the Bluetooth module before it is
usable.
I don't mind getting BDADDR, local Features, and buffer size before that,
especially as these are read only commands (the init script might do module
resets...).
What do you need to do for your setup in the custom commands?
Why would you want to skip right to HCI_STATE_WORKING?
Original comment by matthias.ringwald@gmail.com
on 7 Feb 2014 at 4:44
I am replicating an initialization exactly as I've captured it from the device
I'm reverse engineering.
If I implement my own sequence, I don't have to worry about you modifying your
sequence in a later update.
I don't really have to follow my captured sequence of events, but I'd like to,
just in case something goes wrong. It's better to start with something already
known to work. Plus I don't need to worry about redundant commands that hog
precious boot time.
It's just a suggestion. Not really important but it feels like people might
find it useful. I've already hacked this feature into my copy of your code.
Original comment by frank.zhao.main@gmail.com
on 7 Feb 2014 at 6:35
Original issue reported on code.google.com by
frank.zhao.main@gmail.com
on 6 Feb 2014 at 6:38