{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/434","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/434/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/434/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/434/events","html_url":"https://github.com/raspberrypi/firmware/issues/434","id":85722908,"number":434,"title":"Wrong revision number for older Raspberry Pi","user":{"login":"AndrewFromMelbourne","id":1305783,"avatar_url":"https://avatars.githubusercontent.com/u/1305783?v=3","gravatar_id":"","url":"https://api.github.com/users/AndrewFromMelbourne","html_url":"https://github.com/AndrewFromMelbourne","followers_url":"https://api.github.com/users/AndrewFromMelbourne/followers","following_url":"https://api.github.com/users/AndrewFromMelbourne/following{/other_user}","gists_url":"https://api.github.com/users/AndrewFromMelbourne/gists{/gist_id}","starred_url":"https://api.github.com/users/AndrewFromMelbourne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AndrewFromMelbourne/subscriptions","organizations_url":"https://api.github.com/users/AndrewFromMelbourne/orgs","repos_url":"https://api.github.com/users/AndrewFromMelbourne/repos","events_url":"https://api.github.com/users/AndrewFromMelbourne/events{/privacy}","received_events_url":"https://api.github.com/users/AndrewFromMelbourne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-06T08:25:48Z","updated_at":"2015-06-06T23:18:19Z","closed_at":null,"body":"Since the firmware commit \"kernel: Fix bcm2835-mmc DMA allocation error handling\" (Hexxeh commit a1621d67b20f04acdac602d0b24923ec3cdbfb66) my Raspberry Pi Model B is reporting the wrong (or at least different) revision number. Up until that commit, my Raspberry Pi was reporting revision 000f, it now reports revision 0002. I can revert back to an earlier revision (Hexxeh commit 4f95c894c6a96b265d98f04a889e469833f7e996) and the revision number goes back to the original 000f. I am guessing it was this: \"Replacing board rev functions with board_info library\"\r\n\r\nI have tried the following firmware revisions. The table shows the model reported in dmesg and the revision number from /proc/cpuinfo.\r\n\r\ncommit | dmesg | revision\r\n----------|----------|-----------\r\n4f95c894c6a96b265d98f04a889e469833f7e996 | Raspberry Pi Model B | 000f\r\na1621d67b20f04acdac602d0b24923ec3cdbfb66 | Raspberry Pi Model B Rev 2 | 0002\r\n74fca0c56a378f78ace0148b7d439d177ead3c54 | Raspberry Pi Model B Rev 2 | 0002\r\n\r\nRevision 74fca0c56a378f78ace0148b7d439d177ead3c54 was \"Fix for identifying older model B Pi\", but this doesn't appear to have fixed the issue for my Raspberry Pi.\r\n\r\nI also have the following Raspberry Pi revisions. None of them appear to be affected:-\r\n\r\nmodel | revision\r\n--------|-----------\r\nModel B | 0002\r\nModel A | 0008\r\nModel B+ | 0010\r\nModel B Pi2 | a010041"},"comment":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/comments/109657204","html_url":"https://github.com/raspberrypi/firmware/issues/434#issuecomment-109657204","issue_url":"https://api.github.com/repos/raspberrypi/firmware/issues/434","id":109657204,"user":{"login":"AndrewFromMelbourne","id":1305783,"avatar_url":"https://avatars.githubusercontent.com/u/1305783?v=3","gravatar_id":"","url":"https://api.github.com/users/AndrewFromMelbourne","html_url":"https://github.com/AndrewFromMelbourne","followers_url":"https://api.github.com/users/AndrewFromMelbourne/followers","following_url":"https://api.github.com/users/AndrewFromMelbourne/following{/other_user}","gists_url":"https://api.github.com/users/AndrewFromMelbourne/gists{/gist_id}","starred_url":"https://api.github.com/users/AndrewFromMelbourne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AndrewFromMelbourne/subscriptions","organizations_url":"https://api.github.com/users/AndrewFromMelbourne/orgs","repos_url":"https://api.github.com/users/AndrewFromMelbourne/repos","events_url":"https://api.github.com/users/AndrewFromMelbourne/events{/privacy}","received_events_url":"https://api.github.com/users/AndrewFromMelbourne/received_events","type":"User","site_admin":false},"created_at":"2015-06-06T23:18:19Z","updated_at":"2015-06-06T23:18:19Z","body":"Hi @pelwell. Thanks for the reply. \r\n\r\n1)\r\n\r\nI can't find the board revision on the PCB. It just says Raspberry Pi (c) 2011.12. The board in question can be seen on the [Raspi.TV Raspberry Pi family portrait](http://raspi.tv/wp-content/uploads/2015/02/Pi-Family-Pi2-cropped_1500.jpg), identified as B Rev 2 (China).\r\n\r\nThis Raspberry Pi has 512MB of Ram\r\n\r\n2)\r\n\r\nIt functions correctly for me. I am not using i2c on this board, but I have manually loaded the module(s). The i2c device is created as /dev/i2c-1, which appears to be correct to me.\r\n\r\nThe concern I have is that there is code around that reads the revision number from /proc/cpuinfo and uses the revision to identify the i2c device etc. I know wiringPi uses the revision number. Code I have written for some work I was involved in also makes a decision about which device to open based on the revision. I have some code on github that uses the revision to report a number of attributes ([here](https://github.com/AndrewFromMelbourne/raspberry_pi_revision))\r\n\r\n3)\r\n\r\nI haven't seen any software problems:- \r\n\r\nThis Raspberry Pi has a [320x240 spi TFT](http://www.dx.com/p/mztx-pi-ext-2-5-ips-full-angle-lcd-display-extension-board-module-for-raspberry-pi-green-331576) set up to use fbtft and this is working correctly.\r\n\r\nFor several reasons, this Raspberry Pi sees the most use out of the five that I own. I use it mostly for software development (via ssh).\r\n\r\n@pelwell I hope that helps. Please let me know if you want any more information, or want me to test anything in particular."}}