Hi, On Fri, 2008-08-29 at 10:17 -0700, ext David Brownell wrote: > On Friday 29 August 2008, Steve Sakoman wrote: > > Is anyone aware of a utility to report the state of pin mux settings? > > > > I'd like to verify that u-boot is setting things up properly. > > CONFIG_OMAP_MUX_WARNINGS helps for some definitions of "properly": > when Linux needs one setting, but the boot loader leaves a different > one, you get a warning. That's usually interpreted as u-boot doing > it wrong, except on devboards where the boot loader can't actually > know about all external hardware that might be hooked up (and how)
I'm probably a bit off topic, but since Tony started promoting the concept of multi-arch binary, well, i see it as a huge limitation the fact that the bootloader is expected to the right thing. When thinking about our Nokia HW vs the TI SDP, even the bootloader is different (yes, we should move to uboot and i couldn't be happier, but it's not gonna happen at the moment). In the multi arch case (but even single-arch, if we would like to support multiple boards with one single kernel binary) i see as a much more reasonable solution the case where the bootloader passes the board id to the kernel and the kernel loads the board-specific configuration in the form of a module. DVFS for example defeats the idea that the bootloader would be enough to setup properly the clock tree (of course it will do it, but only for 1 OP and the setting can get lost the first time another OP is selected). Imho the bootloader should just do what the name suggests: load the kernel and boot it. In as minimal configuration as possible. -- Cheers, Igor --- Igor Stoppa Maemo Software - Nokia Devices R&D - Helsinki -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
