Hi Bastien, > > >> As discussed on IRC. > > >> > > >> Still needed: > > >> - patch to wait for the bus to startup in udev mode > > > > Should we really do that? (What if the bus never appears?, how long should we > > wait?) > > The alternative (not overwhelmingly nice, I admit) would be to record > > somewhere in the system that bluetoothd tried to start but could not due to > > the missing bus and then start it "manually" by an init script that is > > guaranteed to run after DBus is started. > > Under normal conditions, we'd exit(1) if started and the bus isn't > available, and udev would pick that up, marking our job as failed, and > relaunching us later in the boot process, under coldplug. > > Marcel didn't like the idea though. so how does udev handle this exactly. We try bluetoothd and it fails, then it tries again later? What time exactly? How often? Does this affect the fast-boot effort? Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
