From: Robert Morse <rmorse@weldtechcorp.com>
To: Edgar Grimberg <edgar.grimberg@zylin.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: PowerPC Ethernet issue
Date: Mon, 08 Jun 2009 10:56:00 -0000 [thread overview]
Message-ID: <1244458362.31511.0.camel@win0040> (raw)
In-Reply-To: <d0f570ed0906060830p56941bccke9a8565e675b2fcb@mail.gmail.com>
Thanks,
That is what I thought I needed to do.
Robert
On Sat, 2009-06-06 at 17:30 +0200, Edgar Grimberg wrote:
> Hi,
>
> >
> > Looking at the situation, it seems like I would need to
> > enable/configure the interrupts for the PHYs. and when a change of
> > duplex is detected cause a reset of the MAC. Has anyone done anything
> > like this before. Looking through the ethernet drivers and phy drivers
> > I do not see anyone doing this (I admit not all).
> >
>
> This looks like the only place to detect if the connection parameters
> have changed (link, duplex, speed).
>
> > Does my idea seem sound, or am I off in the woods somewhere. I know
> > about this duplex issue from another design. Where we had a commercial
> > rtos, that I found out they did not do this and caused a lot of issues,
> > I thought the device driver should of handled it, but they said it was
> > up to the application to control the bit. So I do want to repeat the
> > same issue.
>
> I have some code so show that, but it might not fit your device. The
> idea is to stop and start the ethernet device in the PHY's DSR. In the
> start function, if the ethernet is not already started, you can
> renegotiate the connection parameters.
> The code is at:
>
> http://www.ecosforge.net/ecosforge/trunk/ecos_mpc8313/packages/devs/eth/powerpc/quicc2pro/current/src/tsec.c
>
> search for:
>
> tsec_eth_start
> phy_dsr
> phyAutoNegociate
>
> Best regards,
> Edgar
next prev parent reply other threads:[~2009-06-08 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 15:32 Robert Morse
2009-06-06 15:30 ` Edgar Grimberg
2009-06-08 10:56 ` Robert Morse [this message]
2009-06-08 11:21 ` Edgar Grimberg
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=1244458362.31511.0.camel@win0040 \
--to=rmorse@weldtechcorp.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=edgar.grimberg@zylin.com \
/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).