On Thu, 28 Oct 2010, Rohit Vaswani wrote: > On 10/28/2010 10:46 AM, Russell King - ARM Linux wrote: > > On Thu, Oct 28, 2010 at 09:41:06AM -0700, Daniel Walker wrote: > > > On Thu, 2010-10-28 at 17:35 +0100, Russell King - ARM Linux wrote: > > > > If you don't want it, don't enable DEBUG_LL. DEBUG_LL is what you > > > > enable for initial board bring-up and once you're getting kernel > > > > messages via standard console drivers, you disable it. > > > This board doesn't have the ability to support DEBUG_LL .. I don't want > > > the user to have the option to even select that. > > But do not leave this function empty otherwise if you > > enable DEBUG_LL, you'll get unpredictable behaviour. > > > With DEBUG_LL enabled and if all the 3 macros (addruart, senduart, waituart) > are empty > nothing references these values - so wouldn't this be okay? The addruart macro is used to set up a mapping so the senduart and waituart can access the UART port. But even if senduart and waituart are empty, the empty addruart is wrong because if it doesn't initialize the passed registers, a random mapping will be created with whatever was in those register before. That random mapping could overwrite the mapping that just was created for the kernel image for example. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
