On 16/11/2026 18:20, Ahmad Byagowi wrote:
Match WiWi 2163:1008, subsystem 10ee:0007, without a class filter.
Resolve WiWi devices against the static PCI table so a dynamic ID
cannot substitute an unrelated resource layout. NetTimeLogic uses the PCI
Revision ID for incompatible interface changes. Revision 02 identifies
the LitePCIe/MSI-X interface; the Xilinx subsystem ID and FPGA build
number do not identify the register interface. Reject unknown revisions
and check BAR0 and the MSI-X layout before accessing FPGA registers.
Do not probe a CoreList or require exact versions of individual cores.
Report the full 32-bit image ID as the running firmware build. Derive
signal and frequency capabilities from the supported revision, not the
legacy FB build-number thresholds. This ID does not identify the boot
slot. Retain legacy version reporting on other cards.
WiWi shares the peripheral resource table used by the existing Celestica
entry (18d4:1008), not its PCI addressing and interrupt scheme.
For WiWi only, translate peripheral offsets by 0x02000000 and interrupt
inputs by 32.
Let's not do this magic. If addressing and interrupt schema differ then
it means another resource table. If there is a way to make it flexible,
let's do it compile-time only.
Use aligned 32-bit UART I/O and typed XIIC platform
data, sharing the EEPROM list but not casting another controller's data.
Do not expose an unvalidated second GNSS UART or PPS output source.
Why it's not a problem for ADVA and ART boards?
Keep the external SMA PPS2 input. The PCI revision identifies the host
interface, not optional board wiring. Use hardware selector values for
WiWi DPLL routing; preserve the existing behavior on other boards.
Enable the three UART and XIIC inputs during probe. Reject attempts to
arm a timestamper or generator with -EAGAIN until the timing gate write
has been flushed. This avoids relying on FPGA replay of a pulse caused
by a userspace request made while the gate was closed.
Why is it a problem for new revision but not for the older ones?
Do not register the WiWi SPI flash controller or enable its interrupt.
This prevents the driver from exposing raw MTD access to the golden
image. Reject devlink flash as well. The update format and controller
support are not validated; read access via MTD is intentionally lost.
Is there a process to actually enable flash upgrades?