I think there's too much duplication in the resource map code. resourcemaps.diff tries to address it by:
Creating clear_resource_map() for k8 and fam10. This sets all the routing registers to a known state. Calling clear_resource_map() and then only setting the specific registers that are non-zero in board-specific code. Adding util.c for fam10, so that it can be customized for fam10.
I didn't update all of the resourcemap.c files, yet. I wanted to see what the reaction would be.
sublinks.diff marks that bit as not reserved for all fam10 boards, so that it can be cleared.
Signed-off-by: Myles Watson mylesgw@gmail.com
Thanks, Myles
On Mon, May 10, 2010 at 1:24 PM, Myles Watson mylesgw@gmail.com wrote:
I think there's too much duplication in the resource map code. resourcemaps.diff tries to address it by:
Creating clear_resource_map() for k8 and fam10. This sets all the routing registers to a known state. Calling clear_resource_map() and then only setting the specific registers that are non-zero in board-specific code. Adding util.c for fam10, so that it can be customized for fam10.
I didn't update all of the resourcemap.c files, yet. I wanted to see what the reaction would be.
Ping.
sublinks.diff marks that bit as not reserved for all fam10 boards, so that it can be cleared.
Signed-off-by: Myles Watson mylesgw@gmail.com
Thanks, Myles