CONFIG_USE_INIT 1. car as ram is messed up with inline assembly, So We can check up the auto.inc that gcc produced to verify if the inline assembly is well with other lines from C. 2. ...., the same, except We rename some section name.
Why only cache_as_ram_auto.c
1. then will be section name conflicts to create crt0.s (CONFIG_USE_INIT==0) or init.o (CONFIG_USE_INIT==1)
2. with ROMCC, you can not put these info in reg, it may need 4K bytes. Also for support new CPU or sync different CPU freq to common freq, I need to separate HT freq optimization with coherent_ht and ht_chain. So need to store all link info for optimization later.......
YH
-----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, October 27, 2005 1:56 PM To: Lu, Yinghai Cc: Stefan Reinauer; LinuxBIOS; Greg Watson Subject: RE: [LinuxBIOS] Config file dependencies
On Thu, 2005-10-27 at 13:45 -0700, Lu, Yinghai wrote:
No
- CONFIG_USE_INIT==0 is very useful for debug.
Why??
- CONFIG_USE_INIT==1 is something ppc car using...
AFIAK, the way you are using USE_INIT is totally different from what Greg is doing on PPC. I am not an expert on this issue but I believe the only common thing in these two is the same macro name. Greg, can you have some comment on this?
Auto.c and cache_as_ram_auto.c is very different
- cache_as_ram_auto include failover.c
Why do you do that? Why don't you have cache_as_ram_failover.c too?
- later cache_as_ram_auto will have struct sys_info sysinfox, and it
will include every info include dimm.....and we don't need to keep
read
smbus and pci conf space for....
Any reason it has to be in cache_as_ram_auto only?
-
Lu, Yinghai