[Top][All Lists]

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

Re: [Qemu-devel] How to generate custom fw paths for IDE devices?

From: Mark Cave-Ayland
Subject: Re: [Qemu-devel] How to generate custom fw paths for IDE devices?
Date: Thu, 19 Jul 2018 17:46:17 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

On 19/07/18 09:10, Thomas Huth wrote:

On 18.07.2018 23:13, Mark Cave-Ayland wrote:
Hi all,

Following on from a couple of patches I've previously posted to the
mailing list at
https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg08836.html I've
made some good progress with trying to add bootindex support to OpenBIOS
but I'm stuck with generating the IDE device paths from QEMU.

According to OpenBIOS the device path for a cdrom on a sun4u machine
should be:


whereas with my working patchset I'm currently generating:


The issue is that the address@hidden part is being generated by the IDE drive
device attached to the IDE bus in hw/ide/qdev.c, and so I think I need
to override idebus_get_fw_dev_path() to manually generate the remainder
of the path including both the controller and the correctly named drive

One option may be to consider subclassing IDEBus and overriding
idebus_get_fw_dev_path() there, but the cmd646 device is a child of
TYPE_PCI_IDE which has its own internal IDEBus and so it seems
overriding it is impossible.

Can anyone point me in the right direction as to how to generate the
correct fw path for IDE devices in the above format for sun4u machines?

Not sure if it is of any help, but the pseries machine is also rewriting
the device paths for the device tree: See function spapr_get_fw_dev_path
in hw/ppc/spapr.c.

Ah I see - this is very useful indeed, as it seemingly allows all the fw paths to be managed in a single place without having to add Bus support. Thanks for the reference!



reply via email to

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