Support Raspberry Pi 2 with MoOde 9

[Prince]

Hi,

I run the Pi1B with 512 MB exclusively for nostalgic reasons (I own a Pi4B also). I used the last moOde9 builder with 32bit support to upgrade to Bookworm. It's a dirty image where builders step3 had been skipped and the package dependencies had to be solved by hand afterwards (changing between moOde8 and moOde9 sources). I haven't checked all moOde's functions, but internetradio and upnp-stuff have been running well here for ~6 months. Very dirty but works rocksolid. 
(I can see your eyes rollin'  , but I love my 1B)

For cosmetic reasons, I checked for the incorrect memory size displayed (256MB instead of 512MB). The 1B has the old revision code. 

Code:

cat /proc/cpuinfo | awk -F': ' '/Revision/ {print $2}'
000e

My question is: Why is the revision-code 'and'-combined in the pirev.py-script with 0x17?

Code:

old_rev = OLD_REVISION_CODES[code&0x17]

In my case the code-variable has '14' ('0xe') stored in it. That is right and points to the right pi-model.
After the 'and'-combined with '0x17' the old_rev becomes to '6' and points to the wrong model.

# code  mod   rev    mem      manufacturer
    0x002: ["B", "1.0", "256MB", "Egoman"],
    0x003: ["B", "1.0", "256MB", "Egoman"],
    0x004: ["B", "2.0", "256MB", "Sony UK"],
    0x005: ["B", "2.0", "256MB", "Qisda"],
    0x006: ["B", "2.0", "256MB", "Egoman"],         <- Wrong model shown in moOde
    0x007: ["A", "2.0", "256MB", "Egoman"],
    0x008: ["A", "2.0", "256MB", "Sony UK"],
    0x009: ["A", "2.0", "256MB", "Qisda"],
    0x00d: ["B", "2.0", "512MB", "Egoman"],
    0x00e: ["B", "2.0", "512MB", "Sony UK"],    <- my model
    0x00f: ["B", "2.0", "512MB", "Egoman"],
    0x010: ["B+", "1.2", "512MB", "Sony UK"],
    0x011: ["CM1", "1.0", "512MB", "Sony UK"],
    0x012: ["A+", "1.1", "256MB", "Sony UK"],
    0x013: ["B+", "1.2", "512MB", "Embest"],
    0x014: ["CM1", "1.0", "512MB", "Embest"],
    0x015: ["A+", "1.1", "256MB/512MB", "Embest"]

 


Thanks