From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: sjhill@realitydiluted.com
Cc: linux-mips@linux-mips.org
Subject: Re: Problem with MV64340 serial driver
Date: Fri, 07 Jan 2005 17:27:32 +0100 [thread overview]
Message-ID: <41DEB874.8000809@enix.org> (raw)
In-Reply-To: <E1CmuxT-0002LO-TO@real.realitydiluted.com>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Hello,
sjhill@realitydiluted.com a écrit :
> My first question is, "Why?". You are aware that a serial driver already
> exists for PPC using the 64360 which is the same chip as the 64340
> except that it has a PPC 60x bus interface instead of MIPS? We do NOT
> want multiple drivers. We just went through this with the ethernet
> driver on 64340/64360. Go pull the latest stuff from:
>
> bk://source.mvista.com/linux-2.5-marvell
>
> and look in 'drivers/serial/mpsc'. You should use this as your starting
> point and make the necessary changes to get it working on the 64340.
> Another serial driver will not be accepted into the kernel. Thanks.
Thanks for the information. I have been inside linux-2.5-marvell BK
tree, but I couldn't find the drivers/serial/mpsc directory, nor to find
the driver for the 64340 serial port.
I've used the Web interface at
http://source.mvista.com:14690//linuxppc-2.5/src/drivers/serial?nav=index.html|src/|src/drivers
Thanks,
Thomas
--
PETAZZONI Thomas - thomas.petazzoni@enix.org
http://thomas.enix.org - Jabber: thomas.petazzoni@jabber.dk
http://kos.enix.org, http://sos.enix.org
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E 1624 F653 CB30 98D3 F7A7
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-01-07 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 9:53 Problem with MV64340 serial driver Thomas Petazzoni
2005-01-07 14:19 ` sjhill
2005-01-07 16:27 ` Thomas Petazzoni [this message]
2005-01-07 16:32 ` sjhill
2005-01-07 16:40 ` Thomas Petazzoni
2005-01-07 17:00 ` sjhill
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=41DEB874.8000809@enix.org \
--to=thomas.petazzoni@enix.org \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@realitydiluted.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