From: Dan Malek <dmalek@jlc.net>
To: RTHEANDE <rtheande@dscc.dk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PHY driver for 860T
Date: Tue, 12 Jan 1999 17:16:54 -0500 [thread overview]
Message-ID: <369BC9D6.205B4494@jlc.net> (raw)
In-Reply-To: 9901129161.AA916142427@smtplink.dscc.dk
RTHEANDE wrote:
> Hi there,
>
> I'm building a board with an MPC860T that's supposed to run LinuxPPC.
No problem. I do it every day :-).
> ....... This board should have a 100baseTX PHY chip from
> Level One. If the above information is correct, could someone please
> take a look and tell me which chip they use.
I did the original development of the FEC driver on the 860T FADS board.
I uses the Level One LTX970 part.
I have another board in hand right now that uses the Quality Semiconductor
QS6612 part. I'll have the driver ready pretty soon.
This increases the complexity of the MII functions in the current FEC
driver. I will probably use the de4x5.c as a model. We now have to
determine which PHY is used and program accordingly. The driver
currently does not support multiply PHYs, and I don't intend to do
the modification until I have such a configuration. There is currently
and assumption the PHY address is known and fixed (by default it
is device 0).
I have tested this driver with both 10 and 100 Mbit networks, however
I have not found a full duplex 100 Mbit for testing. The FEC needs to
be reprogrammed when this is detected.
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-01-12 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-12 11:59 PHY driver for 860T RTHEANDE
1999-01-12 12:55 ` Helmut Buchsbaum
1999-01-12 22:16 ` 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=369BC9D6.205B4494@jlc.net \
--to=dmalek@jlc.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rtheande@dscc.dk \
/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).