From: "Aung Soe" <aung.aungkyawsoe@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: PowerPC 8266 ADS-PCI(CPM8260) SCC (UART/Ethernet Mode) and SMC in UART mode
Date: Tue, 6 Jun 2006 16:50:40 +0200 [thread overview]
Message-ID: <d668b9080606060750w59f531f2mda0bf2b465202c8d@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Dear All
I am working on PowerPC 8266 ADS-PCI board
with Montavista Linux with 2.4.20 Kernel to make SCC1, SMC 1& 2
in UART mode, SCC2, 3 & 4 in Ethernet mode, and FCC 2 in Fast
Ethernet Mode; all in NMSI and not TDM. The drivers provided with
2.4.20 Linux on Power PC were refered and reused.
http://lxr.linux.no/source/arch/ppc/8260_io/?v=2.4.20;a=ppc
When there are only 3 SCCs used in Ethernet mode and the last
SCC in UART mode then the system works well.
But when 2 more SMC are added to the UART serial driver, the SCC
Ethernet network driver is not working after all ports working for a while.
I will be appreciate to hear any pointers and hints.
Thanks in advance.
Sincerley
Aung
[-- Attachment #2: Type: text/html, Size: 1292 bytes --]
reply other threads:[~2006-06-06 14:57 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=d668b9080606060750w59f531f2mda0bf2b465202c8d@mail.gmail.com \
--to=aung.aungkyawsoe@gmail.com \
--cc=linuxppc-dev@ozlabs.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).