From mboxrd@z Thu Jan  1 00:00:00 1970
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
Date: Tue, 23 Feb 2021 16:54:45 +0100
Subject: [PATCH v3 1/4] arm: x86: qemu: move qfw to DM, include Arm support
In-Reply-To: <20210223145338.GV10169@bill-the-cat>
References: <20210223114329.16729-1-ashe@kivikakk.ee>
 <20210223114329.16729-2-ashe@kivikakk.ee>
 <d26821d4-dc30-2e17-a2dc-67dbaab6beee@gmx.de>
 <20210223145338.GV10169@bill-the-cat>
Message-ID: <1BAE85FA-C9B5-4067-92D5-0A7639DE1663@gmx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Am 23. Februar 2021 15:53:38 MEZ schrieb Tom Rini <trini@konsulko.com>:
>On Tue, Feb 23, 2021 at 01:59:52PM +0100, Heinrich Schuchardt wrote:
>> On 23.02.21 12:43, Asherah Connor wrote:
>> > Updates the QFW driver to use the driver model, and adds support
>for QFW
>> > on Arm platforms by configuring from the device tree and using MMIO
>> > accordingly.  A sandbox driver for QFW is also included, and a
>simple DM
>> > unit test for it.
>> 
>> For which architectures does the fw_cfg device exist?
>> 
>> It it is only ARM and X86, than I am missing such a dependency on
>> CONFIG_CMD_QFW.
>
>The qemu 'qfw' interface is I believe a generic QEMU thing and a
>generic
>U-Boot cleanup would be to have a common QEMU symbol for everyone to
>select.


qemu-system-riscv64 does not allow me to specify a file for the qfw interface.

Best regards

Heinrich