From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Running arm:versatile_defconfig with qemu in linux-next
Date: Thu, 24 Dec 2015 10:58:30 +0100 [thread overview]
Message-ID: <201512241058.30249.arnd@arndb.de> (raw)
In-Reply-To: <567B76E0.6050106@roeck-us.net>
On Thursday 24 December 2015, Guenter Roeck wrote:
> Hi all,
>
> various versatile and realview configurations fail to run for me with
> qemu (2.5) in linux-next. Some of those are qemu configurations
> I collected from various sources, so I guess I am on my own there.
> However, the following standard configurations no longer work.
>
> arm:versatileab:versatile_defconfig
> arm:versatilepb:versatile_defconfig
Just to be sure to rule out the obvious: are you using the dtb files from
the kernel, or do you have your own?
> I can no longer get realview-eb-mpcore and realview-eb to work either,
> but, again, that is with a qemu specific configuration.
These are still based on board files, right? Do the normal defconfigs
work?
> I tried to bisect, but there have been too many related changes in the code
> for it to succeed; some of the bisect attempts don't even compile, others fail
> due to different problems. Is it known if versatile_defconfig in linux-next runs
> on a real system ? If so, any idea what it might take to get it to work again
> with qemu ?
Please start with the next/multiplatform branch in arm-soc, which has the
conversion to devicetree. Let's first see if that works by itself. I would
hope that all commits on that branch build, but something may have gone wrong.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Guenter Roeck <private@roeck-us.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Running arm:versatile_defconfig with qemu in linux-next
Date: Thu, 24 Dec 2015 10:58:30 +0100 [thread overview]
Message-ID: <201512241058.30249.arnd@arndb.de> (raw)
In-Reply-To: <567B76E0.6050106@roeck-us.net>
On Thursday 24 December 2015, Guenter Roeck wrote:
> Hi all,
>
> various versatile and realview configurations fail to run for me with
> qemu (2.5) in linux-next. Some of those are qemu configurations
> I collected from various sources, so I guess I am on my own there.
> However, the following standard configurations no longer work.
>
> arm:versatileab:versatile_defconfig
> arm:versatilepb:versatile_defconfig
Just to be sure to rule out the obvious: are you using the dtb files from
the kernel, or do you have your own?
> I can no longer get realview-eb-mpcore and realview-eb to work either,
> but, again, that is with a qemu specific configuration.
These are still based on board files, right? Do the normal defconfigs
work?
> I tried to bisect, but there have been too many related changes in the code
> for it to succeed; some of the bisect attempts don't even compile, others fail
> due to different problems. Is it known if versatile_defconfig in linux-next runs
> on a real system ? If so, any idea what it might take to get it to work again
> with qemu ?
Please start with the next/multiplatform branch in arm-soc, which has the
conversion to devicetree. Let's first see if that works by itself. I would
hope that all commits on that branch build, but something may have gone wrong.
Arnd
next prev parent reply other threads:[~2015-12-24 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 4:38 Running arm:versatile_defconfig with qemu in linux-next Guenter Roeck
2015-12-24 4:38 ` Guenter Roeck
2015-12-24 9:58 ` Arnd Bergmann [this message]
2015-12-24 9:58 ` Arnd Bergmann
2015-12-24 15:33 ` Guenter Roeck
2015-12-24 15:33 ` Guenter Roeck
2015-12-24 19:51 ` Guenter Roeck
2015-12-24 19:51 ` Guenter Roeck
2015-12-24 23:04 ` Peter Maydell
2015-12-24 23:04 ` Peter Maydell
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=201512241058.30249.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.