[roll] Roll fuchsia [kernel][x86] Fix off-by-one in MMIO and IOPORT resource allocator ranges The last parameter for InitializeAllocator is the size/count of all valid addresses in the range (not the final valid address). This fixes the off-by-one error and allows the final address of the range to be part of a valid allocation. This was discovered on an AMD system which happens to have a PCI range that uses the final IOPORT address. Test: The PCI driver is able to successfully allocate its BAR region and initialize on my Strix Halo (AMD Ryzen AI Max+ 395). Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1556634 Original-Revision: 7aeaaa8c58ee91e500dd40cc89e6ffacef8315df GitOrigin-RevId: 11ae6137874b16ab087aebe0aa2de979c840ebde Change-Id: I37e4601af58b409c88c9fa10acb9264d71d96be8
This repository contains Fuchsia's Global Integration manifest files.
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 in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.