On Mon, Aug 4, 2008 at 7:38 PM, ron minnich rminnich@gmail.com wrote:
Current state of tree. This all compiles with only errors for stuff not yet defined.
Too many fixes in here to list them all :-) but: convert mcp55 over to new resource maps. fix my misunderstanding of one aspect of resource map setup Fix typo in config_{read,write} naming. Fix random mistakes in include files.
YHLU: question: is REV F a proper superset of all K8? If we do REV F compatible code, and test for REV A-E in our coded and take appropriate action, will the code work properly? Can we have e.g. the same mem_controller struct for all K8?
No. REV A-E got DDR1. REV F got DDR2
I'd like to avoid the files we had in v2 with stuff like xyz_f and just have one common set of K8 files. It's even ok if, e.g., there are struct members in the mem_controller struct that are only used on rev f or dual core, and unused otherwise. I'd like to simplify the tangle we had in v2.
YH