From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43533) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vw03k-0003GW-7A for qemu-devel@nongnu.org; Wed, 25 Dec 2013 20:48:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vw03f-0008Bx-6M for qemu-devel@nongnu.org; Wed, 25 Dec 2013 20:48:24 -0500 Received: from [222.73.24.84] (port=40664 helo=song.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vw03e-0008Br-Qv for qemu-devel@nongnu.org; Wed, 25 Dec 2013 20:48:19 -0500 Message-ID: <52BB8A75.8000506@cn.fujitsu.com> Date: Thu, 26 Dec 2013 09:46:29 +0800 From: Li Guang MIME-Version: 1.0 References: <1387960503-11838-1-git-send-email-lig.fnst@cn.fujitsu.com> <52BB74E5.8010602@cn.fujitsu.com> <52BB7AC0.5080909@cn.fujitsu.com> In-Reply-To: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8; format=flowed Subject: Re: [Qemu-devel] [PATCH] allwinner-a10: add config script support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Peter Crosthwaite , QEMU Developers Peter Maydell wrote: > On 26 December 2013 01:09, Peter Crosthwaite > wrote: > >> Can you just provide a generic solution to the "blob some random data >> into RAM" problem (If one doesn't exist already)? >> > Well, we do already have that (see -machine firmware=whatever), but... > > Yes, right. >> I think your binary file here can then just be treated as any other >> binary boot product and kept outside of QEMU. >> > ...it's much easier to keep the blob outside QEMU because otherwise > it has to have a git submodule and be built somehow and is generally > a bit of a faff. > > Is this FEX stuff actually supported by the upstream Linux kernel? > Googling mostly produced a bunch of stuff from a mid-year flamewar. > I definitely don't think we should add any special support for it in > QEMU if it's just some random thing that isn't going to be upstreamed. > > OK, I will use firmware=script.bin option, thanks!