is GPIO ID of Rev C xM 0,1,0??

i'm hacking on barebox to get it to distinguish between various revs
of the beagle, and here's what i read in the current u-boot tree:

/*
* Routine: get_board_revision
* Description: Detect if we are running on a Beagle revision Ax/Bx,
* C1/2/3, C4 or xM. This can be done by reading
* the level of GPIO173, GPIO172 and GPIO171. This should
* result in
* GPIO173, GPIO172, GPIO171: 1 1 1 => Ax/Bx
* GPIO173, GPIO172, GPIO171: 1 1 0 => C1/2/3
* GPIO173, GPIO172, GPIO171: 1 0 1 => C4
* GPIO173, GPIO172, GPIO171: 0 0 0 => xM
*/

but this is from the kernel tree
(arch/arm/mach-omap2/board-omap3beagle.c):

/*
* OMAP3 Beagle revision
* Run time detection of Beagle revision is done by reading GPIO.
* GPIO ID -
* AXBX = GPIO173, GPIO172, GPIO171: 1 1 1
* C1_3 = GPIO173, GPIO172, GPIO171: 1 1 0
* C4 = GPIO173, GPIO172, GPIO171: 1 0 1
* XMA/XMB = GPIO173, GPIO172, GPIO171: 0 0 0
* XMC = GPIO173, GPIO172, GPIO171: 0 1 0
*/

which appears to clearly distinguish between xM A/B and xM C, which
u-boot does not.

  i have a clearly labelled Rev C xM in front of me, but when i boot
and try to read those GPIO pins, i get all zeroes. that might just be
my idiocy, but can i assume that my Rev C should really and truly
return 0,1,0 as the board ID?

rday

p.s. someone might want to tweak the u-boot code as well.

Oh the xm c’s gpio setting is detected in the uboot’s beagle.c it’s just documented in that text block…