From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001235] National Semiconductor DP83848 PHY
Date: Fri, 22 Jul 2011 16:54:00 -0000 [thread overview]
Message-ID: <20110722165403.45BC92F7800B@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001235-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001235
--- Comment #1 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-07-22 17:54:01 BST ---
(In reply to comment #0)
> Created an attachment (id=1239)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1239) [details]
> Added National Semiconductor DP83848 PHY
Hi Christophe,
IMHO, we can add only new _eth_phy_dev() entry for DP83848 PHY IDs to
DP83847.c, look at page #6, please:
http://www.national.com/an/AN/AN-1425.pdf
as DP83847 driver follows IEEE standard (registers).
It seemed to me that we could set ``DP8384x`` as *display* string for
CYGHWR_DEVS_ETH_PHY_DP83847 option and add new entry to DP83847.c only.
Well, to rename the option to CYGHWR_DEVS_ETH_PHY_DP8384X it would be
nice, but the option's name is already taken by a few powerpc targets.
However, may be to have a few DP8384x.c sources and a few CDL options
is prefered then. What others think?
Sergei
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-07-22 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 16:44 [Bug 1001235] New: " bugzilla-daemon
2011-07-22 16:54 ` bugzilla-daemon [this message]
2011-07-22 17:34 ` [Bug 1001235] " bugzilla-daemon
2011-07-22 18:30 ` bugzilla-daemon
2011-07-22 18:46 ` bugzilla-daemon
2011-07-23 11:34 ` bugzilla-daemon
2011-07-23 11:45 ` bugzilla-daemon
2011-07-23 17:33 ` bugzilla-daemon
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=20110722165403.45BC92F7800B@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).