From: "navinb" <ppc4@rediffmail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: scc2 conflict with usb?
Date: 24 Jun 2002 16:42:45 -0000 [thread overview]
Message-ID: <20020624164245.25843.qmail@webmail11.rediffmail.com> (raw)
Hello,
I am able to run a usb slave driver in linux 2.4.7 on 823/850
(rpxlite) boards.
problem being faced is that usb (scc1 addres space) works when my
CPM ENET is not either at SCC1 or SCC2.
when I enable ENET on SCC3 my UART conflicts and says during
compilation
uart.c:68: #error "Can't use SMC1 for console with Ethernet on
SCC3"
guided by this now when i enable console on SMC2 it compliles but
no o/p during booting on screen.
looks like uart.c file need to be looked upon.
ENET on SCC1 would conflict with USB as there would be clash of
interrupts (CPMVEC_SCC1),
But I am not able to understand why ENET on SCC2 disturbs USB at
all.
is there any solution without touching uart.c file ?
Best Regards,
_________________________________________________________
There is always a better job for you at Monsterindia.com.
Go now http://monsterindia.com/rediffin/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-24 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 16:42 navinb [this message]
2002-06-24 17:32 ` scc2 conflict with usb? Dan Malek
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=20020624164245.25843.qmail@webmail11.rediffmail.com \
--to=ppc4@rediffmail.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).