From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Matthias Thomae <thomae@ei.tum.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Re: bfusb 1.1 firmware loading and rc-scripts
Date: 15 Sep 2003 17:32:14 +0200 [thread overview]
Message-ID: <1063639940.28891.510.camel@pegasus> (raw)
In-Reply-To: <3F65DB01.9030802@ei.tum.de>
Hallo Matthias,
> since upgrading from bfusb 1.0 to 1.1 I have problems creating bluetooth
> connections at system start form the rc-scripts on a debian/unstable
> system, such as PAN or CMTP connections.
>
> I think this is because the old bfusb version was returning only when
> the firmware has finished loading into the dongle (which takes a few
> seconds), whereas the new version returns immediately and loads the
> firmware in the background. Is this correct? When putting "sleep 10" in
> one of the rc scripts, it works as before.
the firmware loading routine is the same and blocks until the firmware
is loading. The only difference is where the firmware file comes from.
> Is there a way to detect when the firmware loading is finished, or would
> you consider to change back to the old behaviour?
The current driver is working fine and the firmware loading is finished,
when the HCI device is created.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2003-09-15 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F65D3E6.60307@ei.tum.de>
2003-09-15 15:30 ` bfusb 1.1 firmware loading and rc-scripts Matthias Thomae
2003-09-15 15:32 ` Marcel Holtmann [this message]
2003-09-15 17:59 ` [Bluez-users] " Matthias Thomae
2003-09-17 0:04 ` 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=1063639940.28891.510.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=thomae@ei.tum.de \
/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