| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
- change scoping of product_map in n3xx
|
| | |
|
| |
|
|
|
|
| |
Since there is no simple mapping from an arbitrary tuple of mboard- and
dboard info dictionaries, we use generate_device_info() to figure out
the product key.
|
| |
|
|
|
|
| |
In the N3xx series, the motherboard ID and the device ID can differ. For
example, the N310 could share the same motherboard with a different
device that uses different daughterboards.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Bump maximum supported motherboard revision to 5 (RevF),
to support upcoming motherboard revisions.
Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
|
| | |
|
| | |
|
| |
|
|
| |
Reviewed-by: Martin Braun <martin.braun@ettus.com>
|
| |
|
|
|
|
| |
Adding address offset to all MBoard and DBoard EEPROM reads. This
matches what we're doing for the user portion of the EEPROM, and
allows us to share access to an EEPROM.
|
| | |
|
| |
|
|
|
| |
The N300-variant has no front-panel LO connectors, so we need to warn
ther user when trying to use them.
|
| |
|
|
|
|
| |
The log output at level 'INFO' was pretty cluttered. This cleans up the
log messages at the higher levels. In some cases, log message typos or
capitalizations were also fixed.
|
|
|
This module (and class) are, in fact, used for all N3xx-derivates so
renaming it is the more correct thing to do.
|
