{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/382","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/382/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/382/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/382/events","html_url":"https://github.com/raspberrypi/firmware/issues/382","id":59354164,"number":382,"title":"i2c-0 broken","user":{"login":"richard-tx","id":6344201,"avatar_url":"https://avatars.githubusercontent.com/u/6344201?v=3","gravatar_id":"","url":"https://api.github.com/users/richard-tx","html_url":"https://github.com/richard-tx","followers_url":"https://api.github.com/users/richard-tx/followers","following_url":"https://api.github.com/users/richard-tx/following{/other_user}","gists_url":"https://api.github.com/users/richard-tx/gists{/gist_id}","starred_url":"https://api.github.com/users/richard-tx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/richard-tx/subscriptions","organizations_url":"https://api.github.com/users/richard-tx/orgs","repos_url":"https://api.github.com/users/richard-tx/repos","events_url":"https://api.github.com/users/richard-tx/events{/privacy}","received_events_url":"https://api.github.com/users/richard-tx/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-02-28T19:24:05Z","updated_at":"2015-03-02T09:20:57Z","closed_at":null,"body":"I2c bus 0 appears broken as verified by Joan.  It appears that bit 9 of the i2c packet is being held low.  See discussion at http://www.raspberrypi.org/forums/viewtopic.php?f=44&t=102130"},"comment":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/comments/76679968","html_url":"https://github.com/raspberrypi/firmware/issues/382#issuecomment-76679968","issue_url":"https://api.github.com/repos/raspberrypi/firmware/issues/382","id":76679968,"user":{"login":"6by9","id":5822349,"avatar_url":"https://avatars.githubusercontent.com/u/5822349?v=3","gravatar_id":"","url":"https://api.github.com/users/6by9","html_url":"https://github.com/6by9","followers_url":"https://api.github.com/users/6by9/followers","following_url":"https://api.github.com/users/6by9/following{/other_user}","gists_url":"https://api.github.com/users/6by9/gists{/gist_id}","starred_url":"https://api.github.com/users/6by9/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/6by9/subscriptions","organizations_url":"https://api.github.com/users/6by9/orgs","repos_url":"https://api.github.com/users/6by9/repos","events_url":"https://api.github.com/users/6by9/events{/privacy}","received_events_url":"https://api.github.com/users/6by9/received_events","type":"User","site_admin":false},"created_at":"2015-03-02T09:20:57Z","updated_at":"2015-03-02T09:20:57Z","body":"Well what would I know - I only worked at Broadcom for 7 years working on this and previous chips.\r\nI would expect badness if both processors try accessing the same I2C peripheral at the same time, but one at a a time they should be fine. It's just an I2C device that should respond on i2c-0.\r\n\r\nBye bye. I'll remember to ignore your posts in the future as you clearly don't actually want help or input from others.\r\n@pelwell Good luck."}}