From: "Jeyner Gil Caga" <jeynergilcaga@gmail.com>
To: "- Reyneke" <reynekejunk@hotmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Eth1 init and link status
Date: Wed, 19 Sep 2007 23:35:27 +0800 [thread overview]
Message-ID: <cad107560709190835t5067c23fv52d5e97d39f6f69d@mail.gmail.com> (raw)
In-Reply-To: <BAY101-F3306F36C70FAA4D450C466BEB90@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
In you statement, initialise correctly (i.e. receive and transmit), did you
use like ping or ftp to do it?
What do you mean by the word initialise?
Are you saying that after Linux has completely booted up:
1. you have one computer pinging to eth0 and you can ping eth0?
2. if eth0 is connected to the network, you use the same computer to ping
eth1 and you can ping eth1?
3. while you are pinging eth1 and you disconnect eth0 from the network,you
can not ping eth1?
On 9/19/07, - Reyneke <reynekejunk@hotmail.com> wrote:
>
> HI,
>
> We've run into a bit of an odd problem and we are not sure where to go and
> look for the cause.
>
> We have some 440EPx based hardware with two GIG-Ethernet ports using RGMII
> and 2x ET1011C PHY's. Problem is that eth1 will only initialise correctly
> (i.e. receive and transmit) if eth0 has a link. Eth0 always work OK,
> regardless of eth1 status. Eth1 will work OK if eth0 has a link (i.e.
> initialised) at time of setup. Once initialised, eth0 status is
> irrelevant.
> All this is during Linux boot process.
>
> Any ideas?
>
> We can access PHY registers via u-boot (mii commands). Same 1Gig link
> speed
> is used on both ports. Linux kernel is 2.6.19.
>
> Regards
> Jan Reyneke
>
> _________________________________________________________________
> Can you see your house from the sky? Try Live Search Maps
> http://maps.live.com
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
[-- Attachment #2: Type: text/html, Size: 2098 bytes --]
prev parent reply other threads:[~2007-09-19 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 13:54 Eth1 init and link status - Reyneke
2007-09-19 14:02 ` Josh Boyer
2007-09-19 15:35 ` Jeyner Gil Caga [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=cad107560709190835t5067c23fv52d5e97d39f6f69d@mail.gmail.com \
--to=jeynergilcaga@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=reynekejunk@hotmail.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 NNTP newsgroup(s).