summaryrefslogtreecommitdiffstats
path: root/sys/dev/sfxge/common/efx_intr.c
diff options
context:
space:
mode:
authorarybchik <arybchik@FreeBSD.org>2016-01-14 14:14:00 +0000
committerarybchik <arybchik@FreeBSD.org>2016-01-14 14:14:00 +0000
commite2384e74e400d55ae8a22df33913f9f4c9ca33a4 (patch)
treee28e2d21348bc6c51a1495613dc8f6d9a3b65ce9 /sys/dev/sfxge/common/efx_intr.c
parent69ebdbc002d69ce3173ceec803afdd44443ed230 (diff)
downloadFreeBSD-src-e2384e74e400d55ae8a22df33913f9f4c9ca33a4.zip
FreeBSD-src-e2384e74e400d55ae8a22df33913f9f4c9ca33a4.tar.gz
MFC r291432
sfxge: modify nvram update functions for uio platform to support RFID-selectable presets Dynamic config partitions on boards that support RFID are divided into a number of segments, each formatted like a partition, with header, trailer and end tags. The first segment is the current active configuration. The segments are initialised by manftest and each contain a different configuration e.g. firmware variant. The firmware can be instructed via RFID to copy a segment over the first segment, hence changing the active configuration. This allows ops to change the configuration of a board prior to shipment using RFID. Changes to the dynamic config may need to be written to all segments (in particular firmware versions written by manftest) or just the first segment (changes to the active configuration). See SF-111324-SW. If only the first segment is written the code still needs to be aware of the possible presence of subsequent segments as writing to a segment may cause its size to increase, which would overwrite the subsequent segments and invalidate them. Boards that do not support RFID will only have one segment in their dynamic config partition. Submitted by: Paul Fox <pfox at solarflare.com> Sponsored by: Solarflare Communications, Inc.
Diffstat (limited to 'sys/dev/sfxge/common/efx_intr.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud