From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: printk/console_init - baud rate setting Date: Wed, 14 Nov 2007 18:17:31 -0800 Message-ID: In-Reply-To: <610b1b49ca582c7a2277e8d6dea2be31@kernel.crashing.org> References: <72880d6da4c2ccb37ba665e420d26666@kernel.crashing.org> <610b1b49ca582c7a2277e8d6dea2be31@kernel.crashing.org> From: "Siva Prasad" To: "Segher Boessenkool" Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Thanks Segher. It was because of the BASE_BAUD value. We are working at 600MHz, not 18.432. After that change, it worked fine. Thanks Siva -----Original Message----- From: Segher Boessenkool [mailto:segher@kernel.crashing.org]=20 Sent: Wednesday, November 14, 2007 3:00 PM To: Siva Prasad Subject: Re: printk/console_init - baud rate setting > Thanks for your response Segher. > I already have the command line "console=3DttyS0, 115200". Now, how to > make sure that 115200 setting is calculated properly for the use by > driver. > > In other words, can you kind enough to please let me know how 115200 is > supported by the driver, based on the clock frequency. That is solely the driver's own responsibility, you'll have to look at the source code. 8250 typically just assumes 18.432MHz. Segher