07.12.2016 01:52, Daniel Kiper пишет: > u_phys is used just in two places and sometimes it may confuse reader. > Additionally, GRUB multiboot2 implementation does not use u_phys anywhere. > So, replace it with basic well defined and used in implementation u32 type. > > Signed-off-by: Daniel Kiper <daniel.ki...@oracle.com> > --- > doc/multiboot.texi | 11 ++++------- > 1 file changed, 4 insertions(+), 7 deletions(-) > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > index 4b92918..2bda9b7 100644 > --- a/doc/multiboot.texi > +++ b/doc/multiboot.texi > @@ -299,9 +299,6 @@ little-endian, u32 is coded in little-endian. > The type of unsigned 64-bit data. Because the target architecture is > little-endian, u64 is coded in little-endian. > > -@item u_phys > -The type of unsigned data of the same size as target architecture physical > address size. > - > @item u_virt > The type of unsigned data of the same size as target architecture virtual > address size. >
So if I understand it correctly, any address used in multiboot2 is limited to 32 bit, so anything that is relevant to boot protocol must reside below 4G. Is my assumption correct? _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel