linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Hyun-Joon Cha" <tachyon@postech.ac.kr>
To: "Dan Malek" <dan@netx4.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Req. help about SCC2 and SCC3 as ethernet.
Date: Thu, 27 Jul 2000 23:38:13 +0900	[thread overview]
Message-ID: <01ff01bff7d8$4b122460$1952df8d@SOYANG> (raw)
In-Reply-To: 39804084.5EA8BA01@embeddededge.com


----- Original Message -----
From: "Dan Malek" <dan@netx4.com>
To: "Hyun-Joon Cha" <tachyon@postech.ac.kr>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, July 27, 2000 11:00 PM
Subject: Re: Req. help about SCC2 and SCC3 as ethernet.


> How do you know that is where it stops?

We are currently using remote GDB with abatron BDI2000. In console_serial_write function, this function can't return any character....

> With SCC3, you are now
> trying to configure Port B, which is also used for the SMC1 configuration.
> Perhaps the console and kernel are working fine, and you just messed up
> the I/O pins for SMC1.

All pin assignments are correct, and during setting port B, we checked the pbpar,pbdir,pbodr also. nothing changed.


> You will also need to make source code changes to enet.c, as it doesn't
> have a standard set of instructions for configuring port B as Ethernet
> control/data pins.

We've changed all port configurations.
>
>
> -- Dan
>

Do you have any code which enables SCC3 for ethernet on 850SAR?


Thank you


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-07-27 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-27  7:23 Req. help about SCC2 and SCC3 as ethernet Hyun-Joon Cha
2000-07-27 14:00 ` Dan Malek
2000-07-27 14:38   ` Hyun-Joon Cha [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='01ff01bff7d8$4b122460$1952df8d@SOYANG' \
    --to=tachyon@postech.ac.kr \
    --cc=dan@netx4.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).