From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: Li Guang <lig.fnst@cn.fujitsu.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] allwinner-a10: add config script support
Date: Fri, 27 Dec 2013 10:54:38 +1000 [thread overview]
Message-ID: <CAEgOgz75wtXuvtrDWLDBRay8aLGRXifyHAg6FqLci_96=H4=mw@mail.gmail.com> (raw)
In-Reply-To: <52BCC812.3080201@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
On Dec 27, 2013 10:24 AM, "Li Guang" <lig.fnst@cn.fujitsu.com> wrote:
>
> Peter Maydell wrote:
>>
>> On 26 December 2013 19:40, Hans de Goede<hdegoede@redhat.com> wrote:
>>
>>>
>>> I'm one of the linux-sunxi developers, the only reason we've
>>> this fex file abomination, is because we've inherited it
>>> from the android-allwinner sources.
>>>
>>
>> Thanks for the clarification; I suspected that might be the case.
>>
>>
>>>
>>> Currently most of the linux-sunxi developers are no longer
>>> focusing on the 3.4 android/allwinner derived sources we
>>> maintain. They are currently in a "good enough for everyday
>>> use" state.
>>>
>>> So now most of us are focusing on getting *proper* sunxi
>>> SoC support upstream. This is using device-tree. Currently
>>> we've working timers, interrupt-controller, uarts, mmc,
>>> sata, nic (both 100mbit and Gbit variants), ehci controller
>>> and builtin rtc support with upstream kernels. Which I
>>> believe likely covers everything the qemu emulation offers
>>> atm. For those interested, see:
>>> https://github.com/linux-sunxi/linux-sunxi/commits/sunxi-devel
>>>
>>> And the mailinglist reports about progress in that branch.
>>>
>>> From the linux-sunxi pov fex files are a legacy thing which
>>> will go away in the future.
>>>
>>
>> Given that, my preference would be to not support fex
>> file loading in QEMU.
>>
>>
>>
>
>
> that means we don't care legacy script which already be used
> in most of cases?
>
Your bootstrap process is just "blob this file at this address" which to me
is legitimate generic functionality. If you implement arbitrary file
blobbing on Cmd line there are many applications across all archs and
plats. and you fex case can be done without any allwinnerisms in tree.
I have use cases for this myself (mainly for emulating handoff in AMP
systems - two guests).
Regards
Peter
>
>
[-- Attachment #2: Type: text/html, Size: 2732 bytes --]
next prev parent reply other threads:[~2013-12-27 0:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 8:35 [Qemu-devel] [PATCH] allwinner-a10: add config script support liguang
2013-12-25 9:29 ` Peter Maydell
2013-12-26 0:14 ` Li Guang
2013-12-26 0:32 ` Peter Maydell
2013-12-26 0:39 ` Li Guang
2013-12-26 0:47 ` Peter Maydell
2013-12-26 0:58 ` Li Guang
2013-12-26 19:40 ` Hans de Goede
2013-12-26 21:34 ` Peter Maydell
2013-12-27 0:21 ` Li Guang
2013-12-27 0:38 ` Peter Maydell
2013-12-27 0:54 ` Peter Crosthwaite [this message]
2013-12-27 1:06 ` Peter Maydell
2013-12-26 1:09 ` Peter Crosthwaite
2013-12-26 1:22 ` Li Guang
2013-12-26 1:30 ` Peter Maydell
2013-12-26 1:46 ` Li Guang
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='CAEgOgz75wtXuvtrDWLDBRay8aLGRXifyHAg6FqLci_96=H4=mw@mail.gmail.com' \
--to=peter.crosthwaite@xilinx.com \
--cc=hdegoede@redhat.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=peter.maydell@linaro.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).