From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Fri, 20 Mar 2015 10:22:59 -0600
Subject: [U-Boot] [PATCH] config: Define BOOTP client architecture and
 VCI for ARMv8
In-Reply-To: <1426853518-30227-1-git-send-email-thierry.reding@gmail.com>
References: <1426853518-30227-1-git-send-email-thierry.reding@gmail.com>
Message-ID: <550C4963.5030507@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 03/20/2015 06:11 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@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.

http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.txt 
lists RFC4578 as the document that defines these options, so I guess 
values have never been allocated for ARM?