qemu-arm
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3 1/1] hw/arm/aspeed:Add vpd data for Rainier machine


From: Cédric Le Goater
Subject: Re: [PATCH v3 1/1] hw/arm/aspeed:Add vpd data for Rainier machine
Date: Fri, 26 May 2023 08:18:44 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0

On 5/25/23 21:57, Ninad Palsule wrote:
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.

That's how I run it :

  qemu-system-arm -M rainier-bmc -net user -drive 
file=./mmc-p10bmc.qcow2,format=qcow2,if=sd,id=sd2,index=2 -nographic -snapshot 
-serial mon:stdio

You will need to use my branch to have emmc support.

Thanks,

C.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]