{"action":"closed","issue":{"url":"https://api.github.com/repos/adafruit/adafruit-beaglebone-io-python/issues/52","repository_url":"https://api.github.com/repos/adafruit/adafruit-beaglebone-io-python","labels_url":"https://api.github.com/repos/adafruit/adafruit-beaglebone-io-python/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/adafruit/adafruit-beaglebone-io-python/issues/52/comments","events_url":"https://api.github.com/repos/adafruit/adafruit-beaglebone-io-python/issues/52/events","html_url":"https://github.com/adafruit/adafruit-beaglebone-io-python/issues/52","id":24858395,"number":52,"title":"SPI writebytes / xfer / xfer2 clocks out arrays of bytes in reverse order","user":{"login":"sidechained","id":859444,"avatar_url":"https://avatars.githubusercontent.com/u/859444?v=3","gravatar_id":"","url":"https://api.github.com/users/sidechained","html_url":"https://github.com/sidechained","followers_url":"https://api.github.com/users/sidechained/followers","following_url":"https://api.github.com/users/sidechained/following{/other_user}","gists_url":"https://api.github.com/users/sidechained/gists{/gist_id}","starred_url":"https://api.github.com/users/sidechained/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sidechained/subscriptions","organizations_url":"https://api.github.com/users/sidechained/orgs","repos_url":"https://api.github.com/users/sidechained/repos","events_url":"https://api.github.com/users/sidechained/events{/privacy}","received_events_url":"https://api.github.com/users/sidechained/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2013-12-29T10:41:30Z","updated_at":"2016-10-19T03:21:09Z","closed_at":"2016-10-19T03:21:09Z","body":"Just wanted to open this as a separate issue, as I'm experiencing the same behaviour as tweekzilla as mentioned here:\r\n\r\nhttps://github.com/adafruit/adafruit-beaglebone-io-python/issues/47\r\n\r\nThat is, that executing spi.writebytes([0x44, 0x88, 0xBB, 0xDD]) clocks out in reverse order (i.e. 0xDD, 0xBB, 0x44, 0x88). I can confirm the same behaviour with xfer and xfer2. Is this a problem with the spidev C++ implementation, or with the bindings?"}}
{"actor":{"display_login":"pdp7"}}