qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Arthur Tumanyan <arthurtumanyan@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org, andrew.smirnov@gmail.com
Subject: Re: How to use designware-root-port and designware-root-host devices ?
Date: Fri, 21 Jun 2024 11:30:14 +0200	[thread overview]
Message-ID: <76070bb3-abf6-491a-a9f3-549f615e23fd@redhat.com> (raw)
In-Reply-To: <CAFEAcA-TV6MKC32zd3WP5yhLABkbDrLKtP7CCZ0kB5pbV+-5Vg@mail.gmail.com>

On 21/06/2024 11.16, Peter Maydell wrote:
> On Fri, 21 Jun 2024 at 08:07, Arthur Tumanyan <arthurtumanyan@gmail.com> wrote:
>>
>> Hi,
>>
>> I just tried to run mcimx7d-sabre machine this way:
>>
>> ${HOME}/cosim/usr/local/bin/qemu-system-arm -M mcimx7d-sabre -m 2G \
>> -kernel ${HOME}/cosim-arm/buildroot/output/images/uImage \
>>          --initrd ${HOME}/cosim-arm/buildroot/output/images/rootfs.cpio.gz \
>> -nographic \
>> -net nic -net user
>>
>> and it just prints this and do nothing: qemu-system-arm: warning: nic imx.enet.1 has no peer
>>
>> Based on what I see in the mcimx7d-sabre.c , it configures just very basic things, no PCIe at all (may be I'm wrong ;) )
> 
> The machine model in mcimx7d-sabre.c creates the SoC object
> (TYPE_FSL_IMX7). It's the code for that in hw/arm/fsl-imx7.c
> that creates all the SoC devices including the PCIe controller.
> (This structure is similar to real hardware where you have a
> board, which has one or two chips on it like RAM but most of
> the complicated stuff is inside the one big SoC chip.)
> 
>> Is there any idea what goes wrong here ? Maybe someone has experience with running this machine ?
> 
> "No output" usually means "your guest kernel is not configured
> correctly for this machine type", and/or possibly "you didn't
> tell the kernel to output on the serial port".

By the way, it seems like we don't even have an avocado test for that 
machine available. Peter, do you know whether there is a kernel for this 
machine available somewhere that we could use for testing?

  Thomas




  reply	other threads:[~2024-06-21  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  8:28 How to use designware-root-port and designware-root-host devices ? Arthur Tumanyan
2024-06-20 17:34 ` Thomas Huth
2024-06-20 19:05   ` Peter Maydell
2024-06-20 19:37     ` Arthur Tumanyan
2024-06-21  7:07       ` Arthur Tumanyan
2024-06-21  9:16         ` Peter Maydell
2024-06-21  9:30           ` Thomas Huth [this message]
2024-06-25  7:52             ` Arthur Tumanyan

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=76070bb3-abf6-491a-a9f3-549f615e23fd@redhat.com \
    --to=thuth@redhat.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=arthurtumanyan@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).