Reworking the attribute is actually causing a huge pain in the ass with
relocations it looks like. I'm going to see if i can have the amdk8 MCT
code return the dimm_mask information back to the board via
I could either just have sdram_initialize() return a merged version of
dimm_mask which would limit the number of dimms supported, or I could
pass in an additional non-static 'population' structure which i think
may be better.<br>
Any thoughts?.. I'm going to modify my stuff to pass in a new structure in the meantime..<br>
<br><br><div><span class="gmail_quote">On 10/20/05, <b class="gmail_sendername">Ronald G Minnich</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
San Mehat wrote:<br>> 1- I dont think we should be worried about names that are too long. I'd<br>> much rather have a long name than a non-descriptive one (or in this case<br>> a totally misleading one)<br>> 2- Changing the attribute shouldn't be that big of a deal.
<br>> 3 - dimm_mask isn't exposed to the mainboard layer which is where we<br>> need it.<br>><br>><br>> As for 'why we need it', we have a post card which displays the DIMM<br>> population map on boot for our ops guys...
<br><br>1. I'm ok with long names. These are rarely typed, more often read, and<br>should be correct.<br>2. yeah<br>3. yeah, expose as much info as we can. We're a bios.<br><br>can you send us a diff in -u format so we can take a look?