All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] config: Define BOOTP client architecture and VCI for ARMv8
Date: Mon, 23 Mar 2015 14:07:42 -0600	[thread overview]
Message-ID: <5510728E.7000201@wwwdotorg.org> (raw)
In-Reply-To: <20150320170853.GI32541@bill-the-cat>

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@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?

  reply	other threads:[~2015-03-23 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 12:11 [U-Boot] [PATCH] config: Define BOOTP client architecture and VCI for ARMv8 Thierry Reding
2015-03-20 16:22 ` Stephen Warren
2015-03-20 17:08   ` Tom Rini
2015-03-23 20:07     ` Stephen Warren [this message]
2015-03-25 16:58       ` Tom Rini
2015-03-28 18:09 ` [U-Boot] " Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5510728E.7000201@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.