Re: [Qemu-devel] [PATCH] allwinner-a10: add config script support

[Li Guang]

Peter Maydell wrote:
> On 26 December 2013 00:39, Li Guang<address@hidden>  wrote:
>    
> > Peter Maydell wrote:
> >      
> > > On 26 December 2013 00:14, Li Guang<address@hidden>   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'd rather not have to add support to QEMU's bootloader
> for weird things like this if I can avoid it...
>
> Who provides this file? The board manufacturer?
> Where's the source? How do you create the blob?
> What license are the sources under?
>
>    

the file will vary for different board,
we can created by our-self,
just write the formatted text script, and
transform it to binary by a tool,
refer to:
http://linux-sunxi.org/Sunxi-tools

Thanks!