qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Li Guang <lig.fnst@cn.fujitsu.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] allwinner-a10: add config script support
Date: Thu, 26 Dec 2013 20:40:47 +0100	[thread overview]
Message-ID: <52BC863F.5010600@redhat.com> (raw)
In-Reply-To: <52BB7F36.6040101@cn.fujitsu.com>

Hi,

On 12/26/2013 01:58 AM, Li Guang wrote:
> Peter Maydell wrote:
>> On 26 December 2013 00:39, Li Guang<lig.fnst@cn.fujitsu.com>  wrote:
>>> Peter Maydell wrote:
>>>> On 26 December 2013 00:14, Li Guang<lig.fnst@cn.fujitsu.com>   wrote:
>>>>> it's the approach sunxi-linux kernel config hardware,
>>>>> the binary is actually a transformed text script,
>>>>> and context of script is like:
>>>>>
>>>>> [card0_boot_para]
>>>>> card_ctrl = 0
>>>>> card_high_speed = 1
>>>>> card_line = 4
>>>>> sdc_d1 = port:PF00<2><1><default><default>
>>>>> sdc_d0 = port:PF01<2><1><default><default>
>>>>> sdc_clk = port:PF02<2><1><default><default>
>>>>> sdc_cmd = port:PF03<2><1><default><default>
>>>>> sdc_d3 = port:PF04<2><1><default><default>
>>>>> sdc_d2 = port:PF05<2><1><default><default>
>>>>>
>>>> So what sets this up on real hardware? Is this part of
>>>> a firmware blob? Is it in ROM or flash?
>>> it's generally in /boot, bootloader will load it
>>> into ram address 0x43000000, kernel will find it
>>> at this fixed address, and parse it, learn the hardware
>>> related configuration, mostly property of devices, and
>>> GPIOes used.
>> Weird. Why isn't this just using devicetree?
>
> don't know the exactly reason linux-sunxi community
> do this(actually, the script parsing code mostly wrote
> by engineer from Allwinner).

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.

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.

Regards,

Hans

  reply	other threads:[~2013-12-26 19:41 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 [this message]
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
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=52BC863F.5010600@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=lig.fnst@cn.fujitsu.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).