well, the btattach tool would still have to be shipped and executed by bluez.
how would the additional info added in the interface data get handed over to the btattach tool ? how would we execute it ? i admit it looks a lot better and bluez wouldn't have to define each and every board implementation. but it also means a new interface from scratch or at least some significant changes to the serial-port interface to deal with the extra values and on the execution side it wont change much (you will still need a systemd unit in bluez and some script to hand the options to btattach (unless you want to patch btattach itself to pick up the options where the interface provides them (but will have to carry and maintain that patch then)). i definitely like the more generic name, and will rename the pi3:pi- bluetooth interface to pi3:bt-serial to get us around the "has to have every board in snapcraft.yaml". for the rest ... the question is how much effort these interface changes or re-implementation of a new takes ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674509 Title: Unable to find bluetooth device on RPi3 running Ubuntu Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1674509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
