[U-Boot] [PATCH] config: Define BOOTP client architecture and VCI for ARMv8
Stephen Warren
swarren at wwwdotorg.org
Mon Mar 23 21:07:42 CET 2015
On 03/20/2015 11:08 AM, Tom Rini wrote:
> On Fri, Mar 20, 2015 at 10:22:59AM -0600, Stephen Warren wrote:
>> On 03/20/2015 06:11 AM, Thierry Reding wrote:
>>> From: Thierry Reding <treding at nvidia.com>
>>>
>>> Reuse the 32-bit ARM client architecture and identify ARMv8 specifically
>>> by setting the BOOTP VCI string.
>>
>> Is there a newer version of
>> https://www.rfc-editor.org/rfc/rfc4578.txt that says what this value
>> should be? Even 32-bit ARM isn't in that document, so I'm not sure
>> where 0x100 came from.
>
> I wonder if 0x100 is treated by the PXE implementations as "set but
> invalid, don't use". Digging into some PXE servers would shed some
> light here.
I can't actually find any use of this in ISC DHCPd. At most, it might be
a value that user config files can match against if they want. I guess
it's not worth worrying about?
More information about the U-Boot
mailing list