From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: confusion regarding UART config and source files
Date: Sat, 24 Jul 2004 09:50:41 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0407240924590.12548@dell.enoriver.com> (raw)
i know this has come up before but, if i understand correctly, given
that UART support is moving from (at least in my case)
arch/ppc/8xx_io/uart.c to drivers/serial/cpm_uart, is there any need
to keep the
[ ] Use UART
entry in the MPC8xx CPM Options menu?
also, if one looks in drivers/serial/cpm_uart/Makefile, there's a
test for the CONFIG_CPM2 variable which doesn't seem to exist anymore;
certainly, a recursive grep doesn't show anything ever setting it,
and grep showed a few other files that test the apparently obsolete
CONFIG_CPM2.
rday
p.s. and i assume that comment at the top of the cpm_uart/Makefile
that reads,
# Makefile for the Motorola 8xx FEC ethernet controller
is just one of those ubiquitous cut and paste glitches. :-)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-07-24 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.60.0407240924590.12548@dell.enoriver.com \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.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).