Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/zynq_zybo: remove defconfig
Date: Fri, 22 Feb 2019 22:15:17 +0100	[thread overview]
Message-ID: <20190222221517.70b6a3b3@windsurf> (raw)
In-Reply-To: <CADvTj4oyc=3ThQ++0CcS+wiYuQrc0sB=67aBamPdPiZjYGMv1w@mail.gmail.com>

Hello,

On Fri, 22 Feb 2019 13:54:11 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:

> On Fri, Feb 22, 2019 at 1:44 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> >
> > This defconfig was added in October 2016 and was never updated since
> > then. It currently fails to build because U-Boot is too old and
> > doesn't build with host-openssl in version 1.1.x.  
> You can probably just replace uboot with this version
> https://github.com/Xilinx/u-boot-xlnx/tree/xilinx-v2018.3 for xilinx
> devices like these.

I'm pretty sure mainline U-Boot has support for this board, so it's not
really the problem. The thing is that defconfigs are meant to be tested
on real HW. Since I don't have this HW, and the original submitter
didn't reply, there is not much I can do except suggesting to drop the
defconfig. Either someone with the HW platform steps in, fixes the
build issue and checks that the new U-Boot version runs OK on the HW,
or we simply drop the defconfig.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-02-22 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 20:44 [Buildroot] [PATCH] configs/zynq_zybo: remove defconfig Thomas Petazzoni
2019-02-22 20:54 ` James Hilliard
2019-02-22 21:15   ` Thomas Petazzoni [this message]
2019-02-22 21:20   ` Peter Korsgaard
2019-02-22 21:19 ` Peter Korsgaard

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=20190222221517.70b6a3b3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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