mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Guenter Roeck <linux@roeck-us.net>,
	Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>,
	"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
Cc: Michal Simek <monstr@monstr.eu>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
	Alistair Francis <alistair@alistair23.me>,
	KONRAD Frederic <frederic.konrad@adacore.com>
Subject: Re: [Qemu-devel] Linux kernel configurations for various Microblaze systems
Date: Wed, 27 Jun 2018 17:01:34 -0300	[thread overview]
Message-ID: <96809884-2f46-ed63-48fd-9fd4c5050e20@amsat.org> (raw)
In-Reply-To: <20180627185248.GA19743@roeck-us.net>


[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]

Hi Guenter,

On 06/27/2018 03:52 PM, Guenter Roeck wrote:
> Hi,
> 
> I would like to add Microblaze "petalogix-ml605" and "xlnx-zynqmp-pmu"
> to my list of qemu boot tests of upstream and stable release kernels.

Do you mind sharing your tests on this thread?

"Who is running QEMU automated tests, and when?"
http://lists.nongnu.org/archive/html/qemu-devel/2018-04/msg04695.html

> Unfortunately I have been unable to locate working kernel configurations
> for the those systems, nor working qemu command lines. I found a few links,
> but they are all dead.

I got more lucky using the Xilinx downstream code from:
https://github.com/Xilinx

In particular using their downstream DeviceTree:

https://github.com/Xilinx/device-tree-xlnx

I also used those links:

http://www.wiki.xilinx.com/MicroBlaze
http://www.wiki.xilinx.com/Build%20kernel

Regards,

Phil.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-06-27 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 18:52 Guenter Roeck
2018-06-27 20:01 ` Philippe Mathieu-Daudé [this message]
2018-06-27 20:59   ` [Qemu-devel] " Guenter Roeck
2018-06-27 22:47     ` Edgar E. Iglesias
2018-06-28  0:34       ` Guenter Roeck
2018-06-28  4:12         ` Edgar E. Iglesias
2018-06-28  4:41           ` Guenter Roeck

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=96809884-2f46-ed63-48fd-9fd4c5050e20@amsat.org \
    --to=f4bug@amsat.org \
    --cc=alistair@alistair23.me \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=frederic.konrad@adacore.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=monstr@monstr.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=sai.pavan.boddu@xilinx.com \
    /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
all inboxes | Powered by JetHome®