Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Michael Stickel <michael@cubic.org>
To: linux-mips@linux-mips.org
Subject: Re: Bitrotting serial drivers
Date: Mon, 21 Mar 2005 08:45:33 +0100	[thread overview]
Message-ID: <423E7B9D.3040908@cubic.org> (raw)
In-Reply-To: <20050320224028.GB6727@linux-mips.org>

Ralf Baechle wrote:

>On Sat, Mar 19, 2005 at 02:13:51PM -0800, Andrew Morton wrote:
>  
>
>No argument here.  Pete says the AMD Alchemy UART is just different enough
>to be hard to handle in the 8250 and so the driver is just an ugly
>chainsawed version of the 8250.c
>  
>
Even if I don't make me a lot of friends, the au1x00 driver seems to be 
a hack.

Most of the difference seems to be the PCI stuff, that has been removed 
and the access method.
Shouldn't we have a driver for the chip and one driver for each access 
method (isa,pci,...).
The access method should handle register access and the bus abstraction.
I have a lot of problems with the au1x00 serial driver, because I use it 
together
with a PCMCIA serial port card.

Michael

  parent reply	other threads:[~2005-03-21  8:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050319172101.C23907@flint.arm.linux.org.uk>
     [not found] ` <20050319141351.74f6b2a5.akpm@osdl.org>
2005-03-20 22:40   ` Bitrotting serial drivers Ralf Baechle
2005-03-20 22:51     ` Pete Popov
2005-03-20 23:24       ` Russell King
2005-03-20 23:42         ` Pete Popov
2005-03-21 20:51       ` Ulrich Eckhardt
2005-03-21 20:57         ` Pete Popov
2005-03-21 22:07           ` Ulrich Eckhardt
2005-03-22  7:28             ` Michael Stickel
2005-03-22  9:58       ` Michael Stickel
2005-03-21  7:45     ` Michael Stickel [this message]
2005-03-21  9:06       ` Stanislaw Skowronek
2005-03-21  9:19       ` Pete Popov
2005-03-21 12:12         ` Michael Stickel
2005-03-21 12:38           ` Ralf Baechle
2005-03-21 21:10 Joseph Chiu
2005-03-21 21:10 ` Joseph Chiu

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=423E7B9D.3040908@cubic.org \
    --to=michael@cubic.org \
    --cc=linux-mips@linux-mips.org \
    /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