Lines Matching full:it
44 update it on each BMC generation, have all the quirks for all the flash
51 3. It's very hard to support "BMC reboots" when doing that
53 4. It's slow
56 risk. It means the host can access any address on the BMC internal bus and
60 flash too as nothing can be trusted. So we want to disable it.
80 window and which offset into the flash it maps.
83 0x3000\_0000) or it can be a window to a RAM image of a flash. It doesn't have
85 it to various parts of the flash) but if it's set to map the actual flash
86 controller space at 0x3000\_0000, it's probably simpler to make it the full
87 flash. The host makes no assumption, it's your choice what to provide. The
91 defined in the spec, but it should be at least one block (4k for now but it
100 Finally, there is a `RESET_STATE`. It's the state in which the bootloader in the
101 SEEPROM of the POWER9 chip will find what it needs to load HostBoot. The
182 the host to notify it of a response.
198 thing it should do it call MBOX_GET_INFO in order to establish the protocol
204 host requests access to a section of flash. It is worth noting that the host
205 can only ever have one window that it is accessing at a time - hence forth
219 multiple of block size it is necessary for the host and BMC to agree on a
220 protocol version as this determines the block size. In V1 it is hard coded at
239 the flash offset it would like to access with the CREATE_{READ,WRITE}_WINDOW
240 commands. The host may give a hint as to how much data it would like to access
255 window and the host must not access the LPC window after it has been closed.
258 window then the active window is closed (and implicitly flushed if it was a
259 write window). If the new window is successfully opened then it is the new
272 within the write window it has modified. The host may also use the
275 reads from an area it has erased that the read values are 0xFF. Any part of the
279 or must on a call to WRITE_FLUSH flush the changes which it has been notified
300 Locked flash regions must persist across a BMC reboot or daemon restart. It is
306 host a change in state which it should take notice of. The host must (if
307 possible for the given event) acknowledge it to inform the BMC it has been
315 active window it has been closed by the BMC and if it was a write window
316 then the host must not assume that it was flushed unless a previous explicit
370 above. However, it is not an error if the BMC receives a `GET_MBOX_INFO` with an
373 response it must consider any in-progress commands to have failed. The host may
410 In V2 it is variable and must be queried with the GET_MBOX_INFO command.
411 In V3 the host can request a given block size however it is ultimately up to
414 host to request a block size is provided such that it can choose an appropriate
437 This command is designed to inform the BMC that it should put
439 use it. Currently, this means pointing back to BMC flash
478 it should wait after issuing a command to the BMC before it
480 which the BMC thinks it could take to service any command which
487 may use this to select the block size which it will use however
488 is free to ignore it. The value in the response is the block
535 taken from the start of flash - that is it is an absolute
539 address space - that is it is an absolute address.
549 requested by the host. It is the responsibility of the host
553 BMC is free to create any sized window but it must contain
559 is the active window. If it fails then there is no active
608 the daemon of where and when a write has occurred so it
617 erase a flash area before writing to it by setting ARG[4]. This
619 and will not try to erase it before hand. This can be used if
706 Lock an area of flash so that the host can't mark it dirty or
715 If the BMC needs to tell the host something then it simply
717 on that register, or otherwise be polling it.
743 must assume it has no active window. The host must not assume
747 that it no longer has an active window. The host is not
764 The BMC daemon must clear this bit itself when it regains
765 control of the flash (the host isn't able to clear it
773 clear it before it terminates (assuming it didn't
778 will respond as it or the BMC may have crashed without clearing
779 it.