All of lore.kernel.org
 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 21:41:07 -0700	[thread overview]
Message-ID: <4193ce56-e3f8-d3f7-52a1-170f2d9185bb@roeck-us.net> (raw)
In-Reply-To: <20180628041217.qxlspqzqfm4gszxd@toto>

On 06/27/2018 09:12 PM, Edgar E. Iglesias wrote:
> On Wed, Jun 27, 2018 at 05:34:15PM -0700, Guenter Roeck wrote:
>> 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.
> 
> I used the one from QEMU. IIRC, there's some offsetting going on there
> that differs between the Xilinx version and the PC version of these
> UARTs...

Yes, I noticed after I sent the previous e-mail.

> 
> Can you try again and see how it goes?
> If it doesn't work, I can share my kernel Image and we can compare from there.
> 

I tried lots of things, nothing worked. Until I got your e-mail, tried again,
and suddenly it works just great. Go figure. Turns out I had used a big endian
toolchain to build a little endian target. Shameface.

I do get this odd gcc warning:

cc1: warning: -mxl-multiply-high can be used only with -mcpu=v6.00.a or greater

Actual parameters are "-mcpu=v10.0 -mxl-multiply-high", so that doesn't really make
sense to me. I tried various toolchains, all with the same result. Any idea what
that is about ?

Thanks,
Guenter

      reply	other threads:[~2018-06-28  4:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 18:52 Linux kernel configurations for various Microblaze systems Guenter Roeck
2018-06-27 18:52 ` [Qemu-devel] " Guenter Roeck
2018-06-27 20:01 ` Philippe Mathieu-Daudé
2018-06-27 20:01   ` 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
2018-06-28  4:12         ` Edgar E. Iglesias
2018-06-28  4:41           ` Guenter Roeck [this message]

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=4193ce56-e3f8-d3f7-52a1-170f2d9185bb@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 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.