"Menon, Nishanth" <nm@xxxxxx> writes: >> -----Original Message----- >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >> owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin Hilman >> >> >>> W17_7XX_USB_VBUSI, >> >>> + >> >>> + /* MMC */ >> >>> + MMC_7XX_CMD, >> >>> + MMC_7XX_CLK, >> >>> + MMC_7XX_DAT0, >> >> >> >> probably a dumb question -> but should'nt these go off to bootloader >> >> perhaps? >> >> >> > >> > Perhaps, although we use either EOL (for HTC Wizard) or Haret to boot, >> > and they don't set up the right mux configuration for our board. >> > >> > This way though, we don't have to worry about the boot loader -- we >> > can set it up right regardless of who boots us. >> >> I agree with Cory. >> >> I prefer that mux settings go into the kernel, even if they are setup >> in the bootloader already. It's better to have redundancy than wonder >> what to do if changing boot loaders. >> > Probably opening up a can of worms.. Are the rules different for OMAP3? > Should'nt we have all mux done at kernel so that kernel is loader > independent? Yes, we should. My preference is to always have muxing in the kernel. Kevin -- 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
