Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: 2015.07 - fix creation of .config
Date: Tue, 11 Aug 2015 12:20:01 +0000	[thread overview]
Message-ID: <1439295600.3252.2.camel@synopsys.com> (raw)
In-Reply-To: <1438600559.13201.4.camel@synopsys.com>

Hi Thomas,

On Mon, 2015-08-03 at 14:15 +0300, Alexey Brodkin wrote:
> Hi Thomas,
> 
> On Fri, 2015-07-31 at 18:14 +0300, Alexey Brodkin wrote:
> > Hi Thomas,
> > 
> > On Fri, 2015-07-31 at 16:18 +0200, Thomas Petazzoni wrote:
> > > Alexey,
> > > 
> > > On Fri, 31 Jul 2015 17:04:35 +0300, Alexey Brodkin wrote:
> > > > Due to recent changes in U-Boot, see
> > > > http://git.denx.de/?p=u-boot.git;a=commit;h=a26cd04920dc069fd6e91abb785426cf6c29f45f
> > > > re-creation of .config from defconfig by "make oldconfig" happened
> > > > incorrectly.
> > > 
> > > Hum, reverting an upstream patch doesn't really seem like a proper
> > > solution for the problem. Also, it will only fix the problem for those
> > > using exactly U-Boot 2015.07, but not for the majority of users who
> > > have to use a vendor-specific U-Boot version (unfortunately).
> > > 
> > > So I believe we need to fix this properly, not by reverting an upstream
> > > patch.
> > 
> > To be honest I think that revert will happen upstream as well.
> > Recently I started discussion on that regard here http://lists.denx.de/pipermail/u-boot/2015-July/221101.html
> > 
> > The point is that problem has to be resolved upstream anyways in that or another way and I'll make sure
> > it happens sooner [I hope] or later. Because you know we prefer to stick to upstream and so we do care upstream
> > projects work for us.
> > 
> > And if [I hope] discussed problem is gone before the next release of Buildroot do we really care
> > how the problem is solved in Buildroot for existing release?
> > 
> > Note that problem I'm attempting to fix doesn't really affect U-Boot compilation or execution.
> > This is only related to its buildsystem. As a developers of U-Boot we [even though it was not I in person
> > behind that patch but I saw this and didn't recognize upcoming problem with oldconfig] wanted to make
> > life of U-Boot users a bit easier [see commit message to the original commit] but that attempt
> > caused problems for those who builds U-Boot in non-standard way [I mean not via "make xxx_defconfig && make"].
> > 
> > Hopefully that comment makes sense.
> > 
> > If not do you think there's a better way to fix a failure on attempt to build vanilla U-Boot v2015.07?
> > 
> > BTW speaking about vendor-specific U-Boot versions I think it's now mostly our legacy now.
> > If I'm not mistaken lots of boards may use vanilla U-Boot. For example Cubieboards and Wandboards
> > (I own these boards and tried vanilla U-boot on them) and many more ARM boards supported in Fedora
> > for ARM like Pandaboard, Olinuxinos etc. So it's just a matter of maintainers of those boards
> > (if we have them at all) to try latest vanilla U-Boot and update defconfigs then if all works.
> 
> Looks like resolution in upstream U-Boot will be with specification of default "platform" for each architecture.
> See http://lists.denx.de/pipermail/u-boot/2015-August/221418.html, 
> http://lists.denx.de/pipermail/u-boot/2015-August/221417.html
> 
> Still this will take quite some time to update all affected 54 Kconfigs.
> 
> So probably proposed patch with revert in Buildroot makes perfect sense as we only build U-Boot but not
> adding new "platforms" etc i.e. proposed patch IMHO won't hurt.
> 
> -Alexey

Any chance for this one to be applied?
Note without this change or anything similar U-Boot from snsp_axs10x_defconfig fails to config.

-Alexey

  reply	other threads:[~2015-08-11 12:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 14:04 [Buildroot] [PATCH] u-boot: 2015.07 - fix creation of .config Alexey Brodkin
2015-07-31 14:18 ` Thomas Petazzoni
2015-07-31 15:14   ` Alexey Brodkin
2015-08-03 11:16     ` Alexey Brodkin
2015-08-11 12:20       ` Alexey Brodkin [this message]
2015-08-12  8:23         ` Thomas Petazzoni
2015-08-16 21:43           ` Jörg Krause
2015-08-17  6:37             ` Alexey Brodkin
2015-08-17  9:31               ` Yann E. MORIN
2015-08-17  9:58                 ` Alexey Brodkin
2015-08-22 22:57           ` Arnout Vandecappelle
2015-08-28  9:36             ` Alexey Brodkin
2015-08-30 20:41             ` Peter Korsgaard
2015-08-30 20:51 ` Peter Korsgaard
2015-08-31 16:43   ` Alexey Brodkin

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=1439295600.3252.2.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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