mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Atilla Filiz <atilla.filiz@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: How to debug Ethernet connectivity
Date: Fri, 6 Dec 2013 13:18:52 +0100	[thread overview]
Message-ID: <CACTZKX5mv6bjbUoWK81BioH3FEboMtN2jOaRQG3eRLbMg97FXA@mail.gmail.com> (raw)
In-Reply-To: <CACTZKX4Phn_pOkEK5SUAva=dAig9rX3eD=ckzadNM9Ht1bLC7Q@mail.gmail.com>

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:

On Fri, Dec 6, 2013 at 1:17 PM, Atilla Filiz <atilla.filiz@gmail.com> wrote:
> On Fri, Dec 6, 2013 at 11:52 AM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
>> There is miitool command to view MII status / registers.
>
>
> How do I use it?
> barebox@Terminal:/ miitool -v /dev/mc13xxx
> 10 Mbit, half duplex, no link
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: no link
>   capabilities:
>   advertising:
> barebox@Terminal:/ dhcp
> T DHCP client bound to address 10.3.4.161
> barebox@Terminal:/ miitool -v /dev/mc13xxx
> 10 Mbit, half duplex, no link
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: no link
>   capabilities:
>   advertising:
>
> But there is link, obviously.
> --
> Atilla Filiz



-- 
Atilla Filiz

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-12-06 12:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 10:21 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 [this message]
2013-12-06 12:21       ` Alexander Aring
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=CACTZKX5mv6bjbUoWK81BioH3FEboMtN2jOaRQG3eRLbMg97FXA@mail.gmail.com \
    --to=atilla.filiz@gmail.com \
    --cc=antonynpavlov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox