mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Sai Pavan Boddu" <sai.pavan.boddu@xilinx.com>,
	"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
	"Michal Simek" <monstr@monstr.eu>,
	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:34:15 -0700	[thread overview]
Message-ID: <ae120580-01f2-672d-edc0-440c2dd3f248@roeck-us.net> (raw)
In-Reply-To: <20180627224718.ewamlt42kvyirhjw@toto>

Hi Edgar,

On 06/27/2018 03:47 PM, Edgar E. Iglesias wrote:

> 
> Hi Guenter,
> 
> Re: ml605
> The thing to watch out for with kernel configs for microblaze systems is the
> physmem address setting. Unfortunately the kernel does not auto-detect this.
> 
> I'm attaching a kernelconfig for the ml605 that works for me and a qemu commandline.
> 
> qemu-system-microblazeel -M petalogix-ml605 -m 256 -serial mon:stdio -dtb petalogix-ml605.dtb -kernel arch/microblaze/boot/linux.bin -append rdinit=/bin/sh
> 

Can you also send me the dtb file or even better its source ? I don't think
the one in qemu is correct. It lists the serial port at 0x83e00000, but qemu
instantiates it at 0x83e01000.

> Re: pmu
> The PMU board does not run Linux, it runs baremetal power-management related firmware.
> 

Ah, good to know.

Thanks!
Guenter


  reply	other threads:[~2018-06-28  0:34 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 ` [Qemu-devel] " Philippe Mathieu-Daudé
2018-06-27 20:59   ` Guenter Roeck
2018-06-27 22:47     ` Edgar E. Iglesias
2018-06-28  0:34       ` Guenter Roeck [this message]
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=ae120580-01f2-672d-edc0-440c2dd3f248@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=alistair@alistair23.me \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=f4bug@amsat.org \
    --cc=frederic.konrad@adacore.com \
    --cc=linux-kernel@vger.kernel.org \
    --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®