Should be Ron.
You should delete 855pm. Without (i) in i855pm, it will not be processed by config.g and ....
YH
-----Original Message----- From: ebiederman@lnxi.com [mailto:ebiederman@lnxi.com] Sent: Tuesday, October 26, 2004 6:26 PM To: Ron Minnich Cc: LinuxBIOS Subject: Q: Which is used the 855pm or the i855pm code?
I am walking through the code converting the sizeram() functions and have run across a duplicate 855pm and the i855pm.
The digitallogic/adl855pc is using the i855pm, so that appears to be the active one.
Is there a reason we have two of these? If not can we just delete src/northbridge/intel/855pm?
Eric _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Tue, 26 Oct 2004, YhLu wrote:
You should delete 855pm. Without (i) in i855pm, it will not be processed by config.g and ....
that's what bit me.
ron
"Ronald G. Minnich" rminnich@lanl.gov writes:
On Tue, 26 Oct 2004, YhLu wrote:
You should delete 855pm. Without (i) in i855pm, it will not be processed by config.g and ....
that's what bit me.
Hmm. I am confused about what part of config.g makes that a problem, but I guess I can look.
Speaking of config.g what would it take to not allow uses in anything except src/mainboard/xxx/Options.lb.
Having one place were we simply declare which variables we are going to be using for the entire board, (while still allowing them to be set elsewhere) seems sane. That actually reflects the current state of the mainboard configuration right now.
When I added part/init_timer.h and set HAVE_INIT_TIMER in src/cpu/k8/Config.lb and src/cpu/tsc/Config.lb I noticed that I had to include a uses directive in those Config.lb files.
Eric
On Wed, 27 Oct 2004, Eric W. Biederman wrote:
Hmm. I am confused about what part of config.g makes that a problem, but I guess I can look.
generated C identifiers somewhere. I don't think it is worth fussing over too much, but that's your call. :-)
Speaking of config.g what would it take to not allow uses in anything except src/mainboard/xxx/Options.lb.
that is a problem for greg and PPC mezzanine cards. We're going to maybe need options in the cpu and one other directory. I would like to make it impossible for Options.lb anywhere else.
When I added part/init_timer.h and set HAVE_INIT_TIMER in src/cpu/k8/Config.lb and src/cpu/tsc/Config.lb I noticed that I had to include a uses directive in those Config.lb files.
eek. I agree with you.
ron
* Eric W. Biederman ebiederman@lnxi.com [041027 19:24]:
Speaking of config.g what would it take to not allow uses in anything except src/mainboard/xxx/Options.lb.
Having one place were we simply declare which variables we are going to be using for the entire board, (while still allowing them to be set elsewhere) seems sane. That actually reflects the current state of the mainboard configuration right now.
Would anything speak against putting a "uses CC" into all mainboard/xxx/Options.lb then? Some mechanism to specify the compiler will be needed for cross compiling LinuxBIOS.
Stefan
On Thu, 28 Oct 2004, Stefan Reinauer wrote:
Would anything speak against putting a "uses CC" into all mainboard/xxx/Options.lb then? Some mechanism to specify the compiler will be needed for cross compiling LinuxBIOS.
works for me!
ron
-
ebiederman＠lnxi.com -
Ronald G. Minnich -
Stefan Reinauer -
YhLu