| Date | Thu, 13 Dec 2012 15:28:44 -0800 | Subject | Re: [PATCH v6 18/27] x86, boot: add fields to support load bzImage and ramdisk above 4G | From | Yinghai Lu <> |
| |
On Thu, Dec 13, 2012 at 2:54 PM, H. Peter Anvin <hpa@zytor.com> wrote: > > 0x1f0 is unsuitable for use as sentinel -- or in fact for any purpose -- > because it is quite plausible that someone may (fairly sanely) start the > copy range at 0x1f0 instead of 0x1f1... we really should have documented > it that way but it is too late now. > > However, we can use 0x1ef.
right. updated to use 0x1ef.
Thanks
Yinghai [unhandled content-type:application/octet-stream] |