From f47d805cc3999a98055c9a1ee132a40c2f58d515 Mon Sep 17 00:00:00 2001 From: Matthew Crymble Date: Tue, 10 Sep 2019 15:44:40 -0500 Subject: mpm: fixed mboard_max_revision value This value should be 9 to correspond with the rev J motherboards. This property was renamed to mboard_last_rev_compat in a previous commit. But mboard_max_rev is actually a more accurate description, since it specifies the latest hardware revision that the software is aware of. I renamed all references back to mboard_max_rev. --- mpm/python/usrp_mpm/periph_manager/n3xx.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'mpm/python/usrp_mpm/periph_manager/n3xx.py') diff --git a/mpm/python/usrp_mpm/periph_manager/n3xx.py b/mpm/python/usrp_mpm/periph_manager/n3xx.py index 3e53ba854..3eb9e709c 100644 --- a/mpm/python/usrp_mpm/periph_manager/n3xx.py +++ b/mpm/python/usrp_mpm/periph_manager/n3xx.py @@ -131,7 +131,7 @@ class n3xx(ZynqComponents, PeriphManagerBase): mboard_eeprom_offset = 0 mboard_eeprom_max_len = 256 mboard_info = {"type": "n3xx"} - mboard_last_rev_compat = 5 # last known compat through dt_compat field + mboard_max_rev = 9 # latest HW revision that this version of MPM is aware of mboard_sensor_callback_map = { 'ref_locked': 'get_ref_lock_sensor', 'gps_locked': 'get_gps_lock_sensor', -- cgit v1.2.3