linux-mips
[Top] [All Lists]

Re: Bitrotting serial drivers

To: Ulrich Eckhardt <eckhardt@satorlaser.com>
Subject: Re: Bitrotting serial drivers
From: Pete Popov <ppopov@embeddedalley.com>
Date: Mon, 21 Mar 2005 12:57:12 -0800
Cc: linux-mips@linux-mips.org
In-reply-to: <200503212151.22059.eckhardt@satorlaser.com>
Organization: Embedded Alley Solutions, Inc
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050319172101.C23907@flint.arm.linux.org.uk> <20050320224028.GB6727@linux-mips.org> <423DFE7C.7040406@embeddedalley.com> <200503212151.22059.eckhardt@satorlaser.com>
Reply-to: ppopov@embeddedalley.com
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020
Ulrich Eckhardt wrote:
On Sunday 20 March 2005 23:51, Pete Popov wrote:

It works and no one has complained about any bugs.


I hereby do complain that it doesn't work. ;)

I'd give more details, but I'm neither at work nor did I investigate the situation properly. What I remember trying is to add 'console=/dev/ttyS0' or somesuch to the commandline, but couldn't get it to work there.

Well, come on, I know that much works :) Which board and kernel rev?

Pete

The funny thing is that when I use the GDB support over serial line (which seems to use a primitive, stripped-down version of a serial driver) it works, I can then redirect boot messages via 'console=gdb'.

Uli




<Prev in Thread] Current Thread [Next in Thread>