<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, Alejandro
<br>
<br>
I think both of them can be safely removed. I don't know if you
know the Allwinner style packaging system. There is an
sys_config.fex file, which is a config file for the hardware related
things. This sys_config.fex will handled by a pc tools to generate a
bin file called sys_config.bin which contains the data structure of
the config. And the sys_config.bin will be loaded by the bootloader
to a reserved memery in linux. Then in the driver, they will use
function like script_parser_xxx to get the hardware information.<br>
I think the main purpose for this complicated method is to
separate the hardware and the software config work. Allwinner's
customs are small companies with low R&D abilities. With this
method, customs only need to change the sys_config.fex file to use
different <span class="Apple-style-span" style="color: rgb(102,
102, 102); font-family: 'Times New Roman'; font-size: 14px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 22px; orphans: 2; text-align:
-webkit-auto; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust:
auto; -webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); display: inline !important; float: none; "></span>peripherals,
without modifying the driver.<br>
Back to the sys_config1.bin and sys_config_verity_dd3.bin,
sys_config1.bin is built in the kernel before, but is loaded by
bootloader now, so sys_config1.bin is no use any more, but no one
cleaned it. And sys_config_verity_dd3.bin, you can see in
sys_config.S,<br>
<br>
1: .globl sys_cofig_data <br>
2:sys_cofig_data:<br>
3: .incbin "arch/arm/mach-sun4i/pin/sys_config_verify_ddr3.bin"<br>
4: .globl sys_cofig_data_end <br>
5:sys_cofig_data_end: <br>
<br>
the label "sys_cofig_data" is only used one place
arch/arm/mach-sun4i/pin/pin_ops.c <br>
<br>
95: #ifdef FPGA_RUNTIME_ENV <br>
96: return script_parser_init((char *)(sys_cofig_data));<br>
97: #else<br>
98: return script_parser_init((char
*)__va(CONFIG_SW_SYSMEM_RESERVED_BASE));<br>
99: #endif<br>
<br>
You can see the macro FPGA_RUNTIME_ENV is never defined if you use a
chip. So, the sys_config_verify_ddr3.bin is a special config used
when the chip is in designing on a fpga, from it's name it should be
the config for verifying the ddr3 controller.<br>
<br>
I hope i have explained clearly. You can remove the sys_config.S,
sys_config1.bin, sys_config_verify_ddr3.bin, and clean the code in
arch/arm/mach-sun4i/pin/pin_ops.c.<br>
<br>
<br>
<br>
On 12/19/2011 04:41 PM, Alejandro Mery wrote:
<blockquote
cite="mid:CACB0nksTY9ir5BykT7RU135S_ybMPQFTG_hQ09Xu6j4YEYCFGQ@mail.gmail.com"
type="cite">
<pre wrap="">Hello, I'm starting to port sun4i support to linus' master and noticed
the beside standby.bin there are two blobs without source code to
generate them.
arch/arm/mach-sun4i/pin/sys_config1.bin and
arch/arm/mach-sun4i/pin/sys_config_verity_dd3.bin, the later been
loaded by sys_config.S
can you try to get that in a form we can actually get mainlined?
Thanks,
Alejandro
_______________________________________________
arm-netbook mailing list <a class="moz-txt-link-abbreviated" href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a>
<a class="moz-txt-link-freetext" href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a>
Send large attachments to <a class="moz-txt-link-abbreviated" href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a>
</pre>
</blockquote>
<br>
</body>
</html>