From mboxrd@z Thu Jan  1 00:00:00 1970
From: haojian.zhuang@gmail.com (Haojian Zhuang)
Date: Tue, 17 May 2011 23:09:19 +0800
Subject: How logs will come to UART serial console?
In-Reply-To: <BANLkTinW5TEsr03Y1Dmw-mXnxP6ji3zmSg@mail.gmail.com>
References: <BANLkTinW5TEsr03Y1Dmw-mXnxP6ji3zmSg@mail.gmail.com>
Message-ID: <BANLkTimGFu_MJRZog7vNbOPefMrVt+r4Mg@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Tue, May 17, 2011 at 3:52 PM, sandeep kumar
<coolsandyforyou@gmail.com> wrote:
> Hi ,
> Here is my question.
> when we put 'printk's in kernel code the logs will go to the log_buffer.(i
> observed that from implementation)
> But when UART is enabled(in the bootloader), the same printk logs?are going
> to the serial console.
> As per my study printk doesnot implementing anything that writes to the UART
> console.
>
> Now here are?my questions,
> how this is being achieved??Where this is implemented?(which file)
>
console_unlock() in kernel/printk.c

> Where wil be the parsing of the cmdline string sent from the bootloader is
> done?
>
>
> Thanking you,
> sandeep kumar.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>