Hi Charles, > For ChromeOS, we're working towards having a single build/image based > on a reference board that then supports multiple models created by > OEMs. > > Some of the bluetooth config differs on a per model basis, so we need > to have multiple *.conf files ship on the actual image. > > We then modify the init script to check the model at runtime and pass > the appropriate *.conf file to bluetoothd when it is started. what are the difference in the config file? I am currently failing to see what you could change across different models. I like to understand this first before applying the everything is a nail approach here. 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
