Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: rolf liu <rolfliu@gmail.com>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: possible serial driver fixup for au1x00 in 2.6?
Date: Wed, 06 Jul 2005 00:10:17 -0700	[thread overview]
Message-ID: <1120633817.5724.26.camel@localhost.localdomain> (raw)
In-Reply-To: <2db32b72050705124078a48aed@mail.gmail.com>

On Tue, 2005-07-05 at 12:40 -0700, rolf liu wrote:
> Pete,
> To try if 8250.c can work under db1550/linux 2.6.12, I turn off the
> au1x00_uart.c config and just compiled in the 8250 support. When I
> boot the kernel, nothing comes up through the console, which should be
> provided by 8250 support, by 8250_early.c?
> 
> Any idea?

Yes. The 8250.c won't work with the au1x uart. I know I said in a
previous email that the 8250 "basically" does the same thing as the au1x
uart driver, but if the 8250 worked with the Au1x SoCs, why would we
even have the au1x serial driver in place?

Pete

> 
> On 7/1/05, Pete Popov <ppopov@embeddedalley.com> wrote:
> > On Fri, 2005-07-01 at 17:56 -0700, rolf liu wrote:
> > > Basically, au1x00_uart.c is doing the same thing as 8250.c.
> > 
> > Basically.
> > 
> > > If I want
> > > to add extra serial port support by 8250.c. There could be some
> > > problem. Any idea?
> > 
> > Don't know, haven't tried it. In general, the au1x00 serial driver needs
> > to be rewritten.
> > 
> > Pete
> > 
> >
> 

  parent reply	other threads:[~2005-07-06  7:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02  0:56 possible serial driver fixup for au1x00 in 2.6? rolf liu
2005-07-02  1:06 ` Pete Popov
2005-07-05 19:40   ` rolf liu
2005-07-05 21:46     ` Michael Stickel
2005-07-05 22:41       ` rolf liu
2005-07-06  7:10     ` Pete Popov [this message]
2005-07-06 16:21       ` rolf liu
2005-09-05  8:40         ` Matej Kupljen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1120633817.5724.26.camel@localhost.localdomain \
    --to=ppopov@embeddedalley.com \
    --cc=linux-mips@linux-mips.org \
    --cc=rolfliu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox