From: Alexander Aring <alex.aring@gmail.com>
To: Atilla Filiz <atilla.filiz@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: How to debug Ethernet connectivity
Date: Fri, 6 Dec 2013 13:21:22 +0100 [thread overview]
Message-ID: <20131206122121.GA22571@omega> (raw)
In-Reply-To: <CACTZKX5mv6bjbUoWK81BioH3FEboMtN2jOaRQG3eRLbMg97FXA@mail.gmail.com>
On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
> Sorry, figured it out. Just most verbose output is funny as well:
> :/ miitool -vvv /dev/mc13xxx
> 10 Mbit, half duplex, no link
> registers for MII PHY:
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> product info: vendor 00:00:00, model 0 rev 0
> basic mode: 10 Mbit, half duplex
> basic status: no link
> capabilities:
> advertising:
>
In my opinion you reading only zeros from bus. Maybe check your muxing
which Sascha already mentioned.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-12-06 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:21 How to debug Ethernet connectivity Atilla Filiz
2013-12-06 10:34 ` Sascha Hauer
2013-12-06 10:52 ` Antony Pavlov
2013-12-06 12:17 ` Atilla Filiz
2013-12-06 12:18 ` Atilla Filiz
2013-12-06 12:21 ` Alexander Aring [this message]
2013-12-06 12:39 ` Sascha Hauer
2013-12-06 12:43 ` Alexander Aring
2013-12-10 13:31 ` Atilla Filiz
2013-12-10 15:24 ` Antony Pavlov
2013-12-10 17:46 ` Alexander Aring
2013-12-11 9:39 ` Atilla Filiz
2013-12-11 10:28 ` Sascha Hauer
2013-12-10 15:30 ` Antony Pavlov
2013-12-11 10:25 ` Sascha Hauer
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=20131206122121.GA22571@omega \
--to=alex.aring@gmail.com \
--cc=atilla.filiz@gmail.com \
--cc=barebox@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.