* bfusb 1.1 firmware loading and rc-scripts [not found] <3F65D3E6.60307@ei.tum.de> @ 2003-09-15 15:30 ` Matthias Thomae 2003-09-15 15:32 ` [Bluez-users] " Marcel Holtmann 0 siblings, 1 reply; 4+ messages in thread From: Matthias Thomae @ 2003-09-15 15:30 UTC (permalink / raw) To: BlueZ Mailing List, Marcel Holtmann Hello Marcel, list, 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. Is there a way to detect when the firmware loading is finished, or would you consider to change back to the old behaviour? Regards. Matthias ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bluez-users] Re: bfusb 1.1 firmware loading and rc-scripts 2003-09-15 15:30 ` bfusb 1.1 firmware loading and rc-scripts Matthias Thomae @ 2003-09-15 15:32 ` Marcel Holtmann 2003-09-15 17:59 ` Matthias Thomae 0 siblings, 1 reply; 4+ messages in thread From: Marcel Holtmann @ 2003-09-15 15:32 UTC (permalink / raw) To: Matthias Thomae; +Cc: BlueZ Mailing List 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-users] Re: bfusb 1.1 firmware loading and rc-scripts 2003-09-15 15:32 ` [Bluez-users] " Marcel Holtmann @ 2003-09-15 17:59 ` Matthias Thomae 2003-09-17 0:04 ` Marcel Holtmann 0 siblings, 1 reply; 4+ messages in thread From: Matthias Thomae @ 2003-09-15 17:59 UTC (permalink / raw) To: Marcel Holtmann; +Cc: BlueZ Mailing List, edd Hi Marcel, Marcel Holtmann wrote: >>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. > I see. Then it must be some other change I did which causes the different behaviour... >>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, > I wasn't meaning to imply that the driver didn't work fine, it even works *very* fine for me :) >when the HCI device is created. > > Ok, then the rc-scripts might need to wait until the hci device is up? Or would you rather handle this through a daemon which has a --persist option like pand? Edd, what do you think? Regards. Matthias ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-users] Re: bfusb 1.1 firmware loading and rc-scripts 2003-09-15 17:59 ` Matthias Thomae @ 2003-09-17 0:04 ` Marcel Holtmann 0 siblings, 0 replies; 4+ messages in thread From: Marcel Holtmann @ 2003-09-17 0:04 UTC (permalink / raw) To: Matthias Thomae; +Cc: BlueZ Mailing List, Edd Dumbill Hi Matthias, > Ok, then the rc-scripts might need to wait until the hci device is up? > Or would you rather handle this through a daemon which has a --persist > option like pand? if you really need it, what about bluetooth.agent ;) 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-09-17 0:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 ` [Bluez-users] " Marcel Holtmann
2003-09-15 17:59 ` Matthias Thomae
2003-09-17 0:04 ` Marcel Holtmann
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.