qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
	"Andrew Jeffery" <andrew@aj.id.au>,
	"Joel Stanley" <joel@jms.id.au>
Cc: "Ninad Palsule" <ninad@linux.ibm.com>,
	"Cameron Esfahani via" <qemu-devel@nongnu.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé via" <qemu-arm@nongnu.org>
Subject: Re: [PATCH v3 1/1] hw/arm/aspeed:Add vpd data for Rainier machine
Date: Thu, 25 May 2023 14:57:43 -0500	[thread overview]
Message-ID: <ba1e794c-ee3a-0dff-b008-7fac4b007255@linux.vnet.ibm.com> (raw)
In-Reply-To: <164e53c1-03dd-a530-8c91-357a10517556@kaod.org>

Hello Cedric,


On 5/25/23 1:37 AM, Cédric Le Goater wrote:
> [ ... ]
>
>> However, regarding Cédric's log above, a reboot is expected on the first
>> boot of a fresh image when there's valid VPD available. For the first
>> boot of a fresh image we configure the kernel with a minimal devicetree
>> that allows us to read the VPD data. This determines the system we're
>> actually on and configures an appropriate devicetree for subsequent
>> boots. We then reboot to pick up the new devicetree.
>
> Yes. Then, the behavior looks correct under QEMU :
>
>   https://www.kaod.org/qemu/aspeed/rainier/rainer.log
>
> Here are the services which still have with some issues :
>
> * clear-once.service                loaded failed failed          
> Clear one time boot overrides
> * ncsi-linkspeed@eth0.service       loaded failed failed          Set 
> eth0 gigabit link speed
> * ncsi-linkspeed@eth1.service       loaded failed failed          Set 
> eth1 gigabit link speed
> * obmc-flash-bios-init.service      loaded failed failed          
> Setup Host FW directories
> * system-vpd.service                loaded failed failed          
> System VPD Collection
> * trace-enable.service              loaded failed failed          
> Enable Linux trace events in the boot loader

On my system system-vpd.service was active. I couldn't run your build on 
my development machine.

I am still checking it.

>
> C.
>
>
>
>


  reply	other threads:[~2023-05-25 19:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 21:45 [PATCH v3 0/1] Add vpd data for Rainier machine Ninad Palsule
2023-05-23 21:45 ` [PATCH v3 1/1] hw/arm/aspeed:Add " Ninad Palsule
2023-05-24  6:36   ` Cédric Le Goater
2023-05-24  7:44     ` Joel Stanley
2023-05-24  8:35       ` Cédric Le Goater
2023-05-25  0:30       ` Andrew Jeffery
2023-05-25  6:37         ` Cédric Le Goater
2023-05-25 19:57           ` Ninad Palsule [this message]
2023-05-26  6:18             ` Cédric Le Goater
2023-06-01 14:36               ` Ninad Palsule
2023-05-25  1:26     ` Ninad Palsule

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=ba1e794c-ee3a-0dff-b008-7fac4b007255@linux.vnet.ibm.com \
    --to=ninad@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=joel@jms.id.au \
    --cc=ninad@linux.ibm.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).