From: Li Guang <lig.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] allwinner-a10: add config script support
Date: Fri, 27 Dec 2013 08:21:38 +0800 [thread overview]
Message-ID: <52BCC812.3080201@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA8OQxSjpFTnS9QdP_iy4NoRnn+krx42tV8DD_okgZpACw@mail.gmail.com>
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?
next prev parent reply other threads:[~2013-12-27 0:23 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 [this message]
2013-12-27 0:38 ` Peter Maydell
2013-12-27 0:54 ` Peter Crosthwaite
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=52BCC812.3080201@cn.fujitsu.com \
--to=lig.fnst@cn.fujitsu.com \
--cc=hdegoede@redhat.com \
--cc=peter.crosthwaite@xilinx.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).