On Mon, Oct 9, 2017 at 12:39 PM, Stephane Charette < [email protected]> wrote:
> In the past, I used to identify the type of device by reading the file > /proc/device-tree/compatible. For example, see this: > > > hexdump -C /proc/device-tree/compatible > 00000000 74 69 2c 61 6d 33 33 35 78 2d 62 6f 6e 65 2d 67 |ti, > am335x-bone-g| > 00000010 72 65 65 6e 00 74 69 2c 61 6d 33 33 35 78 2d 62 |reen > .ti,am335x-b| > 00000020 6f 6e 65 2d 62 6c 61 63 6b 00 74 69 2c 61 6d 33 > |one-black.ti,am3| > 00000030 33 35 78 2d 62 6f 6e 65 00 74 69 2c 61 6d 33 33 > |35x-bone.ti,am33| > 00000040 78 78 00 |xx. > | > > Last night I upgraded to a new build. I installed this one: > > https://rcn-ee.com/rootfs/bb.org/testing/2017-10-08/ > stretch-iot/BBB-blank-debian-9.2-iot-armhf-2017-10-08-4gb.img.xz > > Now I see that same model no longer identifies itself as a BBG. it now > thinks it is a BBB: > > > hexdump -C /proc/device-tree/compatible > 00000000 74 69 2c 61 6d 33 33 35 78 2d 62 6f 6e 65 2d 62 > |ti,am335x-bone-b| > 00000010 6c 61 63 6b 00 74 69 2c 61 6d 33 33 35 78 2d 62 > |lack.ti,am335x-b| > 00000020 6f 6e 65 00 74 69 2c 61 6d 33 33 78 78 00 > |one.ti,am33xx.| > 0000002e > > I should also have mentioned: I have not upgraded or installed new builds since...early 2017? This is my first time back working with my beaglebones in probably 8 months. So this change in behaviour may actually have been quite a while ago. Stéphane -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CA%2BHxBUKDYbOrMuByjisgdPJ3_X-RqS9af2MBHMUZYi%3DxDwOXNw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
