From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
To: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: mpc8260 TDM I/O programming
Date: Mon, 22 Jul 2002 19:29:08 +0200 [thread overview]
Message-ID: <007301c231a5$497a1e60$0700a8c0@pc005> (raw)
Hello,
I'm working with a board which is derived from EST SBC8260 with Linux
2.4.0-test2 where I'm trying to program the MCC in conjunction with TDM1C
and TDM1D.
On the same pins, can be configured both SCC3 and SCC4. For this reason I
have disabled the I/O programming which is performed into the module
arch/ppc/8260_io/uart.c.
Now, upgrading the kernel revision, by using the file uart.c of 2.4.18 I
have performed the same operation but I'm not able to load anymore the
related mcc driver (with "insmod" command).
Anybody can give me the some reference to understand what is changed?
Many thanks
Gianfranco Morandi
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-07-22 17:29 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='007301c231a5$497a1e60$0700a8c0@pc005' \
--to=gianfranco.morandi@euro-studio.it \
--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).