From: Dan Malek <dan@mvista•com>
To: Brian Ford <ford@vss•fsi.com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: EST SBC8260 and Canary CTX-1170
Date: Tue, 28 Nov 2000 17:04:21 -0500 [thread overview]
Message-ID: <3A242BE5.C34D48FC@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0011281308070.493-100000@eos
Brian Ford wrote:
> So does this mean that a "complete" implementation would have a
> "command/status MII interface" or that a "complete" implementation does
> not need one?
The complete implementation should have a real command/status MII
interface.
> Can you help point me to where I need to write code that would initialize
> the FCC to do full duplex,
I just checked in the newer driver that will properly do this on
the EST board with the National PHY in the CTX-1170 gizmo. If for
some reason this doesn't work, just modify mii_discover_phy_poll() to
set 'phy_duplex' to '1'.
I checked this into linuxppc_2_5 BitKeeper on FSM Labs. My 2.3/2.4
kernel is broken and I need to clone a new tree before I can make
changes. That will take a little while......
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-28 22:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-27 20:09 MP8240 UART Dan Jankins
2000-11-27 20:24 ` Dan Malek
2000-11-27 20:36 ` Mark A. Greer
2000-11-27 23:09 ` EST SBC8260 and Canary CTX-1170 Brian Ford
2000-11-28 3:14 ` Dan Malek
2000-11-28 19:19 ` Brian Ford
2000-11-28 22:04 ` Dan Malek [this message]
2000-11-28 22:33 ` Brian Ford
2000-11-28 23:28 ` Dan Malek
2000-11-29 18:18 ` Brian Ford
2000-11-30 14:47 ` diekema_jon
2000-11-30 17:51 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-11-30 16:03 Jerry Van Baren
2000-11-30 18:41 Gessner, Matt
2001-03-08 15:39 Oliver Brown
2001-03-09 0:36 ` Dan Malek
2001-03-09 3:07 ` David Schleef
2001-03-09 4:23 ` Dan Malek
2001-03-09 4:55 ` David Schleef
2001-03-09 4:54 ` Dan Malek
2001-03-09 5:07 ` David Schleef
2001-03-11 13:28 Oliver Brown
2001-03-11 14:19 ` Wolfgang Denk
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=3A242BE5.C34D48FC@mvista.com \
--to=dan@mvista$(echo .)com \
--cc=ford@vss$(echo .)fsi.com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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