{"action":"created","issue":{"url":"https://api.github.com/repos/samnazarko/osmc/issues/159","labels_url":"https://api.github.com/repos/samnazarko/osmc/issues/159/labels{/name}","comments_url":"https://api.github.com/repos/samnazarko/osmc/issues/159/comments","events_url":"https://api.github.com/repos/samnazarko/osmc/issues/159/events","html_url":"https://github.com/samnazarko/osmc/issues/159","id":70978248,"number":159,"title":"OSMC does not run on SLICE","user":{"login":"mdeiders","id":12117014,"avatar_url":"https://avatars.githubusercontent.com/u/12117014?v=3","gravatar_id":"","url":"https://api.github.com/users/mdeiders","html_url":"https://github.com/mdeiders","followers_url":"https://api.github.com/users/mdeiders/followers","following_url":"https://api.github.com/users/mdeiders/following{/other_user}","gists_url":"https://api.github.com/users/mdeiders/gists{/gist_id}","starred_url":"https://api.github.com/users/mdeiders/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mdeiders/subscriptions","organizations_url":"https://api.github.com/users/mdeiders/orgs","repos_url":"https://api.github.com/users/mdeiders/repos","events_url":"https://api.github.com/users/mdeiders/events{/privacy}","received_events_url":"https://api.github.com/users/mdeiders/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-04-25T22:57:10Z","updated_at":"2015-04-26T17:08:31Z","closed_at":null,"body":"When will OSMC support FIVENINJAS SLICE?"},"comment":{"url":"https://api.github.com/repos/samnazarko/osmc/issues/comments/96409798","html_url":"https://github.com/samnazarko/osmc/issues/159#issuecomment-96409798","issue_url":"https://api.github.com/repos/samnazarko/osmc/issues/159","id":96409798,"user":{"login":"samnazarko","id":932652,"avatar_url":"https://avatars.githubusercontent.com/u/932652?v=3","gravatar_id":"","url":"https://api.github.com/users/samnazarko","html_url":"https://github.com/samnazarko","followers_url":"https://api.github.com/users/samnazarko/followers","following_url":"https://api.github.com/users/samnazarko/following{/other_user}","gists_url":"https://api.github.com/users/samnazarko/gists{/gist_id}","starred_url":"https://api.github.com/users/samnazarko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samnazarko/subscriptions","organizations_url":"https://api.github.com/users/samnazarko/orgs","repos_url":"https://api.github.com/users/samnazarko/repos","events_url":"https://api.github.com/users/samnazarko/events{/privacy}","received_events_url":"https://api.github.com/users/samnazarko/received_events","type":"User","site_admin":false},"created_at":"2015-04-26T17:08:31Z","updated_at":"2015-04-26T17:08:31Z","body":">The device tree overlay will be pushed into the build by the NOOBS software running on Slice and it'll modify config.txt to reference it.\r\n\r\nWe will need to take care there. We expect config.txt to be edited within OSMC's 'Pi config' option, so I will have to double-check that we handle existing definitions properly. CC @KODeKarnage. I suspect once we will also want some sanity checking: only make the DT option available in our config utility iff we are on a compute module. \r\n\r\n>The revision numbers in /proc/cpuinfo will indicate whether it is a compute module, although won't tell you which compute module design it is!\r\n\r\nIt would be nice if there was some way to tell, like putting a file on the fat partition called 'SLICE' which we can check at bootup. I suspect your PWM driver has some hooks in to Kodi, and if I am going to allow users to really utilise the LEDs you offer, I'll need to fopen() something when Kodi starts so I know if I'm meant to enable these effects. I don't particularly want to check loaded modules or #ifdef (that would require a separate build anyway)... I am just speculating here anyway, for all I know the LED ring is exposed as a /dev and you handle this all gracefully anyway in a nice diff that can be patched on to Kodi. \r\n\r\n\r\n\r\n"}}