RE: Using DEBUG_LL?
-Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Aguirre, Sergio Sent: Friday, February 26, 2010 8:03 PM To: Tony Lindgren Cc: linux-omap@vger.kernel.org; Pandita, Vikram Subject: Using DEBUG_LL? Hi, Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad-uart. Vikram reported this on list some time back. Regards, Santosh -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Using DEBUG_LL?
-Original Message- From: Shilimkar, Santosh Sent: Friday, February 26, 2010 8:53 AM To: Aguirre, Sergio; Tony Lindgren Cc: linux-omap@vger.kernel.org; Pandita, Vikram Subject: RE: Using DEBUG_LL? -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Aguirre, Sergio Sent: Friday, February 26, 2010 8:03 PM To: Tony Lindgren Cc: linux-omap@vger.kernel.org; Pandita, Vikram Subject: Using DEBUG_LL? Hi, Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad- uart. I know that. But I'm not using a Zoom board now, I'm trying with a 3630SDP. So, I'm not using an external UART anymore. Regards, Sergio Vikram reported this on list some time back. Regards, Santosh -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Using DEBUG_LL?
Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad-uart. Vikram reported this on list some time back. No, looks like this is broken on SDPs as well. Either that, or I haven't understood how to use the early_printk option. I have the same problem on my 3430 SDP and manually patch kernel/printk.c with the patch in Tony's omap-debug branch. - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Using DEBUG_LL?
Hi, In addition to DEBUG_LL you need to append 'earlyprintk' to the cmdline. Hope this helps, Jean On Friday 26 February 2010 16:02:36 Gadiyar, Anand wrote: Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad-uart. Vikram reported this on list some time back. No, looks like this is broken on SDPs as well. Either that, or I haven't understood how to use the early_printk option. I have the same problem on my 3430 SDP and manually patch kernel/printk.c with the patch in Tony's omap-debug branch. - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Using DEBUG_LL?
-Original Message- From: Gadiyar, Anand Sent: Friday, February 26, 2010 8:33 PM To: Shilimkar, Santosh; Aguirre, Sergio; Tony Lindgren Cc: linux-omap@vger.kernel.org; Pandita, Vikram Subject: RE: Using DEBUG_LL? Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad-uart. Vikram reported this on list some time back. No, looks like this is broken on SDPs as well. Either that, or I haven't understood how to use the early_printk option. I have the same problem on my 3430 SDP and manually patch kernel/printk.c with the patch in Tony's omap-debug branch. Missed that point. I always need patch ascii hack to printk to ger LL_DEBUG working. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Using DEBUG_LL?
-Original Message- From: Jean Pihet [mailto:jpi...@mvista.com] Sent: Friday, February 26, 2010 9:10 AM To: Gadiyar, Anand Cc: Shilimkar, Santosh; Aguirre, Sergio; Tony Lindgren; linux- o...@vger.kernel.org; Pandita, Vikram Subject: Re: Using DEBUG_LL? Hi, Hi, In addition to DEBUG_LL you need to append 'earlyprintk' to the cmdline. Brilliant! Now it works. :D Thanks a lot for the help! Regards, Sergio Hope this helps, Jean On Friday 26 February 2010 16:02:36 Gadiyar, Anand wrote: Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad-uart. Vikram reported this on list some time back. No, looks like this is broken on SDPs as well. Either that, or I haven't understood how to use the early_printk option. I have the same problem on my 3430 SDP and manually patch kernel/printk.c with the patch in Tony's omap-debug branch. - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Using DEBUG_LL?
In addition to DEBUG_LL you need to append 'earlyprintk' to the cmdline. Brilliant! Now it works. :D Thanks a lot for the help! Works for me too! Thanks! - Anand Regards, Sergio Hope this helps, Jean On Friday 26 February 2010 16:02:36 Gadiyar, Anand wrote: Wit the current master branch, I tried enabling DEBUG_LL, and EARLY_PRINTK options, but I can't see the LL output as usual (#... kind of thing) on my 3630SDP. Is there a patch to enable it after the serial cleanup patches? I think DEBUG_LL on zoom boards is broken because they use external quad-uart. Vikram reported this on list some time back. No, looks like this is broken on SDPs as well. Either that, or I haven't understood how to use the early_printk option. I have the same problem on my 3430 SDP and manually patch kernel/printk.c with the patch in Tony's omap-debug branch. - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
