From: Thomas Gleixner <tglx@linutronix.de>
To: Tom Rini <trini@kernel.crashing.org>, Gary Thomas <gary@mlbassoc.com>
Cc: Dan Malek <dan@embeddededge.com>,
linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Build issues with 2.6.0-test3
Date: Wed, 13 Aug 2003 01:09:05 +0200 [thread overview]
Message-ID: <200308130109.05741.tglx@linutronix.de> (raw)
In-Reply-To: <20030812215420.GN807@ip68-0-152-218.tc.ph.cox.net>
On Tuesday 12 August 2003 23:54, Tom Rini wrote:
> > > >
> > > > It seems to be [virtually] the same as in
> > > > arch/ppc/8xx_io/uart.c
> > > > drivers/char/amiserial.c
> > > > drivers/char/serial_tx3912.c
> > > > drivers/char/sh-sci.c
> > > > drivers/macintosh/macserial.c
> > >
> > > Those are all of the obsolete, and probably broken drivers.
> > > drivers/serial is where all of the 'new' and working serial drivers
> > > are. If you've got some time, the 8260 serial driver really should be
> > > re-written as a driver inside of drivers/serial. :)
> >
> > I'll look into this. Can you suggest a good driver to use as guidance?
>
> For the conversion? Not off-hand. But there should be some docs on how
> to write these drivers on the ARM pages (RMK wrote this driver /
> abstraction set), or just skim a few of the non-'core' files under
> drivers/serial to see what's needed on the driver-specific part.
I have a nearly ready to use driver for MPC860, which uses driver/serial.c.
There is just an issue regarding startup, when the mmu is not up.
Maybe it can be helpful. It has support for configurable pins and flowcontrol.
If somebody is interrested, I can provide the code and some help to get it
running.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-12 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 15:04 Questions about ARP Steven Scholz
2003-08-08 18:24 ` Dan Malek
2003-08-12 12:34 ` Steven Scholz
2003-08-12 13:56 ` Build issues with 2.6.0-test3 Gary Thomas
2003-08-12 15:25 ` Tom Rini
2003-08-12 15:39 ` Matt Porter
2003-08-12 15:40 ` Gary Thomas
2003-08-12 15:46 ` Tom Rini
2003-08-12 19:13 ` Gary Thomas
2003-08-12 21:54 ` Tom Rini
2003-08-12 23:09 ` Thomas Gleixner [this message]
2003-08-12 22:23 ` Tom Rini
2003-08-12 15:39 ` Questions about ARP Dan Malek
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=200308130109.05741.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=dan@embeddededge.com \
--cc=gary@mlbassoc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).