[roll] Roll fuchsia [kernel][phys] Truncate NVRAM when kernel.memory-limit-mb is set

physboot currently forwards the NVRAM range to the kernel proper as it
existed in the ZBI without taking into account the possible truncation
of the physical address space that may have been performed in handling
kernel.memory-limit-mb.

Original-Fixed: 350747248
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1086919
Original-Revision: af86896ab3e5562809216731d8c4b14542f18eaa
GitOrigin-RevId: 1e8867e4758e48d3c0f9b4224c54f0101a176620
Change-Id: Iaee3611741f2d4c4c2e3c6c78ea5bfe16905bada
1 file changed
tree: 976a55e1c0376b4807d2b4151a5ea1e8a69ffe3e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.