From: Dan Malek <dan@embeddededge.com>
To: navinb <ppc4@rediffmail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: scc2 conflict with usb?
Date: Mon, 24 Jun 2002 13:32:29 -0400 [thread overview]
Message-ID: <3D1757AD.7070305@embeddededge.com> (raw)
In-Reply-To: 20020624164245.25843.qmail@webmail11.rediffmail.com
navinb wrote:
> problem being faced is that usb (scc1 addres space) works when my
> CPM ENET is not either at SCC1 or SCC2.
How does USB conflict with SCC2 in Ethernet mode? The default
configuration should just build this way, since the only thing
you can run on SCC1 is USB. On an 823, the default (and about
the only configuration) is USB on SCC1, Ethernet on SCC2 and console
on SMC1. Not all parts have SCC3.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-06-24 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 16:42 scc2 conflict with usb? navinb
2002-06-24 17:32 ` Dan Malek [this message]
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=3D1757AD.7070305@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ppc4@rediffmail.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;
as well as URLs for NNTP newsgroup(s).