From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by ozlabs.org (Postfix) with ESMTP id 174A967EE1 for ; Sat, 13 Aug 2005 07:28:32 +1000 (EST) Received: by wproxy.gmail.com with SMTP id 68so642607wra for ; Fri, 12 Aug 2005 14:28:31 -0700 (PDT) Message-ID: Date: Fri, 12 Aug 2005 14:28:30 -0700 From: Shawn Jin To: ppcembed In-Reply-To: <20050811231710.GB5796@gate.ebshome.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <20050811231454.GA5796@gate.ebshome.net> <20050811231710.GB5796@gate.ebshome.net> Subject: Re: What's wrong with the serial port? List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 8/11/05, Eugene Surovegin wrote: > On Thu, Aug 11, 2005 at 04:14:54PM -0700, Eugene Surovegin wrote: > > > MMU:exit > > > setup_arch: enter > > > setup_arch: bootmem > > > arch: exit > > > ?????? > > > > Try disabling early text debugging (all that "MMU:..." stuff). > > >=20 > Also, make sure you pass correct "console=3D..." line to the kernel > (with correct device name and baud rate). After early text debugging is disabled and the correct "console=3DttyS0, 115200" option is passed to kernel, the problem still exists. Also I'm sure the divisor set to UART is also correct because they are the same values when U-Boot sets up the port. Has the serial port enabled interrupt so far at this stage? Thanks, -Shawn.