Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/qemu: bump relevant config versions
Date: Sat, 05 Oct 2013 10:11:27 -0300	[thread overview]
Message-ID: <52500FFF.9060603@zacarias.com.ar> (raw)
In-Reply-To: <87wqlsituj.fsf@dell.be.48ers.dk>

On 10/04/2013 06:55 PM, Peter Korsgaard wrote:

> I'm not sure what went wrong here. You renamed a bunch of Linux
> configuration files, but you didn't update the defconfigs to match.
> 
> I tested arm versatile with 3.11 and it didn't boot for me, so I've
> changed the Linux configuration file names back to 3.10 rather than
> adjusting the defconfigs.

I've probably made some mistake when moving things around before doing
the commit.
That said it's working fine with 3.11.3 + qemu 1.6.0 for me, i do
extensive tests before sending this series.
I've placed some of my generated images at
https://www.zacarias.com.ar/buildroot-qemu/ if you want to give those a
try (or someone else to see if there's a pattern with qemu version or
distribution).
Maybe it's time we do a host-qemu for these to make it more
predictable/concise. There's always some breakage when there's a new
qemu version or kernel series and since we can't control which version
each distribution has it's problematic IMHO.
Regards.

  reply	other threads:[~2013-10-05 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 12:49 [Buildroot] [PATCH] configs/qemu: bump relevant config versions Gustavo Zacarias
2013-10-04 13:05 ` Peter Korsgaard
2013-10-04 21:55 ` Peter Korsgaard
2013-10-05 13:11   ` Gustavo Zacarias [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-10 14:14 Gustavo Zacarias
2013-10-10 20:44 ` Peter Korsgaard
2013-07-07 22:34 Gustavo Zacarias
2013-07-08  6:33 ` 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=52500FFF.9060603@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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