From: "Ed Henderson" <ednh@cypress.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: National Semi DP83865 Phy on custom hardware with PPC 8540 CPU
Date: Thu, 26 Jun 2008 20:45:24 -0600 [thread overview]
Message-ID: <018a01c8d7ff$d93f3650$8bbda2f0$@com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Greetings.
I am a hardware engineer and I designed a board based on a Power PC MPC8540
CPU. The hardware was patterned after another board with a Marvel driver. I
had some difficulty locating the Marvel Chips, so I used a National
Semiconductor DP83865 Phy instead, available at Digikey. We looked at this
and felt it would not be too difficult to adapt the current Kernel code to
this phy. In practice, now that we have hardware built, it is proving to be
a bit more difficult to bring up. It is very interesting that u-boot
contains code for this Phy, and we are able to get to the u-boot command
line, setup and Ethernet address, ping and even do a tftpboot kernel
transfer. Unfortunately, in the Kernel, we do not have the same success.
This seems to indicate that the hardware is working, at least to some
degree.
We did some modifications on the Marvel driver in order to 'attempt' to
adapt it to the National Phy. To be honest, we are not that familiar with
this aspect of Kernel development, so we could really use some
pointers/tips/assistance. There are some file geared toward the DP83865,
but they are "PCI" drivers. Our Phy is directly connected to the PPC. I do
not know if it make sense to start with the natsemi.c file (which is geared
toward PCI), or to make our changes to the Marvel phy.
I would appreciate any help in resolving this issue.
Regards,
Ed Henderson
[-- Attachment #2: Type: text/html, Size: 3499 bytes --]
reply other threads:[~2008-06-27 2:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='018a01c8d7ff$d93f3650$8bbda2f0$@com' \
--to=ednh@cypress.com \
--cc=linuxppc-embedded@ozlabs.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).