{"action":"closed","issue":{"url":"https://api.github.com/repos/SolidRun/linux-fslc/issues/61","repository_url":"https://api.github.com/repos/SolidRun/linux-fslc","labels_url":"https://api.github.com/repos/SolidRun/linux-fslc/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/SolidRun/linux-fslc/issues/61/comments","events_url":"https://api.github.com/repos/SolidRun/linux-fslc/issues/61/events","html_url":"https://github.com/SolidRun/linux-fslc/issues/61","id":358209274,"node_id":"MDU6SXNzdWUzNTgyMDkyNzQ=","number":61,"title":"Bluetooth init errors","user":{"login":"warped-rudi","id":912371,"node_id":"MDQ6VXNlcjkxMjM3MQ==","avatar_url":"https://avatars2.githubusercontent.com/u/912371?v=4","gravatar_id":"","url":"https://api.github.com/users/warped-rudi","html_url":"https://github.com/warped-rudi","followers_url":"https://api.github.com/users/warped-rudi/followers","following_url":"https://api.github.com/users/warped-rudi/following{/other_user}","gists_url":"https://api.github.com/users/warped-rudi/gists{/gist_id}","starred_url":"https://api.github.com/users/warped-rudi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/warped-rudi/subscriptions","organizations_url":"https://api.github.com/users/warped-rudi/orgs","repos_url":"https://api.github.com/users/warped-rudi/repos","events_url":"https://api.github.com/users/warped-rudi/events{/privacy}","received_events_url":"https://api.github.com/users/warped-rudi/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-09-07T20:57:48Z","updated_at":"2018-12-24T08:31:57Z","closed_at":"2018-12-24T08:31:57Z","author_association":"NONE","body":"I see (failing) attempts to initialize Bluetooth on SoMs that don't have BT/WIFI at all.\r\n\r\nAlso: Is there a way to switch back to the old mechanism of firmware loading from user space?\r\nI have not tested this yet, but in the past there were a lot of problems when trying to run BT and WIFI simultaneously. Therefore we had disabled BT-firmware loading (which instantiates the HCI device) by default and the user could enable it when needed by unmasking a systemd unit."}}
{"actor":{"display_login":"jnettlet"}}