Hi Charles, On 07/06/2017 01:16 AM, C Shapiro wrote: > ChromeOS is currently shifting to a more dynamic build system where a > single build will be created/managed/deployed to support multiple models > that were all created based on a single reference board. > > This is being done for general cost/maintenance savings around the sheer > number of builds that are currently managed for ChromeOS. I could not understand whether there were any merits except maintenance of your ChromeOS. Are there any merits for other software/users (e.g. container, etc.)? > For the bluetooth stack, models have different product id values in the > DeviceID field for the main.conf config file. Why do not you pass DeviceID as an argument instead of a config file? > E.g. > https://chromium.git.corp.google.com/chromiumos/overlays/board-overlays/+/master/overlay-pyro/chromeos-base/chromeos-bsp-pyro/files/main.conf > https://chromium.git.corp.google.com/chromiumos/overlays/board-overlays/+/master/overlay-reef/chromeos-base/chromeos-bsp-reef/files/main.conf > https://chromium.git.corp.google.com/chromiumos/overlays/board-overlays/+/master/overlay-snappy/chromeos-base/chromeos-bsp-snappy/files/main.conf I could not access without an account. How can I sign up? > This change allows the config file to be passed as a runtime argument to > bluetoothd, which allows the ChromeOS init script to determine the model > at runtime and then pass the appropriate model specific config file. Why do not you change only ChromeOS init scirpt? For example, in ChromeOS init scirpt, 1. Determine the model. 2. Run ln command with --force option to link /etc/bluetooth/main.conf to the appropriate config file. Thank you for reading this to the end :) Regards, Eramoto -- 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
