* Nicolas Pitre <nico@xxxxxxxxxxx> [110204 12:14]: > > Just create a get_config_ptr macro or similar and the trickery will be > nicely encapsulated. You'd have: > > .macro get_config_ptr ptr, tmp > b 9002f > .align > 9001: .long . > .long uart_param_storage > 9002: adr \ptr, 9001b > ldr \tmp, [\ptr] > sub \tmp, \tmp, \ptr > ldr \ptr, [\ptr, #4] > sub \ptr, \ptr, \tmp > .endm > > .macro addruart rp, rv > get_config_ptr \rv > ldr \rp, [\rv] > ldr \rv, [\rv, #4] > .endm > > And for the other macros, you get the hardware address to use already, > but you can still use get_config_ptr for extra config values you > need if necessary. Thanks, will try that out next week. That might run into problems with busyuart as it only has rd register to play with. > > In that case the mapping of IO space for the serial port in head.S > > would have to be changed as that relies on rx containing the port > > IO address.. > > Yes, and I'm not sure if it is worth changing that at this point when it > is possible to do it without introducing such a change which would > affect all machines again. Agreed, let's see how far we can get with the existing setup. What might need to be done is to save and restore rx in busyuart to be able to use your macro above. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
