public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Robert Morse <rmorse@weldtechcorp.com>
To: ecos-devel@ecos.sourceware.org
Subject: PowerPC Ethernet issue
Date: Fri, 05 Jun 2009 15:32:00 -0000	[thread overview]
Message-ID: <1244215787.30295.28.camel@win0040> (raw)

Hi all,

	We are working on a PowerPC ppc405 (AMCC 405ep) based board.  We are
using the following drivers from ECOS v2.

A slight change to the hal/powerpc/.. directory to support our devices.
A change to devs/eth/powerpc/ppc405 directory to support dual ethernet.
Then a new devs/eth/phy to support the national DP8348C part.

	Looking at the data sheet for the 405EP processor, the MAC has a bit
that tells the ethernet channel if it is FULL or HALF duplex mode.  And
on initialization or any time a Ethernet Reset is required we do set it
to the correct Duplex.  My current issue is what happens if someone
unplugs changes the duplex and plugs back in.  I see nothing that will
update the duplex.  

	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).

	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.

Thanks
    Robert





             reply	other threads:[~2009-06-05 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 15:32 Robert Morse [this message]
2009-06-06 15:30 ` Edgar Grimberg
2009-06-08 10:56   ` Robert Morse
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=1244215787.30295.28.camel@win0040 \
    --to=rmorse@weldtechcorp.com \
    --cc=ecos-devel@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).