From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] net: Move the VCI and client arch values to Kconfig
Date: Fri, 6 May 2016 11:38:09 -0400 [thread overview]
Message-ID: <20160506153809.GG24828@bill-the-cat> (raw)
In-Reply-To: <612a8297-09b0-71a4-ccc6-2ab67c9b3b81@suse.de>
On Fri, May 06, 2016 at 05:22:28PM +0200, Alexander Graf wrote:
>
>
> On 06.05.16 16:54, Tom Rini wrote:
> > On Wed, May 04, 2016 at 07:10:52PM +0200, Alexander Graf wrote:
> >
> >> We have a bunch of boards that define their vendor class identifier and
> >> client archs in the board files or in the distro config. Move everything
> >> to the generic Kconfig options.
> >
> > This part is good and fine, thanks. Can you please do a follow-up to
> > convert CONFIG_SPL_NET_VCI_STRING as well?
> >
> >> We're missing the distinction between i386 and x86_64, as I couldn't find
> >> any config variable that would tell us the difference. Is that really important
> >> to people? I guess not, so I left it out.
> >
> > This part however is is from the RFC (and ARM isn't in it, so 0x100 is
> > special magic). See https://tools.ietf.org/html/rfc4578 section 2.1. I
> > suppose reading that now, the right value to use here for your use case
> > actually makes what we're doing now a little harder as "Intel x86PC" is
> > 0x0, and "EFI IA32" is 0x6. Or we could, if I'm reading the RFC right,
> > just drop this part of the code entirely.
>
> Which part? Just drop the ID? Definitely works for me :)
Ah, oops, nope, read the section too quickly. We MUST have this
present. So we should try and make it correct which in your case means
nothing yet, but you could future proof things with:
default 0x6 if EFI_LOADER && X86
default 0x0
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160506/8b6e1215/attachment.sig>
next prev parent reply other threads:[~2016-05-06 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 17:10 [U-Boot] [PATCH 0/4] efi_loader: PXE boot support Alexander Graf
2016-05-04 17:10 ` [U-Boot] [PATCH 1/4] efi_loader: Add network access support Alexander Graf
2016-05-04 17:10 ` [U-Boot] [PATCH 2/4] bootp: Move vendor class identifier set to function Alexander Graf
2016-05-06 17:48 ` Tom Rini
2016-05-04 17:10 ` [U-Boot] [PATCH 3/4] net: Move the VCI and client arch values to Kconfig Alexander Graf
2016-05-06 14:54 ` Tom Rini
2016-05-06 15:22 ` Alexander Graf
2016-05-06 15:38 ` Tom Rini [this message]
2016-05-06 16:07 ` Alexander Graf
2016-05-06 16:07 ` Leif Lindholm
2016-05-06 16:57 ` Tom Rini
2016-05-04 17:10 ` [U-Boot] [PATCH 4/4] distro: Add efi pxe boot code Alexander Graf
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=20160506153809.GG24828@bill-the-cat \
--to=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox